IQ/OQ for Vaisala viewLinc Monitoring System

Page 1 of 161

IQ/OQ
Installation/Operational Qualification Protocol

Vaisala viewLinc Enterprise Server Software Version 5.0

Document #: M211911EN-A

Date Prepared: March 30, 2018

Prepared by: Paul Daniel,

Senior Regulatory Compliance
Expert

Reviewed by: Steven Bell,

Product Manager

© 2018 Vaisala
 IQ/OQ for Vaisala viewLinc Monitoring System
Page 2 of 161

Protocol Pre-approval
This Protocol has been reviewed and approved by the following individuals and is ready for
execution. Signing this Protocol indicates that the contents of this document have been
reviewed, all test procedures are appropriate and the acceptance criteria are applicable for the
intended purpose of this Protocol. The following responsible functional areas have approved
this Installation/Operational Qualification Protocol for the Vaisala viewLinc Monitoring System
software:

Approved By:

Information Technology Date

Operations Date

Quality Assurance Date

© 2018 Vaisala
 IQ/OQ for Vaisala viewLinc Monitoring System
Page 3 of 161

Disclaimers and Prerequisites

• This Protocol is a ready-to-use template. It may be executed with no changes. The Protocol
may be edited to match the needs of a particular customer. Care must be taken in editing to
avoid making material changes to the test procedures. Test discrepancies may occur if the
test procedures are altered.
• Prior to execution of this Protocol, the following conditions must be met:
• All devices (data loggers and transmitters) have been attached to the system via
a USB cable, Ethernet Adaptor, Wi-Fi, or VaiNet connection.
• All cables being used that require drivers have been properly installed on the
viewLinc Enterprise Server.
• All Ethernet Adaptors (vNet/Digi/Moxa) being used have been set up with IP
addresses and correct network information, and have had the appropriate drivers
installed on the viewLinc Enterprise Server.
• All computers used as Enterprise Server, Host Device Servers, or clients, in the
Vaisala viewLinc Monitoring System, must meet the applicable minimum
requirements as specified in the viewLinc User Guide.
• Prior to approval and execution of this Protocol, refer to vaisala.com/viewLinc-Errata to
review known issues related to viewLinc software or viewLinc protocol documentation.
• Administrative access to the desktop of the viewLinc Enterprise Server is required to
complete some sections of this Protocol.
• Two connected devices with temperature channels are recommended to execute the
Protocol. A single device may be used, provided that two temperature channels are
available on the device.
• Unless otherwise specified, the procedures in this Protocol assume that devices on the
system use a five (5) minute sample interval. Test discrepancies may occur if different
sample intervals are used.
• The data connection between test data loggers and the viewLinc Enterprise Server must
not become disconnected during testing (unless otherwise specified within the test
procedure).
• DL-series data loggers used in this Protocol must not be linked to vLog audit trails , as
discrepancies relating to Logger and Channel description modifications may occur.
• Events may not be written to the Event Log immediately. If an expected event does not
appear in the log, wait a few minutes then advance the end time of the log and refresh the
event list.
• When representations of data appear in this Protocol, text surrounded by <angled
brackets> will be replaced by data specific to your installation.
• The procedures in this Protocol may not leave the system in an ideal configuration for your
particular application, especially in the case of an upgrade from a previous version. Review
and modification of the system configuration, settings, and templates is highly
recommended following validation.
Vaisala
Email: [email protected]
Web: www.vaisala.com/en/lifescience
© 2018 Vaisala. All rights reserved. Product and company names listed in this document are trademarks or
trade names of their respective companies.

© 2018 Vaisala
 IQ/OQ for Vaisala viewLinc Monitoring System
Page 4 of 161

Table of Contents
Purpose.......................................................................................................................................... 6
1.1 Installation Qualification ......................................................................................................... 6
1.2 Operational Qualification ........................................................................................................ 6
Responsibilities ............................................................................................................................. 6
2.1 Vendor Responsibilities .......................................................................................................... 6
2.2 User Responsibilities.............................................................................................................. 6
System Description ....................................................................................................................... 6
Objective ........................................................................................................................................ 7
Validation Approach ..................................................................................................................... 7
5.1 Basic Risk Assessment .......................................................................................................... 7
5.2 Installation Qualification (IQ) .................................................................................................. 8
5.3 Operational Qualification (OQ) ............................................................................................... 8
5.4 Performance Qualification (PQ) Considerations ..................................................................... 8
5.5 Other Considerations ............................................................................................................. 8
Documentation Procedures .......................................................................................................... 9
6.1 Good Documentation Practices.............................................................................................. 9
6.2 Execution Guidance ............................................................................................................. 10
Installation Qualification .............................................................................................................. 11
7.1 Test Plan .............................................................................................................................. 11
7.2 Vaisala Software Verification ................................................................................................ 13
7.3 Vaisala Documentation Verification ...................................................................................... 15
7.4 Customer Quality System Documentation Verification .......................................................... 18
7.5 Server Hardware Requirements Verification ......................................................................... 20
7.6 Software Installation Verification ........................................................................................... 23
7.7 Email Configuration Verification ............................................................................................ 26
7.8 SMS Configuration Verification ............................................................................................. 28
7.9 System Hardware Configuration Verification......................................................................... 30
7.10 Sensor Calibration Verification ............................................................................................. 32
IQ Final Approval ......................................................................................................................... 35
Operational Qualification ............................................................................................................ 36
9.1 Test Plan.............................................................................................................................. 36
9.2 Event Log and Audit Trail Verification ................................................................................... 39
9.3 User Creation and Password Verification.............................................................................. 42

© 2018 Vaisala
 IQ/OQ for Vaisala viewLinc Monitoring System
Page 5 of 161

9.4 Group Creation and Assignment Verification ........................................................................ 46

9.5 Security Preferences Verification .......................................................................................... 48
9.6 Security Rights Verification ................................................................................................... 51
9.7 Access Permissions Verification ........................................................................................... 57
9.8 Notification and Threshold Template Verification .................................................................. 65
9.9 Email Alarm Notification Verification ..................................................................................... 70
9.10 SMS Alarm Notification Verification ...................................................................................... 76
9.11 Low Threshold Alarm Verification ......................................................................................... 82
9.12 High Threshold Alarm Verification ........................................................................................ 87
9.13 Multi-Threshold Verification .................................................................................................. 92
9.14 RFL100-Series Local Threshold Verification ........................................................................ 98
9.15 HMT140-Series Local Threshold Verification ...................................................................... 103
9.16 Notification Escalation Verification...................................................................................... 109
9.17 User Schedule Verification .................................................................................................. 115
9.18 Threshold Schedule Verification ......................................................................................... 121
9.19 Alarm Pause Verification .................................................................................................... 125
9.20 Communication Alarm Verification ...................................................................................... 129
9.21 Configuration Alarm Verification ......................................................................................... 133
9.22 Host Communication Alarm Verification .............................................................................. 138
9.23 Data Presentation Verification ............................................................................................ 142
9.24 Calculation Verification ....................................................................................................... 145
9.25 Time Zone Verification ........................................................................................................ 149
9.26 System Watchdog Verification ............................................................................................ 153
OQ Final Approval ..................................................................................................................... 158
Signature ID Form ..................................................................................................................... 159
IQ/OQ Final Approval ................................................................................................................. 160
Revision History ........................................................................................................................ 161

© 2018 Vaisala
 Purpose
The purpose of this Installation / Operational Qualification (IQ/OQ) Protocol is to provide assurance that
the Vaisala viewLinc Monitoring System has been set up properly, is fully functional, and operates with
a high degree of integrity, security, and reliability.
This document is provided in Microsoft Word document format for customization, and as a secure
PDF for use without changes. Both documents are located on the provided USB drive.
1.1 Installation Qualification
The Installation Qualification (IQ) portion of the Protocol was written, executed, and approved to ensure
that the system, composed of both hardware and software elements, has been installed correctly at the
point of use, per the manufacturer’s specifications. The IQ will capture the hardware baseline of the
system, including relevant configuration information. The IQ will also verify the presence of the basic
Quality System elements necessary to support system operation in a GxP environment.

1.2 Operational Qualification

The Operational Qualification (OQ) section of the Protocol was written, executed, and approved to
ensure that each component of the system operates as intended, per the manufacturer's specifications.

Responsibilities
The responsibilities listed below apply only to the creation and execution of this validation Protocol. If
the user chooses to contract out any of the activities associated with the listed responsibilities, sole
responsibility will continue to rest with the user.
2.1 Vendor Responsibilities
Vaisala is responsible for the following:
• IQ/OQ Protocol template creation
2.2 User Responsibilities
User (____________________________________________) is responsible for the following:
• Equipment maintenance
• Ensuring calibrated status of unit(s)
• Protocol pre-approval
• Protocol execution and reporting of results
• Protocol execution deviations, assessment, and corrective measures
• Protocol and report review
• Protocol and report approval

System Description
The Vaisala viewLinc Monitoring System is a server-based, real-time environmental monitoring,
alarming, reporting, and data collection system. The system consists of discrete, self-contained,
microprocessor- based data collection devices (data loggers and transmitters) and a PC-compatible
software reporting system for monitoring and recording temperature and relative humidity in regulated
environments.
Additional types of data input may be monitored by the system with the appropriate Vaisala sensors.

The system is comprised of Vaisala viewLinc Enterprise Server 5.0 software; a Microsoft Windows®

© 2018 Vaisala
 based PC or server; client PCs with an approved web browser; Vaisala data loggers and transmitters;
and connectivity cabling.
The Vaisala viewLinc Monitoring System consists of Server and Client components. For the purposes
of the Protocol, a Server is the computer on which the viewLinc software is installed. The Server
component is the core of the Vaisala viewLinc Monitoring System. It controls the central database, web
server, system configuration, alarming, and other functions. The Clients are standard web browsers
(such as Microsoft Internet Explorer) operating on workstations on the LAN, which connect to the
Server in order to view real-time conditions at the points being monitored, or to make configuration
changes.
The Vaisala viewLinc Monitoring System supports the use of a variety of Vaisala devices, including
Vaisala DL data loggers, Vaisala VaiNet data loggers, Vaisala HMT140-series data loggers, and
Vaisala 300 series transmitters.
The Vaisala viewLinc Monitoring System also includes user-based security and unique file identifiers for
data integrity. The Vaisala viewLinc Monitoring System allows the end user to set alarm thresholds and
notifies the end user through multiple formats (email, SMS, etc), when an alarm condition is triggered,
acknowledged, or when a data logger communication problem exists. The software has built-in trending
functions, and can generate Location data, alarm history, and system configuration reports.

Objective
The objective of this Protocol is to qualify the installation and operation of the Vaisala viewLinc
Monitoring System at
_____________________________________________________________________________.
This Protocol will verify the proper installation, correct functionality and operation of the Vaisala
viewLinc Monitoring System according to manufacturer’s specifications and the requirements of
_____________________________________________________________________________.

Validation Approach
5.1 Basic Risk Assessment
Basic risk assessment philosophy requires that the focus of a validation effort be on the functions most
likely to fail, or those functions with the greatest consequence of a failure.
All viewLinc system elements are considered reliable and were extensively tested in development.
However, configured functions in any system are considered to be more likely to malfunction than
nonconfigured elements.
There are two basic business processes in viewLinc with critical impact on the quality of products in
controlled storage: 1) the collection of the environmental data itself, and 2) any alarm functions to
identify problems, either with the data collected, or with the data collection process itself. Therefore,
testing in this IQOQ Protocol will focus on the two highest risk activities performed by the system (Data
Collection and Alarming) with an emphasis on configurable functions. Peripheral functions will be
included in the testing where they impact the operation of these two critical areas.
All functions not related to Data Collection and Alarming are considered low risk, and may not be tested
in this IQOQ Protocol. These low-risk functions have been thoroughly tested by Vaisala in Unit and
Module testing during development and do not require additional testing in the installed environment.

© 2018 Vaisala
5.2 Installation Qualification (IQ)
The IQ will verify the presence of the minimum Quality System elements considered necessary for basic
system operation. This will be done by verifying the presence of system documentation and supporting
SOPs. Several documentation items to be verified are considered to be customer responsibilities, such
as a Monitoring SOP or a Calibration Program, and will not be supplied by Vaisala. Furthermore, this
verification is not definitive of all documentation that is appropriate or that should be present.
The IQ will document the baseline hardware (data loggers, transmitters, Ethernet adaptors, and servers)
associated with the Vaisala viewLinc Monitoring System, and the configuration of these items to function
on the customer network. It does not document the baseline configuration of the Local Area Network, or
LAN, which may be comprised of additional network equipment, such as switches, routers, and servers.
It is assumed that the qualification of the network has either been performed under the auspices of
another test document, or that such testing has been deemed unnecessary by the user for this
application.
The IQ will document the correct installation of the viewLinc software and record critical installation
parameters.

5.3 Operational Qualification (OQ)

The OQ portion of the IQOQ Protocol documents the correct operation of Vaisala viewLinc software
relative to the manufacturer’s specifications, with specific attention to the configurable aspects of the
software, and to those software operations requiring interaction with the server Operating System, and
the network environment.The tests in this Protocol simply verify that the devices under test respond as
expected to outputs from the Vaisala viewLinc Monitoring System. Refer to the System Description
section of document #M211911.
A risk-based approach, following the rationale presented in section 4.1 will focus OQ testing on the two
highest risk areas of the system: Data Collection and Alarming.
The correct run-time configuration of the data collection process will be verified in the IQ activities
described above. System security, where pertinent to the process and configuration of data collection,
will be verified in the OQ. Furthermore, the data reporting process and the accuracy of the associated
statistics will be verified.
The alarming functions of the software will be tested at arbitrary configured values to demonstrate
functionality in the operating environment. This will include both system alarms (which may indicate
conditions that would compromise accurate and gap-free data collection) as well as threshold alarms
(which may indicate out-of-limit conditions).

5.4 Performance Qualification (PQ) Considerations

The OQ portion of the IQOQ Protocol does not verify the functionality of any specific configuration that
may be adopted for use of the system. It is assumed that if qualification of a specific configuration is
required, a Performance Qualification (PQ) will be performed in addition to this IQOQ document. Such
PQ testing is considered to be outside the scope of this document.

5.5 Other Considerations

The Protocol is written with the expectation that the tester is familiar with the operation of the viewLinc
system. For additional detail to assist in any test steps, refer to the relevant section of the viewLinc User
Guide, viewLinc online Help, or viewLinc embedded Tours.
A ‘black box’ approach to testing is utilized within the IQOQ Protocol to demonstrate the consistent and
reliable function of the various configurable features in viewLinc.

© 2018 Vaisala
 From the perspective of the viewLinc system, any single input is identical to any other input whether it is
derived from a channel from a Vaisala DL data logger, a Vaisala HMT140-series data logger, Vaisala
VaiNet data logger, or a Vaisala 300 series transmitter. Every input is simply a digital data stream. As a
result, it is only necessary to test each function on a single input to have confidence the function will
operate correctly for all inputs.
Vaisala HMT140-series data loggers and Vaisala VaiNet data loggers are unique among Vaisala
devices compatible with viewLinc, as they can store high and low thresholds locally in the data logger
memory. This capability ensures local alarming in the event of disconnection of these wireless devices,
which could prevent the generation of an alarm from the viewLinc Server. In this Protocol, the ability to
adjust the local thresholds will be verified, and the resulting local alarm will be verified for a single
HMT140-series data logger (if applicable) and a single VaiNet data logger (if applicable). However, since
these devices are slaved to the viewLinc Enterprise Server, it is only considered necessary to test the
viewLinc Enterprise Server functions in this IQOQ. Specific testing of local thresholds for each individual
data logger is considered to be performance testing appropriate for a PQ, and therefore out of scope of
this IQOQ.
Two connected devices with temperature channels are recommended to complete the testing described
in this Protocol. A single device may be used, provided it has a minimum of two temperature channels.
The temperature channels must be configured to display Celsius.
In this Protocol, bold text is used to refer to items and text that are visible on the viewLinc interface, such
as Location Names, User Names, Report Names, Template Names, etc.
The computer used to access the viewLinc system for execution of this Protocol must have specific
software installed. Refer to the viewLinc User Guide for a comprehensive list of compatible software.
The following software is required:
• A viewLinc compatible web browser.
• A spreadsheet application, such as Microsoft Excel, capable of opening .tsv files.
• A PDF reader application, such as Adobe Reader, capable of opening .pdf files.

Documentation Procedures
6.1 Good Documentation Practices
Data generated during the execution of this Protocol will be collected and recorded on the datasheets
provided.
Actual results will be recorded at the time of observation. The Protocol is designed to either accept
handwritten data entry, or handwritten indication of a YES or NO answer. In all cases, a NO answer will
be considered to indicate a failed step.
During the execution, the executor’s initials and date will be provided at the time of completion for each
activity.
Handwritten data is to be neatly printed using a black or blue ball point pen. Corrections are to be
crossed out with a single line, initialed, and dated. If the reason for the correction is not obvious, an
explanation for the correction will be included.
Charts, printouts, notes etc. generated during the execution will be dated, signed, and attached to the
completed Protocol document.
All test sections will be reviewed and signed by appropriate __________________________________
personnel to verify document completeness.
Throughout this document, the use of "N/A" and "U/A" shall be interpreted as "not applicable" and
"unavailable", respectively. A written explanation must be provided whenever "N/A" or "U/A" is used,
except where "N/A" is used as the result of explicit test instructions.
• When instructed to mark a test step as "N/A", line out the entire row, mark "N/A" and add
© 2018 Vaisala
 your Initial and Date.
• When instructed to mark a test section as "N/A", line out the entire test table on each
relevant page, mark "N/A" and add your Initial and Date. Add a comment explaining the
reason for not executing the test section.
Pages may be photocopied as needed in order to complete additional testing or perform testing required
to resolve deviations/discrepancies. Additional pages must be numbered appropriately to identify them
as extra pages and to identify the order in which they appear. Identification shall be applied using
alphabetical characters next to the page number and a numeric group annotation to the right of the
page number as it appears in the header. For example, if three (3) additional copies of page seven (7) of
a forty-one (41) page document are required, the page numbering shall be annotated to read as follows:
"Page 7A of 41, Additional page 1 of 3" for the first additional page, "Page 7B of 41, Additional page 2 of
3" for the second additional page, and so on.
Throughout this document, it is necessary to attach additional documents, such as Event Logs, reports,
etc. All attachments should be clearly labeled with the following information on the first page: Document
Number (for example, M211911EN-A), reference section and step (for example, Section 8.6, Step 12),
total number of pages (for example, 6 pages), and the Date/Initial of the test executor.
Protocol Definitions:
• A discrepancy is defined as a difference between the expected results and the actual
results.
• An exception is defined as a difference between the approved Protocol procedure and the
procedure followed in testing.
• A deviation is defined as a discrepancy or exception that prevents meeting the
acceptance criteria.
• Discrepancies, exceptions, and deviations to approved Protocols may occur. It is the
responsibility of the qualification group to document each deviation, exception, or
discrepancy and to provide an explanation of the circumstances that led to said deviation,
exception, or discrepancy. They should be documented in the space provided in each test
section, or utilize the relevant user SOP for Deviation Reporting (if applicable).
• Deviations, exceptions, and discrepancies must be approved by the Quality Assurance
group according to current customer standard operating procedures, prior to any further
execution of the Protocol test section in which the deviation occurred.

6.2 Execution Guidance

The IQ Test Sections of the document should be completed prior to beginning the OQ Test Sections.
However, the following IQ test sections do not need to be completed prior to initiating OQ testing:
• Vaisala Documentation
• Customer Quality System Documentation
• Calibration Verification
• IQ Final Approval
The Test Steps outlined in Test Procedures must be performed in sequence within a given Test
Section. It is recommended that the Test Sections be performed in sequence. If necessary, the Test
Sections within the OQ may be performed out of sequence; however, test sections 8.2, 8.3, and 8.4
must be performed in sequence, and are prerequisites for all later test sections.
Certain OQ Test Procedures require a specific test configuration that may require the user to perform
data entry and/or verify a configuration. In these instances the test procedure will refer to the
Configuration Table located at the end of each test section, after the Comments and Acceptance
Criteria. Only relevant configuration parameters will be included in the Configuration Tables. If a

© 2018 Vaisala
 parameter is not included, it may be left at the default value.
Certain OQ Test Procedures involve timestamp comparisons between timestamps recorded by the
tester (using the viewLinc onscreen clock in HH:MM format), timestamps recorded by the viewLinc
system on reports and event logs (using timestamps in HH:MM:SS format with date), and timestamps
for events recorded by outside systems (such as external email providers). When such timestamps are
compared, they will not be identical due to different source clocks and inherent sources of network lag.
Therefore, it is not required that timestamp comparisons be identical. However, timestamps must
correspond in terms of order of operations, and small time differences will be considered acceptable as
follows:
• Comparison between viewLinc timestamps are considered acceptable with a lag of no more
than 2 minutes.
• Comparison between viewLinc timestamps and external timestamps are considered
acceptable with a lag of no more than 5 minutes. Additional lag should be investigated to
determine the actual time difference between the source clocks.
Certain OQ Test Procedures involve verification that test steps and resulting system actions are
accurately captured in the Event Log. In these instances, it is not necessary that the Event Log text
match the test description. Event Log entries must convey the following:
• General event description
• Event occurred without error
• Event timestamp
• Identity of the correct user (if applicable)
• Data before/after change (if applicable)

Installation Qualification
7.1 Test Plan
Testing will be performed to verify that the installation of the Vaisala viewLinc Monitoring System is in
conformance with manufacturer’s specifications and customer requirements. The test plan consists of
these nine (9) sections:
Vaisala Software Verification
System software is considered a basic requirement for proper maintenance of a GxP computerized
system. This test section will verify that the necessary system software is available and securely stored.
Vaisala Documentation Verification
Vendor documentation is considered a basic requirement for proper maintenance of a GxP
computerized system. This test section will verify that the necessary Vaisala documentation for the
viewLinc software and sensors is available and securely stored.
Customer Quality System Documentation Verification
Customer Quality System documentation is considered a basic requirement for proper operation of a
GxP computerized system. This test section will verify that the Quality System documentation to support
the viewLinc system is available and securely stored.
Server Hardware Requirements and Configuration Verification
The viewLinc server must meet the recommended hardware requirements to ensure satisfactory
performance. This test section will verify that the viewLinc server meets the recommended hardware
requirements for the viewLinc Enterprise Server software.
Software Installation Verification
The viewLinc software must be correctly installed to allow for proper system operation. Capturing the
© 2018 Vaisala
installation variables also allows for easier system recovery and provides a baseline for future change
control. This test section will capture the software installation variables.
Email Configuration Verification
Email is the primary means by which the viewLinc system communicates with users when they are not
actively logged into viewLinc. The capability to successfully send an email is dependent on multiple
network parameters outside the viewLinc system. This test section will verify that email parameters in
viewLinc have been configured to interact correctly with the host network to allow emails from the
viewLinc system to be sent.
SMS Configuration Verification
SMS (Short Message Service) is a secondary means by which the viewLinc system communicates with
users when they are not actively logged into viewLinc. The capability to successfully send an SMS is
dependent on the presence of an installed SMS modem with an active service plan. This test section
will verify that SMS parameters in viewLinc have been configured to interact correctly with the modem
and service plan to allow SMS messages to be sent by the viewLinc system.
Calibration Verification
The viewLinc system depends on accurate measurements. This test section will verify that devices
installed on the viewLinc system have a current calibration and a valid calibration certificate.
System Hardware Configuration Verification
This section will verify that new viewLinc system hardware elements are correctly installed and are
recognized in the viewLinc system.

© 2018 Vaisala
IQ Final Approval
The procedures in this section have been implemented, reviewed, and approved by the individuals
listed below. All results have been documented and all deviations have been identified, documented,
reviewed, and approved.
The final approvers should be the same as the original protocol approvers, when available.

Implemented by (signature): Date:

Name (print):

Title:

Company:

Reviewed by (signature): Date:

Name (print):

Title:

Company:

Approved by (signature): Date:

Name (print):

Title:

Company:

QA approved by (signature): Date:

Name (print):

Title:

Company:

© 2018 Vaisala
 Operational Qualification
9.1 Test Plan
Testing will be performed to verify that the operation of the Vaisala viewLinc Monitoring System is in
conformance with manufacturer’s specifications and customer requirements. The Acceptance Criteria
for all sections are derived from Vaisala recommendations. The test plan will consist of twenty-five (25)
areas of functionality defined below:
Event Log Verification
viewLinc 5.0 has an Event Log in which it records events occurring in the system. The Event Log is also
an Annex 11/Part 11 compliant Audit Trail to record changes to electronic records in the viewLinc
application. This test will verify that the Event Log accurately and effectively records instances of record
creation, modification, and deletion.
User Verification
viewLinc 5.0 utilizes user accounts to control access to viewLinc. Each user must be created and
assigned various rights and permissions to control what actions the user can perform, and what areas
may be accessed by the user. This test will verify that users can be created in viewLinc, and that the
created users may access the viewLinc application to maintain an individual user profile.
Group Verification
viewLinc 5.0 utilizes Groups to simplify management of user accounts and access to viewLinc. Each
group must be created and assigned various rights and permissions to control what actions the member
users can perform, and what areas may be accessed by the member users. This test will verify that
groups can be created in viewLinc, and assigned rights and members.
Security Preferences Verification
viewLinc 5.0 utilizes settings known as Preferences to control global features within viewLinc. Two of
the preferences options directly affect security and transparency within the system, by controlling repeat
authentication and commenting. This test will verify that the system requires authentication and
commenting when configured to require these actions.
Security Rights Verification
viewLinc 5.0 utilizes Rights to determine general user abilities within viewLinc. Rights cannot be
assigned to users directly, and may only be assigned to groups which may include any number of
users. This test will verify that users may only perform those abilities in viewLinc that have been
specifically granted to the members of a group that includes the user.
Access Permissions Verification
viewLinc 5.0 utilizes Permissions to limit access to Zones and Locations. Permissions may be assigned
to groups only, and users receive only the permissions granted to groups in which they are members.
This test will verify that users may only access and control those Zones and Locations in viewLinc that
have been specifically permitted to the user by their group membership.
Notification and Threshold Template Verification
viewLinc 5.0 provides notification and threshold templates to simplify the management of threshold
alarming in viewLinc. This section will verify the management of threshold alarms using Alarm
Notification and Threshold Alarm templates.
Email Notification Verification
Email notification is the primary mode used by viewLinc 5.0 to communicate events to system users
when they are not actively logged in to the system. This section will specifically test the generation of
alarm notification emails in response to an alarm condition.
SMS Notification Verification
SMS notification is another mode by which viewLinc 5.0 can communicate events to system users
when they are not actively logged in to the system. Use of this feature requires an active SMS modem

© 2018 Vaisala
be installed on the viewLinc server. This section will specifically test the generation of alarm SMS
notifications in response to an alarm condition.
Low Threshold Alarm Verification
An important function of viewLinc 5.0 is the generation of threshold alarms when monitored conditions
are found to be below specified limits. This section will specifically test the activation of Low Threshold
Alarms.
High Threshold Alarm Verification
An important function of viewLinc 5.0 is the generation of threshold alarms when monitored conditions
are found to be above specified limits. This section will specifically test the activation of High Threshold
Alarms.
MultiLevel Threshold Verification
Management of threshold settings in viewLinc 5.0 is simplified with the use of Multi-Thresholds. This
section will specifically test the generation of multiple threshold alarms configured using the Multi-
Threshold feature.
RFL100-Series Local Threshold Verification
Vaisala RFL100-series data loggers have the capability to store HighHigh, High, Low, and LowLow
thresholds locally in the data logger memory for each channel. This test section will verify the ability to
manage local thresholds in a RFL100-series data logger. In addition, the functioning of the local
thresholds will be verified for a single RFL100-series data logger.
HMT140 Local Threshold Verification
Vaisala HMT140-series data loggers have the capability to store high and low thresholds locally in the
data logger memory for each channel. This test section will verify the ability to manage local thresholds
in an HMT140-series data logger. In addition, the functioning of the local thresholds will be verified for a
single HMT140-series data logger.
Notification Escalation Verification
An important function of viewLinc 5.0 is the generation of threshold alarms when monitored conditions
are found to be below specified limits. This section will specifically test the activation of Low Threshold
Alarms.
User Schedule Verification
viewLinc 5.0 is designed primarily as a continuous monitoring system. Some users will desire not to be
notified when they are not on duty. For these users, viewLinc uses a scheduling function to define when
notifications will be sent to a given user. This section will specifically test the application of the
scheduling function to a user.
Threshold Schedule Verification
viewLinc 5.0 is designed primarily as a continuous monitoring system. Some applications require
monitoring that is not continuous. For these applications, viewLinc uses a scheduling function to define
when threshold alarming will be active for a given Location. This section will specifically test the
application of the scheduling function to a threshold alarm.
Alarm Pause Verification
viewLinc 5.0 provides the ability to pause alarms to assist in the management of active alarms. This
section will verify the pause alarm functionality in viewLinc.

© 2018 Vaisala
 Communication Alarm Verification
viewLinc collects data from a network of sensors. Consistent communication with the sensors is vital to
ensure that all data, and the resulting alarming functions, are up to date. If viewLinc loses connection
with a sensor, it can generate a communication alarm to notify system users that communication has
been lost. This test will challenge the communication alarm functions in viewLinc.
Configuration Alarm Verification
viewLinc 5.0 collects data from a network of data loggers. The condition of the data loggers is
continually evaluated by viewLinc. If viewLinc detects an error in a data logger that will affect data
collection, a Configuration Alarm may be generated. For instance, a Configuration Alarm would be
generated for a missing sensor probe, or expected historical samples missing from the data logger
memory. This monitoring of the data loggers helps ensure consistent data collection within the viewLinc
system. This test will challenge the Configuration Alarm functions in viewLinc.
Host Communication Alarm Verification
viewLinc 5.0 collects data from a network of sensors. The network of sensors are often connected by
intermediate server hosts to improve performance for large systems. For RFL100-series data loggers,
an access point serves as a host for connection to the viewLinc system. Consistent communication with
the hosts is vital to ensure that all data, and the resulting alarming functions, are up to date. If viewLinc
loses connection with a host, it can generate a communication alarm to notify system users that
communication to the specific host has been lost. This test will challenge the host communication alarm
functions in viewLinc.
Data Presentation Verification
The primary way to view historical data in viewLinc 5.0 is with the Location History Report. This is a
presentation quality report that is highly adaptable and can be easily configured to meet the needs of
multiple users. Data can also be viewed in the Trends window, providing immediate access to data
graphs.
Calculation Verification
viewLinc 5.0 can provide a standard suite of general statistics with the Location History Report,
including Average, Standard Deviation, and Mean Kinetic Temperature (MKT). In addition, the Alarm
Report performs basic calculations to determine Maximum and Minimum values during an alarm period.
This test will verify the calculations performed by viewLinc within the Location History and Alarm
reports.
Time Zone Verification
viewLinc 5.0 is designed to support an enterprise installation involving devices and client PCs in time
zones different than the time zone of the viewLinc Enterprise Server. This test section challenges the
functions of the viewLinc software that pertain to localization of time settings.
System Watchdog Verification
viewLinc 5.0 is supported by a Watchdog Service, which monitors the viewLinc application and restarts
it automatically in the event of a problem. This test section will verify the ability of the System Watchdog
to restart the viewLinc Enterprise Server after being manually stopped. In addition, an in-process
Communication Alarm will be interrupted by the shutdown and verified to continue notification following
the shut-down and restart.

© 2018 Vaisala
9.2 Event Log and Audit Trail Verification
Goal
viewLinc 5.0 has an Event Log in which it records events occurring in the system. The Event Log is also
an Annex 11/Part 11 compliant Audit Trail to record changes to electronic records in the viewLinc
application. This test will verify that the Event Log accurately and effectively records instances of record
creation, modification, and deletion.

Rationale
The Audit Trail function of the Event Log will be challenged by creating, editing, and deleting a new and
unused Location in viewLinc. Evidence will be documented to show that the Event Log accurately
records the events, including the timestamps, the identity of the user, and before and after values within
the record. Please note that monitoring data records cannot be created, accessed, or altered by any
user, and therefore are not included in this test of the Audit Trail.

Prerequisites/Guidance
The following prerequisites and guidance apply to this test:
• This test procedure is written with the assumption that the tester is an experienced user of the
viewLinc application. Utilize the viewLinc User Guide or online Help to gain familiarity with the
viewLinc functions required for this test procedure (see “Events”).
• Read the test procedure prior to executing the test procedure.
• All test steps shall be performed by a user with administrative access.
• When instructed to record the current time, record the HH:MM clock display in viewLinc
window header. When instructed to record a timestamp, record the timestamp associated with
the record or event under test.

Event Log and Audit Trail Verification

Test Instructions Actual Results Initials / Date
1. Create a new temperature Location in viewLinc 1a User name:
and save the change. Do not link the Location to
a device. Record the following items:
• User performing action 1b Location name:
• New Location name
• Date / Time of save action
1c Date / Time:

2. Edit the name of the new Location. Save the 2a Location name:
change. Record the following items:
• Edited Location Name
• Date / Time of save action 2b Date / Time:

3. Delete the edited Location. Save the change. 3a Date / Time:

Record the following items:
• Date / Time of save action

© 2018 Vaisala
Event Log and Audit Trail Verification
Test Instructions Actual Results Initials / Date
4. Locate the Event Log entry for the creation of 4a Event ID:
the Location in Step 1. Record the following
items:
• Event ID 4b User name:
• User performing action
• Location name
• Event timestamp
4c Location name:

4d Timestamp:

5. Locate the Event Log entry for the editing of the 5a Event ID:
Location Name in Step 2. Record the following
items:
• Event ID
• User performing action 5b User name:
• Properties before
• Properties after
• Event timestamp 5c Properties before:

5d Properties after:

5e Timestamp:

6. Locate the Event Log entry for the deletion of 6a Event ID:
the Location in Step 3. Record the following
items:
• Event ID 6b User name:
• User performing action
• Event timestamp
6c Timestamp:

7. Print and attach the Event Log page(s) that 7a Printout attached? Yes No
contain the events related to this test. 7b Attachment #:

8. Verify the recorded test data for the creation of 8a 1a agrees with 4b? Yes No
the new Location (Step 1) against the recorded
Event Log data: 8b 1b agrees with 4c? Yes No
• User performing action
8c 1c agrees with 4d? Yes No
• Location name
• Event timestamp
Verified test data may not be identical in
format.

© 2018 Vaisala
 Event Log and Audit Trail Verification
Test Instructions Actual Results Initials / Date
9. Verify the recorded test data for the editing of 9a 1a agrees with 5b? Yes No
the new Location (Step 2) against the recorded
Event Log data: 9b 1b agrees with 5c? Yes No
• User performing action 9c 2a agrees with 5d? Yes No
• Before value
• After value 9d 2b agrees with 5e? Yes No
• Event timestamp
Verified test data may not be identical in
format.
10. Verify the recorded test data for the deletion of 10a 1a agrees with 6b? Yes No
the new Location (Step 3) against the recorded
10b 3a agrees with 6c? Yes No
Event Log data:
• User performing action
• Event timestamp
Verified test data may not be identical in
format.

Comments/Deviations:

Acceptance Criteria Evaluation

Event Log and Audit Trail Verification: Event Log captures changes to electronic records, including the
date and time of the change, the identity of the person making the change, and the original and new
values.

Acceptance Criteria Met? PASS FAIL Initial/Date:

Reviewed Date:
By:

© 2018 Vaisala
OQ Final Approval
The procedures in this section have been implemented, reviewed, and approved by the individuals
listed below. All results have been documented and all deviations have been identified, documented,
reviewed, and approved.
The final approvers should be the same as the original protocol approvers, when available.

Implemented by (signature): Date:

Name (print):

Title:

Company:

Reviewed by (signature): Date:

Name (print):

Title:

Company:

Approved by (signature): Date:

Name (print):

Title:

Company:

QA approved by (signature): Date:

Name (print):

Title:

Company:

© 2018 Vaisala
 Signature ID Form
All personnel assigned to execute or review this executed Protocol, attached deviations, modifications,
and/or supporting documentation must sign and initial in the space provided below. Signature also
indicates the individual has read and understands the Protocol prior to task execution. In the
Title/Affiliation row fill in designated title and company name.

Printed Name Signature Title/Affiliation Initials/Date

Comments:

Implemented by:
Date:

Reviewed by:
Date:

© 2018 Vaisala
 IQ/OQ Final Approval
The Vaisala viewLinc Monitoring System has passed all tests, and as such, is qualified to be used in
the __________________________ environment:

Pass/Fail: ______ Initials: ______ Date: _______________

Initials: Date:
Reviewed by (signature):

Name (print):

Title:

Company:

Initials: Date:
Approved by (signature):

Name (print):

Title:

Company:

Initials: Date:
QA approved by (signature):

Name (print):

Title:

Company:

© 2018 Vaisala
Revision History
Date Revision Edited By Description

© 2018 Vaisala