Vacuum system central control information server

• US 7,016,751 B2
• Filed: 09/06/2001
• Issued: 03/21/2006
• Est. Priority Date: 07/13/2001
• Status: Active Grant

• Current Assignee: Edwards Vacuum, LLC (Atlas Copco AB)
• Original Assignee: Helix Technology Corporation (Azenta, Inc.)
• Inventors: Hann, John M., Nordquist, John P.
• Primary Examiner(s): Picard, Leo
• Assistant Examiner(s): Rapp, Chad
• Application Number:
  US09/948,303
• Publication Number:
  US 20030014160A1
• Time in Patent Office: 1,657 Days
• Field of Search: 700/83, 700/108, 700/109, 700/110, 700/282, 702/187.188, 702/187, 702/188
• US Class Current: 700/108
• CPC Class Codes: F04B 37/08 by condensing or freezing, e.g. cryogenic pumps
• CPC Class Codes: F04B 49/065 and making use of computers
• CPC Class Codes: G05B 19/0428 Safety, monitoring G05B19/0423 takes precedence
• CPC Class Codes: G05B 2219/24048 Remote test, monitoring, diagnostic
• CPC Class Codes: G05B 2219/31156 Network structure, internet
• CPC Class Codes: G05B 2219/31161 Java programcode or simular active agents, programs, applets
• CPC Class Codes: G05B 2219/31186 TCP-IP internet protocol
• CPC Class Codes: G05B 2219/33284 Remote diagnostic
• CPC Class Codes: G05B 2219/35008 Www cad, world wide design and manufacturing
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

Status information about the vacuum system is received by a server. A portion of the status information is formatted in response to a request from a web browser, and the formatted vacuum system information is forwarded to the web browser. Commands, including parameter values, can are entered by a user from the web browser, and implemented at the server or forwarded to the proper component in the vacuum system. A command or change history log of commands is maintained and forwarded to the web browser upon a request from the web browser. Status information includes information about an on-going regeneration of a pump in the vacuum system. Furthermore, regeneration can be controlled, i.e., started, stopped, parameters adjusted, in response to commands received from the web browser. Plural sets of regeneration parameters can be defined by a user from the web browser, and issued simultaneously to many devices. The vacuum system status information is be compared against one or more alarm definitions to determine whether an alarm exists, i.e., is “active.” Active alarms are sent to the web browser. Furthermore, a historical log of alarms is maintained and a portion of it forwarded to the web browser upon a request for alarm history. Alarms may be enabled or disabled individually by means provided to the browser. Means are provided to the browser to allow a user to specify alarm definitions.

Claims

1. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen that is one of plural screens populated with retrieved data;

wherein one of the plural screens is a calendar screen which provides a calendar showing, for each day on the calendar, events which occurred on that day; and

wherein an event type is from the group consisting of;

alarms, routines and changes.

2. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen that is one of plural screens populated with retrieved data;

wherein each screen is associated with a unique screen identifier.

3. The method of claim 2, wherein each logical piece of equipment is associated with a unique serial number identifier (SNID), and a network address.

4. The method of claim 3, wherein a request comprises the screen identifier of the currently displayed screen and the SNIDs of equipment from which data is requested, further comprising:

selecting an accessor responsive to the screen identifier; and

translating each SNID in the request to a network address if the request is processed by an equipment accessor.

5. The method of claim 2, wherein a request comprises a continuing parameter identifying the next screen to be shown at the browser.

6. The method of claim 2, further comprising:

if the request is for an action, selecting an actionator responsive to the screen identifier; and

passing action parameters in the request to the selected actionator, the actionator communicating with the vacuum system to implement the requested action.

7. A method for monitoring a vacuum system, comprising:

receiving a request from a client browser for vacuum system status information, the client request being an update request, containing at least one parameter value to be updated;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser.

8. A method for monitoring a vacuum system, comprising:

receiving a request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information;

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser; and

forwarding a tree document to the client browser, the tree document at the browser displaying the vacuum system in a hierarchical tree, the tree periodically requesting updates.

9. The method of claim 8, wherein the tree document comprises a Java applet and tree updates comprise Javascript scripts which instruct the Java applet how to draw the tree.

10. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen that is one of plural screens populated with retrieved data;

wherein at least one screen comprises plural tabs, each tab associated with a unique tab identifier, wherein a request comprises a tab identifier associated with a selected tab.

11. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen;

wherein a currently displayed screen is periodically updated automatically according to a defined update period that is configurable.

12. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen;

wherein a currently displayed screen is periodically updated automatically according to a defined update period of about thirty seconds.

13. A method for monitoring a vacuum system, comprising:

receiving a HTTP request from a client browser for vacuum system status information;

retrieving the requested status information;

formatting the retrieved status information; and

forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen;

wherein a currently displayed screen is periodically updated automatically according to a defined update period and the currently displayed screen is not automatically updated while a user is entering data onto the screen.

14. A monitoring system for monitoring a vacuum system, comprising:

a web module which receives HTTP requests from a client browser for vacuum system status information;

a database accessor which accesses requested status information from a database and provides the accessed status information to the web module; and

an equipment accessor which accesses requested status information from the vacuum system and provides the accessed status information to the web module, the database accessor and equipment accessor using the same format to report the accessed status information to the web module,

the web module formatting the retrieved status information and forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen that is one of plural screens populated with retrieved data;

wherein one of the plural screens is a calendar screen which provides a calendar showing, for each day on the calendar, events which occurred on that day; and

wherein an event type is from the group consisting of;

alarms, routines and changes.

15. A monitoring system for monitoring a vacuum system, comprising:

a web module which receives HTTP requests from a client browser for vacuum system status information;

a database accessor which accesses requested status information from a database and provides the accessed status information to the web module; and

an equipment accessor which accesses requested status information from the vacuum system and provides the accessed status information to the web module, the database accessor and equipment accessor using the same format to report the accessed status information to the web module,

the web module formatting the retrieved status information and forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser, the response comprising a screen document which the client browser uses to display a screen that is one of plural screens populated with retrieved data;

wherein each screen is associated with a unique screen identifier.

16. The monitoring system of claim 15, wherein each logical piece of equipment is associated with a unique serial number identifier (SNID), and a network address.

17. The monitoring system of claim 16, wherein a request comprises the screen identifier of the currently displayed screen and the SNIDs of equipment from which data is requested, further comprising:

an accessor table from which an accessor is selected responsive to the screen identifier; and

a SNID translator used to translate each SNID in the request to a network address if the request is processed by an equipment accessor.

18. The monitoring system of claim 15, wherein a request comprises a continuing parameter identifying the next screen to be shown at the browser.

19. The monitoring system of claim 15, further comprising:

an actionator table from which an actionator is selected responsive to the screen identifier if the request is for an action, the web module passing action parameters in the request to the selected actionator, the actionator communicating with the vacuum system to implement the requested action.

20. A monitoring system for monitoring a vacuum system, comprising:

a web module which receives requests from a client browser for vacuum system status information;

a database accessor which accesses requested status information from a database and provides the accessed status information to the web module; and

an equipment accessor which accesses requested status information from the vacuum system and provides the accessed status information to the web module, the database accessor and equipment accessor using the same format to report the accessed status information to the web module,

the web module formatting the retrieved status information and forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser;

wherein the client request is an update request, containing at least one parameter value to be updated.

21. A monitoring system for monitoring a vacuum system, comprising:

a web module which receives requests from a client browser for vacuum system status information;

a database accessor which accesses requested status information from a database and provides the accessed status information to the web module;

an equipment accessor which accesses requested status information from the vacuum system and provides the accessed status information to the web module, the database accessor and equipment accessor using the same format to report the accessed status information to the web module,

the web module formatting the retrieved status information and forwarding, as a response to the request from the client browser, the formatted vacuum system information to the client browser; and

a tree writer which forwards a tree document to the client browser, the tree document at the browser displaying the vacuum system in a hierarchical tree, the tree periodically requesting updates.

22. The monitoring system of claim 21, wherein the tree document comprises a Java applet and tree updates comprise Javascript scripts which instruct the Java applet how to draw the tree.