Table of contents
At a glance
What matters when validating Xcalibur?
Assess the actual combination of Xcalibur, Foundation, instrument control, processing and storage. Check that the sample, effective sequence parameters, method version, raw file and responsible user match. When versions change, include historical analyses and audit information. Use supplier evidence within its demonstrated coverage and test remaining handovers. A saved sequence or successfully installed update alone does not establish operational suitability.
- Sequence values can influence the effective method parameters.
- Foundation, drivers and evaluation belong in the system description.
- Historical audit data and new event capture are to be reviewed separately.
- The Quan Browser and Processing Setup have specific support limitations as documented.
Xcalibur begins with the specific device and software combination
Thermo Scientific Xcalibur integrates instrument methods, sequences, and data acquisition. Foundation supports, among other features, instrument configuration. Additional components include Instrument Control Software, LC drivers, firmware, and analysis programs. For validation, you require the actual combination of these elements, not merely the name of the user interface.
The Release Notes provided herein describe Xcalibur 4.7 SP1, Build 4.7.102.25, together with Foundation 3.1 SP10 and FreeStyle 1.8 SP2 QF1. This represents a documented package configuration, not a recommendation for every device, and does not imply that this is the latest available patch. Verify the target combination against the appropriate manufacturer documentation.
The July 2025 Configuration Manual specifically addresses the TSQ Series II and Orbitrap Tribrid Series. Installation and maintenance guidelines from this document do not automatically apply to any other Xcalibur system. Therefore, device family and operating scenarios must be evaluated together with software versions. A general laboratory PC list is therefore too broad for this purpose.
Which laboratory release decision should the system support?
As a regulatory example, the quality control of human medicinal products is considered. For this purpose, Annex 11 of the EU GMP guidelines outlines the handling of computerised GMP activities. The current EudraLex version references the January 2011 revision. The classification is based on actual activities performed; it is not triggered solely by the use of a mass spectrometer.
Define the relationship between sample, test instruction, and decision. Is a result for identity, content, impurities, or another evaluation used? What information does the inspector need to understand this finding? This leads to specific requirements for sequence, method, file, and result presentation.
Analytical method validation and system suitability address distinct questions. Similarly, successful equipment qualification does not constitute a complete demonstration of the electronic data pathway. If FDA-related records are involved, evaluate Part 11 based on the specific record-keeping and submission context. A general conclusion of FDA compliance for the product name cannot be drawn therefrom.
Make components and lifecycle visible
This work aid links the documented product status with the responsibilities of your laboratory. Complete each line with the actual installation, the responsible party, and existing documentation. This enables determination of which evidence can be accepted and which transition still requires verification.
Particularly relevant are the release notes for Quan Browser and Processing Setup: Both remain available in version 4.7 SP1 but receive no further support or updates. This does not constitute a blanket termination of the entire Xcalibur software. However, a specific planning requirement arises if your laboratory continues to rely on these analysis pathways.
| Component | Documented reference | Specific question in the project |
|---|---|---|
| Xcalibur | 4.7 SP1; Sequence and data capture workflow | Do the probe, active parameters, and generated .raw file align? |
| Foundation | 3.1 SP10 in the described package | How do actual user management and new audit logging function? |
| Device Control and Drivers | Device-dependent ICSW, LC driver, and firmware combination | Is the intended combination for the specific instrument validated? |
| Quan Browser / Processing Setup | Further available, from 4.7 SP1 onwards without additional support/updates | Which inventory processes are affected and how is their transition evaluated? |
| FreeStyle / optional Ardia | Own evaluation or data pathway boundary | What function does the actually deployed component perform and what information does it require? |
The stored method is not always the active value.
The Quick Start provides sequence specifications such as method path, vial, filename, and injection volume. The sequence volume may override the value defined in the instrument method. Therefore, verify the active parameter in the actual run context. Simply reviewing a method file may fail to detect a divergent sequence specification.
Define which changes are permitted and who is authorized to make them. For a sensitive parameter, an additional review prior to execution may be required. Whether the review is conducted technically or organizationally will be determined based on risk and demonstrated effectiveness. The existence of a procedure does not constitute evidence that an inappropriate configuration is adequately controlled.
The guide also describes the storage of a sequence with validation errors for subsequent review. Therefore, various states are stored and ready for execution. Check how a user identifies open errors, what start conditions apply, and how a reviewer can trace the actually used sequence.
Calculation example: 2 or 5 microliters?
The following example is not a completed device test. For sample P17, method M1 is specified at 2 µl. The assumed concentration is 20 ng/µl. A controlled test variant includes 5 µl in the sequence field, although the technical instruction remains unchanged.
Computationally, 2 µl × 20 ng/µl corresponds to a nominal amount of 40 ng. With 5 µl, the amount becomes 100 ng, representing an additional 60 ng and a 2.5-fold increase. These are exclusively theoretical input values. Neither the measured nor the injected volume nor a linear detector response is derived from these calculations.
Every scenario begins with a predefined copy of the initial sequence S17. Following a failure event, the initial state is restored. The table defines expected decisions; actual observations, protocols, and deviations are added during subsequent review.
| Subcase | Provided data | Expected Should |
|---|---|---|
| Intended run | P17, M1, Vial A1, 2 µl, 20 ng/µl | Nominal 40 ng; actual parameter and linkage to P17.raw confirmed. |
| Sequence value not foreseen | M1 remains 2 µl; the sequencing field contains 5 µl | Nominal 100 ng; identify and investigate any deviation prior to productive use, do not implement a technical block. |
| Same numerical value, incorrect sample | 2 µl, but P18 instead of P17 | Assignment verification not passed; correct quantity does not compensate for incorrect identity. |
| Saved with validation error | S17 with intentionally introduced and documented error | The file shall not be considered ready for execution solely because successful storage has occurred; predefined error handling must be verified. |
| Controlled restart | Starting condition S17/M1/P17 after each incident scenario | Next inspection starts without unintentionally imported 5-µl value; document the status comparison. |
Review historical audit data and new records separately
For 4.7 SP1, the Release Notes indicate the end of new entries being added to the previous Microsoft Access audit database. Existing entries remain readable. For Oracle 19c, support is limited to Oracle Server and Client running on the same Xcalibur data system PC. Clarify the exact architecture based on the administration handbook for your target system.
This leads to two independent pieces of evidence. First, any required historical event must remain understandable and retrievable. Second, a relevant new event generated through the intended new pathway must be detectable and observable. The successful opening of an old entry does not prove that new changes have been recorded; the reverse inference is equally invalid.
Prepare a named historical event and a targeted new modification. Define expected attributes, authorized access, and the relationship to the affected object. Also assess the scope and criteria of the search and filter parameters. The specific review shall be based on relevance to the laboratory process, not on a blanket obligation to examine every available event in every data record.
Accounts of technical responsibility are distinguished.
The device-specific configuration manual addresses the technical account for the Xcalibur_System in relation to specific Foundation instances. These installation instructions must not be interpreted as a general directive for modifying all existing accounts. Always use the manufacturer's procedure and assess affected services prior to any modifications.
For operational traceability, a key question remains: Who initiated a measurement run, modified an effective parameter, or evaluated a result? Verify the assignment against the actually used user roles. Technical operations and individual accountability must be clearly aligned.
In addition, define the significance of approval within the intended process. A status change or login alone, merely by its display, does not constitute an appropriate electronic signature. Whether a signature is required and the applicable requirements depend on the specific procedure and regulatory area. A blanket requirement for a signature on every Xcalibur measurement is therefore not derived.
Local data and Ardia require their own validation evidence
The Quick Start describes an optional Ardia integration featuring registration and authentication. When Ardia Path is selected, the Processing Method parameter is unavailable in the displayed workflow. This alters the data pathway beyond a single storage location. It is not assumed that full functional equivalence exists with the local process.
Describe the timing at which data is considered transferred for the actually used route, who has access to it, and the intended processing activities thereafter. A visible filename alone is not always sufficient as evidence of transfer. Select a laboratory scenario and trace the required information through to the intended reviewer.
During interruptions, specify how an ambiguous transmission status is detected and resolved. Automatic retry or seamless restart functions are not assumed capabilities without appropriate supplier documentation. For backup, recovery, and archiving, define the required data linkage and the applicable retention period. A PDF report only replaces the documentation to the extent that it covers the actual required evidence.
Plan version changes and security measures together
A manufacturer safety notice dated January 22, 2025 treats CVE-2024-55957 in the Foundation context. It calls Foundation 3.1 SP10 and Xcalibur 4.7 SP1 as corrected stands and also refers to measures concerning technical support. Whether your installation is affected only results from its inventory.
An update project should therefore take into account both the intended laboratory operations and the specific applicable safety considerations. Define which manufacturer's actions are in place, which components are modified, and which assessments cover the key transition points. Simply installing a version number constitutes insufficient evidence of safety or operational suitability.
Review existing supplier tests for their actual alignment with current requirements. Supplement relevant sequence, analysis, and data cases instead of blindly repeating all cases without justification. For dependent legacy analyses, a clear decision on continued use or replacement is required. A blanket transition to Chromeleon or TraceFinder would be inadequate without evaluation of data, methods, and workflows.
Preparation for Laboratory, QA, and IT
Before the project, assign professional responsibility for methods and results, as well as technical responsibility for components and operation. The laboratory provides representative sequences and data. IT clarifies accounts, services, storage, and recovery procedures. QA and the relevant process owners assist in defining requirements, result handling, and usage decisions.
The effort increases significantly due to different device packages, dependencies on legacy reporting, and changes to audit or storage architectures. Robust vendor documentation and traceable inventory data can help define and scope responsibilities. Relying solely on a name such as Xcalibur would not be sufficient to establish a credible cost or timeline. The following checklist assists in gathering the required information early.
- Are the device, Xcalibur, Foundation, ICSW, drivers, and firmware equipped with appropriate versions documented?
- Are method results and potential sequence overrides understandable and controlled?
- Does the system distinguish permitted user roles from technical accounts?
- Have historical audit usage and new event capture been separately demonstrated?
- Have Quan Browser/Processing Setup dependencies been assessed?
- Is the actually used local or Ardia data pathway, including error handling, described?
- Are change assessments, security measures, storage, and operational responsibility assigned?
Project experience and collaboration
Show which method version was in effect for an Xcalibur run
The laboratory selects an Xcalibur sequence and the result used. We link the sample identifier, effective parameters, raw file and analysis to the documented system version. A method change may affect only a few processing steps. For a version change, the laboratory and IT also examine Foundation, drivers and access to historical data. We record which existing evidence still applies and which handovers need retesting.
Frequently asked questions about Thermo Scientific Xcalibur
Is Xcalibur 4.7 SP1 automatically the appropriate target version for our laboratory?
No. The documented version provides a specific reference point but does not offer a universal recommendation. Key factors include device family, control software, drivers, firmware, data storage, and required analysis. Verify the appropriate compatibility foundation and relevant manufacturer guidance. A more recent or known package name does not substitute for a decision regarding your actual combination and its intended use.
Has the entire Xcalibur software been discontinued?
This is not supported by the reviewed documentation. The release notes for 4.7 SP1 explicitly state that the Quan Browser and Processing Setup remain accessible but are no longer supported or updated. Assess whether your processes depend on these components. This component-specific limitation must neither be ignored nor presented as a blanket termination of all Xcalibur functionalities.
Sources: [1]
Why must the injection volume be verified within the sequence?
The Quick Start indicates that a sequence value may override the instrument method value. Therefore, the correct method file alone cannot exclude the possibility of a differing run parameter. Review the specific device workflow and the current valid instruction. Define allowable changes and controls, rather than treating each override as a failure or each stored change as acceptable.
Does a stored sequence indicate that the run may commence?
No. The guide explicitly states the storage of records with validation errors for subsequent review. Therefore, separate file storage from professional and technical readiness. Define how open errors are detected and addressed. Verify the system's locking mechanism at the specific error case.
Can prior Access Audit records still be used?
The release notes describe continued readability. Whether this adequately establishes a historical transaction depends on content, links and access. Test a representative case. Demonstrate new event capture separately because the documented version creates no new entries in the former Access audit database. Readability alone does not establish complete migration.
Can a technical account replace the personal user?
A technical service account does not replace the personal assignment of technically relevant actions. Annex 11 No. 12.4 expects the identity of persons to be recorded, who enter, modify, confirm or delete data, including date and time. A service account can take over a documented operation task. However, check how measurement runs, changes and evaluations remain associated with the acting user. Changes to the service account itself follow the appropriate manufacturer procedure.
Does every batch release require an electronic signature?
Not every release decision necessarily requires an electronic signature. Clarify the applicable regulations and whether the specific decision, according to your established procedure, requires a signature. If performed electronically, EU GMP Annex 11, Section 14, outlines expectations regarding its function within the organization, permanent linkage to the record, and date and time stamp. A technical confirmation is not automatically considered an electronic signature.
Is Ardia merely an alternative storage path?
No, the described workflow comes with its own access and functional limitations. The Quick Start refers to registration and login, as well as the unavailability of the Processing Method when a specific Ardia Path is selected. Review the actual data flow, including transfer, authorisation, and subsequent processing. Clarify in advance whether Ardia is installed in your environment and which license covers the intended workflow.
Sources: [2]
Does the mentioned security patch constitute valid validation evidence?
No. The safety notification addresses a specific vulnerability and references corrected versions, along with additional support provided by the manufacturer. Assess the impact and appropriate actions. For the regulated laboratory operation, continued application-specific documentation remains required. Conversely, a technical validation review should not omit specific safety information from its scope of changes.
What information enables an assessment of validation effort?
Compile components and equipment, existing analysis pathways, sequence examples, data storage methods, roles, and prior validation evidence. Identify planned changes, legacy dependencies, and known incidents. This enables evaluation of open transition points and usable manufacturer documentation. The number of instruments alone does not determine effort or test volume; what matters are differing workflows and their actual validation requirements.
Sources and review date
Date: 6 October 2026. Product version: Xcalibur 4.7 SP1, Release Notes B51002737 Rev. A2 and Quick Start B51002734 Rev. A, Copyright 2024; device-specific configuration manual Rev. B, July 2025. No statement regarding the most recent applicable patch for any installation. Examples and calculated values are for internal reference purposes only; no device or software evaluation has been performed. Targeted source cross-reference conducted on 18 October 2026: EU GMP Annex 11, Section 12.4 and 14, relating to personalization of actions and electronic signatures.
- Thermo Scientific Xcalibur 4.7 SP1 – Release Notes
- Thermo Scientific Xcalibur 4.7 SP1 – Quick Start Guide
- Configuring the Data System for TNG Instruments
- Thermo Scientific Xcalibur and Foundation – Product Security Bulletin
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU GMP Chapter 4: Documentation
- FDA: Part 11 — Scope and Application
Sources checked: .
Make the actual measurement and data pathway verifiable
We support you in defining the scope of your Xcalibur installation, evaluating existing documentation, and preparing appropriate testing and operational qualification records.
- 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.

