Methods, media and systems for monitoring health of analytical chemistry systems
The described system addresses the inefficiencies of conventional maintenance by using a kiosk-connected method for real-time, direct control and automated problem-solving, enhancing the speed and reliability of diagnosing and resolving issues in laboratory analytical instruments.
Patent Information
- Application Number
- CN202280091671.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2021-12-15
- Filing Date
- 2022-12-14
- Publication Date
- 2024-12-03
AI Technical Summary
Conventional maintenance techniques for laboratory analytical instruments are slow and ineffective, often requiring expert intervention, which can lead to prolonged instrument downtime and difficulty in diagnosing and resolving issues due to indirect control and lack of real-time data analysis.
A computer-implemented method and system that includes a kiosk connected to the analytical chemistry system, capable of receiving data, identifying trigger conditions, and automatically executing problem-solving actions directly on the instrument, with the option for cloud-based analysis for more sophisticated issue identification and resolution.
Facilitates rapid and reliable detection and resolution of system health issues, reducing downtime by enabling real-time, direct control over instrument settings and reducing the need for expert intervention, while allowing for learning and expansion to address new problems.
Smart Images

Figure CN119072756A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 289,938, filed on December 15, 2021. The entire disclosure of that application is hereby incorporated herein by reference. Background Art
[0003] Laboratory analytical instruments are devices used to qualitatively and / or quantitatively analyze samples. They are often used in a laboratory setting for scientific research or testing. Such devices can measure the chemical composition of a sample, the amount of components in a sample, and perform similar analyses. Examples include mass spectrometers, chromatographs, titrators, spectrometers, elemental analyzers, particle size analyzers, rheometers, thermal analyzers, etc.
[0004] An analytical chemistry system may consist of one or more laboratory analytical instruments and other supporting devices. Sometimes, it is necessary to perform maintenance on system devices, and even properly maintained devices may suffer from problems that need to be solved from time to time. In a conventional analytical environment, such maintenance and resolution may be done based on best practices maintained in an operating manual or the general knowledge of an expert user. For example, a laboratory manual may require that a specific maintenance procedure be performed on a given laboratory analytical instrument at regular intervals.
[0005] Conventional techniques can be slow and, in some cases, ineffective. For example, when a new problem arises in a laboratory analytical instrument, an administrative user may need to call an expert who understands the operation of the instrument in detail and can diagnose and solve the problem. Until the expert can solve the problem, the instrument (which tends to be very expensive) may be unusable.
[0006] Furthermore, even an expert user may have difficulty diagnosing and resolving a problem if the problem has not been encountered before. Not only does the expert need to perform analysis on the instrument, but the expert also needs to make changes to the instrument without having direct control over the portion of the instrument being adjusted. This can make resolving problems with the instrument more difficult and time consuming. Summary of the invention
[0007] Exemplary embodiments relate to improved techniques for monitoring the health of analytical chemistry systems.Exemplary embodiments may include a computer-implemented method, as well as a non-transitory computer-readable medium storing instructions for performing the method, an apparatus configured to perform the method, and the like.
[0008] In one embodiment, a computer-implemented method includes receiving data associated with an analytical chemistry system. For example, the data may be analytical data obtained by a laboratory analytical instrument during sample analysis. It may also include instrument status data describing one or more parameter values of the instrument and / or settings of the instrument.
[0009] A trigger condition may be identified in the data. A trigger may be associated with a system health issue. For example, a trigger condition may indicate a maintenance issue or diagnosis of a problem with an instrument, such as when a pattern in the data is known to indicate an impending failure of an instrument subsystem.
[0010] A kiosk in communication with an analytical chemistry system may receive notifications of system health issues of the analytical chemistry system. The kiosk may be an external device separate from the analytical instrument of the system (such as a separate computer, tablet computer, mobile device, etc.). The notification may be generated locally at the kiosk based on the kiosk identifying the trigger condition, or the notification may be sent from a different device (such as one of the instruments or a cloud computing device).
[0011] The problem can be looked up in a system health database to retrieve a problem resolution structure, wherein the problem resolution structure includes explanatory text and adjustments to be made to the analytical chemistry system. The problem resolution structure can be, for example, an entry in a database, dictionary, or other similar structure, wherein the trigger condition (or associated system health problem) can serve as a keyword that can be used to find an explanation and a solution (in the form of an adjustment). The notification and explanatory text can be displayed in an interface on the kiosk. Thus, the problem can be marked for resolution.
[0012] One advantage of the described techniques is that the monitoring system is highly coupled to the laboratory analytical instruments it monitors. It receives data and / or trends in the data as they are generated by the instruments. It can therefore be configured to recognize when the data or trends indicate a problem that needs to be corrected (often much faster than an administrator or expert would be able to recognize the problem).
[0013] Still further, questions need not be limited to questions about a particular type of laboratory analytical instrument (eg, a mass spectrometer) or even questions about laboratory analytical instrumentation in general.The monitoring system may be configured to work with many different types of instruments and / or supporting equipment.
[0014] According to a second embodiment, data may be automatically uploaded to a cloud computing service, and notifications may be received from the cloud computing service. This may allow for more sophisticated analysis, as the cloud system may receive and process more data in a more efficient manner than a kiosk. Thus, more types of issues may be identified (potentially faster than at the kiosk).
[0015] According to a third embodiment, the kiosk can be configured to communicate directly with the analytical chemistry system and perform actions from the problem-solving structure to make the adjustment. Direct communication can refer to a direct communication path (possibly on a local wired or wireless network) between the kiosk and the analytical chemistry system, which allows the kiosk to exert direct physical control over the settings of the device of the system. The kiosk may not require an intermediary or agent to change the settings on its behalf. Because the monitoring system is part of the direct physical control of the instrument, it can solve the problem very quickly without introducing problematic delays. For example, when the monitoring system receives an instruction to stop the fluid from flowing through the instrument (either in response to a user selection or automatically based on an analysis of trend data from the instrument), the flow of the fluid can be stopped almost immediately.
[0016] According to a fourth embodiment, an action may be performed in real time in response to a user instruction. Real time execution means that an action is performed within a predetermined, often guaranteed, finite amount of time of the action that triggered it.
[0017] (typically a relatively short time frame). Due to the direct communication link described in conjunction with the third embodiment, actions taken at the kiosk can be reflected very quickly in the control of the maintained instrument or other device. This can solve problems more quickly and reliably than when the user only has indirect or non-real-time control of the device. For example, if an expert attempts to make changes to a system in a conventional environment, the expert may have indirect and / or non-instant control of the device. Therefore, the change may take some time to filter through the device and become effective. In some cases, the user may make multiple changes (thinking that the previous changes failed to solve the problem), where one of the earlier changes solves the problem with a lag. Therefore, it may be difficult to determine which action solves the problem; in addition, the effect of the earlier change may suppress or enhance the later change, and it may be difficult to isolate the specific change that solves the problem.
[0018] According to the fifth embodiment, the explanatory text may include a first explanatory text describing the problem and the solution. The solution may be linked to the action from the problem solving structure. The selection of the first explanatory text may be received, and the action from the problem solving structure may be automatically executed without further user interaction. This embodiment may reduce or eliminate the need to call an expert user for solving the problem, thereby providing a streamlined approach for solving the problem. In addition, because the solution is stored in the problem solving structure, the system may be easily expanded by adding additional explanatory text and linked actions to the structure, and the same system may be taught to respond to new situations. In some cases, the system may be provided with learning capabilities (such as machine learning and / or artificial intelligence) to learn to respond to problems that have been encountered and solved in the past.
[0019] According to a sixth embodiment, identifying a trigger condition may include comparing the data to a maintenance limit, or identifying a trend in the data. A maintenance limit may be a predefined threshold that the data or instrument parameter value should not exceed. Such a limit may be a maximum or minimum value. If a maintenance limit is exceeded, it may indicate that preventive maintenance needs to be performed earlier than expected. This can reduce instrument downtime (because the instrument may have been damaged before the next planned maintenance cycle and require a larger amount of repairs). For example, if the data increases or decreases at a rate exceeding a predetermined rate, or if different linked data values move together in some way, the trend may indicate a predetermined pattern in the data. Even if the maintenance limit is not exceeded, the direction and rate of change in the data may indicate that a problem may occur in the future, thereby allowing the problem to be solved before it gradually turns into a larger problem.
[0020] According to a seventh embodiment, the system health problem can be a diagnostic or maintenance problem. Although the embodiments described herein can be used to perform all modes of action in response to data trends (e.g., data capture in response to detection of predefined conditions, auditing, identifying relationships between different data elements, etc.), they are particularly suitable for diagnosing problems and / or performing preventive maintenance. For example, instead of performing maintenance on a set schedule that is independent of the system context, the exemplary embodiments can eliminate unnecessary maintenance cycles and perform required maintenance in response to data actually emitted from the analytical chemistry system.
[0021] For those skilled in the art, other technical features can be easily seen from the following figures, descriptions and claims.
[0022] Unless otherwise stated, it is contemplated that each embodiment can be used alone to achieve the advantages specifically noted above. It is also contemplated that the embodiments described above (and elsewhere herein) can be used in any combination to achieve further synergistic effects. Other technical features will be readily apparent to those skilled in the art from the following figures, descriptions, and claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure numeral that first introduces that element.
[0024] Figure 1 An example of an analytical chemistry system according to an exemplary embodiment is shown.
[0025] Figure 2 An exemplary data structure according to one embodiment is shown.
[0026] Figure 3 An exemplary user interface according to one embodiment is shown.
[0027] Figure 4A A first exemplary data processing ecosystem is shown according to one embodiment.
[0028] Figure 4B A second exemplary data processing ecosystem is shown according to another embodiment.
[0029] Figure 5 A first exemplary data processing ecosystem is shown according to one embodiment.
[0030] Figure 6 An environment with an uploader and a cloud storage service is shown according to one embodiment.
[0031] Figure 7 Exemplary logic suitable for practicing the embodiments is depicted.
[0032] Figure 8 An exemplary computer system architecture is depicted that can be used to practice the exemplary embodiments described herein. DETAILED DESCRIPTION
[0033] To aid understanding, a series of examples will first be presented before describing a detailed description of the underlying implementation. It should be noted that these examples are merely illustrative, and the present invention is not limited to the embodiments shown.
[0034] Reference is now made to the accompanying drawings, in which like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding thereof. However, novel embodiments may be practiced without these specific details. In other cases, well-known structures and devices are shown in the form of block diagrams for ease of description thereof. It is intended to cover all modifications, equivalents, and substitutes consistent with the claimed subject matter.
[0035] In the drawings and accompanying description, the names "a", "b", and "c" (and similar designations) are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value of a=5, the complete set of components 122, shown as components 122-1 through 122-a, may include components 122-1, 122-2, 122-3, 122-4, and 122-5. The embodiments are not limited in this context.
[0036] These and other features will be described in more detail below with reference to the accompanying drawings.
[0037] For illustration purposes, Figure 1 is a schematic diagram of an analytical laboratory system that may be used in conjunction with the techniques herein. Figure 1A specific type of laboratory analytical instrument in a specific liquid chromatography / mass spectrometry (LCMS) configuration is depicted, but one of ordinary skill in the art will appreciate that different types of chromatography devices (e.g., MS, tandem MS, etc.) may also be used in conjunction with the present disclosure.
[0038] The sample 102 is injected into the liquid chromatograph 104 via the injector 106. The pump 108 can pump the sample through the chromatography column 110 to separate the mixture into component parts according to the retention time through the chromatography column.
[0039] The output from the chromatographic column is input into a mass spectrometer 112 for analysis. Initially, the sample is desolvated and ionized by a desolvation / ionization device 114. Desolvation can be any desolvation technique, including, for example, a heater, a gas, a heater in combination with a gas, or other desolvation techniques. Ionization can be achieved using any ionization technique, including, for example, electrospray ionization (ESI), atmospheric pressure chemical ionization (APCI), matrix-assisted laser desorption (MALDI), or other ionization techniques. The ions produced by the ionization are sent into a collision cell 118 by a voltage gradient being applied to an ion guide 116. The collision cell 118 can be used to transfer ions (low energy) or to fragment ions (high energy).
[0040] A different technique can be used, where an alternating voltage can be applied across the collision cell 118 to induce fragmentation. Spectra are collected of the precursor at low energy (no collision) and of the fragments at high energy (products of collision).
[0041] The output of the collision cell 118 is input to a mass analyzer 120. The mass analyzer 120 can be any mass analyzer, including a quadrupole, a time of flight (TOF), an ion trap, a magnetic sector mass analyzer, and a combination thereof. The detector 122 detects ions emitted from the mass analyzer 122. The detector 122 can be integrated with the mass analyzer 120. For example, in the case of a TOF mass analyzer, the detector 122 can be a microchannel plate detector that counts ion intensities (i.e., counts incident ions).
[0042] The raw data repository 124 can provide permanent storage for storing ion counts for analysis. For example, the raw data repository 124 can be an internal or external computer data storage device, such as a disk, a flash-based storage device, etc. The analysis device 126 analyzes the stored data. The data can also be analyzed in real time without being stored in the storage medium 124. In real-time analysis, the detector 122 passes the data to be analyzed directly to the analysis device 126, rather than first storing it in a permanent storage device.
[0043] Collision cell 118 performs fragmentation of precursor ions. Fragmentation can be used to determine the primary sequence of peptides and subsequently identify the origin protein. Collision cell 118 comprises a gas, such as helium, argon, nitrogen, air or methane. When charged precursors interact with gas atoms, the collisions produced can fragment the precursors by decomposing the precursors into the resulting fragment ions. This fragmentation can be achieved by switching the voltage in the collision cell between a low voltage state (e.g., low energy, <5V) and a high voltage state (e.g., high energy or elevated energy, >15V). High voltage and low voltage can be referred to as high energy and low energy, because high voltage or low voltage is used, respectively, to give kinetic energy to ions.
[0044] Various protocols may be used to determine when and how to switch voltages for such MS / MS acquisitions.After data acquisition, the resulting spectra may be extracted from the raw data repository 124 and displayed and processed by post-acquisition algorithms in the analysis device 126.
[0045] Metadata describing various parameters related to data collection may be generated with the raw data. This information may include the configuration of the liquid chromatograph 104 or mass spectrometer 112 (or other chromatographic device that collected the data), which may define the data type. An identifier (e.g., a key) of a codec configured to decode the data may also be stored as part of the metadata and / or with the raw data. The metadata may be stored in a metadata catalog 130 in the document repository 128.
[0046] The analysis device 126 can provide the analyst with visualization of data at each workflow step according to the workflow operation, and allow the analyst to generate output data by performing processing specific to the workflow step. The workflow can be generated and retrieved via the client browser 132. When the analysis device 126 performs the steps of the workflow, it can read the raw data from the data stream located in the raw data repository 124. When the analysis device 126 performs the steps of the workflow, it can generate processed data stored in the metadata directory 130 in the document repository 128; alternatively or in addition, the processed data can be stored in a different location specified by the user of the analysis device 126. It can also generate audit records that can be stored in the audit log 134.
[0047] The kiosk 136 can interact with laboratory analytical instruments in the analytical chemistry system. The kiosk 136 can host health monitoring logic 700 that is configured to monitor certain conditions or patterns in the data received from the laboratory analytical instruments. When certain trigger conditions are met, the kiosk 136 can generate a health status database 138 (see Figure 2) and retrieves explanatory text to be displayed on the GUI. When the user selects the explanatory text in the GUI, the workflow retrieved from the health status database 138 can be automatically executed. The workflow can include one or more actions configured to resolve the issue that triggered the notification. At least some of these actions can be automatically executed without further user intervention.
[0048] For example, data received from the liquid chromatograph 104 may indicate that there is a leak somewhere in the liquid chromatograph 104. The workflow involved in resolving the problem may include stopping flow through the liquid chromatograph 104, performing diagnostic tests on system valves, rotors, waste lines, and the like.
[0049] The kiosk 136 can be directly coupled to the laboratory analytical instrument. For example, the kiosk 136 can be connected to the laboratory analytical instrument via a wired or wireless connection in a local area network. In some embodiments, the kiosk 136 can be able to directly control the settings or parameter values of the instrument (such as being able to directly control the power, flow rate, thermal management system, etc. of the instrument without using an intermediate or proxy device). Therefore, the user does not need to move to the device and manually make adjustments (or adjust the device through an associated application) - the user can simply select the question on the kiosk to achieve an immediate (e.g., real-time) response from the instrument.
[0050] For simplicity, kiosk 136 is shown as having connections to liquid chromatograph 104 and mass spectrometer 112 (laboratory analytical instruments); however, embodiments are not limited to connections to laboratory analytical instruments. Kiosk 136 may be directly and / or indirectly connected to other devices, such as analytical device 126, client browser 132, raw data repository 124, document repository 128, or audit log 134.
[0051] The exemplary embodiments described herein may be incorporated into a kiosk 136 (potentially in conjunction with a cloud computing device, as described in more detail below). The exemplary embodiments may also or alternatively be executed at a client browser 132 and an analysis device 126, among other locations. Figure 8 Examples of devices suitable for use as kiosk 136, analysis device 126, and / or client browser 132, as well as various data storage devices, are depicted in FIG.
[0052] Figure 2 The apparatus of the information kiosk 136 and other associated devices such as a cloud storage service 216 that receives and processes data and other information from the analytical chemistry system (see, e.g. Figure 6 ))Exemplary data structures used.
[0053] When data / information is received by the cloud storage service 216, the cloud storage service 216 may identify trends, patterns, values, etc. in the data that exceed a maximum or minimum threshold. These identified features may be compared with one or more trigger conditions 214a, 214b, ... in the trigger database 212.
[0054] Triggers may be associated with patterns or thresholds in data received from laboratory analytical instruments—for example, problems may be identified when the data exhibits artifacts such as peak tailing, peak fronting, split peaks, peak distortion, extra peaks, retention time drift, abrupt retention time changes, baseline drift, baseline noise, broad peaks, loss of resolution, etc. Alternatively or in addition, triggers may be associated with patterns or thresholds in sensor readings of various aspects of the monitoring instrument (e.g., flow rate sensors, pressure sensors, temperature sensors, etc.).
[0055] The trigger condition 214a may involve a comparison, such as comparing a data / sensor value to a threshold, comparing a rate of change of a data / sensor value to a predetermined value, detecting that a value has exceeded a threshold for greater than a predetermined amount of time, comparing an average of a value over a period of time to a predetermined threshold, determining that a value has exceeded a threshold more than a predetermined number of times within a predetermined period of time, etc. The trigger condition may also involve a combination of comparisons (e.g., triggering when either condition A or condition B is met, or only when both condition A and condition B are met; any suitable Boolean or logical combination may be used).
[0056] Many different types of maintenance and / or diagnostic issues can be flagged by triggers. Examples include, but are not limited to, system leaks, lack of pressure or flow, high or low back pressure, fluctuating pressure or temperature, etc.
[0057] Each of the triggering conditions may be associated with one or more resolution workflows 208 configured to resolve the problem that caused the triggering condition. To this end, the health status database 138 may store data structures representing different problems in the form of problem resolution structures 202a, 202b, etc. The problem resolution structures may be used by the kiosk 136 to display information about the problem and its potential solution, and to perform or suggest corrective actions to resolve the problem.
[0058] For example, the problem resolution structure 202a may include a problem name 204 that identifies the problem (e.g., "System Leak"). The problem name 204 may be a relatively short identifier that briefly describes the problem for a user. The problem resolution structure 202a may also include a more detailed problem description 206, which may describe the problem in more detail and / or describe values or patterns in the data / information that caused the triggering condition that triggered the problem resolution structure 202a.
[0059] The problem solving structure 202a may also include a solution workflow 208 consisting of one or more actions 210a, 210b, ... Actions may represent adjustments that may be made to a laboratory analytical instrument or associated equipment that form part of a step in a sequence configured to solve a problem. For example, the first action 210a in a problem solving structure 202a configured to solve a system leak may involve stopping the flow of analytes through the instrument. The actions performed by any given solution workflow 208 may depend on the problem being solved.
[0060] An action may include logic or source code configured to automatically adjust a laboratory analytical instrument (e.g., a command to close a valve, an instruction to adjust a pump speed, a call to a power off or power on method, etc.) An action may also or alternatively include explanatory text describing the automatically performed action and / or instructions to manually perform the action.
[0061] Some actions may be automatically performed without user intervention (other than, for example, receiving input from the user indicating that the user wishes to perform the resolution workflow 208). Other actions may be capable of being automatically performed, but may be presented as options for the user to select on a display of the kiosk; these options may not be automatically performed, but may be performed upon receiving a selection from the user.
[0062] Other actions may involve manual resolution steps to be performed by the user, such as prompting the user to perform certain maintenance activities. For example, in the example of a leak in the liquid chromatograph 104, the system may automatically stop the flow and may display additional steps that the user may take to potentially resolve the problem (like replacing a gasket or fitting, tightening an injector port seal, cleaning a filter, etc.).
[0063] In this latter case, the explanatory text may include an interactive element that, when selected, indicates that the user has performed the manual step suggested by the workflow. The kiosk 136 may then proceed to run a system diagnostic to determine whether the action has resolved the problem. If so, the kiosk 136 marks the problem as resolved and removes it from the interface. If not, the kiosk 136 may proceed to the next action in the workflow.
[0064] A particular problem solving structure 202a may include more than one solution workflow 208, such as when a number of different possible workflows may be used to solve the problem. In this case, the interface of the kiosk (see Figure 3 ) may allow a user to select between different workflows. Alternatively or in addition, a given trigger condition may be associated with multiple different problem solving structures, such as when the trigger condition may represent two or more possible problems. More than one trigger condition may be associated with the same problem solving structure 202a.
[0065] use Figure 2 One advantage of the structure depicted in is extensibility. The system can be taught to recognize and respond to new problems or issues by adding new trigger conditions 214a, 214b, ... to the trigger database 212 and linking the triggers to the problem-solving structures 202a, 202b, etc. from the health database 138. Similarly, if a new resolution workflow 208 is developed for a known problem, the new resolution workflow 208 can be swapped into the problem-solving structure 202a (or a new problem-solving structure 202a can be created for the new resolution workflow 208) to immediately improve the system's problem-solving capabilities.
[0066] Figure 3 An interface 300 for displaying information from the problem resolution structure 202a and guiding a user through problem resolution is depicted. The interface 300 can be displayed on the kiosk 136.
[0067] Figure 3 Describes specific views for troubleshooting system health issues. Figure 3 The view depicted in FIG. 10 may be one of many possible views accessible through kiosk 136 (which may handle other tasks such as performing setup of an analytical chemistry system, adjusting system settings, viewing data, displaying and adjusting maintenance schedules, etc.). Navigation pane 302 may allow a user to switch between different views; selecting system health tab selector 304 in navigation pane 302 may cause display of the system health tab selector 304. Figure 3 The health view depicted in .
[0068] Within health interface 300, recent questions that have been triggered can be displayed in recent questions sub-interface 310. For example, recent questions sub-interface 310 can display a single recent question identified, a predetermined number of recently identified questions, all questions that have been identified since health interface 300 was last loaded, and the like.
[0069] The recent questions sub-interface 310 may include one or more question elements 312. Each question element 312 may correspond to a particular recent question identified and may reflect information from the problem resolution structure 202a. For example, the question element 312 may include a question name 316 reflecting the question name 204 from the problem resolution structure 202a, a question description 318 reflecting the question description 206 from the problem resolution structure 202a, and the like. Any questions that have not been resolved but are not reflected in the recent questions sub-interface 310 may be displayed in the additional questions sub-interface 320.
[0070] Question element 312 may include context menu element 314 that causes a context menu to be displayed. For example, the context menu may allow the user to ignore the question (causing the question to be removed from interface 300 or moved to additional questions sub-interface 320). In addition, the context menu may include an option to retest the specific question identified in question element 312 (e.g., to check whether the triggering conditions of the question are still met).
[0071] In some embodiments, the next action 210a from the solution workflow 208 may be displayed in the question element 312 along with explanatory text describing what the action 210a will automatically do (or instructions for manually performing the action 210a). Selecting the question element 312 may cause the indicated action 210a to be automatically performed. When the automatic action is performed, the interface 300 may be updated to display the next action 210b from the solution workflow 208, and selecting the question element 312 again may cause the next action 210b to be performed. Alternatively or in addition, the system may advance through multiple actions by a single selection of the question element 312.
[0072] In some embodiments, the next action 210a may be a manual action. In this case, selecting the question element 312 may cause a pop-up window or similar interface element to be displayed, wherein the window describes how to perform the manual action. The window may include a selectable element that the user may select to indicate that the manual action has been performed, which may advance the resolution workflow 208 to the next action 210b. Alternatively, selecting the question element 312 directly from the interface 300 when the manual action 210a is displayed may indicate that the action 210a has been performed and may cause the resolution workflow 208 to advance to the next action 210b.
[0073] Some embodiments involve receiving a selection of explanatory text. This may involve selecting a question element 312, a question description 318, a selectable element associated with the explanatory text (e.g., selection of a button configured to perform a next action 210a, etc.). Selecting the explanatory text may involve, for example, selecting the text on a touch screen device (e.g., by registering a tactile contact on a display area corresponding to the text). It may also involve receiving a selection of an interface element (such as a button or icon) associated with the explanatory text, issuing a voice command to execute a workflow associated with the explanatory text, and other similar input options.
[0074] After the problem has been resolved, the associated problem element 312 may be removed from the interface 300. In some cases, the system may automatically detect when a problem has been resolved (e.g., by determining whether the triggering condition that caused the problem continues to persist). In other cases, the user may trigger the kiosk 136 to manually recheck the analytical chemistry system for problems (and / or other identified problems, and / or new, previously unidentified problems). Thus, the interface 300 may include a system health check element 322 that is configured to cause the system to check the system to determine whether any triggers in the trigger database 212 have been triggered.
[0075] The depicted interface 300 is suitable for displaying and resolving identified system problems. In some cases, the user may wish to view diagnostic information (e.g., sensor readouts, values causing trigger conditions, etc.). To do this, the user may select a diagnostic selection element 308 to display a diagnostic view including that information. The user may switch back to the problem view by selecting a problem selection element 306.
[0076] Figure 4A An exemplary data ecosystem 412 for storing and retrieving chromatographic data is depicted.
[0077] A spectral acquisition 428 (such as a spectrometer, chromatograph, or other device) may perform and output measurements (e.g., as a stream of readouts formatted according to data types specific to the acquisition 428 and / or settings applied to the acquisition 428). These measurements may be stored in a raw data repository 424.
[0078] In one example, acquisition 428 can use an acquisition controller service to acquire samples. The acquisition controller service can submit the samples to an acquisition data receiver autonomous service via a RESTful API call. The acquisition data receiver autonomous service can create a sample set, which represents multiple samples sent to the instrument for analysis. In other words, a sample set is an organized sequence of several injections sent to a chromatographic device.
[0079] The raw data repository 424 may include data from multiple different chromatographic devices and / or chromatographic devices operating in multiple different acquisition modes. Thus, the data processing environment acts as a single data source for applications, regardless of which device generates the data (or in which mode the data operates). Calling into any application in the ecosystem ensures that any acquired data can be accessed and processed appropriately.
[0080] The sample set may be stored in a sample set model repository, while the injected raw data blocks may be sent to a separate acquisition data raw block repository. The data may typically be stored in an oracle database as one or more models, which may represent a serialization format for storing data. The serialization format may be a proprietary format. The model may be streamed to various applications and / or requested via an interface call. One or more libraries 432 built into the data ecosystem 412 may be able to read the models and deserialize them by converting them into basic modules. The library 432 may be, for example, a dynamic link library (DLL) of the data ecosystem 412. In addition to deserializing the model, the library 432 may also describe derived channels in the data by defining how to convert the measurement data into data of different types, formats, or organizations.
[0081] The collection 428 may also generate metadata describing the configuration of the collection 428, details of the experiment being performed, decoders configured to decode the data generated for the experiment, etc. This metadata may be stored in the metadata directory 130. As with the raw data repository 424, the metadata directory 130 may store metadata associated with a plurality of different collection devices in a plurality of different configurations.
[0082] The raw data can be decoded by a set of decoders 404, each of which is associated with a specific data type. For example, a decoder can be associated with a specific type of raw data generated by a chromatographic instrument in a specific acquisition mode. The instrument can output a raw data stream, including (for example) binary data, information arrays, etc. The decoder can be programmed to parse the raw data stream generated by such an instrument so that the data stream can be meaningfully interpreted.
[0083] In some embodiments, a single decoder may be associated with multiple data types; in another embodiment, multiple versions of the same decoder may each be associated with a different data type. Decoder 404 may be embedded within data service 402, such as an autonomous service (eg, via reflection).
[0084] Each autonomous service may expose one or more endpoint interfaces. A specific decoder may be associated with each endpoint interface. The decoder may be configured to interpret the raw data associated with the endpoint interface.
[0085] For example, the endpoints may be representational state transfer (REST) endpoints capable of receiving RESTful application programming interface (API) calls. The endpoint interface may receive a request for raw data collected by the chromatographic instrument. The data ecosystem 418 may expose multiple endpoint interfaces; for example, each autonomous service may be associated with at least one endpoint interface and may expose at least one endpoint interface. An application 410a, 310c configured to process raw data may use an API call to call an endpoint interface in order to retrieve data.
[0086] The autonomous service (or another configuration) can retrieve the requested raw data from the raw data repository, apply the decoder to the raw data to generate decoded data, and can return the decoded data in response to the original request. For example, the autonomous service can apply the decoder to the raw data and provide the decoded data to the requesting application, or the autonomous service can identify the decoder and provide it (or a location where it can be accessed) along with the raw data (or the location of the raw data) to the requesting application. In the latter case, the application can use the decoder to decode the data.
[0087] Returning to the above example, the autonomous service may retrieve the sample set model from the sample set model repository and / or may retrieve the original data block from the original data block repository. The data may be decoded according to the decoder, and either version of the data (original data block or sample set) may be provided to the application. The reason for providing either or both of the original data block and the sample set model is that the application may be adjusted to use one or the other representation of the data for performance reasons.
[0088] By showing the endpoint interface in this way, applications 410a, 310c can request data collected by the chromatographic instrument without understanding how to interpret the data. In addition, applications 410a, 410d can store data in a central repository together with metadata in a known or universal format, and metadata indicates, for example, when the data is received by the application, when the data is processed by the decoder, the identity of the user who captures the data, the identity of the instrument that generates the data, and other information describing how and when to collect the data. Therefore, when a new type of instrument is brought online (possibly outputting data in different stream formats), it is not necessary to reprogram each application 410a, 310c that may use the data. Because each application 410a, 410d does not need to be programmed with the details of how to interpret each different type of data stream, more different types of data can be made available to the application, which allows more complex analysis. This configuration also allows multiple different types of data to be stored together in a common source structure, thereby simplifying data retrieval and storage.
[0089] In the depicted embodiment, the endpoint interface has two types. The first type serves as a directory endpoint 406, which is configured to receive a request for metadata. In response to receiving a request for metadata on the directory endpoint 406, the data service 402 can identify the corresponding metadata in the metadata directory 130. The data service 402 can then return the requested metadata to the requesting application, or can return the location of the metadata so that it can be retrieved by the application as needed.
[0090] Another type of endpoint interface may be used as a data endpoint 408. Typically, there are multiple data endpoints 408 in the data ecosystem 412 corresponding to the multiple data types that the raw data repository 424 can support. Each data endpoint 408 is characterized by a data type. When an application requests data, it can call the raw data repository or metadata directory to identify the type of data; for example, the data may be tagged with a codec key stored with the data and / or stored in the metadata. The endpoint interface can be callable based on the data type, so once the data type is known, the requesting application can identify the appropriate endpoint interface to decode the data, and can formulate an appropriate RESTful API call to communicate with the interface. This provides an efficient way for applications to identify and call autonomous services that can decode data.
[0091] Therefore, incoming requests are divided into metadata-specific requests and data-specific requests. Each is handled by a different type of endpoint. This helps isolate incoming requests and provides a known endpoint to the requesting application for the appropriate type of request.
[0092] In this example, a single autonomous service handles requests for metadata and each different data type. Although simple to implement, it may be necessary to update the entire autonomous service every time one of the data types is changed or a new data type is added. This may result in unnecessary downtime. In addition, the autonomous service needs to be able to access both the metadata catalog 130 and the raw data repository 424. These issues can be alleviated by dividing the responsibility for different tasks between different autonomous services. Next, Figure 4B Describe an example of such an environment.
[0093] Figure 4B An alternative configuration is shown in which (1) metadata requests are all directed to a specific data service 414 that interfaces with a document repository 430 rather than a raw data repository 424, and (2) data requests are submitted to any one of a number of additional autonomous services, each of which has a specific decoder or set of decoders embedded and handles requests for data types specific to its embedded decoder.
[0094] In this configuration, multiple data services 420, 322, etc. service incoming requests for data. In addition, at least one data service 414 is specifically configured to respond to requests for metadata. Data services 414 that respond to metadata requests do not respond to requests for data, and therefore do not need to implement any functionality related to decoders. Similarly, data services 420, 322, etc. that respond to data requests do not need to implement any functionality for querying the metadata directory. When new data types are added, new autonomous services that implement decoders for the new data types can be added, or existing autonomous services can be updated with the new functionality. At the same time, most autonomous services can remain unchanged. Similarly, if the metadata directory API is ever changed, only the metadata processing autonomous service needs to be updated.
[0095] The original data repository 424 includes data of multiple different data types. Collectively, autonomous services can be configured to decode each of the multiple different data types. For example, multiple different data types can be included in an interface specification, which can describe how to decode various different types. The interface specification can be implemented at least in part by each of the autonomous services by implementing the corresponding data endpoint 408 and decoders 416, 324. Each data service 420, 322 can be associated with a different group of decoders 416, 324, although there may be some overlap in the decoders supported by different data services. However, no single data service implements all decoders, so the functions for decoding different types of data are distributed on multiple data services. Therefore, different parts of the interface specification can be divided between multiple different autonomous services, so that each autonomous service implements a part of the interface specification, but not all. Each part of the interface specification can be implemented by at least one autonomous service, so that the interface service group implements the interface specification together.
[0096] Because each autonomous service is tasked with implementing only a portion of the interface specification, each autonomous service can be simpler (since it does not need to be concerned with providing decoders and endpoint interfaces for the portions of the interface specification that it does not implement). New autonomous services can be easily added to handle new capabilities, and there is no need to shut down all autonomous services when one decoder needs to be updated.
[0097] Figure 5 An exemplary data ecosystem 510 for storing and retrieving chromatographic data is depicted. Figure 4A (in which case decoder 508 may be associated with decoder 404), Figure 4B The implementation depicted in (where decoder 508 may be associated with decoders 416, 426) or any other suitable configuration may be used.
[0098] Kiosk 136 may be a dedicated computing device for performing various tasks such as authentication and authorization, system setup, system health monitoring, etc. Alternatively, the functionality may be built into another general purpose device. Kiosk 136 may be able to interact with collection device 520 and / or application 410c (there are other possibilities such as analysis device 126 or client browser 132) to perform a system health check.
[0099] To this end, the kiosk 136 may include a short-range wireless transmitter / receiver (e.g., a near field communication (or NFC) reader). The kiosk 136 may be configured to receive a wireless transmission of a security token from the user's mobile device 514 via the short-range wireless transmitter / receiver. The security token may include the login credentials of the user 512 and, optionally, an identification of the device or application that the user is attempting to access. The security token may be encrypted.
[0100] In some embodiments, the user 512 may be required to first log into an application on their mobile device 514 before having the opportunity to transmit the login credentials to the kiosk 136. This provides an additional level of security because an unauthorized user would need to physically possess the user's mobile device 514 and know the user's login name and password in order to be authorized to use the data ecosystem 510 via the kiosk 136.
[0101] In some embodiments, the user may not need to log in to the application, or the previous login may continue to provide access for a period of time (e.g., six hours, a day, a week, etc.). The time period may be predetermined based on the environment and security requirements of the organization maintaining the data ecosystem 510, or may be dynamically determined based on current security conditions. If the previous authorization is valid, the kiosk 136 may automatically receive short-range wireless communications that the user 512 is not prompted for. For example, the kiosk 136 may continuously prompt for new logins via short-range wireless communications. When the user 512 brings their mobile device 514 into close proximity with the kiosk 136, the mobile device 514 may receive a prompt from the kiosk 136 and automatically respond with a security token. The mobile device 514 may be configured to run an application in the background to automatically detect the prompt and respond to the prompt. Therefore, the user can log in to the data ecosystem 510 via the kiosk 136 without taking the mobile device 514 out of the user's pocket, bag, or other storage location.
[0102] The login credentials may be sent from the kiosk 136 to an authentication backend device 516 (such as a server) for verification. The authentication backend device 516 may verify that the user's login credentials are valid (e.g., the credentials correspond to a real user) and that the user is authorized to use the device or application for which access is requested. The authentication backend device 516 may send a confirmation or a denial to the kiosk 136, depending on whether the authentication backend device 516 can verify the user's credentials.
[0103] In some embodiments, the login credentials in the security token may include a data value representing a universal access key that is common to all authorized users of the system. The authentication backend device 516 may recognize the universal access key and allow access to the data ecosystem 510. The use of the universal access key may be controlled by the user application on the mobile device 514, so that if authorization needs to be removed from a given user, the user's application may be configured not to provide access. When logging into the application on the user's mobile device, the user's application may be configured so (which may involve connecting to an authentication server; this may be a backend device 516 that communicates with the kiosk 136, or may be another authentication device). In this way, authentication can be performed in a relatively simple manner because the authentication backend device 516 only needs to recognize one set of credentials: the universal access key.
[0104] In other embodiments, each user may be assigned their own access key. Although this may be more complex from the perspective of the authentication backend device 516, this may allow individual users to be quickly authorized or deauthorized by adding their unique access keys to a list stored at the authentication backend device 516.
[0105] The kiosk 136 may be configured to send a command signal to the connected device that authorizes the user 512 to use the connected device. In response to receiving the command signal, the connected device may become unlocked and able to process instructions from the user (received directly on the connected device, through the kiosk 136, via the user's mobile device 514, or through another device such as the analysis device 126). In the absence of such a command signal, the connected device may be locked and may be unable to accept or process commands from any unauthorized user.
[0106] When a user logs in or out via the kiosk 136, the kiosk 136 may generate an instruction to create an audit record that stores the user's identifier, the action taken (e.g., log in or log out), a timestamp, and any other relevant data used in the audit record. The kiosk 136 may generate the audit record and transmit it to a device responsible for maintaining an audit trail, such as the analysis device 126 and / or the audit log 134. Alternatively or in addition, the audit record may be generated by another device, such as the analysis device 126 or the authentication backend device 516. In some embodiments, the kiosk 136 and the mobile device 514 may work together to create the audit record.
[0107] Once logged into the kiosk 136, the user can display the health interface 300, such as Figure 3 The information kiosk 136 can be connected to a collection device 520 and / or a cloud computing device (see Figure 6 ) to perform a system health check.
[0108] Figure 6 An exemplary environment is depicted including an uploader 614 and a cloud storage service 216. The uploader 614 may be configured to upload data stored in a local data service 626, such as a database system. An example of a local data service 626 is an ORACLE database management system (DBMS).
[0109] The environment includes an installation / configuration module 602 for the uploader. The installation / configuration module 602 may include a setup file to install the uploader 614 on a computing device. As part of the installation of the uploader 614, the installation / configuration module 602 may perform a handshake process with the cloud storage service 216 that authenticates the uploader 614 to the cloud storage service 216. To this end, the installation / configuration module 602 may communicate with a user management service 604 of the cloud storage service 216 to authenticate the user, organization, or other entity that installed the uploader 614. An example of a user management service 604 is the COGNITO service provided by AWS, which registers users with the cloud storage service 216, establishes leases, and maintains and enforces access permissions.
[0110] Once authenticated, the installation / configuration module 602 may install the uploader 614 on the computing device. The user management service 604 may provide a certificate 606 proving authentication, which may be installed on the computing device along with the uploader 614. When uploading data, the uploader 614 may use the certificate 606 to authenticate itself to the cloud storage service 216.
[0111] The data stored in the database 608 of the local data service 626 can be organized into projects. Each project can represent a user-configurable collection of data sets. Data sets can be updated as new results are received from experiments. The uploader 614 can upload all data in a project (referred to as "seeding"), or can upload data related to specific results as they are received (referred to as real-time trickling).
[0112] The uploader 614 may include an uploader UI 612 that allows a user to select data to be manually seeded into the data warehouse 622. To upload data in a real-time trickle, the database 608 may be configured with one or more database triggers 624. The triggers 624 may be configured to fire when new data is added to the database 608. Each trigger 624 may be associated with a stored procedure within the database 608, where the stored procedure sends an API call (such as a REST call) to the uploader 614. The uploader 614 may be configured to listen for the REST call and start uploading the data that triggered the call to the cloud storage service 216.
[0113] To facilitate querying, the database 608 can store data in materialized views. The materialized views can be pre-computed based on the query form used by the local data service 626.
[0114] The goal of the uploader may be to transfer at least some of the data stored in database 608 to data warehouse 622. Because data warehouse 622 will likely respond to many queries for data, 622 may store data in a form optimized for read access. For example, data warehouse 622 may be a relational database such as AWS REDSHIFT.
[0115] Data warehouse 622 may need to store data in a specific form to optimize read access. This may be different from the form used to store data in database 608. Therefore, uploader 614 in conjunction with object storage service 618 and ETL service 620 can convert data from a first data model used to store data in database 608 to a second data model used to store data in data warehouse 622.
[0116] To this end, the data may be uploaded to an object storage service 618 of a cloud storage service 216 (such as AWS S3). The object storage service 618 may be a multi-tenant storage service that stores data in tenant-specific buckets. During installation, the installation / configuration module 602 may prompt the user to enter a lease ID or name that represents the user in the user management service 604. The lease ID / name may be stored in the local data service 626 so that the uploader 614 can isolate the data of a specific user in the user-specific bucket of the object storage service 618.
[0117] In addition to the original data, derived data and metadata may also be uploaded to the object storage service 618. The metadata may include, for example, a lease identifier that identifies a lease associated with a user of the uploader in the cloud storage service 216. In addition, the metadata may include a project identifier indicating the project to which the uploaded data belongs. In addition, the metadata may include a channel identifier for the stream file uploaded by the uploader.
[0118] The ETL service 620 can be configured to monitor new data entering the object storage service 618 (e.g., using a serverless computing service such as AWS LAMBDA), transform it (e.g., into a second data model), and store the transformed data in the data warehouse 622.
[0119] The trend data module 628 can access the data stored in the data warehouse 622 and analyze it to identify data trends. The trend data module 628 can include artificial intelligence or machine learning (AI / ML) capabilities to identify data and suggest the best way to visualize it. An example of a trend data module 628 suitable for use with the exemplary embodiment is AWS QUICKSIGHT.
[0120] The trending data module 628 can identify commonly requested configurations and select the most appropriate visualization for them. For example, the trending data module 628 can identify that the available data contains a set of fields that can be used to perform a specific type of analysis. Alternatively or in addition, the user can select a set of fields, and the trending data module 628 can recognize that the selected fields generally correspond to a specific type of analysis or visualization.
[0121] Examples of analysis types that the trend data module 628 may recognize include: method performance, column performance, product performance, product stability, system suitability, field performance, system performance, and analyst performance.
[0122] Method can refer to the analytical method used to analyze the chemical data. The trend data module 628 can identify the method being analyzed when the available fields in the data set include fields that identify the method or method steps or quantify the performance of the method (e.g., by measuring the accuracy of the method relative to a known standard, or by comparing the settings or parameters of the standard to a known optimal configuration).
[0123] The column can be a column of an analytical laboratory instrument such as a gas or liquid chromatograph. Column performance can be measured by evaluating the repeatability of column measurements, or by determining how accurate the column readings are compared to known standards. The trend data module 628 can determine that column performance is being analyzed when a field in the data set includes an identifier of the column used to make the measurement and / or parameters that are typically used to determine column performance, such as column age, last calibration time, etc.
[0124] Product performance and stability may refer to the potency, quality, strength, and / or stability (e.g., degradation of performance over time) of a given analyte or compound. The trend data module 628 may determine that product performance or stability is being measured when fields of a data set include an identifier of the product under consideration and / or measurements of the product's concentration, quality compared to a reference product (such as a pure sample of the product), amount of impurities, etc., and particularly (in the case of stability) when these values are measured over a period of time.
[0125] System suitability may refer to the suitability of one or more configured analytical laboratory instruments for achieving the type of measurement results required for analytical chemistry experiments. The trend data module 628 may determine that system suitability is being measured when fields of a data set include typical measurements of system suitability, such as an identifier of the system being analyzed, a value of the system's configuration, an identifier of the type of product the system is configured to analyze, and / or a measure of the performance or quality of the results generated by the system.
[0126] Site performance may refer to the performance of a group of instruments at a given location, such as an analytical laboratory. System performance may refer to the performance of a selected one or group of laboratory analytical instruments (e.g., as measured by the repeatability of results, how well the instrument measures known standards, maintenance schedules, etc.). When a field of a data set includes an identifier that associates a particular instrument with a site, such as a laboratory identifier, the trend data module 628 may determine that site performance is being analyzed, particularly where multiple instruments in the data set are associated with a particular site.
[0127] Analyst performance may describe the accuracy or efficiency of a particular user, possibly across a variety of different instruments. The trend data module 628 may determine that analyst performance is being analyzed when a field of a data set includes an identifier of the analyst who generated the results and a measure of the quality of the results generated by the analyst.
[0128] Based on the type of analysis being performed, the trend data module 628 can select an appropriate type of visualization (e.g., a line graph, a specific type of graph such as a line graph or a bar graph, a table, etc.). The type of visualization can be selected based at least in part on the dimensionality of the data. For example, if the selected field represents a single data point, the value of that data point can be displayed in the visualization. If the data is two-dimensional, a line graph can be an appropriate type of visualization.
[0129] The visualizations computed by trend data module 628 may be presented in a visualization interface of visualization application 630. Visualization application 630 may be an application running on a client device or in a browser.
[0130] The trend data module 628 may also be used to trigger a trigger stored in the trigger database 212. When a trigger is activated, the trend data module 628 may send a notification to the kiosk 136 identifying the trigger and / or the problem resolution structure 202a associated with the trigger.
[0131] Figure 7 700 is a flow chart depicting exemplary health monitoring logic for performing a computer-implemented method according to an exemplary embodiment. The logic may be embodied as instructions stored on a computer-readable medium, the instructions being configured to be executed by a processor. The logic may be implemented by a suitable computing system configured to perform the actions described below.
[0132] Processing may begin at start block 702 , which may be performed in response to the kiosk 136 booting up or a user logging into the kiosk 136 .
[0133] In block 704, data associated with the analytical chemistry system may be received. The data may include output data from sample analysis and / or sensor data describing the status of a device in the system, among other possibilities. In general, any diagnostic or maintenance data that can be used to identify a problem or issue with the analytical chemistry system may be provided. The data may be provided to a kiosk, an analytical device, a remote computing device, or any other computing device suitable for comparing the data (or information derived from the data) to a trigger in a trigger database.
[0134] In some embodiments, the data may be provided to a cloud computing environment such as Figure 6 ). Therefore, in block 706, the data may optionally be uploaded to the cloud computing environment.
[0135] In decision block 708, the computing system that received the data (or another processing system to which the recipient sends the data for processing) may determine whether a trigger condition has been met. To do so, the system may compare the data (or information derived from the data) to triggers in a trigger database. Among other possibilities, detecting a trigger condition may involve comparing the data (or information derived from the data) to maintenance limits or identifying a trend in the data (or information derived from the data).
[0136] If any trigger is met ("yes" at decision block 708), processing may proceed to block 710. If not ("no" at decision block 708), processing may return to block 704 and the system may wait for new data.
[0137] In block 710, a notification that a trigger condition was met may be sent from the device processing the data to the kiosk (or the kiosk may generate its own notification if it identifies the trigger). For example, if the data is uploaded to a cloud computing service, the cloud processor processing the data may generate a notification and send it to the kiosk. The notification may include an identification of the trigger condition that was met, an identification of the problem-solving structure 202a associated with the trigger condition, an identification of the problem or question associated with the trigger condition (which may then be looked up in the health status database 138), a copy of the associated problem-solving structure 202a, or any other suitable identifier that allows the kiosk to retrieve the relevant problem-solving structure 202a.
[0138] In box 712, the system can use the notification to find the problem in the health status database 138. The system can retrieve the relevant problem resolution structure 202a and can display a notification of the identified health problem in the interface 300 at box 714. For example, the system can create a question element 312 corresponding to the identified problem and add it to the recent problems sub-interface 310. The system can optionally trigger an alert, such as a pop-up text alert, email, SMS message, audio alert, or any other suitable alert to flag that a new problem has been raised for the appropriate registered users.
[0139] In decision block 716, the system receives and processes input to the interface 300. In some cases, the user may dismiss the question (e.g., via a context menu for the question element 312), at which point processing proceeds to block 718, where the display is updated to reflect the dismissal. For example, the system may completely remove the question element 312 associated with the question from the interface 300, move it to the additional questions sub-interface 320, or change the question element 312 to reflect that the question has been dismissed. Processing may then return to block 704, where the system waits for new data that may trigger the identification of additional questions.
[0140] Alternatively, the user may select a question in decision box 716. For example, the user may select the explanatory text of question element 312. In this case, processing may proceed to box 720, where the next action from the workflow may be performed (automatically in some cases, or manually where appropriate).
[0141] Actions may be automatically performed without requiring further user interaction with interface 300 (other than initially selecting a problem to indicate that the associated workflow should be executed). A workflow may proceed with any actions it can automatically perform, stopping when a problem is resolved, the workflow runs out of actions, or the workflow reaches an action that requires manual execution.
[0142] The kiosk can communicate directly with the analytical chemistry system so that it can perform actions to make adjustments directly to the instrument. The actions can be performed in real time in response to user instructions.
[0143] In some embodiments, the problem element 312 may include explanatory text, such as first explanatory text describing the problem and a solution that is linked to an action from the problem-solving structure. The system may receive a selection of the first explanatory text and automatically perform an action from the problem-solving structure without further user interaction.
[0144] In decision block 722, the system determines whether the actions performed at block 720 resolved the problem. Decision block 722 may be performed automatically after the actions terminate, or may be triggered by a user (e.g., by selecting system health check element 322 in interface 300). At decision block 722, for example, the system may check the most recent data received from the affected device to determine whether the updated data still satisfies the triggering condition that triggered the original problem (and / or optionally satisfies other triggering conditions that may indicate that the fix to the problem caused a different problem, or that the problem is masking another underlying problem).
[0145] Whether the problem is ignored in block 716, resolved at block 722, or involves some other situation (e.g., an action was attempted that failed to resolve the problem), the ignore / action may be stored in a log. For example, the log may store the problem identified, the action taken (or ignored), the status of the problem (resolved / unresolved), and other relevant information about the problem. The log may be stored for later review and / or for use with machine learning / artificial intelligence algorithms to enable more efficient problem resolution in the future.
[0146] If the problem is not solved at decision block 722, processing may return to block 720 and the next action in the resolution workflow 208 may be performed. It should be noted that not every action may necessarily trigger decision block 722—for example, if the action is part of the problem but is known to be insufficient to solve the problem (e.g., stopping flow when a leak is detected), decision block 722 may be omitted and processing may proceed to the next action. If the system runs out of actions to be performed in the resolution workflow 208 without solving the problem, a new notification may be generated indicating that a more intensive corrective action is required. Optionally, the system may take preventive measures at this time, such as shutting down associated instruments.
[0147] On the other hand, if the problem is resolved at decision block 722 , the display may be updated to reflect the fact that the problem has been resolved (e.g., displaying a success notification and / or removing the problem element 312 from the interface 300 ), and processing may return to block 704 , where the system awaits additional data that may indicate a new problem.
[0148] although Figure 7 Specific actions are depicted as being performed in a specific order, but the embodiments are not limited to Figure 7It is contemplated that more, fewer, or different logic blocks may be implemented. Similarly, it is contemplated that Figure 7 The actions may be performed in a different order than shown.
[0149] Figure 8 An example of a system architecture and data processing device that can be used to implement one or more illustrative aspects described herein in a standalone and / or networked environment is shown. Various network nodes such as data server 810, web server 806, computer 804, and laptop computer 802 can be interconnected via a wide area network 808 (WAN) such as the Internet. Other networks can also or alternatively be used, including a private intranet, a company network, a LAN, a metropolitan area network (MAN), a wireless network, a personal network (PAN), etc. Network 808 is for illustrative purposes and can be replaced by fewer or more computer networks. A local area network (LAN) can have one or more topologies in any known LAN topology, and can use one or more protocols in a variety of different protocols, such as Ethernet. Device data server 810, web server 806, computer 804, laptop computer 802 and other devices (not shown) can be connected to one or more networks in the network via twisted pair, coaxial cable, optical fiber, radio waves or other communication media.
[0150] The computer software, hardware, and networks may be used in a variety of different system environments, including stand-alone, networked, remote access (also known as remote desktop), virtualized, and / or cloud-based environments, among others.
[0151] The term "network" as used herein and depicted in the accompanying drawings refers not only to a system in which remote storage devices are coupled together via one or more communication paths, but also to independent devices that may be coupled to such a system from time to time with storage capabilities. Thus, the term "network" includes not only a "physical network" but also a "content network" consisting of data residing on all physical networks that can be attributed to a single entity.
[0152] Components may include a data server 810, a web server 806, a client computer 804, and a laptop computer 802. The data server 810 provides overall access, control, and management of databases and control software for performing one or more illustrative aspects described herein. The data server 810 may be connected to a web server 806, through which a user interacts with the requested data and obtains the data. Alternatively, the data server 810 itself may act as a web server and be directly connected to the Internet. The data server 810 may be connected to the web server 806 via a network 808 (e.g., the Internet), via a direct or indirect connection, or via some other network. A user may interact with the data server 810 using a remote computer 804, a laptop computer 802, such as using a web browser to connect to the data server 810 via one or more external public web sites hosted by the web server 806. The client computer 804, the laptop computer 802 may be used together with the data server 810 to access the data stored therein, or may be used for other purposes. For example, from a client computer 804, a user may access the web server 806 using an Internet browser (as is known in the art) or by executing a software application that communicates with the web server 806 and / or data server 810 via a computer network (such as the Internet).
[0153] The server and application can be combined on the same physical machine and retain separate virtual or logical addresses, or can reside on separate physical machines. Figure 8 Only one example of a network architecture that may be used is shown, and those skilled in the art will appreciate that the specific network architecture and data processing devices used may vary and are secondary to the functionality they provide, as further described herein. For example, the services provided by web server 806 and data server 810 may be combined on a single server.
[0154] Each component data server 810, web server 806, computer 804, laptop computer 802 can be any type of known computer, server or data processing device. Data server 810 can include, for example, a processor 812 that controls the overall operation of data server 810. Data server 810 can also include RAM 816, ROM 818, network interface 814, input / output interface 820 (e.g., keyboard, mouse, display, printer, etc.) and memory 822. Input / output interface 820 can include various interface units and drivers for reading, writing, displaying and / or printing data or files. Memory 822 can also store operating system software 824 for controlling the overall operation of data server 810, control logic components 826 for instructing data server 810 to perform various aspects described herein, and other application software 828 that provides auxiliary, support and / or other functions that can be used in conjunction with or without the various aspects described herein. Control logic can also be referred to as data server software control logic 826 in this article. The functionality of the data server software may refer to a combination of operations or decisions made automatically based on rules encoded into the control logic, manually by a user providing input to the system, and / or automatic processing based on user input (e.g., queries, data updates, etc.).
[0155] The memory 822 may also store data for performing one or more aspects described herein, including a first database 832 and a second database 830. In some embodiments, the first database may include the second database (e.g., as a separate table, report, etc.). That is, the information may be stored in a single database, or divided into different logical, virtual or physical databases, depending on the system design. The web server 806, computer 804, laptop computer 802 may have a similar or different architecture as described with respect to the data server 810. Those skilled in the art will appreciate that the functionality of the data server 810 (or web server 806, computer 804, laptop computer 802) as described herein may be distributed across multiple data processing devices, for example, to distribute processing loads across multiple computers, to separate transactions based on geographic location, user access level, quality of service (QoS), etc.
[0156] One or more aspects may be embodied in computer-usable or readable data and / or computer-executable instructions, such as embodied in one or more program modules executed by one or more computers or other devices as described herein. Typically, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. These modules can be written in source code programming languages, which are then compiled for execution, or these modules can be written in scripting languages such as (but not limited to) HTML or XML. Computer executable instructions can be stored on a computer-readable medium such as a non-volatile storage device. Any suitable computer-readable storage medium can be used, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and / or any combination thereof. In addition, various transmission (non-storage) media representing data or events as described herein can be transmitted between a source and a target in the form of electromagnetic waves propagated through a signal-conducting medium such as a metal wire, an optical fiber, and / or a wireless transmission medium (e.g., air and / or space). The various aspects described herein can be embodied as a method, a data processing system, or a computer program product. Thus, the various functions may be embodied in whole or in part in software, firmware, and / or hardware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGAs), etc. Certain data structures may be used to more efficiently implement one or more aspects described herein, and such data structures are contemplated to be within the scope of the computer-executable instructions and computer-usable data described herein.
[0157] The components and features of the devices described above may be implemented using any combination of discrete circuit systems, application specific integrated circuits (ASICs), logic gates, and / or single chip architectures. In addition, where appropriate, microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the foregoing, may be used to implement the features of these devices. It should be noted that hardware, firmware, and / or software elements may be collectively or individually referred to herein as "logic" or "circuitry."
[0158] It should be understood that the exemplary devices shown in the above block diagrams may represent a functional descriptive example of many possible specific implementations. Therefore, the division, omission or inclusion of block functions depicted in the drawings does not mean that the hardware components, circuits, software and / or elements used to implement these functions will necessarily be divided, omitted or included in the implementation.
[0159] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.
[0160] Some embodiments may be described using the expressions "one embodiment" or "an embodiment" and their derivatives. These terms mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The appearance of the phrase "in one embodiment" in different places in the specification does not necessarily refer to the same embodiment. In addition, unless otherwise stated, the above-mentioned features are considered to be usable together in any combination. Therefore, any features discussed separately can be used in combination with each other, unless it is stated that these features are incompatible with each other.
[0161] The detailed description herein may be presented in terms of program processes executed on a computer or computer network with general reference to the notations and nomenclature used herein. These program descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.
[0162] A process is generally considered to be a self-consistent sequence of operations that brings about a desired result. These operations are those requiring physical manipulation of physical quantities. Although not required, these quantities usually take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. In practice, it has proven convenient at times to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for common reasons. It should be noted, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
[0163] In addition, the manipulations performed are often referred to by terms such as adding or comparing, which are often associated with mental operations performed by a human operator. In any of the operations described herein that form a part of one or more embodiments, in most cases, such capabilities of a human operator are not necessary or desirable. Instead, these operations are machine operations. Useful machines for performing the operations of the various embodiments include general purpose digital computers or similar devices.
[0164] The expressions "coupled" and "connected," as well as their derivatives, may be used to describe some embodiments. These terms are not necessarily intended to be synonymous with each other. For example, the terms "connected" and / or "coupled" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.
[0165] Various embodiments also relate to devices or systems for performing these operations. The device may be specially constructed for the desired purpose, or it may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. The processes presented herein are not inherently related to a particular computer or other device. Various general-purpose machines may be used with programs written according to the teachings of this article, or it may prove convenient to construct more specialized devices to perform the desired method steps. The desired structures of various of these machines will appear in the description given.
[0166] It should be emphasized that the abstract of the present disclosure is provided so as to allow the reader to quickly determine the essence of the technical disclosure. It should be understood that the submitted abstract will not be used to interpret or limit the scope or meaning of the claims. In addition, in the aforementioned specific embodiments, it can be seen that various features can be grouped together in a single embodiment for the purpose of simplifying the present disclosure. This method of the present disclosure should not be interpreted as reflecting the intention that the claimed embodiment requires more features than the features explicitly stated in each claim. On the contrary, as reflected in the following claims, the subject matter of the present invention is less than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the specific embodiments, wherein each claim exists independently as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the colloquial English equivalents of the corresponding terms "comprising" and "wherein", respectively. In addition, the terms "first", "second", "third", etc. are used only as labels and are not intended to impose numerical requirements on their objects.
[0167] What has been described above includes examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and / or methods, but one of ordinary skill in the art will recognize that many further combinations and permutations are possible. Therefore, the novel architecture is intended to encompass all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.
Claims
1. A computer-implemented method, the computer-implemented method include: receiving data associated with an analytical chemistry system; identifying a trigger condition in the data; receiving notification of a system health problem of the analytical chemistry system at a kiosk in communication with the analytical chemistry system; searching the problem in a system health database to retrieve a problem resolution structure, the problem resolution structure including explanatory text and adjustments to be made to the analytical chemistry system; The explanatory text is displayed in an interface on a display of the kiosk. 2 . The computer-implemented method of claim 1 , further comprising automatically uploading the data to a cloud computing service, wherein the notification is received from the cloud computing service.
3. The computer-implemented method of claim 1, wherein the kiosk is configured to communicate directly with the analytical chemistry system and execute actions from the problem-solving structure to make the adjustments. The computer-implemented method of claim 3 , wherein the actions are performed in real time in response to user instructions.
5. The computer-implemented method of claim 3, wherein the explanatory text comprises first explanatory text describing a problem and a solution, the solution being linked to the actions from the problem-solving structure, and further include: receiving a selection of the first explanatory text; as well as The actions from the problem-solving structure are automatically performed without further user interaction.
6. The computer-implemented method of claim 1 , wherein identifying the trigger condition include: Compare said data to maintenance limits, or Identify trends in the data.
7. The computer implemented method of claim 1, wherein the system health issue is a diagnostic or maintenance issue.
8. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: receiving data associated with an analytical chemistry system; identifying a trigger condition in the data; receiving notification of a system health problem of the analytical chemistry system at a kiosk in communication with the analytical chemistry system; searching the problem in a system health database to retrieve a problem resolution structure, the problem resolution structure including explanatory text and adjustments to be made to the analytical chemistry system; The explanatory text is displayed in an interface on the kiosk.
9. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to automatically upload the data to a cloud computing service, wherein the notification is received from the cloud computing service.
10. The computer readable storage medium of claim 8, wherein the kiosk is configured to communicate directly with the analytical chemistry system and execute actions from the problem solving structure to make the adjustment.
11. The computer-readable storage medium of claim 10, wherein the actions are performed in real time in response to user instructions.
12. The computer-readable storage medium of claim 10, wherein the explanatory text comprises first explanatory text describing a problem and a solution, the solution being linked to the actions from the problem-solving structure, and wherein the instructions further configure the computer to: receiving a selection of the first explanatory text; and The actions from the problem-solving structure are automatically performed without further user interaction.
13. The computer-readable storage medium of claim 8, wherein the trigger condition is identified include: Compare said data to maintenance limits, or Identify trends in the data.
14. The computer-readable storage medium of claim 8, wherein the system health issue is a diagnostic or maintenance issue.
15. A computing device, wherein include: processor; and a memory storing instructions that, when executed by the processor, configure the device to: receiving data associated with an analytical chemistry system; identifying a trigger condition in the data; receiving notification of a system health problem of the analytical chemistry system at a kiosk in communication with the analytical chemistry system; searching the problem in a system health database to retrieve a problem resolution structure, the problem resolution structure including explanatory text and adjustments to be made to the analytical chemistry system; The explanatory text is displayed in an interface on the kiosk.
16. The computing device of claim 15, wherein the instructions further configure the device to automatically upload the data to a cloud computing service, wherein the notification is received from the cloud computing service.
17. The computing device of claim 15, wherein the kiosk is configured to communicate directly with the analytical chemistry system and execute actions from the problem solving structure to make the adjustments.
18. The computing device of claim 17, wherein the actions are performed in real time in response to user instructions.
19. The computing device of claim 17, wherein the explanatory text comprises first explanatory text describing a problem and a solution, the solution being linked to the action from the problem-solving structure, and wherein the instructions further configure the device to: receiving a selection of the first explanatory text; and The actions from the problem-solving structure are automatically performed without further user interaction.
20. The computing device of claim 15, wherein the trigger condition is identified include: Compare said data to maintenance limits, or Identify trends in the data.
