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.
Waters Empower connection overview →
ASCII raw-data exports (.arw) and separately configured result reports.
One analytical result per injection or sample, linked to the experiment and original files; preserve reprocessed results as separate source revisions.
Waters MassLynx connection overview →
TargetLynx CSV or tab-delimited summary exports; retain QLD results and RAW acquisitions.
One injection analysis with analyte-specific concentration and qualifier fields linked to the source result set.
Waters Wyatt ASTRA connection overview →
ASTRA text exports of selected data and result tables, with original experiment files retained.
One sample evaluation with selected peak-level mass or size results and source files; add peak records when the study tracks them individually.
Waters Wyatt DYNAMICS connection overview →
Exported result tables and CSV data underlying graphs; preserve experiment files separately.
One sample measurement or well summary linked to its experiment and raw exports, with selected size and dispersity fields.
2Separate raw acquisitions from evaluated result exports.
An Empower raw-data export and an evaluated result report do not contain the same information. Likewise, MassLynx acquisition files, TargetLynx results and exported summaries have distinct purposes. Confirm which output contains the analytes or selected measurements needed by the receiving workflow and which files should be retained as source evidence.
Wyatt ASTRA and DYNAMICS add characterisation workflows with their own detector, method and analysis context. Keep their reported quantities distinct from chromatography or mass-spectrometry values. A shared sample reference connects the measurements; it does not make similarly named output columns analytically equivalent.
3Keep injection, analyte and analysis identities.
A sample may have multiple injections, analytes and evaluations. Resolve those identities before writing selected results. A repeated sample display name is not a safe key across batches or sequences. Preserve the source system and run identity so a reviewer can return from a Seal result to the correct vendor evidence.
For multi-detector or scattering results, retain the calculation and method information available in the export. Keep qualifiers and fit or evaluation context alongside numeric values. If a result depends on a selected peak or interval, retain that selection instead of presenting the value as an unconditional property of the entire sample.
4Test revised analysis as well as repeated collection.
Reprocessing a chromatography or quantitative analysis can legitimately change an evaluated result while the acquisition remains the same. Configure revision handling so the updated evidence is identifiable and does not silently erase the version used for an earlier decision. A duplicate upload, by contrast, should not manufacture another analytical result.
For a comparison across Waters and Wyatt workflows, identify the sample population, methods, units and relevant source revisions. Preserve missing or excluded results explicitly. Use the individual setup guide for the installed software before expanding a mapping from one analysis mode to another.
5Example: combine a chromatographic result and characterisation evidence
Keep separate analytical results connected to one material record, with the exact source analysis attached to each.
- Sample
- Resolve the sample across the relevant experiment and source system identities.
- Chromatography
- Retain the Empower injection and evaluated peak or analyte result.
- Characterisation
- Link the ASTRA or DYNAMICS result with its method, evaluation context and source 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.
- Verify a sample with more than one injection or analyte so the mapping preserves the extra dimension.
- Compare a selected characterisation value with the analysis settings and source evidence that produced it.
- Deliver an identical export and a revised result separately, checking their different record outcomes.
Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.
Discuss your Waters workflow with a representative export, the installed software version and the records you want to connect.