Remote Agents (RAs) are customer-managed components within a validated Seeq deployment. Remote Agents are released independently of Seeq SaaS releases. The RA and Seeq SaaS use different versioning schemes. An RA does not need to have a version number that matches the Seeq server version.
Unlike the Seeq SaaS application, which follows a regulated release cadence, RAs are installed, validated, and upgraded by customers according to their internal quality and change-control procedures.
Version Compatibility and Support Window
Remote agents are supported for 12 months from its release and are compatible with Seeq releases within that window. This allows validated customers to:
-
Maintain consistency by validating a specific RA version.
-
Continue using a validated RA while upgrading the Seeq server.
-
Skip individual RA releases when their current RA remains within the support window.
-
Schedule an RA update according to their internal change-control and validation schedule.
-
Validate a new RA while continuing to use the current RA in production, when appropriate for their procedures.
The 12-month window is a technical support and compatibility limit. It is not a recommendation to wait until the last possible day. Customers should plan an RA update early enough to complete their internal review, testing, approval, and deployment before the current RA reaches 12 months old.
Updating an RA during a quarterly Seeq upgrade
An RA update is not automatically required when a new quarterly Seeq Regulatory Release becomes available. The decision to update the RA is governed by the customer's internal change-control procedure, provided that the RA remains within the 12-month support and compatibility window.
As a best practice, customers may review their RA status as part of each quarterly Seeq upgrade. A quarterly review or update can simplify planning and reduce the risk of approaching the 12-month limit, but it is a recommendation rather than a technical requirement.
There is no required order for updating the Seeq server and the RA:
-
Customers may update the Seeq server while continuing to use the current RA, if the RA remains within the 12-month window.
-
Customers may update the RA independently of a Seeq server update, according to their change-control process.
-
Customers do not need to update the RA solely because the Seeq server was updated.
-
The RA and Seeq server do not need to be on matching version numbers.
What to review with a Seeq Regulatory Release
The quarterly Seeq Regulatory Release contains information about the Seeq server release, including its release notes and associated testing or quality information. The package does not define a corresponding RA version, because RA releases follow an independent release schedule and use a different versioning scheme.
When planning a quarterly upgrade:
-
Review the release notes and other materials provided with the Seeq Regulatory Release.
-
Confirm that the current RA remains within the 12-month support and compatibility window.
-
Decide whether an RA update is needed under the customer's change-control procedure.
-
If an RA update is planned, select an RA version that is within the 12-month window and coordinate it with the customer's procedures.
There is no separate RA version that must be paired with each Seeq for Pharma Regulatory Release.