This description relates to generally to mechanical/electrical equipment operations, monitoring and diagnostics, and more specifically, to systems and methods for automatically advising operators of anomalous behavior of heavy duty gas turbines.
Monitoring machinery health and alerting operators to anomalous machinery conditions is an important part of operating one or a fleet of machines. Specifically, monitoring selected auxiliary system process parameters is important to health monitoring of gas turbine auxiliary systems. There is currently no known monitoring system for online estimation of most auxiliary system process parameters, and only the measured parameter is monitored. By not comparing the measured value to an expected value, the dynamic baseline and physical insight to define alarm thresholds are unknown. Without this calculation, only static thresholds based on constant deviation from preset values is available. Further, troubleshooting is hindered without an estimation of the auxiliary system process parameters. For example, a determination can be made as to the source of a deviation between the expected value and the measured value. Moreover, rapidly changing operational conditions or very slowly changing operational conditions may make it difficult for an operator to recognize anomalous conditions or what operational changes can be made to mitigate the anomalous conditions.
At least some known auxiliary system monitoring systems monitor the measured values only and using historical data for the same type of machine static thresholds are predefined, so that if the measured value exceeds the predefined threshold, an alarm is raised. Many attempts are needed to define and refine these thresholds, which do not take into account the machine running or load conditions. Such systems are prone to too many false alarms, and actual faults are generally detected too late. Moreover, only limited or no troubleshooting information is provided in such systems.
In one embodiment, a computer-implemented method for monitoring and diagnosing anomalies in auxiliary systems of a gas turbine implemented using a computer device coupled to a user interface and a memory device includes storing a plurality rule sets in the memory device, the rule sets relative to the auxiliary systems of the gas turbine, the rule sets including at least one rule expressed as a relational expression of a real-time data output relative to a real-time data input, the relational expression being specific to parameters associated with the auxiliary systems of the gas turbine, receiving real-time and historical data inputs from a condition monitoring system associated with the gas turbine, the data inputs relating to process parameters associated with the auxiliary systems of the gas turbine, and estimating values for at least some of the parameters associated with the auxiliary systems of the gas turbine using the received inputs.
In another embodiment, a monitoring and diagnostic system for auxiliary systems of a gas turbine comprising an axial compressor and a low pressure turbine in flow communication, said system comprising a plurality of rule sets relating to the auxiliary systems, the rule sets each including a relational expression of a real-time data output relative to a real-time data input, the relational expression being specific to inputs relating to respective process parameters of the auxiliary systems.
In yet another embodiment, one or more non-transitory computer-readable storage media has computer-executable instructions embodied thereon, wherein when executed by at least one processor, the computer-executable instructions cause the processor to receive a measured value of a auxiliary system process parameter of a gas turbine, receive measured values and inferred values of parameters associated with the gas turbine, estimate an expected value respective of the received measured value, compare the expected value to the respective measured value, and generate an advisory message recommending an action to be taken based on the comparison
Although specific features of various embodiments may be shown in some drawings and not in others, this is for convenience only. Any feature of any drawing may be referenced and/or claimed in combination with any feature of any other drawing.
The following detailed description illustrates embodiments of the invention by way of example and not by way of limitation. It is contemplated that the invention has general application to analytical and methodical embodiments of monitoring equipment operation in industrial, commercial, and residential applications.
As described herein, auxiliary system rule sets include for example, a bearing radial vibrations rule set, a bearing metal temperature rule set, a mineral lube oil system rule set, a hydraulic oil system rule set, a wheel-space rule set, a bleed valves rule set, a combustion spread rule set, a exhaust temperatures rule set, and a ventilation system rule set.
In the exemplary embodiment, a first site 104 includes one or more process analyzers 106, equipment monitoring systems 108, equipment local control centers 110, and/or monitoring and alarm panels 112 each configured to interface with respective equipment sensors and control equipment to effect control and operation of the respective equipment. The one or more process analyzers 106, equipment monitoring systems 108, equipment local control centers 110, and/or monitoring and alarm panels 112 are communicatively coupled to an intelligent monitoring and diagnostic system 114 through a network 116. Intelligent monitoring and diagnostic (IMAD) system 114 is further configured to communicate with other on-site systems (not shown in
Each of a plurality of other sites, for example, a second site 124 and an nth site 126 may be substantially similar to first site 104 although may or may not be exactly similar to first site 104.
DCS 201 may be configured to receive and display operational parameters associated with a plurality of equipment, and to generate automatic control signals and receive manual control inputs for controlling the operation of the equipment of industrial plant. In the exemplary embodiment, DCS 201 may include a software code segment configured to control processor 205 to analyze data received at DCS 201 that allows for on-line monitoring and diagnosis of the industrial plant machines. Data may be collected from each machine, including gas turbines, centrifugal compressors, pumps and motors, associated process sensors, and local environmental sensors including, for example, vibration, seismic, temperature, pressure, current, voltage, ambient temperature and ambient humidity sensors. The data may be pre-processed by a local diagnostic module or a remote input/output module, or may transmitted to DCS 201 in raw form.
A local monitoring and diagnostic system (LMDS) 213 may be a separate add-on hardware device, such as, for example, a personal computer (PC), that communicates with DCS 201 and other control systems 209 and data sources through network backbone 203. LMDS 213 may also be embodied in a software program segment executing on DCS 201 and/or one or more of the other control systems 209. Accordingly, LMDS 213 may operate in a distributed manner, such that a portion of the software program segment executes on several processors concurrently. As such, LMDS 213 may be fully integrated into the operation of DCS 201 and other control systems 209. LMDS 213 analyzes data received by DCS 201, data sources, and other control systems 209 to determine an operational health of the machines and/or a process employing the machines using a global view of the industrial plant.
In the exemplary embodiment, network architecture 100 includes a server grade computer 202 and one or more client systems 203. Server grade computer 202 further includes a database server 206, an application server 208, a web server 210, a fax server 212, a directory server 214, and a mail server 216. Each of servers 206, 208, 210, 212, 214, and 216 may be embodied in software executing on server grade computer 202, or any combinations of servers 206, 208, 210, 212, 214, and 216 may be embodied alone or in combination on separate server grade computers coupled in a local area network (LAN) (not shown). A data storage unit 220 is coupled to server grade computer 202. In addition, a workstation 222, such as a system administrator's workstation, a user workstation, and/or a supervisor's workstation are coupled to network backbone 203. Alternatively, workstations 222 are coupled to network backbone 203 using an Internet link 226 or are connected through a wireless connection, such as, through wireless base station 207.
Each workstation 222 may be a personal computer having a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations 222, such functions can be performed at one of many personal computers coupled to network backbone 203. Workstations 222 are described as being associated with separate exemplary functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to network backbone 203.
Server grade computer 202 is configured to be communicatively coupled to various individuals, including employees 228 and to third parties, e.g., service providers 230. The communication in the exemplary embodiment is illustrated as being performed using the Internet, however, any other wide area network (WAN) type communication can be utilized in other embodiments, i.e., the systems and processes are not limited to being practiced using the Internet.
In the exemplary embodiment, any authorized individual having a workstation 232 can access LMDS 213. At least one of the client systems may include a manager workstation 234 located at a remote location. Workstations 222 may be embodied on personal computers having a web browser. Also, workstations 222 are configured to communicate with server grade computer 202. Furthermore, fax server 212 communicates with remotely located client systems, including a client system 236 using a telephone link (not shown). Fax server 212 is configured to communicate with other client systems 228, 230, and 234, as well.
Computerized modeling and analysis tools of LMDS 213, as described below in more detail, may be stored in server 202 and can be accessed by a requester at any one of client systems 204. In one embodiment, client systems 204 are computers including a web browser, such that server grade computer 202 is accessible to client systems 204 using the Internet. Client systems 204 are interconnected to the Internet through many interfaces including a network, such as a local area network (LAN) or a wide area network (WAN), dial-in-connections, cable modems and special high-speed ISDN lines. Client systems 204 could be any device capable of interconnecting to the Internet including a web-based phone, personal digital assistant (PDA), or other web-based connectable equipment. Database server 206 is connected to a database 240 containing information about industrial plant 10, as described below in greater detail. In one embodiment, centralized database 240 is stored on server grade computer 202 and can be accessed by potential users at one of client systems 204 by logging onto server grade computer 202 through one of client systems 204. In an alternative embodiment, database 240 is stored remotely from server grade computer 202 and may be non-centralized.
Other industrial plant systems may provide data that is accessible to server grade computer 202 and/or client systems 204 through independent connections to network backbone 204. An interactive electronic tech manual server 242 services requests for machine data relating to a configuration of each machine. Such data may include operational capabilities, such as pump curves, motor horsepower rating, insulation class, and frame size, design parameters, such as dimensions, number of rotor bars or impeller blades, and machinery maintenance history, such as field alterations to the machine, as-found and as-left alignment measurements, and repairs implemented on the machine that do not return the machine to its original design condition.
A portable vibration monitor 244 may be intermittently coupled to LAN directly or through a computer input port such as ports included in workstations 222 or client systems 204. Typically, vibration data is collected in a route, collecting data from a predetermined list of machines on a periodic basis, for example, monthly or other periodicity. Vibration data may also be collected in conjunction with troubleshooting, maintenance, and commissioning activities. Further, vibration data may be collected continuously in a real-time or near real-time basis. Such data may provide a new baseline for algorithms of LMDS 213. Process data may similarly, be collected on a route basis or during troubleshooting, maintenance, and commissioning activities. Moreover, some process data may be collected continuously in a real-time or near real-time basis. Certain process parameters may not be permanently instrumented and a portable process data collector 245 may be used to collect process parameter data that can be downloaded to DCS 201 through workstation 222 so that it is accessible to LMDS 213. Other process parameter data, such as process fluid composition analyzers and pollution emission analyzers may be provided to DCS 201 through a plurality of on-line monitors 246.
Electrical power supplied to various machines or generated by generated by generators with the industrial plant may be monitored by a motor protection relay 248 associated with each machine. Typically, such relays 248 are located remotely from the monitored equipment in a motor control center (MCC) or in switchgear 250 supplying the machine. In addition, to protection relays 248, switchgear 250 may also include a supervisory control and data acquisition system (SCADA) that provides LMDS 213 with power supply or power delivery system (not shown) equipment located at the industrial plant, for example, in a switchyard, or remote transmission line breakers and line parameters.
In the exemplary embodiment, rule set 280 includes one or more rules relating to monitoring and diagnosis of specific problems associated with equipment operating in an industrial plant, such as, for example, a gas reinjection plant, a liquid natural gas (LNG) plant, a power plant, a refinery, and a chemical processing facility. Although rule set 280 is described in terms of being used with an industrial plant, rule set 280 may be appropriately constructed to capture any knowledge and be used for determining solutions in any field. For example, rule set 280 may contain knowledge pertaining to economic behavior, financial activity, weather phenomenon, and design processes. Rule set 280 may then be used to determine solutions to problems in these fields. Rule set 280 includes knowledge from one or many sources, such that the knowledge is transmitted to any system where rule set 280 is applied. Knowledge is captured in the form of rules that relate outputs 284 to inputs 282 such that a specification of inputs 282 and outputs 284 allows rule set 280 to be applied to LMDS 213. Rule set 280 may include only rules specific to a specific plant asset and may be directed to only one possible problem associated with that specific plant asset. For example, rule set 280 may include only rules that are applicable to a motor or a motor/pump combination. Rule set 280 may only include rules that determine a health of the motor/pump combination using vibration data. Rule set 280 may also include rules that determine the health of the motor/pump combination using a suite of diagnostic tools that include, in addition to vibration analysis techniques, but may also include, for example, performance calculational tools and/or financial calculational tools for the motor/pump combination.
In operation, rule set 280 is created in a software developmental tool that prompts a user for relationships between inputs 282 and outputs 284. Inputs 282 may receive data representing, for example digital signals, analog signals, waveforms, processed signals, manually entered and/or configuration parameters, and outputs from other rule sets. Rules within rule set 280 may include logical rules, numerical algorithms, application of waveform and signal processing techniques, expert system and artificial intelligence algorithms, statistical tools, and any other expression that may relate outputs 284 to inputs 282. Outputs 284 may be mapped to respective locations in the memory that are reserved and configured to receive each output 284. LMDS 213 and DCS 201 may then use the locations in memory to accomplish any monitoring and/or control functions LMDS 213 and DCS 201 may be programmed to perform. The rules of rule set 280 operate independently of LMDS 213 and DCS 201, although inputs 282 may be supplied to rule set 280 and outputs 284 may be supplied to rule set 280, directly or indirectly through intervening devices.
During creation of rule set 280, a human expert in the field divulges knowledge of the field particular to a specific asset using a development tool by programming one or more rules. The rules are created by generating expressions of relationship between outputs 284 and inputs 282 such that no coding of the rules is needed. Operands may be selected from a library of operands, using graphical methods, for example, using drag and drop on a graphical user interface built into the development tool. A graphical representation of an operand may be selected from a library portion of a screen display (not shown) and dragged and dropped into a rule creation portion. Relationships between input 282 and operands are arranged in a logical display fashion and the user is prompted for values, such as, constants, when appropriate based on specific operands and specific ones of inputs 282 that are selected. As many rules that are needed to capture the knowledge of the expert are created. Accordingly, rule set 280 may include a robust set of diagnostic and/or monitoring rules or a relatively less robust set of diagnostic and/or monitoring rules based on a customer's requirements and a state of the art in the particular field of rule set 280. The development tool provides resources for testing rule set 280 during the development to ensure various combinations and values of inputs 282 produce expected outputs at outputs 284.
The logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps may be provided, or steps may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other embodiments are within the scope of the following claims.
It will be appreciated that the above embodiments that have been described in particular detail are merely example or possible embodiments, and that there are many other combinations, additions, or alternatives that may be included.
Also, the particular naming of the components, capitalization of terms, the attributes, data structures, or any other programming or structural aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, formats, or protocols. Further, the system may be implemented via a combination of hardware and software, as described, or entirely in hardware elements. Also, the particular division of functionality between the various system components described herein is merely one example, and not mandatory; functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead performed by a single component.
Some portions of above description present features in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations may be used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules or by functional names, without loss of generality.
Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or “providing” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories or registers or other such information storage, transmission or display devices.
While the disclosure has been described in terms of various specific embodiments, it will be recognized that the disclosure can be practiced with modification within the spirit and scope of the claims.
The term processor, as used herein, refers to central processing units, microprocessors, microcontrollers, reduced instruction set circuits (RISC), application specific integrated circuits (ASIC), logic circuits, and any other circuit or processor capable of executing the functions described herein.
As used herein, the terms “software” and “firmware” are interchangeable, and include any computer program stored in memory for execution by processor 205, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are exemplary only, and are thus not limiting as to the types of memory usable for storage of a computer program.
As will be appreciated based on the foregoing specification, the above-described embodiments of the disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof, wherein the technical effect includes (a) storing a plurality rule sets in the memory device, the rule sets relative to the auxiliary systems of the gas turbine, the rule sets including at least one rule expressed as a relational expression of a real-time data output relative to a real-time data input, the relational expression being specific to parameters associated with the auxiliary systems of the gas turbine, (b) receiving real-time and historical data inputs from a condition monitoring system associated with the gas turbine, the data inputs relating to process parameters associated with the auxiliary systems of the gas turbine, and (c) estimating values for at least some of the parameters associated with the auxiliary systems of the gas turbine using the received inputs. Any such resulting program, having computer-readable code means, may be embodied or provided within one or more computer-readable media, thereby making a computer program product, i.e., an article of manufacture, according to the discussed embodiments of the disclosure. The computer readable media may be, for example, but is not limited to, a fixed (hard) drive, diskette, optical disk, magnetic tape, semiconductor memory such as read-only memory (ROM), and/or any transmitting/receiving medium such as the Internet or other communication network or link. The article of manufacture containing the computer code may be made and/or used by executing the code directly from one medium, by copying the code from one medium to another medium, or by transmitting the code over a network.
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays (FPGAs), programmable array logic, programmable logic devices (PLDs) or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
A module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
The above-described embodiments of a method and online auxiliary system monitoring system that includes a rule module provides a cost-effective and reliable means for providing meaningful operational recommendations and troubleshooting actions. Moreover, the system is more accurate and less prone to false alarms. More specifically, the methods and systems described herein can predict component failure at a much earlier stage than known systems to facilitate significantly reducing outage time and preventing trips. In addition, the above-described methods and systems facilitate predicting anomalies at an early stage enabling site personnel to prepare and plan for a shutdown of the equipment. As a result, the methods and systems described herein facilitate operating gas turbines and other equipment in a cost-effective and reliable manner.
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the disclosure is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.
Number | Date | Country | Kind |
---|---|---|---|
CO2012A0008 | Mar 2012 | IT | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2013/054161 | 3/1/2013 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2013/127998 | 9/6/2013 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3898439 | Reed et al. | Aug 1975 | A |
4249238 | Spang, III et al. | Feb 1981 | A |
4449358 | Mani | May 1984 | A |
4969796 | Wescott et al. | Nov 1990 | A |
5271215 | Guillet | Dec 1993 | A |
5761895 | Chu et al. | Jun 1998 | A |
5806299 | Bauermeister et al. | Sep 1998 | A |
6209310 | Kuenzi et al. | Apr 2001 | B1 |
6338240 | Endo et al. | Jan 2002 | B1 |
6460346 | Cleary | Oct 2002 | B1 |
6530207 | Tobo et al. | Mar 2003 | B2 |
6658091 | Naidoo et al. | Dec 2003 | B1 |
6795798 | Eryurek et al. | Sep 2004 | B2 |
7254491 | Mylaraswamy et al. | Aug 2007 | B2 |
7398182 | Petit | Jul 2008 | B2 |
7702447 | Volponi | Apr 2010 | B2 |
7831704 | Schachtely et al. | Nov 2010 | B2 |
8818684 | John et al. | Aug 2014 | B2 |
20020013664 | Strackeljan et al. | Jan 2002 | A1 |
20020193933 | Adibhatla et al. | Dec 2002 | A1 |
20030041135 | Keyes et al. | Feb 2003 | A1 |
20030053906 | Itou et al. | Mar 2003 | A1 |
20030055534 | Saito et al. | Mar 2003 | A1 |
20030061879 | Otsuka | Apr 2003 | A1 |
20040011056 | Yee et al. | Jan 2004 | A1 |
20040024568 | Eryurek et al. | Feb 2004 | A1 |
20040148129 | Gotoh et al. | Jul 2004 | A1 |
20040148940 | Venkateswaran et al. | Aug 2004 | A1 |
20050033481 | Budhraja et al. | Feb 2005 | A1 |
20050096759 | Benjamin, IV et al. | May 2005 | A1 |
20050240289 | Hoyte et al. | Oct 2005 | A1 |
20060025961 | Appel et al. | Feb 2006 | A1 |
20060031187 | Pyrce et al. | Feb 2006 | A1 |
20060116847 | Plotts et al. | Jun 2006 | A1 |
20060241910 | Petchenev et al. | Oct 2006 | A1 |
20070056387 | Obikawa | Mar 2007 | A1 |
20070104306 | Umezawa et al. | May 2007 | A1 |
20070118270 | Wiseman et al. | May 2007 | A1 |
20070186557 | Gallagher et al. | Aug 2007 | A1 |
20070203669 | Hayashi | Aug 2007 | A1 |
20070234730 | Markham et al. | Oct 2007 | A1 |
20080133679 | Addy | Jun 2008 | A1 |
20080208429 | Saravanapriyan et al. | Aug 2008 | A1 |
20080243352 | Healy | Oct 2008 | A1 |
20090055105 | Yoshida et al. | Feb 2009 | A1 |
20090125206 | Tisenchek et al. | May 2009 | A1 |
20090149972 | Nasle | Jun 2009 | A1 |
20090324389 | Fischetti et al. | Dec 2009 | A1 |
20100024536 | Adibhatla et al. | Feb 2010 | A1 |
20100080685 | Morgan et al. | Apr 2010 | A1 |
20100257838 | Mazzaro et al. | Oct 2010 | A1 |
20100262401 | Pfeifer et al. | Oct 2010 | A1 |
20100290889 | Fedor | Nov 2010 | A1 |
20100324870 | Beckman et al. | Dec 2010 | A1 |
20110062708 | Prochaska et al. | Mar 2011 | A1 |
20110112797 | Nëhse et al. | May 2011 | A1 |
20110162386 | Chandrabose et al. | Jul 2011 | A1 |
20110178737 | Hudson et al. | Jul 2011 | A1 |
20110247406 | Grosse-Laxzen et al. | Oct 2011 | A1 |
20110289899 | De La Cruz Garcia et al. | Dec 2011 | A1 |
20120016824 | Kalinkin et al. | Jan 2012 | A1 |
20120150335 | Prabhu et al. | Jun 2012 | A1 |
20120279230 | Botarelli | Nov 2012 | A1 |
20130098042 | Frealle et al. | Apr 2013 | A1 |
20130103353 | Kloppner | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
1494670 | May 2004 | CN |
1621671 | Jun 2005 | CN |
1690684 | Nov 2005 | CN |
1690685 | Nov 2005 | CN |
1721275 | Jan 2006 | CN |
1892029 | Jan 2007 | CN |
101206160 | Jun 2008 | CN |
101858826 | Oct 2010 | CN |
102027348 | Apr 2011 | CN |
102192985 | Sep 2011 | CN |
102226428 | Oct 2011 | CN |
102252850 | Nov 2011 | CN |
102312728 | Jan 2012 | CN |
102010026678 | Jan 2012 | DE |
0198502 | Oct 1986 | EP |
1556598 | Sep 2006 | EP |
2138726 | Dec 2009 | EP |
2345878 | Jul 2011 | EP |
2085528 | Apr 1982 | GB |
4713023 | Jun 1972 | JP |
572497 | Jan 1982 | JP |
5838329 | Mar 1983 | JP |
60142070 | Jul 1985 | JP |
60216098 | Oct 1985 | JP |
0255807 | Feb 1990 | JP |
03155350 | Jul 1991 | JP |
476232 | Mar 1992 | JP |
0586898 | Apr 1993 | JP |
08189846 | Jul 1996 | JP |
09166029 | Jun 1997 | JP |
2000205563 | Jul 2000 | JP |
2002180851 | Jun 2002 | JP |
2003090297 | Mar 2003 | JP |
2003091313 | Mar 2003 | JP |
2003111475 | Apr 2003 | JP |
2004501465 | Jan 2004 | JP |
2004232643 | Aug 2004 | JP |
2004278395 | Oct 2004 | JP |
2005502021 | Jan 2005 | JP |
2005135422 | May 2005 | JP |
2005135430 | May 2005 | JP |
2005147812 | Jun 2005 | JP |
2005195257 | Jul 2005 | JP |
2006125275 | May 2006 | JP |
2006302293 | Nov 2006 | JP |
2007138937 | Jun 2007 | JP |
2007218254 | Aug 2007 | JP |
2007231804 | Sep 2007 | JP |
2008097643 | Apr 2008 | JP |
2008175149 | Jul 2008 | JP |
2009043266 | Feb 2009 | JP |
2009047092 | Mar 2009 | JP |
2010031842 | Feb 2010 | JP |
2010084764 | Apr 2010 | JP |
2010265901 | Nov 2010 | JP |
2011137448 | Jul 2011 | JP |
2011247265 | Dec 2011 | JP |
2011256734 | Dec 2011 | JP |
2012008782 | Jan 2012 | JP |
2012530975 | Dec 2012 | JP |
2013512381 | Apr 2013 | JP |
2005112459 | Sep 2005 | RU |
2005141148 | May 2006 | RU |
66447 | Sep 2007 | RU |
2010121150 | Dec 2011 | RU |
2010144075 | May 2012 | RU |
0169329 | Sep 2001 | WO |
02103177 | Dec 2002 | WO |
2005041209 | May 2005 | WO |
2005124491 | Dec 2005 | WO |
2011003688 | Jan 2011 | WO |
2011073350 | Jun 2011 | WO |
2011075233 | Jun 2011 | WO |
Entry |
---|
Theilliol et al., “A hierarchical fault diagnosis method using a decision support system applied to a chemical plant”, Systems, man and cybernetics, Intelligent Systems for the 21st Century, IEEE International Conference on Vancouver, BC, Canada, NY, USA, IEEE, US, vol. No. 3, pp. 2205-2210, Oct. 22, 1995. |
Wurzbach, “Infrared Thermography of Fan and Compressor Systems in a Predictive Maintenance Program”, Proceedings SPIE, Thermosense XX, vol. No. 3361, Apr. 13, 1998. |
Bayley, “Flows and temperatures in compressor and turbine wheel spaces”, Proceedings of the Institution of Mechanical Engineers, Part C: Journal of Mechanical Engineering Science, vol. No. 213, Issue No. 5, pp. 451-460, May 1, 1999. |
Gulen et al., “Real-Time On-Line Performance Diagnostics of Heavy-Duty Industrial Gas Turbines”, Journal of Engineering for Gas Turbines and Power, ASME, vol. No. 124, pp. 910-921, Oct. 1, 2002. |
Brooks, “GE Gas Turbine Performance Characteristics”, GE Power Systems, Oct. 31, 2000. |
Davis et al., “Dry Low NOx Combustion Systems for GE Heavy-Duty Gas Turbines”, GE Power Systems, Oct. 31, 2000. |
Search Report and Written Opinion issued in connection with corresponding IT Application No. CO2012A000008 dated Oct. 22, 2012. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054098 dated May 21, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054162 dated Jun. 25, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054158 dated Jul. 1, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054154 dated Jul. 4, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054161 dated Jul. 9, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054157 dated Jul. 19, 2013. |
International Search Report and Written Opinion issued in connection with corresponding PCT Application No. PCT/EP2013/054156 dated Jan. 8, 2014. |
Unofficial English Translation of Chinese Office Action issued in connection with related CN Application No. 201380012020. 4 dated May 23, 2016. |
Notice of Allowance issued in connection with related U.S. Appl. No. 14/382,036 dated Oct. 21, 2015. |
Unofficial English translation of Office Action issued in connection with related CN Application No. 201380011998.9 dated Dec. 25, 2015. |
Unofficial English Translation of Chinese Office Action issued in connection with corresponding CN Application No. 201380011941.9 dated Jan. 25, 2016. |
Unofficial English Translation of Chinese Office Action issued in connection with related CN Application No. 201380012000.7 dated Feb. 3, 2016. |
Hui-Ming, “Analysis and Handling of the Combustion Fault in a S109FA Gas Turbine”, Power Equipment, vol. No. 25, Issue No. 5, pp. 331-335, Sep. 2011. |
Unofficial English translation of Office Action issued in connection with related CN Application No. 201380012462.9 dated Apr. 1, 2016. |
Unofficial English translation of Office Action issued in connection with related CN Application No. 201380012036.5 dated Feb. 22, 2016. |
Russian Search Report issued in connection with Related RU Application No. 2014133939 dated Dec. 13, 2016. |
Russian Search Report issued in connection with corresponding RU Application No. 2014133935 dated Dec. 14, 2016. |
Russian Search Report issued in connection with Related RU Application No. 2014133942 dated Dec. 14, 2016. |
Russian Notice of Acceptance issued in connection with corresponding RU Application No. 2014133935 dated Dec. 29, 2016. |
Russian Notice of Acceptance issued in connection with Related RU Application No. 2014133939 dated Dec. 29, 2016. |
Unofficial English Translation of Russian Office action issued in connection with related RU Application No. 2014133941 dated Jan. 12, 2017. |
Unofficial English Translation of Japanese Office action issued in connection with related JP Application No. 2014559227 dated Jan. 24, 2017. |
Russian Office action issued in connection with related RU Application No. 2014134207 dated Jan. 24, 2017. |
Unofficial English Translation of Japanese Search Report issued in connection with related JP Application No. 2014559227 dated Feb. 1, 2017. |
U.S. Appl. No. 14/382,036, filed Aug. 29, 2014, Ali et al. |
U.S. Appl. No. 14/382,013, filed Aug. 29, 2014, Ceccherini et al. |
U.S. Appl. No. 14/382,063, filed Aug. 29, 2014, Saravanapriyan et al. |
U.S. Appl. No. 14/382,049, filed Aug. 29, 2014, Fadlun et al. |
U.S. Appl. No. 14/382,076, filed Aug. 29, 2014, Giannini et al. |
U.S. Appl. No. 14/382,030, filed Aug. 29, 2014, Saravanapriyan et al. |
Unofficial English Translation of Chinese Office Action issued in connection with corresponding CN Application No. 201380011941.9 dated Oct. 17, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with Related JP Application No. 2014-559240 dated Nov. 8, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with Related JP Application No. 2014559241 dated Nov. 8, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with Related JP Application No. 2014559243 dated Nov. 22, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with Related JP Application No. 2014559246 dated Nov. 22, 2016. |
Unofficial English Translation of Japanese Search Report issued in connection with Related JP Application No. 2014559240 dated Nov. 30, 2016. |
Unofficial English Translation of Japanese Search Report issued in connection with Related JP Application No. 2014559241 dated Nov. 30, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with Related JP Application No. 2014559242 dated Dec. 6, 2016. |
Unofficial English Translation of Japanese Office Action issued in connection with corresponding JP Application No. 2014559245 on Dec. 6, 2016. |
Unofficial English Translation of Japanese Search Report issued in connection with Related JP Application No. 2014559242 dated Dec. 22, 2016. |
Unofficial English Translation of Japanese Search Report issued in connection with corresponding JP Application No. 2014559245 dated Dec. 22, 2016. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 14/382,030 dated Apr. 14, 2017. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 14/382,013 dated May 5, 2017. |
Unofficial English Translation of Chinese Notice of Allowance issued in connection with related CN Application No. 201380012462.9 dated Jun. 8, 2017. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 14/382,076 dated Aug. 9, 2017. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 14/382,049 dated Sep. 5, 2017. |
Number | Date | Country | |
---|---|---|---|
20150013440 A1 | Jan 2015 | US |