User manual VAISALA VIEWLINC 3.5

[. . . ] Veriteq > > >> > viewLinc 3. 5 User Guide w w w. veriteq. com w w w. vaisala. com Copyright Copyright © 2010 Veriteq Instruments, Inc. No copying, distribution, publication, modification, or incorporation of this document, in whole or part, is permitted for commercial purposes without the express written permission of Veriteq Instruments, Inc. Veriteq, a Vaisala company 13775 Commerce Parkway Richmond, BC V6V 2V4 Canada Trademarks Veriteq Instruments, Veriteq, Veriteq vLog, Veriteq viewLinc, and Veriteq Spectrum are trademarks of Veriteq Instruments, Inc. All other trademarks referred to are the property of their respective owners. Disclaimer and Limitation of Liability Veriteq Instruments, Inc. [. . . ] There are several types of alarms in viewLinc: threshold alarms, communication alarms, event log validation alarms, and logger sampling alarms. If you are using validatable loggers, you may also receive logger validation alarms and calibration alarms. Using viewLinc, you can customize the alarm information that is issued for threshold, communication and logger alarms by configuring them from the System | Loggers tab. Threshold Alarms Threshold alarms notify users when conditions (such as temperature and relative humidity) are outside acceptable limits. To trigger threshold alarms when certain thresholds are exceeded, users with assigned permissions must configure them. Communication Alarms Communication alarms notify users when communication between a host (Logger Host or viewLinc Server) and its data loggers is down. This may be because viewLinc Server can not communicate with the logger, or the data logger connection to a host has been severed. Communication alarms serve as a system health test, alerting you if there is a problem that might disrupt viewLinc monitoring and alarming. 16 © 2010 Veriteq Instruments Inc. About Alarms Event Log Validation Alarms An Event Log Validation alarm indicates that the viewLinc event log historical data has been modified or tampered with and is therefore no longer validatable. Logger Configuration Alarms If you receive a Configuration Alarm, this indicates that your data logger has stopped recording data history or was configured incorrectly. This could be the result of being set to stop when full, a delayed start, or the logger could have an internal error. This alarm can also be triggered if a channel has been disabled in the logger using Spectrum or vLog. To correct this issue, you can verify or modify the data logger settings using vLog. If the problem persists, contact your Veriteq technical support representative. Logger Validation Alarms If you use a VL-type data logger, you'll receive a Validation alarm if the validation memory in the logger is corrupted or has been modified. Contact your Veriteq technical support representative. Logger Calibration Alarms If you use a VL-type data logger, Calibration Alarms send you intermittent notification when your data logger is due for calibration. You receive notifications at the following intervals: 3 months and 1 month before the calibration date, then again on the data logger's scheduled calibration date. This alarm will remain active until the logger has been recalibrated. What Happens When an Alarm is Triggered? When an alarm is triggered, several things can happen (depending on the configuration set by your administrator): · A pop-up can appear showing a description of the condition, and an alarm message. If pop-ups are blocked in your browser, an error message appears, prompting you to enable pop-ups for viewLinc. If configured, emails are automatically sent to the address (or addresses) specified when threshold limits are exceeded, communications are viewLinc 3. 5 User Guide 17 Chapter 3: Alarms interrupted, or an event log or logger alarm condition is present. Alarm emails can be sent repeatedly based on how alarm properties have been set. · An application can be launched or an external device turned on. If configured, an external device (such as a light or buzzer) or a computer application (such as batch file which can page or phone a particular number) can be triggered when an alarm condition occurs. Your administrator may also set up a tree alarm hierarchy, a method of notifying different individuals of an alarm if the first notification is not acknowledged within a specified time frame. Alarms should be acknowledged in viewLinc and the situation dealt with as soon as possible. All transactions are recorded in the Event Log and Historical database and can be viewed in an Event Log or Alarm report. Acknowledging Alarms All users can receive alarms, but only users with the correct permission can acknowledge alarms. If an alarm is set to require alarm acknowledgement, alarms must be acknowledged. [. . . ] This frequency -known as the sample interval -- is configured in Spectrum or vLog. With viewLinc you can monitor real-time conditions for Veriteq loggers over the network, analyze or graph changes in conditions over time, or compare conditions recorded by different loggers. This analysis is performed using the Reports tab. Generating Historical Data Reports viewLinc provides you with a set of graphical reports which can help you easily view trends in data readings or alarm monitoring statistics (such as alarm trigger frequency). · Alarm reports provide an overview of alarm events over a period of time (events related to every alarm are grouped together and presented in a readable form). [. . . ]