Patent Grant
9665090
The subject matter disclosed herein relates to reliability operations, and more specifically, to controller reliability operations.
Control systems, including industrial control systems, may include a variety of components and subsystems participating in a process. For example, a controller may include one or more processors, I/O subsystems, a memory, and the like. The controller may be operatively coupled to a variety of systems and used, for example, to control an industrial process. However, control systems may be complex, including numerous interrelated components and subsystems. Accordingly, recognizing or predicting a reliability of control system operations may be difficult and time-consuming.
Certain embodiments commensurate in scope with the originally claimed invention are summarized below. These embodiments are not intended to limit the scope of the claimed invention, but rather these embodiments are intended only to provide a brief summary of possible forms of the invention. Indeed, the invention may encompass a variety of forms that may be similar to or different from the embodiments set forth below.
In a first embodiment, a system includes a data collection system configured to collect a data from a control system. The system further includes a configuration management system configured to manage a hardware configuration and a software configuration for the control system based on the data. The system additionally includes a rule engine configured to use the data as input and to output a health assessment by using a rule database configured to store at least one rule, and a report generator configured to provide a health assessment for the control system. The system also includes a rule editor configured to create the at least one rule, update the at least one rule, delete the at least one rule, or a combination thereof.
In a second embodiment, a method includes inputting at least one control system health assessment rule by using a rule editor, and acquiring a data related to a control system. The method further includes analyzing the data. The method additionally includes analyzing the data to obtain a data analysis by using the at least one control system health assessment rule, and deriving a control system health assessment based on the data analysis.
In a third embodiment, a system includes a non-transitory machine readable medium storing code configured to insert a rule, update the rule, delete the rule, or a combination thereof. The code is additionally configured to acquire a data related to a control system and to analyze the acquired data to obtain a data analysis by using the rule. The code is further configured to derive a control system health assessment based on the data analysis.
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
One or more specific embodiments of the present invention will be described below. In an effort to provide a concise description of these embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
When introducing elements of various embodiments of the present invention, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.
In certain embodiments, control of operations for an industrial process and associated machinery may be provided by a control system. In these embodiments, the control system may be implemented as a combination of hardware and software components suitable for receiving inputs (e.g., process inputs), processing the inputs, and deriving certain control actions useful in controlling a machinery or process, such as a power generation process, as described in more detail blow. However, the control system may not be as reliable, for example, due to older hardware and software.
Certain corrective maintenance (CM) techniques may be used, useful in repairing or updating the controller after an unexpected maintenance event. However, because the CM techniques are typically applied after the unexpected event, the controlled process may be stopped until the control system is brought back to a desired operating condition. The novel techniques described herein, including prognostic health monitoring (PHM) techniques, may enable a preventative or predictive approach in which control system issues may be identified prior to their occurrence. Accordingly, maintenance actions, such as control system upgrades, part replacements, supply chain order placement, and the like, may be performed in advance, and the control system may be maintained in an operational status for a longer duration. Indeed, stoppages of the controlled process and associated machinery may be substantially minimized or eliminated.
In certain embodiments, rule-based systems and methods, including a rules editor and a method for using the rules editor, may be included, for example, in a controller health advisor suite of software tools, and used to analyze and derive a health assessment for the control system. The health assessment may include a controller readiness, controller recommendations (e.g., upgrade recommendations, parts replacement recommendations, parts ordering recommendations), a configuration report, early warning reports (e.g., early warning outage reports), and access based reports (e.g., role-based access reports). The health advisor suite may additionally include online and offline components, useful in performing the health assessment while the health advisor suite is communicatively coupled either directly to the control system, or coupled indirectly to the control system. Additionally, the health assessment may be provided in real-time or near real-time. The health assessment may be derived continuously and used to update or improve the control system, thus providing for an up-to-date prognosis of the health of the control system.
With the foregoing in mind and turning now to
The health advisor system 10 may include a health advisor database 16, a health advisor suite (e.g., suite of software and/or hardware tools) 18, and a knowledge base 20. The health advisor database 16 may store, for example, rule-based information detailing expert knowledge on the workings and possible configurations of the control system 12, as well as knowledge useful in making deductions or predictions on the health of the control system 12. For example, the health advisor database 16 may include expert system rules (e.g., forward chained expert system, backward chained expert system), regression models (e.g., linear regression, non-linear regression), fuzzy logic models (e.g., predictive fuzzy logic models), and other predictive models (e.g., Markov chain models, Bayesian models, support vector machine models) that may be used to predict the health, the configuration, and/or the probability of occurrence of undesired maintenance events (e.g., failure of a power supply, failure of a processor core, failure of an input/output [I/O]) pack, insufficient memory, loose bus connection) related to the control system 12.
The knowledge base 20 may include one or more answers to control system 12 questions or issues, including answers relating to controller configurations, unexpected problems, known hardware or software issues, service updates, and/or user manuals. The knowledge base 20 may additionally include operating history details of the plant 14 and equipment related to the plant 14 (e.g., turbine system 68, valve 72, pump 74). The health advisor suite 18 may update the knowledge base 20 based on new information, such as a control system health assessment 24. Additionally, an online life cycle support tool 22 is provided. The online life cycle support tool 22 may use the health advisor suite 18 and the knowledge base 20 to provide support to customers 26 of the power plant 14. For example, the customers 26 may connect to the online life cycle support tool 22 by using a web browser, a client terminal, a virtual private network (VPN) connection, and the like, and access the answers provided by the knowledge base 20, as well as the health advisor suite 18 and/or the health assessment 24, through the online life cycle support tool 22.
The online life cycle support tool 22 may similarly be used by other entities, such as a contract performance manager (CPM) tasked with administrating contractual services delivered to the plant 14, and/or a technical assistant (TA) tasked with providing information technology and/or other system support to the plant 14. For example, the plant 14 may be provided with contractual maintenance services (e.g., inspections, repairs, refurbishments, component replacements, component upgrades), service level agreements (SLAs), and the like, supported by the CPM and the TA.
The health assessment 24 may be used, for example, to enable a new product introduction (NPI) 28 and/or a root cause analysis (RCA) 30. For example, issues found in the health assessment 24 may aid in identifying issues related to the introduction (e.g., NPI 28) of a new hardware or software component for the control system 12, or the introduction of a newer version of the control system 12. The identified issues may then be used to derive the RCA 30. For example, the health advisor suite 18 may use techniques such as fault tree analysis, linear regression analysis, non-linear regression analysis, Markov modeling, reliability block diagrams (RBDs), risk graphs, and/or layer of protection analysis (LOPA). The RCA 30 may then be used to re-engineer or otherwise update the control system 12 to address any issues found.
The health assessment 24 and/or the knowledge base 20 may also be used to derive engineering opportunities 32 and revenue opportunities 34. For example, controller usage patterns (processor usage, memory usage, network usage, program logs), issues found, frequently asked questions, and the like, may be used to derive engineering changes for the control system 12. The engineering changes may include changing memory paging schemes, memory allocation algorithms, applying CPU optimizations (e.g., assigning process priorities, assigning thread priorities), applying programming optimization (e.g., identifying and rewriting program bottlenecks, using improved memory allocation, using processor-specific instructions), applying networking optimizations (e.g., changing transmit/receive rates, frame sizes, time-to-live (TTL) limits), and so on.
Revenue opportunities 34 may also be identified and acted on. For example, the health assessment 24 may detail certain upgrades to the control system 12 based on a desired cost or budget structure, suitable for improving the performance of the control system 12. Upgrades may include software and or hardware updates, such as newer versions of a distributed control system (DCS), a manufacturing execution system (MES), a supervisor control and data acquisition (SCADA) system, a human machine interface (HMI) system, an input/output system (e.g., I/O pack), a memory, processors, a network interface, a power supply, and/or a communications bus. By using the heath advisor suite 18 to derive the health assessment 24, the techniques described herein may enable a more efficient and safe power plant 14, as well as minimize operating costs.
The health advisor 18 may be communicatively coupled to the computer system 36 through direct or indirect techniques. For example, a signal conduit (e.g., cable, wireless router) may be used to directly couple the health advisor 18 to the computer 38. Likewise, a file transfer mechanism (e.g., remote desktop protocol (rdp), file transfer protocol (ftp), manual transfer) may be used to indirectly send or to receive data, such as files. Further, cloud 50 computing techniques may be used, where the health advisor 18 resides in the cloud 50 and communicates directly or indirectly with the computer system 36.
The health advisor suite 18 may include a data collection subsystem 54, a configuration management system 56, and a rule engine 60. In certain embodiments, the data collection subsystem 54 may collect and store data, such as data representative of the status, health, and operating condition of the control system 12. The data collection subsystem 54 may be continuously operating, and may include relational databases, network databases, files, and so on, useful in storing and updating stored data. The configuration management system 56 may be used to manage the various configurations of software and/or hardware components used in constructing the control system 12. Indeed, the control system 12 may include multiple software and/or hardware components, each component having one or more versions. These versioned components may be packaged by a manufacturer into the control system 12 as part of a contract services agreement, and/or may be provided as part of a transactional services agreement (e.g., purchased individually). The rule engine 58 may be used to enable the derivations of the health assessment 24, as described in more detail below with respect to
Further, the computer system 36 and the health advisor 18 may be communicatively connected to a plant data highway 60 suitable for enabling communication between the depicted computer 36 and other computers 36 and/or health advisors 18. Indeed, the industrial control system 12 may include multiple computer systems 36 interconnected through the plant data highway 60, or through other data buses (e.g., local area networks, wide area networks). In the depicted embodiment, the computer system 36 and the health advisor 18 may be further communicatively connected to a unit data highway 62, suitable for communicatively coupling the computer system 36 and the health advisor 18 to an industrial controller system 64. In other embodiments, other data buses (e.g., direct cabling, local area networks, wide area networks) may be used to couple the computer system 36 and the health advisor 18 to the industrial controller 64.
The industrial controller 64 may include a processor 66 suitable for executing computer instructions or control logic useful in automating a variety of plant equipment, such as a turbine system 68, a temperature sensor 70, a valve 72, and a pump 74. The industrial controller 64 may further include a memory 76 for use in storing, for example, control code (e.g., computer instructions and other data). For example, the controller 64 may store one or more function blocks written in an International Electrotechnical Commission (IEC) 61804 language standard, sequential function charts (SFC), ladder logic, or programs written in other programming languages, in the control code. In one embodiment, the control code may be included in a configuration file 65. Additionally or alternatively, the configuration file 65 may include configuration parameter for the controller, such as instantiated function blocks (e.g., function blocks to load into memory), networking parameters, code synchronization and timing, I/O configuration, and so on.
The industrial controller 64 may communicate with a variety of field devices, including but not limited to flow meters, pH sensors, temperature sensors, vibration sensors, clearance sensors (e.g., measuring distances between a rotating component and a stationary component), pressure sensors, pumps, actuators, valves, and the like. In some embodiments, the industrial controller 64 may be a triple modular redundant (TMR) Mark™ VIe controller system, available from General Electric Co., of Schenectady, N.Y. By including three processors, the TMR controller 64 may provide for redundant or fault-tolerant operations. In other embodiments, the controller 64 may include a single processor, or dual processors.
In the depicted embodiment, the turbine system 68, the temperature sensor 70, the valve 72, and the pump 74 are communicatively connected to the industrial controller 64 and/or the health advisor 18 by using linking devices 78 and 80 suitable for interfacing between an I/O network 82 and an H1 network 84. For example, the linking devices 78 and 80 may include the FG-100 linking device, available from Softing AG, of Haar, Germany. Additional field devices 86 (e.g., sensors, pumps, valves, actuators) may be communicatively coupled via the I/O network 82 to the controller 64 and/or the health advisor 18, for example, by using one or more input/output (I/O) packs 88. The I/O packs 88 may each include a microprocessor 90 useful in executing a real-time operating system, such as QNX® available from QNX Software Systems/Research in Motion (RIM) of Waterloo, Ontario, Canada. Each I/O pack 88 may also include a memory 92 for storing computing instructions and other data, as well as one or more sensors 94, such as temperature sensors, useful in monitoring the ambient temperature in the I/O packs 88. In other embodiments, the turbine system 68, the temperature sensor 70, the valve 72, the pump 74, and/or the field devices 86, may be connected to the controller 64 and/or the health advisor 18 by using direct cabling (e.g., via a terminal block) or indirect means (e.g., file transfers).
As depicted, the linking devices 78 and 80 may include processors 96 and 98, respectively, useful in executing computer instructions, and may also include memory 100 and 102, useful in storing computer instructions and other data. In some embodiments, the I/O network 82 may be a 100 Megabit (MB) high speed Ethernet (HSE) network, and the H1 network 84 may be a 31.25 kilobit/second network. Accordingly, data transmitted and received through the I/O network 82 may in turn be transmitted and received by the H1 network 84. That is, the linking devices 78 and 80 may act as bridges between the I/O network 82 and the H1 network 84. For example, higher speed data on the I/O network 82 may be buffered, and then transmitted at suitable speed on the H1 network 84. Accordingly, a variety of field devices may be linked to the industrial controller 64, to the computer 36, and/or to the health advisor 18. For example, the field devices 68, 70, 72, and 74 may include or may be industrial devices, such as Fieldbus Foundation™ devices that include support for the Foundation H1 bi-directional communications protocol. The field devices 68, 70, 72, 74, and 86 may also include support for other communication protocols, such as those found in the HART® Communications Foundation (HCF) protocol, and the Profibus Nutzer Organization e.V. (PNO) protocol.
The site software 108 may include all software (e.g., software tools, operating systems, networking software, firmware, microcode, display drivers, sound drivers, network drivers, I/O system drivers) used by the components of the control system 12 of
The rules 110 may include “if . . . then . . . ” rules with the “if” portion set as an antecedent condition, and the “then” portion set as a consequent of the antecedent condition. The rules may also include fuzzy logic rules, expert system rules (e.g., forward chained expert systems, backward chained expert systems), recursive rules (e.g., Prolog rules), Bayesian inference rules, dynamic logic rules (e.g., modal logic), neural network rules, genetic algorithm rules, or a combination thereof. The rules may be derived through consultation with one or more experts in the field, such as a controller system health experts, or automatically, such as by using machine learning techniques (e.g., reinforcement learning, decision tree learning, inductive logic programming, neural network training, clustering, support vector machine).
The rules 110 may created by using a rules editor 111. In one embodiment, the rules editor 111 may be included as part of the health advisor suite 18. In another embodiment, the rules editor 111 may be provided separate from the health suite 18. The rules editor 111 may include computer instructions stored in a non-transitory machine readable medium, such as the memory of a computer, a tablet, a notebook, a workstation, a cell phone, and/or other computing device. In the depicted embodiment, the rule editor 111 may be used to create, update, and/or delete, one of more of the rules 110. For example,
The process dynamics 112 may include data received when the health advisor 18 is communicatively coupled to the control system 12. The process dynamics 112 data may include alerts issued by the controller 64, and/or the HMI 42, the MES 44, the DCS 46, the SCADA 48. Likewise, the process dynamics 112 may include utilization data (e.g., percent utilization, total utilization) for the memories 40, 76, 92, 100, 102, utilization data for the processors 38, 66, 90, 96, 98 (e.g., utilization by software processes, utilization by software applications), current configuration parameters used by the components of the control system 12 (e.g., memory page size, virtual memory pages, thread priority, process priority) controller 64 parameters (e.g., master/slave configuration, I/O parameter), bus 60, 62, and 84 parameters, I/O pack 88 parameters, linking device 78, 80 parameters, field device 68, 70, 72, 74, 86 parameters.
In the depicted embodiment, the health advisor suite 18 includes online 114 and offline 116 operational modes, which may be used alone or in combination with each other. In the online mode 114 of operations, the health advisor may be constantly receiving the inputs 106, for example, by using the data collection subsystem 54 of the health advisor suite 18, then processing the inputs 106, for example, by using the configuration management 56 and rule engine 58 of the health advisor suite 18, to produce the health assessment 24. In the offline mode 116 of operations, the inputs 106 may be provided, for example, as a set of files or as a “batch job.” That is, the files or “batch job” may be provided to the data collection subsystem 54 as pre-collected data, which may be subsequently used to produce the health assessment 24. By providing for the offline mode 116, the health advisor suite 18 may be used, for example, in a computing device that may be disconnected from the controller system 12. User input 118 is also depicted. The user input 118 may include data related to the control system 12 and manually entered by the user. Additionally, the user input 118 may include usage input (e.g., keyboard, mouse, voice) directing the health advisor 18 to perform certain desired operations, such as operations deriving the health assessment 18, including a TMR readiness report 120, a recommendation report 122, an auto configuration report 124, early warnings 126, and/or access-based reports 128.
The TMR readiness report 120 may detail the condition of the TMR controller 64, including any detected fault conditions, alarm reports based on alarm logging data, error reports based on error logging data, and may also derive an overall readiness metric by using the inputs 106. For example, the readiness metric may detail an approximate percentage readiness (0%-100%) for the overall control system 12, as well as for each component of the control system 12. A higher number for the percentage readiness may indicate that the control system 12 (or component) is more suitable for continued operations, while a lower number for the percentage readiness may indicate that the control system 12 (or component) is less suitable for continued operations. The percentage readiness may be derived by using certain of the rules 110 focused on determining the overall operational health of the control system 12 (or component). The percentage readiness may also be found by using a statistical or historical analysis based on the inputs, such as a Poisson distribution model, linear regression analysis, non-linear regression analysis, Weibull analysis, fault tree analysis, Markov chain modeling, and so on.
The recommendation report 122 may include recommendations on improvements for the control system 12. For example, certain hardware and software upgrades or additions may be recommended. The hardware upgrades may include memory upgrades, network equipment upgrades, processor upgrades, replacement of components of the control system 12, replacement of cabling, replacement of power supplies, and so on. The recommendations may also include adding certain component and related subsystems, for example to enable faster control and/or faster processing of data. The software recommendations may include upgrading or replacing the software components of the control system 12 (e.g., HMI 42, MES, 44, DCS 46, SCADA 48), operating systems, software tools, firmware, microcode, applications, and so on.
The auto configuration report 124 may include details of the configuration of the control system 12. The configuration details may include a list of all software and hardware components used by the control system 12, including details of the components 36, 38, 40, 42, 44, 46, 48, 50, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98, 100, and/or 102. The details may include the number of each of the aforementioned components used by the control system 12, version information for each components (hardware version, firmware version, software version, microcode version), interconnections between component (e.g., network diagram, electronic circuit diagrams, information flow diagrams, programming flowcharts, database diagrams), procurement information (cost, delivery times, supplier information).
The early warning report 126 may include a list of issues that may lead to undesired conditions, such as unexpected maintenance events or stoppage of the control system 12. For example, the early warning report 126 may include issues such as insufficient memory 40, 76, 92, 100, 102, loss of redundancy of the controller 64, low bandwidth capacity of the buses 60, 62, 84, insufficient processing power for the processors 38, 66, 90, 96, 98, failure of any of the components 36, 38, 40, 42, 44, 46, 48, 50, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98, 100, and 102, software errors, hardware errors, and so on.
The access based reports 128 may be reports accessible by certain roles, such as system administrators, plant operators, commissioning engineers, managers, programmers, control engineers, procurement personnel, accounting personnel, and so on, and useful in performing the jobs associated with the aforementioned roles. In one embodiment, the access based reports 128 may be based on the data used in the reports 120, 122, 124, and/or 126 focused on the desired role. For example, a control engineer role may receive a report 128 based on all of the data used in the reports 120, 122, 124, and 126, while a procurement based report 128 may distil the data and present data relevant to procurement activities (e.g., manufacturing information, cost information, delivery time information). In this manner, data from the reports 120, 122, 124, and 126 may be distilled and used to more efficiently support roles such as system administrators, plant operators, commissioning engineers, managers, programmers, control engineers, procurement personnel, accounting personnel.
The process 130 may acquire data (block 132), such as the inputs 106, related to the control system 12. As previously mentioned, the data may be acquired directly (e.g., through a cable or other conduit), or indirectly (e.g., through files loaded onto a storage medium, such as a CD, DVD, flash card, thumb drive). The acquired data may then be analyzed (block 134). For example, the health assessment suite 18 may use the rule engine 58 and rules 110 to analyze the data. Other techniques including statistical and historical analysis techniques may also be used, such as fault tree analysis, linear regression analysis, non-linear regression analysis, Markov modeling, RBDs, risk graphs, LOPA, Poisson distribution model, Weibull analysis, and/or Markov chain modeling.
The process 130 may then derive (block 136) the control system health assessment 24, for example, by using the control system health assessment suite 18 as described above. The health assessment 24 may then be provided (block 138), to the control system 12 operator and/or manufacturer and to user roles (e.g., system administrators, plant operators, commissioning engineers, managers, programmers, control engineers, procurement personnel, accounting personnel), as well as stored in, for example, the knowledge base 20 accessible by the online life cycle support tool 22. As mentioned previously, the health assessment report may include the TRM readiness report 120, the recommendation report 122, the auto configuration report 124, the early warning report 126, and the access based report 128.
The process 130 may then use the provided reports 120, 122, 124, 126, and/or 128 to improve (block 140) the control system 12 and/or the plant 14. For example, components of the control system 12 may be replaced, added, or upgraded. Likewise, NPI 28 and RCA 30, engineering opportunities 32 and/or revenue opportunities 34 may be derived and used to more efficiently and safely operate the control system 12 and/or plant 14.
Turning to
The drop box 154 may include an electronic mailbox (e.g., email folder), a post office mailbox, an online drop box (e.g., file transfer protocol [hp] folder), and so on. A requestor 156 may then submit (block 158) a workflow request. In one embodiment, the requestor 156 may be an automated agent or other software implemented by using computer instructions stored in a non-transitory machine-readable medium. In another embodiment, the requestor 156 may be a human person, such as the customer 26, a manufacturer representative, plant engineer, controls engineer, commissioning engineer, and/or programmer. The workflow submission (block 158) may request that an approver 160 aid in addressing issues, including but not limited to the issues submitted in block 152. Indeed, the requestor 156 may submit (block 158) workflows addressing any issues related to the control system 12 and equipment communicatively or operatively connected to the control system 12. The approver 160 may include or may use computer instructions stored in a non-transitory machine-readable medium, including software agents useful in automatically approving or disapproving (decision 162) the submitted workflow requests.
If the approver 160 does not approve (decision 162) the workflow, then the requestor 156 may be notified (block 164) of the rejection. If the approver 160 approves (decision 162) the workflow, then the rule editor 111 may be used to create (block 166) a health advisor (HA) rule, such as a rule to be included in the rules 110. As mentioned previously, the rules 110 may include any type of rule, including “if . . . then . . . ” rules, fuzzy logic rules, expert system rules (e.g., forward chained expert systems, backward chained expert systems), recursive rules (e.g., Prolog rules), Bayesian inference rules, dynamic logic rules (e.g., modal logic), neural network rules, genetic algorithm rules, or a combination thereof. In certain embodiments, experts having knowledge of the control system 12 and related equipment (e.g., turbine system 68) may be consulted during the creation (block 166) of the rules. For example, tacit knowledge extraction techniques, such as field-oriented interviews, structured interviews, unstructured interviews, analysis of the expert diagnosing the control system 12, and so on, may be used to derive the rules 110. The rules 110 may then be stored in various structured formats, including extensible markup language (XML) files, resource description framework (RDF) files, web ontology language (OWL) files, relational database tables, binary files, flat files, and so forth. For example, a rule may be written in XML as follows:
The rule includes sections for capturing the rule name, a brief description of an issue associated with the rule, a full description of the issue, a recommendation to fix or address the issue, a compliance code, a timing date, a uniform resource locator (URL) associated with the rule, a condition type for the rule, a sequence for the rule, and/or a permutation (e.g., version information) for equipment related to the rule.
The created rule (block 166) may then be used during unit testing (block 168). For example, the rule may be tested to provide for adequate syntax, representation, and execution by the rule engine 58. After the unit testing (block 168), the rule may then be published (block 170), for use, for example, during a beta release. During publication (block 170), the rule may be stored, for example, in the beta testing database. The rule may then be tested (block 172), for example, by one or more testers 174. The testers 174 may include computer instructions stored in a non-transitory machine-readable medium, such as quality assurance code, automatic testing code, and the like, useful in automatically testing the published (block 170) HA rule.
The process 150 may then determine (decision 178) if the HA rule passes beta testing. For example, the rule may not cover a desired scope, or may not adequately cover a desired issue or set of issues. If it is determined (decision 178) that the HA rule does not pass beta testing, then the process 150 may iterate back to block 166 and re-create the HA rule. If it is determined (decision 178) that the HA rule passes beta testing, then the HA rule may be released (block 178), for example, into the health advisor database 16 as a Charlie version. This Charlie version of the HA rule may then be further exposed to testing, including customer 26 testing, and eventually leave the Charlie version as a full HA rule and incorporated into the rules 110 used by the rule engine 58.
Additionally, a recommendation portion 190 (e.g., text box) may be used to enter one or more recommendations for the rule, and a compliance portion 192 (e.g., text box) may be used to enter a compliance data for the rule. Further, a timing portion 194 (e.g., text box) may be used to enter timing information, and a uniform resource locator (URL) portion 196 (e.g., text box) may be used to enter internet and/or intranet information for the rule. The frame portion 198 (e.g., text box) may be used to enter equipment related information, such as a turbine system 68 frame information. Once the user has entered the desired rule information, an update facility 200 (e.g., button) may be used to save the rule's information.
As mentioned previously, the rule may be stored in a hierarchical language, such as XML. Accordingly, each level in the hierarchy may include corresponding details suitable for data entry by using the screen 180. As an example,
Technical effects of the invention include the online and offline gathering of control system information. The gathered control system information may then be used to derive a control system health assessment, for example, by using a rule engine communicatively coupled to a health assessment database. The rules in the rule engine may be edited by using a rule editor. The health assessment may include a triple modular redundant (TMR) readiness report, a controller recommendation, an auto configuration report, an early warning report, an access based report, or a combination thereof, suitable for improving and/or optimizing the control system.
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 invention 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 language of the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4051669 | Yannone et al. | Oct 1977 | A |
| 4116052 | Paluka | Sep 1978 | A |
| 4607256 | Henzel | Aug 1986 | A |
| 4642782 | Kemper et al. | Feb 1987 | A |
| 4649515 | Thompson et al. | Mar 1987 | A |
| 5508897 | Van Order | Apr 1996 | A |
| 5508997 | Katou | Apr 1996 | A |
| 5634008 | Gaffaney et al. | May 1997 | A |
| 6006171 | Vines et al. | Dec 1999 | A |
| 6188962 | Morgan et al. | Feb 2001 | B1 |
| 6199018 | Quist et al. | Mar 2001 | B1 |
| 6268853 | Hoskins et al. | Jul 2001 | B1 |
| 6356199 | Niziolek et al. | Mar 2002 | B1 |
| 6556950 | Schwenke et al. | Apr 2003 | B1 |
| 6615090 | Blevins et al. | Sep 2003 | B1 |
| 6618856 | Coburn et al. | Sep 2003 | B2 |
| 6633782 | Schleiss et al. | Oct 2003 | B1 |
| 6654915 | Lu et al. | Nov 2003 | B1 |
| 6671659 | Troia et al. | Dec 2003 | B2 |
| 6738683 | Dunn | May 2004 | B1 |
| 6862553 | Schwenke et al. | Mar 2005 | B2 |
| 6931288 | Lee et al. | Aug 2005 | B1 |
| 6934696 | Williams et al. | Aug 2005 | B1 |
| 6990432 | McCarthy, IV et al. | Jan 2006 | B1 |
| 6993456 | Brooks et al. | Jan 2006 | B2 |
| 7089452 | Rubin et al. | Aug 2006 | B2 |
| 7092771 | Retlich et al. | Aug 2006 | B2 |
| 7146232 | Staron et al. | Dec 2006 | B2 |
| 7162695 | Zemore et al. | Jan 2007 | B2 |
| 7213065 | Watt | May 2007 | B2 |
| 7228187 | Tichy et al. | Jun 2007 | B2 |
| 7266476 | Coburn et al. | Sep 2007 | B2 |
| 7305272 | Maturana et al. | Dec 2007 | B2 |
| 7324856 | Bromley | Jan 2008 | B1 |
| 7395188 | Goebel et al. | Jul 2008 | B1 |
| 7451351 | Gunnmarker et al. | Nov 2008 | B2 |
| 7509537 | Jensen | Mar 2009 | B1 |
| 7546232 | Brooks et al. | Jun 2009 | B2 |
| 7640291 | Maturana et al. | Dec 2009 | B2 |
| 7702487 | Sherrill et al. | Apr 2010 | B2 |
| 7729886 | Sherrill et al. | Jun 2010 | B2 |
| 7729887 | Sherrill et al. | Jun 2010 | B2 |
| 7774293 | Mosleh et al. | Aug 2010 | B2 |
| 7797141 | O'Connell et al. | Sep 2010 | B2 |
| 7840336 | Muramatsu et al. | Nov 2010 | B2 |
| 7870379 | Krieger et al. | Jan 2011 | B2 |
| 7953844 | Deshpande | May 2011 | B2 |
| 8250914 | Sullivan | Aug 2012 | B2 |
| 8260441 | Scheegabeta et al. | Sep 2012 | B2 |
| 8312040 | Nyman | Nov 2012 | B2 |
| 8392371 | Lam | Mar 2013 | B2 |
| 8437904 | Mansouri et al. | May 2013 | B2 |
| 20010054095 | Kampe et al. | Dec 2001 | A1 |
| 20020035495 | Spira et al. | Mar 2002 | A1 |
| 20020066054 | Jaw et al. | May 2002 | A1 |
| 20020077849 | Baruch et al. | Jun 2002 | A1 |
| 20020108074 | Shimooka et al. | Aug 2002 | A1 |
| 20020120921 | Corburn et al. | Aug 2002 | A1 |
| 20020123864 | Eryurek et al. | Sep 2002 | A1 |
| 20020169734 | Giel et al. | Nov 2002 | A1 |
| 20030126202 | Watt | Jul 2003 | A1 |
| 20030182083 | Schwenke et al. | Sep 2003 | A1 |
| 20030231200 | Zemore et al. | Dec 2003 | A1 |
| 20040073404 | Brooks et al. | Apr 2004 | A1 |
| 20040073843 | Dean et al. | Apr 2004 | A1 |
| 20040098148 | Retlich et al. | May 2004 | A1 |
| 20040153437 | Buchan | Aug 2004 | A1 |
| 20040204772 | Maturana et al. | Oct 2004 | A1 |
| 20040205412 | Staron et al. | Oct 2004 | A1 |
| 20040250168 | Tichy et al. | Dec 2004 | A1 |
| 20040268186 | Maturana et al. | Dec 2004 | A1 |
| 20050015680 | Rubin et al. | Jan 2005 | A1 |
| 20050278670 | Brooks et al. | Dec 2005 | A1 |
| 20060026035 | Younkes et al. | Feb 2006 | A1 |
| 20060126608 | Pereira et al. | Jun 2006 | A1 |
| 20060174051 | Lordi | Aug 2006 | A1 |
| 20070078628 | Virji et al. | Apr 2007 | A1 |
| 20070088570 | Shetty et al. | Apr 2007 | A1 |
| 20070093988 | Chakraborty et al. | Apr 2007 | A1 |
| 20070226543 | Young et al. | Sep 2007 | A1 |
| 20080141072 | Kalgren et al. | Jun 2008 | A1 |
| 20090055676 | Wiebe | Feb 2009 | A1 |
| 20090106589 | Ramacher et al. | Apr 2009 | A1 |
| 20100082125 | Pingel et al. | Apr 2010 | A1 |
| 20100146078 | Wolff et al. | Jun 2010 | A1 |
| 20100146341 | Chen et al. | Jun 2010 | A1 |
| 20100222900 | Kakino et al. | Sep 2010 | A1 |
| 20110040577 | Ward | Feb 2011 | A1 |
| 20110059427 | Hans et al. | Mar 2011 | A1 |
| 20110071692 | D'Amato et al. | Mar 2011 | A1 |
| 20120016607 | Cottrell et al. | Jan 2012 | A1 |
| 20120126539 | Jacob | May 2012 | A1 |
| 20120130553 | Purani et al. | May 2012 | A1 |
| 20120158205 | Hinman et al. | Jun 2012 | A1 |
| 20120159596 | Vandevelde et al. | Jun 2012 | A1 |
| 20120166007 | Jeong et al. | Jun 2012 | A1 |
| 20120266209 | Gooding et al. | Oct 2012 | A1 |
| 20120275899 | Chandler | Nov 2012 | A1 |
| 20130013523 | Herrera campos | Jan 2013 | A1 |
| 20130332383 | Anzai et al. | Dec 2013 | A1 |
| 20140025414 | Worden et al. | Jan 2014 | A1 |
| 20150128293 | Hitomi et al. | May 2015 | A1 |
| 20150186133 | Yarra et al. | Jul 2015 | A1 |
| 20160048125 | Cheta et al. | Feb 2016 | A1 |
| 20160285694 | Maes | Sep 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 100472509 | Mar 2009 | CN |
| 101714273 | May 2010 | CN |
| 102123052 | Jul 2011 | CN |
| 202100437 | Jan 2012 | CN |
| 2947080 | Dec 2010 | FR |
| 0150387 | Jul 2001 | WO |
| 2006138469 | Dec 2006 | WO |
| Entry |
|---|
| GE Industrial Systems GEI-100483A, SPEEDTRONIC™ Mark VI Turbine Control Product Description, pp. 1-22, Jan. 10, 2002. |
| International Search Report and Written Opinion issued from PCT Application No. PCT/US2013/046491 dated Sep. 26, 2013. |
| Khan et al: “Risk-based maintenance: a quantitative approach for maintenance/inspection scheduling and planning”, Journal of Loss Prevention Industries,vol. 16, Issue No. 6, pp. 561-573, Oct. 20, 2013. |
| International Search Report and Written Opinion issued from PCT Application No. PCT/US2013/045353 dated Oct. 2, 2013. |
| International Search Report and Written Opinion issued from PCT Application No. PCT/US2013/050478 dated Jun. 27, 2014. |
| Non-Final Rejection towards related U.S. Appl. No. 13/557,153 dated Jul. 1, 2014. |
| U.S. Appl. No. 13/557,136, filed Jul. 24, 2012, McCarthy et al. |
| U.S. Appl. No. 13/571,148, filed Jul. 24, 2012, McCarthy et al. |
| U.S. Appl. No. 13/557,153, filed Jul. 24, 2012, McCarthy et al. |
| U.S. Appl. No. 13/557,083, filed Jul. 24, 2012, Vendetti et al. |
| Unofficial English translation of CN Office Action issued in connection with corresponding CN Application No. 201380035046.0 on Apr. 1, 2016. |
| Trihedral, “SCADA Workstation Health Monitoring”, VT Scada Software for Monitoring & Control, http://www.trihedral.com/products/vts-hmi-software/systemhealthmonitoring/, pp. 1-2, retrieved on Jun. 16, 2016. |
| Unofficial English translation of CN Office Action issued in connection with corresponding CN Application No. 201380035043.7 dated Sep. 1, 2016. |
| Unofficial English translation of CN Office Action issued in connection with corresponding CN Application No. 201380035084.6 dated Sep. 30, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20140031958 A1 | Jan 2014 | US |
