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.
Revvity LabChip GXII Touch connection overview →
Peak tables, well tables and raw-data CSV or XML exports selected in LabChip Export Setup.
One sample-well analysis with selected purity, size or concentration results and linked electropherograms.
Revvity Operetta Harmony connection overview →
Harmony analysis-result exports and selected image evidence; confirm the installed export layout.
One sample-well analysis with selected phenotype metrics and links to the acquisition and analysis sequence.
Revvity EnVision connection overview →
EnVision exported plate results and reports; confirm the format for the installed EnVision software.
One plate assay linked to selected sample-well responses and the acquisition protocol.
Revvity Cellaca MX connection overview →
Cellaca MX configured CSV or Excel assay-report exports with retained images and reports.
One sample-well count analysis linked to plate scan, assay and source images.
2Choose the result level exposed by the source application.
LabChip exports can distinguish peak, well and raw-data tables. Harmony results depend on the selected image-analysis workflow and export layout. EnVision results need the measurement mode and plate context, while Cellaca MX reports need the configured assay and counting context. Identify the output that actually supports the intended question.
Retain images, curves or other detailed evidence where they are part of the interpretation. A table of image-derived measurements does not replace the images and analysis settings behind it. A plate-reader signal also differs from an evaluated concentration derived through an assay-specific calculation.
3Resolve plates, wells and samples without flattening the analysis.
A well address is meaningful within its plate or source run. Preserve that parent identity and the layout linking wells to samples, controls and standards. If the analysis reports multiple channels, features, populations or time points, choose a record model that keeps those dimensions instead of repeatedly overwriting one result field.
Keep the relationship between detailed observations and reported summaries. For example, an image-analysis summary may derive from selected fields of view or objects; a cell count may involve dilution and classification rules. Retain the relevant context provided by the export and identify any additional transformation performed by the Seal Script.
4Check exclusions and reanalysis explicitly.
Missing wells, rejected objects and excluded results should remain distinguishable from valid observations. Configure the mapping around representative exports that include those cases. A successful transfer of a numeric table does not establish that all expected samples or fields were included in the analysis.
A changed image-analysis protocol or assay report can change both the values and the structure of an export. Record the source version and test a revised analysis against the mapping. Retain the earlier evidence used in a review and expose the revision relationship when the new result is introduced.
5Example: connect an imaging plate and its sample-level assay
A shared sample map joins the evidence while each analysis retains its own method and result dimensions.
- Plate layout
- Resolve the plate and well-to-sample assignments used by the source application.
- Imaging result
- Retain the Harmony analysis identity, selected features and related image evidence.
- Assay result
- Link the corresponding sample result with its detection mode, unit and qualifiers.
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.
- Compare a known plate containing a sample, control and empty or excluded well with the source report.
- Verify that multi-channel or multi-feature exports preserve every dimension required for interpretation.
- Test a changed analysis layout and ensure unexpected columns are held for review instead of silently remapped.
Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.
Discuss your Revvity workflow with a representative export, the installed software version and the records you want to connect.