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.
METTLER TOLEDO LabX connection overview →
CSV or XML through the LabX Auto Import / Export option.
One weighing or analytical task with typed results and source evidence; relate it to the sample or material record.
METTLER TOLEDO STARe connection overview →
STARe exported curves and evaluation reports; verify the configured data-export option and layout.
One sample thermal evaluation with selected transition or mass-change results and original curve evidence.
2Verify the installed LabX or STARe interface.
LabX export options depend on the configured application and licensed capabilities. Confirm the source instrument, result type and export layout rather than assuming every instrument connected to LabX produces an identical table. Keep a representative export with its matching report and the software configuration needed to reproduce it.
STARe workflows involve curves and evaluated thermal-analysis results. Confirm the installed data-export option and the chosen report layout. A native project, a plotted curve and a selected evaluation table serve different purposes; identify which is suitable for mapping and which should be retained as source evidence.
3Keep units, method context and the source result together.
Laboratory results need the sample or material identity, the measurement unit and the relevant method or task context. Preserve the source result identifier so repeated collection can be recognised. Where the source reports several values for one task, map their distinct meanings explicitly instead of selecting a numeric column by position.
For thermal analysis, preserve the curve axes, method program and evaluation context available in the source output. A selected transition or peak result depends on how the measurement and evaluation were performed. Keep the original curve linked to the evaluated value so interpretation does not depend on a number stripped of its experimental setting.
4Review calculations and source revisions before using results.
Decide which calculations belong in the vendor application and which are explicitly performed by the receiving Script. Preserve reported values and units before any transformation. A unit conversion or normalisation should have a defined rule and a test example, especially where a result is later compared with a specification.
Check an identical export, a corrected source result and a changed report layout. The first should not duplicate the measurement; the second needs traceable revision handling; the third may require an updated mapping. Keep those outcomes separate from the review or release decision made in your operational workflow.
5Example: connect a laboratory task and thermal characterisation
The same material can have several measurements without losing the source and method behind each one.
- Material
- Resolve the existing sample or material reference for the laboratory work.
- LabX result
- Retain the source task, result identity, reported unit and original export.
- Thermal result
- Link the STARe curve and evaluation with its method context and selected typed values.
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 result, its reported unit and any configured conversion against the source report.
- Verify the axes and evaluation context associated with a selected thermal-analysis result.
- Confirm that corrected results and changed export layouts are handled explicitly and preserve source evidence.
Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.
Discuss your METTLER TOLEDO workflow with a representative export, the installed software version and the records you want to connect.