How to update software

Abstract

To perform software updates on production lines more efficiently. [Solution] The software update method selects one pilot line from among multiple production lines having multiple production equipment on which the software is installed, and performs a first update process to update the software. Based on the operation log and system log of the pilot line, it performs an evaluation of the operation status of the pilot line. If it is determined that the result of the evaluation of the operation status satisfies the deployment conditions for deploying the software update to other production lines, it performs a second update process to update the software of the production equipment on the other production lines.

Description

Technical Field

[0001] This disclosure relates to a software update method.

Background Art

[0002] Patent Document 1 discloses a software update method for updating the software executed by a plurality of substrate processing machines constituting a production line of substrate products to different versions. The software update method stores a version application plan indicating the version of software to be applied to each production process that a substrate processing machine capable of being installed in advance is scheduled to execute, and when a substrate processing machine is executing one version of a plurality of versions of software, updates the software of other versions, and designates the version of software to be applied to the production process by selecting one of the plurality of versions of software installed in the substrate processing machine based on the version application plan.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In view of the above-described conventional circumstances, this disclosure is devised, and an object thereof is to provide a software update method for more efficiently executing the update of the software of a production line.

Means for Solving the Problems

[0005] This disclosure provides a software update method for updating the software of a plurality of production lines having a plurality of production equipment performed by a processor, wherein the production equipment has the updateable software installed, and the method includes selecting one pilot line from the plurality of production lines to update the software, executing a first update process to update the software of the selected pilot line, evaluating the operating status of the pilot line based on the operation log and system log of the pilot line on which the first update process was executed, and if it is determined that the result of the evaluation of the operating status satisfies the deployment conditions for deploying the software update to the other production lines, executing a second update process to update the software of the production equipment in the other production lines. [Effects of the Invention]

[0006] According to this disclosure, software updates for production lines can be performed more efficiently. [Brief explanation of the drawing]

[0007] [Figure 1] Figure showing example use case 1 of the component mounting system according to the embodiment. [Figure 2] Diagram showing an example of the internal configuration of the management computer according to the embodiment. [Figure 3] Figure showing example use case 2 of the component mounting system according to the embodiment. [Figure 4] A flowchart showing an example of the update procedure for the management computer according to the embodiment. [Modes for carrying out the invention]

[0008] (Background leading to this disclosure) Generally, in production lines that include multiple production facilities, the software versions and settings of one or more production facilities must be standardized across the entire production line to avoid variations in quality and production problems. Each production facility uses various software to realize product production (manufacturing).

[0009] Therefore, when updating the software for each piece of equipment on a production line, the production line manager would run one of the production lines for a certain period using the updated software to check for any production problems, and if there were no problems, deploy the updated software to the other production lines. However, this method of updating software had the problem of increasing the manager's workload, as it required planning for the software update, checking for any production problems caused by the software update, and deciding whether to deploy it to other production lines. Consequently, managers sometimes postponed software updates from the perspective of the workload, which resulted in other problems such as difficulty in implementing measures to improve quality.

[0010] Patent Document 1 discloses a conventional method for updating software. However, Patent Document 1 does not consider whether or not there will be production problems due to the software update. Therefore, if production problems arise due to the software update, there is a possibility that the entire production line may be shut down or the productivity of the production line may decrease.

[0011] The following describes in detail each embodiment that specifically discloses the software update method according to this disclosure, with reference to the drawings as appropriate. However, unnecessary details may be omitted. For example, detailed explanations of already well-known matters or redundant explanations of substantially identical configurations may be omitted. This is to avoid the following explanation becoming unnecessarily verbose and to facilitate understanding by those skilled in the art. The accompanying drawings and the following explanation are provided to enable those skilled in the art to fully understand this disclosure and are not intended to limit the subject matter described in the claims.

[0012] This disclosure describes a method for updating the software of each piece of production equipment included in a production line that produces circuit boards on which electronic components are mounted. However, the production line can be any line that includes multiple pieces of production equipment. Furthermore, for the sake of clarity, this disclosure describes an example in which multiple production lines each have the same number of similar pieces of production equipment. However, the number of each piece of production equipment in each production line is arbitrary and not limited to this.

[0013] <Example Use Case 1> Figure 1 shows an example of use case 1 of the component mounting system 100 according to the embodiment. The component mounting system 100 according to the embodiment is a system that performs, for example, different production processes: a solder printing process for printing solder on a substrate B; a printing inspection process for inspecting printing defects of the solder printed on the substrate B; a component mounting process for mounting components D on the substrate B after solder printing; a mounting inspection process for inspecting the components D mounted on the substrate B; and a reflow process for reflowing the solder printed on the substrate B.

[0014] In Use Case Example 1, the component mounting system 100 is managed by one control computer for one production line. The component mounting system 100 includes multiple control computers P1, P2, ..., multiple production lines L11, L12, ..., and a communication network LN. In Figure 1, as an example, two control computers P1 and P2 are shown, and two production lines L11 and L12 are connected to each control computer in a way that allows communication between them. However, the number of control computers and production lines may be three or more.

[0015] Each of the management computers P1, ... is implemented as, for example, a Personal Computer (hereinafter referred to as "PC"), a notebook PC, or a tablet device. Each of the management computers P1, ... is connected to other management computers and each of the production equipment included in the production line L11 via a communication network LN.

[0016] Each of the management computers P1,... controls each production process (e.g., soldering process, printing inspection process, or component mounting process, etc.) performed by each component mounting device M1, M2, M3, M4, M5, M6, M7, M8 that constitutes each of the corresponding production lines L11,.... Furthermore, the component mounting system 100 has a system in which any one of the multiple management computers connected to each other in a communicative manner performs software update management for each of the multiple component mounting devices M1 to M8 included in each production line L11,.... The management computer that performs software update management may be selected by the operator.

[0017] The communication network LN connects each of the management computers P1, ... to each of the multiple production lines L11, ... enabling data communication. In the example in Figure 1, the communication network LN is shown as being connected via wired communication, but it may also be wireless. Wireless communication here refers to a communication method provided in accordance with wireless communication standards such as wireless Local Area Network (LAN), Bluetooth®, or Wi-Fi®.

[0018] Next, with reference to Figure 2, an example of the internal configuration of the management computers P1, ..., P1A will be described. Figure 2 is a diagram showing an example of the internal configuration of the management computers P1, ..., P1A according to the embodiment. Note that the explanation of the internal configuration example of management computer P1A will be described later as it corresponds to Use Case Example 2. Also, the management computers P1, P2, ... in Use Case Example 1 each have similar configurations and functions. Therefore, in this disclosure, only the internal configuration example of management computer P1 will be described, and the explanation of the internal configuration examples of the other management computers P2, ... will be omitted.

[0019] The management computer P1 includes a communication unit 10, a processor 11, memory 12, a monitor 13, and an input unit 14. Note that the monitor 13 and the input unit 14 may be configured separately from the management computer P1.

[0020] The communication unit 10 is communicably connected to each of the component mounting devices M1 to M8 included in the corresponding production line L11 and the management computers P2, …. The communication unit 10 outputs various data (various information) transmitted from each of the component mounting devices M1 to M8 to the processor 11. Further, the communication unit 10 transmits various data (various information) output from the processor 11 or data related to various software to the corresponding component mounting devices M1 to M8. When the management computer P1 needs to communicate with the component mounting devices M1 to M8 included in other production lines L12, …, it is realized by executing data transmission and reception with the corresponding management computers P2, ….

[0021] The processor 11 is configured using, for example, a Central Processing Unit (hereinafter referred to as “CPU”) or a Field Programmable Gate Array (hereinafter referred to as “FPGA”), and performs various processes and controls in cooperation with the memory 12. Specifically, the processor 11 refers to the programs and data held in the memory 12 and executes the programs to realize the functions of each part. The processor 11 executes, by means of these parts, the production of the substrate B (product) by the production lines L11, … and the management of the software used in the component mounting devices M1 to M8 of the production lines L11, ….

[0022] Memory 12 includes, for example, Random Access Memory (hereinafter referred to as "RAM"), which serves as work memory used when executing each process of the processor 11, and Read Only Memory (hereinafter referred to as "ROM"), which stores programs and data that define the operation of the processor 11. Data or information generated or acquired by the processor 11 is temporarily stored in RAM. Programs that define the operation of the processor 11 are written to ROM. Memory 12 stores production data for circuit boards B produced by production lines L11,... and information related to the software used by component mounting devices M1 to M8 of production lines L11,....

[0023] The monitor 13 is configured using, for example, a Liquid Crystal Display (LCD) or an Organic Electroluminescence (EL). The monitor 13 outputs and displays various screens generated by the processor 11. These various screens include screens related to the production of substrate B by production lines L11,... (for example, screens showing the production results or progress observation results of substrate B), and screens related to the management of the software for each component mounting device M1 to M8 (for example, screens showing the software version list described later).

[0024] The input unit 14 is a user interface that accepts input operations from an operator, and is configured using, for example, a mouse, keyboard, touch panel, touchpad, or pointing device. The input unit 14 outputs signals corresponding to the operator's input operations to the processor 11.

[0025] The monitor 13 may be implemented by an external monitor connected to the management computer P1 in a manner that enables data communication. In such a case, the management computer P1 may have an input unit 14, such as a mouse or keyboard, further connected in a manner that enables communication, which can accept user input operations. The monitor 13 and the input unit 14 may also be configured as an integrated unit, such as a touch panel.

[0026] <Example Use Case 2> Next, with reference to Figures 2 and 3, a use case example 2 of the component mounting system 100A and the management computer P1A will be described. Figure 3 is a diagram showing a use case example 2 of the component mounting system 100A according to the embodiment. Note that the production lines L21 to L23 shown in Figure 3 have the same configuration as the production lines L11, ... shown in Figure 1, so in Figure 3, the assignment of reference numerals to the component mounting devices included in each production line has been omitted.

[0027] In Use Case Example 2, the component mounting system 100A manages multiple production lines with a single management computer. The component mounting system 100A includes a management computer P1A, at least one production line L21-L23, and a communication network LN. Figure 3 shows, as an example, a configuration where one management computer P1 and three production lines L21-L23 are installed on floor F, and the management computer P1 and the three production lines L21-L23 are connected in a communication manner, but is not limited to this configuration. Furthermore, the number of production lines connected to each management computer can be multiple.

[0028] The management computer P1A is implemented using, for example, a PC, a notebook PC, or a tablet device. The management computer P1A is communicated via the communication network LN to each of the production equipment included in the multiple production lines L21 to L23.

[0029] The management computer P1A implements and controls the production process, including each production step (e.g., soldering process, print inspection process, or component mounting process) performed by each component mounting device that constitutes each of the multiple production lines L21 to L23. The management computer P1A also manages the updates of the software used by each of the multiple component mounting devices included in each of the multiple production lines L21 to L23.

[0030] The communication network LNA connects the management computer P1A to multiple production lines L21-L23, enabling data communication. While Figure 3 shows an example where the communication network LNA is connected via wired communication, it may also be connected via wireless communication.

[0031] The management computer P1A includes a communication unit 10A, a processor 11A, memory 12A, a monitor 13, and an input unit 14. Note that the monitor 13 and input unit 14 have the same functions as the management computer P1 shown in Use Case Example 1, so their description is omitted.

[0032] The communication unit 10A is connected to each component mounting device M1 to M8 included in each of the multiple production lines L21 to L23, enabling communication between them. The communication unit 10A outputs various data (various information) transmitted from each component mounting device M1 to M8 to the processor 11A. The communication unit 10A also transmits various data (various information) or data related to various software, etc., output from the processor 11A to the corresponding component mounting devices M1 to M8.

[0033] The processor 11A is configured, for example, using a CPU or FPGA, and works in cooperation with the memory 12A to perform various processing and control operations. Specifically, the processor 11A refers to the programs and data held in the memory 12A and executes those programs to realize the functions of each part. Through these parts, the processor 11A performs tasks such as the production of board B by multiple production lines L21 to L23, and the management of the software for each component mounting device M1 to M8 on the multiple production lines L21 to L23.

[0034] Memory 12A includes, for example, RAM as work memory used when executing each process of processor 11A, and ROM which stores programs and data that define the operation of processor 11A. Data or information generated or acquired by processor 11A is temporarily stored in RAM. Programs that define the operation of processor 11A are written in ROM. Memory 12A stores production data for board B produced by multiple production lines L21 to L23, and information related to the software used by each of the component mounting devices M1 to M8 of the multiple production lines L21 to L23.

[0035] Next, with reference to Figure 4, we will describe examples of software update procedures in use cases 1 and 2. Figure 4 is a flowchart showing examples of update procedures for management computers P1 and P1A according to the embodiment.

[0036] In the following explanation, as an example of an update procedure in Use Case Example 1, we will describe an example in which, among the multiple management computers P1, ... included in the component mounting system 100, management computer P1 functions as a so-called master device and performs software updates for the multiple production lines L11, L12, ... included in the component mounting system 100.

[0037] The processors 11 and 11A of the management computers P1 and P1A acquire the current version information of the software of each component mounting device M1 to M8 included in the production line, which is connected via communication. The current version information of the software of each component mounting device M1 to M8 may be recorded in the memories 12 and 12A, or the latest version information may be collected from each component mounting device M1 to M8. The processors 11 and 11A generate a screen (not shown) containing a version list listing the current version information of the software of each component mounting device M1 to M8, output it to the monitor 13, and display it (St11).

[0038] Processors 11 and 11A accept an operation via the input unit 14 to specify one software to be updated from the software included in the version list, and the updated version of this software (St12).

[0039] In Use Case Example 1, the processor 11 selects one of the multiple production lines L11,… included in the component mounting system 100 as a pilot line based on the production plans of those production lines L11,… (St13). The pilot line is the production line where the software version update is first performed and an examination is conducted to determine whether the updated software can be deployed to all production lines.

[0040] Furthermore, in Use Case Example 2, the processor 11A selects one of the multiple production lines L21 to L23 as a pilot line based on the production plan (St13). The pilot line may be selected (specified) in advance by an operator.

[0041] Specifically, the processor 11A acquires production data for each of the circuit boards B scheduled to be produced on each production line L21 to L23. Based on the production volume (number of boards produced) of circuit boards B indicated by the acquired production data, the processor 11A selects one of the production lines where a certain range of production volume is planned as a pilot line. This allows the processor 11A to suppress delays in the production plan due to excessive production volume or prevent problems from occurring due to insufficient production volume if any problems arise in production due to a version update. Note that the certain range of production volume mentioned here may be set by the operator.

[0042] Furthermore, processors 11 and 11A may select production lines with an operating time of a certain duration or longer, and then select the production line with the shortest operating time among the selected production lines as the pilot line. Similarly, processors 11 and 11A may select production lines with a production volume of a certain amount or more, and then select the production line with the lowest production volume among the selected production lines as the pilot line.

[0043] Processors 11 and 11A update the software version of the selected pilot lines (production lines) that are subject to updating (St13).

[0044] Processors 11 and 11A determine whether or not operational problems occur in the pilot line after a software version update, based on the following two determination processes.

[0045] <First judgment process> As its first determination process, processors 11 and 11A determine whether a certain period or a certain amount of production has been completed, that is, whether the observation period has been completed. If processors 11 and 11A determine that a certain period or a certain amount of production has been completed, they determine whether there are any problems caused by the software version update, based on the operation logs of the pilot line, the system logs of the software, etc., collected during the period or the period of production.

[0046] Specifically, after updating the version, processors 11 and 11A initiate production on the pilot line. Processors 11 and 11A operate the pilot line for a certain period or until a certain quantity of production is completed, collecting operation logs from each of the operating component mounting devices M1 to M8, and monitoring the progress of production (St14). Note that the certain period or quantity here may be set by the operator.

[0047] During the monitoring period, processors 11 and 11A display the collected operation logs or system logs on monitor 13 for visualization to the operator. Processors 11 and 11A also analyze the operation logs or system logs collected over a certain period or until a certain amount of production is completed, and display them on monitor 13 for visualization to the operator. Processors 11 and 11A determine whether a problem has occurred in the production status during the period or until a certain amount of production is completed (i.e., during the monitoring period) (St15).

[0048] Specifically, processors 11 and 11A determine whether or not there is a problem with the operation of the pilot line based on the analysis results of the operation log and system log, respectively. Alternatively, the determination of whether or not a problem has occurred may be made by an operator based on the operation log or analysis results displayed on monitor 13. In such cases, processors 11 and 11A accept operation from the operator via input unit 14.

[0049] If, in step St15, processors 11 and 11A determine that a problem has occurred in the production status during a certain period or until a certain amount of production is completed (i.e., during observation) (St15, YES), they output a notification to monitor 13 indicating that a problem has occurred and perform a software version rollback (St16).

[0050] On the other hand, if processors 11 and 11A determine in step St15 that no problems have occurred in the production status during a certain period or until a certain amount of production is completed (i.e., during observation) (St15, NO), they proceed to the second determination process.

[0051] <Second judgment process> In the second determination process, processors 11 and 11A determine whether the updated version can be deployed to other production lines based on the operation log of the pilot line and the operation logs of other production lines using the software before the version update. Furthermore, processors 11 and 11A determine whether the updated version can be deployed to other production lines based on the system log of the pilot line.

[0052] Specifically, processors 11 and 11A compare the operation logs of the pilot line with the operation logs of other production lines (St17).

[0053] For example, in Use Case Example 1, processor 11 may compare the operation logs of the pilot line (e.g., production line L11) before and after the software version update. Alternatively, processor 11 may obtain operation logs of other production lines (e.g., production line L12) from another management computer (e.g., management computer P2) that is connected to management computer P1 and is using the software version prior to the update, and compare these logs with the operation logs of the pilot line.

[0054] Furthermore, for example, in Use Case Example 2, processor 11A acquires operation logs from other production lines (e.g., production line L22) and compares the operation logs of the pilot line (production line L21) with those of the other production lines (e.g., production line L22). Note that the number of production lines whose operation logs are compared is not limited to one, but may be multiple.

[0055] Processors 11 and 11A determine whether it is possible to deploy the updated version of the software to other production lines based on a comparison of the operation log or system log of the pilot line with the operation logs of other production lines, and the system log of the pilot line (St18).

[0056] Processors 11 and 11A determine whether the updated version of the software can be deployed based on the system log of the pilot line. For example, processors 11 and 11A aggregate the occurrence of errors based on the system log of the pilot line. If processors 11 and 11A aggregate the occurrence of errors, they determine whether the aggregated errors are the same as errors that occurred in the past on other lines before the version update. If processors 11 and 11A determine that the aggregated errors are not the same as errors that occurred in the past on other lines before the version update, they determine that a problem has occurred that prevents the version from being deployed.

[0057] Furthermore, processors 11 and 11A determine whether or not the updated version of the software can be deployed based on the results of analyzing at least one Key Performance Indicator (hereinafter referred to as "KPI") based on the operation log of the pilot line. For example, processors 11 and 11A evaluate changes in the KPI based on the operation log of the pilot line and the operation logs of the production line or other production lines before the version update. Each of the three KPIs in this disclosure is an indicator set to evaluate the performance of the pilot line, and is, for example, the rate of mechanical errors (error rate) of each component mounting device M1 to M8 on the pilot line, the number of times the pilot line was temporarily stopped, and the accuracy (first-pass rate) of Automated Optical Inspection (AOI) in the inspection process of the pilot line. If, based on the evaluation results of the KPI, processors 11 and 11A determine that the KPI of the pilot line has changed in a deteriorating direction and that the amount of change is an unacceptable amount, then it determines that a problem has occurred that prevents the deployment of the version. The unacceptable amount of change may be set by an arbitrary value by the operator.

[0058] The KPIs used for determining version deployment are not limited to the examples described above. One or more arbitrary KPIs may be set for determining version deployment based on the product produced by the production line (in this disclosure, substrate B), the production equipment included in the production line (in this disclosure, component mounting equipment M1 to M8), or the method for producing the product.

[0059] Furthermore, processors 11 and 11A compare the cycle times of identical products (in this disclosure, board B) produced by the pilot line before and after the version upgrade, based on the operation logs of the pilot line before and after the version upgrade. If, based on the comparison of cycle times, processors 11 and 11A determine that the cycle time has worsened and that this change is an unacceptable amount, they determine that a problem has occurred that prevents the version from being deployed. Note that the cycle time referred to here may be the time required to produce one or more products (boards), or it may be the average cycle time per board. Also, the unacceptable amount of change may be set to an arbitrary value by the operator.

[0060] Furthermore, after updating the software version, processors 11 and 11A acquire a request for production data for board B, the target of production, from the pilot line. Based on the acquired request, processors 11 and 11A transmit the production data used for the production of board B to each component mounting device M1 to M8 on the pilot line. Here, processors 11 and 11A measure and record the system response time from the time the production data request is acquired until the time the pilot line completes downloading the production data. If processors 11 and 11A determine that the measured system response time is longer than a predetermined time, they determine that a problem has occurred that prevents version deployment. Also, based on a comparison of the measured system response time with a previously measured system response time, if processors 11 and 11A determine that the system response time has worsened and that this change is an unacceptable amount, they determine that a problem has occurred that prevents version deployment. Note that the unacceptable amount of change may be set by the operator at any value.

[0061] If, based on the second determination process, processors 11 and 11A determine that it is possible to deploy the updated version of the software to other production lines (St18, YES), they automatically deploy the updated version of the software to other production lines (St19). Processors 11 and 11A may also generate a notification indicating that it is possible to deploy the updated version of the software to other production lines and display it on monitor 13.

[0062] Here, if a production plan is stored in memory 12,12A, processors 11,11A select the timing for deploying the updated version based on the production plan. For example, based on information such as the scheduled production time or production completion date indicated in the production plan, processors 11,11A select a time period (for example, a time when no production is taking place) during which production is not under pressure, during which the impact on the production plan itself is deemed to be small, even if a production stoppage occurs due to the software version update, as the timing for deploying the updated version. Note that the date and time on which the software version update process is performed may be set by the operator.

[0063] On the other hand, if processors 11 and 11A determine, based on the second determination process, that it is not possible to deploy the updated version of the software to other production lines (St18, NO), they output a notification to monitor 13 indicating that a problem has occurred in which the updated version cannot be deployed, and perform a rollback of the software version on the pilot line (St16).

[0064] Furthermore, if processors 11 and 11A determine in step St18 that the production line is not running and the second determination process cannot be completed, they extend the observation time. This allows processors 11 and 11A to accurately determine whether or not the software version can be deployed.

[0065] As described above, the management computers P1 and P1A in this embodiment support the management tasks performed by workers in conjunction with software version updates, thereby further suppressing the increase in management workload for workers. Furthermore, the management computers P1 and P1A can perform software version updates at a more appropriate timing based on the operating status or schedule of the production line indicated by the production plan. This allows the management computers P1 and P1A to more effectively suppress production line stoppages and decreases in production efficiency caused by software version update processes.

[0066] Furthermore, as in Use Case Example 2, when a single management computer P1A manages multiple production lines L21 to L23, the management computer P1A can select the production line that is more suitable for the pilot line based on the production plan.

[0067] (Note) Based on the descriptions of the embodiments described above, the following technologies are disclosed.

[0068] (Technology 1) A method for updating the software of multiple production lines having multiple production equipment (component mounting devices M1 to M8) performed by processors 11 and 11A, The aforementioned production equipment (component mounting devices M1 to M8) has the aforementioned updatable software installed. Select one pilot line from the aforementioned multiple production lines to update the software, A first update process is performed to update the software of the selected pilot line. Based on the operation log and system log of the pilot line on which the first update process was performed, an evaluation of the operating status of the pilot line (i.e., the first or second determination process) is performed. If the results of the operational status evaluation determine that the deployment conditions for deploying the software update to other production lines are met (i.e., the updated version of the software can be deployed to other production lines), then a second update process is executed to update the software of the production equipment (component mounting devices M1 to M8) in the other production lines. How to update the software. As a result, processors 11 and 11A support the management tasks performed by workers in conjunction with software version upgrades, and by further suppressing the increase in management workload for workers, production line software updates can be performed more efficiently.

[0069] (Technology 2) Based on the production plan of the aforementioned production line, the pilot line is selected. The software update method described in (Technical 1). This allows processors 11 and 11A to perform software version updates at a more appropriate time based on the operating status or schedule of the production line as indicated in the production plan.

[0070] (Technology 3) Based on the production plan of the aforementioned production line, the production line with the shortest operating time of the aforementioned production equipment (component mounting devices M1 to M8) among the production lines where the operating time of the aforementioned production equipment (component mounting devices M1 to M8) is above a certain period of time is selected as the pilot line. The software update method described in (Technology 1) or (Technology 2). As a result, processors 11 and 11A can select a production line as a pilot line that allows for a thorough evaluation of the production line's operation after a software version update, based on the production line's operating time indicated in the production plan, and where the time required for evaluating the production line's operation does not become excessively long. Therefore, processors 11 and 11A can more efficiently manage the time required to consider whether or not to update the software version of a production line.

[0071] (Technology 4) Based on the production plan of the aforementioned production line, the production line with the lowest production volume among the production lines that produce a certain amount of goods or more is selected as the pilot line. The software update method described in any one of (Technology 1) to (Technology 3). As a result, processors 11 and 11A can select a production line as a pilot line that allows for a thorough evaluation of the production line's operation after a software version update, based on the production volume indicated by the production plan, and where the time required for evaluating the production line's operation is not excessively long. Therefore, processors 11 and 11A can more efficiently manage the time required to consider whether or not to update the software version of a production line.

[0072] (Technology 5) The evaluation of the operating status is performed based on a comparison of the operation log and system log of the pilot line before the software update with the operation log and system log after the software update. The software update method described in any one of (Technology 1) to (Technology 4). As a result, processors 11 and 11A can automatically detect whether there are any operational problems with each component mounting device M1 to M8 due to software version updates, based on a comparison of system logs or operation logs collected on the same production line (pilot line), thereby supporting the work of operators regarding version updates.

[0073] (Technology 6) The evaluation of the operating status is performed based on a comparison of the operation log and system log of the pilot line with the operation log and system log of at least one other production line. The software update method described in any one of (Technology 1) to (Technology 5). As a result, processors 11 and 11A can automatically detect whether there are any operational problems with each component mounting device M1 to M8 due to software version updates, based on a comparison of system logs or operation logs collected from production lines and pilot lines using the same software, thereby supporting operators in their work related to version updates.

[0074] (Technology 7) The deployment conditions are that the production status of the pilot line after the software update is not deteriorating, or the degree of deterioration (amount of change) is less than a predetermined value. Based on the evaluation of the operating status, it is determined whether or not the deployment conditions are met. The software update method described in (Technical 5) or (Technical 6). As a result, processors 11 and 11A can perform a decision on deploying the updated software based not only on the difference between the system log or operation log before and after the software update, but also on whether this difference indicates a deterioration trend in the production equipment and the amount of change in that deterioration trend.

[0075] (Technology 8) The aforementioned production line has at least production equipment (component mounting devices M1 to M8) that performs AOI processing, The evaluation of the operating status is performed based on at least one of the following: the presence or absence of system errors in the software, the rate of processing errors in the production equipment (component mounting devices M1-M8), the number of times the production equipment (component mounting devices M1-M8) has stopped, the first-pass rate of the AOI of the production line, the production cycle time of the products produced on the production line, and the system response time of the production equipment (component mounting devices M1-M8). The software update method described in any one of (Technology 1) to (Technology 7). This allows processors 11 and 11A to perform a deployment decision for the updated software based on the performance required by the production line.

[0076] (Technology 9) If the results of the operational status evaluation determine that the deployment conditions are met, the timing of the second update process is determined for each of the other production lines based on the respective production plans of the other production lines. Based on the determined timing, the second update process of the other production line is executed. The software update method described in any one of (Technology 1) to (Technology 8). As a result, processors 11 and 11A can, based on the production plan, select a time period (for example, a time when no production is taking place) that is deemed to have little impact on the production plan itself, even if a production stoppage occurs due to a software version update, based on information such as the scheduled production time or production completion deadline indicated in the production plan. This allows for more efficient software updates on the production line.

[0077] Although various embodiments have been described above with reference to the attached drawings, this disclosure is not limited to such examples. It will be clear to those skilled in the art that various modifications, alterations, substitutions, additions, deletions, and equivalents can be conceived within the scope of the claims, and these will also be understood to fall within the technical scope of this disclosure. Furthermore, the components of the various embodiments described above can be combined arbitrarily without departing from the spirit of the invention. [Industrial applicability]

[0078] This disclosure is useful as a software update method for more efficiently performing software updates on production lines. [Explanation of Symbols]

[0079] 10,10A Communications Department 11,11A processor 12,12A memory 13 monitors 14 Input section 100, 100A component mounting system B substrate F Floor L11, L12, L21, L22, L23 Production Line LN, LNA communication network M1,M2,M3,M4,M5,M6,M7,M8 Component mounting equipment P1, P1A, P2 Management Computers

Claims

1. A method for updating the software of multiple production lines having multiple production facilities, performed by a processor, The aforementioned production equipment has the aforementioned updatable software installed, Select one pilot line from the aforementioned multiple production lines to update the software, A first update process is performed to update the software of the selected pilot line. Based on the operation log and system log of the pilot line on which the first update process was performed, an evaluation of the operating status of the pilot line is performed. If the results of the operational status evaluation determine that the conditions for deploying the software update to other production lines are met, a second update process is executed to update the software of the production equipment in the other production lines. How to update the software.

2. Based on the production plan of the aforementioned production line, the pilot line is selected. The software update method according to claim 1.

3. Based on the production plan of the aforementioned production line, the production line with the shortest operating time of the production equipment among the production lines whose operating time of the production equipment is above a certain period of time is selected as the pilot line. The software update method according to claim 1.

4. Based on the production plan of the aforementioned production line, the production line with the lowest production volume among the production lines that produce a certain amount of goods or more is selected as the pilot line. The software update method according to claim 1.

5. The evaluation of the operating status is performed based on a comparison of the operation log and system log of the pilot line before the software update with the operation log and system log after the software update. The software update method according to claim 1.

6. The evaluation of the operating status is performed based on a comparison of the operation log and system log of the pilot line with the operation log and system log of at least one other production line. The software update method according to claim 1.

7. The deployment conditions are that the production status of the pilot line after the software update is not deteriorating, or the degree of deterioration is less than a predetermined value. Based on the evaluation of the operating status, it is determined whether or not the deployment conditions are met. The software update method according to claim 5 or 6.

8. The aforementioned production line has at least production equipment for performing AOI processing, The evaluation of the operating status is performed based on at least one of the following: the presence or absence of system errors in the software, the rate of processing errors in the production equipment, the number of times the production equipment has stopped, the first-pass rate of the AOI of the production line, the production cycle time of the products produced on the production line, and the system response time of the production equipment. The software update method according to claim 1.

9. If the results of the operational status evaluation determine that the deployment conditions are met, the timing of the second update process is determined for each of the other production lines based on the respective production plans of the other production lines. Based on the determined timing, the second update process of the other production line is executed. The software update method according to claim 1.

Images