SampleManager LIMS does not expose laboratory execution as a single named module with one fixed sequence. Thermo Fisher documentation instead describes execution as a set of interacting capabilities: an integrated Laboratory Execution System (LES), a workflow engine that assigns tests and methods, stock and reagent records linked to analyses, mobile method execution, and audit transactions that capture field-level changes [1][2][3]. A lab evaluating the product therefore needs to distinguish the procedural record created by LES step guidance from the planning record created by the workflow engine, and from the inventory and audit records that surround both. The vendor's materials support this distinction, but they do not publish a complete data model showing how those records join across a single sample lifecycle. That gap is the most consequential unresolved question for teams planning validation or integration work.
Execution begins as a planning record, not a procedure
Thermo Fisher states that the workflow engine is the driving force behind planning functions. Samples can enter the system in a workflow or be added to a new workflow, and that process automatically assigns tests, monitors processing, and allocates tests or testing methods to designated users [3]. This means the execution workflow starts before an analyst opens a method: the system creates an assignment record that determines which tests exist for a sample and who is expected to perform them.
The planning layer is distinct from the step-by-step execution layer. The vendor describes LES as simplifying SOP compliance and method execution with step-by-step guidance while capturing procedural histories [1][6]. A pharma brochure lists reduced testing as a preconfigured feature, while environmental monitoring, media management, login plans, analyst qualification, content uniformity and dissolution appear with checkmarks under preconfigured LES method [5]. The source does not state whether every listed template includes a complete LES method or only a workflow configuration.
The LES record captures procedure, while the workflow record captures assignment
The distinction matters for audit readiness. Thermo Fisher says LES captures comprehensive procedural histories to enhance audit readiness and data integrity [6]. Separately, the FAQ describes audit transactions that record new and old values, the person who made the change, a timestamp, and a reason unless the audit is silent [3]. A lab should not assume that the LES procedural history and the field-level audit trail are the same record; the documentation presents them as separate capabilities with different triggers.
The ISO 17025 ebook offers a concrete view of the LES role. It states that the LES steps users through SOPs using detailed images and instructions, and that information on execution, consistent practice and control can be ensured through the LES [7]. That positions LES as the mechanism for turning a configured analytical method into a guided procedure. The same source says analytical methods can be configured to comply with various regulatory standards including ASTM and ISO [7]. Configuration is therefore the boundary between the product's generic capability and a lab's actual execution workflow.
A hypothetical execution scenario for a stability pull
A useful validation scenario would start with a scheduled stability pull. The scheduler registers the sample automatically at the planned time [3]. The workflow engine assigns the stability test and method to a qualified analyst [3]. The analyst opens the LES method on a tablet, follows the step guidance, and scans the sample barcode [2][6]. A reagent linked to the analysis is consumed, updating stock quantity [3]. The analyst records an observation, and the audit trail captures the field change with user, timestamp and reason [3][7]. This scenario is a suggestion for mapping record ownership; it is not a documented test result.
The scenario exposes the unresolved handoffs. The source does not state whether the scheduler-created registration record and the workflow-assigned test record are the same object, or whether the LES procedural history references the workflow assignment by a stable identifier. A lab planning validation should ask Thermo Fisher for the data model linking registration, assignment, LES execution, stock consumption and audit events before writing test scripts.
Stock, instruments and training are linked into execution rather than separate
Execution workflows in SampleManager LIMS are documented as consuming laboratory stock. Reagents can be directly linked to analyses for use in testing workflows, allowing users to see when reagents are required and how they are consumed, with quantity updated from consumption and new receipt [3]. Lot number, label, storage location, hazard, available amount, ordering, supplier and calculation parameters are stored for each stock batch [3]. This creates a dependency: an execution step that consumes a reagent should update a stock record, but the source does not specify whether that update is automatic or requires a separate transaction.
Training and instrument authorization also appear as execution preconditions. The vendor says training management verifies competencies and ensures role-based system access control prior to lab instrument usage and testing [1][6]. The ISO 17025 ebook shows training records outlining the SOPs, instruments and equipment an analyst is authorized to use, and instrument records showing whether instruments are authorized for use [7]. These are documented as capabilities that support execution, but the materials do not state that the system blocks execution when a training or instrument record is invalid.
Mobile and voice capture change where execution data originates
The mobile application is documented as a way to execute laboratory methods, collect data and manage samples on tablets [1]. The brochure adds that the native mobile app allows access to LIMS and LES features regardless of network connectivity, with offline capabilities so users can continue work without interruption [2]. That offline claim has a direct validation implication: a lab must determine how offline execution records are synchronized, versioned and reconciled with the server-side workflow record.
Voice control and barcode scanning are described as configurable methods for moving through processes. The software can be configured using barcode scanning and voice commands to step through lab methods such as sample tracking, inventory management and data recording [2]. Voice control is enabled with the mobile app using Siri and Google Assistant, while the LIMS client uses a configurable barcoding process screen [2]. These are input modalities, not separate execution engines, and the documentation does not state whether voice commands can trigger all LES actions or only navigation.
Deployment and version boundaries affect workflow ownership
SampleManager LIMS can be deployed on-premises or in the cloud using the customer's own or Thermo Fisher-managed infrastructure [1][6]. Version 21.3 is the latest documented release, with updates including SAP remote function calls, an upgraded Sweeper for complex files, resource management for task assignment, token authentication and hardened session handling for the REST API [4]. These version-specific changes matter because a workflow built on one version may depend on integration or security behavior that changes in the next.
The pharma brochure describes standardized workflows refined through regulated pharmaceutical implementations and a validation toolkit with OQ scripts, executed OQ scripts and a trace matrix enabling risk-based validation [5]. That positions validation as a workflow-level activity rather than a purely technical exercise. However, the source does not publish the trace matrix itself, so a lab cannot verify from public documentation which execution records are covered by which validation artifact.
Sources & references
- SampleManager LIMS Software – Enhance Lab Productivity & Compliance | Thermo Fisher Scientific | Thermo Fisher Scientific - US · www.thermofisher.com
- SampleManager LIMS, SDMS, LES and ELN software · documents.thermofisher.com
- SampleManager LIMS™ Software - FAQs · www.thermofisher.com
- SampleManager LIMS 21.3 | Thermo Fisher Scientific - US · www.thermofisher.com
- Pharma Solution for manufacturing QA/QC · documents.thermofisher.com
- SampleManager LIMS Software – Enhance Lab Productivity & Compliance | Thermo Fisher Scientific | Thermo Fisher Scientific - US · www.thermofisher.com
- How LIMS enables compliance with ISO 17025 · documents.thermofisher.com