Source: https://patents.google.com/patent/US7047100
Timestamp: 2018-02-23 07:01:59
Document Index: 343834885

Matched Legal Cases: ['art 122', 'art 122', 'art 130', 'art 122', 'art 122', 'art 122', 'art 104', 'art 122', 'art 122', 'art 123', 'art 224', 'art 224', 'art 227', 'art 227', 'art 227', 'art 122', 'art 122', 'art 130', 'art 122', 'art 122', 'art 123', 'art 123', 'art 122', 'art 130', 'art 122', 'art 122', 'art 130', 'art 122', 'art 122', 'art 122', 'art 130', 'art 122', 'art 122', 'art 122', 'art 122', 'art 130', 'art 130', 'art 128', 'art 104', 'art 128', 'art 128', 'art 104', 'art 100', 'art 115', 'art 100', 'art 115', 'art 100', 'art 115', 'art 100', 'arts 115', 'art 100', 'arts 115', 'art 100', 'art 115', 'art 235', 'art 100', 'art 115', 'art 115', 'art 235', 'art 100', 'art 115', 'art 100', 'art 115', 'art 115', 'art 100', 'art 115', 'art 235', 'art 100', 'art 15', 'art 115', 'art 100', 'arts 115', 'art 235', 'art 100', 'art 115', 'art 235', 'art 100', 'art 115', 'application No. 0211937', 'application No. 1999', 'application No. 2000', 'application No. 2001', 'application No. 2001', 'application No. 10', 'application No. 10', 'application No. 10', 'application No. 10']

US7047100B2 - Substrate processing system managing apparatus information of substrate processing apparatus - Google Patents
US7047100B2
US7047100B2 US10189975 US18997502A US7047100B2 US 7047100 B2 US7047100 B2 US 7047100B2 US 10189975 US10189975 US 10189975 US 18997502 A US18997502 A US 18997502A US 7047100 B2 US7047100 B2 US 7047100B2
US10189975
US20030023340A1 (en )
G05B2219/32207—Action upon failure value, send warning, caution message to terminal
A substrate processing system comprises a substrate processing apparatus, an information storage server and a support computer, which are connected to a network respectively. When the substrate processing apparatus causes a failure, an alarm processing part extracts a necessary relevant log file and stores the same in a hard disk of the information storage server. A failure information generation part generates failure information, which in turn is finally stored in the hard disk of the information storage servers as a failure information database. An apparatus information uncasing part renders the relevant log file and the failure information database readable from the support computer located in a remote place. Thus, the relevant log file and the failure information database can be immediately read. In other words, provided is a substrate processing system rendering operation information immediately readable from a remote place when the substrate processing apparatus causes a failure.
The present invention relates to a network communication technique connecting a substrate processing apparatus performing prescribed processing on a semiconductor substrate, a glass substrate for a liquid crystal display, a glass substrate for a photomask or a substrate for an optical disk (hereinafter simply referred to as “substrate”) and a computer with each other through a network.
The present invention is directed to a substrate processing system connecting a substrate processing apparatus and a computer with each other to be capable of making communication through a network.
FIG. 1 schematically illustrates the structure of a substrate processing system according to the present invention;
FIG. 1 schematically illustrates the structure of a substrate processing system 10 according to a first embodiment of the present invention. As shown in FIG. 1, the substrate processing system 10 is mainly formed by connecting substrate processing apparatuses 1 and an information storage server 2 provided on a substrate processing factory 4 and support computers 3 provided on a support center 5 having failure analysts analyzing failures of the substrate processing apparatuses 1 with each other through a network 6.
FIG. 6 illustrates an exemplary alarm definition file 161. As shown in FIG. 6, the alarm definition file 161 is a table having a plurality of fields including “alarm code”, “display text”, “system control code”, “output log file code” etc.
The “alarm code” is a field indicating the identification code included in the given alarm. The remaining fields (“display text”, “system control code”, “output log file code” etc.) are associated with this “alarm code”. It follows that the alarm processing part 122 retrieves the identification code of the received alarm from the “alarm code” and performs processing according to the contents described in the remaining codes corresponding to this identification code.
The “display text” is a field indicating the specific contents of the failure as a text. The alarm processing part 122 makes the display part 130 display the contents indicated in this “display text”. Thus, the operator can grasp what kind of failure has been caused as a specific text.
The “system control code” is a field indicating the contents of control of the substrate processing apparatus 1 at the time of occurrence of the alarm. More specifically, control contents are previously assigned to the “system control code” so that the operation of the substrate processing apparatus 1 is stopped if the “system control code” is “1” and the substrate processing apparatus 1 is forcibly restarted if the “system control code” is “2”. The alarm processing part 122 performs operation control according to the contents described in the “system control code”, and hence it follows that the substrate processing apparatus 1 performs proper operation in response to the type of the failure.
The “output log file code” is a field indicating the identification codes of the log files 162 relevant to the cause of the alarm. In other words, the output log file code selectively describes only the identification codes of the log files 162 necessary for grasping the cause of the failure. Thus, the alarm processing part 122 can readily select and extract only the log files 162 (e.g., only the process log and the operation log) relevant to the cause of the alarm. The log files 162, relevant to the cause of the alarm, extracted by the alarm processing part 122 are hereinafter also referred to as relevant log files 262.
The failure information, one of the apparatus information for specifying the cause of the failure along with the relevant log files 262, comprises items such as “date”, “apparatus”, “unit”, “version”, “contents of failure” and “log”.
The “date” indicating the date of alarming is acquired from a prescribed timer circuit in generation of the failure information.
The “apparatus” is identification information of the faulty substrate processing apparatus 1 itself. The identification information, previously assigned to each of the substrate processing apparatuses 1 arranged on the substrate processing factory 4, is stored in the storage part 104.
The “unit” is identification information of the faulty processing unit 110. This indicates the processing unit 110 transmitting the alarm.
The “version” is version information of a unit control program in the faulty processing unit 110. The failure may occur only in a specific version of the program, and hence it may be possible to specify the cause of the failure through the version information.
The “contents of failure”, indicating the contents of the “display text” of the aforementioned alarm definition file 161, are acquired from the alarm processing part 122.
The “log”, which is a retention path of each relevant log file 262 in the information storage server 2, is acquired from the alarm processing part 122. It follows that the failure information and each relevant log file 262 are associated with each other through this item.
When receiving the failure information from the failure information generation part 123 of the substrate processing apparatus 1, the failure information registration part 224 additionally registers the same in a failure information database (hereinafter referred to as “failure information DB”) 261. Therefore, it follows that the hard disk 24 stores the failure information as the failure information DB 261. In the additional registration of the failure information, the failure information registration part 224 automatically generates an identification number of the added failure information.
FIG. 7 illustrates an exemplary failure information DB 261. As shown in FIG. 7, the failure information DB 261 has a plurality of fields D1 to D6 storing the items “date”, “apparatus”, “unit”, “version”, “contents of failure” and “log” of the failure information respectively. A field D0 stating “No.” stores the identification number of each generated failure information. The field D6 stating “log” stores the retention paths of the relevant log files 262, and hence the failure information DB 261 is also associated with the relevant log files 262. Failure information is stored as the failure information DB 261 every time a failure takes place, and hence it follows that the failure information DB 261 also shows the history of failures occurring in the past in the substrate processing factory 4 along with the information of the present failure.
The countermeasure information registration part 227 receives countermeasure information from the support computer 3. The countermeasure information includes results of analysis made by the failure analyst of the support center 5 reading the apparatus information of the faulty substrate processing apparatus 1 and a countermeasure against the failure etc. In other words, the countermeasure information registration part 227 serves as means acquiring failure countermeasure information based on the apparatus information. When receiving this countermeasure information, the countermeasure information registration part 227 additionally registers the same in a countermeasure information database (hereinafter referred to as “countermeasure information DB”) 263. Therefore, it follows that the hard disk 24 stores the countermeasure information as the countermeasure information DB 263.
The alarm processing part 122 receives the transmitted alarm and performs operation control responsive to the identification code. In other words, the alarm processing part 122 refers to the alarm definition file 161 and makes the display part 130 display specific contents of the failure described in the “display text”, while stopping operation of the substrate processing apparatus 1 according to the “system control code” (step S12).
The alarm processing part 122 further refers to the “output log file code” of the alarm definition file 161, extracts the relevant log files 262 and transmits the same to the information storage server 2 (step S13). The hard disk 24 stores the relevant log files 262 received in the information storage server 2 (step S21). Thus, it follows that only the relevant log files 262 necessary for analyzing the failure are extracted and reliably preserved. The process log, which is particularly important for analyzing the cause of the failure as hereinabove described, is preferably reliably preserved as one of the relevant log files 262.
Then, the alarm processing part 122 instructs the failure information generation part 123 to generate failure information while transferring the contents of the “display text” of the alarm definition file 161 and the retention paths of the relevant log files 262. The failure information generation part 123 instructed by the alarm processing part 122 generates failure information (step S14) and transmits the generated failure information to the information storage server 2 (step S15).
The failure analyst can specifically and readily grasp the contents of the failure through the failure information defining the final data of the failure information DB 261. The failure analyst can further display and read the relevant log files 262 for the failure by specifying the field D6 describing “log” through prescribed operation (steps S32 and S24). Only the relevant log files 262 relevant to the failure have already been extracted and hence the volume of the data is so limited that the data can be received at a relatively high speed.
The countermeasure information comprises information of items “No.”, “object apparatus”, “unit”, “analytic result”, “countermeasure”, “program schedule”, “version” etc.
The item “No.” indicates the identification number of the countermeasure information, which is identical to the identification number of the failure information.
The item “object apparatus” indicates the identification information of the faulty substrate processing apparatus 1, which is identical to the item “apparatus” in the failure information.
The item “unit” indicates the identification information of the faulty processing unit 110, which is identical to the item “unit” in the failure information.
The item “analytic result” indicates the results analyzed on the basis of the failure information and the relevant log files 262, specifically describing the cause of the failure etc.
The item “countermeasure” indicates a specific countermeasure against the failure, describing an operation procedure of action against the failure etc.
The item “program schedule” indicates a planned release date of a new problem for the substrate processing apparatus 1 for avoiding occurrence of failures. The substrate processing apparatus 1 can be prevented from the same failure due to an update to this new program.
The item “version” indicates version information of the aforementioned new program.
FIG. 9 illustrates an exemplary countermeasure information DB 263. As shown in FIG. 9, the countermeasure information DB 263 has a plurality of fields D10 to D16 storing information of the items “No.”, “object apparatus”, “unit”, “analytic result”, “countermeasure”, “program schedule” and “version” of the countermeasure information respectively. The contents of the countermeasure information DB 263 can be read in the information storage server 2 at any time, and hence it follows that the operator of the substrate processing factory 4 can also properly deal with the failure.
While the items “display text”, “system control code”, and “output log file code” are associated with the “alarm code” defining the warning signal in the alarm definition file 161 in the aforementioned embodiment, the “alarm code” may be associated with any other items so far as at least the warning signal and relevant operation information relevant to the cause of the warning signal are associated with each other.
The schematic structure of a substrate processing system 10 according to a second embodiment of the present invent is identical to that shown in FIG. 1. In the substrate processing system 10 according to the second embodiment, however, a support computer 3 stores additional information such as countermeasure information against a failure of a substrate processing apparatus 1, so that the substrate processing apparatus 1 can acquire the stored additional information through a network 6.
The countermeasure information 163 is prepared for each of the types of assumed failures and stored as an individual file. This countermeasure information 163 is selected at need upon occurrence of a failure, so that a display part 130 displays the contents thereof. The countermeasure information 163 previously stored in the substrate processing apparatus 1 is hereinafter also referred to as “in-apparatus countermeasure information” 163.
A hard disk 34 of the support computer 3 also stores additional information such as countermeasure information 363 against any failure of the substrate processing apparatus 1. The contents of the countermeasure information 363 are updated every time a system supervisor of a support center 5 finds out new countermeasure information. Therefore, it follows that the countermeasure information 363, also including information found out and added after introduction of the substrate processing apparatus 1, is regularly stored as the latest countermeasure information. The countermeasure information 363 stored in the support computer 3 is hereinafter also referred to as “latest countermeasure information” 363.
FIG. 12 illustrates an exemplary alarm definition file 461. As shown in FIG. 12, the alarm definition file 461 is a table having a plurality of fields including items such as “alarm code”, “display text”, “system control code”, “countermeasure information”, “date of updating” etc.
The “alarm code” is a field indicating the identification code included in the given alarm. The remaining fields (“display text”, “system control code”, “countermeasure information”, “date of updating” etc.) are associated with this “alarm code”. It follows that the alarm processing part 122 retrieves the identification code of the received alarm from the “alarm code” and performs processing according to the contents described in the remaining fields corresponding to this identification code.
The “display text” is a field indicating the contents of the failure as a text. The alarm processing part 122 makes the display part 130 display the contents indicated in this “display text”. Thus, the operator can grasp what kind of failure has been caused as a specific text.
The “system control code” is a field indicating the contents of control of the substrate processing apparatus 1 at the time of alarming. More specifically, control contents are previously assigned to the “system control code” so that the operation of the substrate processing apparatus 1 is stopped if the “system control code” is “1” and the substrate processing apparatus 1 is forcibly restarted if the “system control code” is “2”. The alarm processing part 122 performs operation control according to the contents described in the “system control code”, whereby it follows that the substrate processing apparatus 1 performs proper operation in response to the type of the failure.
The “countermeasure information” is a field indicating the file name of the in-apparatus countermeasure information 163 corresponding to the failure. In other words, the “alarm code” is associated with in-apparatus countermeasure information 163 corresponding to the failure resulting in the alarm. When the failure takes place, therefore, the alarm processing part 122 can readily select the in-apparatus countermeasure information 163 corresponding thereto. The alarm processing part 122 automatically displays the selected in-apparatus countermeasure information 163 on the display part 130 along with the aforementioned “display text”.
The “date of updating” is a field indicating the date of updating the in-apparatus countermeasure information 163 shown in the “countermeasure information”. In other words, it follows that the “date of updating” indicates that the in-apparatus countermeasure information 163 described on the “countermeasure information” has been the latest information at the point of time of the date shown in the “date of updating”. As to a file previously stored from the time of introduction of the substrate processing apparatus 1 and not updated at all, the dates of shipment or introduction of the substrate processing apparatus 1 may be either described or not described.
The alarm processing part 122 receives the transmitted alarm, for performing operation control responsive to the identification code. In other words, the alarm processing part 122 refers to the alarm definition file 461 and performs operation control such as stoppage of operation of the substrate processing apparatus 1 according to the “system control code” (step T12).
Then, the alarm processing part 122 refers to the “countermeasure information” of the alarm definition file 461 and selects the in-apparatus countermeasure information 163 corresponding to the failure. The alarm processing part 122 displays the contents of the selected in-apparatus countermeasure information 163 on the display part 130 along with the “display text” of the alarm definition file 461 (step T13). Thus, the operator of the substrate processing apparatus 1 can grasp the specific contents of the failure and a specific countermeasure against the failure.
The display part 130 also displays the contents of the “date of updating” of the alarm definition file 461. Thus, the operator can grasp the date of updating of the in-apparatus countermeasure information 163 having the displayed contents, for judging reliability of the contents. In other words, the operator can judge that there is a possibility that the support computer 3 stores new countermeasure information if a time has elapsed from the date of updating.
The countermeasure information acquisition part 128 overwrites the old in-apparatus countermeasure information 163 (that selected at the step T13) with the received latest countermeasure information 363 and makes the storage part 104 store the same. The countermeasure information acquisition part 128 also rewrites the “date of updating” of the alarm definition file 461 with the date of acquisition of the latest countermeasure information 363. The countermeasure information acquisition part 128 further rewrites the “countermeasure information” of the alarm definition file 461 with the file name of the acquired latest countermeasure information 363 for updating the same. Thus, it follows that the acquired latest countermeasure information 363 is newly associated with the alarm and stored as the in-apparatus countermeasure information 163 (step T17). In other words, the storage part 104 stores the latest countermeasure information 363 similarly to the countermeasure information previously existing from the time of introduction, and the alarm definition file 461 is updated in response thereto. Therefore, the added countermeasure information can also be managed as the countermeasure information against the failure in a unified manner, and treated similarly to the old countermeasure information.
While each countermeasure information 163 is stored as an individual file and indirectly associated with the warning signal (alarm) by the alarm definition file 461 in the aforementioned embodiment, the contents thereof may alternatively be described in the “countermeasure information” field of the alarm definition file 461 or the like to be directly associated with the warning signal. In other words, the warning signal and the countermeasure information against the failure resulting in this warning signal may be associated with each other.
The schematic structure of a substrate processing system 10 according to a third embodiment of the present invention is identical to that shown in FIG. 1. In the substrate processing system 10 according to the third embodiment, however, an information storage server 2 stores version information of software modules mounted on a substrate processing apparatus 1, so that the stored version information can be read in a support computer 3 through a network 6.
FIG. 16 illustrates an exemplary version management table 241. Referring to FIG. 16, “apparatus” denotes an identification number supplied to each substrate processing apparatus 1, “system version” denotes the version of the overall system mounted on the substrate processing apparatus 1, and “date of installation” denotes the date of installation of the software module 178 in at least the system control part 100 or the unit control part 115. Further, “category” denotes the type of the installed software module 178, “version classification” denotes whether the installed software module 178 is of a standard specification or a custom-built specification, and “version” denotes the version information of the installed software module 178.
As shown in FIG. 16, the version management table 241 registers the version information every substrate processing apparatus 1 arranged on the substrate processing factory 4. As to a substrate processing apparatus 1 having an apparatus number “8101”, for example, the version management table 241 records that the software module 178 was installed on Apr. 12, 2001 as a system version “1.00”. The version management table 241 also records that the version of the software module 178 is “1.0.0.1” as the version information of the software module 178 (category: “system control”) installed in the system control part 100 of the substrate processing apparatus 1 having the apparatus number “8101”. The version management table 241 further registers that the version classification of the software module 178 is “standard”.
As the version information of the software modules 178 (categories: “spin control”, “chemical solution control” etc.) installed in the unit control part 115 of the substrate processing apparatus 1 having the apparatus number “8101”, further, the version management table 241 registers that the versions of the software modules 178 are “1.1.0.1” and “1.0.0.3” respectively. The version management table 241 also registers that the version classifications of the software modules 178 are “standard” and “custom-built E” respectively.
Similarly as to a substrate processing apparatus 1 having an apparatus number “8100”, the version management table 241 records that the software module 178 was installed on Apr. 12, 2001 as the system version “1.00” and thereafter another software module 178 was installed on Apr. 20, 2001 as a system version “1.10”. That is, the version management table 241 records not only the current version information but also the past version history every substrate processing apparatus 1. In other words, the hard disk 24 according to this embodiment functions as version information storage means storing the version information of the software modules 178 installed in the system control part 100 and the unit control part 115.
The version management table 241 shown in FIG. 16 is constructed as a result of integrating the version information of the software modules 178 presently installed in the system control part 100 and all unit control parts 115 when any software module 178 is installed in the substrate processing apparatus 1. Assuming that the new software module (version: “1.0.0.3”) for chemical solution control was installed in the substrate processing apparatus 1 having the apparatus number “8101” on Apr. 12, 2001, for example, the hard disk 24 stores the version information of the software modules 178 installed in the system control part 100 and all unit control parts 115 included in the substrate processing apparatus 1 having the apparatus number “8101” at this date, to construct the version management table 241 shown in FIG. 16.
When a software module 178 is installed in the system control part 100 or the unit control part 115 of a certain substrate processing apparatus 1, the matching property confirmation part 235 can recognize the version information of the software modules 178 installed in the system control part 100 and the unit control part 115 respectively at that time (immediately after the installation) by referring to the version management table 241. Assuming that the new software module (version: “1.0.0.3”) for chemical solution control is installed in the unit control part 115 of the substrate processing apparatus 1 having the apparatus number “8101”, for example, the matching property confirmation part 235 can recognize that the version information of the software module 178 (category: “system control”) presently installed in the system control part 100 is “1.0.0.1” and the version information of the software modules 178 (categories: “spin control” and “chemical control”) in the unit control part 115 is “1.1.0.1” and “1.0.0.3” respectively by referring to the version management table 241 shown in FIG. 16.
The hard disk 24 of the information storage server 2 stores a confirmation table 242. FIG. 17 illustrates an exemplary confirmation table 242. Referring to FIG. 17, the meanings of “system version”, “category”, “version classification” and “version” are identical to those described with reference to FIG. 16. “Release information” is a comment statement as to each system version. The confirmation table 242 is prepared every system version, and FIG. 17 shows the confirmation table 242 as to the system version “1.00”.
The confirmation table 242 is a matching property confirmation table registering version information of software modules 178 mutually having matching properties, and the hard disk 24 also functions as table holding means holding such a matching property confirmation table 242. According to the confirmation table 242 shown in FIG. 17, it is confirmed that the software modules 178 (version: “1.1.0.1” and “1.1.0.2”) of the category “spin control” and the software module 178 (version: “1.0.0.3”) of the category “chemical solution control” etc. mutually have matching properties as to the software module 178 (version: “1.0.0.1”) of the category “system control” in the system version “1.00”. At the same time, these software modules 178 mutually have matching properties also as to the software module 178 (version: “1.0.0.2”) of the category “system control”. That is, if the confirmation table 242 registers all version information of the software modules 178 installed in the system control part 100 and the unit control part 115 of a certain substrate processing apparatus 1, it follows that these software modules 178 mutually have matching properties.
In the aforementioned case of installing the new software module 178 “version:” 1.0.0.3) for the category “chemical solution control” in the unit control part 115 of the substrate processing apparatus 1 having the apparatus number “8101”, for example, the version information of the software module 178 (category: “system control”) installed in the system control part 100 of the substrate processing apparatus 1 is the version “1.0.0.1”, and the version information of the software modules 178 (categories: “spin control” and “chemical solution control” or the like) installed in the unit control part 115 is the versions “1.1.0.1” and “1.0.0.3” respectively (FIG. 16). The confirmation table 242 (system version: “1.00”) shown in FIG. 17 registers all version information of these software modules 178, and hence the matching property confirmation part 235 determines that the newly installed software module 178 (category: “chemical solution control”, version: “1.0.0.3”) matches with the software module 178 already installed in the system control part 100 and the unit control part 15.
For example, it is assumed that a new software module (version classification: “custom-built F”, version: “1.0.0.4”) of the category “chemical solution control” is installed in the unit control part 115 of the substrate processing apparatus 1 having the apparatus number “8101”. In this case, the hard disk 24 stores the version information of the software modules 178 installed in the system control part 100 and all unit control parts 115 included in the substrate processing apparatus 1 having the apparatus number “8101” at the time of the installation similarly to the above, for constructing a version management table 241 shown in FIG. 18.
In this case, the matching property confirmation part 235 refers to the version management table 241 shown in FIG. 18 thereby recognizing that the version information of the software module 178 (category: “system control”) installed in the system control part 100 is the version “1.0.0.1” and the version information of the software modules 178 (categories: “spin control” and “chemical solution control” or the like) is the versions “1.1.0.1” and “1.0.0.4” respectively. The confirmation table 242 (system version: “1.00”) shown in FIG. 17 does not register the version “1.0.0.4” of the software module 178 (category: “chemical solution control”) installed in the unit control part 115 among the version information, and hence the matching property confirmation part 235 determines that the newly installed software module 178 does not match with the software module 178 already installed in the system control part 100 and the unit control part 115.
US10189975 2001-07-05 2002-07-02 Substrate processing system managing apparatus information of substrate processing apparatus Active 2023-11-22 US7047100B2 (en)
JPP2001-205110 2001-07-01
JPP2001-205111 2001-07-01
JPP2001-205109 2001-07-01
JP2001205109A JP4071461B2 (en) 2001-07-05 2001-07-05 A substrate processing system, the substrate processing apparatus, program and recording medium
JP2001205110A JP3880814B2 (en) 2001-07-05 2001-07-05 A substrate processing system and a substrate processing apparatus management method
JP2001205111A JP2003022200A (en) 2001-07-05 2001-07-05 Substrate processing system, substrate processor, method for acquiring additional information, program, and recording medium
US11368862 US7333867B2 (en) 2001-07-05 2006-03-06 Substrate processing system managing apparatus information of substrate processing apparatus
US11368586 US7460923B2 (en) 2001-07-05 2006-03-06 Substrate processing system managing apparatus information of substrate processing apparatus
US20030023340A1 true US20030023340A1 (en) 2003-01-30
US7047100B2 true US7047100B2 (en) 2006-05-16
ID=27347093
US10189975 Active 2023-11-22 US7047100B2 (en) 2001-07-05 2002-07-02 Substrate processing system managing apparatus information of substrate processing apparatus
US11368586 Active US7460923B2 (en) 2001-07-05 2006-03-06 Substrate processing system managing apparatus information of substrate processing apparatus
US11368862 Active US7333867B2 (en) 2001-07-05 2006-03-06 Substrate processing system managing apparatus information of substrate processing apparatus
US (3) US7047100B2 (en)
KR (3) KR100542813B1 (en)
CN (1) CN1215529C (en)
US20060120716A1 (en) * 2004-12-06 2006-06-08 Dainippon Screen Mfg. Co., Ltd. Substrate processing apparatus
US20070213864A1 (en) * 2006-03-08 2007-09-13 Tokyo Electron Limited Control device and method for a substrate processing apparatus
KR101018682B1 (en) 2007-04-02 2011-03-04 가부시키가이샤 히다치 고쿠사이 덴키 Substrate processing system and group management system
JP3999649B2 (en) * 2002-12-19 2007-10-31 大日本スクリーン製造株式会社 The substrate processing apparatus and method operation, and program
JP2004280345A (en) * 2003-03-14 2004-10-07 Omron Corp Terminal board device
DE10353052A1 (en) * 2003-11-13 2005-06-16 Siemens Ag Automation system with mutually communicating components
WO2006016435A1 (en) * 2004-08-11 2006-02-16 Tokyo Electron Limited Processing system, processing method, computer readable recording medium and computer program
JP2006277298A (en) 2005-03-29 2006-10-12 Tokyo Electron Ltd Substrate processing device, history information recording method, history information recording program, and history information recording system
JP4781832B2 (en) * 2006-02-01 2011-09-28 大日本スクリーン製造株式会社 A substrate processing system, the substrate processing apparatus, program and recording medium
JP4901442B2 (en) * 2006-12-04 2012-03-21 東京エレクトロン株式会社 Trouble cause investigation support device, the trouble cause investigation support method, a storage medium for storing the program
CN105005528A (en) * 2015-06-26 2015-10-28 浪潮(北京)电子信息产业有限公司 Log information extraction method and apparatus
JPS60100806A (en) 1983-11-07 1985-06-04 Sanyo Electric Co Ltd Semiconductor integrated circuit
JPH02311939A (en) 1989-05-26 1990-12-27 Nec Corp Module updating system for work station
JPH04239301A (en) 1991-01-11 1992-08-27 Yaskawa Electric Corp Detecting method for version matching property of multi-cpu software
JPH04369050A (en) 1991-06-18 1992-12-21 Nec Corp Method for maintaining information processing terminal equipment
JPH06119400A (en) 1992-10-05 1994-04-28 Dainippon Screen Mfg Co Ltd Picture data filing device
JPH10124322A (en) 1996-10-23 1998-05-15 Dainippon Screen Mfg Co Ltd Substrate treating device
JPH10154086A (en) 1996-11-21 1998-06-09 Dainippon Printing Co Ltd Error restoration support system
JPH10304056A (en) 1997-04-22 1998-11-13 Nec Corp Exchange system maintenance operation system
JPH1161251A (en) 1997-08-11 1999-03-05 Nisshin Steel Co Ltd Production of ferrum-nickel alloy plate excellent in hot workability
KR19990054594A (en) 1997-12-26 1999-07-15 윤종용 Computer system and method with remote fault-healing capabilities
KR100211937B1 (en) 1997-08-04 1999-08-02 주일성 Remote controller supervision apparatus
KR20000047269A (en) 1998-12-31 2000-07-25 강병호 Subscriber software version confirmation system and automatic software upgrade system thereby in multimedia satellite communication system
JP2000222299A (en) 1999-02-04 2000-08-11 Toshiba Corp Fault information support system and fault information supporting method for computer
KR100484130B1 (en) 1997-12-26 2005-06-16 삼성전자주식회사 Computer system possessing the function of remote recovering its coflicts and method thereof
JP2001332472A (en) * 2000-05-19 2001-11-30 Canon Inc X-ray aligner
JP2001345248A (en) * 2000-05-31 2001-12-14 Canon Inc Aligner, method of manufacturing device, semiconductor manufacturing plant, and method for maintaining aligner
English translation of relevant portions of Japanese Patent Office Action issued Mar. 29, 2005 submitted in lieu of statement of relevancy of prior art teachings to the instant application.
Translation of Korean Patent Office's assertion regarding the relevancy of untranslated Korean application No. 0211937.
Translation of Korean Patent Office's assertion regarding the relevancy of untranslated Korean application No. 1999-54594.
Translation of Korean Patent Office's assertion regarding the relevancy of untranslated Korean application No. 2000-0047269.
Untranslated Office Action issued by the Japanese Patent Office on Apr. 13, 2004 in connection with corresponding Japanese application No. 2001-205111.
Untranslated Office Action issued by the Japanese Patent Office on Mar. 29, 2005 in connection with corresponding Japanese application No. 2001-205111.
Untranslated Office Action issued by the Korean Patent Office on Mar. 18, 2005 in connection with corresponding Korean application No. 10-2002-0035878.
Untranslated Office Action issued by the Korean Patent Office on Nov. 30, 2004 in connection with corresponding Korean application No. 10-2004-0077334.
Untranslated Office Action issued by the Korean Patent Office on Nov. 30, 2004 in connection with corresponding Korean application No. 10-2004-0077335.
Untranslated Office Action issued by the Korean Patent Office on Oct. 13, 2005 in connection with corresponding Korean application No. 10-2004-0077334.
US7512456B2 (en) * 2004-12-06 2009-03-31 Dainippon Screen Mfg. Co., Ltd. Substrate processing apparatus
US7681055B2 (en) * 2006-03-08 2010-03-16 Tokyo Electron Limited Control device and method for a substrate processing apparatus
KR100538459B1 (en) 2005-12-22 grant
US20030023340A1 (en) 2003-01-30 application
US7333867B2 (en) 2008-02-19 grant
US20060206229A1 (en) 2006-09-14 application
KR20030005002A (en) 2003-01-15 application
US7460923B2 (en) 2008-12-02 grant
CN1215529C (en) 2005-08-17 grant
CN1396625A (en) 2003-02-12 application
US20060241803A1 (en) 2006-10-26 application
KR100615974B1 (en) 2006-08-28 grant
KR20040099188A (en) 2004-11-26 application
KR20040097962A (en) 2004-11-18 application
KR100542813B1 (en) 2006-01-11 grant
US20040255191A1 (en) 2004-12-16 Automated diagnostic service
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KITAMOTO, TORU;KAMEI, KENJI;INOUE, HIDEKAZU;AND OTHERS;REEL/FRAME:013256/0285