Sartorius instrument integration

Sartorius workflows connect culture conditions, process measurements and analytical observations. Ambr and Biostat evidence describes a culture or process run; Octet, iQue and Incucyte evidence describes an analysis of material or behavior under specific conditions. Seal can connect those records through configured export collection and mapping without collapsing their different meanings.

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.

Select the Ambr model and source application explicitly.

Ambr 15, Ambr 250 High Throughput and Ambr 250 Modular have separate setup guides. Confirm the installed software and enabled export options for the actual system. BioPAT MFCS batch exports and optional interfaces also depend on the deployment. A model name alone does not establish that a particular export module or interface is available.

For Octet, identify the evaluation and report needed for the binding question. Forecyt protocol exports and iQue result exports serve different purposes. Incucyte metric exports need their corresponding image or movie context where that evidence is part of the study. Configure each source around a known completed experiment.

Connect vessels, collected samples and analytical runs.

Identify a vessel within its experiment so the same position in a later experiment cannot overwrite it. Give offline samples their own identities and preserve collection time separately from analysis time. That distinction lets scientists compare a culture event with the appropriate sample even when the assay ran later.

Keep setpoints separate from measured process channels, and retain the time basis for trend summaries. For Octet, preserve the evaluation model and conditions associated with a reported binding result. For imaging or cytometry, retain the analysis definitions needed to understand a metric rather than treating the metric’s display name as a complete specification.

Make comparisons explicit about coverage and analysis.

A process-development comparison should identify the experiment set, vessels, time window and any exclusions. Store detailed exports as Files and map the selected observations or summaries needed for that comparison. If the exported trend is incomplete, keep coverage visible rather than allowing a missing interval to look like a complete experiment.

Reanalysis can change an Octet fit, an iQue population statistic or an Incucyte metric without changing the original acquisition. Preserve the source revision used for the comparison. Review the mapping when export settings or analysis definitions change, and keep the prior evidence behind decisions already made.

Example: compare culture conditions with a later binding assay

The connection follows sample provenance while preserving the process and analytical evidence independently.

Culture
Reference the Ambr experiment and vessel, with the relevant process window.
Collected material
Record the sample identity and collection event within that culture.
Binding evaluation
Link the Octet source run, evaluation context and selected binding result to the sample.

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. Import two studies that reuse vessel positions and verify that their identities stay separate.
  2. Compare collection times, process events and assay times using the agreed timezone and elapsed-time basis.
  3. Test incomplete trend coverage and a revised analytical evaluation before using cross-run summaries.

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

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

What are you connecting?

All connection guides