UnifiedFlowInfrastructure for Evidence

Deployment / On-premises & hybrid

Built around the work.Within your environment.

Establish where your research data lives, where processing runs and who keeps the workflow operating.

Explore the environmentFor institutional IT
An approved environment around your research workflowInstitution-controlled research storage and on-premises compute share a connected working environment. An optional approved cloud environment extends processing, while workflow coordination connects the work across the agreed deployment.Your institutionOn-premises computeResearch storageInstitution-controlledApproved cloudAn option for your workflowConfigureRunReviewWorkflow coordinationThe agreed environment

An environment for the work

Your infrastructure.
A connected research workflow.

Follow the path from recording to processing, then see how the people and services keep the work connected.

01 / The data

Start where the data lives.

Connect acquisition systems to institution-controlled research storage. Keep recordings and acquisition metadata accessible to the approved processing environment.

An identifiable home for inputs and outputs.

Explore the operating details
Sources
Instruments, recording files, and captured acquisition metadata.
Storage
Agree source and output locations, access and retention.
Ownership
Institutional IT manages research storage and its backup arrangements.
The recording has a home. Local processing remains selected.Institution-approved environmentLab acquisitionResearch storageSource files + outputs
Acquisition feeds research storage within the institution-approved environment.

02 / Local processing

Bring processing to the work.

Use approved institutional compute for the selected workflow. Establish which inputs it reads, where outputs are written and how much capacity the work needs.

Place the workflow around available resources.

Explore the operating details
Compute
Identify suitable workers and the workflow requirements they must meet.
Access
Verify the worker can read selected inputs and write to designated output storage.
Capacity
Exercise representative inputs before agreeing routine workload expectations.
Processing connects to the stored work. Local processing remains selected.Institutional processingResearch storageSource files + outputsInputs / outputsInstitutional computeApproved processing workers
Local workers read selected inputs and write outputs to designated research storage.

03 / The cloud option

Extend where appropriate.

Some workflows may use approved cloud compute. Compare the arrangements here: selected inputs, returned outputs and temporary copies all need a defined scope.

Choose where work runs; agree what moves.

Explore the operating details
Transfer
Specify the inputs and outputs permitted to move across environments.
Temporary storage
Define temporary copies, retention and cleanup.
Placement
Cloud use is configured for an agreed workflow; it does not imply automatic overflow or failover.
Compare the processing arrangements. Local processing remains selected.Institutional processingResearch storageSource files + outputsSelected inputsReturned outputsInstitutional computeApproved processing workers
Select Hybrid processing to reveal the agreed file-transfer path. Your selection stays in place as you scroll.

04 / Coordination

Connect the people to the work.

Researchers can use browser workspaces, mobile review, and approved integrations from outside the lab. Hosted services provide access to run status, selected outputs, and review records while processing can stay on institutional compute.

Remote participation, with an agreed access scope.

Explore the operating details
Client experiences
Browser access to runs, outputs and review; mobile ROI and activity review; approved connected tools.
Access scope
Define which users, outputs and review materials are available through each experience. Remote clients do not gain direct access to lab storage.
Hosted services
Agree service placement, connectivity and metadata scope with institutional IT.
Processing location
Hosted client access can accompany institutional processing or the selected hybrid arrangement.
Connected experiences beyond the lab. Local processing remains selected.Researchers beyond the labBrowser workspaceMobile reviewConnected toolsApproved accessUnifiedFlow coordinationHosted services · placement agreedCoordinate workConnect the recordSupport reviewInstitutional computeHosted access can support local or hybrid processing.
Clients use approved hosted services. Research files follow their agreed storage and transfer paths; client access does not expose lab storage directly.

05 / Shared operation

Give the work clear owners.

The lab defines the science. Institutional IT supports the approved infrastructure. UnifiedFlow configures the workflow and provides support within the agreed scope.

Know who to involve when work is blocked.

Explore the operating details
Lab
Experimental design, representative inputs, and acceptance for the intended use.
Institutional IT
Infrastructure, research storage, backup and approved access.
UnifiedFlow
Platform configuration, workflow implementation and agreed technical support.
A shared operating arrangement. Local processing remains selected.Operate with clear responsibilitiesLabFiles + metadataInstitutional ITInfrastructure, storage + backupUnifiedFlowWorkflow + agreed support
Ownership stays attached to the work, the infrastructure and the services that support it.

Service locations, access, data availability and responsibilities are agreed for each workflow.

From an environment to routine use

From an environment to routine use

A workflow checked.
An operation supported.

Bring the lab, institutional IT and UnifiedFlow together around the work that needs to run.

  1. 01

    Map the work

    Identify recording sources, data volumes, available compute and storage. Establish the capacity the selected workflow needs.

  2. 02

    Agree the arrangement

    Define processing locations, transfers, connectivity and access. Assign retention, backup and recovery responsibilities for files and platform records.

  3. 03

    Exercise the workflow

    Process representative inputs. Inspect outputs, resource use and interruption handling with the people who will operate it. Scientific acceptance remains with the lab.

  4. 04

    Keep it operating

    Establish support and escalation routes, coordinate maintenance and check affected workflows when the environment changes. Review capacity as the work grows.

Prepare for institutional IT review How we work together

A conversation, grounded in your work

Let’s map the environment around your science.

Bring your lab and institutional IT into a conversation about the workflow, infrastructure and operating scope.

Request technical review materials