Ambr 15 and Ambr 250 to LIMS: culture and sample data

Offline lactate for one culture

These example records keep a delayed laboratory result attached to the correct sampling event.

Culture
EXP-021 / vessel 12
Reference the source experiment and vessel together.
Sampling event
SMP-063 at 48 h
Retain collection timestamp and timezone.
Offline result
Lactate / 1.8 g/L
Link the analyser result and method to SMP-063, not merely vessel 12.
Coverage
Process export spans 0–72 h
Record gaps and any reduction before comparing the culture profile.

Treat Ambr 15, 250 High Throughput and 250 Modular as distinct sources.

Confirm the exact instrument model, installed software and export options. The Ambr 15 profile describes periodic CSV through the documented LIMS export module where the required option is installed. Do not transfer that claim automatically to an Ambr 250 configuration. High Throughput, Modular, generation and process options need their own source review.

Decide which evidence the first workflow needs: a complete experiment archive, selected measured parameters, feed events or an offline sample table. Keep measured values distinct from setpoints and recipe settings. An exported setpoint does not prove the culture achieved it, and an available software report does not establish that every historical point is present.

Use experiment, vessel and sampling event together.

Vessel numbers are routinely reused across experiments. Build the receiving identity from the source experiment and vessel, then identify each sampling event within that culture. A label such as vessel 12 cannot safely resolve a sample on its own. Retain any LIMS or offline-analyser sample ID as another explicit reference.

Keep acquisition time, sampling time and result evaluation time separately. When an offline analyser reports a concentration hours after collection, assign that result to the sample time rather than treating the analysis time as a new culture observation. Preserve timezones and the rule used to calculate elapsed culture time.

Choose record granularity around the scientific question.

One experiment with vessel references and source Files can support selected sample results or interval summaries. There is no requirement to create an entity for each raw measurement. If comparing daily growth, retain the exact observations used and their sampling times; if studying a short excursion, choose coverage that can represent the event.

For any aggregation, record the parameter, unit, interval, statistic and coverage. A mean over a full interval and a mean over two surviving points are different evidence. Keep missing periods visible. File collection follows actual exports and does not itself request measurements or make a manual export continuous.

Keep offline test results attached to the sampled culture.

Define the source of record for sample registration, test requests, results and acceptance status. Collection into Seal and writing a request into a LIMS are separate operations. Use the receiving system’s supported interface and agree which fields a Script may update. Preserve analyst notes and review decisions outside import-owned fields.

Reconcile expected sampling events against received results. Missing, failed and qualified results should remain distinct from valid zero values. For a repeated result or revised evaluation, match the source sample and analysis revision before deciding whether to update a permitted field or retain a linked revision.

Test it with your data.

Use these cases to agree and test the connection’s behaviour. They are proposed acceptance checks, not completed tests or automatic connector features.

The assay was measured an hour after sampling

PD-12 / vessel 3 was sampled at culture hour 36. The analyser measured the sample at hour 37.

Expected behaviour: Associate the result with the hour-36 collection event. Retain hour 37 as measurement time; do not shift the sample along the culture timeline.
Evidence to keep: The vessel reference, both timestamps, the elapsed-time origin and the source assay record.

A vessel position is reused in the next study

PD-13 also has a vessel 3. A result arrives with a vessel position but no experiment identifier.

Expected behaviour: Hold the match for resolution. Require experiment and vessel identity together before adding the result to a culture comparison.
Evidence to keep: The unmatched input, the identity rule and the resolved study and vessel references.

More checks for this connection

Import two experiments that both contain vessel 12 and verify they remain separate.
Compare a delayed offline result with its original sample time.
Test a qualified result, missing unit and daylight-saving boundary.
Measure the intended export volume and test recovery after interrupted delivery.

Before you connect

Can the integration upload at every measurement?

Available export behavior depends on the installed system. Choose and test the required export cadence and record granularity; a directory listing does not establish an acquisition rate.

Are Ambr 15 and Ambr 250 exports interchangeable?

No. Confirm the model, software and licensed interface, then map representative exports from that configuration.

Check your system’s connection options.

Confirm the installed version, available exports and permissions. These pages cover the source interface and link to setup instructions.

For configuration: Seal Scripts and local-file collection.

Start with one export.

Bring the source evidence and the records it needs to connect to. For this workflow, a useful starting pack is:

The Ambr model, software version and one representative experiment export.
A vessel map, inoculation times and the study’s definition of elapsed time.
A sample collection log and matching offline assay results, including units and qualifiers.

Discuss this connection