WO2017048640A1 - Mesh network routing based on availability of assets - Google Patents
Mesh network routing based on availability of assets Download PDFInfo
- Publication number
- WO2017048640A1 WO2017048640A1 PCT/US2016/051387 US2016051387W WO2017048640A1 WO 2017048640 A1 WO2017048640 A1 WO 2017048640A1 US 2016051387 W US2016051387 W US 2016051387W WO 2017048640 A1 WO2017048640 A1 WO 2017048640A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- asset
- given
- data
- assets
- mesh network
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 49
- 230000004044 response Effects 0.000 claims abstract description 31
- 230000036541 health Effects 0.000 claims description 46
- 238000005259 measurement Methods 0.000 description 55
- 238000012545 processing Methods 0.000 description 46
- 238000004891 communication Methods 0.000 description 42
- 230000001960 triggered effect Effects 0.000 description 20
- 238000013500 data storage Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 14
- 230000002159 abnormal effect Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 13
- 230000003137 locomotive effect Effects 0.000 description 7
- 238000012544 monitoring process Methods 0.000 description 7
- 238000003860 storage Methods 0.000 description 7
- 239000000446 fuel Substances 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 230000011664 signaling Effects 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 230000000704 physical effect Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 230000007423 decrease Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 230000008439 repair process Effects 0.000 description 4
- 238000005070 sampling Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 238000009529 body temperature measurement Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000004083 survival effect Effects 0.000 description 3
- 239000013598 vector Substances 0.000 description 3
- 235000008694 Humulus lupulus Nutrition 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000002354 daily effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 206010000117 Abnormal behaviour Diseases 0.000 description 1
- 241000854291 Dianthus carthusianorum Species 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 238000009412 basement excavation Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000002059 diagnostic imaging Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000005684 electric field Effects 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 239000012530 fluid Substances 0.000 description 1
- 238000007477 logistic regression Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000003801 milling Methods 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 238000012821 model calculation Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000010248 power generation Methods 0.000 description 1
- 238000007637 random forest analysis Methods 0.000 description 1
- 208000024891 symptom Diseases 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
- 230000003442 weekly effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0748—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a remote unit communicating with a single-box computer node experiencing an error/fault
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D3/00—Indicating or recording apparatus with provision for the special purposes referred to in the subgroups
- G01D3/08—Indicating or recording apparatus with provision for the special purposes referred to in the subgroups with provision for safeguarding the apparatus, e.g. against abnormal operation, against breakdown
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M99/00—Subject matter not provided for in other groups of this subclass
- G01M99/005—Testing of complete machines, e.g. washing-machines or mobile phones
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M99/00—Subject matter not provided for in other groups of this subclass
- G01M99/008—Subject matter not provided for in other groups of this subclass by doing functionality tests
-
- 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
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
-
- 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/024—Quantitative history assessment, e.g. mathematical relationships between available data; Functions therefor; Principal component analysis [PCA]; Partial least square [PLS]; Statistical classifiers, e.g. Bayesian networks, linear regression or correlation analysis; Neural networks
-
- 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/0243—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 model based detection method, e.g. first-principles knowledge model
- G05B23/0254—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 model based detection method, e.g. first-principles knowledge model based on a quantitative model, e.g. mathematical relationships between inputs and outputs; functions: observer, Kalman filter, residual calculation, Neural Networks
-
- 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/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0275—Fault isolation and identification, e.g. classify fault; estimate cause or root of failure
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/008—Reliability or availability analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0721—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment within a central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
- G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0772—Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
- G06F11/2007—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication media
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
- G06F11/263—Generation of test inputs, e.g. test vectors, patterns or sequences ; with adaptation of the tested hardware for testability with external testers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/02—Knowledge representation; Symbolic representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/04—Inference or reasoning models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N7/00—Computing arrangements based on specific mathematical models
- G06N7/01—Probabilistic graphical models, e.g. probabilistic networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/067—Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/08—Construction
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
- G07C5/0825—Indicating performance data, e.g. occurrence of a malfunction using optical means
-
- 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
-
- 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
- G08B21/187—Machine fault alarms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/85—Active fault masking without idle spares
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Definitions
- assets are ubiquitous in many industries. From locomotives that transfer cargo across countries to medical equipment that helps nurses and doctors to save lives, assets serve an important role in everyday life. Depending on the role that an asset serves, its complexity, and cost, may vary. For instance, some assets may include multiple subsystems that must operate in harmony for the asset to function properly (e.g., an engine, transmission, etc. of a locomotive).
- the current approach for monitoring assets generally involves an on-asset computer that receives signals from various sensors distributed throughout an asset that monitor the operating conditions of the asset.
- the sensors may monitor parameters such as temperatures, voltages, and speeds, among other examples. If sensor signals from one or more sensors reach certain values, the on-asset computer may then generate an abnormal-condition indicator, such as a "fault code,” which is an indication that an abnormal condition has occurred within the asset.
- an abnormal condition may be a defect at an asset or component thereof, which may lead to a failure of the asset and/or component.
- an abnormal condition may be associated with a given failure, or perhaps multiple failures, in that the abnormal condition is symptomatic of the given failure or failures.
- a user typically defines the sensors and respective sensor values associated with each abnormal-condition indicator. That is, the user defines an asset's "normal” operating conditions (e.g., those that do not trigger fault codes) and "abnormal" operating conditions (e.g., those that trigger fault codes).
- the indicator and/or sensor signals may be passed to a remote location where a user may receive some indication of the abnormal condition and/or sensor signals and decide whether to take action.
- One action that the user might take is to assign a mechanic or the like to evaluate and potentially repair the asset.
- the mechanic may connect a computing device to the asset and operate the computing device to cause the asset to utilize one or more local diagnostic tools to facilitate diagnosing the cause of the generated indicator.
- Assets at a site may be formed into mesh networks for certain purposes.
- a job construction site may include assets that communicate information with each other, such as location data, status data, etc.
- the mesh network may provide a cheap and reliable way to enable communication between the assets.
- Each asset in the mesh network may use a routing configuration to determine one or more paths for data to travel in the mesh network. For example, a first asset may determine whether to transmit data to a second asset or a third asset depending on various factors including a shortest latency, a shortest distance, a minimum travel time, a minimum energy expenditure, etc.
- the routing configuration may include different data structures for storing the one or more paths including a routing table.
- One or more assets in the mesh network may use a communication network to transmit the data outside the mesh network to a remote computing system.
- This asset may be known as a "gateway" because the asset provides the assets in the mesh network with access to additional network resources.
- the assets in the mesh network include sensors that generate sensor data.
- the assets may transmit the sensor data to the remote computing system by accessing the communication network if the assets are gateways or by transmitting the sensor data to the gateway.
- the remote system defines a predictive model and corresponding workflow (referred to herein as a "model-workflow pair") that are related to the operation of the assets.
- the predictive model may be executed either at the remote system itself or can be executed locally by the assets.
- the assets may be configured to receive the model-workflow pair and utilize a local analytics device to operate in accordance with the model-workflow pair.
- a model-workflow pair may cause an asset to monitor certain operating conditions and when certain conditions exist, modify a behavior that may help facilitate preventing an occurrence of a particular event.
- a predictive model may receive as inputs sensor data from a particular set of asset sensors and output a likelihood that a given asset will be unavailable within a given period of time in the future.
- a workflow may involve one or more operations that are performed based on the likelihood of the one or more particular events that is output by the model.
- the remote computing system may define an aggregate, predictive model and corresponding workflows, individualized, predictive models and corresponding workflows, or some combination thereof.
- An “aggregate” model/workflow may refer to a model/workflow that is generic for a group of assets, while an “individualized” model/workflow may refer to a model/workflow that is tailored for a single asset or subgroup of assets from the group of assts.
- one specific model -workflow pair can be a predictive failure model that triggers a workflow for causing the mesh network' s routing table to be updated.
- This model-workflow pair may be executed at the remote computing system (in which case the remote computing system will instruct the assets in the mesh to update their respective routing tables) or may be executed locally at an asset itself (in which case the asset would instruct the other assets in the mesh to update the tables).
- the predictive failure model may take various forms, one example of which is a health score model where the predictive failure model monitors the health of an asset and outputs a health metric (e.g., "health score") for an asset, which is a single, aggregated metric that indicates whether a failure will occur at a given asset (and thus whether the given asset will become unavailable) within a given timeframe into the future.
- a health metric may indicate a likelihood that no failures from a group of failures will occur at an asset within a given timeframe into the future, or a health metric may indicate a likelihood that at least one failure from a group of failures will occur at an asset within a given timeframe into the future.
- the workflow for causing the routing table to be updated may take various forms, one example of which is a workflow triggered when the heath score falls below a certain threshold.
- a routing configuration for at least one other asset in the mesh network is updated.
- the remote computing system may transmit a determination that the given asset is likely to be unavailable within the given period of time in the future to one of the plurality of assets in the mesh network. That asset may then update its routing configuration and transmit the determination to another asset in the mesh network.
- the remote computing system may send to one or more assets in the mesh network a corresponding updated routing configuration.
- a network configuration may include a communication network that facilitates communications between assets and a remote computing system.
- Figure 1 depicts an example network configuration in which example embodiments may be implemented.
- Figure 2 depicts a simplified block diagram of an example asset.
- Figure 3 depicts a conceptual illustration of example abnormal-condition indicators and triggering criteria.
- Figure 4 depicts a conceptual illustration of a mesh network.
- Figure 5 depicts a simplified block diagram of an example analytics system.
- Figure 6 depicts an example flow diagram of a definition phase that may be used for defining model-workflow pairs.
- Figure 7 depicts an example flow diagram of a modeling phase that may be used for defining a predictive model that outputs a health metric.
- Figure 8 depicts an example method to update a routing configuration for a mesh network.
- Figure 1 depicts an example network configuration 100 in which example embodiments may be implemented.
- the network configuration 100 includes at least three assets 102, 103, and 104 coupled in a mesh network 105, a communication network 106, a remote computing system 108 that may take the form of an analytics system, an output system 110, and a data source 112.
- the communication network 106 may communicatively connect each of the components in the network configuration 100.
- the assets 102, 103, and 104 may communicate with the analytics system 108 via the communication network 106.
- the assets 102, 103, and 104 may communicate with each other via the mesh network 105.
- the assets 102, 103, and 104 may also communicate with the analytics system 108 by communicating via the mesh network 105 and via the communication network 106.
- asset 102 may transmit sensor data to asset 103, which transmits the sensor data to the analytics system 108 via the communication network.
- the mesh network 105 may be configured so that a subset of the assets 102, 103, and 104 communicate with the analytics system 108.
- asset 103 may be the only asset that communicates with the analytics system 108 while assets 102, 103, and 104 communicate only with other assets 103 and 104 or 102 and 103, respectively, in the mesh network 105.
- the assets 102, 103, and 104 may communicate with one or more intermediary systems, such as an asset gateway (not pictured), that in turn communicates with the analytics system 108.
- the analytics system 108 may communicate with the output system 110 via the communication network 106.
- the analytics system 108 may communicate with one or more intermediary systems, such as a host server (not pictured), that in turn communicates with the output system 110.
- a host server not pictured
- the assets 102, 103, and 104 may take the form of any device configured to perform one or more operations (which may be defined based on the field) and may also include equipment configured to transmit data indicative of one or more operating conditions of the given asset.
- an asset may include one or more subsystems configured to perform one or more respective operations. In practice, multiple subsystems may operate in parallel or sequentially in order for an asset to operate.
- Example assets may include transportation machines (e.g., locomotives, aircraft, semitrailer trucks, ships, etc.), industrial machines (e.g., mining equipment, construction equipment, processing equipment, assembly equipment, etc.), medical machines (e.g., medical imaging equipment, surgical equipment, medical monitoring systems, medical laboratory equipment, etc.), utility machines (e.g., turbines, solar farms, etc.), and unmanned aerial vehicles, among other examples.
- transportation machines e.g., locomotives, aircraft, semitrailer trucks, ships, etc.
- industrial machines e.g., mining equipment, construction equipment, processing equipment, assembly equipment, etc.
- medical machines e.g., medical imaging equipment, surgical equipment, medical monitoring systems, medical laboratory equipment, etc.
- utility machines e.g., turbines, solar farms, etc.
- unmanned aerial vehicles e.g., unmanned aerial vehicles, among other examples.
- the assets 102, 103, and 104 may each be of the same type (e.g., a fleet of locomotives or aircraft, a group of wind turbines, a pool of milling machines, or a set of magnetic resonance imagining (MRI) machines, among other examples) and perhaps may be of the same class (e.g., same equipment type, brand, and/or model).
- the assets 102, 103, and 104 may differ by type, by brand, by model, etc.
- assets 102, 103, and 104 may be different pieces of equipment at a job site (e.g., an excavation site) or a production facility, among numerous other examples.
- the assets are discussed in further detail below with reference to Figure 2.
- the assets 102, 103, and 104, and perhaps the data source 112 may communicate with the analytics system 108 via the communication network 106 and/or the mesh network 105.
- the communication network 106 may include one or more computing systems and network infrastructure configured to facilitate transferring data between network components.
- the communication network 106 may be or may include one or more Wide- Area Networks (WANs) and/or Local-Area Networks (LANs), which may be wired and/or wireless and may feature varying degrees of bandwidth, power consumption, and/or latency characteristics.
- WANs Wide- Area Networks
- LANs Local-Area Networks
- the communication network 106 may include one or more cellular or satellite networks and/or the Internet, among other networks.
- the communication network 106 may operate according to one or more communication protocols, such as LTE, CDMA, GSM, WiFi, LPWAN, Bluetooth, Ethernet, HTTP/S, TCP, CoAP/DTLS and the like. Although the communication network 106 is shown as a single network, it should be understood that the communication network 106 may include multiple, distinct networks that are themselves communicatively linked. The communication network 106 could take other forms as well.
- the mesh network 105 may take the form of a network topology where the assets 102, 103, and 104 (and potentially other network elements) serve as "nodes" that are configured to facilitate routing data from a source (e.g., the analytics system 108) to a destination (e.g., the asset 103).
- the analytics system 108 may transmit data destined for the asset 103 via the asset 104 that relays the data to the asset 103.
- the asset 103 may transmit data destined for the analytics system 108 via the asset 102 that relays the data to the analytics system 108 via the communication network 106.
- Other examples of data routing are also possible.
- Mesh networks are discussed in further detail below with respect to Figure 4.
- the analytics system 108 may be configured to receive data from the assets
- the analytics system 108 may include one or more computing systems, such as servers and databases, configured to receive, process, analyze, and output data.
- the analytics system 108 may be configured according to a given dataflow technology, such as TPL Dataflow or NiFi, among other examples.
- TPL Dataflow or NiFi
- the analytics system 108 may be configured to transmit data to the assets 102,
- the particular data transmitted may take various forms and will be described in further detail below.
- the output system 110 may take the form of a computing system or device configured to receive data and provide some form of output.
- the output system 110 may take various forms.
- the output system 110 may be or include an output device configured to receive data and provide an audible, visual, and/or tactile output in response to the data.
- an output device may include one or more input interfaces configured to receive user input, and the output device may be configured to transmit data through the communication network 106 based on such user input. Examples of output devices include tablets, smartphones, laptop computers, other mobile computing devices, desktop computers, smart televisions, and the like.
- output system 110 may take the form of a work-order system configured to output a request for a mechanic or the like to repair an asset.
- output system 110 may take the form of a parts-ordering system configured to place an order for a part of an asset and output a receipt thereof. Numerous other output systems are also possible.
- the data source 112 may be configured to communicate with the analytics system 108.
- the data source 112 may be or include one or more computing systems configured to collect, store, and/or provide to other systems, such as the analytics system 108, data that may be relevant to the functions performed by the analytics system 108.
- the data source 112 may be configured to generate and/or obtain data independently from the assets 102, 103, and 104.
- the data provided by the data source 112 may be referred to herein as "external data.”
- the data source 112 may be configured to provide current and/or historical data.
- the analytics system 108 may receive data from the data source 112 by "subscribing" to a service provided by the data source. However, the analytics system 108 may receive data from the data source 112 in other manners as well.
- Examples of the data source 112 include environment data sources, asset-management data sources, and other data sources.
- environment data sources provide data indicating some characteristic of the environment in which assets are operated.
- environment data sources include weather-data servers, global navigation satellite systems (GNSS) servers, map- data servers, and topography-data servers that provide information regarding natural and artificial features of a given area, among other examples.
- GNSS global navigation satellite systems
- asset-management data sources provide data indicating events or statuses of entities (e.g., other assets) that may affect the operation or maintenance of assets (e.g., when and where an asset may operate or receive maintenance).
- asset-management data sources include traffic-data servers that provide information regarding air, water, and/or ground traffic, asset-schedule servers that provide information regarding expected routes and/or locations of assets on particular dates and/or at particular times, defect detector systems (also known as "hotbox" detectors) that provide information regarding one or more operating conditions of an asset that passes in proximity to the defect detector system, part-supplier servers that provide information regarding parts that particular suppliers have in stock and prices thereof, and repair- shop servers that provide information regarding repair shop capacity and the like, among other examples.
- traffic-data servers that provide information regarding air, water, and/or ground traffic
- asset-schedule servers that provide information regarding expected routes and/or locations of assets on particular dates and/or at particular times
- defect detector systems also known as "hotbox" detectors
- part-supplier servers that provide
- Examples of other data sources include power-grid servers that provide information regarding electricity consumption and external databases that store historical operating data for assets, among other examples.
- power-grid servers that provide information regarding electricity consumption and external databases that store historical operating data for assets, among other examples.
- data sources include power-grid servers that provide information regarding electricity consumption and external databases that store historical operating data for assets, among other examples.
- network configuration 100 is one example of a network in which embodiments described herein may be implemented. Numerous other arrangements are possible and contemplated herein. For instance, other network configurations may include additional components not pictured and/or more or less of the pictured components.
- FIG. 2 a simplified block diagram of an example asset 200 is depicted.
- assets 102, 103, and 104 from Figure 1 may be configured like the asset 200.
- the asset 200 may include one or more subsystems 202, one or more sensors 204, one or more actuators 205, a central processing unit 206, data storage 208, a network interface 210, a user interface 212, and perhaps also a local analytics device 220, all of which may be communicatively linked by a system bus, network, or other connection mechanism.
- the asset 200 may include additional components not shown and/or more or less of the depicted components.
- the asset 200 may include one or more electrical, mechanical, and/or electromechanical components configured to perform one or more operations.
- one or more components may be grouped into a given subsystem 202.
- a subsystem 202 may include a group of related components that are part of the asset 200.
- a single subsystem 202 may independently perform one or more operations or the single subsystem 202 may operate along with one or more other subsystems to perform one or more operations.
- different types of assets, and even different classes of the same type of assets, may include different subsystems.
- examples of subsystems 202 may include engines, transmissions, drivetrains, fuel systems, battery systems, exhaust systems, braking systems, electrical systems, signal processing systems, generators, gear boxes, rotors, and hydraulic systems, among numerous other subsystems.
- examples of subsystems 202 may include scanning systems, motors, coil and/or magnet systems, signal processing systems, rotors, and electrical systems, among numerous other subsystems.
- the asset 200 may be outfitted with various sensors 204 that are configured to monitor operating conditions of the asset 200 and various actuators 205 that are configured to interact with the asset 200 or a component thereof and monitor operating conditions of the asset 200.
- some of the sensors 204 and/or actuators 205 may be grouped based on a particular subsystem 202. In this way, the group of sensors 204 and/or actuators 205 may be configured to monitor operating conditions of the particular subsystem 202, and the actuators from that group may be configured to interact with the particular subsystem 202 in some way that may alter the subsystem's behavior based on those operating conditions.
- a sensor 204 may be configured to detect a physical property, which may be indicative of one or more operating conditions of the asset 200, and provide an indication, such as an electrical signal, of the detected physical property.
- the sensors 204 may be configured to obtain measurements continuously, periodically (e.g., based on a sampling frequency), and/or in response to some triggering event.
- the sensors 204 may be preconfigured with operating parameters for performing measurements and/or may perform measurements in accordance with operating parameters provided by the central processing unit 206 (e.g., sampling signals that instruct the sensors 204 to obtain measurements).
- different sensors 204 may have different operating parameters (e.g., some sensors may sample based on a first frequency, while other sensors sample based on a second, different frequency).
- the sensors 204 may be configured to transmit electrical signals indicative of a measured physical property to the central processing unit 206.
- the sensors 204 may continuously or periodically provide such signals to the central processing unit 206.
- sensors 204 may be configured to measure physical properties such as the location and/or movement of the asset 200, in which case the sensors may take the form of GNSS sensors, dead-reckoning-based sensors, accelerometers, gyroscopes, pedometers, magnetometers, or the like.
- various sensors 204 may be configured to measure other operating conditions of the asset 200, examples of which may include temperatures, pressures, speeds, friction, power usages, fuel usages, fluid levels, runtimes, voltages and currents, magnetic fields, electric fields, and power generation, among other examples.
- temperatures, pressures, speeds, friction, power usages, fuel usages, fluid levels, runtimes, voltages and currents, magnetic fields, electric fields, and power generation may include temperatures, pressures, speeds, friction, power usages, fuel usages, fluid levels, runtimes, voltages and currents, magnetic fields, electric fields, and power generation, among other examples.
- sensors may be configured to measure other operating conditions of the asset 200, examples of which may include temperatures, pressures, speeds, friction, power usages, fuel usages, fluid levels, runtimes, voltages and currents, magnetic fields, electric fields, and power generation, among other examples.
- sensors may be configured to measure other operating conditions of the asset 200, examples of which may include temperatures, pressures, speeds, friction, power usages, fuel usage
- an actuator 205 may be configured similar in some respects to a sensor 204. Specifically, an actuator 205 may be configured to detect a physical property indicative of an operating condition of the asset 200 and provide an indication thereof in a manner similar to the sensor 204.
- an actuator 205 may be configured to interact with the asset 200, one or more subsystems 202, and/or some component thereof.
- an actuator 205 may include a motor or the like that is configured to move or otherwise control a component or system.
- an actuator may be configured to measure a fuel flow and alter the fuel flow (e.g., restrict the fuel flow), or an actuator may be configured to measure a hydraulic pressure and alter the hydraulic pressure (e.g., increase or decrease the hydraulic pressure). Numerous other example interactions of an actuator are also possible and contemplated herein.
- the central processing unit 206 may include one or more processors and/or controllers, which may take the form of a general- or special-purpose processor or controller.
- the central processing unit 206 may be or include microprocessors, microcontrollers, application specific integrated circuits, digital signal processors, and the like.
- the data storage 208 may be or include one or more non-transitory computer-readable storage media, such as optical, magnetic, organic, or flash memory, among other examples.
- the central processing unit 206 may be configured to store, access, and execute computer-readable program instructions stored in the data storage 208 to perform the operations of an asset 200 described herein.
- the central processing unit 206 may be configured to receive respective sensor signals from the sensors 204 and/or actuators 205.
- the central processing unit 206 may be configured to store sensor and/or actuator 205 data in and later access it from the data storage 208.
- the central processing unit 206 may also be configured to determine whether received sensor signals trigger any abnormal-condition indicators, such as fault codes.
- the central processing unit 206 may be configured to store in the data storage 208 abnormal-condition rules, each of which include a given abnormal-condition indicator representing a particular abnormal condition and respective sensor criteria that trigger the abnormal-condition indicator.
- each abnormal-condition indicator corresponds with one or more sensor measurement values that must be satisfied before the abnormal-condition indicator is triggered.
- the asset 200 may be pre-programmed with the abnormal-condition rules and/or may receive new abnormal-condition rules or updates to existing rules from a computing system, such as the analytics system 108.
- the central processing unit 206 may be configured to determine whether received sensor signals trigger any abnormal-condition indicators. That is, the central processing unit 206 may determine whether received sensor signals satisfy any sensor criteria. When such a determination is affirmative, the central processing unit 206 may generate abnormal-condition data and may cause the asset's 200 network interface 210 to transmit the abnormal-condition data to the analytics system 108. The central processing unit 206 may generate abnormal-condition data and may also cause the asset's 200 user interface 212 to output an indication of the abnormal condition, such as a visual and/or audible alert. Additionally, the central processing unit 206 may log the occurrence of the abnormal-condition indicator being triggered in the data storage 208, perhaps with a timestamp.
- Figure 3 depicts a conceptual illustration of example abnormal-condition indicators and respective triggering criteria for an asset.
- Figure 3 depicts a conceptual illustration of example fault codes.
- table 300 includes columns 302, 304, and 306 that correspond to Sensor A, Actuator B, and Sensor C, respectively, and rows 308, 310, and 312 that correspond to Fault Codes 1, 2, and 3, respectively.
- Entries 314 then specify sensor criteria (e.g., sensor value thresholds) that correspond to the given fault codes.
- Fault Code 1 will be triggered when Sensor A detects a rotational measurement greater than 135 revolutions per minute (RPM) and Sensor C detects a temperature measurement greater than 65° Celsius (C)
- Fault Code 2 will be triggered when Actuator B detects a voltage measurement greater than 1000 Volts (V) and Sensor C detects a temperature measurement less than 55°C
- Fault Code 3 will be triggered when Sensor A detects a rotational measurement greater than 100 RPM
- Actuator B detects a voltage measurement greater than 750 V
- Sensor C detects a temperature measurement greater than 60°C.
- the central processing unit 206 may be configured to carry out various additional functions for managing and/or controlling operations of the asset 200 as well.
- the central processing unit 206 may be configured to provide instruction signals to the subsystems 202 and/or the sensors 204 that cause the subsystems 202 and/or the sensors 204 to perform some operation, such as modifying a throttle position or a sensor-sampling rate.
- the central processing unit 206 may be configured to receive signals from the subsystems 202, the sensors 204, the network interfaces 210, and/or the user interfaces 212 and based on such signals, cause an operation to occur.
- the central processing unit 206 may be configured to receive signals from a computing device, such as a diagnostic device, that cause the central processing unit 206 to execute one or more diagnostic tools in accordance with diagnostic rules stored in the data storage 208. Other functionalities of the central processing unit 206 are discussed below.
- the central processing unit 206 may be configured to receive a routing configuration or updates to the routing configuration from the analytics system 108 or another asset 200.
- the central processing unit 206 may cause the asset 200 to perform an operation based on the routing configuration or updates to the routing configuration.
- the network interface 210 may be configured to provide for communication between the asset 200 and various other network components.
- the network interface 210 may be configured to facilitate communications to and from the communication network 106 and may thus take the form of an antenna structure and associated equipment for transmitting and receiving various over-the-air signals and/or may take the form of a wired network interface.
- the network interface 210 may also be configured to provide for communication between the asset 200 and various network components operating in the mesh network 105.
- the network interface 210 may be configured to facilitate communications between assets 102, 103, and 104 in the mesh network. Other examples are possible as well.
- the network interface 210 may be configured according to a communication protocol, such as any of those described above.
- the user interface 212 may be configured to facilitate user interaction with the asset 200 and may also be configured to facilitate causing the asset 200 to perform an operation in response to user interaction.
- Examples of user interfaces 212 include touch-sensitive interfaces, mechanical interfaces (e.g., levers, buttons, wheels, dials, keyboards, etc.), and other input interfaces (e.g., microphones), among other examples.
- the user interface 212 may include or provide connectivity to output components, such as display screens, speakers, headphone jacks, and the like.
- the local analytics device 220 may generally be configured to receive and analyze data and based on such analysis, cause one or more operations to occur at the asset 200.
- the local analytics device 220 may receive sensor data from the sensors 204 and based on such data, may provide instructions to the central processing unit 206 that cause the asset 200 to perform an operation.
- the local analytics device 220 may determine that the asset is likely to be unavailable, for example, based on a predictive model and data from the sensors 204.
- the local analytics device 200 may generating a routing configuration for a mesh network (e.g., mesh network 105) and instruct the central processing unit 206 to transmit data based on the routing configuration.
- the local analytics device 200 may instruct the storage 208 to store the routing configuration and/or updates to the routing configuration.
- the local analytics device 220 may enable the asset 200 to locally perform advanced analytics and associated operations, such as executing the predictive model, that may otherwise not be able to be performed with the other on-asset components. As such, the local analytics device 220 may help provide additional processing power and/or intelligence to the asset 200.
- the local analytics device 220 may include a processing unit 222, a data storage 224, and a network interface 226, all of which may be communicatively linked by a system bus, network, or other connection mechanism.
- the processing unit 222 may include one or more processors, which may take any of the processor forms discussed above.
- the data storage 224 may be or include one or more non-transitory computer-readable storage media, which may take any of the forms of computer-readable storage media discussed above.
- the processing unit 222 may be configured to store, access, and execute computer-readable program instructions stored in the data storage 224 to perform the operations of a local analytics device described herein.
- the processing unit 222 may be configured to receive respective sensor signals from the sensors 204 and execute a predictive model -workflow pair based on such signals. Other functions are described below.
- the network interface 226 may be the same or similar to the network interfaces described above. In practice, the network interface 226 may facilitate communication between the asset 200 and the analytics system 108.
- asset 200 shown in Figure 2 is but one example of a simplified representation of an asset and that numerous others are also possible.
- other assets may include additional components not pictured and/or more or less of the pictured components.
- the network configuration 100 may include a mesh network in which assets serve as nodes that cooperate to distribute data.
- a mesh network includes a plurality of nodes that are configured to relay data from a source, perhaps that is located outside of the mesh network, through the mesh network to a destination in accordance with one or more routing protocols.
- the mesh network may be configured such that the nodes communicate with one another, as opposed to communicating directly with a central access point or the like, and may provide multiple possible paths by which data may travel from a source to a destination.
- Nodes may be dynamically added or removed helping to allow for a flexible communication network.
- Nodes may be mobile, in a fixed location, or some combination thereof.
- FIG. 4 depicts a conceptual illustration of an example mesh network 400 that is communicatively coupled to another communication network (e.g., the communication network 106).
- the mesh network 400 includes a plurality of nodes 402, 404, 406, 408, 410, and 412.
- the nodes 404 and 406 are directly reachable by the node 402, while the nodes 408, 410, and 412 are not directly reachable by the node 402.
- the mesh network 400 may be advantageous in that the nodes 404 and 406 extend the transmission range of the node 402, among other advantages.
- the node 402 may be configured to provide the mesh network 400 connectivity to the communication network 106 (e.g., and thus WANs). In this way, the node 402 allows the other nodes of the mesh network 400 to share a single connection back to the communication network 106.
- the node 402 may be communicatively coupled to the communication network 106 via a wired or wireless mechanism or some combination thereof.
- the node 402 may include, take the form of, or otherwise communicate with an access point, such as a wireless router or the like. In some implementations, the node 402 may take the form of an asset, such as the asset 200.
- the nodes 404-412 may take the form of assets, some of which may be all of the same type and/or class or may differ in some respects.
- each of the assets 404-412 serving as nodes may be configured to route data in accordance with one or more routing techniques.
- each asset may include one or more network interfaces that allow the asset to receive and transmit data, such as any of network interfaces discussed above with reference to Figure 2.
- a given asset may be a "legacy" asset that does not itself include a communications interface but may be retrofitted with an external network interface that provides the given asset connectivity to the mesh network 400.
- an asset may be configured to receive but not transmit data.
- the asset 412 may be a data storage device that receives and stores data but does not transmit data to other nodes in the mesh network 400. Other examples are also possible.
- data may propagate through the mesh network 400 in accordance with one or more routing techniques.
- a given routing technique may provide multiple paths by which data from a source can reach a destination via intermediary nodes (i.e., nodes that are not the final destination for the data). And when the data is sent, the path that provides the quickest and/or most reliable route may be utilized.
- a given routing technique may provide two paths between the communication network 106 and the asset 408 (e.g., path 403 and path 405).
- data that originates from the asset 408 may travel to the communication network 106 via the path 403 (e.g., passing through intermediary nodes 404 and 402), while data that originates from the communication network 106 may travel to the asset 408 via the path 405 (e.g., passing through intermediary nodes 402 and 406), among other possibilities.
- path 403 e.g., passing through intermediary nodes 404 and 402
- path 405 e.g., passing through intermediary nodes 402 and 406
- Various routing techniques may be utilized, such as reactive routing techniques (e.g., ad- hoc on demand distance vector routing (AODV), dynamic source routing (DSR), etc.), proactive routing techniques (e.g., optimized link state routing (OLSR), better approach to mobile ad-hoc networking (BATMAN), destination sequenced distance- vector routing (DSDV), cluster head gateway switch routing (CGSR), etc.), and/or hybrid routing techniques (e.g., some combination of reactive and proactive routing techniques), among other routing techniques.
- reactive routing techniques e.g., ad- hoc on demand distance vector routing (AODV), dynamic source routing (DSR), etc.
- proactive routing techniques e.g., optimized link state routing (OLSR), better approach to mobile ad-hoc networking (BATMAN), destination sequenced distance- vector routing (DSDV), cluster head gateway switch routing (CGSR), etc.
- hybrid routing techniques e.g., some combination of reactive and proactive routing techniques
- the paths by which data may propagate through the mesh network 400 may be determined in a variety of manners. Generally, the paths are determined by each node of the mesh network 400 exchanging, perhaps periodically, respective routing information (e.g., distance vectors, node metrics, etc.) with the other nodes to establish the possible routes from each node to the other in the mesh network 400. More specifically, the mesh network 400 may be established and paths may be determined based on the routing information of the nodes 402-412.
- respective routing information e.g., distance vectors, node metrics, etc.
- the routing information of a given node may include or be based on various node metrics, such as a current load on the given node, radio frequency noise level, GPS coordinates of the given node, received signal strength indicator, signal-to-noise ratio, compass angle, remaining battery power of the given node, and/or remaining energy of the given node (e.g., an indication of the given node's data throughput and/or a number of hops), among other considerations.
- various node metrics such as a current load on the given node, radio frequency noise level, GPS coordinates of the given node, received signal strength indicator, signal-to-noise ratio, compass angle, remaining battery power of the given node, and/or remaining energy of the given node (e.g., an indication of the given node's data throughput and/or a number of hops), among other considerations.
- Each node may then store some or all of the routing information of the other nodes, such as in the form of a routing table, in accordance with a given routing technique.
- a given routing technique may cause the nodes to determine one or more "optimal" paths to distribute data based on the routing information. For instance, the nodes may optimize for the quickest data delivery (e.g., fewest number of hops, shortest overall distance, and/or shortest travel time), the most reliable data delivery, or the path that optimizes both quickness and reliability, among other examples.
- the nodes may configure their respective routing tables to reflect the optimized data delivery such that, when a given node receives data that is destined for a particular node, the given node can readily determine the node to which it should relay the data (e.g., the "next hop") to facilitate delivering the data in accordance with the given routing technique.
- the mesh network 400 may be dynamically updated as network conditions and/or node metrics change. For example, as network conditions change (e.g., as network latency increases or decreases), the nodes may determine that a given path is less optimal than another path and update their respective routing tables to reflect that a different path is now the most optimal path. In another example, as a given node's ability to server as router changes (e.g., as the given asset's health decreases, discussed in further detail below), the nodes may determine that a given path (e.g., one in which the given node is a link in the path) is less optimal than another path and update their respective route tables accordingly. Other examples of updating routing information are also possible.
- the analytics system 500 may include one or more computing systems communicatively linked and arranged to carry out various operations described herein.
- the analytics system 500 may include a data intake system 502, a data science system 504, and one or more databases 506. These system components may be communicatively coupled via one or more wireless and/or wired connections.
- the data intake system 502 may generally function to receive and process data and output data to the data science system 504.
- the data intake system 502 may include one or more network interfaces configured to receive data from various network components of the network configuration 100, such as the assets 102, 103, and 104, the output system 110, and/or the data source 112.
- the data intake system 502 may be configured to receive analog signals, data streams, and/or network packets, among other examples.
- the network interfaces may include one or more wired network interfaces, such as a port or the like, and/or wireless network interfaces, similar to those described above.
- the data intake system 402 may be or include components configured according to a given dataflow technology, such as a NiFi receiver or the like.
- the data intake system 502 may include one or more processing components configured to perform one or more operations.
- Example operations may include compression and/or decompression, encryption and/or de-encryption, analog-to-digital and/or digital-to-analog conversion, filtration, and amplification, among other operations.
- the data intake system 502 may be configured to parse, sort, organize, and/or route data based on data type and/or characteristics of the data.
- the data intake system 502 may be configured to format, package, and/or route data based on one or more characteristics or operating parameters of the data science system 504.
- the data received by the data intake system 502 may take various forms.
- the payload of the data may include a single sensor measurement, multiple sensor measurements and/or one or more fault codes. Other examples are also possible.
- the received data may include certain characteristics, such as a source identifier and a timestamp (e.g., a date and/or time at which the information was obtained). For instance, a unique identifier (e.g., a computer generated alphabetic, numeric, alphanumeric, or the like identifier) may be assigned to each asset, and perhaps to each sensor. Such identifiers may be operable to identify the asset, or sensor, from which data originates. In some cases, another characteristic may include the location (e.g., GPS coordinates) at which the information was obtained. Data characteristics may come in the form of signal signatures or metadata, among other examples.
- a source identifier e.g., a computer generated alphabetic, numeric, alphanumeric, or the like identifier
- a timestamp e.g., a date and/or time at which the information was obtained.
- a unique identifier e.g., a computer generated alphabetic, numeric, alphanumeric, or the like
- the data science system 504 may generally function to receive (e.g., from the data intake system 502) and analyze data and based on such analysis, cause one or more operations to occur.
- the data science system 504 may include one or more network interfaces 508, a processing unit 510, and data storage 512, all of which may be communicatively linked by a system bus, network, or other connection mechanism.
- the data science system 404 may be configured to store and/or access one or more application program interfaces (APIs) that facilitate carrying out some of the functionality disclosed herein.
- APIs application program interfaces
- the network interfaces 508 may be the same or similar to any network interface described above. In practice, the network interfaces 508 may facilitate communication between the data science system 504 and various other entities, such as the data intake system 502, the databases 506, the assets 102, 103, 104, the output system 110, etc.
- the processing unit 510 may include one or more processors, which may take any of the processor forms described above.
- the data storage 512 may be or include one or more non-transitory computer-readable storage media, which may take any of the forms of computer-readable storage media discussed above.
- the processing unit 510 may be configured to store, access, and execute computer-readable program instructions stored in the data storage 512 to perform the operations of an analytics system described herein.
- the processing unit 510 may be configured to perform analytics on data received from the data intake system 502.
- the processing unit 510 may be configured to execute one or more modules, which may each take the form of one or more sets of program instructions that are stored in the data storage 512.
- the modules may be configured to facilitate causing an outcome to occur based on the execution of the respective program instructions.
- An example outcome from a given module may include outputting data into another module, updating the program instructions of the given module and/or of another module, and outputting data to a network interface 508 for transmission to an asset and/or the output system 110, among other examples.
- the databases 506 may generally function to receive (e.g., from the data science system 504) and store data.
- each database 506 may include one or more non-transitory computer-readable storage media, such as any of the examples provided above.
- the databases 506 may be separate from or integrated with the data storage 512.
- the databases 506 may be configured to store numerous types of data, some of which is discussed below. In practice, some of the data stored in the databases 506 may include a timestamp indicating a date and time at which the data was generated or added to the database. Moreover, data may be stored in a number of manners in the databases 506. For instance, data may be stored in time sequence, in a tabular manner, and/or organized based on data source type (e.g., based on asset, asset type, sensor, or sensor type) or fault code, among other examples.
- data source type e.g., based on asset, asset type, sensor, or sensor type
- each block may represent a module or portion of program code that includes instructions that are executable by a processor to implement specific logical functions or steps in a process.
- the program code may be stored on any type of computer-readable medium, such as non-transitory computer-readable media.
- each block may represent circuitry that is wired to perform specific logical functions or steps in a process.
- the blocks shown in the flow diagrams may be rearranged into different orders, combined into fewer blocks, separated into additional blocks, and/or removed based upon the particular embodiment.
- the following description may reference examples where a single data source, such as an asset 102, provides data to the analytics system 108 that then performs one or more functions. It should be understood that this is done merely for sake of clarity and explanation and is not meant to be limiting. In practice, the analytics system 108 may receive data from multiple sources, such as assets 102, 103, and 104, perhaps simultaneously, and perform operations based on such aggregate received data.
- some or all of the assets 102, 103, and 104 may exchange setup messages to establish the mesh network 105 over which the assets and the analytics system 108 may transfer data.
- the mesh network 105 may be established between the assets 102-104 in line with the above discussion with reference to Figure 4.
- the assets 102-104 may generate routing topologies (e.g., routing tables that reflect paths to transfer data) to facilitate optimizing the mesh network 105 according to desired optimization factors.
- the routing topologies may indicate paths that are optimized for fewest number of assets (nodes) that relay data (e.g., hop minimization), shortest data delivery time (e.g., latency minimization), lowest energy expenditure (e.g., energy minimization), least amount of redundancy, some combination thereof, or any of the other examples provided above, among other examples.
- the assets 102- 104 may exchange routing information with one another and/or the analytics system 108. As network conditions and/or asset (node) metrics change, the routing topologies may be updated in accordance with the desired optimization factors.
- the representative asset 102 may take various forms and may be configured to perform a number of operations.
- the asset 102 may take the form of a locomotive that is operable to transfer cargo across the United States.
- the sensors of the asset 102 may obtain sensor data that reflects one or more operating conditions of the asset 102.
- the sensors may transmit the sensor data to a processing unit of the asset 102.
- the processing unit may be configured to receive sensor data from the sensors.
- the processing unit may receive sensor data from multiple sensors simultaneously or sequentially.
- the processing unit may also be configured to determine whether sensor data satisfies sensor criteria that trigger any abnormal-condition indicators, such as fault codes.
- the processing unit may be configured to perform one or more local operations, such as outputting an indication of the triggered indicator via a user interface.
- the asset 102 may then transmit operating data to the analytics system 108 via a network interface of the asset 102 and the communication network 106.
- the asset 102 may transmit operating data to the analytics system 108 continuously, periodically, and/or in response to triggering events (e.g., abnormal conditions).
- the asset 102 may transmit operating data periodically based on a particular frequency (e.g., daily, hourly, every fifteen minutes, once per minute, once per second, etc.), or the asset 102 may be configured to transmit a continuous, real-time feed of operating data.
- the asset 102 may be configured to transmit operating data based on certain triggers, such as when sensor measurements from its sensors satisfy sensor criteria for any abnormal-condition indicators.
- the asset 102 may transmit operating data in other manners as well.
- operating data for the asset 102 may include sensor data and/or abnormal- condition data.
- the asset 102 may be configured to provide the operating data in a single data stream, while in other implementations the asset 102 may be configured to provide the operating data in multiple, distinct data streams.
- the asset 102 may provide to the analytics system 108 a first data stream of sensor data and a second data stream of abnormal-condition data.
- Sensor data may take various forms. For example, at times, sensor data may include measurements obtained by each of the sensors of the asset 102. While at other times, sensor data may include measurements obtained by a subset of the sensors of the asset 102.
- the sensor data may include measurements obtained by the sensors associated with a given triggered abnormal-condition indicator.
- a triggered fault code is Fault Code 1 from Figure 3
- the sensor data may include raw measurements obtained by Sensors A and C.
- the sensor data may include measurements obtained by one or more sensors not directly associated with the triggered fault code.
- the sensor data may additionally include measurements obtained by Sensor B and/or other sensors.
- the asset 102 may include particular sensor data in the operating data based on a fault-code rule or instruction provided by the analytics system 108, which may have, for example, determined that there is a correlation between that which Sensor B is measuring and that which caused the Fault Code 1 to be triggered in the first place. Other examples are also possible.
- the sensor data may include one or more sensor measurements from each sensor of interest based on a particular time of interest, which may be selected based on a number of factors.
- the particular time of interest may be based on a sampling rate.
- the particular time of interest may be based on the time at which an abnormal- condition indicator is triggered.
- the sensor data may include one or more respective sensor measurements from each sensor of interest (e.g., sensors directly and indirectly associated with the triggered indicator).
- the one or more sensor measurements may be based on a particular number of measurements or particular duration of time around the time of the triggered abnormal-condition indicator.
- a triggered fault code is Fault Code 2 from Figure 3
- the sensors of interest might include Sensors B and C.
- the one or more sensor measurements may include the most recent respective measurements obtained by Sensors B and C prior to the triggering of the fault code (e.g., triggering measurements) or a respective set of measurements before, after, or about the triggering measurements.
- a set of five measurements may include the five measurements before or after the triggering measurement (e.g., excluding the triggering measurement), the four measurements before or after the triggering measurement and the triggering measurement, or the two measurements before and the two after as well as the triggering measurement, among other possibilities.
- the abnormal-condition data may take various forms.
- the abnormal-condition data may include or take the form of an indicator that is operable to uniquely identify a particular abnormal condition that occurred at the asset 102 from all other abnormal conditions that may occur at the asset 102.
- the abnormal-condition indicator may take the form of an alphabetic, numeric, or alphanumeric identifier, among other examples.
- the abnormal-condition indicator may take the form of a string of words that is descriptive of the abnormal condition, such as "Overheated Engine” or "Out of Fuel", among other examples.
- the analytics system 108 and in particular, the data intake system of the analytics system 108, may be configured to receive operating data from one or more assets and/or data sources.
- the data intake system may be configured to perform one or more operations to the received data and then relay the data to the data science system of the analytics system 108.
- the data science system may analyze the received data and based on such analysis, perform one or more operations.
- the analytics system 108 may be configured to define predictive models and corresponding workflows based on received operating data for one or more assets and/or received external data related to the one or more assets.
- the analytics system 108 may define model -workflow pairs based on various other data as well.
- a model-workflow pair may include a set of program instructions that cause an asset to monitor certain operating conditions and carry out certain operations that help facilitate preventing the occurrence of a particular event suggested by the monitored operating conditions.
- a predictive model may include one or more algorithms whose inputs are sensor data from one or more sensors of an asset and whose outputs are utilized to determine a probability that a particular event may occur at the asset within a particular period of time in the future.
- a workflow may include one or more triggers (e.g., model output values) and corresponding operations that the asset carries out based on the triggers.
- the analytics system 108 may be configured to define aggregate and/or individualized predictive models and/or workflows.
- An "aggregate" model/workflow may refer to a model/workflow that is generic for a group of assets and defined without taking into consideration particular characteristics of the assets to which the model/workflow is deployed.
- an "individualized” model/workflow may refer to a model/workflow that is specifically tailored for a single asset or a subgroup of assets from the group of assets and defined based on particular characteristics of the single asset or subgroup of assets to which the model/workflow is deployed.
- a model-workflow pair may take the form of a model for predicting that a given asset is likely to be unavailable within a given period of time in the future and a corresponding workflow for causing a routing table to be updated based on this predictive model.
- This model-workflow pair may take various forms.
- the analytics system 108 may be configured to define a model for predicting that a given asset is likely to be unavailable within a given period of time in the future (i.e., an "unavailability model"). The analytics system 108 may carry out this step in various manners.
- FIG. 6 is a flow diagram 600 depicting one possible example of a definition phase that may be used for defining the unavailability model.
- the example definition phase is described as being carried out by the analytics system 108, but this definition phase may be carried out by other systems as well.
- the flow diagram 600 is provided for sake of clarity and explanation and that numerous other combinations of operations may be utilized to define a model-workflow pair.
- the analytics system 108 may begin by defining a set of data that forms the basis for a given unavailability model (e.g., the data of interest).
- the data of interest may derive from a number of sources, such as the assets 102, 103, and 104 and the data source 112, and may be stored in a database of the analytics system 108.
- the data of interest may include historical data for a particular set of assets from a group of assets or all of the assets from a group of assets (e.g., the assets of interest). Moreover, the data of interest may include measurements from a particular set of sensors and/or actuators from each of the assets of interest or from all of the sensors and/or actuators from each of the assets of interest. Further still, the data of interest may include data from a particular period of time in the past, such as two weeks' worth of historical data.
- the data of interest may include a variety of types data, which may depend on the given unavailability model.
- the data of interest may include at least operating data indicating operating conditions of assets, where the operating data is as discussed above in the Collection of Operating Data section.
- the data of interest may include environment data indicating environments in which assets are typically operated and/or scheduling data indicating planned dates and times during which assets are to carry out certain tasks. Other types of data may also be included in the data of interest.
- the data of interest may be defined in a number of manners.
- the data of interest may be user-defined.
- a user may operate an output system 110 that receives user inputs indicating a selection of certain data of interest, and the output system 110 may provide to the analytics system 108 data indicating such selections. Based on the received data, the analytics system 108 may then define the data of interest.
- the data of interest may be machine-defined.
- the analytics system 108 may perform various operations, such as simulations, to determine the data of interest that generates the most accurate predictive model. Other examples are also possible.
- the analytics system 108 may be configured to, based on the data of interest, define an aggregate, predictive model that represents a relationship between operating conditions of an asset and a likelihood of the asset becoming unavailable within a given period of time in the future.
- an aggregate, predictive model may receive as inputs sensor data from sensors of an asset and/or actuator data from actuators of the asset and may output a probability that the asset will become unavailable within a given period of time in the future.
- defining the aggregate, predictive model may involve utilizing one or more modeling techniques to generate a model that returns a probability between zero and one, such as a random forest technique, logistic regression technique, or other regression technique, among other modeling techniques.
- modeling techniques such as a random forest technique, logistic regression technique, or other regression technique, among other modeling techniques.
- other techniques are possible as well.
- the unavailability model may take the form of a predictive model that monitors the health of an asset and outputs a health metric (e.g., "health score") for an asset, which is a single, aggregated metric that indicates whether a failure will occur at a given asset (and thus whether the given asset will become unavailable) within a given timeframe into the future.
- a health metric may indicate a likelihood that no failures from a group of failures will occur at an asset within a given timeframe into the future, or a health metric may indicate a likelihood that at least one failure from a group of failures will occur at an asset within a given timeframe into the future.
- the analytics system 108 may be configured to define different predictive models that output different levels of health metrics, each of which may be used as the unavailability model.
- the analytics system 108 may define a predictive model that outputs a health metric for the asset as a whole (i.e., an asset- level health metric).
- the analytics system 108 may define a respective predictive model that outputs a respective health metric for one or more subsystems of the asset (i.e., subsystem-level health metrics).
- the outputs of each subsystem-level predictive model may be combined to generate an asset-level health metric.
- Other examples are also possible.
- FIG. 7 is a flow diagram 700 depicting one possible example of a modeling phase that may be used for defining a model that outputs a health metric.
- the example modeling phase is described as being carried out by the analytics system 108, but this modeling phase may be carried out by other systems as well.
- the flow diagram 700 is provided for sake of clarity and explanation and that numerous other combinations of operations may be utilized to determine a health metric.
- the analytics system 108 may begin by defining a set of the one or more failures that form the basis for the health metric (i.e., the failures of interest).
- the one or more failures may be those failures that could render an asset (or a subsystem thereof) inoperable if they were to occur.
- the analytics system 108 may take steps to define a model for predicting a likelihood of any of the failures occurring within a given timeframe in the future (e.g., the next two weeks).
- the analytics system 108 may analyze historical operating data for a group of one or more assets to identify past occurrences of a given failure from the set of failures.
- the analytics system 108 may identify a respective set of operating data that is associated with each identified past occurrence of the given failure (e.g., sensor and/or actuator data from a given timeframe prior to the occurrence of the given failure).
- the analytics system 108 may analyze the identified sets of operating data associated with past occurrences of the given failure to define a relationship (e.g., a failure model) between (1) the values for a given set of operating metrics and (2) the likelihood of the given failure occurring within a given timeframe in the future (e.g., the next two weeks).
- the defined relationship for each failure in the defined set (e.g., the individual failure models) may then be combined into a model for predicting the overall likelihood of a failure occurring.
- the analytics system 108 may also continue to refine the predictive model for the defined set of one or more failures by repeating steps 704-710 on the updated operating data.
- the analytics system 108 may begin by defining a set of the one or more failures that form the basis for the health metric.
- the analytics system 108 may perform this function in various manners.
- the set of the one or more failures may be based on one or more user inputs.
- the analytics system 108 may receive from a computing system operated by a user, such as the output system 110, input data indicating a user selection of the one or more failures.
- the set of one or more failures may be user-defined.
- the set of the one or more failures may be based on a determination made by the analytics system 108 (e.g., machine-defined).
- the analytics system 108 may be configured to define the set of one or more failures, which may occur in a number of manners.
- the analytics system 108 may be configured to define the set of failures based on one or more characteristics of the asset 102. That is, certain failures may correspond to certain characteristics, such as asset type, class, etc., of an asset. For example, each type and/or class of asset may have respective failures of interest.
- the analytics system 108 may be configured to define the set of failures based on historical data stored in the databases of the analytics system 108 and/or external data provided by the data source 112. For example, the analytics system 108 may utilize such data to determine which failures result in the longest repair-time and/or which failures are historically followed by additional failures, among other examples.
- the set of one or more failures may be defined based on a combination of user inputs and determinations made by the analytics system 108. Other examples are also possible.
- the analytics system 108 may analyze historical operating data for a group of one or more assets (e.g., abnormal -behavior data) to identify past occurrences of a given failure.
- the group of the one or more assets may include a single asset, such as asset 102, or multiple assets of a same or similar type, such as fleet of assets that includes the assets 102, 103, and 104.
- the analytics system 108 may analyze a particular amount of historical operating data, such as a certain amount of time's worth of data (e.g., a month's worth) or a certain number of data-points (e.g., the most recent thousand data-points), among other examples.
- identifying past occurrences of the given failure may involve the analytics system 108 identifying the type of operating data, such as abnormal-condition data, that indicates the given failure.
- a given failure may be associated with one or multiple abnormal- condition indicators, such as fault codes. That is, when the given failure occurs, one or multiple abnormal-condition indicators may be triggered. As such, abnormal-condition indicators may be reflective of an underlying symptom of a given failure.
- the analytics system 108 may identify the past occurrences of the given failure in a number of manners. For instance, the analytics system 108 may locate, from historical operating data stored in the databases of the analytics system 108, abnormal-condition data corresponding to the abnormal-condition indicators associated with the given failure. Each located abnormal-condition data would indicate an occurrence of the given failure. Based on this located abnormal-condition data, the analytics system 108 may identify a time at which a past failure occurred.
- the analytics system 108 may identify a respective set of operating data that is associated with each identified past occurrence of the given failure.
- the analytics system 108 may identify a set of sensor and/or actuator data from a certain timeframe around the time of the given occurrence of the given failure.
- the set of data may be from a particular timeframe (e.g., two weeks) before, after, or around the given occurrence of the failure.
- the set of data may be identified from a certain number of data-points before, after, or around the given occurrence of the failure.
- the set of operating data may include sensor and/or actuator data from some or all of the sensors and actuators of the asset 102.
- the set of operating data may include data from sensors and/or actuators associated with an abnormal- condition indicator corresponding to the given failure.
- the analytics system 108 may determine whether there are any remaining occurrences for which a set of operating data should be identified. In the event that there is a remaining occurrence, block 706 would be repeated for each remaining occurrence.
- the analytics system 108 may analyze the identified sets of operating data associated with the past occurrences of the given failure to define a relationship (e.g., a failure model) between (1) a given set of operating metrics (e.g., a given set of sensor and/or actuator measurements) and (2) the likelihood of the given failure occurring within a given timeframe in the future (e.g., the next two weeks). That is, a given failure model may take as inputs sensor and/or actuator measurements from one or more sensors and/or actuators and output a probability that the given failure will occur within the given timeframe in the future. [138] In general, a failure model may define a relationship between operating conditions of the asset 102 and the likelihood of a failure occurring.
- a failure model may define a relationship between operating conditions of the asset 102 and the likelihood of a failure occurring.
- a failure model may receive a number of other data inputs, also known as features, which are derived from the sensor and/or actuator signals.
- features may include an average or range of values that were historically measured when a failure occurred, an average or range of value gradients (e.g., a rate of change in measurements) that were historically measured prior to an occurrence of a failure, a duration of time between failures (e.g., an amount of time or number of data-points between a first occurrence of a failure and a second occurrence of a failure), and/or one or more failure patterns indicating sensor and/or actuator measurement trends around the occurrence of a failure.
- features may include an average or range of values that were historically measured when a failure occurred, an average or range of value gradients (e.g., a rate of change in measurements) that were historically measured prior to an occurrence of a failure, a duration of time between failures (e.g., an amount of time or number of data-points between a first occurrence of a failure
- a failure model may be defined in a number of manners.
- the analytics system 108 may define a failure model by utilizing one or more modeling techniques that return a probability between zero and one, which may take the form of any modeling techniques described above.
- defining a failure model may involve the analytics system 108 generating a response variable based on the historical operating data identified at block 706. Specifically, the analytics system 108 may determine an associated response variable for each set of sensor and/or actuator measurements received at a particular point in time. As such, the response variable may take the form of a data set associated with the failure model.
- the response variable may indicate whether the given set of measurements is within any of the timeframes determined at block 706. That is, a response variable may reflect whether a given set of data is from a time of interest about the occurrence of a failure.
- the response variable may be a binary -valued response variable such that, if the given set of measurements is within any of determined timeframes, the associated response variable is assigned a value of one, and otherwise, the associated response variable is assigned a value of zero.
- the analytics system 108 may train the failure model with the historical operating data identified at block 706 and the generated response variable. Based on this training process, the analytics system 108 may then define the failure model that receives as inputs various sensor and/or actuator data and outputs a probability between zero and one that a failure will occur within a period of time equivalent to the timeframe used to generate the response variable. [143] In some cases, training with the historical operating data identified at block 706 and the generated response variable may result in variable importance statistics for each sensor and/or actuator. A given variable importance statistic may indicate the sensor's or actuator's relative effect on the probability that a given failure will occur within the period of time into the future.
- the analytics system 108 may be configured to define a failure model based on one or more survival analysis techniques, such as a Cox proportional hazard technique.
- the analytics system 108 may utilize a survival analysis technique in a manner similar in some respects to the above-discussed modeling technique, but the analytics system 108 may determine a survival time-response variable that indicates an amount of time from the last failure to a next expected event.
- a next expected event may be either reception of senor and/or actuator measurements or an occurrence of a failure, whichever occurs first.
- This response variable may include a pair of values that are associated with each of the particular points in time at which measurements are received. The response variable may then be utilized to determine a probability that a failure will occur within the given timeframe in the future.
- the failure model may be defined based in part on external data, such as weather data, and "hotbox" data, among other data. For instance, based on such data, the failure model may increase or decrease an output failure probability.
- external data may be observed at points in time that do not coincide with times at which asset sensors and/or actuators obtain measurements.
- the times at which "hotbox" data is collected e.g., times at which a locomotive passes along a section of railroad track that is outfitted with hot box sensors
- the analytics system 108 may be configured to perform one or more operations to determine external data observations that would have been observed at times that correspond to the sensor measurement times.
- the analytics system 108 may utilize the times of the external data observations and times of the measurements to interpolate the external data observations to produce external data values for times corresponding to the measurement times. Interpolation of the external data may allow external data observations or features derived therefrom to be included as inputs into the failure model. In practice, various techniques may be used to interpolate the external data with the sensor and/or actuator data, such as nearest-neighbor interpolation, linear interpolation, polynomial interpolation, and spline interpolation, among other examples.
- the analytics system 108 may determine whether there are any remaining failures for which a failure model should be determined. In the event that there remains a failure for which a failure model should be determined, the analytics system 108 may repeat the loop of blocks 704-708. In some implementations, the analytics system 108 may determine a single failure model that encompasses all of the failures defined at block 702. In other implementations, the analytics system 108 may determine a failure model for each subsystem of the asset 102, which may then be utilized to determine an asset-level failure model. Other examples are also possible.
- the defined relationship for each failure in the defined set may then be combined into the model (e.g., the health-metric model) for predicting the overall likelihood of a failure occurring within the given timeframe in the future (e.g., the next two weeks). That is, the model receives as inputs sensor and/or actuator measurements from one or more sensors and/or actuators and outputs a single probability that at least one failure from the set of failures will occur within the given timeframe in the future.
- the analytics system 108 may define the health-metric model in a number of manners, which may depend on the desired granularity of the health metric. That is, in instances where there are multiple failure models, the outcomes of the failure models may be utilized in a number of manners to obtain the output of the health-metric model. For example, the analytics system 108 may determine a maximum, median, or average from the multiple failure models and utilize that determined value as the output of the health-metric model.
- determining the health-metric model may involve the analytics system 108 attributing a weight to individual probabilities output by the individual failure models. For instance, each failure from the set of failures may be considered equally undesirable, and so each probability may likewise be weighted the same in determining the health-metric model. In other instances, some failures may be considered more undesirable than others (e.g., more catastrophic or require longer repair time, etc.), and so those corresponding probabilities may be weighted more than others.
- determining the health-metric model may involve the analytics system 108 utilizing one or more modeling techniques, such as a regression technique.
- An aggregate response variable may take the form of the logical disjunction (logical OR) of the response variables from each of the individual failure models. For example, aggregate response variables associated with any set of measurements that occur within any timeframe determined at block 706 may have a value of one, while aggregate response variables associated with sets of measurements that occur outside any of the timeframes may have a value of zero.
- Other manners of defining the health-metric model are also possible.
- block 710 may be unnecessary.
- the analytics system 108 may determine a single failure model, in which case the health- metric model may be the single failure model.
- the analytics system 108 may be configured to update the individual failure models and/or the overall health-metric model.
- the analytics system 108 may update a model daily, weekly, monthly, etc. and may do so based on a new portion of historical operating data from the asset 102 or from other assets (e.g., from other assets in the same fleet as the asset 102). Other examples are also possible.
- the unavailability model may take various other forms as well.
- the unavailability model may predict an asset's ability of the asset to communicate in a mesh network (e.g., based on the asset's operating data).
- the unavailability model may predict whether the asset is going off-line (e.g., based on time of day, battery life, scheduled maintenance, or the like).
- the analytics system 108 may also be configured to define individualized predictive models for assets, which may involve utilizing the aggregate, predictive model as a baseline. The individualization may be based on certain characteristics of assets. In this way, the analytics system 108 may provide a given asset a more accurate and robust predictive model compared to the aggregate predictive model.
- the analytics system 108 may be configured to decide whether to individualize the aggregate model defined at block 604 for a given asset, such as the asset 102.
- the analytics system 108 may carry out this decision in a number of manners.
- the analytics system 108 may be configured to define individualized predictive models by default. In other cases, the analytics system 108 may be configured to decide whether to define an individualized predictive model based on certain characteristics of the asset 102. For example, in some cases, only assets of certain types or classes, or operated in certain environments, or that have certain health scores may receive an individualized predictive model. In yet other cases, a user may define whether an individualized model is defined for the asset 102. Other examples are also possible.
- the analytics system 108 may do so at block 608. Otherwise, the analytics system 108 may end the definition phase. [160] At block 608 the analytics system 108 may be configured to define an individualized predictive model in a number of manners. In example implementations, the analytics system 108 may define an individualized predictive model based at least in part on one or more characteristics of the asset 102.
- the analytics system 108 may have determined one or more asset characteristics of interest that form the basis of individualized models. In practice, different predictive models may have different corresponding characteristics of interest.
- the characteristics of interest may be characteristics that are related to the aggregate, predictive model.
- the characteristics of interest may be characteristics that the analytics system 108 has determined influence the accuracy of the aggregate, predictive model. Examples of such characteristics may include asset age, asset usage, asset capacity, asset load, asset health (perhaps indicated by an asset health metric, discussed below), asset class (e.g., brand and/or model), and environment in which an asset is operated, among other characteristics.
- the analytics system 108 may have determined the characteristics of interest in a number of manners. In one example, the analytics system 108 may have done so by performing one or more modeling simulations that facilitate identifying the characteristics of interest. In another example, the characteristics of interest may have been predefined and stored in the data storage of the analytics system 108. In yet another example, characteristics of interest may have been defined by a user and provided to the analytics system 108 via the output system 110. Other examples are also possible.
- the analytics system 108 may determine characteristics of the asset 102 that correspond to the determined characteristics of interest. That is, the analytics system 108 may determine a type, value, existence or lack thereof, etc. of the asset 102's characteristics that correspond to the characteristics of interest. The analytics system 108 may perform this operation in a number of manners.
- the analytics system 108 may be configured to perform this operation based on data originating from the asset 102 and/or the data source 112.
- the analytics system 108 may utilize operating data for the asset 102 and/or external data from the data source 112 to determine one or more characteristics of the asset 102.
- Other examples are also possible.
- the analytics system 108 may define an individualized, predictive model by modifying the aggregate model.
- the aggregate model may be modified in a number of manners.
- the aggregate model may be modified by changing (e.g., adding, removing, re-ordering, etc.) one or more model inputs, changing one or more sensor and/or actuator measurement ranges that correspond to asset- operating limits (e.g., changing operating limits that correspond to "leading indicator" events), changing one or more model calculations, weighting (or changing a weight of) a variable or output of a calculation, utilizing a modeling technique that differs from that which was utilized to define the aggregate model, and/or utilizing a response variable that differs from that which was utilized to define the aggregate model, among other examples.
- individualizing the aggregate model may depend on the one or more characteristics of the given asset.
- certain characteristics may affect the modification of the aggregate model differently than other characteristics.
- the type, value, existence, or the like of a characteristic may affect the modification as well.
- the asset age may affect a first part of the aggregate model, while an asset class may affect a second, different part of the aggregate model.
- an asset age within a first range of ages may affect the first part of the aggregate model in a first manner
- an asset age within a second range of ages, different from the first range may affect the first part of the aggregate model in a second, different manner.
- Other examples are also possible.
- individualizing the aggregate model may depend on considerations in addition to or alternatively to asset characteristics.
- the aggregate model may be individualized based on sensor and/or actuator readings of an asset when the asset is known to be in a relatively good operating state (e.g., as defined by a mechanic or the like).
- the analytics system 108 may be configured to receive an indication that the asset is in a good operating state (e.g., from a computing device operated by a mechanic) along with operating data from the asset. Based at least on the operating data, the analytics system 108 may then individualize the leading -indicator predictive model for the asset by modifying respective operating limits corresponding to "leading indicator" events.
- Other examples are also possible.
- the analytics system 108 may be configured to define an individualized predictive model for a given asset without first defining an aggregate predictive model. Other examples are also possible.
- the analytics system 108 may also be configured to define a workflow for causing a routing table to be updated based on an unavailability model.
- the analytics system 108 may execute an unavailability model to determine whether a given asset of a plurality of assets in a mesh network is likely to be unavailable within a given period of time in the future.
- the given asset may be unavailable based on a failure of the given asset, the given asset going off-line, a scheduled down time for the given asset, the given asset being unable to communicate over the mesh network, or the given asset otherwise being unable to function as a data relay in the mesh network, among other scenarios.
- a workflow that updates a routing table may cause an asset serving as a node within a mesh network to update its routing information to account for one or multiple other assets likely becoming unavailable in the future.
- the mesh network may be prospectively updated so as to utilize paths that do not rely on a node (asset) that is likely to become unavailable in the future.
- the analytics system 108 may define such a routing-table workflow so that it is triggered based on a variety of triggers.
- a trigger may indicate that a given asset is likely to be unavailable.
- a trigger may take the form of a health score of the given asset.
- the routing-table workflow may be triggered based on the analytics system 108 (or perhaps a local analytics device of the given asset) determining that the given asset's health score meets, stays below, or exceeds an unavailability threshold (e.g., a health-score threshold value), which may depend on how the scoring is structured.
- an unavailability threshold e.g., a health-score threshold value
- the trigger may be based on the analytics system 108 determining that the given asset's health score meets, stays below, or exceeds an unavailability threshold for a given period of time. For example, it may not be enough for the given asset to be momentarily unavailable; the given asset may be deemed to be unavailable if it is determined that the given asset will likely be unavailable for a particular amount of time, such as 30 minutes, one or multiple hours, etc.
- the analytics system 108 may determine the period of time of unavailability that triggers the workflow based on a comparison of recent throughput of a given route being analyzed and a minimum time needed to transmit a given message (e.g., of particular size) through the given route assuming those throughput conditions are present. The period of time may be determined in other manners as well.
- the analytics system 108 may define the routing-table workflow with respect to all of the assets 102, 103, and 104 (e.g., an aggregate workflow). However, in some implementations, the analytics system 108 may individualize the workflow for one or more assets. For example, asset 102 may have a different unavailability threshold than that of asset 103.
- the analytics system 108 may decide whether to define an individualized workflow based on the individualized predictive model. In yet another implementation, the analytics system 108 may decide to define an individualized workflow if an individualized predictive model was defined. In another implementation, the analytics system 108 may use characteristics of interest that affect the efficacy of the aggregate workflow to determine different unavailability thresholds for different assets. Other examples are also possible.
- the analytics system 108 may transmit a signaling message to one or more of the assets 102-104 based on the executed workflow. That is, the signaling message may reflect the analytics system 108 determining that a given asset is likely to be unavailable within the given period of time in the future. The signaling message may instruct the asset to update its routing table to update the routing topology and may also instruct the asset to relay the update to other assets. For example, based on executing the unavailability model and determining that the asset 104 is likely to become unavailable, the analytics system 108 may transmit a signaling message to asset 102, which in turn updates its routing table. Asset 102 may subsequently transmit the signaling message to asset 103, which updates its routing table.
- the signaling message may include instructions to remove the soon to be unavailable asset (e.g., the asset 104) from the routing topology.
- the analytics system 108 may update the routing topology for each asset in the mesh network 105 and transmit an indication of the updated routing topology to each asset (e.g., via transmitting respective routing tables to the assets).
- model -workflow pair could then be executed by the analytics system 108 and/or could be sent to an asset for local execution (e.g., by a local analytics device).
- the analytics system 108 and/or a given asset may determine that the given asset is likely to become unavailable within a given period of time in the future. For instance, the analytics system 108 and/or a given asset may make this determination by comparing the output of the unavailability model to a threshold and thereby determining that the output has met or exceeded the threshold. In turn, the analytics system 108 and/or the given asset may execute the workflow for causing one or more routing tables to be updated. For instance, the analytics system 108 may transmit a signal message to one or more assets that includes a determination that a given asset is unlikely to be unavailable.
- the analytics system 108 may transmit a signal message to one or more assets that includes updates to a routing configuration for the respective asset.
- the soon-to-be unavailable asset may be removed from the routing table or the paths that include that asset may be disabled.
- the routing table may be updated such that the other assets in the mesh network may route around the soon- to-be unavailable asset by presuming that it is unavailable.
- the model-workflow pair disclosed herein may also cause the routing table to later be updated again if it determines that the soon-to-be unavailable asset becomes available again.
- a sensor e.g., an environmental sensor, industrial automation sensor, etc.
- a node may serve as a node and above operations may be modified accordingly.
- FIG. 8 is a flow diagram 800 depicting an example method to update a routing table for a mesh network 105.
- the example method is described as being carried out by the analytics system 108, but this definition phase may be carried out by other systems as well including a local analytics device 220 of one of the assets in the mesh network 105.
- the flow diagram 500 is provided for sake of clarity and explanation and that numerous other combinations of operations may be utilized to update a routing table in a mesh network.
- the analytics system 108 may begin by, based on a predictive model, determining that a given asset of a plurality of assets in a mesh network is likely to be unavailable within a given period of time in the future.
- the plurality of assets may include at least one of a transportation machine, an industrial machine, a medical machine, and a utility machine.
- the predictive model may be based on historical data received from sensors for multiple assets.
- the analytics system 108 may determine that the given asset is likely to be unavailable based on receiving sensor data from the given asset or from other assets, determining a health score for the given asset based on applying the predictive model to the sensor data, and determining that the health score for the given asset has met an unavailability likelihood threshold.
- the predictive model may be based on information associated with the asset. For example, the given asset may be unavailable based on a failure of the asset, a scheduled down time for the asset (e.g., the asset going off-line), the asset powering down for the night, and the asset being unable to communicate over the mesh network.
- the predictive model may determine that the given asset is likely to be unavailable based on an age of the asset, a total time in operation, a time since a last maintenance event, etc. [186] At block 804, in response to the determining, causing a routing configuration for at least one other asset in the mesh network to be updated.
- the routing configuration may include paths for each of the assets in the mesh network to transmit data to or receive data from one or more other assets and to other entities in the system described above with reference to Figure 1.
- the routing configuration may include removing assets from a routing table that are likely to become unavailable.
- the analytics system 108 may keep those assets as part of the routing table but may update paths that include the assets that are likely to become unavailable until a state of those assets changes. For example, where assets are associated with a health score, the assets might be determined to be available if the health score increases or falls below the unavailability likelihood threshold.
- the asset may communicate based on the updated routing table and transmit at least a portion of the updated routing table to another of the plurality of the assets.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Operations Research (AREA)
- Health & Medical Sciences (AREA)
- Mathematical Physics (AREA)
- Evolutionary Computation (AREA)
- Artificial Intelligence (AREA)
- Automation & Control Theory (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Computer Hardware Design (AREA)
- Educational Administration (AREA)
- Primary Health Care (AREA)
- General Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Manufacturing & Machinery (AREA)
- Biomedical Technology (AREA)
- Emergency Management (AREA)
- Computational Linguistics (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Computational Mathematics (AREA)
- Mathematical Optimization (AREA)
- Probability & Statistics with Applications (AREA)
- Algebra (AREA)
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2998345A CA2998345A1 (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on availability of assets |
EP16847112.6A EP3350978A4 (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on availability of assets |
JP2018511273A JP2018528693A (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on asset availability |
AU2016322513A AU2016322513A1 (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on availability of assets |
KR1020187010351A KR20180042444A (en) | 2015-09-14 | 2016-09-12 | Mesh network routing based on availability of assets |
CN201680059994.1A CN108141473A (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on asset availability |
HK18114872.4A HK1255721A1 (en) | 2014-12-01 | 2018-11-21 | Mesh network routing based on availability of assets |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462086155P | 2014-12-01 | 2014-12-01 | |
US201462088651P | 2014-12-07 | 2014-12-07 | |
US14/732,258 US10417076B2 (en) | 2014-12-01 | 2015-06-05 | Asset health score |
US14/744,352 US10261850B2 (en) | 2014-12-01 | 2015-06-19 | Aggregate predictive model and workflow for local execution |
US14/853,189 | 2015-09-14 | ||
US14/853,189 US9842034B2 (en) | 2014-12-01 | 2015-09-14 | Mesh network routing based on availability of assets |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017048640A1 true WO2017048640A1 (en) | 2017-03-23 |
Family
ID=56078998
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2015/063052 WO2016089794A1 (en) | 2014-12-01 | 2015-11-30 | Adaptive handling of operating data |
PCT/US2015/063047 WO2016089792A1 (en) | 2014-12-01 | 2015-11-30 | Asset health scores and uses thereof |
PCT/US2016/051387 WO2017048640A1 (en) | 2014-12-01 | 2016-09-12 | Mesh network routing based on availability of assets |
PCT/US2016/065262 WO2017100245A1 (en) | 2014-12-01 | 2016-12-07 | Computer architecture and method for modifying data intake parameters based on a predictive model |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2015/063052 WO2016089794A1 (en) | 2014-12-01 | 2015-11-30 | Adaptive handling of operating data |
PCT/US2015/063047 WO2016089792A1 (en) | 2014-12-01 | 2015-11-30 | Asset health scores and uses thereof |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2016/065262 WO2017100245A1 (en) | 2014-12-01 | 2016-12-07 | Computer architecture and method for modifying data intake parameters based on a predictive model |
Country Status (10)
Country | Link |
---|---|
US (15) | US10176032B2 (en) |
EP (4) | EP3227784A4 (en) |
JP (4) | JP6652247B2 (en) |
KR (3) | KR20170117377A (en) |
CN (2) | CN107408225B (en) |
AU (4) | AU2015355156A1 (en) |
CA (5) | CA2969455C (en) |
HK (3) | HK1244937A1 (en) |
SG (3) | SG11201708095WA (en) |
WO (4) | WO2016089794A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020073361A (en) * | 2018-08-07 | 2020-05-14 | ザ・ボーイング・カンパニーThe Boeing Company | Methods and systems for identifying associated events in aircraft |
Families Citing this family (232)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10518411B2 (en) * | 2016-05-13 | 2019-12-31 | General Electric Company | Robotic repair or maintenance of an asset |
US9772741B2 (en) * | 2013-03-15 | 2017-09-26 | Konstantinos (Constantin) F. Aliferis | Data analysis computer system and method for organizing, presenting, and optimizing predictive modeling |
US10599155B1 (en) | 2014-05-20 | 2020-03-24 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
WO2020051523A1 (en) * | 2018-09-07 | 2020-03-12 | Uptake Technologies, Inc. | Computer system and method for recommending an operating mode of an asset |
US10176032B2 (en) * | 2014-12-01 | 2019-01-08 | Uptake Technologies, Inc. | Subsystem health score |
US9882798B2 (en) * | 2015-05-13 | 2018-01-30 | Vmware, Inc. | Method and system that analyzes operational characteristics of multi-tier applications |
WO2016196775A1 (en) * | 2015-06-04 | 2016-12-08 | Fischer Block, Inc. | Remaining-life and time-to-failure predictions of power assets |
US10176279B2 (en) | 2015-06-05 | 2019-01-08 | Uptake Technologies, Inc. | Dynamic execution of predictive models and workflows |
US10848371B2 (en) * | 2015-06-11 | 2020-11-24 | Instana, Inc. | User interface for an application performance management system |
USD807376S1 (en) | 2015-06-14 | 2018-01-09 | Google Inc. | Display screen with animated graphical user interface for smart home automation system having a multifunction status |
USD812076S1 (en) | 2015-06-14 | 2018-03-06 | Google Llc | Display screen with graphical user interface for monitoring remote video camera |
US9361011B1 (en) | 2015-06-14 | 2016-06-07 | Google Inc. | Methods and systems for presenting multiple live video feeds in a user interface |
USD797131S1 (en) | 2015-06-14 | 2017-09-12 | Google Inc. | Display screen with user interface for mode selector icons |
USD809522S1 (en) | 2015-06-14 | 2018-02-06 | Google Inc. | Display screen with animated graphical user interface for an alert screen |
USD803241S1 (en) | 2015-06-14 | 2017-11-21 | Google Inc. | Display screen with animated graphical user interface for an alert screen |
US10133443B2 (en) | 2015-06-14 | 2018-11-20 | Google Llc | Systems and methods for smart home automation using a multifunction status and entry point icon |
USD796540S1 (en) | 2015-06-14 | 2017-09-05 | Google Inc. | Display screen with graphical user interface for mobile camera history having event-specific activity notifications |
US10878385B2 (en) | 2015-06-19 | 2020-12-29 | Uptake Technologies, Inc. | Computer system and method for distributing execution of a predictive model |
US10031815B2 (en) * | 2015-06-29 | 2018-07-24 | Ca, Inc. | Tracking health status in software components |
JP6458663B2 (en) * | 2015-06-29 | 2019-01-30 | 株式会社リコー | Information processing system and program |
US10484257B1 (en) * | 2015-07-15 | 2019-11-19 | Amazon Technologies, Inc. | Network event automatic remediation service |
US10474566B2 (en) * | 2015-08-05 | 2019-11-12 | Equifax Inc. | Model integration tool |
US11107365B1 (en) | 2015-08-28 | 2021-08-31 | State Farm Mutual Automobile Insurance Company | Vehicular driver evaluation |
GB2542370B (en) | 2015-09-16 | 2020-05-27 | Arm Ip Ltd | A system for monitoring a plurality of distributed devices |
JP6249003B2 (en) * | 2015-09-30 | 2017-12-20 | トヨタ自動車株式会社 | Control device for hybrid vehicle |
US9916194B2 (en) * | 2015-10-01 | 2018-03-13 | International Business Machines Corporation | System component failure diagnosis |
US10278014B2 (en) * | 2015-11-04 | 2019-04-30 | xAd, Inc. | System and method for using geo-blocks and geo-fences to predict mobile device locations |
US10455363B2 (en) | 2015-11-04 | 2019-10-22 | xAd, Inc. | Systems and methods for using geo-blocks and geo-fences to discover lookalike mobile devices |
US10547971B2 (en) | 2015-11-04 | 2020-01-28 | xAd, Inc. | Systems and methods for creating and using geo-blocks for location-based information service |
US20170161969A1 (en) * | 2015-12-07 | 2017-06-08 | The Boeing Company | System and method for model-based optimization of subcomponent sensor communications |
US10078571B2 (en) * | 2015-12-09 | 2018-09-18 | International Business Machines Corporation | Rule-based adaptive monitoring of application performance |
US20170183016A1 (en) * | 2015-12-28 | 2017-06-29 | General Electric Company | Early warning system for locomotive bearings failures |
US10860405B1 (en) * | 2015-12-28 | 2020-12-08 | EMC IP Holding Company LLC | System operational analytics |
US10733514B1 (en) | 2015-12-28 | 2020-08-04 | EMC IP Holding Company LLC | Methods and apparatus for multi-site time series data analysis |
US11242051B1 (en) | 2016-01-22 | 2022-02-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
US11441916B1 (en) | 2016-01-22 | 2022-09-13 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
US10134278B1 (en) | 2016-01-22 | 2018-11-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US11719545B2 (en) | 2016-01-22 | 2023-08-08 | Hyundai Motor Company | Autonomous vehicle component damage and salvage assessment |
US10747234B1 (en) | 2016-01-22 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
US10452467B2 (en) * | 2016-01-28 | 2019-10-22 | Intel Corporation | Automatic model-based computing environment performance monitoring |
US9718486B1 (en) * | 2016-02-01 | 2017-08-01 | Electro-Motive Diesel, Inc. | System for analyzing health of train |
US10510006B2 (en) * | 2016-03-09 | 2019-12-17 | Uptake Technologies, Inc. | Handling of predictive models based on asset location |
US10530705B2 (en) * | 2016-03-10 | 2020-01-07 | Ricoh Co., Ltd. | Architecture customization at user application layer |
US10318903B2 (en) | 2016-05-06 | 2019-06-11 | General Electric Company | Constrained cash computing system to optimally schedule aircraft repair capacity with closed loop dynamic physical state and asset utilization attainment control |
US11327475B2 (en) | 2016-05-09 | 2022-05-10 | Strong Force Iot Portfolio 2016, Llc | Methods and systems for intelligent collection and analysis of vehicle data |
WO2019028269A2 (en) | 2017-08-02 | 2019-02-07 | Strong Force Iot Portfolio 2016, Llc | Methods and systems for detection in an industrial internet of things data collection environment with large data sets |
US10983507B2 (en) | 2016-05-09 | 2021-04-20 | Strong Force Iot Portfolio 2016, Llc | Method for data collection and frequency analysis with self-organization functionality |
US11774944B2 (en) | 2016-05-09 | 2023-10-03 | Strong Force Iot Portfolio 2016, Llc | Methods and systems for the industrial internet of things |
KR102599073B1 (en) | 2016-05-09 | 2023-11-10 | 스트롱 포스 아이오티 포트폴리오 2016, 엘엘씨 | Methods and systems for the industrial internet of things |
US20180284746A1 (en) | 2016-05-09 | 2018-10-04 | StrongForce IoT Portfolio 2016, LLC | Methods and systems for data collection optimization in an industrial internet of things environment |
US10102056B1 (en) * | 2016-05-23 | 2018-10-16 | Amazon Technologies, Inc. | Anomaly detection using machine learning |
US10901407B2 (en) * | 2016-05-31 | 2021-01-26 | Applied Materials, Inc. | Semiconductor device search and classification |
WO2017210496A1 (en) * | 2016-06-03 | 2017-12-07 | Uptake Technologies, Inc. | Provisioning a local analytics device |
US10333775B2 (en) | 2016-06-03 | 2019-06-25 | Uptake Technologies, Inc. | Facilitating the provisioning of a local analytics device |
AU2017285130B2 (en) | 2016-06-13 | 2022-04-21 | Xevo Inc. | Method and system for providing auto space management using virtuous cycle |
US11237546B2 (en) | 2016-06-15 | 2022-02-01 | Strong Force loT Portfolio 2016, LLC | Method and system of modifying a data collection trajectory for vehicles |
US10346239B1 (en) * | 2016-06-27 | 2019-07-09 | Amazon Technologies, Inc. | Predictive failure of hardware components |
US10416982B1 (en) * | 2016-06-30 | 2019-09-17 | EMC IP Holding Company LLC | Automated analysis system and method |
USD882583S1 (en) | 2016-07-12 | 2020-04-28 | Google Llc | Display screen with graphical user interface |
US10263802B2 (en) | 2016-07-12 | 2019-04-16 | Google Llc | Methods and devices for establishing connections with remote cameras |
US20180048713A1 (en) * | 2016-08-09 | 2018-02-15 | Sciemetric Instruments Inc. | Modular data acquisition and control system |
US10462026B1 (en) * | 2016-08-23 | 2019-10-29 | Vce Company, Llc | Probabilistic classifying system and method for a distributed computing environment |
US10606254B2 (en) * | 2016-09-14 | 2020-03-31 | Emerson Process Management Power & Water Solutions, Inc. | Method for improving process/equipment fault diagnosis |
JP7183790B2 (en) * | 2016-09-14 | 2022-12-06 | 日本電気株式会社 | SYSTEM ANALYSIS SUPPORT DEVICE, SYSTEM ANALYSIS SUPPORT METHOD AND PROGRAM |
US10127125B2 (en) * | 2016-10-21 | 2018-11-13 | Accenture Global Solutions Limited | Application monitoring and failure prediction |
US10152810B2 (en) * | 2016-10-21 | 2018-12-11 | Siemens Aktiengesellschaft | Techniques for displaying data comprising time and angular values acquired from a technical or industrial process |
US10619760B2 (en) | 2016-10-24 | 2020-04-14 | Fisher Controls International Llc | Time-series analytics for control valve health assessment |
US10877465B2 (en) * | 2016-10-24 | 2020-12-29 | Fisher-Rosemount Systems, Inc. | Process device condition and performance monitoring |
US10257163B2 (en) | 2016-10-24 | 2019-04-09 | Fisher-Rosemount Systems, Inc. | Secured process control communications |
US10530748B2 (en) | 2016-10-24 | 2020-01-07 | Fisher-Rosemount Systems, Inc. | Publishing data across a data diode for secured process control communications |
US10270745B2 (en) | 2016-10-24 | 2019-04-23 | Fisher-Rosemount Systems, Inc. | Securely transporting data across a data diode for secured process control communications |
US10386999B2 (en) | 2016-10-26 | 2019-08-20 | Google Llc | Timeline-video relationship presentation for alert events |
USD843398S1 (en) | 2016-10-26 | 2019-03-19 | Google Llc | Display screen with graphical user interface for a timeline-video relationship presentation for alert events |
US11238290B2 (en) | 2016-10-26 | 2022-02-01 | Google Llc | Timeline-video relationship processing for alert events |
US11012461B2 (en) * | 2016-10-27 | 2021-05-18 | Accenture Global Solutions Limited | Network device vulnerability prediction |
US20180135456A1 (en) * | 2016-11-17 | 2018-05-17 | General Electric Company | Modeling to detect gas turbine anomalies |
US10943283B2 (en) * | 2016-11-18 | 2021-03-09 | Cummins Inc. | Service location recommendation tailoring |
CA2987670A1 (en) * | 2016-12-05 | 2018-06-05 | Aware360 Ltd. | Integrated personal safety and equipment monitoring system |
US10304263B2 (en) * | 2016-12-13 | 2019-05-28 | The Boeing Company | Vehicle system prognosis device and method |
CN106485036A (en) * | 2016-12-21 | 2017-03-08 | 杜伯仁 | Based on the method graded to asset securitization Assets Pool by Survival Models |
AU2017382448B2 (en) | 2016-12-22 | 2023-07-13 | Xevo Inc. | Method and system for providing interactive parking management via artificial intelligence analytic (AIA) services using cloud network |
KR20190103150A (en) * | 2017-01-03 | 2019-09-04 | 인텔 코포레이션 | Sensor management and reliability |
JP6706693B2 (en) * | 2017-01-19 | 2020-06-10 | 株式会社日立製作所 | Maintenance management system and maintenance management confirmation device used therefor |
US10579961B2 (en) * | 2017-01-26 | 2020-03-03 | Uptake Technologies, Inc. | Method and system of identifying environment features for use in analyzing asset operation |
JP6879752B2 (en) * | 2017-02-03 | 2021-06-02 | 株式会社日立システムズ | Medical device monitoring system |
US10318364B2 (en) * | 2017-02-23 | 2019-06-11 | Visual Process Limited | Methods and systems for problem-alert aggregation |
US11044329B2 (en) * | 2017-02-27 | 2021-06-22 | NCR Corportation | Client application user experience tracking |
CN106886481B (en) * | 2017-02-28 | 2020-11-27 | 深圳市华傲数据技术有限公司 | Static analysis and prediction method and device for system health degree |
CN108595448B (en) * | 2017-03-17 | 2022-03-04 | 北京京东尚科信息技术有限公司 | Information pushing method and device |
US10691516B2 (en) * | 2017-04-05 | 2020-06-23 | International Business Machines Corporation | Measurement and visualization of resiliency in a hybrid IT infrastructure environment |
US11182236B2 (en) * | 2017-04-13 | 2021-11-23 | Renesas Electronics Corporation | Probabilistic metric for random hardware failure |
US10671039B2 (en) | 2017-05-03 | 2020-06-02 | Uptake Technologies, Inc. | Computer system and method for predicting an abnormal event at a wind turbine in a cluster |
WO2018213617A1 (en) * | 2017-05-18 | 2018-11-22 | Uptake Technologies, Inc. | Computing system and method for approximating predictive models and time-series values |
US10683962B2 (en) | 2017-05-25 | 2020-06-16 | Google Llc | Thermal management for a compact electronic device |
US10819921B2 (en) | 2017-05-25 | 2020-10-27 | Google Llc | Camera assembly having a single-piece cover element |
US10972685B2 (en) | 2017-05-25 | 2021-04-06 | Google Llc | Video camera assembly having an IR reflector |
US20180347843A1 (en) * | 2017-05-30 | 2018-12-06 | Mikros Systems Corporation | Methods and systems for prognostic analysis in electromechanical and environmental control equipment in building management systems |
JP6718415B2 (en) * | 2017-06-26 | 2020-07-08 | 株式会社日立ビルシステム | Parts replacement prediction device, parts replacement prediction system, parts replacement prediction method |
US11014780B2 (en) | 2017-07-06 | 2021-05-25 | Otis Elevator Company | Elevator sensor calibration |
US10829344B2 (en) | 2017-07-06 | 2020-11-10 | Otis Elevator Company | Elevator sensor system calibration |
EP3655825B1 (en) | 2017-07-21 | 2023-11-22 | Johnson Controls Tyco IP Holdings LLP | Building management system with dynamic rules with sub-rule reuse and equation driven smart diagnostics |
CN111133412A (en) * | 2017-07-25 | 2020-05-08 | 奥罗拉实验室有限公司 | Software incremental update and anomaly detection for building vehicle ECU software based on tool chain |
US10921801B2 (en) | 2017-08-02 | 2021-02-16 | Strong Force loT Portfolio 2016, LLC | Data collection systems and methods for updating sensed parameter groups based on pattern recognition |
US11025693B2 (en) * | 2017-08-28 | 2021-06-01 | Banjo, Inc. | Event detection from signal data removing private information |
US10313413B2 (en) | 2017-08-28 | 2019-06-04 | Banjo, Inc. | Detecting events from ingested communication signals |
KR102025145B1 (en) | 2017-09-01 | 2019-09-25 | 두산중공업 주식회사 | Apparatus and Method for Predicting Plant Data |
US20190080258A1 (en) * | 2017-09-13 | 2019-03-14 | Intel Corporation | Observation hub device and method |
US10976903B2 (en) * | 2017-09-17 | 2021-04-13 | Ge Inspection Technologies, Lp | Industrial asset intelligence |
US11687048B2 (en) * | 2017-09-18 | 2023-06-27 | Johnson Controls Tyco IP Holdings LLP | Method and apparatus for evaluation of temperature sensors |
US10585774B2 (en) * | 2017-09-27 | 2020-03-10 | International Business Machines Corporation | Detection of misbehaving components for large scale distributed systems |
WO2019068196A1 (en) | 2017-10-06 | 2019-04-11 | Raven Telemetry Inc. | Augmented industrial management |
TWI663570B (en) * | 2017-10-20 | 2019-06-21 | 財團法人資訊工業策進會 | Power consumption analyzing server and power consumption analyzing method thereof |
US10379982B2 (en) | 2017-10-31 | 2019-08-13 | Uptake Technologies, Inc. | Computer system and method for performing a virtual load test |
US10956843B2 (en) * | 2017-11-07 | 2021-03-23 | International Business Machines Corporation | Determining optimal device refresh cycles and device repairs through cognitive analysis of unstructured data and device health scores |
US11334854B2 (en) * | 2017-11-10 | 2022-05-17 | General Electric Company | Systems and methods to generate an asset workscope |
US20190304596A1 (en) * | 2017-11-14 | 2019-10-03 | Tagnos, Inc. | Use Of Historic And Contemporary Tracking Data To Improve Healthcare Facility Operations |
US10672204B2 (en) | 2017-11-15 | 2020-06-02 | The Boeing Company | Real time streaming analytics for flight data processing |
CN107730893B (en) * | 2017-11-30 | 2019-08-09 | 大连理工大学 | A kind of shared bus website passenger flow forecasting based on passenger's trip multidimensional characteristic |
US20190180300A1 (en) | 2017-12-07 | 2019-06-13 | Fifth Third Bancorp | Geospatial market analytics |
US11010233B1 (en) * | 2018-01-18 | 2021-05-18 | Pure Storage, Inc | Hardware-based system monitoring |
WO2019142331A1 (en) * | 2018-01-19 | 2019-07-25 | 株式会社日立製作所 | Failure prediction system and failure prediction method |
JP6996002B2 (en) * | 2018-01-22 | 2022-01-17 | 株式会社日立ハイテクソリューションズ | Protecting your system from harmful communications |
EP3514555B1 (en) * | 2018-01-22 | 2020-07-22 | Siemens Aktiengesellschaft | Apparatus for monitoring an actuator system, method for providing an apparatus for monitoring an actuator system and method for monitoring an actuator system |
US10585724B2 (en) | 2018-04-13 | 2020-03-10 | Banjo, Inc. | Notifying entities of relevant events |
US20190266575A1 (en) * | 2018-02-27 | 2019-08-29 | Honeywell International, Inc. | Modifying field workflows |
US11080127B1 (en) * | 2018-02-28 | 2021-08-03 | Arizona Public Service Company | Methods and apparatus for detection of process parameter anomalies |
US10169135B1 (en) | 2018-03-02 | 2019-01-01 | Uptake Technologies, Inc. | Computer system and method of detecting manufacturing network anomalies |
DE102018203179A1 (en) * | 2018-03-02 | 2019-09-05 | Robert Bosch Gmbh | Device, in particular handheld power tool management device, and method for monitoring and / or managing a plurality of objects |
US10554518B1 (en) * | 2018-03-02 | 2020-02-04 | Uptake Technologies, Inc. | Computer system and method for evaluating health of nodes in a manufacturing network |
WO2019182756A1 (en) * | 2018-03-23 | 2019-09-26 | Siemens Healthcare Diagnostics Inc. | Methods, apparatus, and systems for integration of diagnostic laboratory devices |
US10354462B1 (en) * | 2018-04-06 | 2019-07-16 | Toyota Motor Engineering & Manufacturing North America, Inc. | Fault diagnosis in power electronics using adaptive PCA |
US11691755B2 (en) * | 2018-04-16 | 2023-07-04 | Wing Aviation Llc | Multi-UAV management |
US10635095B2 (en) * | 2018-04-24 | 2020-04-28 | Uptake Technologies, Inc. | Computer system and method for creating a supervised failure model |
US20210217256A1 (en) * | 2018-05-16 | 2021-07-15 | Siemens Mobility Austria Gmbh | Method and Apparatus for Diagnosing and Monitoring Vehicles, Vehicle Components and Routes |
CN108648071B (en) | 2018-05-17 | 2020-05-19 | 阿里巴巴集团控股有限公司 | Resource value evaluation method and device based on block chain |
WO2019226715A1 (en) * | 2018-05-21 | 2019-11-28 | Promptlink Communications, Inc. | Techniques for assessing a customer premises equipment device |
US10896114B2 (en) * | 2018-05-23 | 2021-01-19 | Seagate Technology Llc | Machine learning error prediction in storage arrays |
US11823274B2 (en) | 2018-06-04 | 2023-11-21 | Machine Cover, Inc. | Parametric instruments and methods relating to business interruption |
US11842407B2 (en) | 2018-06-04 | 2023-12-12 | Machine Cover, Inc. | Parametric instruments and methods relating to geographical area business interruption |
US20190378349A1 (en) * | 2018-06-07 | 2019-12-12 | GM Global Technology Operations LLC | Vehicle remaining useful life prediction |
DE102018209407A1 (en) * | 2018-06-13 | 2019-12-19 | Robert Bosch Gmbh | Method and device for handling an anomaly in a communication network |
KR102062097B1 (en) * | 2018-06-27 | 2020-06-23 | 송암시스콤 주식회사 | A Bus Information Terminal Having Dual Structure With Automatic Recovery Function |
WO2020023410A1 (en) * | 2018-07-22 | 2020-01-30 | Scott Amron | Distributed inventory system |
DE102018118437A1 (en) | 2018-07-31 | 2020-02-06 | Airbus Defence and Space GmbH | System and method for monitoring the condition of an unmanned aircraft |
US11172324B2 (en) | 2018-08-17 | 2021-11-09 | xAd, Inc. | Systems and methods for predicting targeted location events |
US11146911B2 (en) | 2018-08-17 | 2021-10-12 | xAd, Inc. | Systems and methods for pacing information campaigns based on predicted and observed location events |
US11134359B2 (en) | 2018-08-17 | 2021-09-28 | xAd, Inc. | Systems and methods for calibrated location prediction |
US10349208B1 (en) | 2018-08-17 | 2019-07-09 | xAd, Inc. | Systems and methods for real-time prediction of mobile device locations |
KR102566324B1 (en) * | 2018-08-23 | 2023-08-14 | 지멘스 악티엔게젤샤프트 | Artificial intelligence computing device, control method and apparatus, engineer station, and industrial automation system |
WO2020053727A1 (en) * | 2018-09-10 | 2020-03-19 | 3M Innovative Properties Company | Method and system for monitoring a health of a power cable accessory based on machine learning |
WO2020068036A1 (en) * | 2018-09-24 | 2020-04-02 | Hewlett-Packard Development Company, L.P. | Device status assessment |
US11455223B2 (en) * | 2018-10-11 | 2022-09-27 | International Business Machines Corporation | Using system errors and manufacturer defects in system components causing the system errors to determine a quality assessment value for the components |
US11573879B2 (en) * | 2018-10-22 | 2023-02-07 | General Electric Company | Active asset monitoring |
US11200103B2 (en) * | 2018-10-26 | 2021-12-14 | International Business Machines Corporation | Using a machine learning module to perform preemptive identification and reduction of risk of failure in computational systems |
US11200142B2 (en) | 2018-10-26 | 2021-12-14 | International Business Machines Corporation | Perform preemptive identification and reduction of risk of failure in computational systems by training a machine learning module |
US10635360B1 (en) * | 2018-10-29 | 2020-04-28 | International Business Machines Corporation | Adjusting data ingest based on compaction rate in a dispersed storage network |
US11182596B2 (en) * | 2018-11-08 | 2021-11-23 | International Business Machines Corporation | Identifying a deficiency of a facility |
JP6531213B1 (en) * | 2018-12-04 | 2019-06-12 | Psp株式会社 | Medical device failure prediction system, medical device failure prediction method, and program |
KR102124779B1 (en) * | 2018-12-21 | 2020-06-19 | 한국수력원자력 주식회사 | Early warning device of plant of start and stop using multi-predictive model |
US11062233B2 (en) * | 2018-12-21 | 2021-07-13 | The Nielsen Company (Us), Llc | Methods and apparatus to analyze performance of watermark encoding devices |
US11188691B2 (en) * | 2018-12-21 | 2021-11-30 | Utopus Insights, Inc. | Scalable system and method for forecasting wind turbine failure using SCADA alarm and event logs |
KR102152403B1 (en) * | 2018-12-24 | 2020-09-04 | 아주대학교산학협력단 | Apparatus and method for detecting abnormal behavior using data pattern analysis |
US10984154B2 (en) * | 2018-12-27 | 2021-04-20 | Utopus Insights, Inc. | System and method for evaluating models for predictive failure of renewable energy assets |
CN109840312B (en) * | 2019-01-22 | 2022-11-29 | 新奥数能科技有限公司 | Abnormal value detection method and device for boiler load rate-energy efficiency curve |
US11334057B2 (en) | 2019-01-25 | 2022-05-17 | Waygate Technologies Usa, Lp | Anomaly detection for predictive maintenance and deriving outcomes and workflows based on data quality |
US11030067B2 (en) * | 2019-01-29 | 2021-06-08 | Uptake Technologies, Inc. | Computer system and method for presenting asset insights at a graphical user interface |
WO2020159680A1 (en) * | 2019-01-31 | 2020-08-06 | Exxonmobil Research And Engineering Company | Monitoring and reporting operational performance of machinery |
US11232368B2 (en) * | 2019-02-20 | 2022-01-25 | Accenture Global Solutions Limited | System for predicting equipment failure events and optimizing manufacturing operations |
US11084387B2 (en) * | 2019-02-25 | 2021-08-10 | Toyota Research Institute, Inc. | Systems, methods, and storage media for arranging a plurality of cells in a vehicle battery pack |
US20220103420A1 (en) * | 2019-03-01 | 2022-03-31 | Nec Corporation | Network management method, network system, aggregated analysis apparatus, terminal apparatus and program |
SE543982C2 (en) * | 2019-03-26 | 2021-10-12 | Stoneridge Electronics Ab | Method of processing vehicle data from multiple sources and controller therefor |
JP7162560B2 (en) * | 2019-03-28 | 2022-10-28 | 日立造船株式会社 | Information processing device, information processing method, information processing program, and garbage incineration plant |
CN113632027A (en) * | 2019-04-01 | 2021-11-09 | Abb瑞士股份有限公司 | Asset condition monitoring method using automatic anomaly detection |
JP7320368B2 (en) * | 2019-04-09 | 2023-08-03 | ナブテスコ株式会社 | FAILURE PREDICTION DEVICE, FAILURE PREDICTION METHOD AND COMPUTER PROGRAM |
CA3042657A1 (en) * | 2019-05-06 | 2020-11-06 | Otr Wheel Safety, Inc. | Integrated system for assessing integrity of wheels and rims of off the road vehicles |
CN111846095B (en) * | 2019-05-14 | 2022-05-17 | 北京骑胜科技有限公司 | Fault detection device, electric power-assisted vehicle and fault detection method |
CN110163387A (en) * | 2019-05-17 | 2019-08-23 | 合肥帧讯软件有限公司 | A kind of Design of Laboratory Management System |
AU2020282322A1 (en) | 2019-05-24 | 2021-12-23 | Berkeley Lights, Inc. | Systems and methods for optimizing an instrument system workflow |
US11604934B2 (en) * | 2019-05-29 | 2023-03-14 | Nec Corporation | Failure prediction using gradient-based sensor identification |
US11887177B2 (en) * | 2019-06-18 | 2024-01-30 | Hewlett-Packard Development Company, L.P. | Part re-order based on part-specific sensor data |
US20200401904A1 (en) * | 2019-06-24 | 2020-12-24 | GE Precision Healthcare LLC | Adaptive medical imaging device configuration using artificial intelligence |
US11817212B2 (en) | 2019-06-26 | 2023-11-14 | Roche Diagnostics Operations, Inc. | Maintenance method for a laboratory system |
CN114072825A (en) * | 2019-07-02 | 2022-02-18 | 科路实有限责任公司 | Monitoring, predicting and maintaining condition of railway elements using digital twinning |
GB201909762D0 (en) * | 2019-07-08 | 2019-08-21 | Edwards Vacuum Llc | Vacuum system with diagnostic circuitry and a method and computer program for monitoring the health of such a vacuum system |
FR3098938B1 (en) * | 2019-07-15 | 2022-01-07 | Bull Sas | Method and device for determining an anomaly prediction performance index value in a computer infrastructure from performance indicator values |
US20210019651A1 (en) * | 2019-07-18 | 2021-01-21 | Hitachi, Ltd. | Method for integrating prediction result |
US11334410B1 (en) * | 2019-07-22 | 2022-05-17 | Intuit Inc. | Determining aberrant members of a homogenous cluster of systems using external monitors |
US11086749B2 (en) * | 2019-08-01 | 2021-08-10 | International Business Machines Corporation | Dynamically updating device health scores and weighting factors |
US11374814B2 (en) | 2019-08-01 | 2022-06-28 | Hewlett Packard Enterprise Development Lp | Network device configuration update using rank and health |
US11010222B2 (en) * | 2019-08-29 | 2021-05-18 | Sap Se | Failure mode specific analytics using parametric models |
FR3101164B1 (en) * | 2019-09-25 | 2023-08-04 | Mouafo Serge Romaric Tembo | Method for real-time parsimonious predictive maintenance of a critical system, computer program product and associated device |
US11088932B2 (en) * | 2019-10-14 | 2021-08-10 | International Business Machines Corporation | Managing network system incidents |
US11321115B2 (en) * | 2019-10-25 | 2022-05-03 | Vmware, Inc. | Scalable and dynamic data collection and processing |
US11379694B2 (en) | 2019-10-25 | 2022-07-05 | Vmware, Inc. | Scalable and dynamic data collection and processing |
EP3822725A1 (en) * | 2019-11-15 | 2021-05-19 | General Electric Company | Systems, and methods for diagnosing an additive manufacturing device |
CN112906900A (en) * | 2019-11-19 | 2021-06-04 | D.S.瑞德有限公司 | Method and system for monitoring vehicle condition and for alerting anomalies/defects |
US20210382992A1 (en) * | 2019-11-22 | 2021-12-09 | Pure Storage, Inc. | Remote Analysis of Potentially Corrupt Data Written to a Storage System |
US11941116B2 (en) | 2019-11-22 | 2024-03-26 | Pure Storage, Inc. | Ransomware-based data protection parameter modification |
US11921573B2 (en) * | 2019-12-02 | 2024-03-05 | Accenture Global Solutions Limited | Systems and methods for predictive system failure monitoring |
JP7335154B2 (en) * | 2019-12-17 | 2023-08-29 | 株式会社東芝 | Information processing device, information processing method, and program |
US11509136B2 (en) | 2019-12-30 | 2022-11-22 | Utopus Insights, Inc. | Scalable systems and methods for assessing healthy condition scores in renewable asset management |
GB2591772A (en) * | 2020-02-06 | 2021-08-11 | Roads & Transp Authority | Asset maintenance management system and method |
JP7418256B2 (en) * | 2020-03-24 | 2024-01-19 | 東芝テック株式会社 | Information processing equipment and programs |
US11558767B2 (en) | 2020-03-26 | 2023-01-17 | Sony Group Corporation | Electronic device and related methods for predicting initiation of establishment of a network with one or more other electronic devices |
US11482341B2 (en) | 2020-05-07 | 2022-10-25 | Carrier Corporation | System and a method for uniformly characterizing equipment category |
US20210365449A1 (en) * | 2020-05-20 | 2021-11-25 | Caterpillar Inc. | Callaborative system and method for validating equipment failure models in an analytics crowdsourcing environment |
EP3923213A1 (en) * | 2020-06-08 | 2021-12-15 | ABB Power Grids Switzerland AG | Method and computing system for performing a prognostic health analysis for an asset |
JP2023530904A (en) * | 2020-06-12 | 2023-07-20 | エフ. ホフマン-ラ ロシュ アーゲー | System and method for evaluating bays on diagnostic equipment |
US11210160B1 (en) * | 2020-08-13 | 2021-12-28 | Servicenow, Inc. | Computer information technology alert remediation selection based on alert similarity |
US11188405B1 (en) | 2020-08-25 | 2021-11-30 | Servicenow, Inc. | Similar alert identification based on application fingerprints |
WO2022072908A1 (en) * | 2020-10-02 | 2022-04-07 | Tonkean, Inc. | Systems and methods for data objects for asynchronou workflows |
US11995616B2 (en) * | 2020-10-09 | 2024-05-28 | ANI Technologies Private Limited | Asset health management for vehicles |
US11290343B1 (en) * | 2020-12-10 | 2022-03-29 | Hitachi, Ltd. | System and method for asset and data management |
US11675342B2 (en) * | 2020-12-24 | 2023-06-13 | Noodle Analytics, Inc. | AI-based smart health surveillance system and method |
WO2022159565A1 (en) * | 2021-01-22 | 2022-07-28 | Rutgers, The State University Of New Jersey | Systems for infrastructure degradation modelling and methods of use thereof |
US11633168B2 (en) * | 2021-04-02 | 2023-04-25 | AIX Scan, Inc. | Fast 3D radiography with multiple pulsed X-ray sources by deflecting tube electron beam using electro-magnetic field |
US20220358434A1 (en) * | 2021-05-06 | 2022-11-10 | Honeywell International Inc. | Foundation applications as an accelerator providing well defined extensibility and collection of seeded templates for enhanced user experience and quicker turnaround |
US11688059B2 (en) * | 2021-05-27 | 2023-06-27 | International Business Machines Corporation | Asset maintenance prediction using infrared and regular images |
US11494250B1 (en) * | 2021-06-14 | 2022-11-08 | EMC IP Holding Company LLC | Method and system for variable level of logging based on (long term steady state) system error equilibrium |
TW202311961A (en) * | 2021-09-02 | 2023-03-16 | 遠傳電信股份有限公司 | Method and system for detecting an abnormal occurrence of an application program |
US20230080981A1 (en) * | 2021-09-13 | 2023-03-16 | International Business Machines Corporation | Predictive maintenance explanations based on user profile |
US11789842B2 (en) * | 2021-10-11 | 2023-10-17 | Dell Products L.P. | System and method for advanced detection of potential system impairment |
US20230112875A1 (en) * | 2021-10-13 | 2023-04-13 | Honeywell International Inc. | Alarm performance optimizer |
US11797408B2 (en) * | 2021-12-30 | 2023-10-24 | Juniper Networks, Inc. | Dynamic prediction of system resource requirement of network software in a live network using data driven models |
US20230221693A1 (en) * | 2022-01-10 | 2023-07-13 | General Electric Technology Gmbh | Systems and methods for integrated condition monitoring for power system asset health scoring |
US20230236922A1 (en) * | 2022-01-24 | 2023-07-27 | International Business Machines Corporation | Failure Prediction Using Informational Logs and Golden Signals |
US20230236890A1 (en) * | 2022-01-25 | 2023-07-27 | Poplar Technologies, Inc. | Apparatus for generating a resource probability model |
US20230259419A1 (en) * | 2022-02-14 | 2023-08-17 | Capital One Services, Llc | Incident resolution system |
US20230394888A1 (en) * | 2022-06-01 | 2023-12-07 | The Boeing Company | Vehicle Health Management Using a Counterfactual Machine Learning Model |
JP7292538B1 (en) * | 2022-06-17 | 2023-06-16 | 三菱電機株式会社 | Soundness evaluation device, soundness evaluation method, and soundness evaluation program |
US11907230B1 (en) * | 2023-01-10 | 2024-02-20 | Dell Products L.P. | System and method for distributed management of hardware based on intent |
US11929891B1 (en) | 2023-01-10 | 2024-03-12 | Dell Products L.P. | System and method for distributed management of hardware through relationship management |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090146839A1 (en) * | 2006-05-17 | 2009-06-11 | Tanla Solutions Limited | Automated meter reading system and method thereof |
JP2013239827A (en) * | 2012-05-14 | 2013-11-28 | Secom Co Ltd | Communication failure support system |
US20140098658A1 (en) * | 2006-01-31 | 2014-04-10 | Sigma Designs, Inc. | Node repair in a mesh network |
US20140286301A1 (en) * | 2003-07-17 | 2014-09-25 | Sensicast Systems | Method and apparatus for wireless communication in a mesh network using frequency schedule |
Family Cites Families (254)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3026510A (en) | 1959-10-02 | 1962-03-20 | Bell Telephone Labor Inc | Self timed pcm encoder |
DE3816520A1 (en) * | 1988-05-14 | 1989-11-23 | Bosch Gmbh Robert | CONTROL PROCESS AND DEVICE, IN PARTICULAR LAMBAR CONTROL |
US5633800A (en) | 1992-10-21 | 1997-05-27 | General Electric Company | Integrated model-based reasoning/expert system diagnosis for rotating machinery |
US5363317A (en) * | 1992-10-29 | 1994-11-08 | United Technologies Corporation | Engine failure monitor for a multi-engine aircraft having partial engine failure and driveshaft failure detection |
JP3287889B2 (en) * | 1992-11-24 | 2002-06-04 | トーヨーエイテック株式会社 | Quality control equipment |
US5566092A (en) * | 1993-12-30 | 1996-10-15 | Caterpillar Inc. | Machine fault diagnostics system and method |
US5918222A (en) | 1995-03-17 | 1999-06-29 | Kabushiki Kaisha Toshiba | Information disclosing apparatus and multi-modal information input/output system |
JP3366837B2 (en) | 1997-08-15 | 2003-01-14 | 株式会社小松製作所 | Machine abnormality monitoring device and method |
US6473659B1 (en) | 1998-04-10 | 2002-10-29 | General Electric Company | System and method for integrating a plurality of diagnostic related information |
US6115697A (en) | 1999-02-19 | 2000-09-05 | Dynamic Research Group | Computerized system and method for optimizing after-tax proceeds |
US6625500B1 (en) | 1999-03-16 | 2003-09-23 | Chou H. Li | Self-optimizing method and machine |
US6947797B2 (en) | 1999-04-02 | 2005-09-20 | General Electric Company | Method and system for diagnosing machine malfunctions |
US6622264B1 (en) | 1999-10-28 | 2003-09-16 | General Electric Company | Process and system for analyzing fault log data from a machine so as to identify faults predictive of machine failures |
US6336065B1 (en) | 1999-10-28 | 2002-01-01 | General Electric Company | Method and system for analyzing fault and snapshot operational parameter data for diagnostics of machine malfunctions |
JP3892614B2 (en) | 1999-04-30 | 2007-03-14 | 新日本製鐵株式会社 | Equipment and product process abnormality diagnosis method and apparatus |
US6353902B1 (en) * | 1999-06-08 | 2002-03-05 | Nortel Networks Limited | Network fault prediction and proactive maintenance system |
US20110208567A9 (en) | 1999-08-23 | 2011-08-25 | Roddy Nicholas E | System and method for managing a fleet of remote assets |
US7783507B2 (en) * | 1999-08-23 | 2010-08-24 | General Electric Company | System and method for managing a fleet of remote assets |
US6442542B1 (en) | 1999-10-08 | 2002-08-27 | General Electric Company | Diagnostic system with learning capabilities |
US6615367B1 (en) | 1999-10-28 | 2003-09-02 | General Electric Company | Method and apparatus for diagnosing difficult to diagnose faults in a complex system |
US7020595B1 (en) | 1999-11-26 | 2006-03-28 | General Electric Company | Methods and apparatus for model based diagnostics |
US6650949B1 (en) | 1999-12-30 | 2003-11-18 | General Electric Company | Method and system for sorting incident log data from a plurality of machines |
US6634000B1 (en) | 2000-02-01 | 2003-10-14 | General Electric Company | Analyzing fault logs and continuous data for diagnostics for a locomotive |
US6725398B1 (en) | 2000-02-11 | 2004-04-20 | General Electric Company | Method, system, and program product for analyzing a fault log of a malfunctioning machine |
US20030126258A1 (en) | 2000-02-22 | 2003-07-03 | Conkright Gary W. | Web based fault detection architecture |
US6957172B2 (en) | 2000-03-09 | 2005-10-18 | Smartsignal Corporation | Complex signal decomposition and modeling |
US7739096B2 (en) | 2000-03-09 | 2010-06-15 | Smartsignal Corporation | System for extraction of representative data for training of adaptive process monitoring equipment |
WO2001067262A1 (en) | 2000-03-09 | 2001-09-13 | Smartsignal Corporation | Generalized lensing angular similarity operator |
US6952662B2 (en) | 2000-03-30 | 2005-10-04 | Smartsignal Corporation | Signal differentiation system using improved non-linear operator |
US6708156B1 (en) | 2000-04-17 | 2004-03-16 | Michael Von Gonten, Inc. | System and method for projecting market penetration |
US20020059075A1 (en) | 2000-05-01 | 2002-05-16 | Schick Louis A. | Method and system for managing a land-based vehicle |
US20160078695A1 (en) * | 2000-05-01 | 2016-03-17 | General Electric Company | Method and system for managing a fleet of remote assets and/or ascertaining a repair for an asset |
US6799154B1 (en) | 2000-05-25 | 2004-09-28 | General Electric Comapny | System and method for predicting the timing of future service events of a product |
DE60136773D1 (en) | 2000-06-16 | 2009-01-15 | Ntn Toyo Bearing Co Ltd | Monitoring, diagnostic and sales system for machine components |
US6760631B1 (en) | 2000-10-04 | 2004-07-06 | General Electric Company | Multivariable control method and system without detailed prediction model |
US20020091972A1 (en) | 2001-01-05 | 2002-07-11 | Harris David P. | Method for predicting machine or process faults and automated system for implementing same |
US7233886B2 (en) | 2001-01-19 | 2007-06-19 | Smartsignal Corporation | Adaptive modeling of changed states in predictive condition monitoring |
US6859739B2 (en) | 2001-01-19 | 2005-02-22 | Smartsignal Corporation | Global state change indicator for empirical modeling in condition based monitoring |
US7373283B2 (en) | 2001-02-22 | 2008-05-13 | Smartsignal Corporation | Monitoring and fault detection system and method using improved empirical model for range extrema |
US7539597B2 (en) | 2001-04-10 | 2009-05-26 | Smartsignal Corporation | Diagnostic systems and methods for predictive condition monitoring |
US20020183971A1 (en) * | 2001-04-10 | 2002-12-05 | Wegerich Stephan W. | Diagnostic systems and methods for predictive condition monitoring |
US6643600B2 (en) | 2001-04-26 | 2003-11-04 | General Electric Company | Method and system for assessing adjustment factors in testing or monitoring process |
KR100523228B1 (en) | 2001-05-08 | 2005-10-20 | 히다치 겡키 가부시키 가이샤 | Working machine, trouble diagnosis system of working machine, and maintenance system of working machine |
US7107491B2 (en) | 2001-05-16 | 2006-09-12 | General Electric Company | System, method and computer product for performing automated predictive reliability |
US6975962B2 (en) | 2001-06-11 | 2005-12-13 | Smartsignal Corporation | Residual signal alert generation for condition monitoring using approximated SPRT distribution |
US7120685B2 (en) * | 2001-06-26 | 2006-10-10 | International Business Machines Corporation | Method and apparatus for dynamic configurable logging of activities in a distributed computing system |
US7457732B2 (en) | 2001-08-17 | 2008-11-25 | General Electric Company | System and method for measuring quality of baseline modeling techniques |
US7428478B2 (en) | 2001-08-17 | 2008-09-23 | General Electric Company | System and method for improving accuracy of baseline models |
US8108249B2 (en) | 2001-12-04 | 2012-01-31 | Kimberly-Clark Worldwide, Inc. | Business planner |
EP1468361A1 (en) | 2001-12-19 | 2004-10-20 | Netuitive Inc. | Method and system for analyzing and predicting the behavior of systems |
JP2003256367A (en) | 2002-03-06 | 2003-09-12 | Seiko Epson Corp | Information providing system concerning electronic equipment error and server for managing past error results of electric equipment |
US6892163B1 (en) | 2002-03-08 | 2005-05-10 | Intellectual Assets Llc | Surveillance system and method having an adaptive sequential probability fault detection test |
US7660705B1 (en) | 2002-03-19 | 2010-02-09 | Microsoft Corporation | Bayesian approach for learning regression decision graph models and regression models for time series analysis |
US8176186B2 (en) | 2002-10-30 | 2012-05-08 | Riverbed Technology, Inc. | Transaction accelerator for client-server communications systems |
PT1579288T (en) | 2002-11-04 | 2017-06-23 | Ge Intelligent Platforms Inc | System state monitoring using recurrent local learning machine |
US6823253B2 (en) | 2002-11-27 | 2004-11-23 | General Electric Company | Methods and apparatus for model predictive control of aircraft gas turbine engines |
US8017411B2 (en) * | 2002-12-18 | 2011-09-13 | GlobalFoundries, Inc. | Dynamic adaptive sampling rate for model prediction |
JP4333331B2 (en) | 2002-12-20 | 2009-09-16 | セイコーエプソン株式会社 | Failure prediction system, failure prediction program, and failure prediction method |
US20040243636A1 (en) * | 2003-03-18 | 2004-12-02 | Smartsignal Corporation | Equipment health monitoring architecture for fleets of assets |
US7634384B2 (en) | 2003-03-18 | 2009-12-15 | Fisher-Rosemount Systems, Inc. | Asset optimization reporting in a process plant |
GB0307406D0 (en) * | 2003-03-31 | 2003-05-07 | British Telecomm | Data analysis system and method |
US7054706B2 (en) | 2003-06-30 | 2006-05-30 | Intel Corporation | Managing supply chains with model predictive control |
EP1652138A4 (en) | 2003-07-11 | 2006-12-06 | Computer Ass Think Inc | Modeling of applications and business process services through auto discovery analysis |
US7181370B2 (en) | 2003-08-26 | 2007-02-20 | Siemens Energy & Automation, Inc. | System and method for remotely obtaining and managing machine data |
DE10345440A1 (en) | 2003-09-30 | 2005-05-12 | Siemens Ag | Method, computer program with program code means and computer program product for analyzing influencing variables on a burning process in a combustion chamber using a trainable, statistical model |
US7127371B2 (en) | 2003-10-08 | 2006-10-24 | Ge Medical Systems Information | Customized medical equipment preventative maintenance method and system |
US7451210B2 (en) * | 2003-11-24 | 2008-11-11 | International Business Machines Corporation | Hybrid method for event prediction and system control |
WO2005062554A1 (en) | 2003-12-23 | 2005-07-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for efficient routing in ad hoc networks |
CA2848301A1 (en) | 2004-01-09 | 2005-07-28 | United Parcel Service Of America, Inc. | System, method and apparatus for capturing telematics data with an active rfid tag |
KR101271876B1 (en) | 2004-03-23 | 2013-06-10 | 더 리젠트스 오브 더 유니이버시티 오브 캘리포니아 | Apparatus and method for improving reliability of collected sensor data over a network |
US7062370B2 (en) | 2004-03-30 | 2006-06-13 | Honeywell International Inc. | Model-based detection, diagnosis of turbine engine faults |
US7447666B2 (en) | 2004-04-09 | 2008-11-04 | The Boeing Company | System and method for analyzing a pattern in a time-stamped event sequence |
US7729789B2 (en) | 2004-05-04 | 2010-06-01 | Fisher-Rosemount Systems, Inc. | Process plant monitoring based on multivariate statistical analysis and on-line process simulation |
US7412626B2 (en) | 2004-05-21 | 2008-08-12 | Sap Ag | Method and system for intelligent and adaptive exception handling |
JP2006072717A (en) * | 2004-09-02 | 2006-03-16 | Hitachi Ltd | Disk subsystem |
US7570581B2 (en) * | 2004-09-23 | 2009-08-04 | Motorola, Inc. | Dynamic reduction of route reconvergence time |
US7280941B2 (en) | 2004-12-29 | 2007-10-09 | General Electric Company | Method and apparatus for in-situ detection and isolation of aircraft engine faults |
US7640145B2 (en) | 2005-04-25 | 2009-12-29 | Smartsignal Corporation | Automated model configuration and deployment system for equipment health monitoring |
US7536364B2 (en) | 2005-04-28 | 2009-05-19 | General Electric Company | Method and system for performing model-based multi-objective asset optimization and decision-making |
US9846479B1 (en) | 2005-05-30 | 2017-12-19 | Invent.Ly, Llc | Smart security device with monitoring mode and communication mode |
US20060293777A1 (en) | 2005-06-07 | 2006-12-28 | International Business Machines Corporation | Automated and adaptive threshold setting |
KR101322434B1 (en) * | 2005-07-11 | 2013-10-28 | 브룩스 오토메이션 인코퍼레이티드 | Intelligent condition-monitoring and fault diagnostic system |
US20070174449A1 (en) * | 2005-07-22 | 2007-07-26 | Ankur Gupta | Method and system for identifying potential adverse network conditions |
US7333917B2 (en) | 2005-08-11 | 2008-02-19 | The University Of North Carolina At Chapel Hill | Novelty detection systems, methods and computer program products for real-time diagnostics/prognostics in complex physical systems |
US7599762B2 (en) * | 2005-08-24 | 2009-10-06 | Rockwell Automatino Technologies, Inc. | Model-based control for crane control and underway replenishment |
US7174233B1 (en) | 2005-08-29 | 2007-02-06 | International Business Machines Corporation | Quality/reliability system and method in multilevel manufacturing environment |
US7509235B2 (en) | 2005-08-31 | 2009-03-24 | General Electric Company | Method and system for forecasting reliability of assets |
US7714735B2 (en) * | 2005-09-13 | 2010-05-11 | Daniel Rockwell | Monitoring electrical assets for fault and efficiency correction |
JP4717579B2 (en) | 2005-09-30 | 2011-07-06 | 株式会社小松製作所 | Maintenance work management system for work machines |
US20070088570A1 (en) * | 2005-10-18 | 2007-04-19 | Honeywell International, Inc. | System and method for predicting device deterioration |
US7484132B2 (en) * | 2005-10-28 | 2009-01-27 | International Business Machines Corporation | Clustering process for software server failure prediction |
US7869908B2 (en) | 2006-01-20 | 2011-01-11 | General Electric Company | Method and system for data collection and analysis |
US7509537B1 (en) | 2006-02-02 | 2009-03-24 | Rockwell Collins, Inc. | Prognostic processor system for real-time failure analysis of line replaceable units |
US7496798B2 (en) | 2006-02-14 | 2009-02-24 | Jaw Link | Data-centric monitoring method |
US7647131B1 (en) * | 2006-03-09 | 2010-01-12 | Rockwell Automation Technologies, Inc. | Dynamic determination of sampling rates |
US7693608B2 (en) | 2006-04-12 | 2010-04-06 | Edsa Micro Corporation | Systems and methods for alarm filtering and management within a real-time data acquisition and monitoring environment |
US7949436B2 (en) | 2006-05-19 | 2011-05-24 | Oracle America, Inc. | Method and apparatus for automatically detecting and correcting misalignment of a semiconductor chip |
US7558771B2 (en) * | 2006-06-07 | 2009-07-07 | Gm Global Technology Operations, Inc. | System and method for selection of prediction tools |
US20080040244A1 (en) * | 2006-08-08 | 2008-02-14 | Logcon Spec Ops, Inc. | Tracking and Managing Assets |
US20080097945A1 (en) | 2006-08-09 | 2008-04-24 | The University Of North Carolina At Chapel Hill | Novelty detection systems, methods and computer program products for real-time diagnostics/prognostics in complex physical systems |
US20080059120A1 (en) | 2006-08-30 | 2008-03-06 | Fei Xiao | Using fault history to predict replacement parts |
US20080059080A1 (en) * | 2006-08-31 | 2008-03-06 | Caterpillar Inc. | Method and system for selective, event-based communications |
US8275577B2 (en) | 2006-09-19 | 2012-09-25 | Smartsignal Corporation | Kernel-based method for detecting boiler tube leaks |
JP2008117129A (en) | 2006-11-02 | 2008-05-22 | Nsk Ltd | Data collection device for abnormality analysis and on-vehicle controller using the same |
US7725293B2 (en) | 2006-12-07 | 2010-05-25 | General Electric Company | System and method for equipment remaining life estimation |
US8311774B2 (en) | 2006-12-15 | 2012-11-13 | Smartsignal Corporation | Robust distance measures for on-line monitoring |
US7661032B2 (en) * | 2007-01-06 | 2010-02-09 | International Business Machines Corporation | Adjusting sliding window parameters in intelligent event archiving and failure analysis |
JP4892367B2 (en) * | 2007-02-02 | 2012-03-07 | 株式会社日立システムズ | Abnormal sign detection system |
US7548830B2 (en) | 2007-02-23 | 2009-06-16 | General Electric Company | System and method for equipment remaining life estimation |
US20080221834A1 (en) | 2007-03-09 | 2008-09-11 | General Electric Company | Method and system for enhanced fault detection workflow |
US7730364B2 (en) * | 2007-04-05 | 2010-06-01 | International Business Machines Corporation | Systems and methods for predictive failure management |
US20080255760A1 (en) * | 2007-04-16 | 2008-10-16 | Honeywell International, Inc. | Forecasting system |
US8145578B2 (en) | 2007-04-17 | 2012-03-27 | Eagel View Technologies, Inc. | Aerial roof estimation system and method |
US8229769B1 (en) | 2007-06-13 | 2012-07-24 | United Services Automobile Association | Systems and methods for processing overhead imagery |
US7949659B2 (en) * | 2007-06-29 | 2011-05-24 | Amazon Technologies, Inc. | Recommendation system with multiple integrated recommenders |
EP2171598B1 (en) | 2007-08-03 | 2017-01-11 | GE Intelligent Platforms, Inc. | Fuzzy classification approach to fault pattern matching |
US7919940B2 (en) | 2007-10-21 | 2011-04-05 | Ge Intelligent Platforms, Inc. | System and method for jerk limited trajectory planning for a path planner |
US8050800B2 (en) | 2007-10-21 | 2011-11-01 | Ge Intelligent Platforms, Inc. | Method and system for meeting end conditions in a motion control system |
US8700550B1 (en) | 2007-11-30 | 2014-04-15 | Intellectual Assets Llc | Adaptive model training system and method |
US7962240B2 (en) | 2007-12-20 | 2011-06-14 | Ge Intelligent Platforms, Inc. | Methods and systems for synchronizing a control signal of a slave follower with a master source |
JP2009206850A (en) | 2008-02-28 | 2009-09-10 | Fuji Xerox Co Ltd | Failure diagnosis device and program |
US8352216B2 (en) | 2008-05-29 | 2013-01-08 | General Electric Company | System and method for advanced condition monitoring of an asset system |
US7756678B2 (en) | 2008-05-29 | 2010-07-13 | General Electric Company | System and method for advanced condition monitoring of an asset system |
US7822578B2 (en) | 2008-06-17 | 2010-10-26 | General Electric Company | Systems and methods for predicting maintenance of intelligent electronic devices |
US20090326890A1 (en) | 2008-06-30 | 2009-12-31 | Honeywell International Inc. | System and method for predicting system events and deterioration |
US8285402B2 (en) | 2008-07-14 | 2012-10-09 | Ge Intelligent Platforms, Inc. | Method and system for safety monitored terminal block |
GB0813561D0 (en) | 2008-07-24 | 2008-09-03 | Rolls Royce Plc | Developments in or relating to power demand management |
US8060274B2 (en) * | 2008-10-30 | 2011-11-15 | International Business Machines Corporation | Location-based vehicle maintenance scheduling |
JP5058947B2 (en) * | 2008-11-10 | 2012-10-24 | 株式会社日立製作所 | Terminal, program, and inventory management method |
US8369281B2 (en) * | 2008-11-24 | 2013-02-05 | At&T Intellectual Property I, L.P. | Cell-to-WiFi switcher |
US8289150B2 (en) | 2008-12-05 | 2012-10-16 | Industrial Technology Research Institute | Wireless sensor network and data sensing method thereof |
KR101044074B1 (en) | 2008-12-24 | 2011-06-27 | 동국대학교기술지주 주식회사 | System and method for CAFM based on public concept of space ownership |
KR20100076708A (en) | 2008-12-26 | 2010-07-06 | 한국건설기술연구원 | Asset management information system for social infrastructures |
US8515719B2 (en) | 2009-01-14 | 2013-08-20 | Hitachi, Ltd. | Apparatus anomaly monitoring method and system |
US8024069B2 (en) | 2009-01-28 | 2011-09-20 | Ge Intelligent Platforms, Inc. | System and method for path planning |
US8224765B2 (en) * | 2009-02-05 | 2012-07-17 | Honeywell International Inc. | Method for computing the relative likelihood of failures |
US8989887B2 (en) | 2009-02-11 | 2015-03-24 | Applied Materials, Inc. | Use of prediction data in monitoring actual production targets |
JP5370832B2 (en) * | 2009-07-01 | 2013-12-18 | 株式会社リコー | State determination device and failure prediction system using the same |
DE102009043091A1 (en) * | 2009-09-25 | 2011-03-31 | Wincor Nixdorf International Gmbh | Device for handling notes of value |
US9007896B2 (en) | 2009-10-07 | 2015-04-14 | Verizon Patent And Licensing Inc. | Congestion control based on call responses |
CN102045181B (en) * | 2009-10-10 | 2013-08-07 | 中国移动通信集团公司 | Method and device for handling terminal offline fault |
WO2011104760A1 (en) | 2010-02-26 | 2011-09-01 | 株式会社 日立製作所 | Failure source diagnosis system and method |
EP2375637A1 (en) | 2010-03-22 | 2011-10-12 | British Telecommunications Public Limited Company | Network routing adaptation based on failure prediction |
JP5416630B2 (en) * | 2010-03-24 | 2014-02-12 | 株式会社日立製作所 | Moving object abnormality judgment support system |
US9189485B2 (en) * | 2010-04-26 | 2015-11-17 | Hitachi, Ltd. | Time-series data diagnosing/compressing method |
CA2799404C (en) | 2010-05-14 | 2020-10-06 | Harnischfeger Technologies, Inc. | Remote monitoring of machine alarms |
US8234420B2 (en) | 2010-07-14 | 2012-07-31 | Ge Intelligent Platforms, Inc. | Method, system, and apparatus for communicating using multiple controllers |
US8634314B2 (en) * | 2010-07-30 | 2014-01-21 | Cisco Technology, Inc. | Reporting statistics on the health of a sensor node in a sensor network |
JP5025776B2 (en) * | 2010-09-28 | 2012-09-12 | 株式会社東芝 | Abnormality diagnosis filter generator |
US8532795B2 (en) | 2010-10-04 | 2013-09-10 | General Electric Company | Method and system for offline code validation |
JP2012133672A (en) | 2010-12-22 | 2012-07-12 | Mitsubishi Heavy Ind Ltd | Design optimization device and design optimization method for welded structure |
EP2668545B1 (en) | 2011-01-26 | 2019-06-12 | Google LLC | Dynamic predictive modeling platform |
US8825840B2 (en) * | 2011-02-22 | 2014-09-02 | Intuit Inc. | Systems and methods for self-adjusting logging of log messages |
US8682454B2 (en) | 2011-02-28 | 2014-03-25 | United Technologies Corporation | Method and system for controlling a multivariable system with limits |
US8862938B2 (en) | 2011-04-18 | 2014-10-14 | General Electric Company | System, method, and apparatus for resolving errors in a system |
US20120271612A1 (en) | 2011-04-20 | 2012-10-25 | Barsoum Wael K | Predictive modeling |
US8594982B2 (en) | 2011-06-09 | 2013-11-26 | Pulsar Informatics, Inc. | Systems and methods for distributed calculation of fatigue-risk prediction and optimization |
US8620853B2 (en) | 2011-07-19 | 2013-12-31 | Smartsignal Corporation | Monitoring method using kernel regression modeling with pattern sequences |
DE102011108019A1 (en) * | 2011-07-19 | 2013-01-24 | Daimler Ag | Method for determining a quality of a reducing agent solution containing ammonia used for the reduction of nitrogen oxide |
US8660980B2 (en) | 2011-07-19 | 2014-02-25 | Smartsignal Corporation | Monitoring system using kernel regression modeling with pattern sequences |
US9256224B2 (en) | 2011-07-19 | 2016-02-09 | GE Intelligent Platforms, Inc | Method of sequential kernel regression modeling for forecasting and prognostics |
GB2494416A (en) | 2011-09-07 | 2013-03-13 | Rolls Royce Plc | Asset Condition Monitoring Using Internal Signals Of The Controller |
US9477223B2 (en) | 2011-09-14 | 2016-10-25 | General Electric Company | Condition monitoring system and method |
US9176819B2 (en) | 2011-09-23 | 2015-11-03 | Fujitsu Limited | Detecting sensor malfunctions using compression analysis of binary decision diagrams |
US8560494B1 (en) | 2011-09-30 | 2013-10-15 | Palantir Technologies, Inc. | Visual data importer |
JP2013092954A (en) * | 2011-10-27 | 2013-05-16 | Hitachi Ltd | Management task support device, management task support method, and management task support system |
EP2726987A4 (en) * | 2011-11-04 | 2016-05-18 | Hewlett Packard Development Co | Fault processing in a system |
US8560165B2 (en) * | 2012-01-17 | 2013-10-15 | GM Global Technology Operations LLC | Co-operative on-board and off-board component and system diagnosis and prognosis |
US8825567B2 (en) | 2012-02-08 | 2014-09-02 | General Electric Company | Fault prediction of monitored assets |
US20140309853A1 (en) | 2013-04-15 | 2014-10-16 | Flextronics Ap, Llc | Vehicle diagnostics and roadside assistance |
US8626385B2 (en) | 2012-03-15 | 2014-01-07 | Caterpillar Inc. | Systems and methods for analyzing machine performance |
KR101728597B1 (en) * | 2012-04-19 | 2017-04-19 | 에프. 호프만-라 로슈 아게 | Method and device for determining an analyte concentration in blood |
US9051945B2 (en) | 2012-04-30 | 2015-06-09 | Caterpillar Inc. | System and method for identifying impending hydraulic pump failure |
US8850000B2 (en) | 2012-05-08 | 2014-09-30 | Electro-Motive Diesel, Inc. | Trigger-based data collection system |
US9063856B2 (en) | 2012-05-09 | 2015-06-23 | Infosys Limited | Method and system for detecting symptoms and determining an optimal remedy pattern for a faulty device |
US9433348B2 (en) * | 2012-05-18 | 2016-09-06 | Koninklijke Philips N.V. | Method of rendering hemodynamic instability index indicator information |
US20130325502A1 (en) | 2012-06-05 | 2013-12-05 | Ari Robicsek | System and method for providing syndrome-specific, weighted-incidence treatment regimen recommendations |
US9234750B2 (en) | 2012-07-30 | 2016-01-12 | Caterpillar Inc. | System and method for operating a machine |
US20140060030A1 (en) | 2012-08-31 | 2014-03-06 | Caterpillar Inc. | Hydraulic accumulator health monitor |
US9960929B2 (en) | 2012-09-21 | 2018-05-01 | Google Llc | Environmental sensing with a doorbell at a smart-home |
RU2015115489A (en) | 2012-09-24 | 2016-11-20 | Кейтерпиллар Инк. | MANAGEMENT AND CONTROL OF MINING OPERATIONS |
US20150205657A1 (en) * | 2012-09-28 | 2015-07-23 | Longsand Limited | Predicting failure of a storage device |
JPWO2014054274A1 (en) * | 2012-10-02 | 2016-08-25 | パナソニックIpマネジメント株式会社 | Monitoring device and monitoring method |
WO2014054051A1 (en) | 2012-10-03 | 2014-04-10 | Forbes Marshall Pvt. Ltd. | Health monitoring system for a process plant and a method thereof |
US9176183B2 (en) | 2012-10-15 | 2015-11-03 | GlobalFoundries, Inc. | Method and system for wafer quality predictive modeling based on multi-source information with heterogeneous relatedness |
US9613413B2 (en) | 2012-10-17 | 2017-04-04 | Caterpillar Inc. | Methods and systems for determining part wear based on digital image of part |
US9139188B2 (en) | 2012-11-01 | 2015-09-22 | Caterpillar Inc. | Prediction control strategy for hybrid machinery |
US9647906B2 (en) * | 2012-11-02 | 2017-05-09 | Rockwell Automation Technologies, Inc. | Cloud based drive monitoring solution |
EP2920658B1 (en) * | 2012-11-19 | 2019-03-27 | Siemens Corporation | Resilient optimization and control for distributed systems |
US20140170617A1 (en) | 2012-12-19 | 2014-06-19 | Caterpillar Inc. | Monitoring System for a Machine |
US9151681B2 (en) | 2012-12-19 | 2015-10-06 | Progress Rail Services Corporation | Temperature detector having different types of independent sensors |
US8918246B2 (en) | 2012-12-27 | 2014-12-23 | Caterpillar Inc. | Augmented reality implement control |
US20140184643A1 (en) | 2012-12-27 | 2014-07-03 | Caterpillar Inc. | Augmented Reality Worksite |
US20140188778A1 (en) | 2012-12-27 | 2014-07-03 | General Electric Company | Computer-Implemented System for Detecting Anomaly Conditions in a Fleet of Assets and Method of Using the Same |
US9217999B2 (en) | 2013-01-22 | 2015-12-22 | General Electric Company | Systems and methods for analyzing data in a non-destructive testing system |
US10001518B2 (en) | 2013-02-04 | 2018-06-19 | Abb Schweiz Ag | System and method for power transmission and distribution asset condition prediction and diagnosis |
CN104021264B (en) * | 2013-02-28 | 2017-06-20 | 华为技术有限公司 | A kind of failure prediction method and device |
US10909137B2 (en) * | 2014-10-06 | 2021-02-02 | Fisher-Rosemount Systems, Inc. | Streaming data for analytics in process control systems |
US9593591B2 (en) | 2013-03-13 | 2017-03-14 | Rolls-Royce Corporation | Engine health monitoring and power allocation control for a turbine engine using electric generators |
US9262255B2 (en) * | 2013-03-14 | 2016-02-16 | International Business Machines Corporation | Multi-stage failure analysis and prediction |
US9535808B2 (en) | 2013-03-15 | 2017-01-03 | Mtelligence Corporation | System and methods for automated plant asset failure detection |
US8917274B2 (en) | 2013-03-15 | 2014-12-23 | Palantir Technologies Inc. | Event matrix based on integrated data |
US8937619B2 (en) | 2013-03-15 | 2015-01-20 | Palantir Technologies Inc. | Generating an object time series from data objects |
US8909656B2 (en) | 2013-03-15 | 2014-12-09 | Palantir Technologies Inc. | Filter chains with associated multipath views for exploring large data sets |
US9959738B2 (en) | 2013-04-08 | 2018-05-01 | Centega Services, Llc | Reciprocating machinery monitoring system and method |
JP5768834B2 (en) | 2013-04-12 | 2015-08-26 | 横河電機株式会社 | Plant model management apparatus and method |
US20140330747A1 (en) | 2013-05-01 | 2014-11-06 | International Business Machines Corporation | Asset lifecycle management |
US20140330609A1 (en) | 2013-05-01 | 2014-11-06 | International Business Machines Corporation | Performance Driven Municipal Asset Needs and Sustainability Analysis |
US8799799B1 (en) | 2013-05-07 | 2014-08-05 | Palantir Technologies Inc. | Interactive geospatial map |
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 |
WO2014197497A2 (en) | 2013-06-03 | 2014-12-11 | The Morey Corporation | Geospatial asset tracking systems, methods and apparatus for acquiring, manipulating and presenting telematic metadata |
US11055450B2 (en) * | 2013-06-10 | 2021-07-06 | Abb Power Grids Switzerland Ag | Industrial asset health model update |
US10534361B2 (en) | 2013-06-10 | 2020-01-14 | Abb Schweiz Ag | Industrial asset health model update |
US8886601B1 (en) | 2013-06-20 | 2014-11-11 | Palantir Technologies, Inc. | System and method for incrementally replicating investigative analysis data |
US20160196500A1 (en) | 2013-06-26 | 2016-07-07 | Climate Risk Pty Ltd | Computer implemented frameworks and methodologies for enabling risk analysis for a system comprising physical assets |
US10018997B2 (en) | 2013-06-28 | 2018-07-10 | Fisher-Rosemount Systems, Inc. | Non-intrusive data analytics in a process control system |
US8713467B1 (en) | 2013-08-09 | 2014-04-29 | Palantir Technologies, Inc. | Context-sensitive views |
US9319905B2 (en) * | 2013-08-30 | 2016-04-19 | Google Inc. | Re-tasking balloons in a balloon network based on expected failure modes of balloons |
US9535774B2 (en) * | 2013-09-09 | 2017-01-03 | International Business Machines Corporation | Methods, apparatus and system for notification of predictable memory failure |
US8689108B1 (en) | 2013-09-24 | 2014-04-01 | Palantir Technologies, Inc. | Presentation and analysis of user interaction data |
US8938686B1 (en) | 2013-10-03 | 2015-01-20 | Palantir Technologies Inc. | Systems and methods for analyzing performance of an entity |
US8812960B1 (en) | 2013-10-07 | 2014-08-19 | Palantir Technologies Inc. | Cohort-based presentation of user interaction data |
US8786605B1 (en) | 2013-10-24 | 2014-07-22 | Palantir Technologies Inc. | Systems and methods for distance and congestion-aware resource deployment |
US9355010B2 (en) * | 2013-10-29 | 2016-05-31 | Seagate Technology Llc | Deriving an operational state of a data center using a predictive computer analysis model |
JP5530020B1 (en) * | 2013-11-01 | 2014-06-25 | 株式会社日立パワーソリューションズ | Abnormality diagnosis system and abnormality diagnosis method |
US8832594B1 (en) | 2013-11-04 | 2014-09-09 | Palantir Technologies Inc. | Space-optimized display of multi-column tables with selective text truncation based on a combined text width |
US8868537B1 (en) | 2013-11-11 | 2014-10-21 | Palantir Technologies, Inc. | Simple web search |
US9753796B2 (en) * | 2013-12-06 | 2017-09-05 | Lookout, Inc. | Distributed monitoring, evaluation, and response for multiple devices |
US20150184549A1 (en) * | 2013-12-31 | 2015-07-02 | General Electric Company | Methods and systems for enhancing control of power plant generating units |
US9774522B2 (en) * | 2014-01-06 | 2017-09-26 | Cisco Technology, Inc. | Triggering reroutes using early learning machine-based prediction of failures |
WO2015112892A1 (en) | 2014-01-24 | 2015-07-30 | Telvent Usa Llc | Utility resource asset management system |
JP6459180B2 (en) | 2014-02-10 | 2019-01-30 | 富士ゼロックス株式会社 | Failure prediction system, failure prediction device, job execution device, and program |
CN105940637B (en) | 2014-02-27 | 2020-03-31 | 英特尔公司 | Method and apparatus for workload optimization, scheduling and placement for rack-level architecture computing systems |
US10410116B2 (en) | 2014-03-11 | 2019-09-10 | SparkCognition, Inc. | System and method for calculating remaining useful time of objects |
US8935201B1 (en) | 2014-03-18 | 2015-01-13 | Palantir Technologies Inc. | Determining and extracting changed data from a data source |
US10521747B2 (en) | 2014-04-08 | 2019-12-31 | Northrop Grumman Systems Corporation | System and method for providing a scalable semantic mechanism for policy-driven assessment and effective action taking on dynamically changing data |
US9857238B2 (en) | 2014-04-18 | 2018-01-02 | Google Inc. | Thermodynamic model generation and implementation using observed HVAC and/or enclosure characteristics |
US20160028605A1 (en) | 2014-05-30 | 2016-01-28 | Reylabs Inc. | Systems and methods involving mobile linear asset efficiency, exploration, monitoring and/or display aspects |
US9734693B2 (en) | 2014-07-09 | 2017-08-15 | Mckinley Equipment Corporation | Remote equipment monitoring and notification using a server system |
US9733629B2 (en) | 2014-07-21 | 2017-08-15 | Honeywell International Inc. | Cascaded model predictive control (MPC) approach for plantwide control and optimization |
US20160028648A1 (en) | 2014-07-25 | 2016-01-28 | At&T Intellectual Property I, L.P. | Resource Management Service |
US9348710B2 (en) * | 2014-07-29 | 2016-05-24 | Saudi Arabian Oil Company | Proactive failure recovery model for distributed computing using a checkpoint frequency determined by a MTBF threshold |
CN104398431B (en) | 2014-11-21 | 2017-03-29 | 贵州神奇药物研究院 | It is a kind of to treat Chinese medicine extract product of chloasma and preparation method thereof |
EP3026510B1 (en) | 2014-11-26 | 2022-08-17 | General Electric Company | Methods and systems for enhancing control of power plant generating units |
US10176032B2 (en) * | 2014-12-01 | 2019-01-08 | Uptake Technologies, Inc. | Subsystem health score |
US9960598B2 (en) | 2015-03-03 | 2018-05-01 | General Electric Company | Methods and systems for enhancing control of power plant generating units |
JP6339951B2 (en) * | 2015-03-04 | 2018-06-06 | 株式会社日立製作所 | Data collection system, data collection method, server, and gateway |
CA2983149A1 (en) | 2015-05-15 | 2016-11-24 | Parker-Hannifan Corporation | Integrated asset integrity management system |
US10197631B2 (en) | 2015-06-01 | 2019-02-05 | Verizon Patent And Licensing Inc. | Systems and methods for determining vehicle battery health |
US10579750B2 (en) * | 2015-06-05 | 2020-03-03 | Uptake Technologies, Inc. | Dynamic execution of predictive models |
US10254751B2 (en) * | 2015-06-05 | 2019-04-09 | Uptake Technologies, Inc. | Local analytics at an asset |
US10007710B2 (en) * | 2015-09-21 | 2018-06-26 | Splunk Inc. | Adaptive control of data collection requests sent to external data sources |
US10489752B2 (en) | 2016-08-26 | 2019-11-26 | General Electric Company | Failure mode ranking in an asset management system |
-
2015
- 2015-06-05 US US14/732,285 patent/US10176032B2/en active Active
- 2015-06-05 US US14/732,320 patent/US9471452B2/en active Active
- 2015-06-05 US US14/732,303 patent/US20160155098A1/en not_active Abandoned
- 2015-06-05 US US14/732,258 patent/US10417076B2/en active Active
- 2015-06-19 US US14/744,369 patent/US20160371616A1/en not_active Abandoned
- 2015-06-19 US US14/744,352 patent/US10261850B2/en active Active
- 2015-09-14 US US14/853,189 patent/US9842034B2/en active Active
- 2015-11-30 KR KR1020177018199A patent/KR20170117377A/en unknown
- 2015-11-30 AU AU2015355156A patent/AU2015355156A1/en not_active Abandoned
- 2015-11-30 WO PCT/US2015/063052 patent/WO2016089794A1/en active Application Filing
- 2015-11-30 SG SG11201708095WA patent/SG11201708095WA/en unknown
- 2015-11-30 JP JP2017547925A patent/JP6652247B2/en active Active
- 2015-11-30 AU AU2015355154A patent/AU2015355154A1/en not_active Abandoned
- 2015-11-30 JP JP2017547926A patent/JP2018500710A/en active Pending
- 2015-11-30 SG SG11201708094XA patent/SG11201708094XA/en unknown
- 2015-11-30 EP EP15865024.2A patent/EP3227784A4/en not_active Ceased
- 2015-11-30 CA CA2969455A patent/CA2969455C/en active Active
- 2015-11-30 CA CA2969452A patent/CA2969452A1/en active Pending
- 2015-11-30 KR KR1020177018201A patent/KR20170118039A/en unknown
- 2015-11-30 CN CN201580073119.4A patent/CN107408225B/en active Active
- 2015-11-30 CN CN201580073123.0A patent/CN107408226A/en active Pending
- 2015-11-30 WO PCT/US2015/063047 patent/WO2016089792A1/en active Application Filing
- 2015-11-30 EP EP15866135.5A patent/EP3227852A4/en not_active Ceased
- 2015-12-08 US US14/963,209 patent/US20170161621A1/en not_active Abandoned
- 2015-12-08 US US14/963,212 patent/US10025653B2/en active Active
- 2015-12-08 US US14/963,208 patent/US20170161659A1/en not_active Abandoned
-
2016
- 2016-09-06 US US15/257,276 patent/US9864665B2/en active Active
- 2016-09-06 US US15/257,258 patent/US9910751B2/en active Active
- 2016-09-12 JP JP2018511273A patent/JP2018528693A/en active Pending
- 2016-09-12 WO PCT/US2016/051387 patent/WO2017048640A1/en active Application Filing
- 2016-09-12 EP EP16847112.6A patent/EP3350978A4/en not_active Withdrawn
- 2016-09-12 CA CA2998345A patent/CA2998345A1/en not_active Abandoned
- 2016-09-12 AU AU2016322513A patent/AU2016322513A1/en not_active Abandoned
- 2016-12-07 SG SG11201804807VA patent/SG11201804807VA/en unknown
- 2016-12-07 JP JP2018529105A patent/JP2018536941A/en active Pending
- 2016-12-07 EP EP16873709.6A patent/EP3387531A4/en not_active Withdrawn
- 2016-12-07 KR KR1020187018739A patent/KR20180082606A/en unknown
- 2016-12-07 AU AU2016368298A patent/AU2016368298A1/en not_active Abandoned
- 2016-12-07 CA CA3007466A patent/CA3007466A1/en not_active Abandoned
- 2016-12-07 WO PCT/US2016/065262 patent/WO2017100245A1/en active Application Filing
-
2017
- 2017-11-06 US US15/805,124 patent/US10545845B1/en active Active
-
2018
- 2018-04-03 HK HK18104387.3A patent/HK1244937A1/en unknown
- 2018-04-03 HK HK18104388.2A patent/HK1244938A1/en unknown
- 2018-09-07 US US16/125,335 patent/US11144378B2/en active Active
- 2018-11-16 US US16/194,036 patent/US10754721B2/en active Active
- 2018-11-21 HK HK18114872.4A patent/HK1255721A1/en unknown
-
2019
- 2019-09-06 CA CA3111567A patent/CA3111567A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140286301A1 (en) * | 2003-07-17 | 2014-09-25 | Sensicast Systems | Method and apparatus for wireless communication in a mesh network using frequency schedule |
US20140098658A1 (en) * | 2006-01-31 | 2014-04-10 | Sigma Designs, Inc. | Node repair in a mesh network |
US20090146839A1 (en) * | 2006-05-17 | 2009-06-11 | Tanla Solutions Limited | Automated meter reading system and method thereof |
JP2013239827A (en) * | 2012-05-14 | 2013-11-28 | Secom Co Ltd | Communication failure support system |
Non-Patent Citations (2)
Title |
---|
P. BROWN: "Standard Based Integration Specification: Common Information Model Framework for Asset Health Data Exchange", 16 December 2014 (2014-12-16), XP055371098, Retrieved from the Internet <URL:https://www.epri.com/abstracts/pages/productabstract.aspx?ProductId=000000003002002586> * |
See also references of EP3350978A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020073361A (en) * | 2018-08-07 | 2020-05-14 | ザ・ボーイング・カンパニーThe Boeing Company | Methods and systems for identifying associated events in aircraft |
JP7256092B2 (en) | 2018-08-07 | 2023-04-11 | ザ・ボーイング・カンパニー | Method and apparatus for identifying correlated events in an aircraft |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10545845B1 (en) | Mesh network routing based on availability of assets | |
US10579750B2 (en) | Dynamic execution of predictive models | |
US11036902B2 (en) | Dynamic execution of predictive models and workflows | |
US10878385B2 (en) | Computer system and method for distributing execution of a predictive model | |
US10254751B2 (en) | Local analytics at an asset | |
EP3427200B1 (en) | Handling of predictive models based on asset location | |
EP3497569A1 (en) | Computer architecture and method for recommending asset repairs | |
EP3311345A1 (en) | Local analytics at an asset | |
KR20180042444A (en) | Mesh network routing based on availability of assets |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16847112 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2018511273 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11201801651V Country of ref document: SG |
|
ENP | Entry into the national phase |
Ref document number: 2998345 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2016322513 Country of ref document: AU Date of ref document: 20160912 Kind code of ref document: A Ref document number: 20187010351 Country of ref document: KR Kind code of ref document: A |