Diagnosis support system, diagnosis support method, and program

Abstract

A diagnosis support system for supporting a diagnosis which is related to a mounting device (10) for mounting a component on a substrate and performed on the basis of a production history of the mounting device (10) comprises: a determination unit (52) for determining whether an appropriate diagnosis can be performed for the mounting device (10), the determination being made on the basis of situation information indicating the situation of a collection system for collecting the production history of the mounting device (10); and a control unit (53) which, when it is determined by the determination unit (52) that an appropriate diagnosis cannot be performed for the mounting device (10), executes a notification process for notifying a service terminal (80) of a maintenance person in charge of recovery work of the production history that an appropriate diagnosis cannot be performed for the mounting device (10).

Description

Diagnosis support system, diagnosis support method and program

[0001] The present disclosure relates to a diagnostic support system, a diagnostic support method, and a program that support diagnosis of a mounting device that mounts components on a board, which diagnosis is performed based on the production history of the mounting device.

[0002] Conventionally, diagnostic systems have been known that collect data as a mounting device operates and analyze the collected data, for example, in a host device, to provide information on preventive maintenance of the mounting device. The collected data is transmitted to the host device via a network. For example, Patent Document 1 discloses an equipment element repair management system in which a support management PC (Personal Computer) in a support center located away from a factory acquires operation history information from the component mounter and analyzes the status trends of the equipment elements based on the operation history information.

[0003] Japanese Patent Application Laid-Open No. 2019-3461

[0004] However, in conventional systems, if a problem occurs during the process of collecting data, there is a risk that an appropriate diagnosis will not be made regarding the mounting device.

[0005] Therefore, the present disclosure provides a diagnostic support system, a diagnostic support method, and a program that can assist in performing appropriate diagnosis on a mounting device even if a problem occurs during the data collection process.

[0006] A diagnostic support system according to one aspect of the present disclosure is a diagnostic support system that supports diagnosis of a mounting device that mounts components on a substrate, which is performed based on the production history of the mounting device, and includes a determination unit that determines whether an appropriate diagnosis can be performed for the mounting device based on status information that indicates the status of a collection system that collects the production history of the mounting device, and a control unit that, when the determination unit determines that an appropriate diagnosis cannot be performed for the mounting device, executes a notification process to notify an information terminal of a maintenance technician in charge of restoring the production history that an appropriate diagnosis cannot be performed for the mounting device.

[0007] A diagnostic support method according to one aspect of the present disclosure is a diagnostic support method that supports diagnosis of a mounting device that mounts components on a substrate, which is performed based on the production history of the mounting device.The method determines whether or not an appropriate diagnosis can be performed for the mounting device based on status information that indicates the status of a collection system that collects the production history of the mounting device.If it is determined that an appropriate diagnosis cannot be performed for the mounting device, a notification process is executed to notify an information terminal of a maintenance technician in charge of restoring the production history that an appropriate diagnosis cannot be performed for the mounting device.

[0008] A program according to one aspect of the present disclosure is a program for causing a computer to execute the above-described diagnostic support method.

[0009] According to one aspect of the present disclosure, it is possible to realize a diagnostic support system or the like that can assist in performing appropriate diagnosis on a mounting device even if a problem occurs during the data collection process.

[0010] FIG. 1 is a diagram showing the configuration of a production system according to a comparative example. FIG. 2 is a diagram for explaining data used in diagnosis according to the comparative example. FIG. 3 is a diagram showing the configuration of a production system according to an embodiment. FIG. 4 is a flowchart showing the operation of a diagnosis support system according to an embodiment. FIG. 5 is a diagram for explaining data used in diagnosis according to an embodiment. FIG. 6 is a flowchart showing detailed operations of the current day data verification shown in FIG. 4. FIG. 7 is a flowchart showing operations for resuming diagnosis of a mounting device according to an embodiment.

[0011] (Background to the Invention of the Present Disclosure) Prior to describing the present disclosure, the background to the invention of the present disclosure will be described with reference to FIGS. 1 and 2. FIG. 1 is a diagram showing the configuration of a production system 1001 according to a comparative example. FIG. 1 schematically shows the configuration of a system in which a diagnostic system 1300 diagnoses mounting devices 1110a and 1110b in two factories (a factory 1100a of company A and a factory 1100b of company B). Diagnosis refers to determining whether maintenance or repair is necessary for the mounting devices 1110a and 1110b.

[0012] 1, the production system 1001 includes factories 1100a and 1100b, a cloud 1200, and a diagnostic system 1300. The factories 1100a and 1100b may have the same configuration, and the following description will be given using the factory 1100a.

[0013] The factory 1100a is, for example, a factory owned by company A that manufactures mounted boards and the like, and is equipped with a mounting device 1110a, a management device 1120a, and an auxiliary device 1130a.

[0014] The mounting device 1110a is a mounting facility (component mounting device) that mounts components on a target object such as a substrate. For example, a mounting line is configured including one or more mounting devices 1110a. Note that multiple mounting lines may be arranged on one floor of the factory 1100a.

[0015] The management device 1120a is a computer installed near the site where the mounting device 1110a operates, and collects and temporarily stores various information related to the production of the mounting device 1110a. The various information includes at least one of performance information such as the number of errors that occurred in the mounting device 1110a, events involving boards being transported in and out of each facility, the number of mounted boards produced, and the operating time of the mounting device 1110a. Examples of errors include, but are not limited to, pickup errors, recognition errors, and mounting errors.

[0016] The auxiliary device 1130a periodically acquires and stores production management information, event logs, and mount logs from the management device 1120a. The auxiliary device 1130a has a storage unit with a larger capacity than the management device 1120a. The storage unit may be realized, for example, by a semiconductor memory or the like, but is not limited to this. The auxiliary device 1130a periodically transmits the production management information, event logs, and mount logs to the cloud 1200. The production management information, event logs, and mount logs are also collectively referred to as performance information. The auxiliary device 1130a acquires the above-mentioned information from multiple management devices 1120a corresponding to multiple mounting devices 1110a (here, each of the multiple mounting devices 1110a constitutes a different mounting line).

[0017] In addition, the auxiliary device 1130a periodically transmits health monitoring data indicating whether the collection system on the factory 1100a side (e.g., at least one of the management device 1120a and the auxiliary device 1130a) is operating or not to the cloud 1200 as a status file.

[0018] In addition, the auxiliary device 1130a periodically transmits to the cloud 1200, as a status file, the operating status of the auxiliary device 1130a, the data acquisition status indicating whether the power is on or off, malfunctions, and the like.

[0019] In this way, the auxiliary device 1130a functions as a log collection tool and a vital data generation tool. The auxiliary device 1130a is disposed within the factory 1100a, but may also be disposed, for example, outside the factory 1100a.

[0020] The management device 1120a and the auxiliary device 1130a constitute a collection system in the factory 1100a. The mounting device 1110a and the management device 1120a constitute a client system. Although the management device 1120a and the auxiliary device 1130a are separate devices in the above example, they may be integrated into one device.

[0021] The cloud 1200 stores various information received from the auxiliary device 1130a and transmits the information to the diagnostic system 1300 upon request. The cloud 1200 also stores the data import status as a status file.

[0022] The diagnostic system 1300 diagnoses the mounting device 1110a based on the production history acquired from the cloud 1200. The diagnostic system 1300 performs a diagnosis based on the production history for a predetermined period, such as one day (hereinafter referred to as the diagnosis target period), and stores the results of the diagnosis. For example, if a malfunction occurs in the mounting device 1110a based on the results of the diagnosis, the diagnostic system 1300 notifies the factory 1100a. The diagnostic system 1300 is located outside the factory 1100a and performs a diagnosis based on the production history acquired remotely from the manufacturing site. In this comparative example, the diagnosis is performed on a daily basis, but the diagnosis may also be performed on a production lot basis, a number of mounting points basis, or the like.

[0023] The diagnostic system 1300 includes a downloader 1310 for efficiently downloading data from the cloud 1200, and a diagnostic device 1320 for executing diagnostic processing on the mounting device 1110a based on the data acquired via the downloader 1310. The diagnostic device 1320 generates, for example, a malfunctioning feeder list, which is a list of feeders determined to be malfunctioning in the diagnostic processing. Based on this malfunctioning feeder list, maintenance and other suggestions are made.

[0024] Here, diagnosis of the mounting device 1110a is basically based on the assumption that data acquisition is performed normally. However, even if data acquisition fails due to an infrastructure failure, the diagnostic process is still performed first, which may result in an inappropriate diagnostic result being reported. For example, if data acquisition is delayed due to an infrastructure failure, the diagnostic system 1300 may perform a diagnosis with some production history data from the target diagnostic period missing. In this case, the missing data is not taken into account, making an accurate diagnosis impossible, and manual recovery processing may be performed after the fact. Furthermore, the diagnostic system 1300 is unable to properly distinguish between a situation in which data cannot be acquired due to an infrastructure failure and a situation in which data cannot be acquired because production is not occurring, which may hinder the recovery process.

[0025] The factors that may cause data to be unavailable include factors within the factory 1100a, factors within the system including the diagnostic system 1300, communication factors, and factors within the cloud 1200. Possible factors within the factory 1100a include the state of the local area network (LAN) within the factory 1100a, incorrect settings in the collection system that collects data, malfunction of the collection system, and forgetting to start the collection system. Possible factors within the system including the diagnostic system 1300 include system downtime of the system including the diagnostic system 1300, PC malfunction, and failure to read data from the cloud 1200. Possible communication factors include failures in communication networks including the Internet. Possible factors within the cloud 1200 include failures related to data import. Due to such factors, even if a production history is available, the production history may not reach the diagnostic system 1300. Furthermore, if the mounting device 1110a is not operating, data cannot be acquired.

[0026] FIG. 2 is a diagram illustrating the data used for diagnosis in a comparative example. In FIG. 2, the horizontal axis represents the production time axis, and the vertical axis represents the time axis of the diagnostic device 1320. The bold frames in FIG. 2 indicate that the production history for the mounting device 1110a is used to diagnose the mounting device 1110a. Note that an example will be described in which the production history for the mounting device 1110a is used for the current day, taking into account data loss, and the production history data used for diagnosis is not limited to three days. A day marked with "Today's Production Acquisition Portion" indicates that the diagnostic system 1300 was able to acquire the production history for that day. A day marked with "Existing Acquisition Portion" indicates that data has already been acquired in the past (i.e., data exists). A day marked with "Data Recovery" indicates that data was acquired later that day. A day marked with "Not Downloaded" indicates that the missing data portion was recovered but not downloaded. Furthermore, a bold frame without hatching indicates that data is missing.

[0027] 2, for example, 11 / 3 indicates that production is taking place and that production history for that day has been acquired. On 11 / 4, the diagnostic system 1300 downloads the production history for three days, from 11 / 2 to 11 / 4, from the cloud 1200 and diagnoses the mounting device 1110a based on the downloaded production history for the three days. In this case, there is no missing data, so accurate diagnosis can be performed.

[0028] On the other hand, since no production history was acquired for 11 / 5, the diagnostic system 1300 assumes that there is no production history for 11 / 5 and diagnoses the mounting device 1110a as of 11 / 5 based on the production history for two days, 11 / 3 to 11 / 4. In this case, since there is no data for 11 / 5, there is a risk that the diagnosis of the mounting device 1110a cannot be performed accurately.

[0029] Furthermore, data is missing from November 5th to November 8th. In other words, the diagnostic system 1300 is unable to acquire the production history for those days. Since the production history for the past three days, including the day of November 7th, has not been acquired, the diagnostic system 1300 is unable to diagnose the mounting device 1110a on November 7th.

[0030] Furthermore, on 11 / 8, the production history for 11 / 6 was acquired later. This indicates that if the production history is not acquired, the maintenance person in charge of the production history recovery work handles the matter, and the production history for 11 / 6 was acquired later. Because the production history for 11 / 6 can be acquired on 11 / 8, the diagnostic system 1300 performs a diagnosis for 11 / 8 based on the production history for 11 / 6. The diagnostic system 1300 downloads the production history for 11 / 6 from the cloud 1200 and performs the diagnosis. However, in this case too, the diagnosis is not based on three days' worth of production history, so there is a risk that the diagnosis of the mounting device 1110a may not be accurate.

[0031] Furthermore, it is detected that there is production history for that day on 11 / 9, and the production history for that day is downloaded and diagnosed.

[0032] Also, suppose that on November 10th, the missing data for November 5th was restored, but it was not downloaded because it was outside the three-day grace period, and it was discovered that there was no production on November 7th and that data for November 8th was unavailable. In such cases, the data for November 5th will not be used in the diagnosis on November 10th.

[0033] In this way, in the past, if the diagnostic system 1300 was unable to acquire the production history due to some influence even though production had been performed, the diagnostic system 1300 would perform a diagnosis as if the data was not available, and even if the data became available later, the data would not be used for the diagnosis. Therefore, there is a risk that the diagnostic system 1300 will not be able to accurately diagnose the mounting device 1110a.

[0034] Therefore, the inventors of the present application conducted extensive research into diagnostic support systems that can assist in making appropriate diagnoses of mounting devices even when problems arise during the data collection process, and have devised the diagnostic support system described below. Specifically, the inventors devised a diagnostic support system that stops diagnosis when missing data is detected and performs diagnosis using past data, including data acquired later, on the day when all the data is available. This makes it possible to prevent the output of inaccurate diagnostic results due to missing data, and also makes it possible to output accurate diagnostic results, even if delayed.

[0035] A diagnostic support system according to a first aspect of the present disclosure is a diagnostic support system that supports diagnosis of a mounting device that mounts components on a substrate, which is performed based on the production history of the mounting device, and includes a determination unit that determines whether an appropriate diagnosis can be performed for the mounting device based on status information that indicates the status of a collection system that collects the production history of the mounting device, and a control unit that, when the determination unit determines that an appropriate diagnosis cannot be performed for the mounting device, executes a notification process to notify an information terminal of a maintenance technician in charge of restoring the production history that an appropriate diagnosis cannot be performed for the mounting device.

[0036] This allows a maintenance person to be notified if a problem occurs during the data collection process. The maintenance person can then carry out recovery work to quickly resolve the problem. This makes it possible to realize a diagnosis support system that can support early and appropriate diagnosis of the mounting device.

[0037] Also, for example, the diagnostic support system according to the second aspect may be the diagnostic support system according to the first aspect, and the control unit may output a stop signal to the diagnostic device performing the diagnosis to stop the diagnostic process if an appropriate diagnosis cannot be performed on the mounting device.

[0038] This allows the diagnostic device to stop the diagnosis if it is unable to perform an appropriate diagnosis of the mounting device, thereby supporting appropriate diagnosis of the mounting device from the viewpoint of preventing the output of an uncertain diagnostic result.

[0039] Furthermore, for example, the diagnosis support system according to the third aspect may be the diagnosis support system according to the first or second aspect, and when the determination unit determines that an appropriate diagnosis can be made on the mounting device based on the work information that is the result of the recovery work, the control unit may send information to the information terminal of the maintenance person inquiring whether or not to resume the diagnosis of the mounting device.

[0040] This allows the maintenance person to refer to the inquiry information and determine whether or not to resume the diagnosis.

[0041] Furthermore, for example, a diagnostic support system according to a fourth aspect is the diagnostic support system according to the third aspect, and when the determination unit receives an instruction from the maintenance person to resume the diagnosis of the mounting device, the determination unit may further determine whether or not an appropriate diagnosis can be performed on the mounting device based on the current communication state.

[0042] This allows the diagnostic process to be stopped when there is a risk of missing production history due to an unstable communication state, thereby supporting appropriate diagnosis of the mounting device from the viewpoint of preventing the output of uncertain diagnostic results due to an unstable communication state.

[0043] Furthermore, for example, a diagnostic support system according to a fifth aspect is the diagnostic support system according to the second aspect, and when the control unit resumes the diagnosis of the mounting device, the control unit may cause the diagnostic device to execute a diagnosis of the mounting device based on the production history of the mounting device for one or more operating days from when the diagnosis of the mounting device was stopped until when it was resumed.

[0044] This allows notification of the diagnosis results based on the production history for all operating days from the day the device was stopped until the day it was restarted. This allows diagnosis of the mounting device to be performed using the production history acquired later, which helps ensure that an appropriate diagnosis is performed for the mounting device.

[0045] Furthermore, for example, a diagnostic support system according to a sixth aspect is a diagnostic support system according to any one of the first to fifth aspects, and the control unit may cause a display device to display the results of the recovery work of the production history for each working day.

[0046] This allows the maintenance person to know whether production is in progress, thereby assisting the maintenance person in making the decision to turn off the service outage mode.

[0047] Furthermore, for example, a diagnostic support system according to a seventh aspect is a diagnostic support system according to any one of the first to sixth aspects, wherein the client system including the mounting device comprises a plurality of production devices including one or more of the mounting devices, a management device that collects performance information indicating the performance of each of the plurality of production devices as each of the production devices operates, and an auxiliary device that collects the production history indicating the cumulative total of the performance information from the management device, and the status information may include data indicating the status of at least one of the management device and the auxiliary device.

[0048] This makes it possible to determine whether appropriate diagnosis of the mounting device can be performed using the status of at least one of the management device and the auxiliary device. For example, it can be determined that an abnormality exists in the operation of either the management device or the auxiliary device, making it impossible to transmit the production history from the mounting device to the storage device.

[0049] Furthermore, for example, a diagnostic support system according to an eighth aspect is a diagnostic support system according to any one of the first to seventh aspects, and the determination unit may further determine whether an appropriate diagnosis can be made regarding the mounting device based on the production history of the mounting device.

[0050] This allows for a more accurate determination of whether or not an appropriate diagnosis can be made regarding the mounting device, since the production history is also used.

[0051] Furthermore, for example, a diagnostic support method according to a ninth aspect is a diagnostic support method that supports diagnosis of a mounting device that mounts components on a substrate, which is performed based on the production history of the mounting device, and determines whether or not an appropriate diagnosis can be performed for the mounting device based on status information that indicates the status of a collection system that collects the production history of the mounting device.If it is determined that an appropriate diagnosis cannot be performed for the mounting device, a notification process is executed to notify an information terminal of a maintenance person in charge of restoring the production history that an appropriate diagnosis cannot be performed for the mounting device.

[0052] This provides the same effects as the above-mentioned diagnosis support system.

[0053] Also, for example, a program according to a tenth aspect is a program for causing a computer to execute the diagnosis support method according to the ninth aspect.

[0054] This provides the same effects as the above-mentioned diagnosis support system.

[0055] These general or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a non-transitory recording medium such as a computer-readable CD-ROM, or as any combination of the system, method, integrated circuit, computer program, or recording medium. The program may be pre-stored in the recording medium, or may be supplied to the recording medium via a wide area communication network including the Internet.

[0056] Hereinafter, the embodiments will be specifically described with reference to the drawings.

[0057] The embodiments described below are all comprehensive or specific examples. The numerical values, shapes, components, component placement and connection configurations, steps, and step order shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components not described in independent claims are described as optional components.

[0058] Furthermore, each figure is a schematic diagram and is not necessarily an exact illustration. Therefore, for example, the scales of the figures do not necessarily match. Furthermore, in each figure, substantially the same components are given the same reference numerals, and redundant explanations are omitted or simplified.

[0059] Furthermore, in this specification, numerical values ​​and numerical ranges are not expressions that express only the strict meaning, but are expressions that mean that they also include a substantially equivalent range, for example, a difference of about several percent (or about 10%).

[0060] (Embodiment) Hereinafter, a diagnosis support system according to this embodiment will be described with reference to FIGS.

[0061] [1. Configuration of Diagnosis Support System] First, the configuration of a production system including a diagnosis support system according to this embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing the configuration of a production system 1 according to this embodiment.

[0062] 3 , the production system 1 includes a mounting device 10, a management device 20, an auxiliary device 30, a storage device 40, a service management device 50, a diagnostic device 60, a factory terminal 70, and a service terminal 80. The mounting device 10, the management device 20, and the auxiliary device 30 are, for example, located within a factory, while the service management device 50 and the diagnostic device 60 are, for example, located remotely from the factory. Furthermore, the auxiliary device 30, the storage device 40, the service management device 50, and the factory terminal 70 are communicatively connected via a communication network N.

[0063] The number of factories that are serviced by the service management device 50 is not limited to one, and may be multiple. For example, the number of factories that are serviced by the service management device 50 may be n (n is a natural number equal to or greater than 1).

[0064] The mounting device 10 and the management device 20 constitute a client system (the portion enclosed by the dashed line frame). The client system may also include an auxiliary device 30. For example, the client system may include a plurality of production devices (not shown) including one or more mounting devices, the management device 20, and the auxiliary device 30.

[0065] The management device 20 and the auxiliary device 30 constitute a collection system (the area enclosed by the dashed-dotted line frame).

[0066] The mounting device 10 corresponds to the mounting devices 1110a and 1110b shown in Fig. 1 and is a mounting facility (component mounting device) that mounts components on an object such as a substrate. For example, a mounting line is configured including one or more mounting devices 10. Note that multiple mounting lines may be arranged on one floor in a factory.

[0067] The mounting device 10 includes, as units, a substrate transport mechanism 11, a feeder 12, a mounting head 13, and a recognition camera 14.

[0068] The board transport mechanism 11 transports a board carried in from the upstream side in the transport direction, and positions and holds the board on a mounting stage set for performing component mounting work.

[0069] The feeder 12 supplies components to the component supply position. The feeder 12 may be, for example, a tape feeder that supplies components stored in each pocket of a carrier tape to the component supply position, a bulk feeder that supplies components stored in bulk to the component supply position, or some other feeder.

[0070] The mounting head 13 places (mounts) onto the board the components supplied to the component supply position (component suction position) of the feeder 12. The mounting head 13 is configured to include nozzles that can pick up components from the feeder 12 and move them up and down individually. The mounting head 13 is equipped with, for example, multiple nozzles.

[0071] The recognition camera 14 is a camera that captures a recognition image for recognizing a part.

[0072] The mounting device 10 also has a plurality of sensors that measure the state of each unit or each part that constitutes a unit. Examples of the plurality of sensors include, but are not limited to, a flow sensor that measures the flow rate and is provided in a flow path that supplies air to the suction hole of the nozzle, a current sensor that measures the current value of the motor that drives the feeder, and the recognition camera 14.

[0073] The management device 20 corresponds to the management devices 1120a and 1120b shown in FIG. 1 and has the same functions as the management devices 1120a and 1120b. Specifically, the management device 20 collects and temporarily stores various information related to the production performance of the mounting device 10. For example, when multiple production devices including the mounting device 10 are installed, the management device 20 collects performance information indicating the performance of each production device as the multiple production devices including the mounting device 10 operate. The performance information includes at least one of production management information, an event log, a mount log, the number of errors that occurred in the mounting device 10, events involving the transport of boards into and out of each facility, the number of mounted boards produced, the operating time of the mounting device 10, etc.

[0074] The management device 20 includes an interface 21, a control unit 22, and a temporary memory 23. The management device 20 also includes a processor and a memory. The memory may be a read-only memory (ROM) or a random access memory (RAM), and can store programs executed by the processor. Each function of the management device 20 is realized by the processor that executes programs stored in the memory. The management device 20 may be realized by a desktop PC, a mobile terminal such as a smartphone or tablet, a dedicated computer, or a combination thereof.

[0075] The interface 21 is a communication circuit (or a communication module) for the management device 20 to communicate with each of the mounting device 10 and the auxiliary device 30. The communication performed by the interface 21 may be wireless communication or wired communication.

[0076] The control unit 22 executes a performance information collection process that collects production management information, an event log, and a mount log of the mounting device 10. The control unit 22 acquires the production management information, the event log, and the mount log from the mounting device 10 via the interface 21 and stores them in the temporary memory 23. The timing of acquiring the production management information, the event log, and the mount log is not particularly limited. The performance information may be time-series data of the production management information, the event log, and the mount log for a predetermined period. Examples of the production management information include the total number of produced boards and the total operating time. Examples of the event log include, for example, the cumulative number of events, and examples of the mount log include, but are not limited to, the cumulative number of errors. The cumulative number of events is, for example, the number of events that occurred in a predetermined period, and the cumulative number of errors is, for example, the number of errors that occurred in a predetermined period.

[0077] The control unit 22 also periodically transmits production management information, an event log, and a mount log to the auxiliary device 30. The control unit 22 may also transmit measurement results obtained by a sensor or the like provided in the mounting device 10 to the auxiliary device 30 as current data related to the mounting device 10. The control unit 22 may also store the measurement results in the temporary memory 23.

[0078] The temporary memory 23 is a storage device that stores the production management information, event log, and mount log from the mounting device 10. "Temporarily" means that the production management information, event log, and mount log from the mounting device 10 are stored for a temporary period until the timing of outputting them to the auxiliary device 30. The temporary memory 23 is realized by, for example, a semiconductor memory or the like, but is not limited to this.

[0079] The auxiliary device 30 corresponds to the auxiliary devices 1130a and 1130b shown in FIG. 1 and accumulates data from the management device 20. The auxiliary device 30 includes an interface 31, a control unit 32, and a storage unit 33. The auxiliary device 30 also includes a processor, memory, etc. The memory may be a ROM or RAM, and may store a program executed by the processor. Each function of the auxiliary device 30 is realized by the processor, etc., which executes a program stored in the memory. The auxiliary device 30 may be realized by a desktop PC, a mobile terminal such as a smartphone or tablet, a dedicated computer, etc., or a combination thereof.

[0080] The interface 31 is a communication circuit (or a communication module) that enables the auxiliary device 30 to communicate with each of the management device 20 and the storage device 40. The communication performed by the interface 31 may be wireless communication or wired communication.

[0081] The control unit 32 executes an acquisition process that periodically acquires production management information, an event log, and a mount log from the management device 20 via the interface 31 and stores the acquired information in the storage unit 33. The control unit 32 also periodically generates a monitoring signal indicating that the acquisition process is not stopped and generates a data acquisition status indicating the operating status of at least one of the management device 20 and the auxiliary device 30. The operating status includes, for example, the power status of at least one of the management device 20 and the auxiliary device 30 (e.g., whether the power is on or not), whether there is a malfunction, etc. The control unit 32 transmits the monitoring signal and the data acquisition status to the storage device 40. The monitoring signal is also referred to as alive / dead monitoring data. The alive / dead monitoring data is data for notifying whether the factory's collection system is operating and is periodically transmitted to the storage device 40. The alive / dead monitoring data and the data acquisition status are also collectively referred to as an acquisition history. The control unit 32 can also be said to execute an acquisition history generation process that generates an acquisition history.

[0082] The storage unit 33 is a storage device that stores information from the management device 20. For example, the storage unit 33 stores production management information 33a, an event log 33b, and a mount log 33c. The storage unit 33 may also store an acquisition history generated by the control unit 32. The storage unit 33 is realized by, for example, a semiconductor memory or the like, but is not limited to this.

[0083] 1, and includes a diagnostic database 41 and an acquisition history database 42. The storage device 40 may be a cloud storage or the like.

[0084] The diagnostic database 41 stores information related to the diagnosis of the mounting device 10 by the diagnostic device 60. Specifically, the diagnostic database 41 stores a diagnostic result 41a, a production history 41b, and work information 41c.

[0085] The diagnosis result 41 a indicates the diagnosis result of the mounting apparatus 10 by the diagnosis apparatus 60 .

[0086] The production history 41b is time-series data including the production management information 33a, the event log 33b, and the mount log 33c.

[0087] The work information 41c indicates the results of the recovery work performed by the maintenance person in charge of the production history recovery work. The work information 41c is, for example, information entered by the maintenance person into the service terminal 80. The work information 41c includes information such as whether the missing data was recovered or whether the data cannot be obtained.

[0088] The acquisition history database 42 stores information used to identify the cause of data loss in the service management device 50. Specifically, the acquisition history database 42 stores alive monitoring data 42a and data acquisition status 42b. The alive monitoring data 42a and data acquisition status 42b are as described above.

[0089] The service management device 50 is an example of a diagnostic support system, and executes processing to support appropriate diagnosis of the mounting device 10, even if a problem occurs in the process of collecting data, based on at least the situation information described below. The service management device 50 supports diagnosis of the mounting device 10, which is performed based on the production history of the mounting device 10 that mounts components on a board.

[0090] The service management device 50 includes an interface 51, a determination unit 52, and a control unit 53. The service management device 50 also includes a processor, a memory, etc. The memory may be a ROM or RAM, and may store a program executed by the processor. Each function of the service management device 50 is realized by the processor, etc., that executes a program stored in the memory. The service management device 50 may be realized by a desktop PC, a mobile terminal such as a smartphone or tablet, a dedicated computer, etc., or a combination thereof.

[0091] The interface 51 is a communication circuit (or a communication module) that enables the service management device 50 to communicate with each of the storage device 40, the factory terminal 70, and the service terminal 80. The communication performed by the interface 51 may be wireless communication or wired communication.

[0092] The determination unit 52 determines whether or not an appropriate diagnosis can be made for the mounting device 10 based on status information including at least one of data indicating the production history of the mounting device 10 and data indicating the status of a collection system that collects the production history of the mounting device 10 (for example, the status of at least one of the management device 20 and the auxiliary device 30). In this embodiment, the determination unit 52 determines whether or not an appropriate diagnosis can be made for the mounting device 10 based on at least the status information. The status information includes information indicating whether the power of the management device 20 and the auxiliary device 30 is on / off, whether there is a lot of collected data and whether the operating status of the management device 20 is unstable, etc.

[0093] The control unit 53 executes various processes when the determination unit 52 determines that the production is in an unknown state, that is, when it determines that an appropriate diagnosis cannot be made for the mounting device 10. For example, when it is determined that an appropriate diagnosis cannot be made for the mounting device 10, the control unit 53 executes a notification process to notify the service terminal 80 of the maintenance person in charge of the work of restoring the production history that an appropriate diagnosis cannot be made for the mounting device 10.

[0094] Furthermore, when it is determined that an appropriate diagnosis cannot be performed on the mounting device 10, the control unit 53 transitions the mounting device 10 to a service stop mode in which diagnosis by the diagnostic device 60 is suspended. For example, when data loss occurs, the control unit 53 stops the diagnosis by the diagnostic device 60. For example, the control unit 53 generates a stop signal for transitioning to the service stop mode, that is, a stop signal for stopping the diagnostic process by the diagnostic device 60, and outputs it to the diagnostic device 60. This makes it possible to prevent diagnosis from being performed in a state where data is missing.

[0095] Furthermore, when the control unit 53 receives an instruction permitting a transition from the out-of-service mode to the normal mode, it transitions the diagnostic device 60 from the out-of-service mode to the normal mode. That is, when transition to the normal mode is permitted, the control unit 53 resumes diagnosis by the diagnostic device 60. The control unit 53 generates, for example, a control signal for transitioning to the normal mode and outputs it to the diagnostic device 60. This can assist in resuming diagnosis when the maintenance technician has completed investigation and data recovery. The processing of the control unit 53 will be described later using FIG. 4 and subsequent figures.

[0096] The diagnostic device 60 corresponds to the diagnostic system 1300 (or the diagnostic device 1320) shown in FIG. 1 , downloads the production history 41b from the storage device 40, and executes diagnostic processing for the mounting device 10. The diagnostic device 60 performs diagnosis to perform preventive maintenance on the mounting device 10, but may also detect, for example, a malfunction of the mounting device 10. Note that a malfunction refers to the occurrence of an alert that does not necessarily accompany the shutdown of the mounting device 10, and is, for example, a state in which it is suspected that at least one of the feeder, head spindle, and nozzle has failed or deteriorated. A malfunction of the mounting device 10 may be detected, for example, by an increasing error rate or a decreasing feeder feeding accuracy.

[0097] The diagnostic device 60 is controlled to stop and restart diagnosis based on instructions from the service management device 50. The diagnostic device 60 is configured to be switchable between a normal mode in which the mounting device 10 is diagnosed using the production history 41b and a service stop mode in which the diagnosis is stopped. Note that in the service stop mode, a download process for downloading the production history from the storage device 40 is not performed.

[0098] A diagnostic system may be configured to include the service management device 50 and the diagnostic device 60. The service management device 50 and the diagnostic device 60 may also be realized as an integrated device.

[0099] The factory terminal 70 is an information terminal carried by a factory staff member. The factory terminal 70 has a function of, for example, acquiring diagnostic results from the service management device 50 and presenting them to the staff member. The factory terminal 70 includes a presentation unit that presents the diagnostic results to the factory staff member and a reception unit that receives input of countermeasure results according to the diagnostic results. The presentation unit is realized by, for example, a display panel, a speaker, etc. The reception unit is realized by, for example, a touch panel, buttons, a microphone, etc. The factory terminal 70 is realized by, for example, a PC, a smartphone, etc.

[0100] The service terminal 80 is an information terminal carried by a maintenance staff member in charge of investigating and recovering production history. The service terminal 80, for example, acquires a request for investigation and recovery work from the service management device 50 and outputs the results of the investigation and recovery work to the service management device 50. The service terminal 80 includes a presentation unit that presents the request for investigation and recovery work to the maintenance staff and a reception unit that receives input of the results of the recovery work. The presentation unit is realized, for example, by a display panel, a speaker, etc. The reception unit is realized, for example, by a touch panel, buttons, a microphone, etc. The service terminal 80 is realized, for example, by a PC, a smartphone, etc.

[0101] The service terminal 80 receives a notification from the service management device 50 indicating that a maintenance person will investigate and recover data regarding the unknown production state during the service outage period when the diagnostic device 60 has stopped diagnosis in service outage mode.

[0102] The service terminal 80 is provided, for example, for each factory, and in this embodiment, n service terminals 1 to n may be provided.

[0103] [2. Operation of the Service Management Device] Next, the operation of the service management device 50 of the production system 1 configured as described above will be described with reference to FIGS. 4 to 7. FIG. 4 is a flowchart showing the operation of the diagnostic support system (diagnostic support method) according to this embodiment. FIG. 4 shows the operation executed by the service management device 50, which is an example of a diagnostic support system. Steps S10 to S60 in FIG. 4 are processes executed on a mounting line basis, and step S70 and subsequent steps are processes executed on a floor basis. FIG. 5 is a diagram for explaining data used in the diagnosis according to this embodiment. For example, the table shown in FIG. 5 may be displayed on the service terminal 80.

[0104] 4, the determination unit 52 executes a download process to download the production history for three days starting from the current day from the storage device 40 via the interface 51 (S10). The downloaded production history may be stored in a storage unit (not shown) included in the service management device 50. The storage unit may be realized by, for example, but is not limited to, a semiconductor memory or the like.

[0105] Explaining this with reference to FIG. 5, for example, if the current day is November 4th, the production history for three days including November 4th (that is, November 2nd to November 4th) is downloaded from the storage device 40.

[0106] 4 again, the determination unit 52 then performs a verification of the current day data based on the production history acquired by the download process (S20). The current day data verification includes verifying the production history (for example, S21 shown in FIG. 6, which will be described later) and verifying the acquisition history (for example, S22 shown in FIG. 6, which will be described later).

[0107] FIG. 6 is a flowchart showing the detailed operation (diagnosis support method) of the current day data verification shown in FIG.

[0108] 6, the determination unit 52 determines whether or not there is download data (S21). If the production history for the day has been downloaded (YES in S21), the determination unit 52 determines that there is download data, and if the production history for the day has not been downloaded (NO in S21), the determination unit 52 determines that there is no download data.

[0109] If the production history for that day is not downloaded (NO in S21), the determination unit 52 determines that the production status for that day is unknown (YES in S30). For example, if multiple mounting lines are arranged on a factory floor, the determination unit 52 may stop diagnosis of all mounting lines if it determines that the production status for at least one mounting line is unknown.

[0110] 5, data for that day is missing on November 5. In this case, the determining unit 52 determines that the production status for that day is unknown because there is no download data for that day.

[0111] Referring again to FIG. 6, if the production history for that day has been downloaded (S21), the determination unit 52 may determine that the production status for that day is not unknown (NO in S30).

[0112] If the result of step S21 is YES, the determination unit 52 may further execute the processes of step S22 and subsequent steps.

[0113] When the production history for that day has been downloaded (S21), the determination unit 52 determines the state of the communication infrastructure (S22). The determination unit 52 determines whether there is a concern about the communication state, for example, when a failure occurs in the communication infrastructure. Whether a failure occurs in the communication infrastructure is determined based on the acquisition history of at least one of the alive monitoring data and the data acquisition status from the auxiliary device 30, but may also be acquired from an external device, for example. In this way, at least one of the alive monitoring data and the data acquisition status may be used to determine whether a failure occurs in the communication infrastructure.

[0114] If a fault has occurred in the communication infrastructure (NG in S22), the judgment unit 52 judges that the production status on that day is unknown (YES in S30), and if no fault has occurred in the communication infrastructure (OK in S22), the judgment unit 52 proceeds to step S23.

[0115] Next, the determination unit 52 determines whether or not the production history includes an equipment log for that day (S23). If the equipment log for that day is present (S23), the determination unit 52 determines whether or not the number of sheets produced on that day is one or more based on the production management information 33a for that day included in the production history 41b (S24).

[0116] Next, if the determination unit 52 determines that the number of boards produced on that day is one or more (YES in S24), it determines whether or not boards have been carried in and out through all of the equipment included in the mounting line based on the event log 33b for that day included in the production history 41b (S25). If boards have been carried in and out through all of the equipment based on the event logs 33b for that day for all of the equipment, the determination unit 52 determines that boards have been carried in and out through all of the equipment. It can also be said that the determination unit 52 determines whether boards have been carried in and out through each piece of equipment from the beginning to the end of the mounting line based on the event logs 33b.

[0117] Next, when it is determined that boards have been carried in and out through all the equipment (YES in S25), the determination unit 52 determines whether there is one or more records with a mounting count of 1 or more based on the mount log 33c included in the production history 41b (S26). When the number of pickup errors included in the mount log is less than the number of mounting attempts, the determination unit 52 determines that there is one or more records with a mounting count of 1 or more.

[0118] Next, if the determination unit 52 determines that there is one or more records with a placement count of 1 or more (valid in S26), it determines that production is occurring (S27). That is, it determines that production is occurring at the factory that day. Furthermore, if there are no equipment logs for that day (NO in S23), if it determines that the number of boards produced that day is less than one (NO in S24), if it determines that no boards have been carried in or out through all the equipment (NO in S25), or if it determines that there are no records with a placement count of 1 or more (invalid in S26), it determines that there is no production (S28). That is, the determination unit 52 determines that production is not occurring at the factory that day. Then, proceed to NO in step S30.

[0119] In this way, the service management device 50 may be able to automatically determine whether or not the mounting device 10 is in production. The determination result as to whether or not the mounting device 10 is in production may be notified to the service terminal 80 of the maintenance person.

[0120] 4 , next, when the determination unit 52 determines that the production status for that day is unknown (YES in S30), the control unit 53 sets the diagnosis for that day to be suspended (S40) and turns on the service stop mode (S50). Specifically, the control unit 53 sends a stop signal to the diagnostic device 60 indicating that the diagnosis for that day is to be suspended. As a result, the diagnostic device 60 stops performing diagnosis. The current day becomes the first day of the diagnosis suspension period. Note that the diagnosis suspension period is the aforementioned diagnosis target period, and is a period that includes the day on which some production history data for the diagnosis target period was not acquired and the determination unit 52 determined that the production status for that day was unknown.

[0121] Next, the control unit 53 notifies relevant parties of information indicating that the diagnosis for that day will be stopped (S60). The control unit 53 notifies the relevant information to, for example, the service terminal 80 of the maintenance person who handles the fact that the production status for that day is unknown, and returns to step S10, and executes the processing from step S10 onwards on the next day in the service stop mode. The control unit 53 may also send information indicating that the diagnosis for that day will be stopped to the factory terminal 70. This allows the factory person to be notified that the diagnosis for that day will be stopped.

[0122] 5, the data for November 6th is also missing. Therefore, when step S10 is executed again the next day (November 6th) after step S60, the determination unit 52 determines that the production status is unknown because there is no download data for that day, and the diagnosis remains stopped.

[0123] Also, 11 / 7 indicates that as a result of verifying some of the obtained logs, it was determined that there was no production (S28 in FIG. 6). For example, even if the communication infrastructure is normal and equipment logs can be obtained, if all of steps S24, S25, and S26 are not satisfied, it is determined that there is no production. In this way, it is possible that there are logs but it is determined that there is no production (S28).

[0124] Furthermore, data is missing on November 8. Therefore, diagnostic device 60 operates in out-of-service mode from November 5 to November 8, and no diagnosis is performed.

[0125] 4, if the determination unit 52 determines that the production status of the day is not unknown (NO in S30), the control unit 53 determines whether or not to cancel the service suspension mode if the service suspension mode is currently active (S70). The process for canceling the service suspension mode will be described later with reference to FIG.

[0126] Next, if the control unit 53 determines that the current mode is the service stop mode and that the service stop mode should be continued (ON in S70), it returns to step S10 and executes the processing from step S10 onwards on the next day in the service stop mode.

[0127] Furthermore, if the control unit 53 determines that the diagnostic device 60 is currently in the out-of-service mode and will not continue in the out-of-service mode (OFF in S70), the control unit 53 transitions the diagnostic device 60 from the out-of-service mode to the normal mode. The control unit 53 generates a control signal for switching to the normal mode and transmits it to the diagnostic device 60.

[0128] If there are multiple mounting lines on the floor, the processes from step S80 onward may be executed if it is determined in step S70 that the status is OFF for multiple mounting lines.

[0129] Next, the control unit 53 determines whether or not there is a diagnosis suspension period (S80). The diagnosis suspension period is a period including days during which the device is operating in out-of-service mode and diagnosis has not been performed.

[0130] Referring back to FIG. 4 , when the control unit 53 determines that there is a diagnosis suspension period (S80), it causes the diagnostic device 60 to perform a diagnosis using the production history for the entire suspension period plus two days (see the bold box around 11 / 10 in FIG. 5) (S90). In the example of FIG. 5 , there is production history for 11 / 10, so the diagnostic device 60 can perform a diagnosis for 11 / 10. However, the diagnostic device 60 is in service suspension mode for the period from 11 / 5 to 11 / 9, and no diagnosis has been performed. In step S90, the diagnostic device 60 performs a diagnosis for the period from 11 / 5 to 11 / 9, which is the diagnosis suspension period, together with the period from 11 / 10 to 11 / 9. The diagnostic device 60 may perform a diagnosis for 11 / 10 after performing a diagnosis for the period from 11 / 5 to 11 / 9, which is the diagnosis suspension period. In the example of FIG. 5 , the control unit 53 causes the diagnostic device 60 to perform a diagnosis using the production history for the period from 11 / 3 to 11 / 10. In the example of FIG. 5, the data for 11 / 5 and 11 / 6 has been restored, there was no production on 11 / 7 (i.e., there is no production history), and data for 11 / 8 is unavailable, so the diagnostic device 60 will perform diagnosis using the production history from 11 / 3 to 11 / 6 and 11 / 9 to 11 / 10.

[0131] In this way, when the control unit 53 resumes diagnosis of the mounting device 10, it may cause the diagnostic device 60 to perform diagnosis of the mounting device 10 based on the production history of the mounting device 10 for one or more operating days from when the diagnosis of the mounting device 10 was stopped until it was resumed.

[0132] The number of days added to the total reservation period is not limited to two days, and may be, for example, one day, three or more days, or 0 days. The number of days added is, for example, set in advance.

[0133] The control unit 53 may display the results of the production history restoration work (for example, the table shown in FIG. 5) for each working day on a display device (for example, the display unit of the service terminal 80).

[0134] 4 again, next, the control unit 53 notifies the relevant parties of the diagnosis result (S100). The control unit 53 may notify the service terminal 80 of the maintenance person or may notify the factory terminal 70 of the factory person of the diagnosis result. Then, the process returns to step S10, and the processes from step S10 onwards are executed the next day.

[0135] If the control unit 53 determines that there is no diagnosis pending period (No in S80), it performs diagnosis based on the production history for the three days starting from the current day (S110).Then, the process returns to step S10, and the process from step S10 onwards is executed on the following day.

[0136] Next, a process for canceling the service stop mode will be described with reference to Fig. 7. Fig. 7 is a flowchart showing the operation (diagnosis support method) for restarting the diagnosis of the mounting device 10 according to this embodiment.

[0137] 7 , the determination unit 52 of the service management device 50 acquires work information (S71). The determination unit 52 acquires the work information from a maintenance technician via, for example, the service terminal 80. The determination unit 52 may transmit the acquired work information to the storage device 40.

[0138] Next, the determination unit 52 determines whether or not the investigation of the reservation period and data recovery are completed based on the acquired work information (S72). The determination unit 52 may execute the determination of step S72 based on information acquired from outside, such as the work information, and information acquired by processing of its own device, such as a determination of whether production is occurring.

[0139] Next, if the determination unit 52 determines that the investigation and data recovery for each day of the suspension period have been completed (YES in S72), the control unit 53 inquires of the maintenance staff's service terminal 80 whether to transition from the service suspension mode to the normal mode (whether to resume the diagnosis) (S73). The control unit 53 may display an icon (e.g., an OFF button) for transitioning to the normal mode (i.e., turning off the service suspension mode) on the display unit of the service terminal 80. The control unit 53 may further display information indicating that the investigation and data recovery for each day of the suspension period have been completed on the service terminal 80 of the maintenance staff. The control unit 53 may, for example, display the table shown in FIG. 5 on the service terminal 80. The determination unit 52 determines whether the investigation and data recovery for the suspension period have been completed by, for example, determining whether a certain period of time has elapsed.

[0140] In this way, when the judgment unit 52 determines that an appropriate diagnosis can be made on the mounting device 10 based on the work information that is the result of the investigation and recovery work, the control unit 53 sends information to the service terminal 80 of the maintenance staff inquiring whether or not to resume the diagnosis of the mounting device 10.

[0141] Next, the control unit 53 determines whether or not pressing of the OFF button to turn off the service stop mode has been detected (S74). That is, the control unit 53 determines whether or not the OFF button has been pressed by the maintenance person. The control unit 53 acquires information indicating whether or not the OFF button has been pressed from the service terminal 80.

[0142] Next, if the judgment unit 52 does not detect the pressing of the OFF button (NO in S74), it determines that the situation is such that appropriate diagnosis cannot be performed on the mounting device 10, and proceeds to ON in step S70 shown in Figure 4.If the judgment unit 52 detects the pressing of the OFF button (YES in S74), it determines that appropriate diagnosis can be performed on the mounting device 10, and proceeds to step S75.

[0143] Next, the determination unit 52 determines the current state of the communication infrastructure (S75). In this way, when the determination unit 52 receives an instruction from the maintenance person to resume the diagnosis of the mounting device 10 (YES in S74), the determination unit 52 further determines whether or not an appropriate diagnosis can be performed on the mounting device 10 based on the current communication state. If there is a concern about the communication state, such as when a failure occurs in the communication infrastructure, the determination unit 52 determines that the communication infrastructure state is NG.

[0144] If the determination unit 52 determines that the communication infrastructure state is NG (NG in S75), the control unit 53 causes the service terminal 80 to display an error (S76) and proceeds to ON in step S70. Also, if the determination unit 52 determines that there is no problem with the communication infrastructure state (OK in S75), the control unit 53 turns off the service stop mode (S77). That is, the control unit 53 causes the diagnostic device 60 to resume diagnosis. The control unit 53 generates a control signal for resuming diagnosis and transmits it to the diagnostic device 60.

[0145] Next, the control unit 53 notifies the relevant parties that the diagnosis has been resumed (S78). The control unit 53 notifies the service terminal 80 of the maintenance person that the diagnosis has been resumed, but may also notify the factory terminal 70 of the factory person. Then, the process proceeds to OFF in step S70.

[0146] (Other Embodiments) While the diagnosis support system according to one or more aspects has been described above based on the embodiments, the present disclosure is not limited to these embodiments. As long as it does not deviate from the spirit of the present disclosure, various modifications conceivable by a person skilled in the art to the present embodiments and embodiments constructed by combining components of different embodiments may also be included in the present disclosure.

[0147] For example, in the above embodiment, an example was described in which the processing shown in Figure 4 is executed once a day, but the execution cycle is not limited to once a day, and it may be executed every few hours or every few days.

[0148] Furthermore, for example, in the above-described embodiments, each component may be configured with dedicated hardware, or may be realized by executing a software program suitable for each component. Each component may be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

[0149] The order in which the steps in the flowchart are executed is merely an example for specifically explaining the present disclosure, and other orders may be used. Some of the steps may be executed simultaneously (in parallel) with other steps, or some of the steps may not be executed.

[0150] The division of functional blocks in the block diagram is an example, and multiple functional blocks may be realized as a single functional block, one functional block may be divided into multiple blocks, or some functions may be moved to another functional block.Furthermore, the functions of multiple functional blocks having similar functions may be processed in parallel or in time-sharing by a single piece of hardware or software.

[0151] Furthermore, the diagnosis support system according to the above-described embodiment may be realized as a single device or may be realized by multiple devices. When the diagnosis support system is realized by multiple devices, the components of the diagnosis support system may be distributed among the multiple devices in any manner. When the diagnosis support system is realized by multiple devices, the communication method between the multiple devices is not particularly limited, and may be wireless communication or wired communication. Furthermore, wireless communication and wired communication may be combined between the devices.

[0152] Furthermore, each component described in the above embodiments may be implemented as software or, typically, as an LSI, which is an integrated circuit. These components may be individually integrated into a single chip, or some or all of them may be integrated into a single chip. Here, the term "LSI" is used, but depending on the level of integration, it may also be referred to as an IC, system LSI, super LSI, or ultra LSI. Furthermore, the integrated circuit implementation method is not limited to LSI, and may be implemented using a dedicated circuit (a general-purpose circuit that executes a dedicated program) or a general-purpose processor. After LSI fabrication, a field programmable gate array (FPGA) that can be programmed or a reconfigurable processor that can reconfigure the connections or settings of circuit cells within the LSI may also be used. Furthermore, if an integrated circuit technology that replaces LSI emerges due to advances in semiconductor technology or a derivative technology, that technology may naturally be used to integrate the components.

[0153] A system LSI is an ultra-multifunctional LSI manufactured by integrating multiple processing units on a single chip, and is specifically a computer system comprising a microprocessor, ROM, RAM, etc. The ROM stores computer programs. The system LSI achieves its functions when the microprocessor operates in accordance with the computer programs.

[0154] Furthermore, one aspect of the present disclosure may be a computer program that causes a computer to execute each of the characteristic steps included in the diagnostic support method shown in any one of FIG. 4, FIG. 6, and FIG.

[0155] Furthermore, for example, the program may be a program to be executed by a computer. Another aspect of the present disclosure may be a computer-readable non-transitory recording medium on which such a program is recorded. For example, such a program may be recorded on a recording medium and distributed or circulated. For example, the distributed program may be installed in a device having another processor, and the program may be executed by the processor, thereby causing the device to perform each of the above processes.

[0156] The present disclosure is useful for a diagnostic system that diagnoses the state of a mounting device.

[0157] 1, 1001 Production system 10, 1110a, 1110b Mounting device 11 Board transport mechanism 12 Feeder 13 Mounting head 14 Recognition camera 20, 1120a, 1120b Management device 21, 31, 51 Interface 22, 32, 53 Control unit 23 Temporary memory 30, 1130a, 1130b Auxiliary device 33 Storage unit 40 Storage device 41 Diagnostic database 41a Diagnostic result 41b Production history 41c Work information 42 Acquisition history database 42a Alive monitoring data 42b Data acquisition status 50 Service management device (diagnosis support system) 52 Determination unit 60, 1320 Diagnostic device 70 Factory terminal 80 Service terminal 1100a, 1100b Factory 1200 Cloud 1300 Diagnostic system 1310 Downloader N Communication network

Claims

1. A diagnostic support system that supports diagnosis of a mounting device that mounts components on a board, which is performed based on the production history of the mounting device, comprising: a determination unit that determines whether or not an appropriate diagnosis can be made for the mounting device, based on status information that indicates the status of a collection system that collects the production history of the mounting device; and a control unit that, when the determination unit determines that an appropriate diagnosis cannot be made for the mounting device, executes notification processing to notify an information terminal of a maintenance person in charge of restoring the production history that an appropriate diagnosis cannot be made for the mounting device.

2. The diagnostic support system according to claim 1, wherein the control unit outputs a stop signal to the diagnostic device performing the diagnosis to stop the diagnostic process when an appropriate diagnosis cannot be performed on the mounting device.

3. The diagnostic support system according to claim 1 or 2, wherein when the determining unit determines that an appropriate diagnosis can be made on the mounting device based on the work information resulting from the recovery work, the control unit transmits information to the information terminal of the maintenance person inquiring whether or not to resume the diagnosis of the mounting device.

4. The diagnostic support system according to claim 3, wherein, upon receiving an instruction from the maintenance person to resume diagnosis of the mounting device, the determination unit further determines whether or not an appropriate diagnosis can be performed on the mounting device based on the current communication state.

5. The diagnostic support system according to claim 2, wherein when the control unit resumes the diagnosis of the mounting device, the control unit causes the diagnostic device to execute a diagnosis of the mounting device based on the production history of the mounting device for one or more operating days from when the diagnosis of the mounting device was stopped until it was resumed.

6. The diagnostic support system according to claim 1 or 2, wherein the control unit causes a display device to display the results of the restoration work for the production history for each working day.

7. The diagnostic support system according to claim 1 or 2, wherein the client system including the mounting device comprises: a plurality of production devices including one or more of the mounting devices; a management device that collects performance information indicating the performance of each of the plurality of production devices as each of the production devices operates; and an auxiliary device that collects the production history indicating the cumulative total of the performance information from the management device; and the status information includes data indicating the status of at least one of the management device and the auxiliary device.

8. The diagnosis support system according to claim 1 or 2, wherein the determination unit further determines whether or not an appropriate diagnosis can be made for the mounting device based on the production history of the mounting device.

9. A diagnostic support method for supporting a diagnosis of a mounting device that mounts components on a substrate, which is performed based on the production history of the mounting device, the diagnostic support method comprising: determining whether or not an appropriate diagnosis can be made for the mounting device based on status information indicating the status of a collection system that collects the production history of the mounting device; and, if it is determined that an appropriate diagnosis cannot be made for the mounting device, executing a notification process to notify an information terminal of a maintenance person in charge of restoring the production history that an appropriate diagnosis cannot be made for the mounting device.

10. A program for causing a computer to execute the diagnostic support method according to claim 9.

Images