Empower Tip: waters_connect™ System Monitoring

In this tip, we will show you how to view System History in waters_connect System Monitoring.

To view System History in the System Monitoring dashboard, search for the system you are interested in. In this example, we selected System BU_8167.

Once in the System Details screen, view the current status as highlighted in the middle of the screen. This section shows which was the last sample set run and if currently running, how long before it is completed.

In the bottom section of the screen, notice the Recent History of the system. This is a default to show you the history of the last 7 days.

To change the Recent History view, click on the ‘System History’ tab (on the upper left corner of the screen) or the ‘View more details’ link (on the lower right part of the screen).

STEP 5:

Once in the System History screen, you will see the system history default for one day (Today) status view. To change the System History, select other date tabs like 30 days or even the Custom range to define a different date range.

In this example, 30 Days is selected. As highlighted, view the total metrics of how much time (and percentage) the system maintained a certain status. Please Note: running metrics include not just when injections were collected, it includes the time when the system was in equilibrate, column conditioning, or pause as long as these non-inject functions are selected as part of the sample set method.

The middle and bottom sections of the System History tab show a ‘graphical timeline’ and a ‘tabular timeline’ of the system status during the time period selected, in this case, a Custom range. Details on the tabular timeline include the project and sample set when the system is running. Or when the system has an error, the details include the error reported.

Hover your cursor on a segment of the graphical timeline, it will provide the start and end time of that status. Please Note: when viewing a section with an error, the error may not be for the full duration, it may be that the status persists in the error state until someone fixes the problem and the state changes.

It’s that easy!