viewLinc Software Update Checklist

What’s in it for you? 

• Improved security options (modern encryption and authentication features).
• Better user management (including Active Directory integration and synchronization, where applicable).
• Enhanced alarming (earlier warning of potential issues and clearer handling of delayed or unrecoverable data situations).
• Global usability (expanded language support).
• Ongoing fixes and reliability improvements documented through errata and service updates.

How to plan, update, and stay audit-ready

Updating a monitoring system requires planning. This checklist helps you reduce risk, protect uptime, and confirm compliance while updating your Vaisala viewLinc Continuous Monitoring System. We’ve also included risk assessment checkpoints and validation considerations for regulated environments. 

1) Decide if you should update now

Use these questions to confirm if it is the right time for you to update.

☑ Is there a fix you need in the latest software?
A known issue, recurring problem, or support-recommended correction.

☑ Is there a security improvement you want?
Stronger encryption and authentication options, improved security controls, or alignment with current IT standards.

☑ Do you need a feature upgrade?
User management improvements, better alarming, language support, or hardware compatibility.

☑ Are you expanding your system?
New locations, new devices, or new requirements can be a good time to update.

☑ Can you schedule a controlled maintenance window?
Plan for change control, validation testing, and controlled downtime.

Risk Assessment Checkpoint: 

Before you commit to updating, assess these items: 

☑ Business risk of not updating (security, reliability, supportability, upcoming changes, etc.)

☑ Operational risk of updating (downtime tolerance, staffing, production schedule)

☑ GxP risk (impact to data integrity, audit trail, alarms, reporting, access control, compliance with new/revised regulations)

Deliverables: software Update Justification + Overall assessment of scope + Preliminary test strategy.

2) What you need before you start:

☑ Record your current viewLinc version, including the service update level (for example, 5.2 with Service Update 1 = 5.2.1).

☑ Confirm server details (OS version, hardware resources, and network access).

☑ Collect your viewLinc license key and installation media.

☑ Confirm certificate and URL requirements (hostnames, aliases, and allowed connection names).

☑ List all connected devices and integrations
Examples: AP10 Access points and other device hosts, OPC/Modbus devices, alarming methods: email/SMS/voice notification services, signal towers.

Optional but helpful: Create a one-page “system map” (server, devices, critical locations, integrations, notification paths).

3) Plan change control and validation (including risk assessment)

This step is key for validated monitoring systems: 

☑ Open a change control record for the update.

☑ Review release notes and errata for your target version and service updates.
Use them to document “what changed” and “why we updated.”

☑ Do a simple risk assessment – see checkpoint below. 
Identify what the update could affect: alarms, reports, audit trails, user access, integrations, and device communications.

☑ Define the validation approach/scope

• Full IQ/OQ execution, or
• Risk-based testing of impacted functions, following your quality procedures.
• Any Internal PQ requirements for your facility.

Support note: Vaisala provides documented update pathways and errata information to support change control and validation planning. We’ll help you define the parts of the system that are most important to revalidate after updating. 

Go/No-Go before execution

✔ Change control is approved.
✔ Validation scope and acceptance criteria are defined.
✔ Rollback/restore plan is documented.
✔ Maintenance window and required resources are confirmed. 

Risk Assessment Checkpoint: 

During Step 3 - Confirm what functions could change and define validation depth.

Assess these: 

☑ What may be impacted by the update: device communications, integrations with other systems, user authentication. Note that one of the best things about a viewLinc version update is that your installation is left intact. You aren’t starting from scratch. 

☑ Which components are changing (software only vs software + OS/server move + certificates/integrations)

☑ Needed test coverage: full IQ/OQ vs risk-based subset (per your Quality Management System), plus any facility-specific PQ needs

Output: Final test plan (or subset of the viewLinc IQ/OQ document from Vaisala), acceptance criteria, rollback plan, required approvals.

4) Protect uptime and data integrity

These steps are safeguards. In our technical note, we provide three methods for backing up your existing system. 

☑ Back up viewLinc and store backups in a secure location.

☑ Confirm current alarms are reviewed
Resolve or acknowledge any persistent historical-data alarms if applicable.

☑ Document baseline evidence (before update)
Examples: authentication functions, alarms function, key reports generate, audit trail is recording, critical locations are trending.

☑ Schedule the update window
Include time for upgrade, verification, and post-update validation tests.

Go/No-Go before installation

✔ Backups are completed and stored securely.
✔ Restore method is confirmed (or a restore test is completed).
✔ Baseline evidence is captured (login, alarms, audit trail, key reports).

5) Select the right update path

Different starting versions need different paths. We can help you through updating all previous versions of viewLinc to the latest version. But – things to know: 

☑ If you are on a recent version: you may be able to update directly to the current release.

☑ If you are on an older version: you may need an intermediate step before moving to the latest version.

☑ If you are moving to a new server: plan for data migration and certificate setup.

Best practice: If you are not sure which path applies, contact Vaisala. We will confirm the safest upgrade route for your current version.

6) Execute the update in a controlled way

Avoid improvising during any change to a validated system. Here’s how: 

☑ Confirm you have backups and approvals in place.

☑ Stop viewLinc services before making server-level changes.

☑  Install or upgrade viewLinc using the documented procedure for your scenario:

• upgrade on the existing server, or
• install on a new server and migrate data.

☑ Re-enable services and confirm the system starts normally.

☑ Log in as an administrator and confirm core functions.

7) Verify system operation after the update (The following verifications and tests are provided in detail in the Vaisala viewLinc IQOQ Protocol Templates)

Access & security

☑ Verify user login and role permissions.

☑ Confirm authentication and user management behave as expected (especially if using Active Directory integration).

Audit readiness

☑ Confirm audit trail events are created and searchable.

☑ Confirm system time, timestamps, and event logging are correct.

☑ Confirm system time synchronization and time zone are correct (server and clients as applicable).

Alarms & notifications

☑ Verify alarms trigger and clear correctly at a test location.

☑ Verify notifications (email/SMS/voice) send successfully and acknowledgments work as intended.

Data integrity

☑ Confirm devices are communicating and data is updating.

☑ Confirm backfill behavior after any communication interruption (if applicable).

Reports & trends

☑ Generate a standard historical report (PDF) and confirm formatting and content.

☑ Verify key trend views and location history outputs.

Integrations

☑ Confirm any OPC/Modbus or external integrations are operating normally.

Go/No-Go before returning to service

✔ Authentication and user permissions work as expected.
✔ Audit trail and event logging are recording correctly.
✔ Alarms and notifications work end-to-end (as applicable).
✔ Devices are communicating and data is current.
✔ Critical reports and trends run successfully.
✔ Any deviations are assessed and acceptable (or resolved).

Risk Assessment Checkpoint

Confirm the system is stable and compliant in real operation.

What you assess:

☑ Any deviations encountered, and whether they affect compliance or data integrity

☑ Whether verification results meet acceptance criteria

☑ Whether it is safe to resume normal monitoring and rely on the system for GxP records

Output: “Release to production” decision + documented evidence.

8) Complete validation and close change control

☑ Approve the executed IQ/OQ activities or risk-based testing.

☑ Attach release notes/errata references to your change control record.

☑ Record final outcomes and approvals.

☑ Update your SOP references (if required) and schedule the next review.

9) Contact Vaisala

• We can help – even if you are updating from a much older major version.
• We assist with migrating to a new server.
• If you have a large system, with many devices, sites, or integrations, our application engineers can boost your internal quality and validation teams. 
• Let us help you minimize downtime.
• We provide guidance on a risk-based validation approach.
• For 20+ years, our customers have been updating their viewLinc software. We can guide you through the safest path to updating. 

Contact us