1Choose the source software and evidence.
Each route starts from a documented output of the vendor software. Check the installed version, licensed options and export settings against the linked docs. A listed route is not an acquisition driver or a universal parser.
Tecan Spark connection overview →
SparkControl XLSX results; Magellan supports configured ASCII and Excel exports.
One plate assay linked to well results with selected raw signals or calculated endpoints.
Tecan Fluent connection overview →
FluentControl Sample Tracking PDF reports and optional CSV exports; the add-on must be configured.
One preparation run with selected transfer or plate-result records linked to the tracking report.
2Confirm 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.
3Trace 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.
4Make retries safe across preparation and measurement.
Configure collection so an identical report can be delivered again without duplicating a preparation or result. Distinguish a repeated file delivery from a repeated 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.
5Example: 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 are configured through Seal Scripts and APIs.
6Configure 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; Seal collects the completed results and does not send instructions to the instrument.
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.
7Test the configured workflow with known evidence.
- Trace a known transfer and a pooled destination into the reader’s sample layout.
- Verify that partial execution and excluded assay wells remain visible in the receiving records.
- Replay a report and test an intentional rerun, confirming that the replay does not duplicate a preparation or result.
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.