Skip to main content

Fluidic Sciences instruments in Seal

Seal Edge collects the files Fluidic Sciences software saves and sends each original to Seal, linked to its sample, method and run.

Fluidic Sciences instruments to SealInstrument export

Seal reads
Exports from Fluidity Insight
Writes back
No
Source of truth
Instrument software
Set up
Seal Edge and an upload Script

1How the results reach Seal.

In the laboratory

Fluidic Sciences Fluidity Insight and Fluidity One-M

  • Fluidity Insight

Export folder

On the workstation or a network share

Seal Edge

Waits until each file is complete, then sends it

Outbound HTTPSNo inbound connection

Nothing is written back to the instrument or its software

In Seal

Seal Script

Checks the file’s layout and matches it to its record

Record

Sample and run

  • Result
  • Unit
  • Method
  • Original file, kept
How a result from the Fluidic Sciences Fluidity Insight and Fluidity One-M reaches Seal.

Results from the Fluidic Sciences Fluidity Insight and Fluidity One-M come from Fluidity Insight.

Seal Edge runs on the instrument workstation, or a host that can read the files, and watches the folder the software exports to. When a file is complete it sends it to Seal over outbound HTTPS; no inbound connection to the workstation is needed.

A Seal Script checks the export’s layout, resolves the record it belongs to and writes the selected values into typed fields. The original file is kept with the result. Acquisition and analysis stay in Fluidity Insight: Seal collects completed results and sends nothing back to the instrument or its software.

How capture works and what IT confirms are set out on the instruments page; the setup instructions cover installation.

2The Fluidic Sciences models.

These are Fluidic Sciences instruments laboratories connect to Seal, listed from the manufacturer’s own documents. A model not listed here works the same way if its software saves a file: send us the model and an example output.

Other

  • Fluidity Insight
  • Fluidity One-M

3Start with one instrument.

Bring the model, the installed software version and an example output. We map the connection into your workflow and test it with a late file, a duplicate transfer and a failed integrity check before you rely on it. Discuss your Fluidic Sciences instruments.

See your process in Seal.

Bring a procedure or a recurring problem. See how your team configures it with Neil and improves the next run.