CA2689219C - Method and system for state encoding - Google Patents
Method and system for state encoding Download PDFInfo
- Publication number
- CA2689219C CA2689219C CA2689219A CA2689219A CA2689219C CA 2689219 C CA2689219 C CA 2689219C CA 2689219 A CA2689219 A CA 2689219A CA 2689219 A CA2689219 A CA 2689219A CA 2689219 C CA2689219 C CA 2689219C
- Authority
- CA
- Canada
- Prior art keywords
- signature
- equipment
- state detector
- pattern
- detector data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
- G05B23/0224—Process history based detection method, e.g. whereby history implies the availability of large amounts of data
- G05B23/0227—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions
- G05B23/0229—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions knowledge based, e.g. expert systems; genetic algorithms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
- G16Z99/00—Subject matter not provided for in other main groups of this subclass
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
- G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
- G06K7/10009—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation sensing by radiation using wavelengths larger than 0.1 mm, e.g. radio-waves or microwaves
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F04—POSITIVE - DISPLACEMENT MACHINES FOR LIQUIDS; PUMPS FOR LIQUIDS OR ELASTIC FLUIDS
- F04B—POSITIVE-DISPLACEMENT MACHINES FOR LIQUIDS; PUMPS
- F04B51/00—Testing machines, pumps, or pumping installations
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01L—MEASURING FORCE, STRESS, TORQUE, WORK, MECHANICAL POWER, MECHANICAL EFFICIENCY, OR FLUID PRESSURE
- G01L19/00—Details of, or accessories for, apparatus for measuring steady or quasi-steady pressure of a fluent medium insofar as such details or accessories are not special to particular types of pressure gauges
- G01L19/06—Means for preventing overload or deleterious influence of the measured medium on the measuring device or vice versa
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01L—MEASURING FORCE, STRESS, TORQUE, WORK, MECHANICAL POWER, MECHANICAL EFFICIENCY, OR FLUID PRESSURE
- G01L23/00—Devices or apparatus for measuring or indicating or recording rapid changes, such as oscillations, in the pressure of steam, gas, or liquid; Indicators for determining work or energy of steam, internal-combustion, or other fluid-pressure engines from the condition of the working fluid
- G01L23/26—Details or accessories
- G01L23/30—Means for indicating consecutively positions of pistons or cranks of internal-combustion engines in combination with pressure indicators
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01L—MEASURING FORCE, STRESS, TORQUE, WORK, MECHANICAL POWER, MECHANICAL EFFICIENCY, OR FLUID PRESSURE
- G01L7/00—Measuring the steady or quasi-steady pressure of a fluid or a fluent solid material by mechanical or fluid pressure-sensitive elements
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B17/00—Systems involving the use of models or simulators of said systems
- G05B17/02—Systems involving the use of models or simulators of said systems electric
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B13/00—Burglar, theft or intruder alarms
- G08B13/02—Mechanical actuation
- G08B13/14—Mechanical actuation by lifting or attempted removal of hand-portable articles
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
- G08B21/18—Status alarms
Abstract
A system comprising at least one piece of equipment; a plurality of sensors adapted to measure one or more operating parameters of the equipment; and a signature generator adapted to encode a plurality of data streams from the sensors into an operating signature for the equipment.
Description
METHOD AND SYSTEM FOR STATE ENCODING
FIELD OF THE INVENTION
[0001] The present disclosure relates to methods and systems for state encoding.
BACKGROUND
FIELD OF THE INVENTION
[0001] The present disclosure relates to methods and systems for state encoding.
BACKGROUND
[0002] U.S. Patent Application Publication 2008/0129507 discloses a method for employing radio frequency (RF) identifier (ID) transponder tags (RFID
tags) to create a unique identifier, termed an RFID signature, for use within a data processing system with respect to a person or an object. An interrogation signal is transmitted toward a person or an object with which a set of one or more RFID tags are physically associated. A first set of RFID
tag identifiers are obtained from an interrogation response signal or signals returned from the set of one or more RFID tags. A mathematical operation is performed on the first set of RFID tag identifiers to generate an RFID
signature value, which is employed as an identifier for the person or the object within the data processing system with respect to a transaction that is performed by the data processing system on behalf of the person or the object. U.S. Patent Application Publication 2008/0129507 is herein incorporated by reference in its entirety.
tags) to create a unique identifier, termed an RFID signature, for use within a data processing system with respect to a person or an object. An interrogation signal is transmitted toward a person or an object with which a set of one or more RFID tags are physically associated. A first set of RFID
tag identifiers are obtained from an interrogation response signal or signals returned from the set of one or more RFID tags. A mathematical operation is performed on the first set of RFID tag identifiers to generate an RFID
signature value, which is employed as an identifier for the person or the object within the data processing system with respect to a transaction that is performed by the data processing system on behalf of the person or the object. U.S. Patent Application Publication 2008/0129507 is herein incorporated by reference in its entirety.
[0003] U.S. Patent Application Publication 2008/0016353 discloses a method and system for verifying the authenticity and integrity of files transmitted through a computer network. Authentication information is encoded in the filename of the file. In a preferred embodiment, authentication information is provided by computing a hash value of the file, computing a digital signature of the hash value using a private key, and encoding the digital signature in the filename of the file at a predetermined position or using delimiters, to create a signed filename. Upon reception of a file, the encoded digital signature is extracted from the signed filename. Then, the encoded hash value of the file is recovered using a public key and extracted digital signature, and compared with the hash value computed on the file. If the decoded and computed hash values are identical, the received file is processed as authentic.
SUMMARY
SUMMARY
[0004] One aspect of the invention provides a system comprising at least one piece of equipment; a plurality of sensors adapted to measure one or more operating parameters of the equipment; and a signature generator adapted to encode a plurality of data streams from the sensors into an operating signature for the equipment.
[0005] Another aspect of the invention provides a method comprising identifying at least one piece of equipment to be monitored; installing a plurality of sensors to measure operating data of the equipment; establishing an operating range for each of the sensors; and creating an encoding key for each of the ranges.
[0006] Other aspects of the invention will be apparent from the following description and the appended claims.
BRIEF DESCRIPTION OF DRAWINGS
BRIEF DESCRIPTION OF DRAWINGS
[0007] Figure 1 shows a schematic diagram of a system in accordance with one or more embodiments of the invention.
[0008] Figure 2 shows an example schematic diagram of a signature in accordance with one or more embodiments of the invention.
[0009] Figures 3A, 3B, 3C show patterns in accordance with one or more embodiments of the invention
[0010] Figures 4-7 show flowcharts in accordance with one or more embodiments of the invention.
[0011] Figures 8A-8B show an example in accordance with one or more embodiments of the invention.
[0012] Figure 9 shows a computer system in accordance with one or more embodiments of the invention.
DETAILED DESCRIPTION
DETAILED DESCRIPTION
[0013] Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.
[0014] In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.
[0015] In general, embodiments of the invention provide a method and system for analyzing equipment using encoded data obtained from the equipment. The data represents the operational conditions of the equipment. The operational conditions may define both conditions internal to the equipment, such as how well the equipment is operating, as well as conditions external to the equipment, such as the environment in which the equipment is operating. State detectors monitoring the equipment are used to obtain unprocessed state detector data values representing the operational conditions. Unprocessed state detector data values from different state detectors may be processed, such as by being mathematically combined, to create processed state detector data values. The different state detector data values, including processed and/or unprocessed state detector data values, are encoded. The encoding is based on whether the value is in a predefined range of values. The ranges are defined based on acceptable limits for the equipment. For example, the range may include a high range, an above normal range, a normal range, a below normal range, and a low range. If value is within the range, then one or more bits are set to indicate that the value is within the range. The bits are concatenated to generate a signature.
Thus, the single signature represents the state of the equipment at a moment in time.
Specifically, a single signature concisely represents which processed and/or unprocessed state detector data values are within acceptable limits and which state detector data values are outside of acceptable limits.
Thus, the single signature represents the state of the equipment at a moment in time.
Specifically, a single signature concisely represents which processed and/or unprocessed state detector data values are within acceptable limits and which state detector data values are outside of acceptable limits.
[0016] One or more signatures may be compared with stored patterns of signatures. A pattern associates the occurrence of one or more classified or known signatures with a definition of how the equipment is functioning.
Specifically, when one or more generated signatures matches the classified signatures in a pattern, then the equipment is determined to be functioning as defined by the pattern. Thus, by comparing one or more generated signatures with known patterns of signatures, embodiments of the invention may be used to evaluate the state of the equipment.
Figure 1:
Specifically, when one or more generated signatures matches the classified signatures in a pattern, then the equipment is determined to be functioning as defined by the pattern. Thus, by comparing one or more generated signatures with known patterns of signatures, embodiments of the invention may be used to evaluate the state of the equipment.
Figure 1:
[0017] Figure 1 shows a schematic diagram of a system in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, the system includes equipment (100), a data repository (102), a signature generator (104), and a signature analyzer (106). Each of these components is described below.
[0018]
Equipment (100) corresponds to the physical devices that are being monitored. For example, the equipment (100) may include gearboxes, compressors, pumps, lubricating systems, as well as other such equipment.
In one or more embodiments of the invention, the equipment includes functionality to perform oilfield operations. In one or more embodiments of the invention, each piece of equipment is represented by separate signatures. Further, one piece of equipment may be a component of another piece of equipment. For example, one piece of equipment may correspond to a compressor while another piece of equipment corresponds to a bearing in the compressor. In such a scenario, one series of signatures (i.e., signatures generated from state detector data obtained at different moments in time) may represent the compressor with the bearing while another series of signatures represents only the bearing.
Equipment (100) corresponds to the physical devices that are being monitored. For example, the equipment (100) may include gearboxes, compressors, pumps, lubricating systems, as well as other such equipment.
In one or more embodiments of the invention, the equipment includes functionality to perform oilfield operations. In one or more embodiments of the invention, each piece of equipment is represented by separate signatures. Further, one piece of equipment may be a component of another piece of equipment. For example, one piece of equipment may correspond to a compressor while another piece of equipment corresponds to a bearing in the compressor. In such a scenario, one series of signatures (i.e., signatures generated from state detector data obtained at different moments in time) may represent the compressor with the bearing while another series of signatures represents only the bearing.
[0019] In one or more embodiments of the invention, the equipment (100) is monitored by state detectors (112). Each state detector (112) includes functionality to obtain unprocessed state detector data. The state detector (112) may be a sensor, a person monitoring the equipment, or any other monitoring unit that obtains data about the operations conditions. For example, state detector M (112M) may be a temperature sensor while state detector N (112N) detects the composition of fluid from the oilfield.
[0020] The state detector data represents operational conditions of the equipment. An operational condition includes internal or external conditions under which the equipment is operating. For example, the operational condition may include temperature, pressure, composition, health of the equipment, performance of the equipment, and other such data. The state detector data may include unprocessed state detector data and/or processed state detector data. Unprocessed state detector data corresponds to data obtained directly from the equipment, such as temperature, pressure, flow, density, viscosity. Processed state detector data corresponds to data calculated from the unprocessed state detector data, such as changes in temperature, the difference between inlet and outlet pressure, efficiency, and other such calculated data. Thus, processed state detector data may represent the combination of state detector data values from different pieces of equipment. In one or more embodiments of the invention, each state detector data value in the combination is collected at the same moment in time or within a defined period of time.
[0021] In one or more embodiments of the invention, the data repository (102) is any type of storage unit and/or device (e.g., a file system, database, collection of tables, or any other storage mechanism) for storing data.
Further, the data repository (102) may include multiple different storage units and/or devices. The multiple different storage units and/or devices may or may not be of the same type or located at the same physical site.
For example, a portion of the data repository (102) may be on an internal server while another portion is distributed across the Internet. In one or more embodiments of the invention, the data repository (102), or a portion thereof, is secure. In one or more embodiments of the invention, the data repository (102) includes detector information (108) and a pattern repository (110). The detector information (108) and the pattern repository (110) are discussed below.
Further, the data repository (102) may include multiple different storage units and/or devices. The multiple different storage units and/or devices may or may not be of the same type or located at the same physical site.
For example, a portion of the data repository (102) may be on an internal server while another portion is distributed across the Internet. In one or more embodiments of the invention, the data repository (102), or a portion thereof, is secure. In one or more embodiments of the invention, the data repository (102) includes detector information (108) and a pattern repository (110). The detector information (108) and the pattern repository (110) are discussed below.
[0022] Detector information (108) includes an encode key set (114) for units of processed and unprocessed state detector data. For example, an encode key set S (114S) may correspond to state detector M (112M) while encode key set T (114T) corresponds to processed state detector data defining the performance of the equipment (100). An encode key set (114) includes one or more encode keys. Each encode key defines a mapping between the possible values of the state detector data and a bit value in the signature.
Specifically, the encode key assigns a range of possible values or a discrete group of possible values of the state detector data to a value of a bit in the signature. The encode keys are discussed in further detail below.
Specifically, the encode key assigns a range of possible values or a discrete group of possible values of the state detector data to a value of a bit in the signature. The encode keys are discussed in further detail below.
[0023]
Continuing with Figure 1, a signature generator (104) includes functionality to generate a signature using the detector information (108).
As discussed above, a signature represents the state of the equipment at a moment in time. Specifically, the signature includes the encoded processed and unprocessed state detector data values obtained from the state detectors (112). The signature is discussed below and in Figure 2.
Continuing with Figure 1, a signature generator (104) includes functionality to generate a signature using the detector information (108).
As discussed above, a signature represents the state of the equipment at a moment in time. Specifically, the signature includes the encoded processed and unprocessed state detector data values obtained from the state detectors (112). The signature is discussed below and in Figure 2.
[0024]
Continuing with Figure 1, the data repository (102) may also include a pattern repository (110). A pattern repository (110) is a storage unit for patterns (116) of classified signatures. A pattern associates the occurrence of one or more classified signatures with a definition of how the equipment is functioning. A classified signature is any signature in a defined pattern.
The patterns may be used to evaluate the signature. When generated signatures match a pattern, the equipment is determined to be performing as defined by the pattern. The patterns (116) may be used to detect failure or a potential for failure in the equipment, the type of failure, the general condition of the equipment, how well the equipment is processing, as well as other uses. Patterns are discussed below and in Figures 3A-3C.
Continuing with Figure 1, each pattern (116) in the pattern repository (110) may have a corresponding action (118). The action (118) defines the steps to perform when the pattern is detected. For example, the action (118) may define parts of the equipment to replace, adjustments to make to the equipment, as well as other actions to perform. Further, the action (118) may define a degree of urgency to perform the steps of the action and consequence of delaying or not performing the action.
[0026] In addition to the detector information (108) and the pattern repository (110), the data repository (102) may also include a repository (not shown) for state detector data. For example, the processed and unprocessed state detector data may be stored in the repository. In one or more embodiments of the invention, generated signatures are stored in the repository. The repository of state detector data may be used, for example, to create or modify encode key sets and patterns in the data repository (102). For example, the repository of state detector data may be used to create a pattern for detecting a newly discovered type of failure of the equipment.
[0027]
Continuing with Figure 1, the signature analyzer (106) includes functionality to evaluate the equipment by analyzing the generated signatures. The signature analyzer (106) includes a match finder (120), identified matches (122), and an event engine (124). The match finder (120), identified matches (122), and the event engine (124) are discussed below.
[0028] The match finder (120) includes functionality to identify when one or more generated signatures match the patterns in the pattern repository (110).
Specifically, the match finder (120) includes functionality to determine whether a signature generated by the signature generator (104) matches a classified signature in a pattern (116). Further, the match finder (120) includes functionality to determine whether an entire pattern is matched by one or more generated signatures.
[0029]
Identified match repository (122) is a storage repository for generated signatures that match classified signatures in a pattern. Specifically, the identified match repository (122) may store signatures while the match finder (120) determines whether the generated signatures match a pattern (116). In one or more embodiments of the invention, the identified matches are stored with the patterns that may be potentially matched. For example, consider the scenario in which a pattern requires that seven specific signatures are generated within a specific duration. The first six signatures that match six classified signatures in the example pattern are stored in the identified match repository (122) with identification of the example pattern.
When the seventh generated signature is analyzed, the match finder may access the identified match repository (122) to determine whether the six previously generated signatures with the seventh generated signature match the example pattern in the required duration.
[0030] In one or more embodiments of the invention, the event engine (124) includes functionality to perform the action (118) and/or generate an alert when the pattern is matched. Specifically, the event engine (124) may include functionality to control the equipment to perform the action (118).
Alternatively, or additionally, the event engine (124) may include functionality to generate an alert, such as create an auditory alarm, send an email or text message to an operator, display a warning message, or perform any other steps defined by the action.
Figure 2:
100311 Figure 2 shows an example signature (130) in accordance with one or more embodiments of the invention. The following is for exemplary purposes only and not intended to limit the scope of the invention. In one or more embodiments of the invention, the data type of the signature (130) is an unsigned Big Int. A Big Int has sixty-four bits that are stored as a single block of data. An unsigned Big Int represents integer values of 0 to 264-1. In one or more embodiments of the invention, the signature (130) is a concatenation of four Big Ints. Those skilled in the art will appreciate that different sizes of the signature and different data types may be used without departing from the scope of the invention.
[0032] In Figure 2, the signature (130) includes bit strings for encoding a high range, a normal range, and a low range. Specifically, when a state detector data value is in the high range, a bit may be set to "1" in the high range bit string (132) with the corresponding bit set to "0" in the low range bit string. When the state detector data value is in the low range, a bit may be set to "1" in the low range bit string (134) with the corresponding bit set to "0" in the high range bit string. A state detector data value that is in the normal range has the bit set to "0" in the high range bit string (132) and "0"
in the low range bit string (134).
100331 As discussed above, the encoding of state detector data values is performed by an encode key that maps the value to bits in the bit string.
Each encode key in the encode key set has a corresponding position for a bit (136, 138) in the signature (130) in the corresponding range. For example, high range keys have corresponding high range key bits (136) in the high range bit string (132) while low range keys have corresponding bits (138) in the low range bit string (134). For example, state detector data encoded by encode key set 1 is encoded in high range key 1 bit (136B) and in low range key 1 bit (138B). Thus, two bits in the signature (130) are used to represent the three possible ranges.
[0034] Encode keys may be defined as a single numeric value and a bit position. In particular, the high range encode key may be defined by the high number in which all values above the high number are in the high range. Conversely, the low range encode key may be defined by the low number in which all values below the low number are in the low range. For example, state detector data values above the value of the high range key are in the high range and therefore are encoded as a "1" in the high range key bit (136). Similarly, state detector data values below the low range key are in the low range and therefore are encoded as a "1" in the low range key bit (138). State detector data values that are lower than the high range key and higher than the low range key are in the acceptable range and may be encoded as a "0" in the high range key bit (136) and as a "0" in the low range key bit (138).
[0035] For the following example, consider the scenario in which the high range is above 295, the low range is below 225, and the normal range is between 225 and 295. In the example, a high range key may define that state detector data having a value above 295 is encoded as a "1" for the high range bit. Further, in the example, a low range key may define that state detector data having a value below 225 is encoded as a "1" for the low range bit. Thus, in the example, a state detector data value of 312 is assigned a "1" for the high range bit and a "0" for the low range bit.
[0036] As discussed above, Figure 2 is only an example of one possible format for the signature. Alternative variations for the format of the signature may be used. Below is a discussion of some of the different variations that may not be represented directly in Figure 2.
[0037] In a first variation, a different encoding than discussed above may be used. Specifically, a value of "0" may be used to represent when the state detector data value is in the range specified by the bit. For example, rather than using a value of "1", a value of "0" in the high range key bit may represent when the state detector data value is above the high range key.
[0038] In another variation, although Figure 2 shows only two bit strings, additional bit strings may be used to represent additional ranges. For example, consider the scenario in which the data is to be encoded into a low range, a below normal range, a normal range, an above normal range, and a high range. In the example, the five different ranges may be represented by three or four bits depending on the encoding. For example, using the encoding discussed above, four bits may be used. Each of the four bits represents whether the state detector data value is one of the four abnormal ranges. Alternatively, three bits may be used to represent the five ranges.
In such an alternative, more than one of the three bits may be "1" in the generated signature. For example, the following encoding may be used for the state detector data value: "000" represents normal range, "001"
represents below normal range, "011" represents low range, "100"
represents above normal range, and "110" represents high range.
[0039] In another variation, rather than identifying whether the state detector data value is within a range of values, an encode keys may be used to specify when the value is a member of a discrete set of values. In such scenario, rather than having a high range key bit and a low range key bit, the signature may have a single bit that represents whether the value of the state detector data is in the set. For example, consider the scenario in which the discrete set of values is Xl, X2, X3, X4, and X5. A value of "1" may be used to represent when the value of the state detector data is either Xl, X2, X3, X4, or X5 while a value of "0" may be used to represent when the value of the state detector data is not X1 , X2, X3, X4, or X5. Thus, in the example, X3 maps to "1" while X7 maps to "0" as defined by the encode key set.
[0040] In another variation of Figure 2, the number of encode keys in the encode key set may not be uniform. Thus, the number of bits in the high range bit string may be different from the number of bits in the low range bit string. For example, consider the scenario in which a first portion of the state detector data have four corresponding encode keys (e.g., to represent a low range, a below normal range, a normal range, an above normal range, and a high range), a second portion has two corresponding encode keys (e.g., to represent a low range, a normal range, and a high range), and a last portion have a single encode key (e.g., to represent when the value of the state detector data is in the set represented by the encode key). In the example scenario, the signature may have five bit strings (e.g., a low range bit string, a below normal range bit string, an above normal bit string, a high range bit string, and a single set bit string). The low range bit string and the high range bit string may have bits for both the first portion and the second portion of the state detector data. The below normal bit string and above normal bit string may have bits for only the second portion of state detector data. The single set bit string may have bits for the last portion of state detector data.
[0041] In another variation, virtually any configuration of bits in the signature may be used. For example, although Figure 2 shows having a high range bit string and a low range bit string, bit positions for encode keys in the same encode key set may be adjacent. As an example, bits that encode temperature may be adjacent rather than in separate bit strings.
[0042] Further, although Figure 2 shows the bit strings as separated, the bit strings may be concatenated to form the signature. Specifically, bit bp in the high range bit string (132) may immediately precede bit 1)0 in the low range bit string (134). Thus, the signature may be the concatenation of the bit strings.
[0043] Further, although Figure 2 shows the signature as a bit string, those skilled in the art will appreciate that the signature, when presented to the user, may be the numeric value of the bit string. Specifically, each bit string has a unique numeric value for the data type. For example, the bit string "00000110" in the unsigned byte data type represents the value of six.
[0044] Those skilled in the art will appreciate that the above is only a few of the possible variations of the signature. Different variations maybe used without departing from the scope of the invention.
Figures 3A - 3C:
[0045] Figures 3A-3B show example patterns in accordance with one or more embodiments of the invention. A pattern associates the occurrence of one or more signatures with a definition of how the piece of equipment is functioning. As shown in Figure 3A, a pattern (140) may include a classified signature (142) and a frequency of the classified signature (144) in accordance with one or more embodiments of the invention.
[0046] A
classified signature (142) is a pre-defined signature that is previously associated with a pattern. Thus, the configuration of encode key bits in the classified signature (142) is the same as the configuration in a generated signature. In one or more embodiments of the invention, the frequency of the classified signature (144) defines the number of signatures matching the classified signature (142) that must be generated within a specified duration before the equipment is evaluated as functioning as defined by the pattern.
[0047] For the following example, consider the scenario in which the frequency of the classified signature is four of the classified signatures in three minutes. In the example, the first time that a signature is generated which matches the classified signature, the signature analyzer may be undecided whether the equipment is functioning as defined by the pattern or whether faulty data is obtained. If three additional matching signatures are generated within the three minutes, then the equipment may be evaluated to be functioning as defined by the pattern. The pattern may or may not require that the signatures are consecutively generated.
[0048] As shown in Figure 3B, patterns (150) may be nested in accordance with one or more embodiments of the invention. Specifically, a pattern (150) may include one or more patterns. For example, as shown in Figure 3B, pattern A (150A) includes pattern B (150B) and pattern C (150C).
Pattern B (150B) and pattern C (150C) may be any of the patterns represented in Figures 3A-3C.
[0049] Further, as shown in Figure 3C, in addition to nested patterns, a pattern (154A) may also include a sequence definition (156). The sequence definition (156) defines an ordering between the nested patterns (154B, 154C). Specifically, the sequence definition (156) defines whether pattern B (154B) precedes or succeeds pattern C (154C) before a state of the equipment is detected. Additionally, the sequence definition may describe the number of times each of the nested patterns is generated.
[0050] Using the pattern definitions described in Figures 3A-3C, an example pattern is: "<signature A>, <signature B>, <frequency of signature B = 2>, <sequence definition: signature A precedes signature B><signature C>".
While the example shows one technique for defining a pattern, many different techniques may be used. For example, the example pattern definition may be stored as previously described or as "<signature A>, <signature B>, < signature B>, <signature C> and <signature C> <signature A>, <signature B>, < signature B>".
Figures 4-7:
[0051] Figures 4-7 show flowcharts in accordance with one or more embodiments of the invention. While the various steps in this flowchart are presented and described sequentially, one of ordinary skill will appreciate that some or all of the steps may be executed in different orders, may be combined or omitted, and some or all of the steps may be executed in parallel.
[0052] Figure 4 shows a flowchart for generating encode keys in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, patterns are defined separately for each piece of equipment. Each pattern is associated with a definition of how the piece of equipment is functioning. In step 201, the equipment is identified. A set of state detectors related to the evaluation of the equipment is identified in step 203. In one or more embodiments of the invention, the set of identified state detectors include all state detectors required to monitor and evaluate the equipment.
[0053] From the set of state detectors, the type of state detector data to encode is identified in Step 205. Specifically, the type of state detector data that is identified may be unprocessed state detector data obtained from a specific state detector. Alternatively, the type of state detector data that is identified may be processed state detector data that is created by performing a specific set of steps on unprocessed state detector data obtained from one or more state detectors. For example, the type of state detector data that is identified may be unprocessed data such as temperature, or processed data, such as the pressure drop between inlet and outlet pressure.
[0054] For the identified type of state detector data, the ranges of the state detector data values are identified in Step 207. In one or more embodiments of the invention, a determination is made as to the number of ranges to define for the state detector data. For each of the ranges, the boundaries of the range are identified. In one or more embodiments of the invention, the boundaries are identified from historical data, experience with the same or similar equipment, and/or specifications from the equipment manufacturer.
[0055] In step 209, encode keys are created based on the ranges.
Specifically, the boundaries of each of the ranges are used to define the encode keys. Thus, a mapping is created between the boundaries of the ranges and values for the encode key bit. The encode keys are stored in Step 211. In one or more embodiments of the invention, an ordering of the encode key bits in the signature for the equipment is defined. Specifically, each encode key is assigned a position in the signature.
[0056] In step 213, a determination is made whether to create additional encode key sets. If a determination is made to create additional encode key sets, then the method repeats with Step 207.
[0057] Once encode keys exist, the configuration of the bits in the signature is defined. Thus, one or more patterns may be defined (not shown). In one or more embodiments of the invention, a pattern is defined based on the type of evaluation to perform for the equipment.
[0058] For the following example, consider the scenario in which the evaluation of the equipment is to detect failure or the potential for failure.
In such an example, the different types of failure modes of the equipment are identified. For each of the different types of failure modes, the symptoms of the failure modes are identified. In particular, a determination is made as to the state detector data values from each state detector that typically exists prior to the failure associated with the failure mode. Based on the state detector data values and the encode keys, a classified signature is defined. The classified signature may be used to define the pattern.
Specifically, a determination may be made as to the number of times in which signatures matching the classified signature is to be generated before the failure is detected. The number of times and the classified signature may be stored in the data repository as a pattern. If the type of failure mode requires a change in the state detector data values over time, then multiple classified signatures may be defined. In such a scenario, a pattern may be created by requiring that the multiple classified signatures occur in succession.
[0059] Figure 5 shows a flowchart for generating a signature in accordance with one or more embodiments of the invention. As shown in Figure 5, signature creation is initiated in Step 221. Specifically, an empty signature is defined.
[0060] In step 223, unprocessed state detector data is obtained from the state detectors. For example, sensors on the equipment may gather the state detector data from the equipment and store the state detector data in a data repository. The unprocessed state detector data may be processed to create processed state detector data. For example, the processing may include calculating changes in the operational state of the equipment using the unprocessed state detector data, calculating the performance of the equipment, and performing other such calculations. The processed state detector data may also be stored in the data repository.
[0061] In step 225, an encode key set is obtained. The unit of state detector data corresponding to the obtained code key set is identified in step 227.
Specifically, an identification is made as to which state detector data is encoded by the encode key set. The values of the identified state detector data may be obtained from the data repository. Using the encode key set, the state detector data is encoded to obtain encoded data in step 229. The encoded data is added to the location in the signature specified by the encode key set (Step 231). In step 233, a determination is made whether another encode key set exists. If another encode key set exists, then the method may repeat with step 225. If no other encode key set exists, then the signature generation is complete.
[0062] Figure 6 shows a flowchart for determining whether generated signatures match a pattern in accordance with one or more embodiments of the invention. The generated signature is compared with classified signatures in the repository (Step 241).
Specifically, the generated signatures are compared with each of the classified signatures in each pattern in the repository. Those skilled in the art will appreciate that multiple different methods for comparing signatures may be used without departing from the scope of the invention. For example, the comparison may be performed by performing a bitwise comparison. In another example, a determination may be made whether the number represented by the generated signature matches the number represented by a classified signature. If the number matches, then the signature matches. In step 243, a determination is made whether a match is found.
[0063] If a match is not found, then the generated signature is stored in accordance with one or more embodiments of the invention (Step 245).
Storing the generated signature provides a historical record of the generated signatures. Using the historical record, new patterns may be learned in accordance with one or more embodiments of the invention.
[0064] If a match is found, then the pattern(s) having the classified signature that matches the generated signature identified in Step 247. In one or more embodiments of the invention, more than one pattern may be identified.
Specifically, the same classified signature may be in multiple different patterns of signatures.
[0065] In one or more embodiments of the invention, a determination is made whether to trigger an event based on a pattern in step 249. An event is triggered when one or more generated signatures match a pattern.
[0066] In step 251, an event is triggered based on the determination.
Specifically, the action corresponding to the matched pattern is identified.
The steps of the action are performed. For example, an alert may be issued via email, text, or phone, or a message may be displayed that defines the state of the equipment. Further, rather than or in addition to triggering an alert, the event engine may automatically adjust the equipment according to the action. For example, the event engine may shut down the equipment, adjust flow of the equipment, adjust operating parameters of the equipment, or perform other actions.
[0067]
Regardless of whether a determination is made to trigger an event, the newly identified match is stored. Specifically, the newly generated signature may be stored with identified matches. Further, the newly generated signature may be stored for learning additional patterns.
[0068] Figure 7 shows a flowchart of a method for learning new patterns for failure detection in accordance with one or more embodiments of the invention. In step 261, a failure of the equipment is detected. In one or more embodiments of the invention, the failure of the equipment was not previously detected using the patterns. For example, an operator of the equipment may determine that the equipment is no longer functioning properly.
[0069] Stored signatures that were generated for the equipment prior to the failure are obtained in step 263. At this stage, the data repository is accessed to identify all signatures generated prior to the failure.
[0070] In step 265, the generated signatures are analyzed to identify a new pattern. Different methods may be used to analyze the generated signatures. For example, the analysis may include determining the symptoms of the failure that existed prior to the failure. Based on the symptoms, the state detector data that may identify the existence symptoms are identified. The encode key bits corresponding to the identified state detector data are identified. The identified encode key bits in the generated signatures are used to define a new pattern. In step 267, the new pattern is stored in the data repository.
Figures 8A ¨ 8B:
[0071] Figures 8A-8B show an example in accordance with one or more embodiments of the invention. The following is for exemplary purposes only and not intended to limit the scope of the invention. In the following hypothetical example, consider the scenario in which Equipment X is being monitored to prevent failure. Equipment X has four state detectors (i.e., sdl, sd2, sd3, sd4) gathering unprocessed state detector data from equipment X. Those skilled in the art will appreciate that, in actuality, many more state detectors may be gathering state detector data from equipment X.
[0072] Figure 8A shows encode key sets for state detector data from Equipment X (300) in accordance with one or more embodiments of the invention. As shown in the example Figure 8A, encode key set 1 (302) encodes unprocessed state detector data from state detector sdl. The low range encode key is 5.759 and the high range encode key is 5.963 in encode key set 1 (302). Encode key set 2 (304) encodes unprocessed state detector data from state detector sd2. The low range encode key is 35 and the high range encode key is 96 in encode key set 2 (304).
[0073] Encode key set 3 (306) encodes processed state detector data.
Specifically, to obtain the processed state detector data value for encode key set 3 (306), the state detector data value from state detector sd2 is subtracted from the state detector data value from state detector sd3. The low range encode key for the processed state detector data is -352 and the high range encode key is 48 in encode key set 3 (304).
[0074] Encode key set 4 (308) encodes unprocessed state detector data from state detector sd4. The low range encode key is 96.3 and the high range encode key is 165.8 in encode key set 4 (308).
[0075] In the hypothetical example, the bits of each signature are in the following order: low range key bit for encode key 1, low range key bit for encode key 2, low range key bit for encode key 3, low range key bit for encode key 4, high range key bit for encode key 1, high range key bit for encode key 2, high range key bit for encode key 3, high range key bit for encode key 4.
[0076]
Continuing with the hypothetical example, Figure 8B shows example patterns for detecting a failure in accordance with one or more embodiments of the invention. In the example, the patterns may be used to detect three different types of failures. Specifically, pattern 1 (310) associates classified signature 00111000 with failure type 1. The operator is emailed when the classified signature in pattern 1 (310) is generated.
Pattern 2 (312) associates classified signatures in a pattern of 00000001, 00100001, 10100001 with failure type 2. Equipment X is stopped when pattern 2 (312) is matched. Pattern 3 (314) associates classified signature 00000010 occurring eight times in twelve minutes with failure type 3. A
valve is replaced when pattern 3 (314) is detected.
[0077]
Continuing with the example, unprocessed state detector data is collected from the equipment. For example, at time to, 5.83 is obtained from sdl, 40 is obtained from sd2, -258 is obtained from sd3, and 179 is obtained from sd4. The state detector data for time to is encoded using the encode keys in Figure 8A. Specifically, 5.83 is in the normal range for encode key set 1. Therefore, 5.83 is encoded as 0 for the high range key bit and 0 for the low range key bit. 40 is also in the normal range for encode key set 2 and therefore is similarly encoded. Similarly, -258 ¨ 40 equals -298 for encode key set 3 and is also in the normal range. However, 179 from sd4 is above normal and is therefore encoded as a 0 for the low range bit and a 1 for the high range bit. Accordingly, the signature generate for time to is 00000001.
[0078] The generated signature 00000001 is compared with patterns in Figure 8B . At this stage, the generated signature matches only one classified signature in pattern 2 (312). Because the pattern is not completely matched, no failure is detected.
[0079] At time t1, 5.92 is obtained from sdl, 41 is obtained from sd2, -318 is obtained from sd3, and 190 is obtained from sd4. Similar to encoding the state detector data for time to, the state detector data for time t1 is encoded using the encode keys in Figure 8A. Accordingly, the resulting signature is 00100001. The generated signature 00100001 is compared with patterns in Figure 8B . At this stage, the generated signatures from times to and ti matches two of the classified signature in pattern 2 (312). Because the pattern is not completely matched, no failure is detected.
[0080] At time t2, 5.97 is obtained from sdl, 38 is obtained from sd2, -317 is obtained from sd3, and 223 is obtained from sd4. Similar to encoding the state detector data for times to and t1, the state detector data for time t2 is encoded using the encode keys in Figure 8A. Accordingly, the resulting signature is 10100001. The generated signature 10100001 is compared with patterns in Figure 8B . At this stage, the generated signatures from times to, t1, and t2 matches the pattern 2 (312). Because the pattern is matched, failure 2 is detected and equipment X is immediately stopped.
[0081] Those skilled in the art will appreciate that the above is for explanatory purposes only. At any given time multiple pieces of equipment may be simultaneously monitored by state detectors. Each piece of equipment may have many different types of failures that may occur. The signatures may simplify the amount of state detector data to consider when determining whether a failure exists.
Figure 9:
[0082]
Embodiments of the invention may be implemented on virtually any type of computer regardless of the platform being used. For example, as shown in Figure 9, a computer system (400) includes one or more processor(s) (402), associated memory (404) (e.g., random access memory (RAM), cache memory, flash memory, etc.), a storage device (406) (e.g., a hard disk, an optical drive such as a compact disk drive or digital video disk (DVD) drive, a flash memory stick, etc.), and numerous other elements and functionalities typical of today's computers (not shown). The computer (400) may also include input means, such as a keyboard (408), a mouse (410), or a microphone (not shown). Further, the computer (400) may include output means, such as a monitor (412) (e.g., a liquid crystal display (LCD), a plasma display, or cathode ray tube (CRT) monitor). The computer system (400) may be connected to a network (414) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, or any other similar type of network) via a network interface connection (not shown). Those skilled in the art will appreciate that many different types of computer systems exist, and the aforementioned input and output means may take other forms. Generally speaking, the computer system (400) includes at least the minimal processing, input, and/or output means necessary to practice embodiments of the invention.
[0083] Further, those skilled in the art will appreciate that one or more elements of the aforementioned computer system (400) may be located at a remote location and connected to the other elements over a network.
Further, embodiments of the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention (e.g., data repository, signature generator, signature analyzer, etc.) may be located on a different node within the distributed system. In one embodiment of the invention, the node corresponds to a computer system.
Alternatively, the node may correspond to a processor with associated physical memory. The node may alternatively correspond to a processor with shared memory and/or resources. Further, software instructions to perform embodiments of the invention may be stored on a computer readable medium such as a compact disc (CD), a diskette, a tape, a file, or any other computer readable storage device.
Illustrative Embodiments:
100841 In one embodiment, there is disclosed a system comprising at least one piece of equipment; a plurality of sensors adapted to measure one or more operating parameters of the equipment; and a signature generator adapted to encode a plurality of data streams from the sensors into an operating signature for the equipment. In some embodiments, the system also includes a signature repository containing a number of signatures that correspond to known operating conditions of the equipment. In some embodiments, the system also includes an action repository containing a number of actions to be taken which correspond to the signatures in the signature repository. In some embodiments, the system also includes a signature analyzer adapted to compare a signature from the signature generator with a known signature from the signature repository. In some embodiments, the system also includes an event engine adapted to take a predetermined action when a signature from the signature generator matches a known signature from the signature repository. In some embodiments, the signature generator produces a signature comprising at least two of a high, normal, and low range bit string. In some embodiments, the signature generator converts the bit string to a number.
100851 In one embodiment, there is disclosed a method comprising identifying at least one piece of equipment to be monitored; installing a plurality of sensors to measure operating data of the equipment;
establishing an operating range for each of the sensors; and creating an encoding key for each of the ranges. In some embodiments, the method also includes converting a plurality of the encoding keys into an operating signature. In some embodiments, the method also includes storing a plurality of known signatures in a database, the signatures corresponding to known operating conditions of the equipment. In some embodiments, the method also includes storing a plurality of actions to take in a database, the actions corresponding to the known signatures. In some embodiments, the method also includes comparing the operating signature with known signatures in the database. In some embodiments, the method also includes taking a predetermined action when the operating signature matches a known signatures in the database. In some embodiments, the method also includes storing a new signature in a database, the signature corresponding to an observed or measured operating condition of the equipment. In some embodiments, the method also includes storing a new action in a database, the action corresponding to a new signature, the new action designed to correct observed or measured operating conditions of the equipment.
100861 While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein.
Accordingly, the scope of the invention should be limited only by the attached claims.
Continuing with Figure 1, the data repository (102) may also include a pattern repository (110). A pattern repository (110) is a storage unit for patterns (116) of classified signatures. A pattern associates the occurrence of one or more classified signatures with a definition of how the equipment is functioning. A classified signature is any signature in a defined pattern.
The patterns may be used to evaluate the signature. When generated signatures match a pattern, the equipment is determined to be performing as defined by the pattern. The patterns (116) may be used to detect failure or a potential for failure in the equipment, the type of failure, the general condition of the equipment, how well the equipment is processing, as well as other uses. Patterns are discussed below and in Figures 3A-3C.
Continuing with Figure 1, each pattern (116) in the pattern repository (110) may have a corresponding action (118). The action (118) defines the steps to perform when the pattern is detected. For example, the action (118) may define parts of the equipment to replace, adjustments to make to the equipment, as well as other actions to perform. Further, the action (118) may define a degree of urgency to perform the steps of the action and consequence of delaying or not performing the action.
[0026] In addition to the detector information (108) and the pattern repository (110), the data repository (102) may also include a repository (not shown) for state detector data. For example, the processed and unprocessed state detector data may be stored in the repository. In one or more embodiments of the invention, generated signatures are stored in the repository. The repository of state detector data may be used, for example, to create or modify encode key sets and patterns in the data repository (102). For example, the repository of state detector data may be used to create a pattern for detecting a newly discovered type of failure of the equipment.
[0027]
Continuing with Figure 1, the signature analyzer (106) includes functionality to evaluate the equipment by analyzing the generated signatures. The signature analyzer (106) includes a match finder (120), identified matches (122), and an event engine (124). The match finder (120), identified matches (122), and the event engine (124) are discussed below.
[0028] The match finder (120) includes functionality to identify when one or more generated signatures match the patterns in the pattern repository (110).
Specifically, the match finder (120) includes functionality to determine whether a signature generated by the signature generator (104) matches a classified signature in a pattern (116). Further, the match finder (120) includes functionality to determine whether an entire pattern is matched by one or more generated signatures.
[0029]
Identified match repository (122) is a storage repository for generated signatures that match classified signatures in a pattern. Specifically, the identified match repository (122) may store signatures while the match finder (120) determines whether the generated signatures match a pattern (116). In one or more embodiments of the invention, the identified matches are stored with the patterns that may be potentially matched. For example, consider the scenario in which a pattern requires that seven specific signatures are generated within a specific duration. The first six signatures that match six classified signatures in the example pattern are stored in the identified match repository (122) with identification of the example pattern.
When the seventh generated signature is analyzed, the match finder may access the identified match repository (122) to determine whether the six previously generated signatures with the seventh generated signature match the example pattern in the required duration.
[0030] In one or more embodiments of the invention, the event engine (124) includes functionality to perform the action (118) and/or generate an alert when the pattern is matched. Specifically, the event engine (124) may include functionality to control the equipment to perform the action (118).
Alternatively, or additionally, the event engine (124) may include functionality to generate an alert, such as create an auditory alarm, send an email or text message to an operator, display a warning message, or perform any other steps defined by the action.
Figure 2:
100311 Figure 2 shows an example signature (130) in accordance with one or more embodiments of the invention. The following is for exemplary purposes only and not intended to limit the scope of the invention. In one or more embodiments of the invention, the data type of the signature (130) is an unsigned Big Int. A Big Int has sixty-four bits that are stored as a single block of data. An unsigned Big Int represents integer values of 0 to 264-1. In one or more embodiments of the invention, the signature (130) is a concatenation of four Big Ints. Those skilled in the art will appreciate that different sizes of the signature and different data types may be used without departing from the scope of the invention.
[0032] In Figure 2, the signature (130) includes bit strings for encoding a high range, a normal range, and a low range. Specifically, when a state detector data value is in the high range, a bit may be set to "1" in the high range bit string (132) with the corresponding bit set to "0" in the low range bit string. When the state detector data value is in the low range, a bit may be set to "1" in the low range bit string (134) with the corresponding bit set to "0" in the high range bit string. A state detector data value that is in the normal range has the bit set to "0" in the high range bit string (132) and "0"
in the low range bit string (134).
100331 As discussed above, the encoding of state detector data values is performed by an encode key that maps the value to bits in the bit string.
Each encode key in the encode key set has a corresponding position for a bit (136, 138) in the signature (130) in the corresponding range. For example, high range keys have corresponding high range key bits (136) in the high range bit string (132) while low range keys have corresponding bits (138) in the low range bit string (134). For example, state detector data encoded by encode key set 1 is encoded in high range key 1 bit (136B) and in low range key 1 bit (138B). Thus, two bits in the signature (130) are used to represent the three possible ranges.
[0034] Encode keys may be defined as a single numeric value and a bit position. In particular, the high range encode key may be defined by the high number in which all values above the high number are in the high range. Conversely, the low range encode key may be defined by the low number in which all values below the low number are in the low range. For example, state detector data values above the value of the high range key are in the high range and therefore are encoded as a "1" in the high range key bit (136). Similarly, state detector data values below the low range key are in the low range and therefore are encoded as a "1" in the low range key bit (138). State detector data values that are lower than the high range key and higher than the low range key are in the acceptable range and may be encoded as a "0" in the high range key bit (136) and as a "0" in the low range key bit (138).
[0035] For the following example, consider the scenario in which the high range is above 295, the low range is below 225, and the normal range is between 225 and 295. In the example, a high range key may define that state detector data having a value above 295 is encoded as a "1" for the high range bit. Further, in the example, a low range key may define that state detector data having a value below 225 is encoded as a "1" for the low range bit. Thus, in the example, a state detector data value of 312 is assigned a "1" for the high range bit and a "0" for the low range bit.
[0036] As discussed above, Figure 2 is only an example of one possible format for the signature. Alternative variations for the format of the signature may be used. Below is a discussion of some of the different variations that may not be represented directly in Figure 2.
[0037] In a first variation, a different encoding than discussed above may be used. Specifically, a value of "0" may be used to represent when the state detector data value is in the range specified by the bit. For example, rather than using a value of "1", a value of "0" in the high range key bit may represent when the state detector data value is above the high range key.
[0038] In another variation, although Figure 2 shows only two bit strings, additional bit strings may be used to represent additional ranges. For example, consider the scenario in which the data is to be encoded into a low range, a below normal range, a normal range, an above normal range, and a high range. In the example, the five different ranges may be represented by three or four bits depending on the encoding. For example, using the encoding discussed above, four bits may be used. Each of the four bits represents whether the state detector data value is one of the four abnormal ranges. Alternatively, three bits may be used to represent the five ranges.
In such an alternative, more than one of the three bits may be "1" in the generated signature. For example, the following encoding may be used for the state detector data value: "000" represents normal range, "001"
represents below normal range, "011" represents low range, "100"
represents above normal range, and "110" represents high range.
[0039] In another variation, rather than identifying whether the state detector data value is within a range of values, an encode keys may be used to specify when the value is a member of a discrete set of values. In such scenario, rather than having a high range key bit and a low range key bit, the signature may have a single bit that represents whether the value of the state detector data is in the set. For example, consider the scenario in which the discrete set of values is Xl, X2, X3, X4, and X5. A value of "1" may be used to represent when the value of the state detector data is either Xl, X2, X3, X4, or X5 while a value of "0" may be used to represent when the value of the state detector data is not X1 , X2, X3, X4, or X5. Thus, in the example, X3 maps to "1" while X7 maps to "0" as defined by the encode key set.
[0040] In another variation of Figure 2, the number of encode keys in the encode key set may not be uniform. Thus, the number of bits in the high range bit string may be different from the number of bits in the low range bit string. For example, consider the scenario in which a first portion of the state detector data have four corresponding encode keys (e.g., to represent a low range, a below normal range, a normal range, an above normal range, and a high range), a second portion has two corresponding encode keys (e.g., to represent a low range, a normal range, and a high range), and a last portion have a single encode key (e.g., to represent when the value of the state detector data is in the set represented by the encode key). In the example scenario, the signature may have five bit strings (e.g., a low range bit string, a below normal range bit string, an above normal bit string, a high range bit string, and a single set bit string). The low range bit string and the high range bit string may have bits for both the first portion and the second portion of the state detector data. The below normal bit string and above normal bit string may have bits for only the second portion of state detector data. The single set bit string may have bits for the last portion of state detector data.
[0041] In another variation, virtually any configuration of bits in the signature may be used. For example, although Figure 2 shows having a high range bit string and a low range bit string, bit positions for encode keys in the same encode key set may be adjacent. As an example, bits that encode temperature may be adjacent rather than in separate bit strings.
[0042] Further, although Figure 2 shows the bit strings as separated, the bit strings may be concatenated to form the signature. Specifically, bit bp in the high range bit string (132) may immediately precede bit 1)0 in the low range bit string (134). Thus, the signature may be the concatenation of the bit strings.
[0043] Further, although Figure 2 shows the signature as a bit string, those skilled in the art will appreciate that the signature, when presented to the user, may be the numeric value of the bit string. Specifically, each bit string has a unique numeric value for the data type. For example, the bit string "00000110" in the unsigned byte data type represents the value of six.
[0044] Those skilled in the art will appreciate that the above is only a few of the possible variations of the signature. Different variations maybe used without departing from the scope of the invention.
Figures 3A - 3C:
[0045] Figures 3A-3B show example patterns in accordance with one or more embodiments of the invention. A pattern associates the occurrence of one or more signatures with a definition of how the piece of equipment is functioning. As shown in Figure 3A, a pattern (140) may include a classified signature (142) and a frequency of the classified signature (144) in accordance with one or more embodiments of the invention.
[0046] A
classified signature (142) is a pre-defined signature that is previously associated with a pattern. Thus, the configuration of encode key bits in the classified signature (142) is the same as the configuration in a generated signature. In one or more embodiments of the invention, the frequency of the classified signature (144) defines the number of signatures matching the classified signature (142) that must be generated within a specified duration before the equipment is evaluated as functioning as defined by the pattern.
[0047] For the following example, consider the scenario in which the frequency of the classified signature is four of the classified signatures in three minutes. In the example, the first time that a signature is generated which matches the classified signature, the signature analyzer may be undecided whether the equipment is functioning as defined by the pattern or whether faulty data is obtained. If three additional matching signatures are generated within the three minutes, then the equipment may be evaluated to be functioning as defined by the pattern. The pattern may or may not require that the signatures are consecutively generated.
[0048] As shown in Figure 3B, patterns (150) may be nested in accordance with one or more embodiments of the invention. Specifically, a pattern (150) may include one or more patterns. For example, as shown in Figure 3B, pattern A (150A) includes pattern B (150B) and pattern C (150C).
Pattern B (150B) and pattern C (150C) may be any of the patterns represented in Figures 3A-3C.
[0049] Further, as shown in Figure 3C, in addition to nested patterns, a pattern (154A) may also include a sequence definition (156). The sequence definition (156) defines an ordering between the nested patterns (154B, 154C). Specifically, the sequence definition (156) defines whether pattern B (154B) precedes or succeeds pattern C (154C) before a state of the equipment is detected. Additionally, the sequence definition may describe the number of times each of the nested patterns is generated.
[0050] Using the pattern definitions described in Figures 3A-3C, an example pattern is: "<signature A>, <signature B>, <frequency of signature B = 2>, <sequence definition: signature A precedes signature B><signature C>".
While the example shows one technique for defining a pattern, many different techniques may be used. For example, the example pattern definition may be stored as previously described or as "<signature A>, <signature B>, < signature B>, <signature C> and <signature C> <signature A>, <signature B>, < signature B>".
Figures 4-7:
[0051] Figures 4-7 show flowcharts in accordance with one or more embodiments of the invention. While the various steps in this flowchart are presented and described sequentially, one of ordinary skill will appreciate that some or all of the steps may be executed in different orders, may be combined or omitted, and some or all of the steps may be executed in parallel.
[0052] Figure 4 shows a flowchart for generating encode keys in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, patterns are defined separately for each piece of equipment. Each pattern is associated with a definition of how the piece of equipment is functioning. In step 201, the equipment is identified. A set of state detectors related to the evaluation of the equipment is identified in step 203. In one or more embodiments of the invention, the set of identified state detectors include all state detectors required to monitor and evaluate the equipment.
[0053] From the set of state detectors, the type of state detector data to encode is identified in Step 205. Specifically, the type of state detector data that is identified may be unprocessed state detector data obtained from a specific state detector. Alternatively, the type of state detector data that is identified may be processed state detector data that is created by performing a specific set of steps on unprocessed state detector data obtained from one or more state detectors. For example, the type of state detector data that is identified may be unprocessed data such as temperature, or processed data, such as the pressure drop between inlet and outlet pressure.
[0054] For the identified type of state detector data, the ranges of the state detector data values are identified in Step 207. In one or more embodiments of the invention, a determination is made as to the number of ranges to define for the state detector data. For each of the ranges, the boundaries of the range are identified. In one or more embodiments of the invention, the boundaries are identified from historical data, experience with the same or similar equipment, and/or specifications from the equipment manufacturer.
[0055] In step 209, encode keys are created based on the ranges.
Specifically, the boundaries of each of the ranges are used to define the encode keys. Thus, a mapping is created between the boundaries of the ranges and values for the encode key bit. The encode keys are stored in Step 211. In one or more embodiments of the invention, an ordering of the encode key bits in the signature for the equipment is defined. Specifically, each encode key is assigned a position in the signature.
[0056] In step 213, a determination is made whether to create additional encode key sets. If a determination is made to create additional encode key sets, then the method repeats with Step 207.
[0057] Once encode keys exist, the configuration of the bits in the signature is defined. Thus, one or more patterns may be defined (not shown). In one or more embodiments of the invention, a pattern is defined based on the type of evaluation to perform for the equipment.
[0058] For the following example, consider the scenario in which the evaluation of the equipment is to detect failure or the potential for failure.
In such an example, the different types of failure modes of the equipment are identified. For each of the different types of failure modes, the symptoms of the failure modes are identified. In particular, a determination is made as to the state detector data values from each state detector that typically exists prior to the failure associated with the failure mode. Based on the state detector data values and the encode keys, a classified signature is defined. The classified signature may be used to define the pattern.
Specifically, a determination may be made as to the number of times in which signatures matching the classified signature is to be generated before the failure is detected. The number of times and the classified signature may be stored in the data repository as a pattern. If the type of failure mode requires a change in the state detector data values over time, then multiple classified signatures may be defined. In such a scenario, a pattern may be created by requiring that the multiple classified signatures occur in succession.
[0059] Figure 5 shows a flowchart for generating a signature in accordance with one or more embodiments of the invention. As shown in Figure 5, signature creation is initiated in Step 221. Specifically, an empty signature is defined.
[0060] In step 223, unprocessed state detector data is obtained from the state detectors. For example, sensors on the equipment may gather the state detector data from the equipment and store the state detector data in a data repository. The unprocessed state detector data may be processed to create processed state detector data. For example, the processing may include calculating changes in the operational state of the equipment using the unprocessed state detector data, calculating the performance of the equipment, and performing other such calculations. The processed state detector data may also be stored in the data repository.
[0061] In step 225, an encode key set is obtained. The unit of state detector data corresponding to the obtained code key set is identified in step 227.
Specifically, an identification is made as to which state detector data is encoded by the encode key set. The values of the identified state detector data may be obtained from the data repository. Using the encode key set, the state detector data is encoded to obtain encoded data in step 229. The encoded data is added to the location in the signature specified by the encode key set (Step 231). In step 233, a determination is made whether another encode key set exists. If another encode key set exists, then the method may repeat with step 225. If no other encode key set exists, then the signature generation is complete.
[0062] Figure 6 shows a flowchart for determining whether generated signatures match a pattern in accordance with one or more embodiments of the invention. The generated signature is compared with classified signatures in the repository (Step 241).
Specifically, the generated signatures are compared with each of the classified signatures in each pattern in the repository. Those skilled in the art will appreciate that multiple different methods for comparing signatures may be used without departing from the scope of the invention. For example, the comparison may be performed by performing a bitwise comparison. In another example, a determination may be made whether the number represented by the generated signature matches the number represented by a classified signature. If the number matches, then the signature matches. In step 243, a determination is made whether a match is found.
[0063] If a match is not found, then the generated signature is stored in accordance with one or more embodiments of the invention (Step 245).
Storing the generated signature provides a historical record of the generated signatures. Using the historical record, new patterns may be learned in accordance with one or more embodiments of the invention.
[0064] If a match is found, then the pattern(s) having the classified signature that matches the generated signature identified in Step 247. In one or more embodiments of the invention, more than one pattern may be identified.
Specifically, the same classified signature may be in multiple different patterns of signatures.
[0065] In one or more embodiments of the invention, a determination is made whether to trigger an event based on a pattern in step 249. An event is triggered when one or more generated signatures match a pattern.
[0066] In step 251, an event is triggered based on the determination.
Specifically, the action corresponding to the matched pattern is identified.
The steps of the action are performed. For example, an alert may be issued via email, text, or phone, or a message may be displayed that defines the state of the equipment. Further, rather than or in addition to triggering an alert, the event engine may automatically adjust the equipment according to the action. For example, the event engine may shut down the equipment, adjust flow of the equipment, adjust operating parameters of the equipment, or perform other actions.
[0067]
Regardless of whether a determination is made to trigger an event, the newly identified match is stored. Specifically, the newly generated signature may be stored with identified matches. Further, the newly generated signature may be stored for learning additional patterns.
[0068] Figure 7 shows a flowchart of a method for learning new patterns for failure detection in accordance with one or more embodiments of the invention. In step 261, a failure of the equipment is detected. In one or more embodiments of the invention, the failure of the equipment was not previously detected using the patterns. For example, an operator of the equipment may determine that the equipment is no longer functioning properly.
[0069] Stored signatures that were generated for the equipment prior to the failure are obtained in step 263. At this stage, the data repository is accessed to identify all signatures generated prior to the failure.
[0070] In step 265, the generated signatures are analyzed to identify a new pattern. Different methods may be used to analyze the generated signatures. For example, the analysis may include determining the symptoms of the failure that existed prior to the failure. Based on the symptoms, the state detector data that may identify the existence symptoms are identified. The encode key bits corresponding to the identified state detector data are identified. The identified encode key bits in the generated signatures are used to define a new pattern. In step 267, the new pattern is stored in the data repository.
Figures 8A ¨ 8B:
[0071] Figures 8A-8B show an example in accordance with one or more embodiments of the invention. The following is for exemplary purposes only and not intended to limit the scope of the invention. In the following hypothetical example, consider the scenario in which Equipment X is being monitored to prevent failure. Equipment X has four state detectors (i.e., sdl, sd2, sd3, sd4) gathering unprocessed state detector data from equipment X. Those skilled in the art will appreciate that, in actuality, many more state detectors may be gathering state detector data from equipment X.
[0072] Figure 8A shows encode key sets for state detector data from Equipment X (300) in accordance with one or more embodiments of the invention. As shown in the example Figure 8A, encode key set 1 (302) encodes unprocessed state detector data from state detector sdl. The low range encode key is 5.759 and the high range encode key is 5.963 in encode key set 1 (302). Encode key set 2 (304) encodes unprocessed state detector data from state detector sd2. The low range encode key is 35 and the high range encode key is 96 in encode key set 2 (304).
[0073] Encode key set 3 (306) encodes processed state detector data.
Specifically, to obtain the processed state detector data value for encode key set 3 (306), the state detector data value from state detector sd2 is subtracted from the state detector data value from state detector sd3. The low range encode key for the processed state detector data is -352 and the high range encode key is 48 in encode key set 3 (304).
[0074] Encode key set 4 (308) encodes unprocessed state detector data from state detector sd4. The low range encode key is 96.3 and the high range encode key is 165.8 in encode key set 4 (308).
[0075] In the hypothetical example, the bits of each signature are in the following order: low range key bit for encode key 1, low range key bit for encode key 2, low range key bit for encode key 3, low range key bit for encode key 4, high range key bit for encode key 1, high range key bit for encode key 2, high range key bit for encode key 3, high range key bit for encode key 4.
[0076]
Continuing with the hypothetical example, Figure 8B shows example patterns for detecting a failure in accordance with one or more embodiments of the invention. In the example, the patterns may be used to detect three different types of failures. Specifically, pattern 1 (310) associates classified signature 00111000 with failure type 1. The operator is emailed when the classified signature in pattern 1 (310) is generated.
Pattern 2 (312) associates classified signatures in a pattern of 00000001, 00100001, 10100001 with failure type 2. Equipment X is stopped when pattern 2 (312) is matched. Pattern 3 (314) associates classified signature 00000010 occurring eight times in twelve minutes with failure type 3. A
valve is replaced when pattern 3 (314) is detected.
[0077]
Continuing with the example, unprocessed state detector data is collected from the equipment. For example, at time to, 5.83 is obtained from sdl, 40 is obtained from sd2, -258 is obtained from sd3, and 179 is obtained from sd4. The state detector data for time to is encoded using the encode keys in Figure 8A. Specifically, 5.83 is in the normal range for encode key set 1. Therefore, 5.83 is encoded as 0 for the high range key bit and 0 for the low range key bit. 40 is also in the normal range for encode key set 2 and therefore is similarly encoded. Similarly, -258 ¨ 40 equals -298 for encode key set 3 and is also in the normal range. However, 179 from sd4 is above normal and is therefore encoded as a 0 for the low range bit and a 1 for the high range bit. Accordingly, the signature generate for time to is 00000001.
[0078] The generated signature 00000001 is compared with patterns in Figure 8B . At this stage, the generated signature matches only one classified signature in pattern 2 (312). Because the pattern is not completely matched, no failure is detected.
[0079] At time t1, 5.92 is obtained from sdl, 41 is obtained from sd2, -318 is obtained from sd3, and 190 is obtained from sd4. Similar to encoding the state detector data for time to, the state detector data for time t1 is encoded using the encode keys in Figure 8A. Accordingly, the resulting signature is 00100001. The generated signature 00100001 is compared with patterns in Figure 8B . At this stage, the generated signatures from times to and ti matches two of the classified signature in pattern 2 (312). Because the pattern is not completely matched, no failure is detected.
[0080] At time t2, 5.97 is obtained from sdl, 38 is obtained from sd2, -317 is obtained from sd3, and 223 is obtained from sd4. Similar to encoding the state detector data for times to and t1, the state detector data for time t2 is encoded using the encode keys in Figure 8A. Accordingly, the resulting signature is 10100001. The generated signature 10100001 is compared with patterns in Figure 8B . At this stage, the generated signatures from times to, t1, and t2 matches the pattern 2 (312). Because the pattern is matched, failure 2 is detected and equipment X is immediately stopped.
[0081] Those skilled in the art will appreciate that the above is for explanatory purposes only. At any given time multiple pieces of equipment may be simultaneously monitored by state detectors. Each piece of equipment may have many different types of failures that may occur. The signatures may simplify the amount of state detector data to consider when determining whether a failure exists.
Figure 9:
[0082]
Embodiments of the invention may be implemented on virtually any type of computer regardless of the platform being used. For example, as shown in Figure 9, a computer system (400) includes one or more processor(s) (402), associated memory (404) (e.g., random access memory (RAM), cache memory, flash memory, etc.), a storage device (406) (e.g., a hard disk, an optical drive such as a compact disk drive or digital video disk (DVD) drive, a flash memory stick, etc.), and numerous other elements and functionalities typical of today's computers (not shown). The computer (400) may also include input means, such as a keyboard (408), a mouse (410), or a microphone (not shown). Further, the computer (400) may include output means, such as a monitor (412) (e.g., a liquid crystal display (LCD), a plasma display, or cathode ray tube (CRT) monitor). The computer system (400) may be connected to a network (414) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, or any other similar type of network) via a network interface connection (not shown). Those skilled in the art will appreciate that many different types of computer systems exist, and the aforementioned input and output means may take other forms. Generally speaking, the computer system (400) includes at least the minimal processing, input, and/or output means necessary to practice embodiments of the invention.
[0083] Further, those skilled in the art will appreciate that one or more elements of the aforementioned computer system (400) may be located at a remote location and connected to the other elements over a network.
Further, embodiments of the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention (e.g., data repository, signature generator, signature analyzer, etc.) may be located on a different node within the distributed system. In one embodiment of the invention, the node corresponds to a computer system.
Alternatively, the node may correspond to a processor with associated physical memory. The node may alternatively correspond to a processor with shared memory and/or resources. Further, software instructions to perform embodiments of the invention may be stored on a computer readable medium such as a compact disc (CD), a diskette, a tape, a file, or any other computer readable storage device.
Illustrative Embodiments:
100841 In one embodiment, there is disclosed a system comprising at least one piece of equipment; a plurality of sensors adapted to measure one or more operating parameters of the equipment; and a signature generator adapted to encode a plurality of data streams from the sensors into an operating signature for the equipment. In some embodiments, the system also includes a signature repository containing a number of signatures that correspond to known operating conditions of the equipment. In some embodiments, the system also includes an action repository containing a number of actions to be taken which correspond to the signatures in the signature repository. In some embodiments, the system also includes a signature analyzer adapted to compare a signature from the signature generator with a known signature from the signature repository. In some embodiments, the system also includes an event engine adapted to take a predetermined action when a signature from the signature generator matches a known signature from the signature repository. In some embodiments, the signature generator produces a signature comprising at least two of a high, normal, and low range bit string. In some embodiments, the signature generator converts the bit string to a number.
100851 In one embodiment, there is disclosed a method comprising identifying at least one piece of equipment to be monitored; installing a plurality of sensors to measure operating data of the equipment;
establishing an operating range for each of the sensors; and creating an encoding key for each of the ranges. In some embodiments, the method also includes converting a plurality of the encoding keys into an operating signature. In some embodiments, the method also includes storing a plurality of known signatures in a database, the signatures corresponding to known operating conditions of the equipment. In some embodiments, the method also includes storing a plurality of actions to take in a database, the actions corresponding to the known signatures. In some embodiments, the method also includes comparing the operating signature with known signatures in the database. In some embodiments, the method also includes taking a predetermined action when the operating signature matches a known signatures in the database. In some embodiments, the method also includes storing a new signature in a database, the signature corresponding to an observed or measured operating condition of the equipment. In some embodiments, the method also includes storing a new action in a database, the action corresponding to a new signature, the new action designed to correct observed or measured operating conditions of the equipment.
100861 While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein.
Accordingly, the scope of the invention should be limited only by the attached claims.
Claims (4)
1. A system comprising:
at least one piece of equipment;
a plurality of sensors adapted to measure one or more operating parameters of the equipment; a signature generator adapted to encode a plurality of data stream-5õ from the sensors into an operating signature for the equipment;
a pattern repository comprising a pattern, wherein the pattern comprises a classified signature and a frequency specifying a number of occurrences of the classified signature over time; and a signature analyzer configured to compare the operating signature to the pattern and perform an action based on the comparison.
at least one piece of equipment;
a plurality of sensors adapted to measure one or more operating parameters of the equipment; a signature generator adapted to encode a plurality of data stream-5õ from the sensors into an operating signature for the equipment;
a pattern repository comprising a pattern, wherein the pattern comprises a classified signature and a frequency specifying a number of occurrences of the classified signature over time; and a signature analyzer configured to compare the operating signature to the pattern and perform an action based on the comparison.
2. The system of claim 1, further comprising: an action repository comprising a number of actions, wherein the action performed by the signature analyzer is one of the number of actions.
3. The system of claim 1, wherein the operating signature comprises at least two of a high, normal, and low range bit string.
4. The system of claim 3, wherein: the signature generator converts the bit string to a number.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US94428607P | 2007-06-15 | 2007-06-15 | |
US60/944,286 | 2007-06-15 | ||
PCT/US2008/067116 WO2008157491A1 (en) | 2007-06-15 | 2008-06-16 | Method and system for state encoding |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2689219A1 CA2689219A1 (en) | 2008-12-24 |
CA2689219C true CA2689219C (en) | 2017-07-04 |
Family
ID=40156658
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2689237A Active CA2689237C (en) | 2007-06-15 | 2008-06-16 | Framework and method for monitoring equipment |
CA2689252A Active CA2689252C (en) | 2007-06-15 | 2008-06-16 | Methods and systems for predicting equipment operation |
CA2689238A Active CA2689238C (en) | 2007-06-15 | 2008-06-16 | Reciprocating compressor simulator and a computer system using the same |
CA2690459A Expired - Fee Related CA2690459C (en) | 2007-06-15 | 2008-06-16 | Remote monitoring systems and methods |
CA2689219A Active CA2689219C (en) | 2007-06-15 | 2008-06-16 | Method and system for state encoding |
CA2689256A Active CA2689256C (en) | 2007-06-15 | 2008-06-16 | Remote monitoring systems and methods |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2689237A Active CA2689237C (en) | 2007-06-15 | 2008-06-16 | Framework and method for monitoring equipment |
CA2689252A Active CA2689252C (en) | 2007-06-15 | 2008-06-16 | Methods and systems for predicting equipment operation |
CA2689238A Active CA2689238C (en) | 2007-06-15 | 2008-06-16 | Reciprocating compressor simulator and a computer system using the same |
CA2690459A Expired - Fee Related CA2690459C (en) | 2007-06-15 | 2008-06-16 | Remote monitoring systems and methods |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2689256A Active CA2689256C (en) | 2007-06-15 | 2008-06-16 | Remote monitoring systems and methods |
Country Status (4)
Country | Link |
---|---|
US (6) | US8688405B2 (en) |
CA (6) | CA2689237C (en) |
GB (6) | GB2464002B (en) |
WO (6) | WO2008157494A2 (en) |
Families Citing this family (219)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6658091B1 (en) | 2002-02-01 | 2003-12-02 | @Security Broadband Corp. | LIfestyle multimedia security system |
US8963713B2 (en) | 2005-03-16 | 2015-02-24 | Icontrol Networks, Inc. | Integrated security network with security alarm signaling system |
US11368429B2 (en) | 2004-03-16 | 2022-06-21 | Icontrol Networks, Inc. | Premises management configuration and control |
US10382452B1 (en) | 2007-06-12 | 2019-08-13 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10721087B2 (en) | 2005-03-16 | 2020-07-21 | Icontrol Networks, Inc. | Method for networked touchscreen with integrated interfaces |
US9531593B2 (en) | 2007-06-12 | 2016-12-27 | Icontrol Networks, Inc. | Takeover processes in security network integrated with premise security system |
US9141276B2 (en) | 2005-03-16 | 2015-09-22 | Icontrol Networks, Inc. | Integrated interface for mobile device |
US8635350B2 (en) | 2006-06-12 | 2014-01-21 | Icontrol Networks, Inc. | IP device discovery systems and methods |
GB2428821B (en) | 2004-03-16 | 2008-06-04 | Icontrol Networks Inc | Premises management system |
US9191228B2 (en) | 2005-03-16 | 2015-11-17 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US10062273B2 (en) | 2010-09-28 | 2018-08-28 | Icontrol Networks, Inc. | Integrated security system with parallel processing architecture |
US11368327B2 (en) | 2008-08-11 | 2022-06-21 | Icontrol Networks, Inc. | Integrated cloud system for premises automation |
US20090077623A1 (en) | 2005-03-16 | 2009-03-19 | Marc Baum | Security Network Integrating Security System and Network Devices |
US11159484B2 (en) | 2004-03-16 | 2021-10-26 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US7711796B2 (en) | 2006-06-12 | 2010-05-04 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US9609003B1 (en) | 2007-06-12 | 2017-03-28 | Icontrol Networks, Inc. | Generating risk profile using data of home monitoring and security system |
US11582065B2 (en) | 2007-06-12 | 2023-02-14 | Icontrol Networks, Inc. | Systems and methods for device communication |
US10444964B2 (en) | 2007-06-12 | 2019-10-15 | Icontrol Networks, Inc. | Control system user interface |
US11244545B2 (en) | 2004-03-16 | 2022-02-08 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US11316958B2 (en) | 2008-08-11 | 2022-04-26 | Icontrol Networks, Inc. | Virtual device systems and methods |
US11113950B2 (en) | 2005-03-16 | 2021-09-07 | Icontrol Networks, Inc. | Gateway integrated with premises security system |
US10142392B2 (en) | 2007-01-24 | 2018-11-27 | Icontrol Networks, Inc. | Methods and systems for improved system performance |
US11489812B2 (en) | 2004-03-16 | 2022-11-01 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US8988221B2 (en) | 2005-03-16 | 2015-03-24 | Icontrol Networks, Inc. | Integrated security system with parallel processing architecture |
US10522026B2 (en) | 2008-08-11 | 2019-12-31 | Icontrol Networks, Inc. | Automation system user interface with three-dimensional display |
US10313303B2 (en) | 2007-06-12 | 2019-06-04 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US10348575B2 (en) | 2013-06-27 | 2019-07-09 | Icontrol Networks, Inc. | Control system user interface |
US9729342B2 (en) | 2010-12-20 | 2017-08-08 | Icontrol Networks, Inc. | Defining and implementing sensor triggered response rules |
US11916870B2 (en) | 2004-03-16 | 2024-02-27 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US10375253B2 (en) | 2008-08-25 | 2019-08-06 | Icontrol Networks, Inc. | Security system with networked touchscreen and gateway |
US10339791B2 (en) | 2007-06-12 | 2019-07-02 | Icontrol Networks, Inc. | Security network integrated with premise security system |
US11343380B2 (en) | 2004-03-16 | 2022-05-24 | Icontrol Networks, Inc. | Premises system automation |
US11677577B2 (en) | 2004-03-16 | 2023-06-13 | Icontrol Networks, Inc. | Premises system management using status signal |
US11277465B2 (en) | 2004-03-16 | 2022-03-15 | Icontrol Networks, Inc. | Generating risk profile using data of home monitoring and security system |
US11811845B2 (en) | 2004-03-16 | 2023-11-07 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US10156959B2 (en) | 2005-03-16 | 2018-12-18 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US11201755B2 (en) | 2004-03-16 | 2021-12-14 | Icontrol Networks, Inc. | Premises system management using status signal |
US10237237B2 (en) | 2007-06-12 | 2019-03-19 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10200504B2 (en) | 2007-06-12 | 2019-02-05 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US7412842B2 (en) | 2004-04-27 | 2008-08-19 | Emerson Climate Technologies, Inc. | Compressor diagnostic and protection system |
US7275377B2 (en) | 2004-08-11 | 2007-10-02 | Lawrence Kates | Method and apparatus for monitoring refrigerant-cycle systems |
US11615697B2 (en) | 2005-03-16 | 2023-03-28 | Icontrol Networks, Inc. | Premise management systems and methods |
US11496568B2 (en) | 2005-03-16 | 2022-11-08 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US11700142B2 (en) | 2005-03-16 | 2023-07-11 | Icontrol Networks, Inc. | Security network integrating security system and network devices |
US10999254B2 (en) | 2005-03-16 | 2021-05-04 | Icontrol Networks, Inc. | System for data routing in networks |
US20110128378A1 (en) | 2005-03-16 | 2011-06-02 | Reza Raji | Modular Electronic Display Platform |
US20170180198A1 (en) | 2008-08-11 | 2017-06-22 | Marc Baum | Forming a security network including integrated security system components |
US20120324566A1 (en) | 2005-03-16 | 2012-12-20 | Marc Baum | Takeover Processes In Security Network Integrated With Premise Security System |
US9306809B2 (en) | 2007-06-12 | 2016-04-05 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US10079839B1 (en) | 2007-06-12 | 2018-09-18 | Icontrol Networks, Inc. | Activation of gateway device |
US11706279B2 (en) | 2007-01-24 | 2023-07-18 | Icontrol Networks, Inc. | Methods and systems for data communication |
US8010589B2 (en) * | 2007-02-20 | 2011-08-30 | Xerox Corporation | Semi-automatic system with an iterative learning method for uncovering the leading indicators in business processes |
US7633385B2 (en) | 2007-02-28 | 2009-12-15 | Ucontrol, Inc. | Method and system for communicating with and controlling an alarm system from a remote server |
US8451986B2 (en) | 2007-04-23 | 2013-05-28 | Icontrol Networks, Inc. | Method and system for automatically providing alternate network access for telecommunications |
US10666523B2 (en) | 2007-06-12 | 2020-05-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10498830B2 (en) | 2007-06-12 | 2019-12-03 | Icontrol Networks, Inc. | Wi-Fi-to-serial encapsulation in systems |
US11218878B2 (en) | 2007-06-12 | 2022-01-04 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10423309B2 (en) | 2007-06-12 | 2019-09-24 | Icontrol Networks, Inc. | Device integration framework |
US11316753B2 (en) | 2007-06-12 | 2022-04-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11601810B2 (en) | 2007-06-12 | 2023-03-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10389736B2 (en) | 2007-06-12 | 2019-08-20 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10051078B2 (en) | 2007-06-12 | 2018-08-14 | Icontrol Networks, Inc. | WiFi-to-serial encapsulation in systems |
US11423756B2 (en) | 2007-06-12 | 2022-08-23 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11646907B2 (en) | 2007-06-12 | 2023-05-09 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10523689B2 (en) | 2007-06-12 | 2019-12-31 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US11089122B2 (en) | 2007-06-12 | 2021-08-10 | Icontrol Networks, Inc. | Controlling data routing among networks |
US11237714B2 (en) | 2007-06-12 | 2022-02-01 | Control Networks, Inc. | Control system user interface |
US11212192B2 (en) | 2007-06-12 | 2021-12-28 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10616075B2 (en) * | 2007-06-12 | 2020-04-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
WO2008157494A2 (en) * | 2007-06-15 | 2008-12-24 | Shell Oil Company | Framework and method for monitoring equipment |
US20090037142A1 (en) | 2007-07-30 | 2009-02-05 | Lawrence Kates | Portable method and apparatus for monitoring refrigerant-cycle systems |
US11831462B2 (en) | 2007-08-24 | 2023-11-28 | Icontrol Networks, Inc. | Controlling data routing in premises management systems |
US8688700B2 (en) | 2007-10-19 | 2014-04-01 | Oracle International Corporation | Scrubbing and editing of diagnostic data |
US9140728B2 (en) | 2007-11-02 | 2015-09-22 | Emerson Climate Technologies, Inc. | Compressor sensor module |
US11916928B2 (en) | 2008-01-24 | 2024-02-27 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US20170185278A1 (en) | 2008-08-11 | 2017-06-29 | Icontrol Networks, Inc. | Automation system user interface |
US10530839B2 (en) | 2008-08-11 | 2020-01-07 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US11792036B2 (en) | 2008-08-11 | 2023-10-17 | Icontrol Networks, Inc. | Mobile premises automation platform |
US11729255B2 (en) | 2008-08-11 | 2023-08-15 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US11758026B2 (en) | 2008-08-11 | 2023-09-12 | Icontrol Networks, Inc. | Virtual device systems and methods |
US11258625B2 (en) | 2008-08-11 | 2022-02-22 | Icontrol Networks, Inc. | Mobile premises automation platform |
US8638211B2 (en) | 2009-04-30 | 2014-01-28 | Icontrol Networks, Inc. | Configurable controller and interface for home SMA, phone and multimedia |
US8417656B2 (en) * | 2009-06-16 | 2013-04-09 | Oracle International Corporation | Techniques for building an aggregate model for performing diagnostics |
US8171343B2 (en) | 2009-06-16 | 2012-05-01 | Oracle International Corporation | Techniques for determining models for performing diagnostics |
US8140898B2 (en) * | 2009-06-16 | 2012-03-20 | Oracle International Corporation | Techniques for gathering evidence for performing diagnostics |
US8326789B2 (en) | 2009-08-20 | 2012-12-04 | Uop Llc | Expert system integrated with remote performance management |
IT1395935B1 (en) | 2009-09-29 | 2012-11-02 | Nuovo Pignone Spa | SYSTEM FOR THE ACQUISITION, MEASUREMENT AND CONTROL OF THE OPERATING PARAMETERS OF AN ALTERNATIVE FLUID MACHINE |
US20110138335A1 (en) * | 2009-12-08 | 2011-06-09 | Sybase, Inc. | Thin analytics for enterprise mobile users |
US8612377B2 (en) * | 2009-12-17 | 2013-12-17 | Oracle International Corporation | Techniques for generating diagnostic results |
US9122273B2 (en) * | 2010-02-26 | 2015-09-01 | Hitachi, Ltd. | Failure cause diagnosis system and method |
EP2569712B1 (en) | 2010-05-10 | 2021-10-13 | Icontrol Networks, Inc. | Control system user interface |
US20110292834A1 (en) * | 2010-05-27 | 2011-12-01 | International Business Machines Corporation | Maintaining Time Series Models for Information Technology System Parameters |
US8836467B1 (en) | 2010-09-28 | 2014-09-16 | Icontrol Networks, Inc. | Method, system and apparatus for automated reporting of account and sensor zone information to a central station |
US9046891B2 (en) | 2010-10-22 | 2015-06-02 | Honeywell International Inc. | Control effector health capabilities determination reasoning system and method |
US11750414B2 (en) | 2010-12-16 | 2023-09-05 | Icontrol Networks, Inc. | Bidirectional security sensor communication for a premises security system |
US9147337B2 (en) | 2010-12-17 | 2015-09-29 | Icontrol Networks, Inc. | Method and system for logging security event data |
WO2012118830A2 (en) | 2011-02-28 | 2012-09-07 | Arensmeier Jeffrey N | Residential solutions hvac monitoring and diagnosis |
US20130115109A1 (en) * | 2011-05-05 | 2013-05-09 | William G. Hall | Compressor discharge temperature monitor and alarm |
US9310790B2 (en) * | 2011-05-23 | 2016-04-12 | Honeywell International Inc. | Large-scale comprehensive real-time monitoring framework for industrial facilities |
US20130103767A1 (en) * | 2011-10-21 | 2013-04-25 | Microsoft Corporation | Return notifications of tasks performed with entities |
US8930756B2 (en) * | 2011-12-22 | 2015-01-06 | International Business Machines Corporation | Grouping related errors in a distributed computing environment |
JP2013132551A (en) * | 2011-12-26 | 2013-07-08 | Angel Playing Cards Co Ltd | Simple shuffling device |
CN102562564B (en) * | 2012-01-11 | 2014-10-01 | 福州大学 | Hardware system of high-pressure pump performance test table using PXI bus technology |
US8964338B2 (en) | 2012-01-11 | 2015-02-24 | Emerson Climate Technologies, Inc. | System and method for compressor motor protection |
CN102562565B (en) * | 2012-01-13 | 2015-04-22 | 杭州哲达科技股份有限公司 | Method and device for water pump delivery inspection |
US9477936B2 (en) | 2012-02-09 | 2016-10-25 | Rockwell Automation Technologies, Inc. | Cloud-based operator interface for industrial automation |
ITCO20120008A1 (en) * | 2012-03-01 | 2013-09-02 | Nuovo Pignone Srl | METHOD AND SYSTEM FOR MONITORING THE CONDITION OF A GROUP OF PLANTS |
US20130282333A1 (en) * | 2012-04-23 | 2013-10-24 | Abb Technology Ag | Service port explorer |
US9525976B2 (en) * | 2012-05-10 | 2016-12-20 | Honeywell International Inc. | BIM-aware location based application |
EP2875409A4 (en) * | 2012-07-19 | 2017-02-15 | Saudi Arabian Oil Company | System and method for effective plant performance monitoring in gas oil separation plant (gosp) |
US20140032172A1 (en) * | 2012-07-24 | 2014-01-30 | General Electric Company | Systems and methods for health assessment of a human-machine interface (hmi) device |
US9043263B2 (en) * | 2012-07-24 | 2015-05-26 | General Electric Company | Systems and methods for control reliability operations using TMR |
US9218233B2 (en) * | 2012-07-24 | 2015-12-22 | Paul Venditti | Systems and methods for control reliability operations |
US9665090B2 (en) | 2012-07-24 | 2017-05-30 | General Electric Company | Systems and methods for rule-based control system reliability |
US20140032169A1 (en) * | 2012-07-24 | 2014-01-30 | General Electric Company | Systems and methods for improving control system reliability |
US9479388B2 (en) | 2012-08-29 | 2016-10-25 | Maintenance Assistant Inc | Computer system and method for maintenance management including collaboration across clients |
US10169743B2 (en) | 2012-08-29 | 2019-01-01 | Fiix Inc. | Computer system and method for maintenance management including collaboration across clients |
JP5652444B2 (en) * | 2012-08-31 | 2015-01-14 | 横河電機株式会社 | Maintenance support system and method |
US9626634B2 (en) * | 2012-09-12 | 2017-04-18 | Abb Schweiz Ag | Industrial plant equipment, process and maintenance optimization |
US9310439B2 (en) | 2012-09-25 | 2016-04-12 | Emerson Climate Technologies, Inc. | Compressor having a control and diagnostic module |
US20150222639A1 (en) * | 2012-10-22 | 2015-08-06 | Cyber-Ark Software Ltd. | Maintaining Continuous Operational Access Augmented with User Authentication and Action Attribution in Shared Environments |
US20150337823A1 (en) * | 2012-11-08 | 2015-11-26 | Viking At, Llc | Lubricant-Free Compressor Having a Graphite Piston in a Glass Cylinder |
US9594491B2 (en) * | 2012-11-26 | 2017-03-14 | Ca, Inc. | Slide control for setting boundaries between regions of a data range |
DE102012222661A1 (en) * | 2012-12-10 | 2014-06-12 | Robert Bosch Gmbh | Monitoring system for a surveillance area, procedures and computer program |
US9201113B2 (en) | 2012-12-17 | 2015-12-01 | General Electric Company | Systems and methods for performing redundancy tests on turbine controls |
CN103105778B (en) * | 2013-02-05 | 2015-07-15 | 中原工学院 | Estimation method for industrial process simulation mathematical model parameters |
WO2014144446A1 (en) | 2013-03-15 | 2014-09-18 | Emerson Electric Co. | Hvac system remote monitoring and diagnosis |
US9803902B2 (en) | 2013-03-15 | 2017-10-31 | Emerson Climate Technologies, Inc. | System for refrigerant charge verification using two condenser coil temperatures |
WO2014145056A1 (en) | 2013-03-15 | 2014-09-18 | Adt Us Holdings, Inc. | Security system health monitoring |
US9551504B2 (en) | 2013-03-15 | 2017-01-24 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
AU2014248049B2 (en) | 2013-04-05 | 2018-06-07 | Emerson Climate Technologies, Inc. | Heat-pump system with refrigerant charge diagnostics |
CN104995570B (en) * | 2013-04-25 | 2017-09-22 | 西门子公司 | A kind of industrial monitoring system |
US9786197B2 (en) | 2013-05-09 | 2017-10-10 | Rockwell Automation Technologies, Inc. | Using cloud-based data to facilitate enhancing performance in connection with an industrial automation system |
US9703902B2 (en) | 2013-05-09 | 2017-07-11 | Rockwell Automation Technologies, Inc. | Using cloud-based data for industrial simulation |
US9989958B2 (en) | 2013-05-09 | 2018-06-05 | Rockwell Automation Technologies, Inc. | Using cloud-based data for virtualization of an industrial automation environment |
US9438648B2 (en) | 2013-05-09 | 2016-09-06 | Rockwell Automation Technologies, Inc. | Industrial data analytics in a cloud platform |
US9665843B2 (en) | 2013-06-03 | 2017-05-30 | Abb Schweiz Ag | Industrial asset health profile |
US10528357B2 (en) | 2014-01-17 | 2020-01-07 | L3 Technologies, Inc. | Web-based recorder configuration utility |
US11405463B2 (en) | 2014-03-03 | 2022-08-02 | Icontrol Networks, Inc. | Media content management |
US11146637B2 (en) | 2014-03-03 | 2021-10-12 | Icontrol Networks, Inc. | Media content management |
US9628340B2 (en) * | 2014-05-05 | 2017-04-18 | Ciena Corporation | Proactive operations, administration, and maintenance systems and methods in networks using data analytics |
US9912733B2 (en) | 2014-07-31 | 2018-03-06 | General Electric Company | System and method for maintaining the health of a control system |
US20160092808A1 (en) * | 2014-09-25 | 2016-03-31 | Yu Cheng | Predictive maintenance for critical components based on causality analysis |
US10247705B2 (en) * | 2014-10-01 | 2019-04-02 | Sensor Networks, Inc. | Asset-condition monitoring system |
US10908130B2 (en) | 2014-10-01 | 2021-02-02 | Sensor Networks, Inc. | Asset integrity monitoring using cellular networks |
CN104483566A (en) * | 2014-12-04 | 2015-04-01 | 国家电网公司 | Power grid data acquisition method and device |
US11513477B2 (en) | 2015-03-16 | 2022-11-29 | Rockwell Automation Technologies, Inc. | Cloud-based industrial controller |
US11243505B2 (en) | 2015-03-16 | 2022-02-08 | Rockwell Automation Technologies, Inc. | Cloud-based analytics for industrial automation |
US11042131B2 (en) | 2015-03-16 | 2021-06-22 | Rockwell Automation Technologies, Inc. | Backup of an industrial automation plant in the cloud |
US10496061B2 (en) | 2015-03-16 | 2019-12-03 | Rockwell Automation Technologies, Inc. | Modeling of an industrial automation environment in the cloud |
US11042128B2 (en) * | 2015-03-18 | 2021-06-22 | Accenture Global Services Limited | Method and system for predicting equipment failure |
US10129156B2 (en) * | 2015-03-31 | 2018-11-13 | At&T Intellectual Property I, L.P. | Dynamic creation and management of ephemeral coordinated feedback instances |
CN106151085B (en) | 2015-04-09 | 2019-12-03 | 开利公司 | Fluid device surge monitoring method and refrigeration system |
WO2016170798A1 (en) * | 2015-04-22 | 2016-10-27 | Sharp Kabushiki Kaisha | Systems and methods for content information communication |
US9811699B2 (en) | 2015-05-15 | 2017-11-07 | Schlumberger Technology Corporation | Master tracking device |
DE102016008987B4 (en) * | 2015-07-31 | 2021-09-16 | Fanuc Corporation | Machine learning method and machine learning apparatus for learning failure conditions, and failure prediction apparatus and failure prediction system including the machine learning apparatus |
US10775274B2 (en) | 2015-08-12 | 2020-09-15 | Baker Hughes, A Ge Conipany, Llc | Analyzing machinery operating parameters |
US9694834B2 (en) * | 2015-10-19 | 2017-07-04 | Elecro-Motive Diesel, Inc. | Machine asset management system having user interface |
US9688296B2 (en) * | 2015-10-19 | 2017-06-27 | Electro-Motive Diesel, Inc. | Remote data backup for locomotive on-board equipment |
KR102006436B1 (en) * | 2015-10-30 | 2019-08-01 | 삼성에스디에스 주식회사 | Method for detecting false alarm |
US9945375B2 (en) | 2016-01-20 | 2018-04-17 | Caterpillar Inc. | System and method for automatic tuning of reference model for fracking rig pump |
JP6333868B2 (en) * | 2016-01-21 | 2018-05-30 | ファナック株式会社 | Cell control device and production system for managing the operating status of a plurality of manufacturing machines in a manufacturing cell |
US20180284741A1 (en) * | 2016-05-09 | 2018-10-04 | StrongForce IoT Portfolio 2016, LLC | Methods and systems for industrial internet of things data collection for a chemical production process |
WO2018012391A1 (en) * | 2016-07-15 | 2018-01-18 | 株式会社村田製作所 | Rfid tag manufacturing device and rfid tag manufacturing method |
GB2553299B (en) * | 2016-08-29 | 2019-02-06 | Aker Solutions Ltd | Monitoring operational performance of a subsea pump for pumping product from a formation |
US10628567B2 (en) * | 2016-09-05 | 2020-04-21 | International Business Machines Corporation | User authentication using prompted text |
US10126284B1 (en) * | 2016-09-15 | 2018-11-13 | Jentek Water Treatment, Inc. | System and method for monitoring water treatment systems |
US11003988B2 (en) * | 2016-11-23 | 2021-05-11 | General Electric Company | Hardware system design improvement using deep learning algorithms |
US10979305B1 (en) * | 2016-12-29 | 2021-04-13 | Wells Fargo Bank, N.A. | Web interface usage tracker |
US11061424B2 (en) | 2017-01-12 | 2021-07-13 | Johnson Controls Technology Company | Building energy storage system with peak load contribution and stochastic cost optimization |
US10995746B2 (en) * | 2017-01-17 | 2021-05-04 | Innio Jenbacher Gmbh & Co Og | Two-stage reciprocating compressor optimization control system |
US11847617B2 (en) | 2017-02-07 | 2023-12-19 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with financial analysis functionality |
US11900287B2 (en) | 2017-05-25 | 2024-02-13 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with budgetary constraints |
US11277420B2 (en) | 2017-02-24 | 2022-03-15 | Ciena Corporation | Systems and methods to detect abnormal behavior in networks |
US11130111B2 (en) * | 2017-03-28 | 2021-09-28 | Uop Llc | Air-cooled heat exchangers |
US11396002B2 (en) * | 2017-03-28 | 2022-07-26 | Uop Llc | Detecting and correcting problems in liquid lifting in heat exchangers |
US10333906B2 (en) * | 2017-03-30 | 2019-06-25 | Bank Of America Corporation | Network communication decoder using key pattern encryption |
US11120411B2 (en) | 2017-05-25 | 2021-09-14 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with incentive incorporation |
US11409274B2 (en) | 2017-05-25 | 2022-08-09 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system for performing maintenance as soon as economically viable |
US11636429B2 (en) | 2017-05-25 | 2023-04-25 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance systems and methods with automatic parts resupply |
US11747800B2 (en) | 2017-05-25 | 2023-09-05 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with automatic service work order generation |
JP7184797B2 (en) * | 2017-05-25 | 2022-12-06 | ジョンソン コントロールズ テクノロジー カンパニー | Model predictive maintenance system for building equipment |
US11416955B2 (en) | 2017-05-25 | 2022-08-16 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with integrated measurement and verification functionality |
US10102693B1 (en) * | 2017-05-30 | 2018-10-16 | Deere & Company | Predictive analysis system and method for analyzing and detecting machine sensor failures |
WO2018220813A1 (en) * | 2017-06-02 | 2018-12-06 | 富士通株式会社 | Assessment device, assessment method, and assessment program |
US11493348B2 (en) | 2017-06-23 | 2022-11-08 | Direct Current Capital LLC | Methods for executing autonomous rideshare requests |
DE102017116167A1 (en) * | 2017-07-18 | 2019-01-24 | Endress+Hauser Process Solutions Ag | Method for monitoring an automation system |
US11721195B2 (en) * | 2017-10-06 | 2023-08-08 | Raven Telemetry Inc. | Augmented industrial management |
US11348013B2 (en) * | 2017-10-31 | 2022-05-31 | Vie Technologies Inc. | Determining, encoding, and transmission of classification variables at end-device for remote monitoring |
US10416661B2 (en) * | 2017-11-30 | 2019-09-17 | Abb Schweiz Ag | Apparatuses, systems and methods of secure cloud-based monitoring of industrial plants |
CN109944787A (en) * | 2017-12-20 | 2019-06-28 | 长城汽车股份有限公司 | A kind of determination method and apparatus of compressor of air conditioner |
US20190236497A1 (en) * | 2018-01-31 | 2019-08-01 | Koninklijke Philips N.V. | System and method for automated model selection for key performance indicator forecasting |
JP6528869B1 (en) * | 2018-02-13 | 2019-06-12 | オムロン株式会社 | Session control apparatus, session control method and program |
CN110224970B (en) * | 2018-03-01 | 2021-11-23 | 西门子公司 | Safety monitoring method and device for industrial control system |
US10829698B2 (en) | 2018-03-16 | 2020-11-10 | Uop Llc | Power recovery from quench and dilution vapor streams |
US11131218B2 (en) | 2018-03-16 | 2021-09-28 | Uop Llc | Processes for adjusting at least one process condition of a chemical processing unit with a turbine |
US10690010B2 (en) | 2018-03-16 | 2020-06-23 | Uop Llc | Steam reboiler with turbine |
US10745631B2 (en) | 2018-03-16 | 2020-08-18 | Uop Llc | Hydroprocessing unit with power recovery turbines |
US10871085B2 (en) | 2018-03-16 | 2020-12-22 | Uop Llc | Energy-recovery turbines for gas streams |
US11507031B2 (en) | 2018-03-16 | 2022-11-22 | Uop Llc | Recovered electric power measuring system and method for collecting data from a recovered electric power measuring system |
US10811884B2 (en) | 2018-03-16 | 2020-10-20 | Uop Llc | Consolidation and use of power recovered from a turbine in a process unit |
US10508568B2 (en) | 2018-03-16 | 2019-12-17 | Uop Llc | Process improvement through the addition of power recovery turbine equipment in existing processes |
US10794225B2 (en) | 2018-03-16 | 2020-10-06 | Uop Llc | Turbine with supersonic separation |
US11194301B2 (en) | 2018-03-16 | 2021-12-07 | Uop Llc | System for power recovery from quench and dilution vapor streams |
US10753235B2 (en) | 2018-03-16 | 2020-08-25 | Uop Llc | Use of recovered power in a process |
SG11202009473XA (en) * | 2018-03-29 | 2020-10-29 | Central Glass Co Ltd | Substrate processing gas, storage container, and substrate processing method |
US11157710B2 (en) * | 2018-05-04 | 2021-10-26 | Rowan Companies, Inc. | System and method for monitoring operations and personnel in designated areas on offshore unit |
CN108775281B (en) * | 2018-06-25 | 2019-07-23 | 西安交通大学 | A kind of the F-V figure monitoring method and device of reciprocating compressor |
US10920624B2 (en) | 2018-06-27 | 2021-02-16 | Uop Llc | Energy-recovery turbines for gas streams |
CN109162912B (en) * | 2018-09-10 | 2020-06-23 | 贵州省水利水电勘测设计研究院 | Method and system for monitoring and controlling water pumping device |
US11275488B2 (en) | 2018-10-23 | 2022-03-15 | International Business Machines Corporation | Augmenting user interface to convey a state of drilling operations |
SE543122C2 (en) * | 2019-02-05 | 2020-10-13 | Brokk Ab | Method, device and user interface describing an operational state of operation of a demolition robot |
WO2020247557A1 (en) * | 2019-06-04 | 2020-12-10 | Phantom Auto Inc. | Platform for redundant wireless communications optimization |
US11480360B2 (en) | 2019-08-06 | 2022-10-25 | Johnson Controls Tyco IP Holdings LLP | Building HVAC system with modular cascaded model |
CN114730182A (en) * | 2019-11-12 | 2022-07-08 | 阿韦瓦软件有限责任公司 | Computerized system and method for automatically detecting anomalies in a distributed SCADA system and thereby dynamically displaying a unified interface |
DE102020109858A1 (en) * | 2020-04-08 | 2021-10-14 | Balluff Gmbh | Method of operating a system |
CN112081734B (en) * | 2020-07-28 | 2022-05-03 | 中广核核电运营有限公司 | Method and system for testing performance of double-acting plunger pump |
US20220164730A1 (en) * | 2020-11-25 | 2022-05-26 | Well Thought LLC | Multi-factor real time decision making for oil and gas operations |
US20220365508A1 (en) * | 2021-05-12 | 2022-11-17 | Bell And Howell, Llc | Service console log processing devices, systems, and methods |
Family Cites Families (124)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2238914A (en) * | 1931-02-24 | 1941-04-22 | Pearson Erick | Control system for the remote operation of power plants |
US2172918A (en) * | 1934-11-27 | 1939-09-12 | Pittsburgh Equitable Meter Co | Remote indicating and control system |
US2191997A (en) * | 1938-09-24 | 1940-02-27 | Brown Instr Co | Measuring and control apparatus |
US2699328A (en) * | 1949-04-02 | 1955-01-11 | Union Carbide & Carbon Corp | Mining process and system by remote control |
US2901728A (en) * | 1951-04-10 | 1959-08-25 | North Electric Co | Supervisory control system |
US2864943A (en) * | 1954-02-24 | 1958-12-16 | Motorola Inc | Central station interrogation via relays of unattended data satellites which answer back |
US2883255A (en) * | 1954-04-28 | 1959-04-21 | Panellit Inc | Automatic process logging system |
US2940069A (en) * | 1954-11-15 | 1960-06-07 | Gen Electric | Combined supervisory control and telemetering system |
US2913703A (en) * | 1955-10-28 | 1959-11-17 | Kunits Paul Von | Automatic control system with remote supervision |
US2922142A (en) * | 1957-05-29 | 1960-01-19 | Rca Corp | Remote control system |
US2922475A (en) * | 1958-04-09 | 1960-01-26 | Industrial Nucleonics Corp | Measuring and controlling system |
US2939054A (en) * | 1958-06-25 | 1960-05-31 | Frank E Caruso | Remote control device |
US3046525A (en) * | 1958-09-16 | 1962-07-24 | Bell Telephone Labor Inc | Supervisory control system |
US3110013A (en) * | 1960-07-11 | 1963-11-05 | North Electric Co | Supervisory control and communications system |
US3219107A (en) * | 1960-09-14 | 1965-11-23 | Socony Mobil Oil Co Inc | Remote and automatic control of petroleum production |
US3321613A (en) * | 1961-09-19 | 1967-05-23 | Automation Man Inc | Measuring instrument |
US3116753A (en) * | 1961-12-21 | 1964-01-07 | Foxboro Co | Industrial process control apparatus |
US3268867A (en) * | 1962-07-16 | 1966-08-23 | North Electric Co | Pressurized cable monitoring system having direct current interrogation of remote monitoring apparatus |
US3397386A (en) * | 1963-04-03 | 1968-08-13 | Leeds & Northrup Co | Telemetering and supervisory control system having normally continuous telemetering signals |
US3441053A (en) * | 1965-10-22 | 1969-04-29 | Foxboro Co | Industrial process control apparatus |
US3368757A (en) * | 1966-10-03 | 1968-02-13 | Coulombe Alyre | Monitor and control for process variables |
US3566355A (en) * | 1968-03-07 | 1971-02-23 | Motorola Inc | Supervisory control system |
US3611290A (en) * | 1968-06-03 | 1971-10-05 | North American Rockwell | Fingerprint minutiae reading device |
US3555516A (en) * | 1968-08-26 | 1971-01-12 | Allen Bradley Co | Supervisory system for time-shared numerical control system |
GB2086061B (en) * | 1980-10-13 | 1985-05-22 | Marconi Instruments Ltd | Automatic test systems |
US4559610A (en) * | 1983-05-04 | 1985-12-17 | Southwest Research Corporation | Gas pumping system analog |
US4573115A (en) * | 1983-10-28 | 1986-02-25 | Standard Oil Company (Indiana) | Supervisory control system for remotely monitoring and controlling at least one operational device |
US4568909A (en) * | 1983-12-19 | 1986-02-04 | United Technologies Corporation | Remote elevator monitoring system |
US4622538A (en) * | 1984-07-18 | 1986-11-11 | Otis Elevator Company | Remote monitoring system state machine and method |
JPS60235050A (en) | 1984-05-07 | 1985-11-21 | Toyota Motor Corp | Method for controlling current supplied to electric heater of oxygen sensor |
EP0252131A1 (en) * | 1986-01-14 | 1988-01-13 | Auditel Systems Pty. Ltd. | Remote process control apparatus |
US4831873A (en) * | 1986-04-04 | 1989-05-23 | Movats Incorporated | Method and apparatus for remote monitoring of valves and valve operators |
US5000040A (en) * | 1986-04-04 | 1991-03-19 | Movats Incorporated | Method and apparatus for remote monitoring of valves and valve operators |
US4891975A (en) * | 1986-04-04 | 1990-01-09 | Movats Incorporated | Method and apparatus for remote monitoring of valves and valve operators |
JPH0631615B2 (en) * | 1986-12-16 | 1994-04-27 | 三菱電機株式会社 | Gas compressor |
EP0283610A1 (en) * | 1987-03-27 | 1988-09-28 | Hewlett-Packard Limited | Improvements in or relating to the testing of electronic equipment |
JPH01286626A (en) * | 1988-01-18 | 1989-11-17 | Hitachi Ltd | Data encoding system |
WO1989008362A1 (en) * | 1988-02-29 | 1989-09-08 | Kabushiki Kaisha Komatsu Seisakusho | Series control unit and method of control |
CA2034421C (en) * | 1990-03-26 | 1995-12-19 | Subhash C. Singhal | Quality control using multi-process performance analysis |
US5930136A (en) * | 1990-06-04 | 1999-07-27 | Hitachi, Ltd. | Control device for controlling a controlled apparatus, and a control method therefor |
US5210704A (en) * | 1990-10-02 | 1993-05-11 | Technology International Incorporated | System for prognosis and diagnostics of failure and wearout monitoring and for prediction of life expectancy of helicopter gearboxes and other rotating equipment |
WO1992015951A1 (en) * | 1991-03-04 | 1992-09-17 | Inference Corporation | Case-based reasoning system |
US5461311A (en) | 1992-12-24 | 1995-10-24 | Kayaba Kogyo Kabushiki Kaisha | Rod axial position detector including plural scales wherein nonmagnetized portions have differing spacing and differing depths and means for calculating the absolute position are provided |
US5355735A (en) * | 1993-02-23 | 1994-10-18 | Datrend Systems Inc. | Apparatus for metering liquid flow |
JPH06294371A (en) | 1993-04-12 | 1994-10-21 | Mitsubishi Electric Corp | Internal combustion engine ignition device |
GB9412264D0 (en) * | 1994-06-18 | 1994-08-10 | Int Computers Ltd | Console facility for a computer system |
US5890142A (en) * | 1995-02-10 | 1999-03-30 | Kabushiki Kaisha Meidensha | Apparatus for monitoring system condition |
US6208266B1 (en) * | 1995-08-23 | 2001-03-27 | Scientific Telemetry Corporation | Remote data acquisition and processing system |
US6489884B1 (en) * | 1996-01-30 | 2002-12-03 | Skf Condition Monitoring | Apparatus and method for the remote monitoring of machine condition |
US5845230A (en) * | 1996-01-30 | 1998-12-01 | Skf Condition Monitoring | Apparatus and method for the remote monitoring of machine condition |
US6842742B1 (en) * | 1996-04-23 | 2005-01-11 | Ascom Hasler Mailing Systems, Inc. | System for providing early warning preemptive postal equipment replacement |
US5892758A (en) * | 1996-07-11 | 1999-04-06 | Qualcomm Incorporated | Concentrated subscriber wireless remote telemetry system |
US6445969B1 (en) * | 1997-01-27 | 2002-09-03 | Circuit Image Systems | Statistical process control integration systems and methods for monitoring manufacturing processes |
US6437692B1 (en) * | 1998-06-22 | 2002-08-20 | Statsignal Systems, Inc. | System and method for monitoring and controlling remote devices |
ATE464614T1 (en) * | 1998-08-14 | 2010-04-15 | 3M Innovative Properties Co | METHOD OF USING A PORTABLE RFID READER |
CN100492388C (en) | 1998-08-14 | 2009-05-27 | 3M创新有限公司 | Radio frequency identification system applications |
US7308322B1 (en) * | 1998-09-29 | 2007-12-11 | Rockwell Automation Technologies, Inc. | Motorized system integrated control and diagnostics using vibration, pressure, temperature, speed, and/or current analysis |
US6757665B1 (en) | 1999-09-28 | 2004-06-29 | Rockwell Automation Technologies, Inc. | Detection of pump cavitation/blockage and seal failure via current signature analysis |
WO2000019369A1 (en) * | 1998-10-01 | 2000-04-06 | Bios Group Lp | Automatic evolution of mixed analog and digital electronic circuits |
US7103511B2 (en) * | 1998-10-14 | 2006-09-05 | Statsignal Ipc, Llc | Wireless communication networks for providing remote monitoring of devices |
EP1014240A1 (en) * | 1998-12-17 | 2000-06-28 | Siemens Aktiengesellschaft | A system of case-based reasoning for sensor prediction in a technical process, especially in a cement kiln, method and apparatus therefore |
US8044793B2 (en) * | 2001-03-01 | 2011-10-25 | Fisher-Rosemount Systems, Inc. | Integrated device alerts in a process control system |
ATE383645T1 (en) * | 1999-03-30 | 2008-01-15 | Nidec Sankyo Corp | DATA DEMODULATION METHOD AND APPARATUS FOR MAGNETIC CARD. |
US6947797B2 (en) * | 1999-04-02 | 2005-09-20 | General Electric Company | Method and system for diagnosing machine malfunctions |
GB2349020A (en) * | 1999-04-17 | 2000-10-18 | Interface Inf Syst Ltd | Monitoring condition of a machine |
US6292757B1 (en) | 1999-08-16 | 2001-09-18 | Windrock, Inc. | Method and apparatus for continuously monitoring parameters of reciprocating compressor cylinders |
US6635512B1 (en) * | 1999-11-04 | 2003-10-21 | Rohm Co., Ltd. | Method of producing a semiconductor device by dividing a semiconductor wafer into separate pieces of semiconductor chips |
US6745321B1 (en) * | 1999-11-08 | 2004-06-01 | International Business Machines Corporation | Method and apparatus for harvesting problematic code sections aggravating hardware design flaws in a microprocessor |
US6453265B1 (en) | 1999-12-28 | 2002-09-17 | Hewlett-Packard Company | Accurately predicting system behavior of a managed system using genetic programming |
US6353390B1 (en) * | 1999-12-31 | 2002-03-05 | Jeffrey Beri | Method and system of configuring a boundary and tracking an object thereby |
CN1433534A (en) * | 2000-01-29 | 2003-07-30 | Abb研究有限公司 | System and method for determining overall equipment feeectiveness of production plants, failure events and failure causes |
US6522768B1 (en) * | 2000-01-31 | 2003-02-18 | Hewlett-Packard Company | Predicting system behavior of a managed system using pattern recognition techniques |
AU4733601A (en) | 2000-03-10 | 2001-09-24 | Cyrano Sciences Inc | Control for an industrial process using one or more multidimensional variables |
US6754673B2 (en) | 2000-06-14 | 2004-06-22 | General Electric Company | Method and system for assessing plant parameters and performance over a global network |
JP2002032274A (en) * | 2000-07-19 | 2002-01-31 | Hitachi Ltd | Remote diagnostic system of equipment and remote diagnostic method |
US20020067361A1 (en) * | 2000-12-02 | 2002-06-06 | Jens Rennert | Screen raster generation via programmable lookup tables |
JP2002182725A (en) * | 2000-12-11 | 2002-06-26 | Japan Institute Of Plant Maintenance | Facility overall efficiency calculating device in work factory |
ITPC20000041A1 (en) * | 2000-12-27 | 2002-06-27 | Aem Gas Spa | APPARATUS AND METHOD FOR DETECTION OF DATA AND REMOTE CONTROL OF EVENTS THROUGH THE ETHERNET NETWORK, IN PARTICULAR FOR CONTROL |
JP4160399B2 (en) | 2001-03-01 | 2008-10-01 | フィッシャー−ローズマウント システムズ, インコーポレイテッド | Creating and displaying indicators in the process plant |
US6646564B1 (en) * | 2001-03-07 | 2003-11-11 | L'air Liquide Societe Anonyme A Directoire Et Conseil De Surveillance Pour L'etude Et L'exploitation Des Procedes Georges Claude | System and method for remote management of equipment operating parameters |
US6587754B2 (en) * | 2001-03-19 | 2003-07-01 | General Electric Company | System and methods for remote management of steam generating systems |
US20020183971A1 (en) * | 2001-04-10 | 2002-12-05 | Wegerich Stephan W. | Diagnostic systems and methods for predictive condition monitoring |
US6819327B2 (en) * | 2001-05-18 | 2004-11-16 | Sun Microsystems, Inc. | Signature analysis registers for testing a computer graphics system |
US20020198978A1 (en) * | 2001-06-22 | 2002-12-26 | Watkins Gregg S. | System to remotely control and monitor devices and data |
US6748341B2 (en) | 2002-04-12 | 2004-06-08 | George E. Crowder, Jr. | Method and device for machinery diagnostics and prognostics |
US7260505B2 (en) | 2002-06-26 | 2007-08-21 | Honeywell International, Inc. | Method and apparatus for developing fault codes for complex systems based on historical data |
GB0216858D0 (en) * | 2002-07-19 | 2002-08-28 | Bae Systems Plc | Fault diagnosis system |
US7287164B2 (en) | 2002-09-12 | 2007-10-23 | International Business Machines Corporation | Method and system for encoding signatures to authenticate files |
WO2004036357A2 (en) * | 2002-10-15 | 2004-04-29 | Informance International | Graphical overall equipment effectiveness system & method |
FR2848044B1 (en) * | 2002-11-28 | 2005-04-01 | Qosmos | METHOD AND COMPUTER SYSTEM FOR TRIGGERING ACTION ON DIGITAL COMMUNICATION DATA |
US6799143B1 (en) * | 2002-12-10 | 2004-09-28 | Abb Inc. | Process and device for evaluating the performance of a process control system |
US7930490B2 (en) | 2002-12-23 | 2011-04-19 | Siemens Industry, Inc. | Method for utilizing a memory device for a programmable logic controller (PLC) |
US6999884B2 (en) * | 2003-01-10 | 2006-02-14 | Oxford Biosignals Limited | Bearing anomaly detection and location |
US7584165B2 (en) | 2003-01-30 | 2009-09-01 | Landmark Graphics Corporation | Support apparatus, method and system for real time operations and maintenance |
US20040158474A1 (en) | 2003-02-06 | 2004-08-12 | Karschnia Robert J. | Service facility for providing remote diagnostic and maintenance services to a process plant |
US7953842B2 (en) * | 2003-02-19 | 2011-05-31 | Fisher-Rosemount Systems, Inc. | Open network-based data acquisition, aggregation and optimization for use with process control systems |
US7082352B2 (en) * | 2003-02-25 | 2006-07-25 | Paseco Co. Ltd. | Temperature control apparatus for a heater using an encoder switch and method thereof |
GB0307406D0 (en) * | 2003-03-31 | 2003-05-07 | British Telecomm | Data analysis system and method |
EP1484910A1 (en) * | 2003-06-03 | 2004-12-08 | Asulab S.A. | Adaptive redundant analog-to-digital conversion device and method for image sensor |
US7075327B2 (en) * | 2003-06-18 | 2006-07-11 | Eaton Corporation | System and method for proactive motor wellness diagnosis |
US7209860B2 (en) * | 2003-07-07 | 2007-04-24 | Snap-On Incorporated | Distributed expert diagnostic service and system |
US7072797B2 (en) | 2003-08-29 | 2006-07-04 | Honeywell International, Inc. | Trending system and method using monotonic regression |
US7127371B2 (en) * | 2003-10-08 | 2006-10-24 | Ge Medical Systems Information | Customized medical equipment preventative maintenance method and system |
US6955302B2 (en) * | 2003-11-13 | 2005-10-18 | York International Corporation | Remote monitoring diagnostics |
US20050159992A1 (en) * | 2004-01-16 | 2005-07-21 | Lawrence Richard D. | Process for identifying potential customers for business outsourcing |
US7194993B2 (en) | 2004-03-19 | 2007-03-27 | Ford Global Technologies, Llc | Starting an engine with valves that may be deactivated |
WO2005108744A1 (en) | 2004-04-08 | 2005-11-17 | Gas Machinery Research Council | Measuring work performed by a reciprocating machine |
US7676285B2 (en) * | 2004-04-22 | 2010-03-09 | General Electric Company | Method for monitoring driven machinery |
US6973396B1 (en) * | 2004-05-28 | 2005-12-06 | General Electric Company | Method for developing a unified quality assessment and providing an automated fault diagnostic tool for turbine machine systems and the like |
JP4347751B2 (en) * | 2004-06-07 | 2009-10-21 | 株式会社アドバンテスト | Defect analysis system and defect location display method |
US7333906B2 (en) * | 2004-08-11 | 2008-02-19 | Oes, Inc. | Quality analysis including cumulative deviation determination |
EP1820040A4 (en) * | 2004-11-29 | 2009-03-11 | Hydrogenics Corp | Systems and methods for detecting and indicating fault conditions in electrochemical cells |
US7900201B1 (en) * | 2004-12-21 | 2011-03-01 | Zenprise, Inc. | Automated remedying of problems in software application deployments |
US6970124B1 (en) * | 2005-02-11 | 2005-11-29 | Analog Devices, Inc. | Inherent-offset comparator and converter systems |
EP1866819A2 (en) * | 2005-02-25 | 2007-12-19 | Biogen Idec MA Inc. | Process equipment monitoring |
US7581449B2 (en) * | 2005-05-16 | 2009-09-01 | Wrds, Inc. | System and method for power pump performance monitoring and analysis |
US7323992B2 (en) | 2005-06-21 | 2008-01-29 | International Business Machines Corporation | Method and system for aggregation of RFID signal sources and composite to develop a unique signature |
EP1785888A2 (en) * | 2005-11-07 | 2007-05-16 | Mazda Motor Corporation | Internal-combustion engine design support system |
US7596718B2 (en) * | 2006-05-07 | 2009-09-29 | Applied Materials, Inc. | Ranged fault signatures for fault diagnosis |
US8010321B2 (en) * | 2007-05-04 | 2011-08-30 | Applied Materials, Inc. | Metrics independent and recipe independent fault classes |
WO2008157494A2 (en) * | 2007-06-15 | 2008-12-24 | Shell Oil Company | Framework and method for monitoring equipment |
US7747417B2 (en) * | 2007-08-06 | 2010-06-29 | Arizona Public Service Company | Method and system for transformer dissolved gas harmonic regression analysis |
US7765445B2 (en) * | 2008-02-16 | 2010-07-27 | International Business Machines Corporation | Analog testing of ring oscillators using built-in self test apparatus |
US7680627B2 (en) * | 2008-04-01 | 2010-03-16 | Kabushiki Kaisha Toshiba | Plant operation data monitoring apparatus |
-
2008
- 2008-06-16 WO PCT/US2008/067119 patent/WO2008157494A2/en active Application Filing
- 2008-06-16 US US12/664,090 patent/US8688405B2/en active Active
- 2008-06-16 WO PCT/US2008/067125 patent/WO2008157498A1/en active Application Filing
- 2008-06-16 GB GB0921721.7A patent/GB2464002B/en active Active
- 2008-06-16 GB GB0921598.9A patent/GB2462768B/en active Active
- 2008-06-16 GB GB0921200.2A patent/GB2464001B/en active Active
- 2008-06-16 US US12/664,103 patent/US8643471B2/en active Active
- 2008-06-16 CA CA2689237A patent/CA2689237C/en active Active
- 2008-06-16 US US12/664,095 patent/US8510015B2/en active Active
- 2008-06-16 CA CA2689252A patent/CA2689252C/en active Active
- 2008-06-16 CA CA2689238A patent/CA2689238C/en active Active
- 2008-06-16 WO PCT/US2008/067116 patent/WO2008157491A1/en active Application Filing
- 2008-06-16 CA CA2690459A patent/CA2690459C/en not_active Expired - Fee Related
- 2008-06-16 GB GB0920078.3A patent/GB2462394B/en active Active
- 2008-06-16 WO PCT/US2008/067132 patent/WO2008157503A1/en active Application Filing
- 2008-06-16 CA CA2689219A patent/CA2689219C/en active Active
- 2008-06-16 GB GB0920915.6A patent/GB2462047B/en active Active
- 2008-06-16 US US12/664,091 patent/US8749372B2/en active Active
- 2008-06-16 GB GB0921377.8A patent/GB2464846B/en active Active
- 2008-06-16 WO PCT/US2008/067122 patent/WO2008157496A1/en active Application Filing
- 2008-06-16 WO PCT/US2008/067134 patent/WO2008157505A1/en active Application Filing
- 2008-06-16 US US12/664,098 patent/US8612029B2/en active Active
- 2008-06-16 CA CA2689256A patent/CA2689256C/en active Active
-
2014
- 2014-01-07 US US14/149,584 patent/US9035750B2/en active Active
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2689219C (en) | Method and system for state encoding | |
TWI632443B (en) | Apparatus for determining importance of abnormal data and method for determining importance of abnormal data | |
JP6669156B2 (en) | Application automatic control system, application automatic control method and program | |
US10679135B2 (en) | Periodicity analysis on heterogeneous logs | |
CN113157524B (en) | Big data based exception problem solving method, system, equipment and storage medium | |
US20210224383A1 (en) | Abnormality detection device | |
KR20210017637A (en) | Apparatus and method for precise state diagnosis of rotating machinery based on IoT sensor | |
US20230388202A1 (en) | Methods and systems for inferred information propagation for aircraft prognostics | |
CN113934720A (en) | Data cleaning method and equipment and computer storage medium | |
CN105825641A (en) | Service alarm method and apparatus | |
CN116886335A (en) | Data security management system | |
WO2016098805A1 (en) | Data-related information processing device and program | |
CN111309584A (en) | Data processing method and device, electronic equipment and storage medium | |
CN113162904B (en) | Power monitoring system network security alarm evaluation method based on probability graph model | |
JP7437163B2 (en) | Diagnostic equipment, diagnostic methods and programs | |
JP7218765B2 (en) | Time series data processing method | |
US11593245B2 (en) | System, device and method for frozen period detection in sensor datasets | |
CN113938306A (en) | Credible authentication method and system based on data cleaning rule | |
US9054995B2 (en) | Method of detecting measurements in service level agreement based systems | |
CN105827447A (en) | Service alarm method and apparatus | |
JP6998803B2 (en) | Transmitter, receiver, transmit method, receive method, transmit program and receive program | |
WO2022244228A1 (en) | Information processing device, information processing method, and recording medium | |
WO2021131146A1 (en) | Information processing device, information processing method, and information processing program | |
JP2004220373A (en) | Unauthorized access detection log information analysis support system, unauthorized access detection log information analysis support method, and computer program thereof | |
CN117150506A (en) | Vulnerability full life cycle management operation system and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |
Effective date: 20130612 |