Platform / Lab operations

A working lab.A connected operation.

Coordinate instrument configurations, processing methods, and active runs across the lab. See what was configured, what ran, and where your team needs to intervene.

A shared research laboratory and its connected operationsA microscope acquisition station and two analysis workstations share a fitted island, surrounded by enclosed imaging and acquisition systems, a full-height compute rack, and a shared work queue.Instrument suitesAcquisition & analysisWork queueCompleteRunningQueuedCompute & records

01 / Before the run

Make the setup
part of the record.

Follow a recording from instrument setup to a configured analysis run. See how acquisition settings, source files, and processing parameters are recorded along the way.

01 / Place the work

Start with the scientific purpose.

Connect the recording to its project and lab site. Give the work a setting that another researcher can understand.

A shared starting point

Inspect the setup
Project
Cellular activity
Lab site
Imaging room A
Scope
Representative recordings for a defined analysis
A recording belongs to an experiment.PROJECT / Cellular activityLAB SITE / Imaging room A
Keep the scientific purpose and the lab setting with the recording.

02 / Describe the equipment

Make the shared setup visible.

Connect the instrument, detector and acquisition computer to a rig configuration. Keep calibration references with the equipment they describe.

Equipment knowledge the team can reuse

Inspect the setup
Rig
Imaging rig A
Configuration
Instrument, detector and acquisition computer
Reference
Calibration record linked to the equipment
The rig becomes a described configuration.Configuration 2DetectorInstrumentAcquisition computerCalibration reference
Equipment profiles can be reused; each recording retains the acquisition settings used to collect it.

03 / Capture this recording

Keep what actually happened.

Start from an acquisition profile, then capture the observed setup. An adjustment belongs with the recording, alongside the planned settings.

The plan and the observed setup, together

Inspect the setup
Profile
Example imaging acquisition · revision 2
Planned exposure
40 ms
Observed exposure
45 ms · adjusted for this recording
Recording A carries its collection settings.collected withRecording AAcquisition profile · revision 2Planned exposure40 msObserved exposure45 ms
The highlighted exposure change is an invented example of a recording-specific adjustment.

04 / Prepare the analysis

Give this run its own configuration.

Select a processing method and parameter preset. Retain the resolved settings for this run, with a connection back to the recording.

A reusable method. A specific run.

Inspect the setup
Method
Cellular activity · version 3
Preset
Lab processing parameters
Run configuration
Resolved settings retained for Recording A
Acquisition settings inform method selection.Processing methodCellular activity · v3Lab parameter presetretained for this runRun configurationResolved settings retainedRecording A
Acquisition settings describe collection. Processing settings describe the analysis to be performed.

05 / Establish where it runs

Connect the work to its environment.

Identify the source and output storage, then assign processing within the approved environment. The run keeps the references that connect it all.

An execution location and a supporting record

Inspect the setup
Storage
Institution-controlled research storage
Compute
Approved institutional worker
Coordination
Run assignment and retained artifact references
A connected record, ready for the next step.Run configurationResolved settings retainedRecording Afile accesswork assignmentResearch storageSource files + outputsApproved computeInstitutional worker
File access and processing assignment are different relationships. Both belong in the operating picture.

02 / While the work moves

Understand the batch.
Inspect the individual run.

Select a recording below. Each state calls for a different next action, with the method version and source files still linked.

A recording becomes a reviewed result

Example project / Cellular activity

A morning of recordings

04 recordings
Acquisition
Imaging setup · revision 2
Processing
Cellular activity · version 3
Execution
Institutional compute

Select a recording

Recording C / Needs attention

An interruption should leave a trail.

  1. 1
    Attempt 1 · interrupted

    Worker unavailable during region extraction.

  2. 2
    Inspect the run

    Check the input references, settings and available resources.

  3. 3
    Choose the next action

    Resolve the environment issue before requesting another attempt.

  4. 4
    Retain both attempts

    A subsequent attempt belongs in the history of the same work.

UnifiedFlow + institutional IT

Check worker availability and coordinate a retry.

In this example, a worker becomes unavailable. The operator checks the cause and decides whether another attempt is appropriate.

Investigate interruptions and coordinate the next attempt.

03 / Beyond one session

Make the next handover
easier than the last.

Technical completion, scientific review and routine operational use are distinct steps.

Investigate from the run history

Keep the source references, run settings, stage attempts and output records available to the people supporting the workflow. A new operator should have a starting point for investigating the work.

Change with a reference point

When equipment, processing settings or methods change, identify the affected workflow and evaluate the next configuration with the lab. Retain the configuration used by earlier runs.

Follow the record behind a result

Supporting the operation

Connect the work to its environment.

A conversation, grounded in your work

Start with the work your lab repeats.

We’ll discuss the equipment, methods and operational steps needed to make that workflow easier to run and support.

Discuss your workflow