Agilent instrument integration

Agilent instrument integration spans several different kinds of laboratory evidence: chromatographic signals, mass-spectrometry results, electrophoresis measurements, plate assays and cellular metabolism studies. Start with the software that produces the result your team needs. A connection for one Agilent application does not define the file layout or analytical meaning of another.

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.

Choose the result-producing application.

OpenLab CDS and MassHunter support different analytical workflows. For chromatography, distinguish exported detector signals from evaluated peak or concentration reports. For quantitative mass spectrometry, identify the batch, sample and analyte result you intend to transfer, together with its calibration and qualification context. A raw acquisition remains valuable evidence even when a smaller results table drives the workflow.

TapeStation and Bioanalyzer results need their sample, lane or well relationships and assay context. Gen5 plate assays need a layout and the calculation behind the reported value. Seahorse results add a time-dependent experiment with injection or assay phases. Use the individual setup guides below to select evidence appropriate to that application.

Connect assays through sample identity, not matching column names.

A sample can appear in a TapeStation assay and later in another analytical workflow. Reuse the sample reference while preserving a separate record for each measurement or evaluated result. Keep the method, source run, unit and revision on those records so a downstream comparison can identify what each number represents.

Decide which detailed arrays remain in source Files and which selected values become queryable fields. Electropherograms, chromatograms and kinetic traces should retain their axes and coverage. An export summary should not appear to contain the complete acquisition when it includes only selected lanes, channels or evaluation results.

Verify one complete analytical path before broadening collection.

Begin with one known sample and the matching vendor report. Compare the source identity and selected values after collection and mapping, then try a repeated export and a revised analysis. Retain the report or source archive needed to understand the revision rather than silently replacing a previously used result.

Treat a software upgrade, report change or newly enabled analysis mode as a possible change to the import contract. Check field names, units and the meaning of the exported values. Expand the integration only after a representative example of the additional mode has passed the same review.

Example: electrophoresis evidence beside a downstream assay

The source applications produce separate evidence, while the sample reference lets your team follow the material through the study.

Sample
Resolve the existing sample using the full study and source sample identity.
Electrophoresis result
Retain the assay, source well or lane, selected quality metrics and original export.
Subsequent assay
Create its own method-specific result record and link it to the same 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. Compare an evaluated result and its matching raw or detailed evidence with the vendor application.
  2. Test a multi-sample export so lane, well and sample assignments cannot shift silently.
  3. Verify that an identical delivery is distinct from a new evaluation of the same source run.

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

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

What are you connecting?

All connection guides