Table of contents
At a glance
What do you actually need to validate in testo Saveris 1?
Test the monitoring process from the assigned sensor through to assessment of a deviation. Include limits, transmission paths, alarm recipients, acknowledgement permissions, data availability and restart. Sensor calibration alone does not demonstrate that the alarm chain works. For Saveris 1 with CFR software V6, include the approval and recording functions actually enabled. Intended use, configuration and failure consequences determine the scope.
- Saveris 1 with CFR Software V6 is the focus; Saveris 2 and other software variants are considered separately.
- A triggered alert, its acknowledgment, and the technical assessment of a temperature excursion are distinct forms of validation evidence.
- Calibration, spatial mapping, and system validation each address their respective questions.
- Communication failure and retry are equally part of the testing scope as normal measurement operation.
Which Saveris variant is intended?
Testo uses the name Saveris for various solutions. The manufacturer's page for pharmaceutical storage explicitly refers to Saveris 1 and Saveris 2. The present article focuses on Testo Saveris 1 equipped with the Testo Saveris 1 CFR-Software V6, product number 0526 1004, for installation on PC or server. For this variant, Testo describes role management, audit trail, electronic records, and digital signatures, as well as alarm escalation.
Saveris 2 is described as a Wi-Fi data logger system with Testo Cloud. Testo now also offers local and cloud models for Saveris 1. Therefore, you cannot derive any operational responsibility or functionality from the family name. In the project, make product number, software version, license, components and operating model authentically documented.
The focus is on the monitoring of storage, laboratory, or production conditions for human medicinal products. Temperature control, refrigeration system control, and safety-related protective functions should be considered separately. The V6 Handbook describes Saveris as a monitoring system, not as a control system.
Define the intended use prior to the test list.
Start with the decision based on data: monitor a storage area, assess a temperature deviation, or use time-series data for a batch-specific quality decision? Identify products, areas, measurement points, responsible personnel, and key records. The same technical installation may require different levels of validation evidence.
Within the GMP scope, Annex 11 requires a risk-based approach to computerized systems. In the GDP scope, EU guidelines address, among other things, environmental monitoring, alarm testing, and appropriate pre-implementation evidence for system deployment. Part 11 is evaluated based on FDA recordkeeping requirements and the actual electronic records in use. The term CFR alone does not establish the regulatory scope.
Recommendation: Define testable requirements. "Monitor temperatures" is too vague. Instead, specify which measurement point must trigger an alert at which deviation level, which recipient must be notified, the expected response, and what documentation must be generated. Predefine allowable interruptions and alternate procedures prior to testing.
Measurement site, calibration, and system verification combined
A calibration provides a metrological proof for the tested measuring chain under specified conditions. Mapping investigates the spatial temperature distribution. System validation considers the planned overall process. The EU-GDP guidelines treat measurement point placement based on mapping, risk-based calibration intervals and computer-based systems accordingly as their own test fields.
Recommendation: Link each relevant measurement point to location, sensor identity, logger, channel, unit, calibration status, and rationale for limit values. A swapped channel may display a plausible measurement value at the wrong location. Therefore, physically verify the channel assignments. Identical device designation alone is insufficient as a proof of identity following a device replacement.
The following table is a separate planning aid. It describes required proofs, no flat-rate supplied manufacturer services.
| Area to assess | Guiding question | Suitable evidence |
|---|---|---|
| Calibration | How does the measurement chain compare to a reference? | Certificate including identity, measurement points, results, and assessed suitability |
| Mapping | Which positions represent the critical storage conditions? | Rationale selection of sampling locations based on spatial evaluation |
| Configuration | Is the correct channel connected with the appropriate alarm threshold? | Approved measurement points and alarm matrix with reconciliation |
| End-to-end process | Does a significant deviation reach the responsible employee? | Examination of triggering, delivery, acknowledgement and subsequent processing |
Sources: [9]
Verify the entire alarm sequence
The V6 Manual distinguishes between server alarms, base alarms, and alarm groups. Testo specifies for the base visual alerts, email notifications, SMS alerts, and optional signal devices. The actual implementation paths must be derived from your configuration.
Recommendation: Track an alarm through all involved stations. Separate the measurement timestamp, detected out-of-limit condition, transmitted alert, receipt by recipient, and first processing action. Also assess deviations occurring outside of scheduled working hours. Successful transmission to an unmonitored mailbox does not satisfy the requirement for a responsive reaction.
Critical limits, delays, recipients, and escalation rules require subject matter ownership. Test short-term and persistent exceedances in accordance with your intended process. Additionally, assess the behavior when alarm groups are disabled, when substitutes are designated, and when contact information is outdated. These scenarios are proposed test cases; they do not represent a specific standard configuration.
Upon an alarm, the responsible professional determines the affected products and further actions. A returned temperature alone does not indicate whether material stored during the period is still suitable for use.
Treat communication failure as its own condition
The emergency backup battery of the base unit and the described data transfer pathways are component characteristics. This does not imply unlimited bridging of all failures. Separate the following failure modes: sensor or logger failure, loss of connection to the base, interruption of connection to the server, and failure of the alerting pathway.
Recommendation: Define for each case what is subsequently measured, where data are stored, how a deviation is visible, and who takes action. The most recently displayed plausible value must not be confused with a fresh measurement in your operating procedure. Verify timestamps and the marking of missing values, as well as subsequent data transfers.
For a resumption, compare the expected time period with the existing data points. Check for gaps, duplicate entries, chronological order, and remaining alarms. The availability of a server is only the first step toward substantive review. Document how product decisions were made during the outage and whether subsequent data alter those decisions.
In case of external alarm routes, their operational manager belongs in the test. Vote for the experiment with IT and warehouse management; use a controlled test scenario without endangering stored goods.
Withdrawal, signature, and deviation evaluation differ
In the described CFR operation, the V6 Manual permits clearance by authorized software users, not at the base or via SMS or email. It also distinguishes between login and an optionally activated CFR authorization for alarm clearance. Therefore, re-authentication for each simple clearance shall not be assumed as a general requirement.
Recommendation: Check with separate roles, who can see an alarm, acknowledge, approve and change its configuration. Keep in mind the importance of each confirmation. "Knowledge taken, "Examines the cause and "Product released" may not run into each other professionally. Which electronic signature is required results from your recording obligation and your procedure.
The documented REST interface supports read-only data retrieval. Therefore, a connected external system is not automatically considered an acceptable release pathway. For reports or transfers to other applications, verify channel identity, time period, units, and completeness. Identify which data source remains materially relevant in the event of a discrepancy.
Example: Refrigerated room with disrupted alarm notification
Assume a facility monitors a cold room. For a selected measurement point, the area of responsibility, allowable alarm delay, on-call personnel, and alternate contact have been professionally defined. The assessment shall demonstrate that a relevant exceedance is addressed even when the primary communication pathway is compromised. This example does not describe a failure of testo Saveris 1 and is not a completed product test.
Use an appropriate test environment or a securely isolated measurement site. Document initial configuration, independent time reference, implemented measurement simulation, and expected response. The following cases constitute individual required tests; an alternative alarm pathway is only expected if provided in your approved architecture.
| Test case | Activation | Expectation from the defined target process |
|---|---|---|
| Limit excursion | Detected sensor threshold exceedance at the associated sensor generates | Correct channel, alarm timing, and responsible recipient are demonstrable |
| Primary communication channel disrupted | Shipping route monitored interrupted | Disruption is detected; the intended alternate route or organizational contingency procedure is activated. |
| Unauthorised acknowledgement | Employees without release rights attempt verification | Approval is not effective; observation is documented |
| No reaction | Alarm remains unattended in the predefined escalation scenario | The next stage is reached and notified to the responsible replacement contact. |
| Data transfer interrupted | Deliberately disconnect and restore the connection | Missing time period is assessed; re-imported data remains temporally correctly attributed. |
| Return to Operation | End test condition and verify configuration alignment | Measurement location, alarm rules, and recipients again correspond to the approved operating status. |
What the operation should prepare prior to the project
For an SME, a joint inventory by warehouse or process managers, QA, IT and the person responsible for measurement technology is recommended. One person decides the technical limits; another explains the technical configuration. Determine who evaluates deviations and who releases the use.
Prepare a room and measurement point list, existing mapping, calibration documentation, system overview, alarm matrix, and user concept. Supplement existing vendor assessments, installation results, failure data, and contracts. For each delivered evidence, verify the actual software version and components it covers.
The effort depends particularly on locations, communication channels, alarm variants, interfaces, and the quality of the existing system. Additional work often arises from unclear responsibilities or configurations that are no longer traceable. A reliable planning process identifies open decisions and available personnel prior to setting deadlines. A product brochure or certificate does not replace this inventory assessment.
Sources: [8]
Maintain the demonstrated state during operation
Recommendation: Treat sensor changes, new measuring points, firmware, software updates and changes to receivers as evaluable events. A new mail server may affect the alarm chain although Saveris remains unchanged. Determine which existing check is still meaningful and what will be proven again.
The local operation shall have defined backup and restoration procedures for data and configuration. Verify the restoration of a known time period, including associated alarm and evaluation records. Additionally, agree on how historical data remains readable during software version changes or system decommissioning.
Cloud variants offload operational responsibilities but do not replace your professional accountability. Testo outlines various update options including Version Freeze. The specific duration, exceptions, pre-implementation information, and provided evidence must be clarified in writing. The locally defined V6 inspection scope shall not be unreviewedly transferred to a cloud agreement.
Release checklist
This recommendation consolidates the decisions for handover. Each point requires a named responsible party and a retrievable justification.
- Variant, Build, License, Base, Logger, and data pathways are clearly defined.
- Measurement points, spatial suitability, calibration status, and limit values are appropriate for the intended use.
- Alarm receivers, representatives, escalation procedures, and response protocols have been coordinated and practically verified.
- Communication failure, missing messages, and retry mechanisms are controlled and validated.
- Withdrawal, optional approval, and product evaluation are functionally separated.
- Test modifications have been withdrawn; alarm functionality in operating condition has been demonstrated.
- Records, backups, restoration, changes, and periodic evaluation are the responsibility of designated personnel.
Project experience and collaboration
Follow a temperature excursion through to the response
With the responsible owners, we trace a Saveris alarm from its assigned sensor through threshold and notification to the response to a deviation. We also test who can still respond when communications fail. A known monitoring point may need a targeted change. Before adding new areas, we agree sensor assignments, recipients and deputy cover. Calibration, spatial mapping and system testing each have a distinct purpose and supporting evidence.
Frequently asked questions about testo Saveris
Does this guide apply to any product named Saveris?
No. The focus is on Testo Saveris 1 with CFR software V6 in local operation. Saveris 2, previous PRO/CFR versions, and Saveris-1 cloud models require a separate reconciliation. Therefore, document the product number, build, components, and contract first. Similar-named functions do not constitute evidence of identical behavior.
Is Saveris 1 licensed under CFR already validated for my operation?
The license describes a range of functions offered. Whether your monitoring process works properly also depends on installation, measuring points, configuration and organization. Arrange the supplier proofs to your requirements. Open points are closed by appropriate own tests or other reliable documents.
Does a calibration certificate replace system validation?
No. The calibration certificate pertains to the tested measurement equipment and does not indicate whether the correct measurement point triggers an alarm, whether the recipient is reachable, or whether data is correctly captured following a failure. Link messtechnical evidence to your own monitoring process assessments; treat spatial mapping separately.
Sources: [9]
Which alarm pathways should be tested?
Verify all routes used for the intended purpose, including their interdependencies. This includes responses outside normal working hours and during failure of the primary route. The audit plan follows your alarm matrix. A shipping record alone does not confirm the recipient's operational capability.
Can a SMS clear an alarm in CFR operation?
The V6 Manual excludes acknowledgment via SMS or email, as well as base-based acknowledgment for CFR operations. Authorization and confirmations must be considered within the software. Therefore, a received message and a valid acknowledgment should appear as separate events in the test protocol.
Sources: [3]
Is every alarm clearance automatically a renewed electronic signature?
You should not accept this without scrutiny. Key factors include activated approval rules, roles, and the specific software version in use. Verify which approval is actually required and documented. Additionally, define whether the action constitutes awareness, review, or another business decision.
What does a communication failure mean for product decision-making?
First, it must be evident which time period and which measurement point cannot be reliably assessed. Apply the predefined backup procedure and document the preliminary evaluation. Following a re-run, reconcile any missing or late-delivered data. Technical reconnection alone does not determine the suitability of the product.
Can an attached LIMS alarm be automatically cleared?
From the described reading REST API, such a function cannot be derived. Verify the specifically agreed interface scope and the permitted processing pathway. For pure data transfer, alarm handling and its documentation remain within the defined primary application or the supplementary procedure.
Sources: [6]
What changes trigger new testing?
Assess impacts on measurement, data linkage, and system response. A sensor change, altered setpoints, or new messaging pathways may require different testing protocols. Document the rationale and return to approved operating conditions. The scope shall align with the affected functions and risks, not solely with the designation as maintenance or update.
Sources: [8]
What determines the cost and duration of a Saveris project?
Crucial factors include system scope, measurement point quality, communication architecture, alarm scenarios, and existing validation evidence. Equally important is whether QA, IT, and operations can make timely decisions. Start with a verifiable inventory of existing assets and open issues. From this, the required scope of work can be derived; a blanket time or cost commitment would lack a solid foundation.
Sources: [8]
Sources and review date
Source: October 6, 2026. The focus is testo Saveris 1 with CFR software V6 in local operation. Manufacturer documents describe functions and limits; their applicability is to be compared with the installed stand. The test examples are own recommendations. Annex 11 is used in the January 2011 version listed by the Commission.
- Testo: Pharmaceutical Storage – testo Saveris 1 and 2
- Testo: testo Saveris 1 CFR software, Version 6
- Testo: testo Saveris V6 – Instruction manual
- Testo: testo Saveris Base V3.0
- Testo: Automated Monitoring System testo Saveris 1
- Testo: testo Saveris 1 – REST API and Components
- Testo: testo Saveris 2 Advanced Cloud licence
- European Commission: EU GMP Annex 11
- European Commission: GDP Guidelines 2013/C 343/01
- FDA: Part 11 – Electronic Records; Electronic Signatures, Scope and Application
- European Commission: EudraLex Volume 4
Sources checked: .
Clarify the own Saveris test scope
Daniel Herrmann is your point of contact for defining the boundaries between monitoring processes, supplier certification evidence, and in-house testing. We assist you in translating open decisions and required documentation into a mutually agreed work scope. Limit values, product assessment, and release decisions remain the responsibility of your designated authorities.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

