CN117677966A

CN117677966A - Configuration of asset monitoring system

Info

Publication number: CN117677966A
Application number: CN202280042135.7A
Authority: CN
Inventors: A·R·汉普顿; C·沃斯诺普
Original assignee: Baker Hughes Holdings LLC
Current assignee: Baker Hughes Holdings LLC
Priority date: 2021-07-14
Filing date: 2022-07-11
Publication date: 2024-03-08
Also published as: EP4371055A1

Abstract

The present invention provides a method for configuring an asset monitoring system. The method may include receiving a configuration including measured configuration attributes determined by an asset monitoring system configured to monitor an asset. The method may also include generating a graphical user interface including the identifier of the measurement and one or more configuration attributes corresponding to the measurement. The method may also include verifying the received configuration and receiving a selection of a measurement within a first window of the GUI. The method may further include updating the GUI to include verification errors corresponding to the selected measurements within the second window. The method may further include correcting the validation error and updating the GUI to include a third window listing at least one correction corresponding to the selected validation error. Related systems and non-transitory media related to the method are also provided.

Description

Configuration of asset monitoring system

Cross Reference to Related Applications

The present application claims priority from 35U.S. c. ≡120 to U.S. patent application No. 17/861,407 entitled "CONFIGURATION OF ASSET MONITORING SYSTEMS" filed on day 11, 7, 2022, and from 35U.S. c. ≡119 (e) to U.S. provisional application No. 63/221,927 entitled "CONFIGURATION OF ASSET MONITORING SYSTEMS" filed on day 14, 7, 2021. The entire contents of each of these applications are hereby expressly incorporated by reference in their entirety.

Background

Many industries, such as hydrocarbon extraction, refining, and power generation, may rely heavily on the operation of assets (e.g., machinery) and, in some cases, on the continuous operation of such assets. In these environments, unplanned asset outages and/or malfunctions may lead to serious consequences, including costs due to production loss and/or costs, potential injury to workers, and the like. In view of these risks, it may be common to monitor selected parameters of various assets during operation. The measurement of the operating parameters may provide an indication of the condition of the respective asset component and the condition of the entire asset. Thus, deviations between normal operation and asset operation can be identified and accounted for to avoid asset downtime and/or failure. Accordingly, asset monitoring may provide a variety of long-term benefits, such as lower production costs, reduced equipment downtime, improved reliability, and enhanced security.

Disclosure of Invention

An asset monitoring system (e.g., a protection monitoring system and/or a condition monitoring system) may be configured to obtain one or more measurements of respective operating parameters that characterize a monitored asset. These measurements may be further analyzed to determine whether the operating parameters are within or outside of a predetermined range of normal (safe) operation. For example, the set point may be used to define a normal operating range, and measurements of operating parameters outside of that range may be recorded (e.g., as an alarm, warning, etc.). In the context of a protection monitoring system, if the measured operating parameter is outside of a normal operating range, the protection monitoring system may control the monitored asset such that the measured operating parameter is within the normal operating range and/or suspend operation of the monitored asset to avoid damage to the monitored asset. In the context of a condition monitoring system, measured operating parameters may be used to make predictions regarding performance of a monitored asset and to actively identify potential asset damage or failure before it occurs.

The sensor may be used to obtain a sensor signal that characterizes an operating parameter of the asset. Other computing devices may execute algorithms to analyze the sensor signals and determine operating parameters. Protection and condition monitoring functions may be performed by measurement of operating parameters of the asset. However, these sensors and algorithms may need to be configured to provide accurate operating parameter measurements.

Existing asset monitoring systems may be manually configured. That is, an operator may be required to manually input one or more configuration attributes for the sensors and/or algorithms to determine the operating parameter measurements. However, such manual configuration can be complex and tedious, and requires a great deal of domain expertise. Further, configuration attributes may vary between corresponding asset monitoring systems. Therefore, special care needs to be taken to employ appropriate configuration attributes and avoid errors. In addition, when errors in configuration attributes occur, they can be problematic because the configuration attributes can be complex and interrelated.

Accordingly, embodiments of the present disclosure provide systems and methods for improving the configuration of asset monitoring systems. As discussed in more detail below, the configuration system may be used in conjunction with an asset monitoring system to identify errors in configuration attributes and generate a Graphical User Interface (GUI) that facilitates resolving such errors. For example, the configuration system may determine one or more possible solutions to correct the selected error. The GUI may display these correction options for consideration by the operator. Once the operator selects a correction, the configuration system may further update the configuration of the asset monitoring system to achieve the selected correction.

In certain embodiments, the correction options may be based on domain knowledge and best practices (e.g., as determined by the manufacturer of the asset monitoring system, the operator of the asset monitoring system, and/or another regulatory agency). In further embodiments, the configuration system may be configured to automatically resolve configuration errors. For example, one of the corrections to the validation error may be the default. The default correction may be further associated with a configuration file. Thus, by selecting a configuration file, default correction may be automatically implemented for one or more configuration errors.

Advantageously, such automation may significantly reduce the amount of time required to configure the asset monitoring system, as it may help operators resolve errors that they would otherwise take more time to manually resolve. Furthermore, the configuration best practices may be coded, thereby reducing the level of domain knowledge required by the operator to resolve configuration errors.

In one embodiment, a method for configuring an asset monitoring system is provided. The method may include receiving a configuration by a configuration system including one or more processors. The configuration may include at least one configuration attribute corresponding to a measurement determined by an asset monitoring system configured to monitor the asset. The method may also include generating, by the configuration system, a Graphical User Interface (GUI). The GUI may include a first window including an identifier of a measurement and one or more configuration attributes corresponding to the measurement. The method may also include outputting, by the configuration system, the GUI to a display device for displaying the GUI. The method may further include verifying, by the configuration system, the received configuration. The verification may include receiving a selection of a measurement within a first window of the GUI. Verification may also include comparing a configuration attribute of the one or more configuration attributes to a corresponding reference configuration attribute. The verification may additionally include: when a configuration attribute of the one or more configuration attributes does not satisfy its corresponding reference configuration attribute, at least one validation error for the selected measurement is determined. The method may further include updating the GUI to include at least one validation error corresponding to the selected measurement within the second window. The method may further include correcting, by the configuration system, a validation error of the at least one validation error that corresponds to the selected measurement. The correction may include receiving a selection of a verification error of the at least one verification error within the second window. The correction may also include updating the GUI to include a third window listing at least one correction corresponding to the selected validation error.

In another embodiment, the at least one correction may include updated configuration attributes for the measurement or component. The method may further include receiving, by the configuration system, a selection of a correction from the at least one correction within the third window, updating the configuration to replace the configuration attribute with an updated configuration attribute corresponding to the selected correction, updating the GUI to include the updated configuration attribute within the first window and remove a display of the selected validation error within the second window, and transmitting the updated configuration attribute to the asset monitoring system.

In another embodiment, the GUI may be configured to, upon receiving a second selection of a validation error, navigate the GUI to a portion of the first window that includes configuration attributes corresponding to the selected error. The method may further include receiving, by the configuration system, a second selection, receiving, within a portion of the first window, an input of an updated configuration attribute corresponding to the selected error, updating the configuration to replace the configuration attribute with the updated configuration attribute, updating the GUI to include the updated configuration attribute within the first window and remove the selected validation error from the second window, and transmitting the updated configuration attribute to the asset monitoring system.

In another embodiment, the at least one correction may be disabling the selected configuration attribute, and the method may further include receiving, by the configuration system, a selection of one of the at least one correction within the third window, updating the GUI to remove the selected at least one validation error from the second window, and transmitting information operable to disable the selected configuration attribute to the asset monitoring system.

In another implementation, each of the at least one correction may be associated with a configuration file. The at least one correction may be an updated configuration attribute corresponding to the selected measurement. The method may further include receiving, by the configuration system, a selection of a configuration file in the configuration file list, automatically selecting a correction associated with the selected configuration file from at least one correction, updating the configuration to replace the configuration attribute with an updated configuration attribute corresponding to the selected correction, updating the GUI to include the updated configuration attribute within the first window and remove the selected validation error from the second window, and transmitting the updated configuration attribute to the asset monitoring system.

In another embodiment, the method may further comprise: before updating the configuration, the GUI is updated by the configuration system to include a fourth window displaying the automatically selected corrections and each correction corresponding to the selected validation error. The fourth window may also be configured to receive user input of an updated correction that is different from the automatically selected correction. In the case where no updated correction is received, the selected correction may be an automatically selected correction, and when an updated correction is received, the selected correction may be an updated correction.

In another embodiment, the method may further include receiving user input confirming the displayed correction associated with the selected configuration file prior to updating the configuration of the hardware component.

In another embodiment, the configuration attribute may include at least one of a scale factor, a linear range, a frequency response, or a health limit of a sensor in communication with the asset monitoring system.

In another embodiment, the configuration attribute may include at least one of a measurement type or observation information defining at least a portion of the measurement to be observed.

In another embodiment, the configuration parameters may include at least one set point corresponding to a respective operating parameter measurement determined by the asset configuration system.

In another embodiment, each profile may be associated with a status of an asset. The method may also include receiving, by the configuration system, a rule set, determining a status of the monitored asset based on the rule set, and selecting a configuration file corresponding to the determined status of the asset.

Drawings

These and other features will be more readily understood from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one exemplary embodiment of an operating environment including a configuration system configured to configure an asset monitoring system;

FIG. 2A is a schematic block diagram illustrating one exemplary embodiment of the asset monitoring system of FIG. 1;

FIG. 2B is a table illustrating an exemplary embodiment of a circuit of the asset monitoring system of FIG. 2A;

FIG. 3 is a flow chart illustrating one exemplary embodiment of a method for configuring the asset monitoring system of FIG. 1;

FIG. 4 is a schematic diagram illustrating one exemplary embodiment of a Graphical User Interface (GUI) generated by the configuration system of FIG. 1, the GUI including a navigation window, a configuration window, and an error window;

FIG. 5 illustrates the GUI of FIG. 4 displaying measurements and corresponding configuration attributes within a configuration window;

FIG. 6 illustrates the GUI of FIG. 5 displaying a configuration error corresponding to a selected configuration attribute within an error window;

FIG. 7A illustrates the GUI of FIG. 5 showing a correction window including configuration attribute corrections made in response to selection of an error within the error window;

FIG. 7B illustrates selection of the corrections listed in the correction window of the GUI of FIG. 7A;

FIG. 7C illustrates the removal of selected errors from the error window of the GUI of FIG. 7A in response to selection of a correction listed in the correction window;

FIG. 8 illustrates navigating within the GUI of FIG. 5 to a portion of a configuration window corresponding to an error selected within the error window;

FIG. 9A illustrates the GUI of FIG. 5 displaying a profile menu listing corresponding profiles within an error window;

FIG. 9B illustrates selection of a configuration file in a configuration file menu and selection of a configuration file (e.g., a quick repair button) to implement automatic error correction within the GUI of FIG. 9A; and is also provided with

FIG. 10 illustrates a validation window generated by the configuration system in response to selection to implement automatic error correction within the GUI of FIG. 9B.

It should be noted that the figures are not necessarily drawn to scale. The drawings are intended to depict only typical aspects of the subject matter disclosed herein, and therefore should not be considered as limiting the scope of the disclosure.

Detailed Description

Asset monitoring systems may be designed to measure and analyze various operating parameters of an asset in order to detect incorrect asset operation and predict when damage to the asset may occur. In this way, corrective actions may be taken to control the asset and/or to maintain the asset, thereby avoiding costly asset downtime and repairs. Existing asset monitoring systems may manually configure the asset monitoring system to provide the configuration attributes necessary to perform these functions. However, manual configuration is prone to errors, such as entering incorrect configuration attributes or missing configuration attributes. Furthermore, in some cases, these configuration errors may require a significant amount of time and/or expertise to identify and correct. Accordingly, embodiments of the present disclosure provide systems and methods for improving the configuration of asset monitoring systems. As discussed in more detail below, the configuration system may be used to identify configuration errors and generate a Graphical User Interface (GUI) that facilitates correction of such errors. In one example, the configuration system may determine possible corrections to the selected errors. In another example, the configuration system may recommend one of the possible corrections and use the recommended correction to automatically resolve the error. Advantageously, this may significantly reduce the amount of time and knowledge required to configure the asset monitoring system.

Embodiments of a system and corresponding method for configuring an asset monitoring system are discussed herein. However, embodiments of the present disclosure may be used to configure other systems without limitation.

FIG. 1 is a schematic block diagram illustrating one exemplary embodiment of an operating environment 100 including an asset 102, an asset monitoring system 104, a configuration system 106, a user computing device 110, and a data storage device 112. Configuration system 106 may communicate with asset monitoring system 104, user computing device 110, and data storage device 112 via a network.

Embodiments of the asset 102 may include one or more machines or machine components monitored by the asset monitoring system 104. In certain embodiments, the asset 102 may be a machine that includes one or more components (e.g., rotating components, reciprocating components, and/or stationary asset components). Such components may include, but are not limited to, gears, bearings, shafts, and the like. Examples of machines containing such components may include, but are not limited to, turbomachinery, turbines (e.g., hydro turbines, wind turbines), generators, reciprocating compressors, and the like.

The asset monitoring system 104 may be in communication with one or more sensors 108 configured to generate one or more sensor signals 108s representative of respective operating parameters of the asset 102. The sensor 108 may also be configured to transmit the sensor signal 108s to the asset monitoring system 104 (e.g., via field wiring).

In use, the asset monitoring system 104 may be configured to analyze the received sensor signals 108s and output one or more monitoring signals 104s representative of the respective measurements. In one aspect, the measurement may be a measurement of an operating parameter of the asset. Asset monitoring system 104 may also be configured to analyze the operating parameter measurements to determine the status (e.g., OK, not OK, alert, hazard, etc.) of one or more monitored machines and/or machine components. For example, the operating parameter measurements may be compared to predefined set points or other criteria to determine corresponding alarms. The measured operating parameters, alarms, and/or results from other analysis of the measured operating parameters may be output from the asset monitoring system 104 as the monitoring signal 104s.

Asset monitoring system 104 may require configuration attributes in order to determine operating parameter measurements from received sensor signals 108s and/or analyze operating parameter measurements. Configuration attributes may be managed by configuration system 106. As discussed in more detail below, the configuration system 106 may include one or more processors that receive a configuration from the asset monitoring system 102. The configuration may include at least one configuration attribute corresponding to the measurement determined by asset monitoring system 102. Upon receiving the configuration, the configuration system 106 can generate a Graphical User Interface (GUI) 116 that includes a first window that includes the measured identifier and one or more configuration attributes corresponding to the measurement. The GUI 116 may be output to a display device for displaying the GUI 116. For example, the user computing device 110 may include a display device, and thus the GUI 116 may be transmitted to the user computing device 110 for display.

Configuration system 106 may also be configured to verify the received configuration. For example, the configuration system 106 may receive an operator input 120 (e.g., via the user computing device 110) that includes a selection of measurements within the first window. Configuration system 106 may also compare at least one of the one or more configuration attributes of the selected measurement to a corresponding reference configuration attribute. For example, a reference configuration attribute (e.g., reference configuration signal 112 s) may be retrieved from data storage 112. In the event that at least one configuration attribute does not match its corresponding reference configuration attribute, at least one validation error for the measurement may be determined. Configuration system 106 can update GUI 116 to include verification errors for the selected measurement in the second window.

Configuration system 106 may also be configured to correct the determined validation error. For example, the configuration system 106 may receive an operator input 120 selecting a validation error within a second window of the GUI 116. In response to receiving the selection, configuration system 106 may further update GUI 116 to include displaying at least one corrected third window corresponding to the selected validation error.

As discussed in more detail below, the configuration system may be configured to automatically update the configuration to replace the configuration attributes with updated configuration attributes in accordance with one of the corrections. In further embodiments, the correction may be a correction recommended by a regulatory agency (e.g., manufacturer of the asset monitoring system 104, operator of the asset monitoring system 104, etc.). In this case, GUI 116 may be further updated by configuration system 106 to replace the erroneous configuration properties with the updated configuration properties within the first window. The configuration system 106 may also transmit the updated configuration to the asset monitoring system 104 (e.g., via the updated configuration signal 106 s) for subsequent use.

In this way, the configuration system 106 may provide a variety of benefits. In one aspect, the recommended correction may reflect the current best practice. Thus, the level of domain expertise required to correct verification errors using an embodiment of the configuration system 106 may be reduced. In another aspect, the use of configuration system 106 may automatically detect and resolve verification errors, providing significant time savings and improved configuration consistency as compared to manual detection and resolution of verification errors. Thus, the overall availability and operator experience of the asset monitoring system 104 may be significantly enhanced as compared to asset monitoring systems that do not employ the configuration system 106.

For a better understanding of the embodiments of the configuration system 106, an embodiment of the asset monitoring system 104 in the form of an asset monitoring system 202 is shown and discussed in detail below with reference to FIG. 2. As shown, asset monitoring system 202 includes a base 204 including a backplane 206, and one or more circuits 210. The backplane 206 may be configured to be communicatively coupled with two or more circuits 210 and to receive data from at least one circuit 210 coupled thereto. As described herein, the data transmitted to the backplane 206 may be referred to as monitoring data. In one aspect, the monitoring data may include information contained within the sensor signal 108 s.

For example, the sensor 108 may include a probe, a transducer, and signal conditioning circuitry (not shown). The probe may interact with the asset 102 to obtain measurements of physical phenomena characterizing the operating parameters of the asset 102. The transducer may convert the measurement of the physical phenomenon to an electrical signal (e.g., voltage), and the signal conditioning circuit may condition and/or amplify the electrical signal to generate the sensor signal 108s (e.g., a voltage between a minimum and a maximum). Thus, in one aspect, the sensor signal 108s may comprise a direct or raw measurement made by the sensor transducer. The sensor signal 108s may be an analog signal or a digital signal.

In another aspect, the sensor signal 108s may include an enhanced data set in addition to a direct measurement of the operating parameter. The enhanced data set may include a plurality of measured variables, depending on the type of operating parameter being measured. For example, the asset 102 may be a rotating component, such as a shaft, and the radial vibration may be a variable measured by a sensor 108 in the form of a proximity sensor. In these cases, the enhanced data set may include one or more of gap voltage, 1x filtered amplitude, 2x filtered amplitude, 1x filtered phase, 2x filtered phase, non-1 x amplitude, and maximum axis displacement (Smax). The gap voltage is the voltage output by the probe and represents the physical distance between the asset 102 and the end of the probe. The 1-fold amplitude is the vibration amplitude having the same frequency as the shaft rotation, and the 2-fold amplitude is the vibration amplitude having twice the frequency as the shaft rotation. For example, a rotational speed of 1480 revolutions per minute corresponds to a frequency of 24.66 cycles per second (Hz). The phase is the time delay between vibrations measured at a predetermined measurement position relative to the reference position. Thus, the 1x phase refers to a vibration phase having the same frequency as the shaft rotation, and the 2x phase refers to a vibration phase having a frequency twice that of the shaft rotation. Non-1 x amplitudes refer to all amplitudes except 1x amplitudes. In other embodiments, the enhanced data set may include metadata about one or more components of the sensor 108 (such as the transducer). Examples of metadata may include one or more of a serial number, a version number, an operating temperature, and a health status.

Thus, the monitoring data may include raw measurements characterizing the respective operating parameters of the asset 102. The monitoring data may also include any values, status, and/or annunciation alarms determined based on measured operating parameters of the asset 102 and/or measured variables of the enhanced data set.

In another aspect, the sensor signal 108s may include information other than a direct measurement of the operating parameter. For example, the sensor signals 108s may include metadata about one or more components (such as transducers) of the corresponding sensor 108. Examples of metadata may include, but are not limited to, one or more of a serial number, version number, operating temperature, and health.

The number and type of sensors 108 may be determined by one or more operating parameters intended to be measured. In one aspect, the sensor 108 may take the form of one or more proximity probes for measuring vibration, position, velocity, direction of movement, and eccentricity. In another aspect, the sensor 108 may take the form of one or more accelerometers for measuring seismic vibrations and acceleration. In another aspect, the sensor 108 may take the form of one or more temperature probes or pressure probes for measuring temperature and pressure, respectively. It should be appreciated that the types of sensors 108 and corresponding measured operating parameters discussed above are not exhaustive, and that embodiments of the sensors 108 may include any sensor or combination of sensors suitable for measuring an operating parameter of interest.

Circuitry 210 coupled to the backplane 206 may retrieve the monitoring data from the backplane 206. In certain implementations, the target 206 may be non-magnetized. The passive backplane may include substantially no or no logic circuitry to perform the computing functions. The required arbitration logic may be placed on a daughter card (e.g., one or more of the circuits 210) that is plugged into or otherwise communicatively coupled to the passive backplane.

The circuit 210 may be designed with a generic architecture that may be programmed to perform different predetermined functions of the asset monitoring system 202. The sensor signals 108s received by one or more of the circuits 210 may be transmitted to the backplane 206, and the monitoring data represented by the sensor signals 108s may be accessed by any of the circuits 210. Further, asset monitoring system 202 may be communicatively coupled to multiple bases by a separate backplane 206 (e.g., a logical backplane) of each base 204 forming a common backplane 206'. Thus, the circuit 210 may retrieve the monitoring data from any backplane 206 that forms the common backplane 206' rather than just from the backplane 206 to which they are physically coupled.

An exemplary embodiment of circuit 210 is shown in fig. 2B and discussed in detail below. For example, the circuit 210 may include an input circuit 210i, a processing circuit 210p, an output circuit 210o, and an infrastructure circuit 210n. It should be appreciated that the circuit 210 may also be programmed to perform other functions as desired. Further discussion of circuit 210 may also be found in U.S. patent application Ser. No. 15/947,716, entitled "Gated Asynchronous Multipoint Network Interface Monitoring System," which is incorporated herein by reference in its entirety. Accordingly, the asset monitoring system 202 may be configured to receive the sensor signals 108s and output the monitoring signals 104s to the internal network 220a and the external network 220b in the form of monitoring signals 206s, 208s, respectively.

The internal network 220a may be an in-plant network in communication with the asset control system 212. The asset control system 212 may be configured to provide commands to the asset 102 that are operable to control one or more operating parameters of the asset 102. The internal network 220a may also communicate with other systems, such as computing devices executing configuration software (e.g., the configuration system 106), a human-machine interface (HMI) 216, and/or a customer history database 216.

The external network 220b may be a business network in communication with the diagnostic system 222. The diagnostic system 222 may analyze any data included within the monitoring signals 208s to diagnose improper operation of the asset 102 and/or predict improper operation of the asset 102 before improper operation occurs. Thus, providing the monitoring signal 208s to the external network 220b may facilitate condition monitoring of the asset 102.

As described above, the configuration system 106 may be used to provide configuration information to the asset monitoring system 104. HMI 214 may be one or more computing devices in communication with a user interface device (e.g., a display) to allow an operator of the machine to view measured operating parameters and/or provide instructions to asset control system 212. The asset monitoring system 202 may receive command signals 209s, 211s from the internal network 220a and the external network 220b, respectively, without compromising the security of the asset control system 212.

The circuitry 210 may be combined on one or more backplanes 206 in a variety of ways to form different implementations of the asset monitoring system 202. The number of pedestals 204, input circuits 210i, processing circuits 210p, output circuits 210o, and infrastructure circuits 210n included in a given implementation of asset monitoring system 202 may also vary independently of one another. In some implementations, the asset monitoring system 202 may be in the form of a single base 204 including circuitry 210 configured to provide signal input, signal output, protection monitoring, condition monitoring, and combinations thereof. In other implementations, the asset monitoring system 202 may be in the form of at least two bases 204, and the circuitry 210 configured to perform any combination of signal input, signal output, protection monitoring, and condition monitoring may be distributed between the at least two bases 204. In this way, the input, processing, and output capabilities of the asset monitoring system 202, as well as the physical location of the different circuits 210 of the asset monitoring system 202, may be tailored to a particular monitoring application.

In certain embodiments, the input circuit 210i may be configured to receive the sensor signal 108s, perform signal conditioning on the sensor signal 108s, and output the conditioned sensor signal 108s to the backplane 206. The input circuitry 210i may be decoupled from the processing circuitry 210p, allowing the number of input circuitry 210i of the asset monitoring system 202 to vary independently of the number of processing circuitry 210 p.

The sensor signals 108s may be received from a variety of different types of sensors 108. Examples of sensor types may include, but are not limited to, vibration sensors, temperature sensors (e.g., resistance temperature detectors or RTDs), position sensors, and pressure sensors.

Embodiments of asset monitoring system 202 may include one or more input circuits 210i. As shown in fig. 2A, asset monitoring system 202 includes two input circuits 210i. Each of the input circuits 210i may communicate with a respective sensor 108, 108 'to receive a corresponding sensor signal 108, 108'. For example, the sensor signal 108s may represent first monitoring data (e.g., acquired by the sensor 108) including measurements of a first operating parameter of a first machine component. The sensor signal 108 'may represent second monitoring data (e.g., acquired by the sensor 108') including a measurement of a second operating parameter of a second machine component. In certain embodiments, the first machine component and the second machine component may be the same (e.g., asset 102). In other embodiments, the first machine component and the second machine component may be different (e.g., asset 102 and different asset [ not shown ]). Similarly, in some embodiments, the first operating parameter and the second operating parameter may be the same operating parameter. In one aspect, this configuration may provide redundancy in the event of a failure of one of the sensors 108, 108'. In another aspect, such a configuration may be utilized wherein the desired measurement (e.g., shaft rotational speed) is derived from two sensor measurements coordinated in time (phase). In further embodiments, the first operating parameter and the second operating parameter may be different. While two input circuits 210i have been shown and discussed, other embodiments of the monitoring system may include more or fewer input circuits.

Different types of sensors 108 may generate sensor signals 108s in different formats, and the input circuit 210i may be programmed to perform signal conditioning appropriate for the different sensor signals 108s before transmitting the conditioned sensor signals to the backplane 206. For example, the sensor signal 108s generated from the position sensor may be received by the position input circuit 250. The sensor signal 108s generated by the vibration sensor may be received by the vibration input circuit 252. The sensor signal 108s generated by the temperature sensor may be received by the temperature input circuit 254. The sensor signal 108s generated by the pressure sensor may be received by the pressure input circuit 256.

In other embodiments, the input circuit 210i may be in the form of a discrete contact circuit 260. The discrete contact circuit 260 may include a pair of contacts that may be closed by an external switch or relay. The pair of contacts may be closed by the asset control system 212 or by an operator of the asset control system 212 closing a switch. Discrete contact circuitry 260 may be used to alter the behavior of asset monitoring system 202. Examples of behavior changes may include, but are not limited to, different machine operating modes, causing asset monitoring system 202 to suppress alarm determination, and resetting alarm conditions.

While the asset monitoring system 104 may include discrete contacts, it may lack specificity. For example, the change implemented by closing a discrete contact in the asset monitoring system 104 may be implemented on all alarms generated by the asset monitoring system 104. In contrast, because the discrete contact circuit 260 of the asset monitoring system 202 may be separate from the protection processing circuit 264, the discrete contact circuit 260 may be configured to implement only selected alert determinations and/or resets alert states, or to implement all alerts.

In further embodiments, input circuit 210i may be in the form of digital data stream input circuit 262. For example, the digital data stream input circuitry 262 may be configured to receive digital data streams from the sensors 108, the asset control system 212, and/or the trusted third party system, instead of analog data streams (e.g., from the sensors 108).

Processing circuitry 210P may be configured to retrieve any data from backplane 206, analyze the retrieved operating parameters, and output the results of such analysis. In certain embodiments, the processing circuitry 210p may be configured to perform protection functions and may be referred to herein as protection processing circuitry 264. In other embodiments, the processing circuit 210p may be configured to retrieve selected data from the backplane 206 and transmit the retrieved information to the diagnostic system 222 for performing diagnostic and/or prognostic functions (e.g., condition monitoring), and may be referred to herein as the condition processing circuit 266.

The number of processing circuits 210p and input circuits 210i included in a given implementation of asset monitoring system 202 may vary independently of one another. In certain embodiments, the processing circuitry 210P may be added to or removed from the backplane 206 to customize the amount of computing resources available for protection monitoring and/or condition monitoring. In other embodiments, a given processing circuit 210P may be replaced with another processing circuit 210P having more or less computing power.

Protection processing circuitry 264 and condition processing circuitry 266 are discussed below with reference to different functions. However, the protection processing circuitry 264 may be programmed to perform any of the functions of the condition processing circuitry 266. The condition processing circuitry 266 may be programmed to perform the functions of the protection processing circuitry 264 in addition to transmitting data to the backplane 206 and providing local storage. The ability to inhibit the transmission of data by the condition processing circuitry 266 to the backplane 206 may inhibit unauthorized intrusion and facilitate protection of the internal network 220a and the asset control system 212.

The protection processing circuitry 264 may be configured to retrieve selected monitoring data from the backplane 206 in response to receiving the protection command. For example, one or more protection commands can be transmitted to the protection processing circuitry 264 in the form of protection command signals 209s received from the internal network 220a (e.g., from an operator of the asset control system 212). The selected monitoring data may include at least a portion of the monitoring data transmitted to the backplane 206. The monitoring data transmitted to the backplane may be received from the input circuit 210i or another protection processing circuit 264. The protection processing circuitry 264 may also be configured to determine a value representative of the selected monitoring data and transmit the determined value as additional monitoring data to the backplane 206.

The protection processing circuit 264 may be configured to determine the status of the selected monitoring data based on the determined value, another determined value retrieved from the backplane 206 (e.g., from another protection processing circuit 264), and a comparison of a combination thereof to one or more predetermined set points. The predetermined set points may correspond to respective alarm conditions (e.g., alert conditions, dangerous conditions, etc.). Continuing with the above example, where the determined value is the amplitude of the radial vibration, the one or more set points may include a warning set point, a hazard set point greater than the warning set point, and combinations thereof. In certain embodiments, a single set point may be employed. Assuming that warning and hazard set points are used, if the radial amplitude value is less than the warning set point, the state of the radial amplitude may be determined to be "OK". If the radial amplitude value is greater than or equal to the alert set point, the state of the radial amplitude may be determined to be "alert". If the radial amplitude value is greater than the hazard set point, the state of the operating parameter may be determined to be "hazard". After determining the status of the selected monitoring data in this manner, the protection processing circuitry 264 may transmit the determined status to the backplane 206. The condition processing circuit 266 may be configured to retrieve selected monitoring data from the backplane 206 and provide the retrieved monitoring data to the external network 220b for use by the diagnostic system 222.

In some embodiments, in response to receiving the adjustment command, the condition processing circuit 266 may retrieve the selected monitoring data. For example, one or more adjustment commands can be transmitted to the condition processing circuit 266 in the form of an adjustment command signal 211s, which can be received from the external network 220 b. (e.g., from an operator of diagnostic system 222). In turn, diagnostic system 222 may utilize the retrieved monitoring data to determine a status and/or cause of the alarm condition. Alternatively or in addition, diagnostic system 222 may also employ the retrieved monitoring data to predict the development of a status and/or alarm condition prior to the occurrence of the status and/or alarm condition. In further embodiments, diagnostic system 222 may store the retrieved monitoring data for subsequent analysis. In further embodiments, diagnostic system 222 may transmit the retrieved monitoring data to another computing device for analysis.

In further embodiments, the condition processing circuit 266 may retrieve selected monitoring data from the backplane 206 based on detection of a predetermined condition. For example, the condition processing circuit 266 may retrieve and view the state generated by the protection processing circuit 264 to identify a state that matches the predetermined state. The identified state may also include a state time that characterizes a time when the state was determined. Upon identifying a match, the condition processing circuit 266 may retrieve selected monitoring data including operating parameter measurements corresponding to predetermined duration states before and/or after the state time. In this way, diagnostic system 222 may be provided with operating parameter information related to the cause of the determined state. The predetermined status and the selected monitoring data may be included in one or more adjustment commands.

The output circuit 210o may be configured to obtain any monitoring data included on the backplane 206 in response to receiving an output command (e.g., included in one or more protection command signals 209s received from the internal network 220 a). The output circuit 210o may also output the retrieved monitoring data to the internal network 220a in the form of the monitoring signal 206s. Examples of monitoring data retrieved by output circuit 210o may include, but are not limited to, operating parameter measurements, determined values, variables of the enhanced data set, status, and alarms.

In one aspect, the output circuit 210o may be in the form of a proportional output circuit 270. The proportional output circuit 270 may be configured to output the monitor signal 206s in the form of a process control signal. The process control signal may be proportional to a process variable, such as a direct measurement or a variable of the enhanced data set, as compared to a predetermined scale. For example, the current output may be a 4-20mA output. The process control signals may be provided to the asset control system 212 directly or via the internal network 110a to facilitate control of the operating parameters of the asset 102. The process variable included in the process control signal may be specified by the protection command signal 209 s.

In further embodiments, the output circuit 210o may be in the form of one or more relay circuits 272, the relay circuits 272 configured to retrieve selected status data from the backplane 206 and actuate to annunciate an alarm based on the received alarm status. The annunciation alarm can be output in the form of an alarm signal. In one example, the relay may be actuated based on a single state. In another example, the relay may be actuated based on a predetermined boolean expression (e.g., and or voting) that combines two or more states. The alert signal may be provided to the asset control system 212 via the internal network 220a or directly to the asset control system 212 to facilitate control of the operating parameters of the asset 102. For example, the asset control system 212 may shut down operation of the asset 102 in response to receiving the alert signal. The selected status data and logic for actuating the relay may be specified by the protection command signal 209 s.

In other embodiments, the output circuit 210o may be in the form of at least one communication interface circuit 274. The communication interface circuit 274 may be configured to retrieve the selected monitoring data from the backplane 206 in response to receiving the protection command signal 209 s. The selected monitoring data may include one or more of a measured operating parameter, a measured variable of the enhanced data set, a determined state, and a determined alarm. The retrieved data can be transmitted to the internal network 220a as one or more return signals for use by the asset control system 212 (e.g., for process control), the HMI 214 (e.g., for display to an operator), and/or stored by the history database 216.

Infrastructure circuitry 210n may be configured to perform functions required for operation of asset monitoring system 202. In one aspect, the infrastructure circuit 210n may take the form of a system interface circuit 276. The system interface circuit 276 may serve as an access point for transmitting the protection command signal 209s from the internal network 110a to the diagnostic system 222, thereby facilitating configuration of the circuitry involved in protection monitoring (e.g., protection processing circuit 264, output circuit 210 i). The protection command signal 209s may include one or more signals including any one of the following in any combination: the selected monitoring data for each of the protection processing circuitry 264 and the output circuitry 210i for retrieval and/or output, the alarm set point of the protection processing circuitry 264, and logic for annunciating the relay through the relay output circuitry 272.

In another aspect, the infrastructure circuit 210n may take the form of a power input circuit 280. The power input circuit 280 may provide the ability to connect one or more power sources to the asset monitoring system 202.

In another aspect, the infrastructure circuit 210n may take the form of a bridge circuit 282. The bridge circuit 282 may provide the ability to connect together the backplanes 206 of two or more pedestals 204 and form a common backplane 206' to communicate between the two.

With a more complete understanding of the asset monitoring system 104, the steering configuration system 106 will now be discussed. An exemplary embodiment of a method 300 of configuring an asset monitoring system 104 with a configuration system 106 is shown in fig. 3. As shown, the method 300 includes operations 302 through 312. However, it will be appreciated that alternative embodiments of the method may include more or fewer operations than shown in FIG. 3, and/or may be performed in a different order than shown in FIG. 3. Exemplary embodiments of the GUI 116 generated by the configuration system 106 are further illustrated in fig. 4-10.

In operation 302, a configuration may be received by one or more processors (e.g., configuration system 106). The configuration may include at least one configuration attribute corresponding to the measurement determined by the asset monitoring system 104. As discussed in more detail below, the configuration system 106 may receive from at least one of the data storage 112 or the asset monitoring system 104 in response to a query.

In some embodiments, the configuration attributes may relate to hardware components of the asset monitoring system 104 used to determine the measurements. For example, hardware components of asset monitoring system 104 may include, but are not limited to, circuitry 210 (e.g., input circuitry 210i, processing circuitry 210p, output circuitry 210, and/or infrastructure circuitry 210 n). In other embodiments, the configuration attributes may relate to logical processes (e.g., calculations, analyses, etc.) performed by the asset monitoring system 104 to determine the measurements.

In one embodiment, the configuration attribute may be one or more sensor information. The sensor information may be information about hardware (e.g., the sensor 108, the output of the sensor signal 108 s) and/or calculations (e.g., algorithms or other logical processes) performed to determine the operating parameters of the asset 102 from the sensor signal 108 s. That is, the sensor information may be related to obtaining an operating parameter measurement. Examples may include, but are not limited to:

scaling factor-the measured operating parameter and the sensor signal 108 (e.g., voltage)

And between the transitions. For example, the proximity transducer may employ a scaling factor that sets the output voltage per unit distance.

Linear range—a range in which the sensor signal 108 (sensor output) is approximately linear with respect to the measured operating parameter (sensor input). In some cases, it may be preferable to operate within a linear range. For example, in the context of a sensor having an output range between 0-20V, the linear range may be 5-15V.

Frequency response—the speed at which the sensor can respond to changes in the measured operating parameter.

Health limit—the range of sensor signals 108s corresponding to the state of the sensor 108 corresponding to the received sensor signals 108 s. Examples of such states may include, but are not limited to, sensor off or on, sensor within or outside of a linear range, sensor present or absent, and the like.

Measurement calculation—any information (e.g., mathematical formulas) for determining an operating parameter measurement from the sensor signal 108 s.

In another embodiment, the configuration attribute may be one or more measurement information. The measurement information may be used to determine how to use the operating parameter measurements. Examples may include, but are not limited to:

measurement type-confirm what the operating parameter measurement is. Examples may include, but are not limited to, offset, gap, bandpass, NX, synchronization, crest factor, peak-to-peak, and the like.

Observation information—given a measurement type, the observation information may define at least a portion of the measurement to be observed. For example, in the context of bandpass, the observed information may define signal frequencies that are allowed to pass and signal frequencies that are not allowed to pass and are rejected.

In one embodiment, the configuration attribute may be a set point. As described above, the asset monitoring system 104 may be configured to determine a condition (e.g., an alarm condition, a warning condition, etc.) based on a comparison of the operating parameter measurements to one or more set points. For example, an alarm condition may be determined when the operating parameter measurement is one or more of above a set point, below a set point, or outside a set point range.

In further embodiments, the configuration attribute may be a status of the asset. Examples of asset states may include, but are not limited to, modes of operation of the asset 102, such as start-up, shutdown, and steady state. The configuration attributes may also include one or more asset state configuration attributes that may be used to determine asset states. For example, in the context of a rotating asset (e.g., a rotor), an asset state configuration attribute may be a range of rotational speeds of the asset 102 that define the respective asset state.

In further embodiments, the configuration attribute may be a system configuration associated with the asset monitoring system 104 itself. The system configuration may take a variety of forms. In one example, the system configuration may involve timing of the asset monitoring system 104. For example, the asset monitoring system 104 may employ a network resource (e.g., a time server) to time in comparison to a local clock maintained by the asset monitoring system 104 (e.g., one or more processors of the asset monitoring system 104). Thus, the configuration attribute for timing may be the network address of the time server. In another example, the system configuration may be a plurality of networks in communication with the asset monitoring system 104.

In operation 304, the configuration system may generate the GUI 116. An example of GUI 116 is shown in fig. 4. As shown, GUI 116 may include a navigation window 400, a configuration window 402, and an error window 404.

The navigation window 400 may include a hierarchical list 406 of the respective assets 102 monitored by the asset monitoring system 104. As shown, the hierarchical list 406 includes a plurality of levels, such as a system (asset monitoring system 104) level, a rack level, and a aisle level. The GUI 116 may be configured to receive an operator selection (e.g., operator input 120) of a level of the hierarchical list 406.

In one embodiment, the lowest level of the hierarchical list 406 may be a channel level. The channels may be respective ones of the sensors 108 of the asset monitoring system 104. Thus, the selection of a channel at the channel level may include an operating parameter measurement determined from the sensor signal 108s acquired by the selected channel.

The next higher level of the hierarchical list 406 may be the module level. The modules may be respective ones of the circuits 210 of the asset monitoring system 104 and, as described above, may be in communication with one or more channels. Thus, selection of a module at the module level may include an operating parameter measurement determined by the selected module and thus a logic process performed based on the corresponding channel.

The next higher level of the hierarchical list 406 may be the rack level. The chassis may be a physical frame that houses at least a portion of the hardware modules (e.g., circuitry 210) of the asset monitoring system 104. Thus, the selection of a rack at the rack level may include an operational parameter measurement determined by a module of the selected rack and a logic process performed thereby.

The highest level of the hierarchical list 406 may be the system level. Thus, the system level selection includes all measurements determined by the asset monitoring system 104.

Configuration system 106 can determine measurements associated with the selected hierarchical level. For example, associations between respective levels of the hierarchical list 406 and corresponding measurements may be maintained by the data store 112 (e.g., within a database). Thus, in response to receiving an operator selection from the hierarchical list 406, the configuration system 106 may transmit a query to the data store 112 regarding measurements corresponding to the selection from the hierarchical list 406, and receive a response from the data store regarding measurements corresponding to the selection from the hierarchical list.

Once configuration system 106 determines the operating parameter measurements corresponding to the selections from hierarchy list 406, it may further determine at least one configuration attribute corresponding to the respective measurements. For example, associations between respective ones of the measurements and corresponding configuration attributes may be maintained by data store 112 (e.g., within a database). Thus, in response to receiving an operator selection from the hierarchical list 406, the configuration system 106 may further transmit a query to the data store 112 regarding the configuration attributes corresponding to the respective measurements, and receive a response from the data store regarding the configuration attributes corresponding to the respective measurements.

As shown in fig. 4-5, the configuration system 106 may further update the GUI 116 to include a first window (e.g., the configuration window 402) that includes at least the identifier of the measurement and one or more configuration attributes corresponding to the measurement. For example, the at least one measurement may be a measurement corresponding to a selection from the hierarchical list 406. Examples of measurement identifiers include the name of the measurement. Examples of the at least one configuration attribute may take a variety of forms, as will be discussed in more detail below.

Optionally, other information about the measurements may be included within the configuration window 402. Examples may include, but are not limited to, measurement type (e.g., status measurement, relay channel, temperature, bandpass, bias, vector, velocity, etc.), channel name, and channel type (e.g., relay channel, temperature channel, radial vibration channel, velocity channel, etc.). In some embodiments, the measurement name and channel name may be the same as the measurement type and channel type, respectively.

Optionally, other information regarding the configuration of asset monitoring system 104 may be listed within configuration window 402. For example, the chassis may include a plurality of slots in which corresponding ones of the circuits 210 are positioned. The slot in which the circuit 210 that determines the corresponding operating parameter measurement is located may be listed in the entry corresponding to the measurement.

In operation 306, the GUI 116 may be output by the configuration system 106 to a display device for displaying the GUI 116. For example, the configuration system 106 may output the GUI 116 to the user computing device 112, and the GUI 116 may be displayed on a display device in communication with the user computing device 112.

In operation 310, the configuration system 106 may verify the received configuration. For example, the configuration system 106 may receive a selection of measurements within the configuration window 402. As shown in fig. 6, measurement 1 is selected.

Configuration system 106 may further compare a configuration attribute of the one or more configuration attributes to a corresponding reference configuration attribute. For example, the data store 112 may maintain a plurality of reference configuration attributes associated with respective configuration attributes, and the configuration system 106 may retrieve the reference configuration attributes from the data store in response to a query. Configuration system 106 can determine at least one validation error when a configuration attribute of the one or more configuration attributes does not satisfy its corresponding reference configuration attribute. In some embodiments, such satisfaction may be achieved when a configuration attribute of the one or more configuration attributes matches its corresponding reference configuration attribute.

In one aspect, the reference configuration attribute may include a range of values. Matching may occur when the value of the configuration attribute is within or outside of a range of values, as the case may be. As described above, the configuration attributes of the sensor 108 may include a scale factor. In this case, the reference configuration attribute may be a linear range. The match may be determined when the scale factor is within the linear range and not determined when the scale factor is outside the linear range.

In another aspect, the reference configuration attribute may be a single value. Matching may occur when the value of the configuration attribute is higher, lower, or equal to the reference configuration attribute, as the case may be. As described above, the configuration attributes of the sensor 108 may include set points. In this case, the reference configuration attribute may be a full scale range of the sensor 108. The match may be determined when the set point is within the full-scale range and not determined when the set point is outside the full-scale range.

In further aspects, the reference configuration attribute may be a particular type of value (e.g., an integer). When the values of the configuration attributes take the same numerical type as the reference configuration attributes, a match may be determined. In contrast, when the value of the configuration attribute is not the same number type as the reference configuration attribute, the match is not determined.

In further aspects, the reference configuration attribute and the configuration attribute may each be a boolean value (e.g., 0 or 1, true or false, etc.). When the boolean values of the configuration attribute and the reference configuration attribute are equal, a match may be determined. In contrast, when the boolean values of the configuration attribute and the reference configuration attribute are not equal, a match is not determined.

In some embodiments, configuration attributes may be specified as desired or alternatively. In one aspect, when there is no value of the desired configuration attribute in the received configuration, a match is not determined. When there is no value of the desired configuration attribute in the received configuration, a match may be determined. Configuration attributes may be specified as needed or alternatively for the measurements.

In other embodiments, configuration system 106 may detect various other verification errors. Examples may include, but are not limited to:

there are no required components listed within the hierarchical list 406 (e.g., racks, power input modules (e.g., power inputs 280)).

List the required components in slots of the chassis other than the predetermined slot (e.g., the chassis in slots other than the predetermined first slot, the power input 280 in slots other than the predetermined second slot).

Two or more components are listed in the same slot of the rack.

When only one of the components should be present in the rack (e.g., system interface module 276)

Two or more components are listed.

List channels that do not have associated modules (e.g., processing circuitry 210 p).

List modules that do not have associated channels.

The listed channels are not recommended for the corresponding measurements (e.g., accelerometer channels are indicated for a).

Duplicate naming of the individual operating parameter measurements.

One or more invalid characters are used in any information presented in the GUI 116.

It will be appreciated that the verification errors discussed above are given by way of example only. Other criteria for determining whether there is a match and whether a validation error is determined may be employed without limitation.

The configuration system 106 may be further configured to update the GUI 116 to include at least one validation error corresponding to the selected measurement in a second window (e.g., the error window 404). As shown in fig. 6, each of the at least one validation error may be displayed as a separate entry of the list within the GUI 116. Each entry may include a name of the validation error and a description of the validation error. In further embodiments, the entry may include other information about the listed validation errors. In one aspect, the additional information may include selected paths from the hierarchical list 406 (e.g., rack > module > channel > measurements) corresponding to the selected measurements. In another embodiment, the additional information may include a configuration file corresponding to the validation error, as discussed in more detail below.

In operation 312, the configuration system 106 may be configured to correct one or more validation errors corresponding to the selected measurements. As shown in fig. 6, configuration system 106 may receive a selection (e.g., operator input 120) of a validation error of at least one validation error within error window 404 via user computing device 110.

In response to receiving the verification error selection, the configuration system 106 may be configured to determine at least one corresponding correction. For example, the data store 112 can include data that associates corresponding verification errors with corrections. Accordingly, configuration system 106 may query data store 112 to receive one or more corrections corresponding to the selected validation errors.

Depending on the nature of the corresponding validation error, at least one embodiment of the correction may take a variety of forms. As described above, a validation error may be a lack of match between a value or range of values of a configuration attribute and its corresponding reference configuration attribute. In these cases, the at least one correction may be an updated configuration attribute comprising a value or range of values that matches the reference configuration attribute.

As further shown in fig. 7A, the configuration system 106 may update the GUI 116 to include a third window (e.g., correction window 410) in response to receiving the first selection of the validation error within the error window 404. The first selection may be a predetermined interaction between the operator and the verification errors listed within the error window 404. Examples may include, but are not limited to, clicking a right mouse button, clicking a left mouse button, double clicking a mouse (e.g., double clicking a right mouse button), and so forth. It will be appreciated that in the context of a touch sensitive display device, a mouse click may be used interchangeably with a tap on the screen of the display.

Correction window 410 may include at least one correction corresponding to the selected validation error. As shown, at least one correction may be displayed as a separate entry of the list. Each entry may include a description of the listed corrections. In further embodiments, the entry may include other information about the listed validation errors without limitation.

In some embodiments, the at least one correction may be implemented by the configuration system 106 after receiving the first selection of a correction of the at least one correction. Continuing with the example above, the at least one correction may be an updated value/range of attribute 1 of measurement 1 having an updated value/range. As shown in fig. 7B, the configuration system 106 may update the GUI 116 to display the updated configuration properties (values/ranges) in the appropriate fields of the configuration window 402. After selecting the correction, the configuration system 106 may further update the GUI 116 to remove the display of the selected validation error (e.g., error 1) from the error window, as shown in fig. 7C. Configuration system 106 may additionally transmit the updated configuration attributes to asset monitoring system 104.

In other embodiments, the configuration system 106 may be configured for manual input of at least one correction (e.g., via the user computing device 110). For example, the GUI 116 may be configured to receive a second selection of the validation error that is different from the first selection. The second selection may be a predetermined interaction between the operator and the verification errors listed within the error window 404. Examples of the second selection may include, but are not limited to, clicking a right mouse button, clicking a left mouse button, double clicking a mouse (e.g., double clicking a right mouse button), and so forth. It will be appreciated that in the context of a touch sensitive display device, a mouse click may be used interchangeably with a tap on the screen of the display.

In contrast to the first selection, the second selection may result in navigating within the GUI 116 to a portion of the GUI 116 that includes configuration properties corresponding to the selected error. For example, navigation may highlight a field within configuration window 402 that includes a configuration attribute corresponding to the selected error (e.g., designate the highlighted field as an active field for receiving input). For example, as shown in FIG. 8, the navigation highlights the field corresponding to configuration attribute 1 of measurement 1. Following this navigation, configuration system 106 may also be configured to receive input of updated configuration attributes corresponding to the selected error within the highlighting field.

Advantageously, the ability to navigate in this manner may provide significant time savings and improved user experience. Notably, the operator is spared the trouble of manually looking up and navigating to fields, which can be particularly troublesome when the operator is required to correct multiple verification errors.

After receiving the correction within the highlighting field, the correction may be implemented by the configuration system 106. Continuing with the example above, the correction may be an updated value/range of attribute 1 of measurement 1 with an updated value/range. As described above, the configuration system 106 may update the GUI 116 to display the updated configuration properties (values/ranges) in the highlighting field of the configuration window 402, as shown in fig. 7B. After manually entering the correction, the configuration system 106 may further update the GUI 116 to remove the display of the selected validation error (e.g., error 1) from the error window, as shown in fig. 7C. Configuration system 106 may additionally transmit the updated configuration attributes to asset monitoring system 104.

It will be appreciated that in some embodiments, at least one correction may include disabling selected configuration attributes. Disabling may mean maintaining the original configuration properties but removing the configuration properties from runtime processing (e.g., analysis or other calculations to determine measurements). The option to disable the selected configuration attribute may be used for measurements that may employ but do not require the disabled configuration attribute. In one aspect, the operator may disable the selected configuration attribute via one of the corrections within the correction window, as shown in fig. 7A. After selecting this correction, configuration system 106 may further update GUI 116 to remove the display of the selected validation error from the error window, as shown in fig. 7C. Configuration system 106 may additionally transmit information to asset monitoring system 104 operable to disable the updated configuration attributes.

In some embodiments, it may be desirable to automatically correct verification errors in order to save time and improve operator experience. Thus, in some implementations, the configuration system 106 may include a user interface object 412 that automatically implements verification error correction (e.g., a "quick fix" button 412) upon selection. In some implementations, selection of the quick repair button 412 may cause the configuration to implement correction only for verification errors selected within the error window. In further embodiments, the quick fix button may be disabled when no validation error is selected within the error window, thereby preventing the configuration system from implementing a correction via selection of the quick fix button. In an alternative implementation, a quick fix button may be enabled when no validation errors are selected within the error window, and when selected, the button may cause the configuration system to implement correction of each of the validation errors listed in the error window.

In the case where only a single correction is determined for a validation error, configuration system 106 can easily implement the single correction when the quick fix button is selected. However, where multiple corrections are determined for a given validation error, configuration system 106 may need a mechanism for identifying which correction to implement from a list of multiple correction options. Thus, the determined corrected embodiments may be further associated with a configuration file.

As shown in fig. 9A, the GUI 116 generated by the configuration system 106 may also include a user interface object 414 that allows a configuration file to be selected from a menu (e.g., a configuration file menu) listing a plurality of configuration files. As shown, profile menu 414 may be positioned within error window 404. However, in alternative implementations, the profile menu may be located in another location within the GUI. In use, prior to selecting quick repair button 412, configuration system 106 may receive a profile selection within the GUI (e.g., via a selection from profile menu 414).

For a given validation error, when quick repair button 142 is selected, configuration system 106 may automatically select a correction corresponding to the selected configuration file from the determined corrections for the selected validation error, as shown in FIG. 9B. That is, the automatically selected correction is the default correction for the selected configuration file. As described above, the determined correction may include updated configuration attributes. Thus, in some embodiments, the configuration may be updated to replace the configuration attributes with updated configuration attributes corresponding to the automatically selected corrections.

After selecting quick repair button 412, configuration system 106 may further update GUI 116 to display the updated configuration properties (values/ranges) in configuration window 402, as discussed above and shown in fig. 7B. Configuration system 106 may further update GUI 116 to remove the display of the selected validation error from error window 406, as discussed above and shown in fig. 7C. Configuration system 106 may additionally transmit the updated configuration attributes to asset monitoring system 104.

As described above, the asset 102 may operate in various states (e.g., start-up, shut-down, steady state, etc.). It will be appreciated that the recommendation correction defined by the corresponding profile may vary depending on the asset status. Thus, in some embodiments, each profile may be further associated with an asset status. When performing automatic correction (e.g., selecting quick fix button 412), configuration system 106 may select a configuration file based further on the asset status. For example, the configuration system may receive a rule set and determine an asset status based on the rule set. For example, the rule set may specify a rotational speed associated with each of the asset states. Thus, the asset status may be determined from a measurement of the asset rotation speed. Once the asset status is determined, the configuration system may further select a configuration file corresponding to the determined asset status.

In certain implementations, while it may be desirable to use the quick fix button 412 to automatically implement verification error correction, it may also be beneficial for the operator to check and approve default correction prior to implementation. Thus, in one embodiment, after selecting quick fix button 412, configuration system 106 may be configured to update GUI 116 to include confirmation window 1000. The validation window 1000 may include a list of validation errors to be corrected in response to selection of the quick repair button 412, corrections determined for each validation error, and a selection area 1002 that allows selection of the corresponding correction. The validation window 1100 may include corrections (e.g., automatically selected default corrections) for each validation error associated with the selected configuration file within the selection area 1002.

In the event that the operator is satisfied with the selected correction, the operator may approve the selected correction without change (e.g., select the "OK" button without change within the selection area). Alternatively, if the operator is not satisfied with one or more of the selected corrections, the operator may approve the change to the correction for one or more of the verification errors (e.g., select the "OK" button after the change is made within the selection area). That is, in the event that the operator does not make a change within the confirmation window 1000, the selected correction implemented by the configuration system 106 may be the default correction that is automatically selected. Alternatively, where the operator updates the correction associated with the validation error within the validation window 1000, the selected correction implemented by the configuration system 106 for the validation error may be an updated correction.

In some embodiments, when an operator changes one or more corrections from a default selection, the configuration system 106 may record the operator's authorization for the change. Recording operator authorization may include, but is not limited to, recording an operator's unique identifier (e.g., operator name, operator number, etc.), correction after the change, date/time the change was authorized, etc. Such recorded information may be transmitted from the configuration system 106 to the asset monitoring system and/or data storage 112 for storage and subsequent retrieval.

As described above, the default selections may represent recommended corrections determined by the manufacturer and/or operator of the asset monitoring system 104. Thus, the operator should only authorize the change to the default selection if warranted. By recording when an operator changes one or more corrections in the default selections, an authorized operator can be identified in the audit with relative ease in the event that the change is found to be erroneous or unsuitable.

As a non-limiting example, exemplary technical effects of the methods, systems, and apparatus described herein include improved configurations of asset monitoring systems. Configuration errors and possible corrections can be quickly identified. Recommendation corrections reflecting domain knowledge and best practices may be automatically implemented to address configuration errors. Such automation may significantly reduce the amount of time required to configure the asset monitoring system, as it may help operators resolve errors that they would otherwise take more time to manually resolve. Furthermore, the configuration best practices may be coded, thereby reducing the level of domain knowledge required by the operator to resolve configuration errors.

Certain exemplary embodiments are described to provide an overall understanding of the principles of the structure, function, manufacture, and use of the systems, devices, and methods disclosed herein. One or more examples of these embodiments have been illustrated in the accompanying drawings. Those skilled in the art will understand that the systems, devices and methods specifically described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments and that the scope of the present invention is defined solely by the claims. The features illustrated or described in connection with one exemplary embodiment may be combined with the features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention. Furthermore, in this disclosure, similarly-named components of an embodiment generally have similar features, and thus, within a particular embodiment, each feature of each similarly-named component is not necessarily fully set forth.

The subject matter described herein may be implemented in analog electronic circuitry, digital electronic circuitry, and/or computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described herein may be implemented as one or more computer program products, such as one or more computer programs tangibly embodied in an information carrier (e.g., in a machine-readable storage device), or in a propagated signal, for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). A computer program (also known as a program, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program does not necessarily correspond to a file. A program may be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification, including method steps of the subject matter described herein, can be performed by one or more programmable processors executing one or more computer programs to perform functions of the subject matter described herein by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus of the subject matter described herein may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from and/or transfer data to, one or more mass storage devices for storing data (e.g., magnetic, magneto-optical disks, or optical disks). Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical discs; and optical discs (e.g., CD and DVD discs). The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user. For example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user may be received in any form, including acoustic, speech, or tactile input.

The techniques described herein may be implemented using one or more modules. As used herein, the term "module" refers to computing software, firmware, hardware, and/or various combinations thereof. However, at a minimum, a module should not be construed as software (i.e., the module itself is not software) that is not implemented on hardware, firmware, or recorded on a non-transitory processor-readable storage medium. In practice, a "module" will be construed to always include at least some physical non-transitory hardware, such as a processor or a portion of a computer. Two different modules may share the same physical hardware (e.g., two different modules may use the same processor and network interface). The modules described herein may be combined, integrated, separated, and/or duplicated to support various applications. Additionally, functions described herein as being performed at a particular module may be performed at one or more other modules and/or by one or more other devices instead of or in addition to functions performed at a particular module. Further, modules may be implemented across multiple devices and/or other components, either locally or remotely relative to one another. In addition, modules may be moved from one device and added to another device, and/or may be included in both devices.

The subject matter described herein may be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), such as the internet.

Approximating language, as used herein throughout the specification and claims, may be applied to modify any quantitative representation that could vary without resulting in a change in the basic function to which it is related. Accordingly, values modified by one or more terms such as "about," "approximately," and "substantially" should not be limited to the precise values specified. In at least some cases, the approximating language may correspond to the precision of an instrument for measuring the value. Here and throughout the specification and claims, range limitations may be combined and/or interchanged, such ranges are identified and include all the sub-ranges contained therein unless context or language indicates otherwise.

Based on the above embodiments, one of ordinary skill in the art will appreciate additional features and advantages of the invention. Accordingly, the application is not to be limited by what has been particularly shown and described, except as indicated by the appended claims. All publications and references cited herein are expressly incorporated by reference in their entirety.

Claims

1. A method, the method comprising:

receiving, by a configuration system comprising one or more processors, a configuration comprising at least one configuration attribute, the at least one configuration attribute corresponding to a measurement determined by an asset monitoring system configured to monitor an asset;

generating, by the configuration system, a Graphical User Interface (GUI), the GUI comprising a first window comprising an identifier of the measurement and one or more configuration attributes corresponding to the measurement;

providing, by the configuration system, the GUI to a display device to display the GUI;

validating, by the configuration system, the received configuration, comprising:

receiving a selection of measurements within the first window of the GUI;

comparing a configuration attribute of the one or more configuration attributes with a corresponding reference configuration attribute; and

Determining at least one validation error for the selected measurement when a configuration attribute of the one or more configuration attributes does not satisfy its corresponding reference configuration attribute;

updating the GUI to include the at least one validation error corresponding to the selected measurement within a second window; and

determining, by the configuration system, a validation error of the at least one validation error that corresponds to the selected measurement by:

receiving a selection of a validation error from among the at least one validation error within the second window; and

a third window is provided within the GUI listing at least one correction corresponding to the selected validation error.

2. The method of the preceding claim, wherein the at least one correction comprises updated configuration attributes for the measurement or component, and wherein the method further comprises, by the configuration system:

receiving a selection of a correction from among the at least one correction within the third window;

updating the configuration to replace the configuration attribute with an updated configuration attribute corresponding to the selected correction;

updating the GUI to include the updated configuration properties within the first window and remove display of the selected validation error within the second window; and

Transmitting the updated configuration attributes to the asset monitoring system.

3. The method of any of the preceding claims, wherein the GUI is configured to provide, upon receiving a second selection of a validation error, a portion of the first window in the GUI that includes the configuration attribute corresponding to the selected error, and wherein the method further comprises, by the configuration system:

receiving the second selection;

receiving input of updated configuration attributes corresponding to the selected error within the portion of the first window;

updating the configuration to replace the configuration attribute with the updated configuration attribute;

updating the GUI to include the updated configuration properties within the first window and remove the selected validation errors from the second window; and

4. The method of any of the preceding claims, wherein the at least one correction disables the selected configuration attribute, and wherein the method further comprises, by the configuration system:

receiving a selection of one of the at least one correction within the third window;

Updating the GUI to remove the selected at least one validation error from the second window; and

information is transmitted to the asset monitoring system that operates to disable selected configuration attributes.

5. The method of any of the preceding claims, wherein each of the at least one correction is associated with a configuration file, and wherein the at least one correction is an updated configuration attribute corresponding to the selected measurement, and wherein the method further comprises, by the configuration system:

receiving a selection of a profile in a profile list;

automatically selecting the correction associated with the selected profile from the at least one correction;

updating the configuration to replace the configuration attribute with the updated configuration attribute corresponding to the selected correction;

6. The method of claim 5, wherein each profile is associated with a status of the asset, and wherein the method further comprises, by the configuration system:

Receiving a rule set;

determining a status of the monitored asset based on the rule set; and

the configuration file corresponding to the determined asset status is selected.

7. The method of claim 5, the method further comprising: prior to updating the configuration, by the configuration system:

updating the GUI to include a fourth window displaying the automatically selected correction and each correction corresponding to the selected validation error,

wherein the fourth window is further configured to receive user input of an updated correction that is different from the automatically selected correction, and

wherein the selected correction is the automatically selected correction if the updated correction is not received, and wherein the selected correction is the updated correction when the updated correction is received.

8. The method of claim 7, further comprising receiving user input confirming a displayed correction associated with a selected configuration file prior to updating the configuration of a hardware component.

9. The method of any of the preceding claims, wherein the configuration attribute comprises at least one of a scale factor, a linear range, a frequency response, or a health limit of a sensor in communication with the asset monitoring system.

10. The method of any of the preceding claims, wherein the configuration attribute comprises at least one of a measurement type or observation information defining at least a portion of the measurement to be observed.

11. A method according to any preceding claim, wherein the configuration parameter is at least one setpoint corresponding to a respective operating parameter measurement determined by the asset configuration system.

12. A system, the system comprising:

a display device;

a memory storing non-transitory computer readable and executable instructions, and at least one processor communicatively coupled to the memory and configured to execute the instructions that, when executed, cause the at least one processor to

Receiving a configuration including at least one configuration attribute, the at least one configuration attribute corresponding to a measurement determined by an asset monitoring system configured to monitor an asset;

generating a Graphical User Interface (GUI), the GUI comprising a first window comprising an identifier of the measurement and one or more configuration attributes corresponding to the measurement;

Providing the GUI to the display device to display the GUI;

validating the received configuration, wherein validating the received configuration comprises:

receiving a selection of measurements within the first window of the GUI;

determining a validation error of the at least one validation error that corresponds to the selected measurement by:

13. The system of claim 12, wherein the at least one correction includes updated configuration attributes for the measurement or component, and wherein the instructions cause the at least one processor to perform operations further comprising

14. The system of any of claims 12 to 13, wherein the GUI is configured to provide a portion of the first window in the GUI that includes the configuration attribute corresponding to the selected error upon receiving a second selection of a validation error, and wherein the instructions cause the at least one processor to perform operations further comprising

Receiving the second selection;

15. The system of any of claims 12 to 14, wherein the at least one correction disables the selected configuration attribute, and wherein the instructions cause the at least one processor to perform operations further comprising

16. The system of any of claims 12 to 15, wherein each of the at least one correction is associated with a configuration file, and wherein the at least one correction is an updated configuration attribute corresponding to the selected measurement, and wherein the instructions cause the at least one processor to perform operations further comprising

Receiving a selection of a profile in a profile list;

17. The system of claim 16, wherein prior to updating the configuration, the instructions cause the at least one processor to perform operations further comprising

18. The system of claim 17, wherein the instructions cause the at least one processor to perform operations further comprising: user input confirming the displayed correction associated with the selected configuration file is received prior to updating the configuration of the hardware component.

19. The system of any of claims 12 to 18, wherein the configuration attribute comprises at least one of a scale factor, a linear range, a frequency response, or a health limit of a sensor in communication with the asset monitoring system.

20. The system of any of claims 12 to 19, wherein the configuration attribute comprises at least one of a measurement type or observation information defining at least a portion of the measurement to be observed.