Table of contents
At a glance
How do you validate Agilent OpenLab CDS?
Test the installed combination of OpenLab CDS, drivers, methods, roles, storage and connected systems against its intended regulated use. Cover data acquisition, processing, reprocessing, review and long-term availability. Installation evidence supports this work. Add process tests for situations such as manual integration, method changes and use of restored data.
- OpenLab CDS, OpenLab ChemStation, and content management components are not considered equivalent.
- Method, sequence, result, and system event require appropriate documentation and validation evidence.
- Manual integration is evaluated based on authorization, professional justification, and verifiable results.
- A report alone does not fully represent a dynamic chromatographic data set.
1. Define the laboratory process and its scope of application
What decision is based on the result: a GMP audit, a stability assessment, or another investigation? Describe sample acceptance, measurement, evaluation, testing, and result transfer. Capture also rejected, discontinued, or repeated work steps. Software validation and method suitability address different questions; both types of evidence must align meaningfully within the laboratory.
For GMP activities involving human medicinal products, Annex 11 is a key basis. The EU directory continues to list the January 2011 revision on the research day. Part 11 is aligned with relevant FDA record-keeping obligations and the use of electronic records. The product designation alone does not establish either a general requirement or a general exemption.
2. OpenLab CDS, Version and Storage Architecture Differ
The architectural description draws on the May 2026 edition of the OpenLab CDS 3.0 documentation. The manufacturer distinguishes between several topologies and storage components. OpenLab CDS and OpenLab ChemStation are distinct products. OpenLab ECM and ECM XT are also distinct products that can form part of the architecture as additional data management components.
The detailed operation examples provided in this article for roles, audit trails, integration, and signatures specifically refer to the publicly available help version 2.8. For a 3.0 installation, compare this documentation with the included help and release notes. Additionally, maintain records for driver versions, devices, add-on modules, and interfaces. A mere version specification for the CDS client does not fully describe the overall system.
| Configuration | Documented difference | Project question |
|---|---|---|
| Workstation | Components on a computer; local file storage | Who safeguards and ensures the completeness of the entire dataset? |
| Workstation Plus | Local Content Management Components | How are data holdings and associated services restored? |
| Client/Server | CDS clients, or AICs, and separate server components | Which components and versions are used together? |
| ECM-XT-Cloud Deployment | Supported client/server configurations in AWS or Azure | What specific architecture and operational responsibility were agreed upon? |
3. Align roles and responsibilities with actual job duties
The 2.8-Helper separates permissions for manual integration, method processing, post-processing, and security management. From this, a task matrix for your laboratory can be developed. An analyst, a result verifier, and an administrator do not necessarily require the same capabilities. Also monitor access to projects and the actual effective rights.
Validate methods using a manageable reference dataset. Do calibration, dilution factor, units, rounding, and result presentation align with your defined specifications? Independently recalculate selected results. Repeat the scenario with missing or invalid inputs. Custom calculations and report templates require targeted test cases; a functional login does not validate their accuracy. Separate the method's scientific appropriateness from correct processing within the implemented system.
4. Verify audit trails by data object and decision
During project setup, the 2.8 Help defines separate settings for method, sequence, and result audit trails. Additional options are available for justifying specific actions. Verify the required settings at the specific project level and on actual generated data. The presence of a menu item does not imply that every relevant activity is fully recorded.
The FDA treats review of changes to records as part of data review. Define which events the result reviewer needs to see before deciding. In our test, change an integration setting, save a new result version and ask a second user to reconstruct the trigger, action and impact. Also define how to assess unusual or unexplained events.
5. Example test: manual integration and method change
The example employs an appropriate test dataset featuring an overlapping peak. Prior to analysis, the laboratory team documents the expected results and permissible data editing. It first evaluates the established automated integration and subsequently performs a professionally justified manual correction. A method deemed acceptable for this test must be used; method authorization and user permissions must align with the intended action.
For version 2.8, Agilent describes that manual corrections can be stored in a method or a single injection. Therefore, it is also important which further evaluations are affected by a correction. Document the location of the storage and specifically compare a second data set. The following expectations are project criteria to be determined before the test, no claimed measurement results.
| Test step | Observation | Justifiable acceptance criterion |
|---|---|---|
| Analyst without integration rights | Attempt at a manual correction | Unauthorized editing remains locked |
| Authorized user corrects the peak | Traceability of result changes and rationale | The new status is technically verifiable and distinguishable from the previous |
| Correction in method instead of injection | Evaluate a second suitable test dataset | The scope of the change corresponds to the documented intent. |
| Reprocessing | Compare methodological basis and effective corrections | No unintended takeover or removal of a correction |
| Close without saving | Check available events and detail limits | The agreed review identifies the inspectionable process or a assessed control gap. |
6. Testing, electronic signature, and reprocessing linkage
OpenLab CDS 2.8 provides configurable signature levels with user and group assignments. Define the intended professional responsibility associated with each level. Verify correct mapping to the result status, authorized roles, and an unauthorized signature attempt. The presence of a configured function does not constitute a comprehensive statement regarding compliance with all applicable requirements.
The 2.8 Guidance explicitly states that a signature is not retained upon reprocessing of signed data. Consequently, a specific verification task arises: Can users clearly identify the updated version and re-verify it? Additionally, verify the report output. The visible report must reflect the intended current status; an old signature display must not be misinterpreted as confirmation of a subsequent edit.
7. Complete electronic data instead of PDFs containing only results
A chromatographic dataset encompasses more than just the visible curve in the report. The FDA explains that a printed chromatogram alone does not represent the complete electronic raw data including context. A PDF, by its file format, is not automatically equivalent to a complete, immutable original record.
Therefore, describe the required data package for the respective workflow: raw data, relevant methods, sample and sequence information, results, as well as necessary amendment and review information. Enable a qualified user to trace the quality decision through a selected case study. Additionally, assess the availability following a user change or project end. If data is exported, evaluate content and future usability rather than merely the number of generated files.
Sources: [14]
8. Review result transfers and reports containing error cases
In case of a LIMS or other result connection, assignment and status count as well as the numerical value. For example, develop a test with two similarly marked samples, different dilutions and a new evaluation. The transfer should clearly assign the agreed dataset and use the correct released state.
Resume an interrupted transfer and initiate a retry transmission. Prior to doing so, define how the target system handles duplicate, missing, or outdated results. Verify units, decimal representation, and limit value labeling. These validation considerations do not require any specific standard LIMS function from OpenLab: what is critical is the actual installed interface including its own software and configuration.
9. Plan separate data transfer and version changes
A transition from ChemStation or EZChrom is not merely a renaming of an installation. For example, Agilent specifies limitations regarding manual integration corrections when loading EZChrom data into OpenLab CDS 2.8. This statement is specific to EZChrom and must not be unverifiedly extended to ChemStation. For each data type, determine whether it is accepted, made available through an appropriate reading system, or otherwise controlled and made available.
For OpenLab CDS 3.0, the release notes distinguish supported direct upgrade paths and the recovery of older backups. Therefore, check baseline and selected technical path separately. A separate comparison data set should cover critical methods, reports, roles and interfaces. Evaluate known errors and changes before productive use. Different results are explained and decided, not subsequently concealed by an adapted target.
10. Clarify restoration and collaboration prior to startup
The Workstation Handbook 3.0 describes software verification, backup, and restore as separate tasks. A successful installation validation does not confirm that your laboratory process is correctly implemented. A completed backup run does not verify that a restored dataset remains technically and functionally usable.
Plan a recovery scenario with representative data and the appropriate environment. Subsequently, verify method alignment, result presentation, and required history. For server architectures, incorporate the documentation and specifications of the actually deployed storage components. Prior to project initiation, the team should jointly determine the following points:
- Proposed laboratory procedures, regulatory assignments, and result responsibility defined.
- CDS version, devices, drivers, storage components, and add-on modules documented.
- Methods, calculations, report templates, and critical error cases selected.
- Confirm the user roles, administrative activities and meaning of each signature.
- Audit trail settings, as well as the process and scope of the review, are defined.
- Interfaces, migration, storage, and recovery planned.
- Test environment, appropriate data, and participation from laboratory, IT, QA, and manufacturer partner available.
Project experience and collaboration
Assess a laboratory decision in the context of the complete data
With the laboratory and QA, we examine an OpenLab workflow, including method version, possible reprocessing and review. IT identifies the storage and version in use. For an unchanged, controlled workflow, manufacturer evidence and targeted internal tests may suffice. Changes to integration or archiving require additional cases. We check whether another authorised reviewer can reconstruct the decision from the records. Scientific assessment of the method remains with your laboratory specialists.
Frequently asked questions about Agilent OpenLab CDS
Has Agilent already validated OpenLab CDS for our GxP usage?
Manufacturer documentation, installation certificates, and offered testing services can provide valuable components. However, they do not inherently demonstrate your specific methods, responsibilities, reporting practices, and handovers. Assign existing evidence to your specific requirements and supplement any missing process validations. The documented assessment of suitability for internal use remains a responsibility of your organization.
Sources: [11]
Are OpenLab CDS, ChemStation, and ECM the same system?
No. Maintain the exact product name and version of each component. OpenLab CDS is considered independently here; ChemStation is not simply a interchangeable name. ECM or ECM XT may be included as a component of data management. For migration, operation, and recovery, you will need the documentation appropriate to the actual combination.
Sources: [2]
Are IQ and OQ required for the release of the laboratory process?
First assess what these validations actually evaluate. The installation and defined system functions are distinct from your actual implemented analysis, review, and transfer workflow. Verify the coverage of your requirements and supplement with appropriate scenarios. An independent assessment of the analytical method is not automatically replaced by this.
Sources: [11]
Must every manual integration be fundamentally prohibited?
A blanket ban does not address the technical question. Define acceptable justifications, legitimate roles, and a transparent approach to result handling. Test both permitted and unauthorized modifications, and assess their observable impacts. The laboratory must provide a technically sound rationale for any methodologically acceptable interventions. Software authorization alone does not determine suitability.
Which audit trails should the reviewer examine?
Determine the extent of the relevant data and decisions. Changes in methods, reprocessing and other recording-related events can be decisive for the result evaluation. The FDA links their examination with the data verification. Technical events need to be handled in a suitable manner. A complete daily check of all logs or a one-off look at the installation would not be sufficient justification.
Sources: [13]
Is an electronic signature valid following a subsequent processing?
For the currently evaluated assistance 2.8, Agilent states that the signature is not retained upon reprocessing of signed data. Please verify the specific workflow of your version and configuration: How is the new version displayed, who evaluates it, and how is a required reconfirmation performed? Exported reports must also align with the correct version.
Sources: [8]
Is it sufficient to archive chromatograms as PDF files?
Not solely because a report contains all visible results. Assess which electronic source data and relationships are required for reconstruction. The FDA explicitly highlights the limitations of printed chromatograms. Evaluate an archiving concept based on complete, accessible, and long-term usable records; the PDF file format does not inherently meet these requirements.
Sources: [14]
What should we prepare together prior to project start?
System and equipment overview, exact versions, method lists, user roles, and information on data storage and interfaces are required. Supplement existing supplier or service provider reports and critical laboratory procedures. Maintain appropriate test data and a functional test environment. Early clarification of data migration and retention ensures that critical questions do not arise shortly before batch release.
Who must work in a smaller laboratory?
The laboratory defines technical requirements and expected results. The IT department or operator is responsible for the technical implementation and operation. QA evaluates quality requirements and the established release procedure. The manufacturer or service partner provides product knowledge and agreed-upon validation evidence. Name a point of contact for coordination and allocate dedicated time for method examples, review, and decision on test results.
What affects the effort and duration of OpenLab-CDS validation?
Important factors are the range of devices and methods, own calculations, storage architecture, role model and interfaces. Migration with older result formats can trigger additional comparison and archiving tasks. In addition, there is quality of existing evidence, availability of the test environment and processing of open findings. Plan on this basis concrete work packages; a fixed duration from the product name would not be loadable.
Sources and review date
The OpenLab CDS 3.0 documentation was used to check the system architecture and current changes. The detailed operating examples refer specifically to help version 2.8. Assess whether they apply to your version and configuration. The test examples are our recommendations. They do not represent Agilent statements or tests that have been carried out.
- Agilent: OpenLab CDS 3.0 Release Notes
- Agilent: OpenLab CDS 3.0 Requirements and Supported Instruments
- Agilent: OpenLab CDS 3.0 Workstation Installation and Configuration
- Agilent OpenLab CDS Help 2.8: OpenLab CDS Roles
- Agilent OpenLab CDS Help 2.8: Add a project
- Agilent OpenLab CDS Help 2.8: Adjust the settings for manual integration
- Agilent OpenLab CDS Help 2.8: Remove manual integration corrections
- Agilent OpenLab CDS Help 2.8: Reprocess the data
- Agilent OpenLab CDS Help 2.8: Signature Settings
- Agilent OpenLab CDS Help 2.8: Use existing EZChrom data and methods
- European Commission: EU GMP Annex 11
- European Commission: EudraLex Volume 4
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers
- FDA: CGMP Records and Reports – Question 4
- eCFR: 21 CFR Part 11
Sources checked: .
Align the evidence to the actual laboratory process flow.
We support you in aligning existing supplier certifications and planning your own assessments for methods, data flow, and review processes. The starting point is your system overview and a representative laboratory process together with its critical decision points.
- 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.

