Abstract:
The facility monitor ( 670 ) is used to monitor and collect measured parameter data and alarm status data for a facility ( 615 ), such as a semiconductor processing facility. A graphical user interface (GUI) is used for monitoring the current status ( 625 ) and accessing the system history of the facility ( 645 ). The GUI provides easily readable screens where the graphical display is organized so that the measured parameter data is logically presented to the user, alarm status data are clearly indicated to the user, and the user can efficiently review the data and respond.

Description:
CROSS-REFERENCE TO RELATED APPLICATION  
       [0001]    The present application claims priority to U.S. provisional application serial No. 60/315,342, filed on Aug. 29, 2001, the entire contents of which are herein incorporated by reference. 
     
    
     
       BACKGROUND OF THE INVENTION  
         [0002]    1. Field of the Invention  
           [0003]    The invention relates generally to a method and apparatus for monitoring a local or remote facility (e.g., a facility used in a semiconductor fabrication process). More particularly, the invention relates to a graphical user interface for facility monitoring.  
           [0004]    2. Background of the Invention  
           [0005]    Maintaining a semiconductor-processing facility is a time consuming and expensive procedure. The inefficient monitoring of a facility can result in facility downtimes that add to the overall operational cost.  
           [0006]    Generally, facility control is performed by a number of different control systems having a variety of controllers. Some of the control systems may have man-machine interfaces such as touch panel displays, others may only display readings such as temperature. In addition, facility monitoring is usually time consuming and requires manual entry of data. Facility monitoring also includes recording and responding to problems. Oftentimes, the response time for dealing with problems is lengthened because of a lack of data or lack of personnel trained to respond to a particular problem. This can lead to significant facility down time and the subsequent loss of processing time.  
           [0007]    What is needed is an efficient way to monitor a semiconductor-processing facility to reduce facility down times.  
         BRIEF SUMMARY OF THE INVENTION  
         [0008]    It is an object of the present invention to provide a method and apparatus for monitor a semiconductor-processing facility to reduce facility down times. In one aspect of the invention, a facility monitoring system for monitoring a facility is described wherein the system includes (1) a facility monitor coupled to said facility, said facility monitor receiving monitored parameter data and alarm status data from said facility; (2) a user interface coupled to said facility monitor; and (3) an external interface coupled to said facility monitor.  
           [0009]    In one aspect of the invention, the facility monitor further includes memory for storing the monitored parameter data and the alarm status data.  
           [0010]    In another aspect of the invention, the user interface includes a first graphical user interface (GUI) providing a facility monitor logger status screen and a plurality of facility monitor logger history screens.  
           [0011]    In an additional aspect of the invention, the external interface includes a dial-in service, a paging service, and/or an internet service.  
           [0012]    Additional objects and advantages of the invention will be set forth in the description which follows, and in part will be evident from the description, or may be learned by practice of the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out hereinafter or by other instrumentalities and combinations. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0013]    The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate presently preferred embodiments of the invention, and together with the general description given above and the detailed description of the preferred embodiments given below, serve to explain the principles of the invention.  
         [0014]    [0014]FIG. 1 is a simplified block diagram showing a facility monitoring system according to a preferred embodiment of the present invention;  
         [0015]    [0015]FIG. 2 shows an exemplary view of a Facility Monitor Logger Status Screen and displays information to be selected by a user;  
         [0016]    [0016]FIG. 3 shows an exemplary view of the monitored status display area of a Facility Monitor Logger Status Screen and displays information to be selected by a user;  
         [0017]    [0017]FIG. 4 shows an exemplary view of the alarm status display area of a Facility Monitor Logger Status Screen and displays information to be selected by a user;  
         [0018]    [0018]FIG. 5 shows an exemplary view of a Facility Monitor Logger History Screen displaying a Facility Monitor Logger Graph Display for a process being monitored at a facility;  
         [0019]    [0019]FIG. 6 illustrates a simplified flow diagram for a method of operating a Facility Monitor Logger GUI in accordance with a preferred embodiment of the invention;  
         [0020]    [0020]FIG. 7 illustrates a simplified flow diagram for a method of operating a Facility Monitor Logger GUI in accordance with a preferred embodiment of the invention.  
         [0021]    [0021]FIG. 8 illustrates a computer for implementing either one of a remote facility monitor and a data gathering computer. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0022]    Embodiments of the present invention will be described hereinafter with reference to the accompanying drawings. In the following description, the constituent elements having substantially the same function and arrangement are denoted by the same reference numerals, and repetitive descriptions will be made only when necessary.  
         [0023]    [0023]FIG. 1 is a simplified block diagram showing a facility monitoring system according to a preferred embodiment of the present invention. Facility monitoring system  100  includes a facility monitor  120 , a user interface  130 , and an external interface  140 .  
         [0024]    Facility monitoring system  100  is coupled to facility  110 . Facility monitor  120  is coupled to facility  110 , user interface  130 , and external interface  140 . Facility monitor  120  includes software and hardware means for communicating  115  with facility  110 , for communicating  135  with user interface  130 , and for communicating  145  with external interface  140 .  
         [0025]    In a preferred embodiment, system components communicate with each other using TCP/IP compatible networks. The data passed over the TCP/ IP compatible networks is encrypted and uniquely identified. For example, TCP/IP compatible networks can include an intranet, a virtual private network (VPN), and the internet.  
         [0026]    In a preferred embodiment, facility  110  includes a plurality of sensors and alarms located throughout facility  110 . Exemplary sensors include facility indicators (not shown), scrubber indicators (not shown), gas system sensors (not shown), processing tool sensors (not shown), and alarm indicators (not shown). Facility  110  provides monitored parameter data and alarm status data to facility monitor  120 . In an alternate embodiment, facility monitor can provide additional measured data.  
         [0027]    Facility monitor  120  includes hardware and software elements (not shown) for monitoring and storing the monitored parameter data and alarm status data from facility  110 . The monitored parameter data provides facility readings for facility  110  and system status for the systems (not shown) in facility  110 . For example, the hardware can include a computer, memory, video display, mouse and keyboard, and the software can include an operating system.  
         [0028]    Facility monitor  120  also includes a database (not shown) for collecting the monitored parameter data and alarm status data. In a preferred embodiment, the database is a Structured Query Language (SQL) database and additional memory space and/or disk storage is provided for the SQL database.  
         [0029]    In a preferred embodiment, facility monitor  120  comprises facility monitor logger  122  and facility monitor viewer  124 . Facility monitor logger  122  and facility monitor viewer  124  comprise computational resources and operational software. Facility monitor logger  122  is coupled to the database and includes software and/or hardware to read from and write to the database. Facility monitor viewer  124  is coupled to the database and comprises means to read from the database.  
         [0030]    In a preferred embodiment, facility monitor logger  122  includes software that is installed onto a computer in a network of computational resources. Desirably, the installation of the software on a computer causes an icon to be displayed on the computer&#39;s display. For example, double-clicking the icon can cause the software to begin executing. Desirably, a facility monitor logger computer can obtain data from one or more data collection computers.  
         [0031]    In a preferred embodiment, facility monitor viewer  124  includes software that is installed onto several computers in a network of computational resources. Desirably, the installation of the software on a computer causes an icon to be displayed on the computer&#39;s display. For example, double-clicking the icon can cause the software to begin executing. Desirably, a facility monitor logger computer, acting as a server, sends out updates to other facility monitor viewer computers, acting as monitors. For example, data can be sent every five seconds.  
         [0032]    In a preferred embodiment, a splash screen is displayed and the computer&#39;s clock is synchronized. In addition, the computer program is coupled to the database . In a preferred embodiment, user interface  130  comprises a display device (e.g., a monitor, a TV or a flat panel display) (not shown in FIG. 1) that provides a graphical user interface (GUI). In addition, user interface  130  comprises input devices (not shown in FIG. 1) (e.g., a mouse and/or a keyboard).  
         [0033]    User interface  130  includes a graphical user interface (GUI) on a computer. In a preferred embodiment, the GUI includes a facility monitor logger status screen for monitoring the current status of facility  110  and a plurality of facility monitor logger history screens for accessing the system history of facility  110 .  
         [0034]    In addition, the GUI includes a facility monitor viewer status screen for monitoring the current status of facility  110  and a plurality of facility monitor viewer history screens for accessing the system history of facility  110 . The facility monitor logger status screen also provides a graphical view of the data that is currently being stored.  
         [0035]    In a preferred embodiment, the GUI is presented to the user on a video display such as a computer monitor, and the uses interacts with the GUI using an input device such as a keyboard or a mouse.  
         [0036]    In a preferred embodiment, external interface means  140  includes a dial-in service, although any other network adapter using an error checking and retransmission protocol (e.g., TCP/LP) can be used. The dial-in service allows a user to access database  130  via a telephone line and provides limited access to the data in database  130 . Desirably, the dial-in service requires the user to input an authorization code (e.g., a PIN number or a password) before gaining access. For example, when a correct PIN number has been entered, the caller can hear the current status for the gas system sensors, facility indicators, scrubber indicators, and alarm status.  
         [0037]    In alternate embodiments, the PIN numbers can be used to provide different menus to different users. For example, various menus can be used to provide alarm statuses in different formats.  
         [0038]    In a preferred embodiment, external interface means  140  includes a one-way paging service. The paging service allows users to be notified via wireless devices having receiving capabilities. For example, a wireless device can be a one-way pager, a cellular phone, or other computing device having a wireless receiver and display. The one-way paging service provides the user with a limited amount of data from database  130  via a wireless connection.  
         [0039]    Desirably, a facility manager&#39;s pager is sent a first set of messages, a facility engineer&#39;s pager is sent a second set of messages, and a facility technician&#39;s pager is sent a third set of messages.  
         [0040]    In an alternate embodiment, external interface means  140  includes a two-way paging service. The two-way paging service can allow users to be notified via wireless devices having receiving and transmitting capabilities. For example, a wireless device can be a two-way pager, a cellular phone, or other computing device having a wireless receiver, transmitter, user interface, and display. The two-way paging service can provide the user with a limited amount of data from database  130  via a wireless connection and can provide limited access to the data in database  130 . Desirably, the two-way paging service would require the user to input a PIN number before gaining access. For example, when a correct PIN number has been entered, the user could receive the current status for the gas system sensors, facility indicators, scrubber indicators, and alarm status. Authorized users may ‘restart’, ‘shutdown’, and EMO the facility.  
         [0041]    In alternate embodiments, the PIN numbers can be used to provide different menus to different users. For example, various menus can be used to provide alarm statuses in different formats to different wireless devices.  
         [0042]    [0042]FIG. 2 shows an exemplary view of a Facility Monitor Logger Status Screen and displays information to be selected by a user. Facility Monitor Logger Status Screen  200  includes title bar  205 , monitored parameter data display area  210 , corporate logo  215 , control boxes ( 220 ,  230 ,  235 ,  240 ,  245 , and  250 ), time stamp  225 , and alarm status display area  260 .  
         [0043]    As shown in FIG. 2, control boxes include program control box  220 , first bay selection button  230 , second bay selection button  235 , bay selection display  240 , close button  245 , and page button  250 .  
         [0044]    Program control box  220  allows a user to select the data viewer software or the data logger software. The name of the software selected is displayed in program control box  220 .  
         [0045]    First bay selection button  230  and second bay selection button  235  allow a user to select the first bay or the second bay for displaying. The bay selected is displayed in bay selection display  240 . Alternately, a combination box or a drop down list can be used for bay selection.  
         [0046]    Close button  245  provides a user with a means for closing the GUI screen currently being displayed.  
         [0047]    Page button  250  provides a user with a means for sending a page. In a preferred embodiment, a drop-down list of pagers is provided, and the user selects one or more pagers from the list. Pages are sent to the selected pagers.  
         [0048]    [0048]FIG. 3 shows an exemplary view of the monitored status display area of a Facility Monitor Logger Status Screen and displays information to be selected by a user.  
         [0049]    Monitored status display area  300  includes a first display area  302 , which includes first status data button  304  and second status data button  306 . Activating the first status data button  304  or second status data button  306  causes a Facility Monitor Logger History Screen to be displayed. An exemplary view of a Facility Monitor Logger History Screen is shown in FIG. 5. Can be any monitored parameter vs time, clean room temp is just an example.  
         [0050]    As shown in FIG. 3, first display area  302  is labeled “Labs”, first status data button  304  is labeled “Ar”, and second status data button  306  is labeled “O2”. Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for the “Ar” status, when the “Ar” button is double-clicked, or the “O2” status, when the “O2” button is double-clicked.  
         [0051]    Monitored status display area  300  further includes a first facility sensor data button  310  and display box  312 , second facility sensor data button  314  and display box  316 , third facility sensor data button  318  and display box  320 , fourth facility sensor data button  322  and display box  324 .  
         [0052]    In a preferred embodiment, first facility sensor data button  310  is labeled “Server Room Temperature” and display box  312  shows the current value of the Server Room Temperature. Second facility sensor data button  314  is labeled “Server Room RH %” and display box  316  shows the current value of the Server Room relative humidity in percent. In addition, third facility sensor data button  318  is labeled “Clean Room Temperature” and display box  320  shows the current value of the Clean Room Temperature, and fourth facility sensor data button  322  is labeled “Clean Room RH %” and display box  324  shows the current value of the Clean Room relative humidity in percent.  
         [0053]    Activating first facility sensor data button  310 , second facility sensor data button  314 , third facility sensor data button  318 , or fourth facility sensor data button  322  causes a Facility Monitor Logger History Screen to be displayed.  
         [0054]    In a preferred embodiment, Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for the “Server Room Temperature” status, when the “Server Room Temperature” button is double-clicked, the “Server Room Relative Humidity” status, when the “Server Room Relative Humidity” button is double-clicked, the “Clean Room Temperature” status, when the “Clean Room Temperature” button is double-clicked or the “Clean Room Relative Humidity” status, when the “Clean Room Relative Humidity” button is double-clicked.  
         [0055]    Also, monitored status display area  300  further includes a second group  330  of data buttons and display boxes. Second group  330  comprises data button  326 , data button  332  and associated display box  334 , data button  336  and associated display box  338 , data button  340 , data button  342 , data button  344 , data button  346 , and data button  348 .  
         [0056]    As shown in FIG. 3, second group  330  is labeled “Scrubber”. Data button  326  is labeled “Fan” and shows the current operational status for the scrubber fan. The current operational status is shown using colors. Data button  332  is labeled “PH” and associated display box  334  shows the current value of the scrubber PH, data button  336  is labeled “Temp” and associated display box  338  shows the current value of the scrubber temperature. Data button  340  is labeled “H20 Pump”, data button  342  is labeled “Drain Closed”, data button  344  is labeled “Acid Pump”, data button  346  is labeled “Fresh H2O”, and data button  348  is labeled “H2O Mix”.  
         [0057]    Activating data button  336 , data button  340 , data button  342 , data button  344 , data button  346 , or data button  348  causes a Facility Monitor Logger History Screen to be displayed.  
         [0058]    In a preferred embodiment, Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for the “Scrubber PH” status, when the “PH” button is double-clicked, the “Scrubber Temperature” status, when the “Temp” button is double-clicked, the “H20 Pump” status, when the “H20 Pump” button is double-clicked, the “Drain” status, when the “Drain Closed” button is double-clicked, the “Acid Pump” status, when the “Acid Pump” button is double-clicked, the “Fresh Water” status, when the “Fresh H2O” button is double-clicked, or the “Fresh Water Mixture” status, when the “H2O Mix” button is double-clicked.  
         [0059]    Furthermore, monitored status display area  300  further includes data button  350  and data button  352 . As shown in FIG. 3, data button  350  is labeled “AH Fan” and data button  352  is labeled “Process Loop H2O”. Activating data button  350  or data button  352  causes a Facility Monitor Logger History Screen to be displayed. In a preferred embodiment, Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for the “AH Fan, when the “AH Fan” button is double-clicked, or the “Process Loop H2O” status, when the “Process Loop H2O” button is double-clicked.  
         [0060]    In addition, monitored status display area  300  further includes a third group  360  of data buttons and display boxes. Third group  360  includes data button  364  and associated display boxes ( 362 ,  366 ), data button  370  and associated display boxes ( 368 ,  372 ), data button  376  and associated display boxes ( 374 ,  378 ), data button  382  and associated display boxes ( 380 ,  384 ), and data button  388  associated display boxes ( 386 ,  390 ). Alternately, display boxes  366 ,  372 ,  378 ,  382 , and  390  can be eliminated.  
         [0061]    As shown in FIG. 3, third group  360  is labeled “MST [ppm]”. Display box  362  is labeled “Assembly” and associated display box  364  shows the current value of the gas flow rate in the Assembly. Display box  368  is labeled “Gas Cab” and associated display box  370  shows the current value of the gas flow rate in the Gas Cabinet. Display box  374  is labeled “Hallway” and associated display box  376  shows the current value of the gas flow rate in the “Hallway”. Display box  380  is labeled “Pump Alley” and associated display box  382  shows the current value of the gas flow rate in the Pump Alley. Display box  386  is labeled “Tool” and associated display box  388  shows the current value of the gas flow rate in the Tool.  
         [0062]    Activating data button  364 , data button  370 , data button  376 , data button  382 , or data button  388  causes a Facility Monitor Logger History Screen to be displayed. Alternately, display boxes can be used to cause Facility Monitor Logger History Screens to be displayed.  
         [0063]    In a preferred embodiment, Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for the “Assembly gas flow” status, when button  364  is double-clicked, the “Gas Cabinet gas flow” status, when button  370  is double-clicked, the “Hallway gas flow” status, when button  376  is double-clicked, the “Pump Alley gas flow” status, when button  382  is double-clicked, or the “Tool gas flow” status, when button  388  is double-clicked.  
         [0064]    In addition, monitored status display area  300  further includes corporate logo display area  394 . In an alternate embodiment, a help screen can be displayed when corporate logo display area is double-clicked.  
         [0065]    [0065]FIG. 4 shows an exemplary view of the alarm status display area of a Facility Monitor Logger Status Screen and displays information to be selected by a user. Alarm status display area  400  includes first display area  402 , second display area  404 , third display area  406 , and fourth display area  408 .  
         [0066]    First display area  402  includes data buttons  410 - 425 . Selecting any one of data buttons  410 - 425  causes a corresponding Facility Monitor Logger History Screen to be displayed. In a preferred embodiment, Facility Monitor Logger History Screen includes a Facility Monitor Logger Graph Display for at least one of the processes being monitored in first display area  402 .  
         [0067]    As shown in FIG. 4, data button  410  is labeled “Dist Rack EMO”, data button  411  is labeled “Chiller EMO”, data button  412  is labeled “Gas Box EMO”, data button  413  is labeled “Gas Cab EMO”, data button  414  is labeled “K8 Rack EMO”, data button  415  is labeled “Facility Scrub EMO”, data button  416  is labeled “Inert Exh Fan EMO”, data button  417  is labeled “Proc Exh EMO”, data button  418  is labeled “Proc 1 Excess Flow”, data button  419  is labeled “Proc 2 Excess Flow”, data button  420  is labeled “He Excess Flow”, data button  421  is labeled “O2 Excess Flow”, data button  422  is labeled “Ar Excess Flow”, data button  423  is labeled “Excess Flow 6”, data button  424  is labeled “Excess Flow 7”, and data button  425  is labeled “AN2 Over Pressure”. Clearly other buttons are possible.  
         [0068]    In a preferred embodiment, tile history status of the sensor or equipment corresponding to a button is displayed when the respective button of buttons  410 - 425  are pressed.  
         [0069]    Similarly, second display area  404  includes data buttons  430 - 435 ; third display area includes data buttons  450 - 465 ; and fourth display area includes data buttons  470 - 485 . Selecting any one of those buttons causes a Facility Monitor Logger History Screen to be displayed for the corresponding sensor or equipment.  
         [0070]    [0070]FIG. 5 shows an exemplary view of a Facility Monitor Logger History Screen displaying a Facility Monitor Logger Graph Display for a process being monitored at a facility. Facility Monitor Logger History Screen  500  includes a title bar  505 , display area  510 , monitored value name  515 , x-axis  520 , y-axis  525 , date window  530 , time window  535 , time selection buttons  540 , first operation button  545 , second operation button  550 , and corporate logo display area  555 .  
         [0071]    In a preferred embodiment, one screen  500  is displayed at one time. In alternate embodiments, multiple screens can be displayed at one time. For example, multiple screens can be overlaid or paneled.  
         [0072]    Display area  510  provides a graphical representation of one of the monitored values over a given time period. For example, monitored temperatures can be graphically displayed as shown in FIG. 5.  
         [0073]    Monitored value name  515  provides a description of the monitored value currently being graphically displayed. For example, monitored value name  515  can be Computer Room Temperature as shown in FIG. 5.  
         [0074]    X-axis  520  displays time in different manners. Time selection buttons  540  are used to determine the time scale for viewing. In a preferred embodiment, time selection buttons are provided for four hours, eight hours, and twenty-four hours. The selected button is highlighted on the screen. In alternate embodiment, other time selection buttons can be provided.  
         [0075]    Y-axis  525  displays a range based on the monitored values to be displayed. For example, when temperature is being displayed Y-axis  525  units are degrees.  
         [0076]    Date window  530  displays the day, month, and year for the monitored value currently being graphically displayed. In a preferred embodiment, date window  530  allows dates to be scrolled forward and backward by day.  
         [0077]    Time window  535  displays the starting time, using hours, minutes, and seconds, for the monitored value currently being graphically displayed. In a preferred embodiment, time window  535  allows time to be scrolled forward and backward by the time increment selected by one of the time selection buttons  540 .  
         [0078]    First operation button  545  is used to display a new graph after a new time or a new date is selected. Second operation button  550  is used to return to the Facility Monitor Logger Status Screen.  
         [0079]    [0079]FIG. 6 illustrates a simplified flow diagram for a method of operating a facility monitor logger GUI in accordance with a preferred embodiment of the invention.  
         [0080]    Procedure  600  starts in step  605 .  
         [0081]    In step  610 , a facility is determined and the facility monitor logger is initialized. In a preferred embodiment, the facility to be monitored is determined using input data from the user. For example, the user determines that the facility to be monitored is a research laboratory having a specific set of systems to be monitored. The specific set of systems to be monitored arc used to configure the facility monitor logger status screen.  
         [0082]    In step  615 , a timer is set. In a preferred embodiment, time is synchronized using a global time standard that is accessed via the Internet. Files are saved with a time stamp.  
         [0083]    In step  620 , the file name is compared. In a preferred embodiment, the file name includes date information that is used to compare files. The comparison determines if the file being accessed has the proper date. If the current file is not the required file then a new file is created with the proper name.  
         [0084]    In step  625 , a query is performed to determine when the date is current. When the date is current, procedure  600  branches to step  635 . When the date is not current, procedure  600  branches to step  630 .  
         [0085]    In step  630 , the file name is changed. In a preferred embodiment, data logger is not allowed to overwrite previously stored data. A new file is created each day.  
         [0086]    In step  635 , an interlock check is made. In a preferred embodiment, data is obtained for the current status for all of the monitored interlocks and the current status is displayed on the GUI screen.  
         [0087]    In step  640 , the data file is time stamped. In step  645 , the data file is transmitted to the SQL server database. In step  655 , a query is performed to determine when to open a graph. When a graph is to be opened, procedure  600  branches to step  660 . When the graph is not to be opened, procedure  600  branches to step  665 . In a preferred embodiment, a user can elect to view a graph by selecting one of the data buttons being displayed.  
         [0088]    In step  660 , a graphical display is presented based on the selected data button. In a preferred embodiment, the graphical display can be closed by selecting the “close” button (for example, button  550 , FIG. 5).  
         [0089]    In step  665 , a query is performed to determine when to stop the timer. When the timer is to be stopped, procedure  600  branches to step  670 . When the timer is not to be stopped, procedure  600  branches to step  620 . In a preferred embodiment, a user can elect to stop the data monitoring process by selecting one of the data buttons being displayed. For example, the user can select the “Close” button.  
         [0090]    In step  670 , procedure  600  ends and the Facility Monitor Logger GUI is closed.  
         [0091]    [0091]FIG. 7 illustrates a simplified flow diagram for a method of operating a Facility Monitor Logger GUI in accordance with a preferred embodiment of the invention. Procedure  700  starts in step  705 .  
         [0092]    In step  710 , a least one monitored value is determined. In a, preferred embodiment, the monitored value is determined using input data from the Facility Monitor Logger Status Screen. For example, the “Computer Rm Temp” data button has been selected on the Facility Monitor Logger Status Screen. Desirably, a server builds a graph as a JPEG file and sends the file to a viewer.  
         [0093]    In step  715 , a date and time are determined for the graph. In a preferred embodiment, date and time are initially determined using a system clock and can be changed based on the selected time selection button.  
         [0094]    In step  720 , data is sent to and retrieved from a SQL server database  725 . The graph type, date, and time are sent to the database. Database  725  returns the data for the graph.  
         [0095]    In step  730 , a query is performed to determine when to display a graph. When at least one graph is to be displayed, procedure  700  branches to step  735 . When at least one graph is not to be displayed, procedure  700  branches to step  755 . In a preferred embodiment, one or more graphs can be displayed at a particular time.  
         [0096]    In step  735 , a query is performed to determine when to use a first time period to display a graph. When the first time period is to be used, procedure  700  branches to step  750 . When the first time period is not to be used, procedure  700  branches to step  740 . In a preferred embodiment, the first time period is a twenty-four hour interval.  
         [0097]    In step  745 , a third time period is selected, procedure  700  continues to step  750 . In a preferred embodiment, the third time period is a four-hour interval.  
         [0098]    In step  750 , the graph is displayed on the Facility Monitor Logger Status Screen.  
         [0099]    In step  755 , a query is performed to determine when to close a graph. When a graph is to be closed, procedure  700  branches to step  760 . When the graph is not to be closed, procedure  700  branches back to step  715 . In a preferred embodiment, a user can select a new date and/or time values.  
         [0100]    In step  760 , procedure  700  ends, and the Facility Monitor Viewer GUI returns control to the Facility Monitor Logger GUI.  
         [0101]    [0101]FIG. 8 is a schematic illustration of a computer system for implementing a remote facility monitor. A computer  800  implements the method of the present invention, wherein the computer housing  802  houses a motherboard  804  which contains a CPU  806 , memory  808  (e.g., DRAM, ROM, EPROM, EEPROM, SRAM, SDRAM, and Flash RAM), and other optional special purpose logic devices (e.g., ASICs) or configurable logic devices (e.g., GAL and reprogrammable FPGA). The computer  800  also includes plural input devices, (e.g., a keyboard  822  and mouse  824 ), and a display card  810  for controlling monitor  820 . In addition, the computer system  800  further includes a floppy disk drive  814 ; other removable media devices (e.g., compact disc  819 , tape, and removable magneto-optical media (not shown)); and a hard disk  812 , or other fixed, high density media drives, connected using an appropriate device bus (e.g., a SCSI bus, an Enhanced IDE bus, or a Ultra DMA bus). Also connected to the same device bus or another device bus, the computer  800  may additionally include a compact disc reader  818 , a compact disc reader/writer unit (not shown) or a compact disc jukebox (not shown). Although compact disc  819  is shown in a CD caddy, the compact disc  819  can be inserted directly into CD-ROM drives which do not require caddies. In addition, a printer (not shown) also provides printed listings of process characteristics (either real-time or logged).  
         [0102]    As stated above, the system includes at least one computer readable medium. Examples of computer readable media are compact discs  819 , hard disks  812 , floppy disks, tape, magneto-optical disks, PROMs (EPROM, EEPROM, Flash EPROM), DRAM, SRAM, SDRAM, etc. Stored on any one or on a combination of computer readable media, the present invention includes software for controlling both the hardware of the computer  800  and for enabling the computer  800  to interact with a human user. Such software may include, but is not limited to, device drivers, operating systems and user applications, such as development tools. Such computer readable media further includes the computer program product of the present invention for implementing a remote facility monitor. The computer code devices of the present invention can be any interpreted or executable code mechanism, including but not limited to scripts, interpreters, dynamic link libraries, Java classes, and complete executable programs.  
         [0103]    The present invention can be applied to a facility other than a plasma processing facility. Additional advantages and modifications will readily occurs to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.