Table of contents
At a glance
How do you validate Rotronic HygroLab?
Define the intended use, software version, compatible probe, measurement method and data flow. Derive testable requirements for measurement completion, attribution and use of the result. Assess supplier evidence and add missing tests. Demonstrate method suitability and calibration separately. An FDA mode, green completion indicator or PDF report does not establish these points.
- HygroLab is laboratory water activity measurement; RMS is another monitoring system.
- HC2A-AW and HC2A-AW-USB have different interface and software boundaries.
- Evaluate measurement stability, numerical product specification, and technical suitability separately.
- Assign each calibration point, adjustment, and control measurement unambiguously.
Device, sensor head, and software clearly defined
The current HygroLab is a laboratory instrument equipped with its own software and supports up to four digital sensor probes. It measures water activity along with associated humidity and temperature data. This generation of equipment must not be equated with earlier HygroLab models or PC-based configurations. Therefore, in addition to recording "Rotronic" in inventory, ensure documentation of the complete device, serial number, software version, and each individual probe used.
The interface boundary is clear: The HC2A-AW can be operated on the HygroLab. In contrast, the manufacturer specifies that the HC2A-AW-USB is intended for use on a PC running HygroSoft. Additionally, operating the HC2A-AW via a PC through an adapter alters the system configuration. Therefore, a similar sensor designation alone is insufficient to transfer existing test results without modification.
The current version of this article is primarily based on the documented software version 3.0.0.7 dated 16 February 2026. This does not imply that it is the latest available version. Compare the actually installed version with the corresponding functional and error guidance. A screenshot of the version screen may serve as evidence of the installed version, but does not replace a detailed description of its intended use.
Describe the quality decision and its prerequisites
The example framework represents a laboratory that uses water activity values for decision-making regarding human medicinal products. For computerized activities in this GMP context, Annex 11 serves as a relevant GMP guideline. A development study without corresponding quality decisions may require a different scope of validation evidence. Similarly, requirements cannot be solely transferred to food, cosmetic, or medical device products based on the same equipment.
Three questions aid in defining the boundaries: Is the testing instrument appropriate and validated? Is the analytical method suitable for the sample? Does the software-driven execution and data recording function as required? Chapter 3 covers testing instruments, and Chapter 6 addresses quality control and testing methods. These analytical objectives can be integrated into a single common documentation; they do not automatically necessitate three separate documentation systems.
Describe who uses the value, for what purpose, and the consequences if the value is incorrect, missing, or incorrectly assigned. For an additional FDA reference, review the applicable recordkeeping requirements and the actual use of electronic records. The product name or device option "FDA Mode" does not determine the scope of applicability.
Make the sample manageable prior to software testing
Rotronic identifies appropriate sample vials, temperature equilibration, and a stable measurement environment as key prerequisites. A sample directly taken from the refrigerator or from a hot process may introduce different conditions compared to the measurement head. Such differences must be specified in the method protocol. A repeatable software workflow cannot compensate for inadequate sample preparation.
Your testing protocol should clearly define sample identity, container, preparation, measurement position, and allowable interruptions. Specify when the sample is considered ready and outline the actions taken following a prolonged interruption. Use pre-prepared samples under justified conditions for comparison. If the sample is altered during repeated measurements, a difference is not automatically indicative of a software error.
In addition, verify contact and sealing surfaces in accordance with manufacturer instructions. In cases of atypical results, a clear sequence of actions should be followed: first, confirm assignments and conditions, followed by investigation of possible equipment, method, or operator-related causes. Repeat measurements should be used to address a technical question. Repeated measurement until a desired result is achieved would not constitute valid justification for its use.
Use AWE and AW Quick with proprietary method specifications.
AWE is waiting for the set stability of temperature and water activity. AW Quick uses an algorithm and an adjustable waiting phase called Dwell time. This is followed by a practical test question: Which parameters and closing conditions are part of your released method, and how do you detect a different setting?
The online handbook provides varying temperature rise recommendations. For AWE, it specifies 0.1 °C/min in the text section under Stab.T and 0.01 °C/min in the summary table. The stated AW-Quick wait times also do not fully align. Therefore, these values are not recommended as universal defaults. Clarify the appropriate setpoint with Rotronic and justify the parameters for your specific application.
A meaningful in-house test pair includes a measurement under intended operating conditions and a deliberately deviant case. In this scenario, evaluate whether settings, run profile, completion, and documentation remain understandable. A comparison of both modes must align with the sample matrix and the intended accuracy. The manufacturer's specification for a rapid method does not constitute a guarantee that every sample can be assessed with equivalent quality within a fixed time frame.
Sources: [3]
Distinguish calibration points from the adjustment performed
The HygroLab Handbook first describes the storage of calibration points, followed by the actual calibration procedure. A recorded point does not constitute evidence that the sensor head has been modified. After confirmed calibration, Rotronic specifies an event log entry and a report. Review these differences in relation to the intended workflow and assign the documentation to the specific sensor head in use.
From Software version 3.0.0.0, control deadlines and other criteria are specified. Note the unit: the accuracy specification for the control function is entered in %RH, not directly as an aw value. A numerically similar input may therefore represent a different value. Neither the manufacturer's recommendations establish a general seven-day deadline nor a specific test frequency for each laboratory.
For operations, you need a clearly defined approach to handling overdue or failed controls. Do not assume an automatic measurement lock at every deadline expiration. Therefore, describe the actual existing warning or blocking mechanism and the associated organizational response. The deadline check should not merely display a calendar; it must enable a traceable decision regarding further use.
Requirements relate to specific transitions.
A requirement such as "HygroLab is validated" leaves open what exactly is being assessed. A more precise statement is: "A finalized measurement result remains attributable to the intended sample, the used sensor head, and the applied method." Appropriate evidence and failure scenarios can be defined accordingly. The table below is an internal work aid and does not constitute an officially mandated form.
Begin with the actual workflow required by your laboratory. Add notes for abort, misidentified lot numbers, or unauthorized method changes where such actions could lead to incorrect decisions. Manufacturer documentation may already include individual requirements. They do not need to be redundantly repeated; however, their alignment must be clearly demonstrable.
| Transition | Expected result for this example | Suitable evidence |
|---|---|---|
| Probe for measurement | The identifier remains unique | Prepared sample and stored measurement assignment |
| Method for startup | The proposed mode and parameters apply. | Compare settings with the approved requirement |
| Run to result | Completion and termination are distinguishable | Normal case and controlled termination |
| Result of the assessment | The limits and data status are separately verified. | Independent expected results and process-owner review |
| Summary of the report | Identity and value remain correct | Stored dataset versus report |
Example: Measurement completion is not a product determination
The following example was not performed on the product. The starting point is the laboratory sample P-101, detector K-01, and method M-01. The product specification in the example is aw ≤ 0.600. Each row of the table begins again from this initial condition. The numerical values are pre-prepared test data for the decision pathway; they are not provided as guaranteed results from real reference materials.
For the pure boundary comparison applies: 0.580 minus 0.600 returns −0.020; 0.600 minus 0.600 returns zero; 0.620 minus 0.600 returns +0.020. Thus, normal, limit and exceedance cases are determined independently. A real release rule must also take into account measurement uncertainty, rounding and analytical suitability. This table does not validate an analytical procedure.
Assess both the procedural evaluation process and the actual software controls in place. If a boundary is assessed on an organisational basis, the test need not implement an automatic product hold. What is essential is that a user is able to identify the correct dataset and make a decision that is traceable and consistent with the previously defined criteria.
| Prepared Case | Closure / Assignment | Expected result defined in advance |
|---|---|---|
| aw 0.580 | Completed; P-101 / K-01 / M-01 | Numerical example limit met |
| aw 0.600 | Completed; correct assignment | Boundary included; additionally consider the actual decision logic. |
| aw 0.620 | Completed; correct assignment | Numerical example limit exceeded |
| 0.580 | Run prematurely terminated | Do not use as a result of a regular completed analysis. |
| aw 0.580 | Incorrect sample identification | Clarify assignment; no release solely based on the numerical value |
Understand, report, and verify shared results, rights, and responsibilities
The automatically generated measurement batch identifier is not inherently your production batch. Define the assignment to laboratory sample and, if applicable, to batch reference. A logically named file export facilitates workflow but does not replace the relationship between measurement, method, sensor, and evaluation. Verify at least one complete dataset from start to later retrievability.
The FDA mode describes access controls and event logging. The manufacturer identifies limitations for administrative rights and LDAP, as well as the absence of time zone notation in event entries. This raises specific questions regarding your environment: Which role is authorized to make changes? How is the time reference defined? Can an auditor correlate relevant changes with the affected results?
Define which electronic data and supporting documents support the quality decision. A PDF is not automatically complete or tamper-evident. Verify content, readability, and retention in accordance with the intended retention procedure. This includes assessing whether required information remains accessible following equipment failure or replacement. The presence of an export button does not confirm the capability for recovery.
Evaluate the manufacturer package and changes to the actual in-use situation
Rotronic provides a separate IQ/OQ template. Please inquire about its specific delivery scope and version reference. Map applicable evidence to your requirements: which functions, settings, environments, and deviations are covered? Only the gaps remaining for your specific application remain unaddressed. A package does not need to comprehensively cover all aspects nor merely include standard functions.
For changes, a controlled decision-making process is required. Identify affected methods, records, and operating procedures and derive appropriate supplemental validations from this assessment. The general warning in the manufacturer section regarding updates does not constitute standalone regulatory justification for a complete restart of all tests.
The Release Notes 3.0.0.7 also mention a known issue related to password changes in standalone mode. Clarify the scope and impact of this issue with the vendor prior to planning any corresponding tests. A documented defect constitutes a relevant input for your evaluation; it does not prove that every device operation is affected.
Checklist: What the Laboratory, QA, and IT Provide Before Start
The laboratory outlines samples, methods, and decision criteria. QA defines the scope of evidence and evaluates open points. IT or the equipment responsible party provides software version status, roles, data retention, and recovery procedures. Rotronic supports with version boundaries and functions that are not clearly described. In a small team, individuals may assume multiple responsibilities, provided responsibilities remain clearly defined.
Effort arises particularly due to numerous method variations, unclear sample assignments, missing historical data, different measurement probes, and undefined storage conditions. A clear inventory review makes these factors visible early. Generic time- or price guarantees are less effective than a specific list of critical evidence questions.
- Device, software, sensor serial numbers, and connection variants to be recorded.
- Scope, sample matrices, and approved methods to be provided.
- Stability and maintenance parameters including open manufacturer questions to be clarified.
- Describe the reference standards, check intervals and how deviations are handled.
- Define sample- and batch assignments and identify critical records.
- Normal, boundary, stop and assignment cases with independently defined expected plans.
- Assign manufacturer records, pending tests, and operational responsibility.
Project experience and collaboration
Check the water activity measurement against the intended procedure
With the laboratory, we start with the sample, measurement conditions and selected HygroLab evaluation method. We define what the result must establish and which data make that conclusion traceable. For an established application, suitable test cases and a focused evidence review may suffice. For a new workflow, we first agree sample assignment, settings and the use of the result. A faster display alone does not demonstrate suitability.
Frequently asked questions about Rotronic HygroLab
Has Rotronic HygroLab been validated for our GxP usage?
Manufacturer submissions and provided IQ/OQ documents may provide relevant evidence. Whether they adequately cover your intended use depends on version, probe, method, and data usage. Assess the actual scope and address any outstanding requirements. A product description or activated FDA mode does not constitute a complete evaluation of your laboratory process.
What are the differences between HygroLab and Rotronic RMS?
HygroLab is used here for laboratory measurement of water activity using associated sampling probes and individual measurement cycles. RMS operates as a separate monitoring system. Therefore, a continuous alarm chain for rooms cannot be transferred to HygroLab as a standard inspection model. For HygroLab, the focus lies on sample preparation, method, measurement completion, and the traceable application of the aw result.
Can an HC2A-AW-USB be used on the HygroLab?
Per manufacturer statement: no. The HC2A-AW-USB is intended for use with PC and HygroSoft. For HygroLab, the HC2A-AW is specified with its corresponding interface. Always verify the complete device designation prior to equipment changeover or transfer of existing validation data. A PC-based setup would additionally have its own separate software and data retention boundaries.
Sources: [4]
Is AW Quick equally suitable for every sample as AWE?
Do not assume general equivalence. AW Quick and AWE use different release criteria. Assess their suitability for your sample matrix, preparation, and defined parameters based on the required analytical performance. A rapidly reported value does not constitute evidence of equivalent measurement or successful product specification.
What stability values should we set?
Determine the stability criteria for your measurement process instead of taking over a general number. First, check with the manufacturer, which of the recommendations for your device and software version specified in the online manual. Then, on appropriate comparative measurements of your samples, assess whether the chosen setting provides a technically resilient result. The justified values are part of the test order; they are not loosened afterwards, only so that a run ends faster.
Sources: [3]
Does a stored calibration point indicate that the probe has been adjusted?
No. The described procedure separates the recording of points from the performed calibration. Verify the process and the associated report at the specific measurement head. A subsequent control measurement serves a different purpose: it assesses suitability according to the intended criteria. These processes should be clearly distinguishable in your documentation.
How do we assess the handling of expired calibration deadlines?
Check your version to determine what is displayed after the expiry date and which actions remain available. Document whether a reminder, a technical lock, or a predefined administrative step controls further usage. Record how an undefined suitability is handled prior to the next result usage. A visible warning alone does not constitute effective suspension of the laboratory workflow.
Is the PDF report sufficient as the sole laboratory record?
Only if the report contains all required information completely and clearly traceable. This includes, depending on the laboratory procedure, sample, probe, method, result, and relevant background information. If these relationships are missing from the PDF, supplementary records are required. The linkage to electronic data and future access must also be established. The file format alone does not ensure completeness nor protection beyond the retention period.
Must every update be re-validated?
The scope of enhancements should be derived from the affected functions and associated risks. Compare release, configuration, existing documentation, and known defects. Unaltered applicable evidence may remain usable; unresolved implications require justified resolution. A generic supplier statement does not substitute for this evaluation in your specific context. Ensure that subsequent operational release is clearly documented and traceable.
What affects effort and involvement in the small lab?
The main factors are the range of methods, the measuring heads in use, the data flows and the quality of existing documentation. The laboratory, QA and equipment owner should agree the expected result, installed configuration and method of reviewing results. Prepare one complete sample dataset and its method. This helps identify evidence gaps more accurately than a fixed test count or project duration.
Sources and review date
Date: 6 October 2026. Product reference: current HygroLab version with documented software 3.0.0.7 and the respective minimum version requirements specified. Discrepancies in manufacturer recommendations are not resolved into generic set values. The example is a standalone work aid and does not represent a completed product test.
- HygroLab — Device description
- HygroLab — Release Notes 3.0.0.7
- HygroLab — How to measure water activity
- HC2A-AW / HC2A-AW-USB — General description
- HC2A-AW / HC2A-AW-USB — Measurement guidelines
- HygroLab — Calibration / Adjustment
- HygroLab — Calibration / adjustment expiration
- HygroLab — FDA Mode
- HygroLab — Reports & Logs
- Introduction to the Rotronic Monitoring System
- European Commission — EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU GMP Chapter 3: Premises and Equipment
- EU GMP Chapter 4: Documentation
- EU-GMP Chapter 6: Quality Control
- FDA: Part 11 — Electronic Records; Electronic Signatures — Scope and Application
Sources checked: .
Align the HygroLab assay with the laboratory process.
We support you in consolidating the measurement procedure, existing documentation, and open inspection questions into a traceable justification for your use.
- 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.

