Cytiva instrument integration

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.

• ÄKTA UNICORN connection overview

  Set up ÄKTA UNICORN in the docs ↗

  ASCII curves and peak tables; keep the UNICORN result archive separately.

  One chromatography run linked to the experiment, column and source files; add fraction or peak records only when you need to track them individually.

  Cytiva UNICORN 7.9 Evaluation Manual

• Cytiva Biacore Insight connection overview

  Set up Cytiva Biacore Insight in the docs ↗

  Excel evaluation exports and retained reports; native database exports are separate.

  One binding evaluation linked to the molecule, ligand and source runs, with selected fit parameters and supporting sensorgrams.

  Cytiva Biacore Insight software: evaluation and data export

• Cytiva Sepax C-Pro connection overview

  Set up Cytiva Sepax C-Pro in the docs ↗

  Sepax C-Pro PDF procedure reports and available procedural graph or log exports.

  One cell-processing procedure linked to input material, output fractions and its original report.

  Cytiva Sepax C-Pro: procedure reports and data management

Choose the export that answers the scientific question.

For UNICORN, a curve, an evaluated peak table and a native result archive have different roles. A curve helps explain the run; a selected peak result can support comparison; the native archive preserves vendor-specific context. Decide which evidence the receiving workflow needs rather than assuming one exported file contains everything.

Biacore Insight evaluation exports describe the chosen analysis and require its experimental and model context. A Sepax C-Pro procedure report records information about a processing run. Neither should be interpreted as evidence of a downstream assay that was never performed or imported.

Preserve material identity through fractions and evaluations.

A purification fraction needs a parent run and its own identity. Retain the collection boundaries and the axis used to describe them. Time and volume are not interchangeable coordinates without the relevant process history. Link later measurements to the collected material while keeping their analytical records separate from the purification record.

For binding results, retain the sample, ligand or surface context available in the report and the evaluation that produced the value. A revised fit should remain traceable to the source evidence. For processing workflows, distinguish input and output material identities and the reported outcome of the procedure.

Verify evidence continuity across the workflow.

Start with one completed run and follow a known fraction or output sample into its next assay. Check that references resolve to the intended material and that the selected results agree with the vendor report. Keep the original exports available so the review can inspect more than the copied numeric fields.

Test identical file delivery separately from a revised evaluation or a new physical run. Those events require different record handling. The configuration should avoid duplicate results while preserving new evidence and any review required before it supersedes a result already used in a report.

Example: link an ÄKTA fraction to a Biacore evaluation

The sample reference connects the workflows; it does not imply that their result types or units are interchangeable.

Purification

Keep the UNICORN run, method and curve or peak evidence.

Fraction

Resolve the fraction within its run and preserve its collection boundaries.

Binding result

Link the tested fraction to the Biacore evaluation and its analysis context.

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. Compare curve axes, boundaries and a selected evaluated result with the vendor view.
2. Trace one fraction into the next assay using source identities rather than matching filenames.
3. Verify that a changed evaluation preserves its relationship to the earlier evidence.

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

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