NOTE : The “Current Status” page is visible to cloud accounts with SensoScientific’s Cold Storage monitoring system.
The “Current Status” page displays all the Wi-Fi nodes that are registered and assigned to the current user's account. (To learn how to assign nodes to users, see Add/Remove Nodes to Users and/or Add/Remove Users from Groups.)
Contents
Select the “MONITORING” tab in the main menu.
Select the “Current Status” tab in the submenu.
“Current Status” Page
The “Current Status” table displays the Name, Node ID, Location, Alarm High, Alarm Low, Alarm Delay, Node Type, Value, Graph (readings taken within a 24-hr time period), Last Updated (date and time stamp), Value Status (In/Out of Range), Connectivity Status (Connected/Disconnected), Alarm Status (Alarmed/No Alarm), Notification Status (Active/Inactive), Speaker Symbol (to enable/disable audible alarms), and a Checkbox used in congruence with the “Audit Node” button at the bottom of the page to timestamp when users have viewed Nodes on this Current Status page. (See Audit Node for more information.)
The color legend is a great “at-a-glance” identifier of the Node’s current status. The Node’s row will highlight as one of the following colors: of the system. A row of cells with highlight in a color according to its status:Â
Green indicates all values are within range.Â
Yellow indicates temperatures/data are out of range, but the node has not yet alarmed due to the Alarm Delay feature (See Primary Alarm Limit for more information.)Â
Red indicates the node has a Data, Signal, or Battery Alarm.
Pink indicates a Suspended Alarm (See Suspend Alarm for info).Â
Blue indicates a Spare Node that is inactive on your account.Â
Grey  indicates RMA Nodes that have been shipped to your facility and need to be turned on and configured to Wi-Fi. (See Replace RMA Nodes for more information.)Â
Please note that occasionally the node may still present itself in the alarmed (red) state even if there is no out-of-range value, signal, or battery level issue. This can be due to the fact that an alarm condition existed and was triggered. The node would then enter an alarmed (red) state. There are two steps which must be taken respectively return the node to a Normal (green) state.Â
 The issue must be corrected so that the data is in range, the connection is established, and/or the battery is full.Â
The alarm must then be confirmed by going to the ALARM tab and confirming the alarm event.Â
Press on the printer icon to print the Current Status Page
Print Icon
Selecting the “24 Hrs” button in the “Graph” column will generate an interactive graph displaying the node’s readings taken within a 24-hr time period.
Once a node enters an alarmed (RED) state, all the associated alarms must be confirmed for the node to go back to a normal (GREEN) state. If the node is still displaying as RED on the “Current Status” page, ensure there are no alarms associated with the node by selecting the “Alarmed” button and viewing the “View Alarm” page. There are two steps which must be taken to return the node to a normal (GREEN) state:
The issue must be corrected so that the data is in range, the connection is established, and/or the battery is full.
The alarm(s) must be confirmed.
24-Hour Graph Button
24-Hour Graph
Users can confirm alarms either via the “Current Status” page or from the “ALARM” tab (See Confirm Multiple Alarms for more information.)
Users can confirm singular alarms through the “Current Status” page. Once the system sends you a notification letting you know a node has alarmed, you should diagnose the situation at the node level then document the situation by confirming the alarm. (See Alarm Types for more information on corrective actions by alarm type.)
Select the “MONITORING” tab in the main menu.
Select the “Current Status” tab in the submenu.
Select the “Alarmed” button of the desired node.
The “View Alarm” page will display all active alarms associated with the node. Select the “Take Action” button of the desired alarm.
Diagnose the alarm by entering the Root Cause, Detail Description, Corrective Action, and answer the question, “Is the equipment working properly?”
Click the “Confirm” or “Suspend” button to diagnose the alarm.
When a node has an alarm, the “Alarmed” button will show up on the “Alarm Status” column of the “Current Status” page. Selecting the “Alarmed” button will take you to the Node’s “View Alarm” page which displays all active alarms associated with the node.
Select View Alarm
The table on the “View Alarm” page displays data such as Node Name, Node ID, Location, Node Type, Alarm Date (date and time of alarm), Alarm Type (Data/Signal/Battery Alarm), Graph (readings taken within a 24-hr time period of the alarm), and the Take Action button to confirm alarm.
View Alarm Page
“View Alarm” Page GraphÂ
By selecting the “Take Action” button, you will be taken to the “Diagnose Alarm” page where you can document the Root Cause, Detail Description, and Corrective Action for the alarm; as well as Suspend the Node from sending notifications by answering the question, “Is the equipment working properly?”
Root Cause
The Root Cause identifies general category for the reason for the alarm. SensoScientific provides standard root causes (Defrost Cycle, Equipment Lost Power, Device was restocked, and Other). System Admins can add/delete facility-specific Root Causes. (See Add/Delete Root Cause for more information.)
Detail Description
The Detail Description is used to provide circumstantial information that may give insight as to WHY the node experienced an alarm. This field is optional.
Corrective Action
The Correct Action text is the most important section. It is used to document the actions taken to rectify the situation.
Is the equipment working properly?
This Yes/No field will appear to account types with the privilege to suspend alarms. (See Suspend Node Privileges for more information.) Selecting “Yes” will allow you to confirm the alarm. Selecting “No” will generate a Suspend duration to postpone notifications for a selected time period. (See Suspend Alarm for more information.)
"Diagnose Alarm" Page
Current Status with Suspended Node
NOTE: This feature is reserved for users with System Admin account type privileges. (See User Level Type Permissions for more information.)
System Admins have the ability to add or delete Root Causes to the populated list for facility-specific situations or common occurrences. Standard root causes that are automatically generated include Defrost Cycle, Equipment lost power, Device was restocked, and Other. These root causes cannot be deleted or altered. To add a Root Cause:
Select the “MONITORING” tab in the main menu.
Select the “Current Status” tab in the submenu.
Click the “Alarmed” button for the desired alarmed node.
Click the “Take Action” button of the desired alarm.
Select the “Add” link next to the Root Cause drop-down list.
Enter the title of the Root Cause you would like to add to the list and select the “Add” button to confirm.
Similarly, System Admins can delete the root causes they have created. To delete a Root Cause:
Select the “MONITORING” tab in the main menu.
Select the “Current Status” tab in the submenu.
Click the “Alarmed” button for the desired alarmed node.
Click the “Take Action” button of the desired alarm.
Select a Root Cause from the drop-down list.
Select the “Delete” link to confirm.
Add Root Cause
NOTE: User types with the privilege to be able to suspend nodes is determined by the System Administrator through the Global Settings page. (See Suspend Node Privileges for more information.)
You can suspend a node from sending notifications for a designated time period through the “Current Status” page by following these directions:
Select the “MONITORING” tab in the main menu.
Select the “Current Status” tab in the submenu.
Select the “Alarmed” button of the desired node.
Select the “Take Action” button of the desired alarm.
Enter the Root Cause, Detail Description, Corrective Action, and select “No” for the question, “Is the equipment working properly?”
Select a Suspend Duration to postpone notifications for the selected time period.
Click the “Suspend” button to confirm the suspend duration.
Suspend Alarm
To re-suspend an alarm, follow the same directions used to suspend the alarm originally. The new Suspend Duration will override the previous suspend duration.
Select the “MONITORING” tab from the main menu.
Select the “Current Status” tab from the submenu.
Select the “Alarmed” button of the desired node.
Select the “Take Action” button of the desired alarm.
Enter the Root Cause, Detail Description, Corrective Action, and select “No” for the question, “Is the equipment working properly?”
Select a Suspend Duration to postpone notifications for the selected time period.
NOTE: This feature must be enabled by System or Group Admins through the Node’s configured settings. (See Audit Node Function for more information.)
From the “Current Status” page, users can audit nodes, creating a timestamp that they have logged in to the cloud and viewed the “Current Status” page. System and Group Admins can then generate a report showing audited nodes through the Audit Node Report. (See Audit Node Report for more information.)
Select the “MONITORING” tab from the main menu.
Select the “Current Status” tab in the submenu.
Mark the checkboxes in the right-most column of the desired nodes.
Click the “Audit Node” button at the bottom of the page.
Audit Node
By default, alarms trigger an audible speaker to turn ON to alert users that either a battery or data alarm has occurred (Signal alarms will not cause the audible alarm to sound). This can be permanently silenced from the device or the cloud. This will cause the node to trigger silent alarms when a battery or data alarm has occurred. All other notifications will be sent to the applicable users (email, SMS, etc…). To change the audible alarm settings, go to the MONITORING tab.Â
Silence Audible Alarm
Audible Symbols