In a fault diagnostic system, an operator interface simultaneously displays an operations hierarchy and a components hierarchy in two separate windows. The display system is used with a model-based diagnostic system that monitors operational parameters of an industrial process. The diagnostic system identifies possible failure source components in the industrial process and the display system uses these diagnostics to display the most interesting portions of the operations hierarchy and the components hierarchy. The most interesting node, to be displayed with its subtree, is defined as the node at the lowest level of the hierarchy that is both a fault source and that has more children than than other fault sources at that level.

Patent
   5420977
Priority
Oct 24 1990
Filed
Oct 12 1993
Issued
May 30 1995
Expiry
May 30 2012
Assg.orig
Entity
Large
107
6
EXPIRED
1. A method for interactively displaying results of a diagnostic analysis system used for analyzing operation of a monitored process, comprising the steps of
providing a hierarchical component model representing a relationship between components of the monitored process, any of the components being a potential faulty component,
providing a hierarchical process operation model representing a relationship between operations of the monitored process, any of the operations possibly affected by the potential faulty component,
receiving, from the diagnostic analysis system, signals indicating potential faulty components,
simultaneously displaying, based on the received signals, in a first display window of a display at least a portion of the hierarchical component model including the potential faulty component and in a second display window at least a portion of the hierarchical process operation model including the operations possibly affected by the potential faulty component, and
allowing a user to scroll said first window in two orthogonal directions independent of the scrolling in said second window,
providing a plurality of nodes to each said hierarchical model, each said node being at a hierarchical level in said hierarchical model,
providing a plurality of propagation paths to each said hierarchical model wherein each said path interconnects two said nodes for representing propagation of information from a node at a lower hierarchical level to a node at a higher hierarchical level;
designating the node at the highest hierarchical level to be a root node and any node interconnected to a selected node and having a hierarchical level lower than the hierarchical level of said selected node to be a subnode of said selected node; and
automatically determining, based upon the signals from the diagnostic analysis system, a base-display node which serves as a highest level node of a portion of the hierarchial model to be displayed in one of said windows, said base-display node initially being designated the root node for each hierarchical model,
providing alarms at associated nodes to each said hierarchical model, each said alarm having a first clear state and a second selected state, and
wherein said automatic determining step comprises the steps of
reading current data signals from the diagnostic system wherein said data signals represent the current state of alarms at various nodes,
determining from said data signals one selected node to designate as the base-display node,
displaying a subtree of the hierarchical model in one of said windows wherein said base-display node is a highest level node in said subtree, and
wherein said determining from said data signals step comprises the steps of
reading the alarms at selected nodes;
designating any node having an alarm in said selected state as a fault source node;
determining how many subnodes are interconnected to each fault source node, and designating the fault source node having the most interconnected subnodes as the base-display node.
4. Apparatus for interactively displaying results of a diagnostic analysis system used for analyzing operation of a monitored process, comprising
means for providing a hierarchical component model representing a relationship between components of the monitored process, any of the components being a potential faulty component,
means for providing a hierarchical process operation model representing a relationship between operations of the monitored process, any of the operations possibly affected by the potential faulty component,
means for receiving signals, from the diagnostic analysis system, indicating potential faulty components,
means for simultaneously displaying, based on the received signals, in a first display window of a display at least a portion of the hierarchical component model including the potential faulty component and in a second display window at least a portion of the hierarchical process operation model including the operations possibly affected by the potential faulty component, and
means for allowing a user to scroll said first window in two orthogonal directions independently of the scrolling in said second window,
wherein each said hierarchical model of the means for providing a hierarchical component model and the means for providing a hierarchical process operation model includes:
a plurality of nodes, each said node being at a hierarchical level in said hierarchical model,
a plurality of propagation paths wherein each said path interconnects two said nodes for representing propagation of information from a node at a lower hierarchical level to a node at a higher hierarchical level;
wherein the node at the highest hierarchical level is a root node and any node interconnected to a selected node and having a hierarchical level lower than the hierarchical level of said selected node is a subnode of said selected node; and
said apparatus further comprising
means for automatically determining, based upon the signals from the diagnostic analysis system, a base-display node which serves as a highest level node of a portion of the hierarchical model to be displayed in one of said windows, said base-display node initially being designated the root node for each hierarchical model;
wherein each said hierarchical model of the means for providing a hierarchical component model and the means for providing a hierarchical process operation model includes:
alarms at associate nodes, each said alarm having a first clear state and a second selected state, and wherein said automatic determining means comprises
means for reading current data signals from the diagnostic system wherein said data signals represent the current state of alarms at various nodes,
means for determining from said data signals one selected node to designate as the base-display node, and
means for displaying a subtree of the hierarchical model in one of said windows wherein said base-display node is a highest-level node in said subtree;
wherein said determining from said data signals means comprises
means for reading the alarms at selected nodes;
means for designating any node having an alarm in said selected state as a fault source node;
means for determining how may subnodes are interconnected to each fault source node, and
means for designating the fault node having the most interconnected subnodes as the base-display node.
2. The method of claim 1 further comprising the step of
altering said display at each node at which a fault or alarm occurs to provide a visual indication of said fault or alarm.
3. The method of claim 2 further comprising the step of
changing a background color of a block identifying a node having a fault or alarm condition for making a visual presentation of the fault or alarm condition to a user.
5. The apparatus of claim 4 further comprising
means for altering said display at each node at which a fault or alarm occurs to provide a visual indication of said fault or alarm.
6. The apparatus of claim 5 further comprising
means for changing a background color of a block identifying a node having a fault or alarm condition for making a visual presentation of the fault or alarm condition to a user.

This is a continuation of application Ser. No. 07/602,944, filed Oct. 24, 1990, now abandoned.

The present invention relates in general to real-time fault diagnostic systems, and more particularly to a multiple aspect operator interface for displaying fault diagnostic results in a real-time diagnostic system.

In complex industrial processes, a computerized fault diagnostic system is frequently used to monitor alarms and detect possible sources of failure in the industrial process. Real-time fault diagnostic systems observe the operation of processes, detect the appearance and propagation of faults, and continuously update the list of possible fault causes to support the on-line decision making which determines whether to intervene in the process being monitored.

The ultimate purpose of the diagnostic system is to minimize the cost of operation of the industrial process being monitored by finding all possible sources of detected process anomalies as early as possible, and by predicting the prospective impact of the faults on the operation of related process components. These techniques are particularly applicable in chemical and power engineering because of the extreme expense of down-time and the adverse economic effect which can be caused by a degradation of product quality.

Thus, a diagnostic system is frequently used to monitor extremely complex industrial operations, such as in a chemical or power plant. A typical industrial operation can have thousands of components performing hundreds of operations at any given time. Many of these operations are interdependent, and constantly interact with each other. The failure of any one component can potentially affect adversely the performance of other operations that do not directly use the failed component. Therefore, a single component fault can effectively propagate to many other operations, and can set off many different alarms.

When a failure occurs in one or more components, the plant operator is often inundated with data describing many more alarms than actual failures. It is essential that the operator be able to determine what component or components are responsible for a plant failure and what operations have been affected at the different levels of plant operation. The identity of fault source components and affected operations allows repair of the faulty component, shutdown of an operation, or initiation of fault recovery procedures to take place.

Thus, if an operator of a diagnostic system knew which components were responsible for plant failures, effective repair or alternatively, switching to backup components, could be begun quickly. And if the operator knew which operations were affected by the faulty component, future failures might be avoided by inactivating a particular operation. It would also be advantageous to provide continuing updates of the results of a fault diagnostic system analysis as refinements of the diagnosis occur; because by obtaining even partial results, further failures can be avoided and failure recovery actions can be taken.

Therefore, an object of the present invention is an operator interface that allows a quick and correct response to a rapidly evolving fault scenario in a diagnostic system.

Another object of the present invention is an operator interface that simultaneously displays the status of components as well as the status of operations in a diagnostic system.

Another object of the present invention is an operator interface that provides both component and operation information in a diagnostic system at different levels of abstraction.

A further object of the present invention is an operator interface that presents information in a format that can be understood quickly and easily by the operator of a diagnostic system.

The operator interface of the present invention is used with a model-based diagnostic system that monitors operational parameters of an industrial process. The diagnostic system is based on a hierarchical fault model that uses a directed graph to represent fault nodes and fault propagation paths between plant components and plant operations. The model-based diagnostic system has both on-line and off-line alarm sources and identifies possible failure source components in the industrial process.

The hierarchy is made up of a group of nodes, with the root node being the node from which all other nodes are derived. The hierarchy is defined as a set of hierarchy levels, each level having a group of nodes. A node is assigned to a particular hierarchy level based on the distance of the node from the root node. The root node is in the highest hierarchy level and the leaf nodes are in the lower hierarchy levels.

The operator interface displays the operational hierarchy of the modeled industrial process in one window and displays the component hierarchy of the process in another window. The results of the failure diagnostic system is used to determine which area of the operational hierarchy and the component hierarchy it would be most useful to display to an operator.

The operator interface displays two separate two-dimensional windows simultaneously, one for the operations hierarchy, and one for the components hierarchy. Each window is scrollable in two dimensions, and each window can be moved independently of the other window.

In the preferred embodiment, each node in a hierarchy is preferably displayed in a small block, with the name of the node displayed as text within the block. The background color of each block can be changed dynamically to represent different states of particular components or operations. Lines showing propagation paths are drawn from hierarchical parent to its immediate child(ren).

The display of the entire model hierarchy usually requires an area that is larger than that of the display screen. Therefore, only a portion of the hierarchical model can be shown in one display at a time. The operator can observe particular parts of the hierarchy by scrolling or by using an automatic portion display option.

The automatic portion display option displays the subhierarchy which is rooted at the highest "interesting "node in the hierarchy. In normal operations, the highest interesting node is the root node of the entire graph, that is, the node from which all other nodes are derived. However, if a fault has occurred, the most interesting node is one that has been diagnosed as a fault source.

The automatic operator interface selects the most interesting node in any hierarchy and displays a selected portion of the hierarchy using the initial most interesting node as the root node. Each hierarchy level is examined to determine which node is the most interesting node at that level. In the preferred embodiment, the most interesting node at a particular level is, of all the nodes that are a fault source, the one with the most children. The method continues examining each hierarchy level, displaying, if a more interesting node is found, the current most interesting node and its sub-tree of nodes, including nodes at lower hierarchy levels. If a more interesting node becomes available at a lower level, that node becomes the most interesting node.

The operator interface then displays the most interesting node and as much of its sub-tree as can be displayed. If there are no faults in the system, the operator interface displays the hierarchical model using the root node, or the highest node in the model, as the most interesting node and the operator is free to scroll through the hierarchical display.

Other objects, features, and advantages of the invention will become apparent from the description of a particular embodiment, taken in combination with the drawings, in which:

FIG. 1 is a representation of the application environment of the system;

FIG. 2 is an example of a component hierarchical model and an operations hierarchical model;

FIG. 3 is a block diagram of the integration of the operator interface with the diagnostics system;

FIG. 4 is an example of a operator display screen using the present invention;

FIG. 5 is a flow chart of the algorithm to find the root node from which to display the hierarchy; and

FIG. 6 is a flow chart of the subroutine to find the most interesting node in a hierarchy level.

The operator interface of the present invention is a graphics-oriented color-coded multiple aspect operator interface that graphically (using text also) displays diagnostic results in a fault diagnostic system. A computerized fault diagnostic system is frequently used to monitor alarms and detect possible sources of failure in a complex industrial process. Real-time fault diagnostic systems observe the operation of processes, detect the appearance and propagation of faults, and continuously update the list of possible fault causes in order to support on-line decision making for deciding whether to intervene in the process being monitored.

The operator interface displays the operational hierarchy of the modeled industrial process in one window and displays the component hierarchy of the process in another window. The results of the failure diagnostic system are used to determine which area of the operational hierarchy and the component hierarchy it would be most useful to display to an operator.

As the fault diagnostic system makes refinements to the diagnosis, the operator interface displays can, using an automatic display option, change according to the latest diagnosis. The graphical operator interface of the present invention allows a quick and correct response to a rapidly evolving fault scenario in a diagnostic system.

The operator interface simultaneously displays the status of components as well as the status of operations being monitored by the diagnostic system and provides both component and operation information at different levels of abstraction. The information is presented in a format that can be understood quickly and easily by the operator.

The operator interface simultaneously displays the physical component and the operations aspects of a process, represented as hierarchical graphs, in separate, two-dimensional graphic windows. The complete model of the components and of the operations usually do not fit on one screen. The operator interface therefore can show only a portion, or a "window", of the operation or component hierarchical graph model at one time. The graphic windows can be scrolled in two dimensions by the operator, to look at and review the complete model.

Both the operations and the components being monitored appear to the operator in a graphed hierarchical model. The models consist of components and sub-components or of operations and sub-operations. Individual elements of each hierarchy are represented, in the illustrated embodiment, in a small block containing the name of the individual element. In the illustrated embodiment, the background color of each block can be changed dynamically to reflect the status of the individual component or operation.

Referring now to FIG. 1, the operator interface of the present invention is used with a model-based diagnostic system 10 that monitors an industrial process 20. The model-based diagnostic system has both on-line and off-line alarm sources and identifies possible failure source components in the industrial process in response to alarm signals. The potential failure source components are displayed on a display 25 of an operator interface 30.

In a preferred embodiment of the present invention, the diagnostic system is based on a hierarchical fault model which uses a directed graph to represent fault nodes and fault propagation paths between plant components and plant operations. The plant components and the plant operations are represented in a hierarchy which is derived from the structural models of plant components and operations respectively.

The hierarchy is made up of a group of nodes, with the root node being the node from which all other nodes are derived. The hierarchy is defined as a set of hierarchy levels, each level having a group of nodes. A node is assigned to a particular hierarchy level based on the distance of the node from the root node. The root node is in the highest hierarchy level and the leaf nodes are in the lower hierarchy levels.

Each hierarchical model consists of nodes (denoted by the circular shapes in the figure) connected by fault propagation paths (the connecting lines in the figure). The fault propagation paths represent how a fault, which occurs at one node, can propagate through the industrial process. Each fault propagation path is characterized by the upper and lower limit of the propagation time, and by the propagation probability.

Referring to FIG. 2, an example of a component hierarchical model 50 and an operations hierarchical model 60 is shown. The plant component hierarchy is a hierarchical decomposition of the components present within the plant. The plant operations hierarchy is a hierarchical decomposition of the operations being performed within the plant.

Referring to FIG. 2, the root node "PLANT" 51 of the plant component hierarchy 50 is the plant itself, and is at the highest hierarchical level. The root node "PLANT" has five children at a second hierarchical level, "CONTROLLER" 52, "FUEL ASSEMBLY" 53, "REACTION ASSEMBLY" 54, "STORAGE ASSEMBLY" 55, and "PUMP" 56. The remaining nodes are at the lowest, or third hierarchical level. These nodes are children of the nodes at the second hierarchical level. For example, nodes "PIPE 3" 57 and "VALVE" 58 are the children of the "FUEL ASSEMBLY" 53 node. A failure occuring at "PIPE 3" 57 would propagate up to "FUEL ASSEMBLY" 53, and finally to "PLANT" 51. When a failure is discovered at a particular component, the hierarchical model can be used to determine both what components at a higher level can be affected by the failure and also what components at a lower level could have failed and caused this particular component to fail.

Similarly, in the operations hierarchical model 60, the root node "PROCESS" is the industrial process. The root node has three children, "HEATING" node 62 , "TEMP CONTROL" node 63, and "OUTPUT" node 64. The "HEATING" node 62 has two children, "BURNING" node 65, and "FUEL SUPPLY" node 66. When a failure is discovered at a particular operation, the hierarchical model can be used to determine both what operations at a higher level can be affected by the failure and also what operations at a lower level could have failed and caused this particular operation to fail. Referring to FIG. 3, the system integrates the operator interface with the diagnostic system. The model database 100 contains both the component model hierarchy 120 and the operations model hierarchy 110. A layout generator 130 generates a component layout 150 for the component hierarchy 120 and stores it for runtime use. The layout generator 130 also generates and stores an operations layout 140 for the operations hierarchy 110.

A display manager 160 uses the component and operations layouts 140, 150 to display the appropriate portion of each hierarchy, based on the inputs received from the diagnostic system. The display screen 25 displays two separate two-dimensional windows simultaneously, one window 210 for the operations hierarchy, and one window 200 for the components hierarchy.

Each window is scrollable in both dimensions, and each window can be moved independently relative to the other window. The hierarchical model to be displayed usually requires an area that is larger than that available on the display screen. Because the maximum size of the window is fixed by the size of the display screen, typically, only a portion of the model can be shown at a time. The operator can observe particular parts of the hierarchical model by manual scrolling or by using the automatic portion display option.

Referring to FIG. 4, an example of an operator display screen of the present invention is shown. The automatic portion display option displays a "sub-hierarchy" which is rooted at the highest "interesting" node in the hierarchy. In normal operations, the highest interesting node is the root node itself. However, if a fault has occurred, the most interesting node is one that has been diagnosed as a fault source.

FIG. 4 shows an example of an operations hierarchy display 250 with root node 255. Each node in a hierarchy, for example node 260, is displayed in a small block, with the name of the node displayed as text within the block. Each hierarchy is displayed in a horizontal orientation, from left to right. Each parent node is displayed as a block in the window that is typically centered with respect to its immediate children. For example, the parent node 290, labelled "Generation" is centered with respect to its child nodes 300 "Exciter" 310 "Speed Regulator" and 320 "Generator". The vertical left hand edges of each node in the same level of the hierarchy are aligned on the same vertical line.

Lines showing propagation paths are drawn from the midpoint of each parent's right hand vertical corner to the midpoint of the left hand edge of each immediate child. The horizontal distance between the left-hand vertical edge of any two blocks of text need not be constant, and may be changed for different applications.

In the illustrated embodiment, color is used to convey analysis information. The color of the text strings within the blocks are black. The background color of each block is changed dynamically to represent different states of particular components or operations. In the illustrated embodiment, the color codes for blocks on the operation hierarchy are:

Green: Operation is normal.

Pink: Operation contains ringing alarms.

Red: Operation is a possible failure source.

Yellow: Off-line alarm information is requested for this operation.

The color codes for blocks on the component hierarchy are:

Green: Component is normal

Red: Component is a possible failure source.

Referring to FIG. 5, the automatic portion display method selects the highest interesting node in a hierarchy and directs the display of selected portions of the hierarchy. Initially, the most interesting node is set at 400 to the root node. Then, the next hierarchy level is obtained at 410 and is examined at 420 to determine if there is a more interesting node at this lower hierarchical level. The system continues examining each hierarchical level (tested at 430), and when all levels have been examined, displays at 440 the sub-tree with the root node being that node determined as being the most interesting node.

Referring to FIG. 6, in the illustrated embodiment, the method for determining if a more interesting node exists examines the nodes at each level to find the fault source, if any, with the most children. This node is set to be the most interesting node at that level.

Referring in particular to the flow chart of FIG. 6, the system first zeroes, at 500, the parameter MAXCHILDS. It then fetches, at 510, the next node in the current hierarchical level and it tests, at 520, whether that node, designated the current node, is a fault source. If it is not a fault source, the next node is fetched at 510. If it is a fault source, the system tests, at 530, whether the number of children from that node exceeds the current MAXCHILDS. If it does not, the system returns and obtains the next node of the hierarchical level. If its number of children exceeds the current maximum, the maximum is reset, at 540, and the most "interesting" node is set, at 550, to be the most interesting node. The system checks, at 560, for additional nodes at this hierarchical level, and if there are none returns to the main program.

Thus, if there is a more interesting node at a lower hierarchical level, that node becomes the most interesting node; and the system will display the most interesting node and as much of its subtree as can fit in the display. The most interesting node is initially the root node of the entire hierarchy, and is displayed in the center of the far left of the graph. When, in the preferred embodiment, a more interesting node is found, the display if the most interesting node is shifted to the upper left corner of the display.

While the foregoing invention has been described with reference to a particularly preferred embodiment, it should be understood that various modifications and alterations will occur to those practiced in the art. Such modifications and alterations are intended to fall within the scope of the appended claims.

Okuda, Koji, Sztipanovits, Janos, Biegl, Csaba, Karsai, Gabor, Padalkar, Samir, Miyasaka, Nobuji

Patent Priority Assignee Title
10016554, Jul 09 2008 Baxter International Inc.; BAXTER HEALTHCARE SA Dialysis system including wireless patient data
10061899, May 15 2012 Baxter International Inc.; BAXTER HEALTHCARE SA Home therapy machine
10068061, May 15 2012 Baxter International Inc.; BAXTER HEALTHCARE SA Home therapy entry, modification, and reporting system
10089443, May 15 2012 Baxter International Inc.; Baxter Healthcare S.A.; Baxter International Inc; BAXTER HEALTHCARE S A Home medical device systems and methods for therapy prescription and tracking, servicing and inventory
10095840, May 15 2012 Baxter International Inc.; BAXTER HEALTHCARE SA System and method for performing renal therapy at a home or dwelling of a patient
10173008, Jan 29 2002 Baxter International Inc. System and method for communicating with a dialysis machine through a network
10224117, May 15 2012 Baxter International Inc.; BAXTER HEALTHCARE SA Home therapy machine allowing patient device program selection
10272190, Jul 09 2008 Baxter International Inc.; BAXTER HEALTHCARE SA Renal therapy system including a blood pressure monitor
10347374, Oct 13 2008 BAXTER CORPORATION ENGLEWOOD Medication preparation system
10552577, Aug 31 2012 BAXTER CORPORATION ENGLEWOOD Medication requisition fulfillment system and method
10556062, Jan 29 2002 Baxter International Inc. Electronic medication order transfer and processing methods and apparatus
10646405, Oct 26 2012 BAXTER CORPORATION ENGLEWOOD Work station for medical dose preparation system
10646634, Jul 09 2008 Baxter International Inc.; BAXTER HEALTHCARE SA Dialysis system and disposable set
10818387, Dec 05 2014 BAXTER CORPORATION ENGLEWOOD Dose preparation data analytics
10971257, Oct 26 2012 BAXTER CORPORATION ENGLEWOOD Image acquisition for medical dose preparation system
11107574, Sep 30 2014 BAXTER CORPORATION ENGLEWOOD Management of medication preparation with formulary management
11241811, Mar 02 2018 Engel Austria GmbH Method and device for visualizing or evaluating a process state
11311658, Jul 09 2008 Baxter International Inc.; BAXTER HEALTHCARE SA Dialysis system having adaptive prescription generation
11367533, Jun 30 2014 BAXTER CORPORATION ENGLEWOOD Managed medical information exchange
11495334, Jun 25 2015 Gambro Lundia AB Medical device system and method having a distributed database
11516183, Dec 21 2016 Gambro Lundia AB Medical device system including information technology infrastructure having secure cluster domain supporting external domain
11575673, Sep 30 2014 BAXTER CORPORATION ENGLEWOOD Central user management in a distributed healthcare information management system
5504863, Aug 30 1994 Fujitsu Limited Centralized network monitoring device for monitoring devices via intermediate monitoring devices by means of polling and including display means displaying screens corresponding to heirarchic levels of the monitored devices in a network
5539869, Sep 28 1992 FORD GLOBAL TECHNOLOGIES, INC A MICHIGAN CORPORATION Method and system for processing and presenting on-line, multimedia information in a tree structure
5588109, Jan 23 1995 Agilent Technologies Inc User interface for a remote diagnostic device
5790797, Feb 17 1995 Fujitsu Limited Load distribution system for monitoring device
5793933, Sep 13 1993 Kabushiki Kaisha Toshiba Computer-implemented system and method for constructing a system
5805442, May 30 1996 SCHNEIDER AUTOMATION INC Distributed interface architecture for programmable industrial control systems
5838563, Apr 12 1996 FISHER-ROSEMONT SYSTEMS, INC.; Fisher-Rosemount Systems, Inc System for configuring a process control environment
5903455, Feb 06 1996 Fisher-Rosemount Systems, Inc. Interface controls for use in a field device management system
5940294, Apr 12 1996 FISHER-ROSEMONT SYSTEMS, INC.; Fisher-Rosemount Systems, Inc System for assisting configuring a process control environment
5960214, Feb 06 1996 Fisher-Rosemount Systems, Inc. Integrated communication network for use in a field device management system
5973696, Aug 08 1996 Conexant Systems, Inc Embedded web server
6078320, Apr 12 1996 Fisher-Rosemount Systems, Inc. System for configuring a process control environment
6108662, May 08 1998 Allen-Bradley Company, LLC System method and article of manufacture for integrated enterprise-wide control
6151625, Sep 10 1997 Schneider Automation Inc. Internet web interface including programmable logic controller for controlling output devices based on status of input devices
6233626, Oct 06 1998 SCHNEIDER AUTOMATION, INC System for a modular terminal input/output interface for communicating messaging application layer over encoded ethernet to transport layer
6259981, Jun 17 1999 Caterpillar Inc Caution/warning system for displaying system malfunctions/faults in a night-time viewing mode
6282454, Sep 10 1997 SCHNEIDER AUTOMATION INC , C O SQUARE D COMPANY Web interface to a programmable controller
6327511, Dec 30 1998 SCHNEIDER AUTOMATION INC Input/output (I/O) scanner for a control system with peer determination
6381508, Apr 15 1997 Process and equipment for optimizing production
6434157, Oct 06 1998 SCHNEIDER AUTOMATION, INC MODBUS plus ethernet bridge
6456308, Aug 08 1996 Conexant Systems, Inc Embedded web server
6466995, Oct 06 1998 Schneider Automation, Inc. Messaging application layer over ethernet to transport layer (TCP) communications method and apparatus for a modular terminal input/output system
6510352, Jul 29 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for object-based process control
6587884, Sep 10 1997 SCHNEIDER AUTOMATION INC Dual ethernet protocol stack for maximum speed access to a programmable logic controller (PLC)
6618630, Jul 08 1999 Fisher-Rosemount Systems, Inc. User interface that integrates a process control configuration system and a field device management system
6640140, Oct 10 2000 SCHNEIDER AUTOMATION, INC C O SQUARE D COMPANY PLC executive with integrated web server
6732191, Sep 10 1997 Schneider Automation Inc. Web interface to an input/output device
6754885, May 17 1999 Invensys Systems, Inc Methods and apparatus for controlling object appearance in a process control configuration system
6788980, Jun 11 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
6845401, Dec 30 1998 SCHNEIDER AUTOMATION INC Embedded file system for a programmable logic controller
6853867, Dec 30 1998 SCHNEIDER AUTOMATION INC Interface to a programmable logic controller
6868538, Apr 12 1996 Fisher-Rosemount Systems, Inc. Object-oriented programmable controller
6963922, Sep 10 1997 Schneider Automatiion Inc. Dual protocol stack for maximum speed access to a programmable logic controller (PLC) in a factor automation system
7017121, Dec 01 1997 Siemens Aktiengesellschaft Method for visual display unit-based definition and parametrization of interfaces
7023795, Nov 07 2000 SHNEIDER AUTOMATION INC Method and apparatus for an active standby control system on a network
7028204, Sep 06 2000 SCHNEIDER AUTOMATION, INC ; SCHNEIDER AUTOMATION, INC C O SQUARE D COMPANY Method and apparatus for ethernet prioritized device clock synchronization
7032029, Jul 07 2000 Schneider Automation Inc. Method and apparatus for an active standby control system on a network
7035898, Sep 10 1997 Schneider Automation Inc. System for programming a factory automation device using a web browser
7058693, Sep 10 1997 Schneider Automation Inc.; SCHNEIDER AUTOMATION INC System for programming a programmable logic controller using a web browser
7062335, Dec 30 1998 Schneider Automation Inc. Interface to a programmable logic controller
7089530, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Process control configuration system with connection validation and configuration
7096465, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Process control configuration system with parameterized objects
7146408, May 30 1996 SCHNEIDER AUTOMATION INC Method and system for monitoring a controller and displaying data from the controller in a format provided by the controller
7162510, Mar 16 1998 Schneider Automation Inc. Communication system for a control system over Ethernet and IP networks
7181487, Jul 07 2000 SCHNEIDER AUTOMATION INC Method and system for transmitting and activating an application requesting human intervention in an automation network
7200774, Jul 22 2000 Intellectual Ventures II LLC System and method for supporting a fault cause analysis
7272815, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for control configuration with versioning, security, composite blocks, edit selection, object swapping, formulaic values and other aspects
7295887, Feb 20 2004 Yokogawa Electric Corporation Machine management system and message server used for machine management
7490138, May 30 1996 Schneider Automation Inc. System for distributed programmable control
7519737, Mar 02 2002 Schneider Automation Inc. Input/output (I/O) scanner for a control system with peer determination
7590702, Oct 06 1998 Schneider Automation Inc. Messaging application layer over ethernet to transport layer (TCP) communications method and apparatus for a modular terminal input/output system
7676292, Oct 20 2006 Rockwell Automation Technologies, Inc. Patterns employed for module design
7680550, Oct 20 2006 Rockwell Automation Technologies, Inc. Unit module state processing enhancements
7684877, Oct 20 2006 Rockwell Automation Technologies, Inc. State propagation for modules
7698156, Jan 29 2002 Baxter International Inc. System and method for identifying data streams associated with medical equipment
7725200, Oct 20 2006 Rockwell Automation Technologies, Inc. Validation of configuration settings in an industrial process
7756733, Feb 25 2000 Siemens Aktiengesellschaft Method for operating and device for monitoring a technical installation
7761923, Mar 01 2004 SCHNEIDER ELECTRIC SYSTEMS USA, INC Process control methods and apparatus for intrusion detection, protection and network hardening
7778717, Apr 15 2002 Schneider Electric Software, LLC Component object model communication method for a control system
7844349, Oct 20 2006 Rockwell Automation Technologies, Inc. Standard MES interface for discrete manufacturing
7860857, Mar 30 2006 SCHNEIDER ELECTRIC SYSTEMS USA, INC Digital data processing apparatus and methods for improving plant performance
7890927, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Apparatus and method for configuring and editing a control system with live data
7894917, Oct 20 2006 Rockwell Automation Technologies, Inc.; ROCKWELL AUTOMATION TECHNOLOGIES, INC Automatic fault tuning
7984420, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Control systems and methods with composite blocks
8023500, Aug 20 1996 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods for process control with change updates
8028272, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Control system configurator and methods with edit selection
8028275, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Control systems and methods with smart blocks
8060222, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Control system configurator and methods with object characteristic swapping
8090452, Jun 11 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
8127060, May 29 2009 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware
8185871, Apr 12 1996 Fisher-Rosemount Systems, Inc System for configuring a process control environment
8199678, Oct 21 2005 Hewlett Packard Enterprise Development LP Graphical arrangement of IT network components
8214231, Jan 29 2002 Baxter International, Inc. System and method for identifying data streams associated with medical equipment
8225271, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Apparatus for control systems with objects that are associated with live data
8229579, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Control systems and methods with versioning
8234128, Apr 30 2002 Baxter International Inc System and method for verifying medical device operational parameters
8291121, Sep 10 1997 SCHNEIDER AUTOMATION, INC C O SQUARE D COMPANY System and method for interfacing with a controller
8368640, May 17 1999 SCHNEIDER ELECTRIC SYSTEMS USA, INC Process control configuration system with connection validation and configuration
8392008, Oct 20 2006 Rockwell Automation Technologies, Inc. Module arbitration and ownership enhancements
8463964, May 29 2009 SCHNEIDER ELECTRIC SYSTEMS USA, INC Methods and apparatus for control configuration with enhanced change-tracking
8594814, Jun 20 2008 Invensys Systems, Inc Systems and methods for immersive interaction with actual and/or simulated facilities for process, environmental and industrial control
8601435, Oct 20 2006 Rockwell Automation Technologies, Inc. Module class subsets for industrial control
8775196, Jan 29 2002 Baxter International Inc System and method for notification and escalation of medical data
9557735, Dec 10 2009 Fisher-Rosemount Systems, Inc. Methods and apparatus to manage process control status rollups
9691038, Nov 03 2006 International Business Machines Corporation Method and apparatus for examining workflow processes
Patent Priority Assignee Title
4710763, Oct 19 1984 Texas Instruments Incorporated; TEXAS INSTRUMENTS INCORPORATED, A DE CORP Method for generating and displaying tree structures in a limited display area
4953106, May 23 1989 NCR Corporation Technique for drawing directed graphs
4970664, Jun 10 1988 MENTOR GRAPHICS CORPORATION, 8500 S W CREEKSIDE PLACE, BEAVERTON, OR 97005-7191 A CORP OF OR Critical path analyzer with path context window
EP243782,
EP245039,
EP263636,
//
Executed onAssignorAssigneeConveyanceFrameReelDoc
Oct 12 1993Vanderbilt University(assignment on the face of the patent)
Oct 12 1993Osaka Gas Co., Ltd.(assignment on the face of the patent)
Date Maintenance Fee Events
Dec 22 1998REM: Maintenance Fee Reminder Mailed.
May 30 1999EXP: Patent Expired for Failure to Pay Maintenance Fees.


Date Maintenance Schedule
May 30 19984 years fee payment window open
Nov 30 19986 months grace period start (w surcharge)
May 30 1999patent expiry (for year 4)
May 30 20012 years to revive unintentionally abandoned end. (for year 4)
May 30 20028 years fee payment window open
Nov 30 20026 months grace period start (w surcharge)
May 30 2003patent expiry (for year 8)
May 30 20052 years to revive unintentionally abandoned end. (for year 8)
May 30 200612 years fee payment window open
Nov 30 20066 months grace period start (w surcharge)
May 30 2007patent expiry (for year 12)
May 30 20092 years to revive unintentionally abandoned end. (for year 12)