Table of contents
At a glance
How do you validate Agilent SLIMS in a GMP laboratory?
Validate the laboratory process using your specific SLIMS or OpenLab Sync version. Describe the sample path, protocols, data transfers and release rules. Map supplier evidence to requirements, then test critical workflows, including incorrect assignment, limits, changes and restoration. Product renaming and built-in controls do not demonstrate the suitability of your configuration.
- Classify SLIMS and OpenLab Sync jointly early on; evaluate specific version functionalities separately.
- The probe, subprobe, executed protocol, and results must collectively be traceable and logically consistent.
- OpenLab CDS remains an independent system with its own original records.
- Assess history, results review, and report jointly.
Agilent SLIMS and OpenLab Sync: Which application is being evaluated?
Agilent refers to OpenLab Sync as the next generation of Agilent SLIMS. The current product page integrates LIMS, electronic laboratory notebook, and guided laboratory workflows. The documentation for SLIMS 7.2 explicitly states that this version is still being released under the previous name, with subsequent releases designated as OpenLab Sync. A new name does not imply that every existing SLIMS installation automatically possesses the same features.
Start with your actual installation: Release, configuration, installed packages, operating mode, connected devices, and used interfaces. Treat new vendor functionalities as areas to be verified. Screenshots of a current web page do not constitute evidence that an older environment supports corresponding rights, dialogs, or validation rules.
OpenLab CDS remains a standalone chromatography data system. Integration with SLIMS or OpenLab Sync assigns tasks and results to a laboratory workflow; it does not make the systems interchangeable. Define where raw measurement data, analysis, laboratory report, and released report are respectively considered authoritative.
Define the GMP process and supplier documentation meaningfully and clearly.
This article addresses a pharmaceutical GMP laboratory for human medicinal products. Annex 11 covers computerized systems used in GMP-controlled activities. Whether FDA Part 11 is applicable depends on the specific record-keeping obligations and the electronic use of the systems. A LIMS product name or general laboratory operations alone does not constitute compliance with these requirements.
The Agilent Compliance Whitepaper 5994-8080en for SLIMS 7.2 distinguishes between vendor and user responsibilities. It supports validation planning, but does not provide access to the configuration. Map inherited development or installation validation records to your own requirements. Clarify version references, limitations, and future changes.
Describe as your first independent work aid a complete process: sample acceptance, sub-sampling, preparation, measurement, evaluation, and reporting. Identify decisions that could lead to an incorrect quality conclusion if erroneous data is present. This results in a justified testing scope rather than a generic category or individual screen inspection.
Sample pathway, digital guidance, and documentation integrated
The distinct advantage of an integrated LIMS/ELN/LES approach lies in the linkage between sample and actual execution. SLIMS documentation includes sample tracking, protocols, and customizable workflows. Therefore, verify not only the displayed sample list but also the technical relationships: which sub-sample corresponds to the order, which preparation led to the result, and which protocol version was actually executed?
A released instruction is a directive. The executed protocol documents what occurred during a specific procedure. Modifications to the directive must not alter the meaning of completed records without notice. This separation should remain understandable to a technical reviewer even after a workflow update.
| Object | Subject Matter Relationship | Appropriate test sample |
|---|---|---|
| Incoming sample check | Order, material identity, and incoming condition | Complete example dataset with unique identifier |
| Subsample | Origin and Intended Use | Traceability to the incoming sample and the associated test |
| Protocol | Valid instruction and actually performed steps | Specifications together with completed protocol |
| Result | Measurement, unit, method, and evaluation | Assignment to the source system and documented assessment |
| Report | Approved status and responsible reviewer | Legible output with traceable reference to complete documentation |
Configurations and store contents, including changes, to be managed
According to Agilent, the SLIMS Store provides prefabricated content, such as sample types, metadata, automation modules and configurations. Such content can serve as a starting point. It remains crucial whether its fields, rules and processes fit your shared working methods. The installation of a package does not answer this question.
Capture the origin, status, and any custom modifications for each adopted module. Specifically review mandatory fields, selection values, sample identifiers, permitted status transitions, and the assignment of tests. If a module is modified, also investigate other workflows that utilize it; otherwise, a side effect outside the original test scope may remain undetected.
An example is an additional field for the dilution factor. Verify whether the value is only displayed or actually influences calculation, reporting, or interface functionality. A technically meaningful standard field must not be recognized as a non-binding free-text entry only after go-live.
Test example: Subsample, dilution, and limit value
The following example was not executed in SLIMS. An incoming sample P-01 is split into sub-sample P-01-A. The example method calculates a concentration from measured value multiplied by dilution factor. The upper acceptance limit is 10.00 mg/l inclusive; the decision uses the unrounded value. The display with two decimal places is separate from this rule. These rules do not constitute a general analytical procedure.
Start with a correct mapping and deliberately modify each prerequisite thereafter. This demonstrates not only successful execution but also whether the process reliably detects incorrect identity, missing information, and unauthorized release. Expected responses must be predefined prior to execution, in alignment with the configured solution.
| Test case | Input or action | Expected behavioral performance |
|---|---|---|
| Normal case | P-01-A; 1.98 mg/l; Factor 5 | 9.90 mg/l; within the example limit; assignment remains unchanged |
| Upper limit | 2.00 mg/l; Factor 5 | 10.00 mg/l; limit inclusive |
| Slightly outside | 2.0002 mg/l; factor 5 | 10.001 mg/l; out of specification, even if the display reads 10.00 |
| Missing prerequisite | Dilution factor missing | No implicit acceptance of factor 1; processing requirement visible |
| Incorrect sub-sample | Result for P-02-A under order P-01 | Prevent misallocations or clearly identify them prior to use. |
| Premature Release | Request report despite review still open | Do not imply that a final version has been approved |
| Correction after review | Modify the measurement value of a reviewed process step | Change and downstream effects are traceable; triggers required re-evaluation |
Verify the interface to OpenLab CDS as a dedicated data pathway.
The SLIMS 7.2 documentation describes an integration with OpenLab CDS starting from version 2.6. This statement applies exclusively to this document version; it does not replace a current compatibility assessment of your specific combination. Record both releases and the used connection method prior to transferring any orders or results.
Verify sample identity, test identity, unit, dilution information, and result status based on own requirements. Resend the same dataset and observe whether a duplicate, a silent overwrite, or a logically inconsistent conflict arises. Interrupt the transfer such that a professionally incomplete process could occur; subsequently, it must be clearly established which side holds which status.
A result value stored in the LIMS does not automatically replace the original chromatographic chromatograms. Define which raw data, analysis methods, and metadata are required for reconstruction and specify where they remain available. A link is only useful if an authorized reviewer can access the correct object at a later time.
Review results, history, and report together
The white paper for SLIMS 7.2 describes a change history and the versioning of protocols. For practice, the question is: Can an examiner recognize and assess a relevant correction in the context of the affected result? An existing history is not yet a completed review.
No. 4.3 of the same whitepaper states that the indication of subsequent changes directly in the printout is not supported and refers to audit trails. This statement applies to the documented state of SLIMS 7.2. Clarify for your release how the report and associated changes will be made jointly visible.
Define professionally, who is authorized to review results, which signature authority is applied, and what types of changes require a renewed assessment. Verify the login process for a role without release authorization. The laboratory result release or a Certificate of Analysis is not automatically equivalent to the legally mandated certification and release of a medicinal product batch.
Assess professionally the data transfer and recovery process
The current product page lists Excel imports as a method for data transfer. Whether this approach is used to transfer master data, samples, or other contents depends on your specific configuration. A successful import dialog does not guarantee complete relationships or correct interpretations.
For your own take-over test, you can record datasets, mandatory fields, unique identifiers, units and parent-child relationships in advance. Do not just compare sums afterwards: open specifically datasets with umlauts, empty values, eliminated status data and multiple sub-samples. Document discarded lines and their treatment.
During database backup and recovery, ensure that required files and linkages are included. Have a technical reviewer verify the completeness and traceability of a completed recovery procedure. For hosted operations, clarify in the service agreement which backup responsibilities are assumed by the provider and what recovery evidence is provided.
What effort and involvement are determined in SMEs
Before project initiation, collect approved work instructions, real-world anonymized example processes, role definitions, master data lists, and interface descriptions. The laboratory head and department establish rules and expected behaviors. IT clarifies the environment and connections; QA evaluates the scope of evidence and release criteria. The implementation partner explains which standard function, configuration, or enhancement fulfills a requirement.
Particularly complex projects arise when sample pathways are known only orally, multiple teams apply different rules for the same status, or legacy data lacks stable identity. A technically simple interface may mask a complex process. Therefore, establish a complete and representative workflow first, rather than immediately configuring numerous additional screens.
In operation, evaluate release switches, modified protocols, new equipment, and adjustments to common modules. Agilent publishes architecture documentation with version references, including for SLIMS 6.9 and 7.2. Map such documentation to your actual current state. Renaming to OpenLab Sync alone does not establish functional equivalence nor triggers an automatic full revalidation.
Checklist prior to productive use
Walk through the sampling procedure jointly with the laboratory, QA, and IT. For open items, a deliberate decision and appropriate justification are required; a completed form does not substitute for evaluation.
- Product name, release, operating mode, and actually used modules are clearly defined.
- The probe, sub-sample, protocol, measurement, and report remain traceable and interlinked.
- Stored contents and customizations have been identified and evaluated in accordance with their intended use.
- Boundaries, rounding, missing entries, and unauthorized status changes were specifically considered.
- CDS transmission, repetition, and error handling are demonstrably testable.
- Reviewers assess relevant changes together with the results to be evaluated.
- Rights, signature significance, role representation, and required re-evaluation have been clarified.
- Data transfer, restoration, and subsequent modifications are managed by designated responsible parties.
Project experience and collaboration
Link the sample, protocol version and result in SLIMS
In SLIMS, we connect the laboratory's process with the configured workflow. Together, we trace a sample to the result used and examine the processing steps, data relationships and available evidence. An existing workflow may need a limited set of tests or corrections. For a new process, we clarify requirements and handovers first. The staff who take ownership should be able to reconstruct the relationships themselves.
Frequently asked questions about Agilent SLIMS
Is Agilent SLIMS today OpenLab Sync?
Agilent refers to OpenLab Sync as the next generation of SLIMS. For existing systems, you should document the previous product name together with release and configuration. The name change is not evidence of identical functionalities. When transitioning, verify which components and workflows actually change.
Is SLIMS the same as OpenLab CDS?
No. SLIMS or OpenLab Sync integrates sample management and laboratory workflows; OpenLab CDS handles chromatographic tasks. Integration can link data between the two applications. Determine which system is primarily responsible for order, measurement, analysis, and reporting, and assess the data transfers.
Which manufacturer documentation can support validation?
Use development, installation, testing, and architecture documentation appropriate to your version, along with known limitations. Map these to your specific requirements. The SLIMS Whitepaper outlines responsibilities and technical controls, but it neither replaces the evaluation of your configuration nor the review of the actual sample run.
Are pre-configured contents from the SLIMS Store already released?
The presence of a package in the store does not constitute approval for your specific GMP use. Document the contents and current status of the package and verify its rules against your current workflow. Special attention should be given to customized fields, automation, and shared components, as changes to these elements can impact multiple processes.
Which tests are particularly important for sub-samples?
Verify origin, unique identifier, intended investigation, and traceability to the original order. Correct a deliberately misassigned result dataset. The exact failure mechanism depends on your configuration; technically, a misassignment must be identified or prevented prior to use in the quality assessment.
Is the PDF report sufficient for results review?
For the evaluation of subsequent changes, not solely relying on the change notification in the SLIMS 7.2 Whitepaper, Agilent marks the change notification in the printout as unsupported and directs to audit trails. For your batch release, verify which reports, histories, and original data collectively enable the required results review.
Who must approve a protocol amendment?
The roles defining your change control procedure. Clarify who is authorized to modify, review, and approve specifications, and who must be trained subsequently. Test these responsibilities and the assignment of ongoing and completed activities to their respective protocol status.
Sources: [7]
How can a CDS interface be meaningfully tested?
Does cloud hosting alter the laboratory's responsibility?
Hosting can offload technical operational responsibilities. The laboratory must still define its own process, data requirements, and intended usage. Establish responsibilities for changes, authorizations, backup, recovery, and data access. Review these boundaries based on the actual services ordered and a specific recovery scenario.
How can the effort required for a SLIMS validation be estimated?
First, assess the number and distinctiveness of processes, custom configurations, interfaces, data transfers, and existing quality evidence. A representative sample pathway often reveals deficiencies in requirements early on. Only thereafter can work packages and stakeholder involvement be planned; a one-size-fits-all duration derived solely from the product name would not be sustainable.
Sources and review date
The compliance whitepaper 5994-8080en describes SLIMS 7.2. The passages used here for the task distribution and audit trails were specifically checked on October 18, 2026. Don't transfer them unchecked to other releases. The remaining documented source status remains from October 6, 2026. Example process, test matrix and checklist are own work aids, no executed product tests.
- Agilent: OpenLab Sync — Product Overview and FAQ
- Agilent: What is new in SLIMS version 7.2
- Agilent: The best of LIMS and ELN in one software — Agilent SLIMS
- Agilent: Save Time and Effort with SLIMS Predefined Configurations
- Agilent: Support for Title 21 CFR Part 11 and Annex 11 compliance – SLIMS 7.2, 5994-8080en
- Agilent: OpenLab Sync Policies
- European Commission: EU GMP Annex 11, Computerised Systems
- FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application
- FDA: Data Integrity and Compliance With Drug CGMP — Questions and Answers
- European Commission: EU GMP Annex 16 — Certification by a Qualified Person and Batch Release
Sources checked: .
Build validation evidence for your specific laboratory workflow
Daniel Herrmann Consulting supports your team in defining the GMP process, evaluating existing evidence, and planning traceable assessments for your configuration.
- 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.

