The present invention relates to a remote maintenance system for maintaining an industrial equipment installed at a remote location.
Maintenance against a trouble in an industrial equipment requiring maintenance, such as a semiconductor device manufacturing apparatus has been made such that, upon occurrence of a trouble, maintenance personnel instruct a countermeasure to an operator for the manufacturing apparatus through telephone or facsimile communication or directly visit a factory where the manufacturing apparatus is installed. This also applies to periodical maintenance.
Along with recent increases in investment in the semiconductor industries, the number of installed production equipment increases to cause a chronic shortage in maintenance personnel. To achieve a low cost, production sites have been distributed at domestic and foreign remote locations. Under these circumstances, it becomes more difficult to provide countermeasures against troubles and periodic maintenance. The distributed production locations result in distribution of information about maintenance of manufacturing apparatuses. This makes it difficult to perform centralized management of information. The experiences of past troubles cannot be effectively utilized.
The present invention has been made in consideration of the above situation, and has as its object to immediately and efficiently perform maintenance of industrial equipment installed at remote locations.
According to the present invention, the foregoing object is attained by providing a remote maintenance system for maintaining an industrial equipment installed at a remote location, the system comprising monitor means for monitoring an operating state of one or a plurality of industrial equipment, and management means for managing maintenance of the industrial equipment while communicating information associated with maintenance of the industrial equipment with the monitor means through the internet.
Another aspect is attained by providing a monitor apparatus arranged on an industrial equipment side to constitute a remote maintenance system for maintaining an industrial equipment installed at a remote location, comprising, obtaining means for detecting occurrence of a trouble of one or a plurality of industrial equipment and obtaining status information representing a state of the trouble, and communication means for notifying, through the internet, a management apparatus for performing centralized maintenance management of the industrial equipment of status information obtained by the obtaining means, and for receiving response information sent from the management apparatus through the internet in response to notification of the status information.
In another aspect of the present invention, the foregoing object is attained by providing a management apparatus arranged on a vendor side to constitute a remote maintenance system for maintaining an industrial equipment installed at a remote location, comprising, communication means for communicating, through the internet, with each monitor means of at least one factory in which a monitor apparatus is arranged to monitor an operating state of at least one industrial equipment, and corresponding means for determining a countermeasure against a trouble on the basis of status information associated with a state of the trouble of the industrial equipment, which is received by the communication means from the monitor apparatus, and causing the communication means to notify the corresponding monitor apparatus of response information based on the determined countermeasure.
In still another aspect of the present invention, the foregoing object is attained by providing a remote maintenance method of maintaining an industrial equipment installed at a remote location, comprising the steps of, communicating, through the internet, maintenance information between a first vendor for supplying a first industrial equipment, a second vendor for supplying a second industrial equipment, a first factory in which the first and second industrial equipments are installed, and a second factory in which the first and second industrial equipments are installed, causing the first vendor to perform centralized maintenance management of the first industrial equipments installed in the first and second factories, and causing the second vendor to perform centralized maintenance management of the second industrial equipments installed in the first and second factories.
Further objects, features and advantages of the present invention will be apparent from the following description of embodiments of the present invention with reference to be accompanying drawings.
Reference numerals 102 to 104 denote production factories of at least one semiconductor manufacturing maker serving as the user of industrial equipments. That is, the production factories 102 to 104 may belong to different makers or one maker (e.g., preprocessing and postprocessing factories).
A plurality of industrial equipments 106, a LAN (intranet) 109 for connecting these equipments 106, and a host computer 107 serving as a monitor apparatus for monitoring the operating states of the respective industrial equipments 106 are arranged in each of the factories 102 to 104.
The host computer 107 in each of the factories 102 to 104 is connected to a host computer 108 serving as the management apparatus on a vendor 101 side through the internet 105 serving as a worldwide communication means. The host computer 107 notifies status information (e.g., the state of the corresponding industrial equipment in trouble) representing the operating state of the corresponding industrial equipment 106 from the factory side to the vendor side. At the same time, the host computer 107 receives response information (e.g., information for instructing a countermeasure against the trouble, or a countermeasure program or its data) from the vendor side in response to the above notification. The status information and/or the response information will be referred to as maintenance information thereinafter.
In communication between the factories 102 to 104 and the vendor 101 and LAN communication in each factory, a packet communication protocol (TCP/IP) generally used in the internet is used.
The host computer 108 on the vendor 101 side can instantaneously grasp the operating states of the industrial equipments 106 in the user factories 102 to 104 through the internet 105. The maintenance information representing the operating state and the maintenance state can be looked up from computers in other departments of the vendor 101, e.g., computers 110 in the manufacturing department and the department of development in addition to the department of maintenance. The maintenance information can be fed back to the manufacturing department and the department of development.
In the flow chart of
Each industrial equipment 106 has a function of notifying the corresponding host computer 107 of the presence/absence of a trouble in response to a request from the host computer 107 (corresponding to step S203), and a function of specifying the contents of the trouble and notifying the host computer 107 of the status information (e.g., an error code representing the contents of the trouble) representing the specified contents (corresponding to step S204).
In step S205, the status information notified from the host computer 107 to the vendor 101 side contains, e.g., the model of the industrial equipment in trouble, the serial number, the error code, and trouble occurrence time. The corresponding relationship between the error code and the contents of the trouble can be spontaneously updated from the host computer 108 of the vendor 101 side through the internet 105.
If the contents of a trouble are not registered in advance, an error code representing this may be contained in the status information. In this case, the operator can notify the vendor side of detailed information by means of telephone, facsimile, or E-mail.
The host computer 108 serving as the management apparatus on the vendor 101 side waits for communication from the host computer 107 in each factory for, e.g., 24 hours.
The host computer 108 on the vendor 101 side periodically executes processing represented by the flow chart in
First, the host computer 108 monitors whether the report of a trouble is present (step S302). If YES in step S302, the host computer 108 obtains status information about this report (step S303). The host computer 108 looks up the trouble database (DB) for managing the maintenance of the industrial equipments of each factory on the basis of this status information. The host computer 108 checks whether the same trouble state as the currently reported trouble state for the same industrial equipment has occurred in the past, i.e., whether the same trouble state is registered in the trouble database (501 to be described later) (step S304).
If the same trouble state is registered in the trouble database (“YES” in step S304), it is determined whether a countermeasure against this trouble state is registered (step S306). If YES in step S306, the host computer 108 notifies the host computer 108, in the factory which has reported the trouble, of response information about the registered countermeasure (e.g., code information or message representing the countermeasure, a countermeasure program, or its data) through the internet 105 (step S307).
Upon reception of the response information, the host computer 107 on the factory side automatically restores the industrial equipment in trouble to a normal state, if possible. When such automatic restoration is impossible, the host computer 107 outputs a message to, e.g., a display for the operator of the industrial equipment in trouble.
The host computer 108 reports, to a person in charge on the vendor 101 side, the fact of occurrence of the trouble, the contents of the trouble (status information), the presence/absence of notification of the countermeasure (response information), the current state, and any other associated information. This report is displayed on the display of the computer 110 and made by automatically transmitting an E-mail from the host computer 108 to the mail address of the person in charge on the vendor side.
If it is determined in step S304 that the same trouble state as the currently reported trouble state is not registered in the trouble database, this trouble state is newly registered in the trouble database (step S305), and then step S308 is executed.
When the report to the operator is complete (step S308), the host computer 108 updates the trouble database (step S309). By this updating, the presence/absence of transmission of the countermeasure (response information), trouble report reception time, and the like are registered in the trouble database.
If, however, a countermeasure is required (i.e., “YES” in step S402), the person in charge selects an appropriate countermeasure by looking up the information stored in the trouble database (step S403).
As a countermeasure policy, the trouble can be eliminated on-line through the internet 105 (step S407). As an example, the trouble may be caused by a software error. In this case, the parameters and program in the memory of the industrial equipment in trouble may be corrected on-line through the internet 105 and the host computer 107 on the factory side.
As another countermeasure policy, a method of eliminating the trouble may be instructed to the operator by means of E-mail, facsimile, telephone, or the like (step S406).
For a serious trouble which cannot be eliminated by the methods in steps S406 and S407, the person in charge visits the factory to eliminate the trouble (step S405).
When the countermeasure is complete, the person in charge operates the host computer 108 or the computer 110 to update the trouble database on the basis of the information associated with this trouble (step S408).
The trouble database in the host computer 108 on the vendor 101 side will be described below. Dedicated or general-purpose browser software is installed in each computer 110 connected to the host computer 108 through the LAN 109 and the console of the industrial equipment 106 of each factory connected through the internet, thereby constituting, e.g., the user interface window shown in
The operator on the vendor or factory side can input information such as the model (401) of the industrial equipment, the serial number (402), the case of trouble (403), the date of trouble occurrence (404), the emergency degree (405), the trouble state (406), the countermeasure (407), and progress (408). Note that information may be automatically input to the trouble database by the host computer 108, as described above.
The browser software of the window shown in
As described above, the worker in each department on the vendor 101 side, such as the department of maintenance, the manufacturing department, and the department of development can access the trouble database by using the computer 110 connected to the host computer 108 through the LAN 109. The outside maintenance personnel can also access the trouble database by using a portable terminal through the internet 105. Therefore, the information of the respective departments of the vendor can be centralized and managed, and each department can always access the latest information.
Information as part of the trouble database can be disclosed to users (factories), and each user can access various kinds of past maintenance information through the internet and employs an appropriate countermeasure against his own trouble. As described above, in this embodiment, the maintenance information can be shared by the vendor and the plurality of users to remarkably improve the maintenance efficiency.
This embodiment also comprises a communication security system for inhibiting the third party from accessing confidential information from the trouble database through the internet.
This system has a fire wall to perform validation using a password, and a computer which is allowed to access the database is registered in the host computer 108 of the vendor 101 in advance, thereby inhibiting access by a computer other than the registered computers.
In the system of this embodiment, as described above, the internet serving as the exiting infrastructure and its communication protocol, and internet access software are used to communicate maintenance information of the industrial equipments. For this reason, loads on installation of dedicated communication lines and development of new software can be reduced, and a high-speed, low-cost remote maintenance system can be constructed.
The plurality of factories in which the industrial equipments are installed are connected to the vendor management system through a communicating means to perform centralized management of maintenance information and share the information. The experiences of the past troubles can be utilized beyond the production sites, thereby immediately coping with troubles. In particular, when maintenance information is shared by different business enterprises as users, the efficiency of the whole industry can be improved.
Referring to
In this system, when a trouble has occurred in one of the series of production equipments on the production line, the operation of the production line stops. Remote maintenance is received from the vendor for the equipment in trouble through the internet 200 to immediately cope with the trouble, thereby minimizing the stop period of the production line. The host management system of each vendor has a trouble database as described with reference to the first embodiment. Maintenance information is stored in this trouble database. Different communication security systems are used between the production factory and different vendors to prevent leakage of information. The detailed maintenance contents and method are identical to those of the first embodiment, and a detailed description thereof will be omitted.
As described above, in the system of this embodiment, a plurality of factories of one or a plurality of users, which have industrial equipments of the plurality of vendors on the production line are connected to the management systems of the respective vendors to communicate maintenance information. Even if a given equipment during production gets in trouble, immediate maintenance can be received from the corresponding vendor. The line stop time can be minimized to improve the production efficiency. In particular, when maintenance information is shared by different users, different business enterprises, or different vendors, the efficiency of the whole industry can be improved.
A semiconductor device production method in a facility using the above-described remote maintenance system will be described below.
As has been described above, according to the present invention, the worldwide internet is used as the remote maintenance communication means for the industrial equipments to allow construction of an effective maintenance system with less capital investment regardless of the installation locations of the equipments.
The user factories in which industrial equipments are installed are connected to the vendor management systems through the communicating means to immediately cope with troubles. In addition, when the maintenance information is shared, the maintenance capability can be expected to be improved.
The present invention is not limited to the above embodiments and various changes and modifications can be made within the spirit and scope of the present invention. Therefore, to apprise the public of the scope of the present invention the following claims are made.
Number | Date | Country | Kind |
---|---|---|---|
8-202057 | Jul 1996 | JP | national |
8-251623 | Sep 1996 | JP | national |
9-167233 | Jun 1997 | JP | national |
This application is a continuation of application Ser. No. 11/117,455, filed Apr. 29, 2005, now U.S. Pat. No. 7,062,343, which issued Jun. 13, 2006, which is a divisional of application Ser. No. 09/988,573, filed Nov. 20, 2001, now U.S. Pat. No. 6,963,786, which issued Nov. 8, 2005, which is a divisional of application Ser. No. 08/902,160, filed Jul. 29, 1997, now U.S. Pat. No. 6,385,497, which issued May 7, 2002, the contents all of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
4390953 | Johnstone | Jun 1983 | A |
4517468 | Kemper et al. | May 1985 | A |
4847795 | Baker et al. | Jul 1989 | A |
5212645 | Wildes et al. | May 1993 | A |
5225997 | Lederer et al. | Jul 1993 | A |
5243377 | Umatate et al. | Sep 1993 | A |
5245554 | Tsuyama et al. | Sep 1993 | A |
5299027 | Nakamura et al. | Mar 1994 | A |
5311562 | Palusamy et al. | May 1994 | A |
5315711 | Barone et al. | May 1994 | A |
5350547 | Yamaguchi et al. | Sep 1994 | A |
5351247 | Dow et al. | Sep 1994 | A |
5383113 | Kight et al. | Jan 1995 | A |
5432715 | Shigematsu et al. | Jul 1995 | A |
5458732 | Butler et al. | Oct 1995 | A |
5461570 | Wang et al. | Oct 1995 | A |
5483530 | Davis et al. | Jan 1996 | A |
5533093 | Horton et al. | Jul 1996 | A |
5544320 | Konrad | Aug 1996 | A |
5591299 | Seaton et al. | Jan 1997 | A |
5594663 | Messaros et al. | Jan 1997 | A |
5610689 | Kamiya et al. | Mar 1997 | A |
5619307 | Machino et al. | Apr 1997 | A |
5680521 | Pardo et al. | Oct 1997 | A |
5689589 | Gormish et al. | Nov 1997 | A |
5691895 | Kurtzberg et al. | Nov 1997 | A |
5694325 | Fukuda et al. | Dec 1997 | A |
5696686 | Sanka et al. | Dec 1997 | A |
5696901 | Konrad | Dec 1997 | A |
5710700 | Kurtzberg et al. | Jan 1998 | A |
5724511 | Moritomo | Mar 1998 | A |
5726920 | Chen et al. | Mar 1998 | A |
5761064 | La et al. | Jun 1998 | A |
5802176 | Audebert | Sep 1998 | A |
5832126 | Tanaka | Nov 1998 | A |
5835726 | Shwed et al. | Nov 1998 | A |
5872915 | Dykes et al. | Feb 1999 | A |
5897493 | Brown | Apr 1999 | A |
5923247 | Dowden et al. | Jul 1999 | A |
5950150 | Lloyd et al. | Sep 1999 | A |
5951611 | La Pierre | Sep 1999 | A |
5963444 | Shidara et al. | Oct 1999 | A |
5963884 | Billington et al. | Oct 1999 | A |
5974444 | Konrad | Oct 1999 | A |
5984498 | Lem et al. | Nov 1999 | A |
5995916 | Nixon et al. | Nov 1999 | A |
6125390 | Touboul | Sep 2000 | A |
6185546 | Davis | Feb 2001 | B1 |
6226752 | Gupta et al. | May 2001 | B1 |
6728660 | Bjornson | Apr 2004 | B2 |
6785623 | Higgins | Aug 2004 | B2 |
6853959 | Ikeda et al. | Feb 2005 | B2 |
20020022969 | Berg et al. | Feb 2002 | A1 |
20020049053 | Nomura et al. | Apr 2002 | A1 |
20040176868 | Haga et al. | Sep 2004 | A1 |
Number | Date | Country |
---|---|---|
19506764 | Aug 1995 | DE |
0051861 | May 1982 | EP |
2688643 | Sep 1993 | FR |
01-155799 | Jun 1989 | JP |
02-277396 | Nov 1990 | JP |
04-028238 | Jan 1992 | JP |
5-73745 | Mar 1993 | JP |
05-143611 | Jun 1993 | JP |
07-128098 | May 1995 | JP |
08-036415 | Feb 1996 | JP |
08-037157 | Feb 1996 | JP |
08-129497 | May 1996 | JP |
8-161200 | Jun 1996 | JP |
08-115125 | Jul 1996 | JP |
63-166211 | Jul 1998 | JP |
Number | Date | Country | |
---|---|---|---|
20060282188 A1 | Dec 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09988573 | Nov 2001 | US |
Child | 11117455 | US | |
Parent | 08902160 | Jul 1997 | US |
Child | 09988573 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11117455 | Apr 2005 | US |
Child | 11438440 | US |