Skip to main content

PHCbi instruments in Seal

Seal IoT collects the files PHCbi instruments save, directly or through LabSVIFT, and sends each original to Seal over outbound HTTPS, linked to its sample, method and run.

Illustration of a seal following a sample vial to an analytical instrument and its result.

PHCbi instruments to SealInstrument export

Seal reads
Exports from LabSVIFT
Writes back
No
Source of truth
Instrument software
Set up
Seal IoT and an upload Script

1How the results reach Seal.

In the laboratory

PHCbi freezers

  • LabSVIFTSaves CSV data to a local or cloud folder

Export folder

On the workstation or a network share

Seal IoT

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

Storage unit

  • Temperature
  • Set point
  • Alarm
  • Original file, kept
How a result from the PHCbi freezers reaches Seal.

Results from the PHCbi freezers come from LabSVIFT.

Seal IoT 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 LabSVIFT: 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 software and what it saves.

LabSVIFT
20 models: incubators, freezers and refrigerators. Saves CSV data to a local or cloud folder.

Saved by the instrument

Incubators, freezers and refrigerators
36 models. Each saves logged data over USB.

3The PHCbi models.

These are PHCbi 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.

Freezers

Cabinet temperature over time and alarm events, from the unit’s own log or a monitoring system.

  • MDF-594 Chest ULT Freezer
  • MDF-794 Chest ULT Freezer
  • MDF-1156 Cryogenic Freezer (-152°C)
  • MDF-C2156VAN Cryogenic Freezer (-150°C)
  • MDF-C2156VANC
  • MDF-DU502VHA
  • MDF-DU503VHA
  • MDF-DU702VHA
  • MDF-DU703VHA
  • MDF-DU901VHA
  • MDF-MU339H
  • MDF-MU339HL
  • MDF-MU539H
  • MDF-MU539HL
  • MDF-MU549DH
  • MDF-MU549DHL
  • MDF-U731
  • MDF-U731M
  • PRO ECO MDF-DU300H
  • TwinGuard ECO MDF-DU303VXH
  • TwinGuard ECO MDF-DU503VXH
  • TwinGuard ECO MDF-DU703VXH
  • TwinGuard MDF-DC500VX Chest
  • TwinGuard MDF-DC700VX Chest
  • TwinGuard MDF-DU702VX
  • TwinGuard MDF-U500VX
  • TwinGuard MDF-U700VX
  • VIP ECO MDF-DC102VH Chest
  • VIP ECO MDF-DC202VH Chest
  • VIP ECO MDF-DU500ZH
  • VIP ECO MDF-DU502VH
  • VIP ECO MDF-DU503VH
  • VIP ECO MDF-DU700ZH
  • VIP ECO MDF-DU702VH
  • VIP ECO MDF-DU703VH
  • VIP ECO MDF-DU901VH
  • VIP MDF-DU900V
  • VIP MDF-U33V
  • VIP MDF-U54V
  • VIP MDF-U55V
  • VIP MDF-U74V

Incubators

Chamber temperature over time, with carbon dioxide and humidity where they are controlled, and alarm events.

  • MCO-50AICL
  • MCO-50M
  • MCO-80ICL
  • MCO-170ACL
  • MCO-170AICUVDL
  • MCO-170MP
  • MCO-171AICUVD
  • MCO-173AICUV
  • MCO-173AICUVH
  • MCO-173AICUVHX
  • MCO-173AICUVX
  • MCO-233AICUV
  • MCO-233AICUVH
  • MCO-233AICUVHX
  • MCO-233AICUVX
  • MIR-154
  • MIR-254
  • MIR-554

Refrigerators

Cabinet temperature over time and alarm events, from the unit’s own log or a monitoring system.

  • MPR-722
  • MPR-722R
  • MPR-1412
  • MPR-1412R
  • MPR-N200H
  • MPR-N250FH
  • MPR-N250FSH
  • MPR-N450FH
  • MPR-N450FSH
  • MPR-N650FH
  • MPR-S300H
  • MPR-S500H
  • MPR-S500RH
  • MPR-S1201RXH
  • MPR-S1201XH

Other

  • MLR-352H

4Where the results go next.

Blueprints

5Start 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 PHCbi instruments.