Tecan instrument integration

Tecan integration can connect Fluent sample preparation with Spark plate-reader assays. The important boundary is between instructions, execution evidence and analytical results. Seal can preserve those relationships through supported exports and configured Scripts; a planned worklist alone does not establish that a transfer happened or that an assay result exists.

Choose your instrument software

Choose the source software and evidence.

These are connection routes to configure using the documented source output. Check the installed version, licensed options and export settings in the linked platform docs; the listing does not install an acquisition driver or a universal parser.

Confirm the installed Fluent and reader software options.

For Fluent, verify that the relevant sample-tracking add-on and report exports are configured. An input or worklist export may describe requested work rather than completed transfers. Establish which available report carries the run identity, sample relationships and outcomes needed for your process, including the limits of its detail.

For Spark, distinguish SparkControl result exports from analysis and export options configured in Magellan. Keep the plate layout and detection or analysis context with the selected results. The mapping should be based on a representative file from the installed workflow, not a generic assumption about all Tecan spreadsheets.

Trace the prepared plate into the assay.

Resolve source and destination containers as well as well addresses. Preserve the preparation request, the vendor execution identity and the available outcome evidence. A destination well may have several contributors or dilutions, so keep the relationships needed to explain the material that was subsequently measured.

Link the reader’s plate and sample layout to the prepared destination. Keep assay signals, calculated results, units and qualifiers separate from preparation quantities. A requested transfer volume is not an analytical concentration, and a completed reader export does not prove the preceding preparation was complete.

Make retries safe across preparation and measurement.

Configure collection so an identical report can be delivered again without duplicating a preparation or result. If separately supported dispatch is in scope, use a stable request identity and reconcile uncertain acknowledgements before resubmitting physical work. Repeating a file transfer must not accidentally repeat an instrument run.

Test a partial preparation and an assay with an excluded or missing well. The connected record should retain unresolved outcomes instead of appearing complete because one expected report arrived. Keep the evidence used for review, and distinguish an intentional rerun from a duplicate delivery of the same run.

Example: connect a Fluent preparation to a Spark result

Use separate identities for the requested preparation, reported execution and analytical measurement.

Preparation
Retain source-to-destination assignments and the reported Fluent execution outcome.
Destination plate
Resolve the prepared plate and wells to the sample layout used by the reader.
Assay
Link the Spark result with its detection mode, analysis context and original export.

Use these relationships as a mapping example for your own templates. The receiving fields and record grain remain configurable through normal Seal Scripts and APIs.

Configure the collection and mapping for your site.

For local exports, use a completed-file handoff on the instrument workstation or another approved site computer. Seal IoT collects the file and uploads it to the chosen Seal destination over outbound HTTPS. Keep source files until delivery and mapping have been verified.

A Seal Script can validate the expected layout, resolve source identities and write selected typed fields. Keep the original export as File content. Acquisition and vendor analysis remain in the source application; configure and verify any separately supported dispatch operation on its own terms.

Follow the on-site equipment setup instructions, then use the source-specific guide above to test the actual export and mapping. For a result exchange with an existing LIMS, also define that system’s supported receiving operation and sample identifiers.

Test the configured workflow with known evidence.

  1. Trace a known transfer and a pooled destination into the reader’s sample layout.
  2. Verify that partial execution and excluded assay wells remain visible in the receiving records.
  3. Replay a report and test an intentional rerun, confirming that neither handling path dispatches unintended physical work.

Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.

Discuss your Tecan workflow with a representative export, the installed software version and the records you want to connect.

What are you connecting?

All connection guides