JP4979448B2 - Component data receiving apparatus, component mounter, component data receiving method, and program - Google Patents

Description

The present invention relates to a component data receiving method for receiving a part product data that is used in the component mounting machine when mounting the components on a substrate, a technique especially activate the circulation of the component data.

  Conventionally, with regard to component mounters that mount components on boards, service supply that provides users with various support data such as sales information, electronic manuals, virtual training, and mounted component data (hereinafter simply referred to as component data) via the Internet A method is known (see, for example, Patent Document 1).

  Among these, in particular, for component data that is data used by a component mounter when mounting a component on a board, Patent Document 1 describes that component data with a track record of producing non-defective products is held in a service supply device, and the component data Or a range designated by a component mounter, component type, etc., is supplied to the service receiving device (paragraph 0153). As a result, by receiving component data corresponding to the type of component or circuit board to be used, it is said that even a simple operator can perform good mounting production.

Such component data can be provided from a user who has successfully produced non-defective products. In order to facilitate the provision of part data, a well-known technique for returning rewards to the provider may be used.
Japanese Patent No. 3626578

  However, according to the technique of the above-mentioned Patent Document 1, since the part data is the object of distribution only after the achievement of good product production, the quality of the distributed part data is maintained very high, but the part data is distributed. The number will be sluggish due to the time and effort it takes to target.

  In addition, for each user, the parts data that has been completed before the achievement of good product production is know-how with various ideas, trial and error, and ingenuity, and such valuable information should be disclosed to third parties. The sense of resistance to the situation is also one of the factors that slow the distribution of component data.

  The present invention has been made in view of such circumstances, and a component data supply method and a component data receiving method for activating the distribution of component data and thereby improving the efficiency of production performed using a component mounter. It aims to provide a method.

In order to achieve the above object, the component data receiving method according to the present invention, the receiving Oite the component data receiving device, component data used in the component mounting apparatus for mounting on a substrate a component from a component data providing device A component data receiving method for transmitting a search condition to the component data supply device, wherein the component data receiving device identifies one or more component data that match the search condition, and A part that obtains a search result including the result data indicating the degree of work necessary for successful production using each part data from the part data supply device, and presents the obtained search result to the operator receiving a data retrieval step, the component data receiving device, an operation of selecting one or more component name from the displayed search results from the operator And component data selection step of applying, the component data receiving device by transmitting an acquisition request specifying the component name said selected into the component data supply device, component data specified by the part name said selected only contains the component data acquisition step of acquiring from the component data supply device, is still without a track record of good production, it is distributed together with the doneness data the component data work are still required before a successful actual production Thus, it is possible for the user of the component mounter to determine whether or not to utilize the component data from the result data .

  According to this configuration, even part data that has not yet been produced in good quality and has the work necessary to succeed in actual production is collected and used together with the result data representing the work. The number of parts data to be distributed increases and the distribution of parts data is activated.

  Various parts data will be distributed, but when receiving the part data, the part data to be acquired is shown to the operator in advance, so the operator can send the part data according to the condition. Can be selected.

  In order to encourage the provision of part data, the part data supply method further includes, for each part data, a reward determination step for determining a reward according to the corresponding performance data, and a part data corresponding to the determined reward. A reward accumulation step of accumulating in association with the provider.

  Further, when the component data providing device is realized as a component mounter, the component mounter performs notification in the component mounter in order to promote provision of component data having a production record in the component data collection step. Parts data with production results in the mounting machine may be collected.

  According to this configuration, there is an increased possibility that component data with production results can be collected directly from the component mounter.

In addition, when the component data receiving device is realized as a component mounting machine, the component data supply method is further acquired when the component data supply device sends a component verification from the component mounting device. Upon request, the component data may include component data supply step of supplying to the component mounting machine.

  According to this configuration, necessary component data is supplied when necessary in the component mounter, which is useful for improving the efficiency of production performed using the component mounter.

Also, parts the component data receiving device if it is implemented as a component mounting machine, the component data supply method further the component data supply apparatus, in free, to provide the component data to the component mounting machine A data supply step may be included .

  According to this configuration, it is possible to appeal the introduction merit to the prospective customer of the component mounting machine by appealing that the component data is provided free of charge.

Also, the component data supply method further the component data supply device, the component data to which the collected when you supplied to the component data receiving device, used in accordance with the doneness data of the component data to be supplied fees May include a usage fee payment instruction step of notifying the component data receiving apparatus of the payment instruction.

  According to this configuration, since the efficiency of collecting the fee for use as a source of reward is improved, it is useful for smoothly encouraging provision of part data by reward.

The present invention not only can be realized as such a part goods data receiving method, apparatus for performing the method, it is realized as a storage medium for storing system including the apparatus, a program, the program Can do.

According to Part goods data receiving method and the like of the present invention, yet without proven good production, even parts of data remaining work required before a successful actual production, since circulating with doneness data representing the work The component mounter user can look at the result data and determine whether the component data can be used immediately or how much adjustment is required on the actual device. As a result, it is possible to quickly bring up the part data to a level where it can be produced. The provision of parts data is facilitated by rewards according to their performance and usage.

  As a result, various kinds of component data are collected by the server device as the component data supply device and are distributed, increasing the opportunity for the component mounter to obtain usable component data. When acquiring the part data, the operator can select and acquire the part data in the required condition by confirming the condition of the part data to be acquired.

  As a result, adjustment work of parts data by trial and error and improvement work of parts data by analysis of defects are reduced, so that the production resources required in the prototype process up to the production of non-defective products are optimized. Here, the optimization of the production resource corresponds to, for example, reduction of the number of work man-hours, reduction of electric power, fuel, water, and reduction of prototype materials.

  Furthermore, the quality of a product manufactured in a non-defective product production process is improved by acquiring component data of a desired quality (that is, well-considered and having a high degree of completeness) from a server device and using it on a component mounter. . As a result, the power consumption of the product itself is reduced and the service life is extended, which contributes to social and energy savings and resource savings.

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

<System configuration>
FIG. 1 is a configuration diagram showing an outline of a component data distribution system according to an embodiment of the present invention.

  The component data distribution system 1 includes a server device 10 and a plurality of terminal devices 20 connected via a network 30. Here, the server device 10 is an example of a component data supply device, and the terminal device 20 is an example of a component data providing device and a component data receiving device.

  In FIG. 1, a server device 10 is a computer installed at a service base of a component mounter manufacturer as an example, and each terminal device 20 is realized as a component mounter installed at a factory of a component mounter user as an example. The

  In the component data distribution system 1 configured as described above, the server device 10 and the plurality of terminal devices 20 exchange component data via the network 30 to distribute component data. Here, the component data is one of the data used by the component mounter when mounting the component on the board, and minimizes the mounting error of the component in addition to the data related to the component itself such as the dimension of the component. The data for determining the device conditions for each model of the component mounting machine is included. The component data is taught to the component mounter together with NC data that specifically defines where and in what order on the board, and is used for controlling the component mounter when mounting the component on the board.

  The server device 10 collects and registers 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 supplies the registered component data to a second terminal device that is different from the first terminal device. The second terminal device receives the component data supplied from the server device 10 and uses the received component data. In this way, the server device 10 distributes the component data.

  Accordingly, the server device 10 functions as a component data distribution device that distributes component data, and also functions as a component supply device that supplies the component data to the second terminal device. The first terminal device functions as a component data providing device that provides component data to the server device 10. In addition, the second terminal device functions as a component data receiving device that receives component data from the server device 10.

  In the distribution of the component data, for example, first, the terminal device 20 which is a component mounting machine of the company A-1 factory sends the component data created in the terminal device 20 to the server device 10 at the service base together with the result data. The server device 10 at the service base receives the component data and newly registers it.

  Here, the completion status data represents the degree of work required for successful actual production using the component data. In other words, the result data is adjusted, for example, in order to improve the current part data up to the stage of realizing the non-defective product production and what is lacking in the current part data to the stage of realizing the good product production. This is an index indicating what kind of work such as work is necessary.

  At this time, unlike the prior art, the terminal device 20 sends, to the server device 10, component data that indicates that the quality data has not yet been successfully produced and the work remains until the actual production is successful. It is allowed to send.

  The component data newly registered in the server device 10 is acquired by the component mounting machine in the company A-2 factory, supplemented and adjusted according to the quality of the product, and successfully produced non-defective products. The server device 10 updates and registers the adjusted component data.

  Then, the adjusted component data updated and registered in the server device 10 is acquired by the component mounting machine in the B company B-1 factory, and used as it is for non-defective product production.

  New and updated registrations of part data are encouraged by rewards that are returned to the part data provider on a performance basis. The returned reward is stored in the server device 10 in association with the provider of the component data.

<Configuration of server device and terminal device>
FIG. 2 is a block diagram illustrating an example of a functional configuration of the server device 10 and the terminal device 20. In FIG. 2, a network 30 that connects the server device 10 and the terminal device 20 is also depicted.

  The server device 10 is a device that collects component data and corresponding result data from the terminal device 20, and supplies the collected component data to one of the terminal devices 20. The component data storage unit 11, component data It comprises a supply unit 12, a communication I / F (interface) unit 13, a component data collection unit 14, a reward determination unit 15, and a reward storage unit 16. The component data supply unit 12 includes a search unit 121 and a usage data recording unit 122.

  The component data collection unit 14 receives the component data and the corresponding condition data from the terminal device 20 and stores the received component data and the condition data in the component data storage unit 11.

  When a search condition specifying a part name is given from the terminal device 20, the search unit 121 searches the part data storage unit 11 for one or more parts data that matches the given search condition. The search result including the part name and the model name of the component mounter, which are identification keys of the searched part data, and the corresponding result data is transmitted to the terminal device 20.

  When receiving an acquisition request specifying one or more identification keys included in the search result from the terminal device 20, the component data supply unit 12 supplies the component data identified by the identification key to the terminal device 20.

  When the component data is supplied and when a complaint about the component data is received from the terminal device 20, the usage data recording unit 122 displays the number of component data used and the number of complaints recorded in the component data storage unit 11. Update usage data to represent. Here, the claim for the component data is component data such that the component is tried to be mounted using the component data, but the component is not attracted to the mounting head, or the component is dropped from the mounting head during the suction transfer. This is information indicating a problem caused by the deficiency.

  The reward determination unit 15 determines a reward according to the performance data and usage data stored in the part data storage unit 11 corresponding to the part data, and associates the determined reward with the provider of the part data. Is accumulated in the reward accumulation unit 16.

  Here, it should be noted that there can be a plurality of parts data providers for one part name. For example, the parts data is produced by non-defective products by multiple providers, such as the provider of shape data first, the provider that supplemented the mounting data, and the provider that modified the mounting data to the stage of successful trial run and actual production. Is completed step by step so that the reward is stored in the reward storage unit 16 in association with each provider.

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

  The terminal device 20 is a device that provides component data to the server device 10 and acquires and uses component data already registered in the server device 10. As an example in the case of being realized as a component mounter, 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, and a result level The determination unit 27 and the component data registration unit 28 are included. The mounting 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 to mount the component on the board.

  The mounting mechanism unit 25, for example, a substrate table on which a substrate is placed, a component supply unit that supplies each component from a component storage tape that stores a plurality of components, and sucks and transfers the components to a target position on the substrate. It is configured to include a mounting head to be mounted and a camera for recognizing the suction state of components. Since the mounting mechanism unit 25 is not the subject of the present invention, it is assumed to be realized by using a well-known technique, and detailed description thereof is omitted.

  When the component storage tape is mounted, the component supply unit performs a collation process for reading the component name from a barcode or IC tag attached to the component storage tape, and notifies the mounting control unit 21 of the read component name.

  If there is no component data identified by the notified component name and the model name of the component mounting machine itself and indicated that the actual production has been successful based on the result data, the component data acquisition unit 211 Then, the search condition specifying the part name is transmitted to the server device 10. Then, a part name and a model name of the component mounting machine that are identification keys for the part data that matches the search condition, and corresponding performance data are acquired from the server device 10 and displayed on the operator I / F unit 22.

  The operator I / F unit 22 is, for example, a liquid crystal display attached to the housing of the component mounting machine, a touch panel provided on the front surface of the liquid crystal display, and a keyboard.

  The component data acquisition unit 211 receives an operation for selecting component data according to the degree of completion through the operator I / F unit 22 and transmits an acquisition request including an identification key of the selected component data to the server device 10. Thus, the component data identified by the identification key is acquired and stored in the component data storage unit 23.

  The component data input unit 26 receives an input received via the operator I / F unit 22 when no component data is retrieved from the server device 10 or when only component data with insufficient performance can be acquired. In accordance with the operation, new part data is created, or the part data is supplemented or corrected. Then, the newly created part data or the part data after supplement or correction is stored in the part data storage unit 23.

  The mounting control unit 21 uses the component data stored in the component data storage unit 23 in this way to perform a trial operation for mounting production and actual production. The component data input unit 26 further performs rough adjustment and fine adjustment of the component data according to the input operation received through the operator I / F unit 22 in the initial stage of the trial run and actual production.

  The completion condition determination unit 27 determines the completion condition data according to the state of the component data, and records it in the component data storage unit 23. The completion condition determination unit 27 re-determines the completion condition data and updates the component data storage unit 23 according to the change in the state of the component data. A specific example of work required for successful actual production according to the state of the part data and details of the result data will be described later.

  The component data registration unit 28 notifies the operator I / F unit 22 of notification for promoting registration of the component data in the server device 10 when the result data of the component data is determined and updated. In response to the operator's response operation, the component data and the corresponding result data are registered in the server device 10.

<Part data>
The component data will be described in detail.

  FIG. 3 is a top view showing an example of a component. This part has a rectangular body when viewed from above and has leads extending outward from two opposing sides. The shape of all parts sharing this feature is determined using the same dimension items as in FIG.

  4A and 4B are diagrams illustrating an example of component data stored in the component data storage unit 11 of the server device 10 and the component data storage unit 23 of the terminal device 20, and FIG. An example for the components shown is shown.

  FIG. 4A shows a common part 110 of the component data that does not depend on the model of the component mounter, and shows shape data representing the dimensions of the component as an example. One part has one common part.

  Here, the shape type represents the feature of the shape of the part, and each item of the shape data represents the size of each part appearing in the top view of the part shown in FIG. The same shape type may be given to all parts whose shapes are determined by the same dimension item.

  FIG. 4B shows a model-dependent part 111 of the component data that depends on the model of the component mounting machine. As an example, the number of usages of mounting data and component data that defines device conditions for minimizing component mounting errors. And usage data representing the number of claims generated, and operation data representing the number of mount trials and the number of successes in the component mounter. One component can have a model-dependent part of the number of models of component mounters to be applied.

The performance data is recorded in this model-dependent part.
In the mounting data, the recognition part defines a recognition part image that becomes a reference for detecting the component adsorption deviation, the illuminations 1 and 2 determine the optimum illumination intensity for recognition of the part, and the nozzle and the movement acceleration are respectively mounted. Determine the optimum conditions for picking up and transferring the parts by the head.

  The operation data item can be omitted in the component data storage unit 11, and the usage data item can be omitted in the component data storage unit 23.

  FIG. 5 is a diagram illustrating an example of a recognition site image. The recognition site image R11 shown in this example defines a lead position that appears in an image taken when the mounting head sucks the component shown in FIG. 3 as a reference.

  A deviation between the lead appearing in the image obtained by actual imaging and the lead appearing in the recognition site image is detected as an adsorption deviation, and the attachment error is minimized by correcting the detected adsorption deviation.

<Performance data>
The result data will be described in detail.

FIG. 6A and FIG. 4B are diagrams for explaining the result data.
FIG. 6A shows an example of the work necessity table 150. The work necessity table 150 shows the part data at that stage corresponding to the plurality of stages of the part data for a plurality of works generally performed on the part data until the actual production is successful. It is a matrix that indicates whether each operation is unnecessary or still necessary by using it. Each row of the work necessity table 150 represents work such as “creation of shape data” and “creation of mounting data”, and each column represents a stage of completion such as “no part data” and “with shape data”. At the intersection of the matrix, it is indicated by ◯ that the work is still necessary when the part data at that stage is used, and by × that it is not necessary.

  For example, the column of the intersection between the “shape data creation” row and the “no component data” column is marked with ◯. This indicates that when the degree of part data is in a stage where no part data exists (or even shape data does not exist), an operation of “shape data creation” is necessary.

  Further, the column of the intersection between the “shape data creation” row and the “shape data present” column is marked with “x”. This indicates that when the result of the part data is in the stage where the shape data has already been created, the work of “shape data creation” becomes unnecessary by using the part data. .

  The work necessity table 150 further shows a cost value representing the labor and difficulty of each work. This cost value is reflected in rewards for providing component data, as will be described later.

  Here, as specific examples of the work described above, shape data (part data mounting machine model common part) creation, mounting data (model dependent part) creation, mounting data coarse adjustment in trial operation, and mounting data fine adjustment in actual production 4 types are illustrated. And the cost value of each operation | work is set to 10, 30, 50, and 10 as an example. Further, as the above-mentioned stage of completion, there are specifically illustrated five types: no part data, shape data, mounting data, trial operation success, and actual production success.

  When there is no part data at all, all work after creation of shape data is required before successful production using part data. When there is only shape data, work after creation of mounting data is required. In the stage where there is mounting data, work after the rough adjustment of mounting data in the trial run is necessary. Not shown.

  The work necessity table 150 is used for the explanation in the present embodiment, and the server device 10 and the terminal device 20 are not necessarily provided.

  FIG. 6B is a diagram illustrating an example of the completion status table 151. The performance level table 151 stores different level values and reward points corresponding to the above-described 5 types of levels of performance level. Specifically, the reward points are indicated as unnecessary by the work necessity table 150 corresponding to the stage (the work indicated as unnecessary (×) in each stage (column) in FIG. 6A). The total cost value of

  This total value is the sum of the amount of work and difficulty considered to have been input to the part data until the part data is at that stage, and is one specific example of reward value. Represents. The larger the total value, that is, the larger the step value of the completed condition, the smaller the degree of work required for successful actual production using the part data.

The performance status table 151 is provided in the reward determination unit 15 of the server device 10.
Such reward points are preferably determined to be higher as the difficulty related to the creation of the part data is higher or the time and effort is increased. Therefore, for example, considering the difficulty and effort involved in creating part data related to the part shape, a plurality of performance tables that define different reward points corresponding to a plurality of shape types representing different part shapes. 151 may be provided, and reward points may be determined according to a performance table corresponding to the shape type of the component data.

  FIG. 7A is a diagram illustrating an example of a component that has a relatively high level of difficulty in creating component data, and FIG. 7B is a diagram illustrating an example of a recognition site image of the component. For such a component, a shape type different from the shape type of the component shown in FIG. 3 is determined. As a general example, a component having a circular main body has a high difficulty because it is difficult to determine a portion where angular deviation can be detected with high accuracy, and a component having a large number of leads is laborious.

<Reward data>
The reward data will be explained in detail.

  FIG. 8 is a diagram illustrating an example of the reward table 160. The reward table 160 is provided in the reward storage unit 16 of the server device 10.

  In the reward table 160, for each new registration and update registration of part data, the registration date and time, the provider of the part data, the part name that is the part data identification key, the model name of the part mounting machine, and the result data before and after registration , And reward points returned to the provider are recorded as reward data.

  Further, in the reward table 160, for each acquisition of the component data, the acquisition date and time, the acquirer of the component data, the component name that is the identification key of the component data and the model name of the component mounting machine, the result data at the time of acquisition and the acquisition An imposition point (that is, a usage fee) imposed on a person may be recorded as imposition data.

  The reward determination unit 15 records the reward data and the imposed data in the reward table 160.

  Specific contents of the reward data and the imposition data recorded in the reward table 160 will be described with reference to the third and fourth lines in FIG. 8 as an example.

  The reward data on the third line is the part with the grade value of “3” when the part data with the grade value of “1” has already been registered (the grade before completion is “1”). Data is recorded when the terminal device 20 registers with the server device 10 (the result is “3” after registration).

  Before and after the registration, reward points corresponding to the degree of the part data increase from “10” to “90” (see FIG. 6B). 80 ”is determined as a reward point for the provider“ C3 ”and recorded as the reward data.

  Further, the imposition data on the fourth line is recorded when the terminal device 20 has acquired the part data having the step value of “4” from the server device 10 (the result of registration is “4”).

  Since the reward point corresponding to the degree of completion of the acquired parts data is “100” (see FIG. 6B), the reward determination unit 15 imposes the reward point “100” on the acquirer “C4”. It is determined as a point and recorded as the imposed data.

  By referring to the reward table 160, the cumulative total of reward points returned to the provider is calculated for each provider, and the cumulative total of imposed points imposed on the acquirer is calculated for each acquirer. be able to.

  In addition, considering that parts data is generally acquired and used by multiple acquirers, each acquirer pays a point obtained by multiplying the charge points by a predetermined rate (about several percent) as the actual usage fee. It is good as well.

<Detailed operation of server device>
The operation of the server device 10 will be described in detail using a flowchart.

  FIG. 9 is a flowchart showing a detailed operation of the server apparatus 10. In this flowchart, main operations of the server device 10 that processes various requests related to the component data from the terminal device 20 are shown.

  The server device 10 repeats the following process until receiving an operation end instruction (NO in S401).

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

  When the search condition is received (search condition in S403), the search unit 121 searches the component data storage unit 11 for one or more component data that matches the received search condition, and identifies the searched component data. A search result including the key component name, the component mounter model name, and the corresponding performance data is transmitted to the terminal device 20 (S412).

  If there is no part data that matches the search condition, the search unit 121 includes, for example, part data of another part with the same manufacturer and a similar part name in the search result, and further includes part data that matches the shape type in the search result. For example, the search range may be expanded step by step. Further, part data of parts from other manufacturers whose shape types match or are similar may be included in the search range. Obtaining parts data for similar parts across multiple manufacturers as a search result is useful for quickly obtaining parts data when, for example, similar parts from other manufacturers are used instead of parts because they are out of stock. .

  When a component data acquisition request specifying a component name as a component data identification key and a model name of the component mounting machine is received (component data acquisition request in S403), the component data supply unit 12 receives the received acquisition request. The component data identified by the identification key included in is acquired from the component data storage unit 11 and transmitted to the terminal device 20 (S421). At this time, the use number of the component data identified by the identification key in the component data storage unit 11 is incremented (S422).

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

  The reward determination unit 15 rewards the acquisition date and time, the acquirer of the component data, the component name that is the identification key of the component data, the model name of the component mounting machine, the result data at the time of acquisition, and the imposition points imposed on the acquirer. The data is recorded in the storage unit 16 (S424). At this time, the component data supply unit 12 calculates the usage fee of the component data from the imposed points recorded in the reward accumulation unit 16, and notifies the terminal device 20 of the instruction to pay the calculated usage fee.

  When the part data registration request including the part data and the condition data is received (part data registration request in S403), the part data collection unit 14 includes the part data and the condition data included in the received part data registration request. Are stored in the component data storage unit 11 (S431).

  The reward determination unit 15 refers to the result table shown in FIG. 6B, and reward points corresponding to the result of the part data before storage and reward points corresponding to the result of the part data after storage. Is determined as a reward point for registering the part data (S432). In this determination, for example, if there is component data that matches the component name but does not match the model name of the component mounter (ie, corresponds to another model of the component mounter) before storing the component data, Since the shape data common to the model of the component mounting machine has already been registered for the component, the result before storage is set to 1.

  When the part data is registered, the reward determination unit 15 already has other part data similar to the registered part data in the part data storage unit 11 (in other words, other similar part data exists. In particular, the performance of the similar part data is more advanced than the level before the registered part data is stored (including the stage where no part data exists). In some cases, a lower reward point may be determined as compared to the case where the similar part data does not exist.

  Here, the similar parts data specifically refers to the parts data of other parts with the same name and other parts with the same manufacturer, the parts data of parts of other manufacturers that can replace the part, and the parts data having the same shape type. , And component data having the same component name and different models of the corresponding component mounters.

  This is because, when similar part data already exists, the work for creating the part data to be registered is reduced by referring to the similar part data. Based on the idea that the actual reward value will decline.

  The reward determination unit 15 rewards the registration date and time, the supplier of the component data, the component name and the model name of the component mounting machine, the result data before and after registration, and the reward points returned to the provider. Recording is performed in the storage unit 16 (S433).

  When a complaint designating a component name that is a component data identification key and a model name of a component mounting machine is received (claimed in S403), the usage data recording unit 122 of the component data supply unit 12 stores the component data storage unit 11 In step S441, the number of complaints of the component data identified by the identification key is incremented.

  It is also conceivable that reward points may be returned after some usage data including the number of usages and the number of complaints is collected, not immediately after registration. In that case, as an example, if the number of uses exceeds a predetermined threshold, use one-step good performance data, and if the number of complaints exceeds a predetermined threshold, use one-step bad data. Good.

  Further, as a modification, for example, when the usage number exceeds a predetermined threshold by incrementing the usage number in step S422, a predetermined positive reward point is returned to the provider of the component data, When the number of complaints exceeds a predetermined threshold value by incrementing the number of complaints in S441, it is also conceivable to return a predetermined negative reward point to the component data provider.

  Further, the component data supply unit 12 may transmit the component data to the terminal device 20 free of charge in step S421. Then, by appealing that the component data is provided free of charge, it is possible to appeal the introduction merit to potential customers of the component mounter and promote the sales of the component mounter.

<Detailed operation of terminal device>
The operation of the terminal device 20 will be described in detail using a flowchart and a screen display example.

  FIG. 10 is a flowchart showing a detailed operation of the terminal device 20. In this flowchart, as an example of the case where the terminal device 20 is realized as a component mounter, main operations related to component data from production preparation to actual production success are shown.

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

  The component supply unit in the mounting mechanism unit 25 reads the component name automatically from the component storage reel or according to the operation of the operator (S103). The mounting control unit 21 searches the component data storage unit 23 for component data that is identified by the read component name and the model name of the component mounting machine itself and that is shown to have succeeded in actual production based on the result data. If there is no matching part data (NO in S104), the search condition specifying the part name is transmitted to the server device 10 (S105). The mounting control unit 21 displays the search result returned from the server device 10 on the operator I / F unit 22 (S106).

  FIG. 11 is a diagram illustrating an example of a search result display screen. The display at the top of the screen indicates that the part name related to the part data to be prepared is P1, the shape type of the part is T1, and the model name of the component mounter itself is M1. The component data that matches both the component name and the model name of the component mounting machine has only a result level of 2 (there is mounting data, no trial operation results), and the server device 10 expands the search range, resulting in the result level Is part data of 4 (with actual production results), and the part name matches but the model name of the component mounting machine does not match, and the shape type matches but the part name does not match appear in the search results. In the search result, an acquisition button for receiving an instruction to acquire the corresponding component data and a new creation button for receiving an instruction for newly creating the component data are displayed.

  When the acquisition button is touched (YES in S107), the mounting 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 notifies the terminal device 20 of an instruction for payment of the usage fee of the component data, and the terminal device 20 stores information for settlement of the usage fee instructed to pay. The usage fee is paid by transmitting to the apparatus 10. As described above, the usage fee of the component data is calculated by multiplying the levy point recorded when transmitting the component data by the server device 10 by a predetermined rate.

  Note that the server device 10 may instruct the payment of the usage fee for the component data not according to the supply of the component data, but in accordance with the total number of imposed points recorded in the cycle, for example, once a month. Good. At that time, when the same user provides part data, the usage fee may be calculated according to the amount of points obtained by offsetting the charge points with the reward points related to the provision.

  The component data input unit 26 supplements and corrects the acquired component data according to the input operation by the operator, supplements the component data stored in the component data storage unit 23, and updates it with the corrected component data (S109). ).

  On the other hand, when the new creation button is touched (NO in S107), the component data input unit 26 creates new component data in accordance with an input operation by the operator, and stores the newly created component data in the component data storage unit 23. (S110).

  FIG. 12 is a diagram illustrating an example of a shape data input screen. When a value is input to each item of the shape data displayed on such a screen by an operator's keyboard operation and the determination button is touched, new creation, supplement, or correction content of the shape data is stored in the component data storage unit 23. Reflected.

  FIG. 13 is a diagram illustrating an example of a mounting data input screen. When a value is input to each item of the mounting data displayed on such a screen by an operator's keyboard operation and the determination button is touched, new creation, supplement, or correction contents of the shape data are stored in the component data storage unit 23. Reflected.

  As an example, the recognition part image is generated from an image of a part photographed by the camera of the mounting mechanism unit 25, and the photographing is performed by touching the photographing button. Further, as another example, the recognition site image may be generated from an image of a component read by an external scanner device and captured by the terminal device 20.

  When the contents of new creation, supplement, or correction of part data are reflected in the part data storage unit 23 by touching the determination button, the result determination unit 27 inputs data to all items of the shape data. If there is shape data, and if the data is input to all the items of the mounting data, the result data indicating the mounting data is determined and recorded in the component data storage unit 23 (S111).

  The component data registration unit 28 displays on the operator I / F unit 22 notification content that prompts registration of the component data in the server device 10.

  FIG. 14 is a diagram illustrating an example of a part data registration promotion screen. The determined result data is displayed, and the currently accumulated reward points and the reward points obtained by registration are displayed to prompt the operator to register the part data.

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

  Now, when all necessary component data is prepared by the loop processing from step S102 to step S113, the mounting control unit 21 controls the mounting mechanism unit 25 to perform a trial run of mounting production (S201). At this time, the mounting control unit 21 records the number of mount trials and the number of successful mounts using the component data in the component data storage unit 23.

  For example, if the condition that the number of mount trials is 20 times or more and the mount success rate is less than 80% is satisfied, it is determined that the mount success rate is low (YES in S202), and the complaint sending unit 212 determines whether or not to send a complaint. Is displayed on the operator I / F unit 22. In general, such a claim is transmitted when the component data acquired in step S108 does not function well, but the component data created by itself in step S110 and registered in step S112 functions well. If not, it is of course possible to report the problem regarding the component data.

  FIG. 15 is a diagram illustrating an example of a complaint transmission confirmation screen. The number of mount attempts recorded, the number of successful mounts, the mount success rate, and the like are displayed, and a button for accepting whether to make a claim is displayed.

  When the button to be attached is touched, the complaint transmitter 212 transmits the complaint data regarding the component data to the server device 10 (S203). When the complaint data is transmitted or the button that is not attached is touched, the component data input unit 26 displays the input screen as shown in FIGS. 12 and 13 on the operator I / F unit 22 again, and the mounting data Accept the amendment details. After the rough adjustment of the component data is performed through such an input screen (S204), the test run is performed again.

  If it is determined that there is no component having a low mount success rate in the trial operation (NO in S202), the performance condition determination unit 27 re-determines that the performance of the component data is successful, and updates the component data storage unit 23 ( S205).

  The part data registration unit 28 again displays a part data registration promotion screen as shown in FIG. 14 on the operator I / F unit 22 as a result of successful trial operation. When the registration button is touched, the component data registration unit 28 registers the component data and the corresponding result data in the server device 10 (S206).

  Here, for the sake of simplicity, it has been described that all components achieve a good mount success rate, and then update the result and register the component data, but there are still components with a low mount success rate Even in such a case, it is of course possible to register the result of the component data as the trial run success sequentially from the component that has achieved a good mounting success rate.

  If the trial run is successful, the mounting control unit 21 controls the mounting mechanism unit 25 and starts actual production (S301). At this time, the mounting control unit 21 determines whether or not a predetermined amount of actual production has been successful by counting the number of successful production boards (S302). If it is determined that the production of the predetermined amount of board has not been successful (NO in S302), the transmission of the complaint according to the operator operation (S303) and the fine adjustment of the component data are performed in the same manner as described above (S304). ) Continue actual production.

  When it is determined that the actual production of the predetermined amount of substrates has been successful (YES in S302), the completion status determination unit 27 re-determines that the production status of the component data is successful, and stores the component data storage unit 23. Update (S305).

  The part data registration unit 28 again displays a part data registration promotion screen as shown in FIG. 14 on the operator I / F unit 22 as a result of successful production. When the registration button is touched, the component data registration unit 28 registers the component data and the corresponding result data in the server device 10 (S306).

  In this case as well, even if the board has not been successfully produced in a certain amount, it is a good part that has not hindered its success, that is, a component that is correctly mounted on a certain amount of board if only the parts are viewed. As described above, it is possible to sequentially register the result of the part data as the actual production success.

  In the above description, the terminal device 20 is described as being realized as a component mounter. However, the present invention is not limited to this, and the terminal device 20 is a computer that is separated from the component mounter and connected by a communication line. It doesn't matter. In this case, the component data acquired by the terminal device 20 is transmitted to the component mounter via the communication line and used for mounting the component, and information indicating the test operation and actual production status in the component mounter is the communication It may be transmitted to the terminal device 20 via a line.

  In the description so far, the server device 10 is a computer installed at a service base of a component mounter manufacturer, and the component mounter manufacturer communicates between customers, that is, the component mounter via the server device 10. Although an example in which a service for promoting the distribution of component data between users is used, the provider of such a service does not necessarily have to be a component mounter manufacturer.

  For example, in a manufacturer that has many factories and operates a large number of component mounting machines, the manufacturing support department may operate the server device 10 and develop such services throughout the company.

  In that case, for example, a main server may be provided in the manufacturing support department, and a middle server may be provided in each factory, which may be realized as a hierarchical distributed database. If each component mounter acquires component data from the middle server in the factory where the component mounter is installed, the component library data amount, communication traffic amount, and server device calculation processing amount are suitably set. Can be distributed. The hierarchical distributed database itself can be constructed using a well-known technique.

<Summary>
As described above, according to the parts data supply method and the parts data receiving method of the present invention, even if the part data that has not been used for good production and has the work necessary to succeed in actual production, Since it is distributed along with the work condition data representing the work, the component mounter user can look at the work condition data and determine whether the component data can be used immediately or how much adjustment with the actual machine is necessary. As a result, the distribution of the part data is activated, and the part data can be quickly started up to a level where good product production is possible. The provision of parts data is facilitated by rewards according to their performance and usage.

  As a result, various kinds of component data are collected by the server device and are subject to distribution, so that the opportunity for acquiring available component data for the component mounter increases. When acquiring the part data, the operator can select and acquire the part data in the required condition by confirming the condition of the part data to be acquired.

  As a result, adjustment work of parts data by trial and error and improvement work of parts data by analysis of defects are reduced, so that the production resources required in the prototype process up to the production of non-defective products are optimized. Here, the optimization of the production resource corresponds to, for example, reduction of the number of work man-hours, reduction of electric power, fuel, water, and reduction of prototype materials.

  Furthermore, the quality of a product manufactured in a non-defective product production process is improved by acquiring component data of a desired quality (that is, well-considered and having a high degree of completeness) from a server device and using it on a component mounter. . As a result, the power consumption of the product itself is reduced and the service life is extended, which contributes to social and energy savings and resource savings.

<Supplement>
As mentioned above, although the component data distribution system of this invention was demonstrated based on embodiment, this invention is not limited to this embodiment. Unless it deviates from the meaning of the present invention, those in which various modifications conceived by those skilled in the art have been made in the present embodiment are also included in the scope of the present invention.

  For example, in the embodiment, it is assumed that there is no restriction on the user to be disclosed about the registered (provided) part data. However, the present invention is not limited to this, and the provider may create the following restrictions on the disclosure destination user for the component data created and registered in the server device 10.

  That is, when each user joins the parts data distribution system, the user group to which the user belongs is recorded, and when the user searches for part data, the user belonging to a user group different from that user is recorded. The part name of the registered part data is excluded from the search result. It should be noted that the disclosure restriction of component data may be specified for each component name, or may be specified by a list of user groups permitted to be disclosed.

  As a specific configuration, for example, a user group table is provided in the server device 10, and a user name is stored in the user group table in advance. The user group table holds a user group name and a user name included in the user group in association with each other. Here, the user group corresponds to a group of companies having a relationship such as an affiliated company.

  The terminal device 20 receives an operation for designating the disclosure range of the component data created by itself for each component name from the component data creator. The creator of the part data specifies that, for example, a part that does not require much time for creation from the part shape specifies that the disclosure range is not limited. May be specified to be restricted.

  The terminal device 20 transmits information on the disclosure range designated by the creator to the server device 10 together with the component data. In the server device 10, information related to the disclosure range is recorded in the component data storage unit 11 together with the component data.

  When the search condition is given from the terminal device 20, the search unit 121 has a part name of the part name in which information indicating that the disclosure range is limited is recorded in a user group different from the user who issued the search condition. If it is registered by the user to which it belongs, it is excluded from the search results.

  Since the component data excluded from the search result is not displayed on the terminal device 20, it is not possible to request acquisition of the component data from the terminal device 20. As a result, a component data supply step for supplying component data only to a user within a range set by the component data provider is realized.

  The user group can be used not only for limiting the disclosure range of the component data described above, but also for determining the usage fee of the component data imposed when the component data is acquired.

  In the embodiment, it has been described that the usage fee is a point obtained by multiplying the levying point by a predetermined rate. For example, when the user group to which the user who acquired the component data and the provider of the component data belong is different, the rate may be set higher than when the user data is the same.

  According to this configuration, there is a higher possibility that a component data provider can obtain higher consideration from users belonging to different user groups instead of prohibiting disclosure of the component data to users belonging to different user groups.

  Note that the component data supply apparatus of the present invention can be realized as a computer system.

  In this case, the computer system that implements the component data supply apparatus of the present invention records a CPU and a program that defines a processing procedure for supplying component data used by the component mounter for mounting the component on the board. A ROM for storing work data, a RAM for storing work data, a large-capacity storage means, and a communication means for communicating with the component data providing device and the component data receiving device, and the CPU is recorded in the ROM. Under the control performed by executing the program using the RAM, the communication means is necessary to succeed in actual production using one or more part data and each part data. One or more performance data indicating the degree of work is received from the component data providing device, and the mass storage means is configured to receive the one or more received data. When the component data and one or more completion status data are accumulated, and the search condition is received from the component data receiving device by the communication means, the CPU stores the component data accumulated in the mass storage means. One or more parts data that matches the search condition received from the inside is searched, and a search result including a part name for specifying each searched part data and corresponding result data is obtained by the communication means. When the acquisition request specifying one or more part names included in the search result is received from the component data receiving apparatus by the communication means, the CPU stores the mass data storage device. The component data specified by the received component name is acquired from the component data stored in the unit, and the acquired component data is acquired by the communication unit. It may be transmitted to the data receiving device.

  According to this configuration, the component data supply device can be realized as a computer system that operates under the control of predetermined software.

  Also, the component data receiving apparatus of the present invention can be realized as a computer system.

  In that case, the computer system for realizing the component data supply apparatus of the present invention defines a processing procedure for receiving from the component data supply apparatus the component data used by the component mounter for mounting the component on the board. A ROM that stores the program, a RAM that holds work data, a large-capacity storage means, a communication means for communicating with the component data supply device, and an operator I / F means, Under the control performed by the CPU executing the program recorded in the ROM using the RAM, the communication means transmits the search condition to the component data supply device, thereby the component. A part name that identifies one or more part data that matches the search condition returned from the data supply device, and each part data And the operator I / F means presents the received search result to the operator and is presented to the operator. The search result including the result data indicating the degree of work necessary for the actual production to be successful. An operation for selecting one or more component data from the retrieved results is received from the operator, and the communication means transmits an acquisition request designating the selected component name to the component data supply device, The component data specified by the selected component name may be acquired.

  According to this configuration, the component data receiving apparatus can be realized as a computer system that operates under the control of predetermined software.

  The component data supply method of the present invention can be used for a server device placed at a service base of a component mounter or a factory where the component mounter is installed, and the component data receiving method can be used for the component mounter itself.

The block diagram which shows the outline | summary of the components data distribution system in embodiment of this invention The block diagram which shows an example of a functional structure of a server apparatus and a terminal device Top view showing an example of parts (A), (B) is a figure which shows an example of the component data stored in the component data storage part 11 and the component data storage part 23 The figure which shows an example of a recognition part image (A) and (B) are diagrams for explaining the result data. (A) is a diagram showing an example of a component having a relatively high difficulty in creating component data, and (B) is a diagram showing an example of a recognition site image of the component. The figure which shows an example of the reward table 160 The flowchart which shows the detailed operation | movement of the server apparatus 10. The flowchart which shows the detailed operation | movement of the terminal device 20. The figure which shows an example of the display screen of a search result Figure showing an example of the shape data input screen Diagram showing an example of the input screen for mounting data The figure which shows an example of the registration promotion screen of parts data The figure which shows an example of the transmission confirmation screen of a claim

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Parts data distribution system 10 Server apparatus 11 Parts data storage part 12 Parts data supply part 13 Communication I / F part 14 Parts data collection part 15 Award determination part 16 Award accumulation part 20 Terminal device 21 Mounting control part 22 Operator I / F part 23 Component Data Storage Unit 24 Communication I / F Unit 25 Mounting Mechanism Unit 26 Component Data Input Unit 27 Degree of Determining Unit 28 Component Data Registration Unit 30 Network 110 Common Part 111 Model Dependent Part 121 Search Unit 122 Usage Data Recording Unit 150 Work Required Reject table 151 Completion table 160 Reward table 211 Parts data acquisition unit 212 Claim transmission unit

Claims (8)

  In the component data receiving device, a component data receiving method for receiving from the component data supply device the component data used in the component mounter for mounting the component on the board,
  The component data receiving device transmits a search condition to the component data supply device, whereby a part name that identifies one or more component data that matches the search condition and each part data is used for actual production. A part data search step for obtaining a search result including the result data representing the degree of work necessary to succeed from the part data supply device, and presenting the obtained search result to the operator;
  A component data selection step in which the component data receiving device receives an operation of selecting one or more component names from the displayed search results from the operator;
  The component data receiving device acquires the component data specified by the selected component name from the component data supply device by transmitting an acquisition request designating the selected component name to the component data supply device. Parts data acquisition step
  Including
  By distributing the component data that has not yet been produced in good quality and has the necessary work to succeed in the actual production together with the result data, the user of the component mounter can change the component data from the result data. Make it possible to determine the necessity of utilization
A part data receiving method characterized by the above. further,
A reward determination step in which the component data supply device determines a reward for each component data according to the corresponding performance data;
The component data receiving method according to claim 1, further comprising: a reward storage step in which the component data supply device stores the determined reward in association with a corresponding component data provider. The component data receiving device is realized as a component mounter,
further,
The component data supply apparatus includes a component data supply step of supplying the component data to the component mounter in response to an acquisition request sent from the component mounter during component verification. Item data receiving method according to Item 1. The component data receiving device is realized as a component mounter,
further,
2. The component data receiving method according to claim 1, wherein the component data supply device includes a component data supply step of supplying the component data to the component mounter free of charge. further,
The component data supply device, the component data to which the collected when you supplied to the component data receiving device, notifies the payment instruction royalties based on doneness data of the component data to be supplied to the component data receiving device The component data receiving method according to claim 1, further comprising a usage fee payment instruction step. A component data receiving device for receiving component data used by a component mounter for mounting a component on a board from a component data supply device,
By sending the search conditions to the parts data supply device, the part name that identifies one or more parts data that matches the search conditions and the work required to make the actual production successful using each part data. Parts data search means for obtaining a search result including the result data indicating the degree, and presenting the obtained search result to the operator;
Component data selection means for accepting an operation for selecting one or more component data from the displayed search results from the operator;
Part data acquisition means for acquiring part data specified by the selected part name by transmitting an acquisition request designating the selected part name to a part data supply device ;
By distributing the component data that has not yet been produced in good quality and has the necessary work to succeed in the actual production together with the result data, the user of the component mounter can change the component data from the result data. A component data receiving device characterized in that it is possible to determine whether or not it is necessary to utilize the component data. A component mounter that receives component data for mounting a component on a board from a component data supply device,
By sending the search conditions to the parts data supply device, the part name that identifies one or more parts data that matches the search conditions and the work required to make the actual production successful using each part data. Parts data search means for obtaining a search result including the result data indicating the degree, and presenting the obtained search result to the operator;
Component data selection means for accepting an operation for selecting one or more component names from the displayed search results from the operator;
Part data acquisition means for acquiring part data specified by the selected part name by transmitting an acquisition request designating the selected part name to a part data supply device ;
By distributing the component data that has not yet been produced in good quality and has the necessary work to succeed in the actual production together with the result data, the user of the component mounter can change the component data from the result data. A component mounter that makes it possible to determine the necessity of utilization . The program which makes a computer perform the step contained in the component data receiving method of Claim 1.

Images