Workflow Orchestration
Your SOPs are modeled as BPMN workflows that Labbit executes directly, so every step runs the way it was approved and every result stays linked to the step that produced it.
Platform
/
Workflow Orchestration
Workflow Orchestration
Your SOPs are modeled as BPMN workflows that Labbit executes directly, so every step runs the way it was approved and every result stays linked to the step that produced it.
THE PROBLEM
An SOP in a binder doesn't enforce itself
In many labs, the system records results and leaves the procedure to the analyst. The SOP lives in a binder, the process diagram lives in a slide deck, and what actually happens at the bench depends on who is on shift.
Where a workflow engine does exist, it is often optional, and the diagram a lab draws gets rebuilt by a developer into something that looks and behaves differently. The documented process and the executed process drift apart, and an auditor is usually the one who finds the gap.
CAPABILITIES
Model each step and decision point of your SOP in BPMN, and Labbit runs it as drawn. No translation layer, no drift between the document and the system.
Decision gateways determine the path each sample takes. Samples move according to the logic you defined and approved, not an analyst's memory of it, and nested workflows handle repeatable sub-processes.
Each task runs in a workbook configured for that step: which entities it takes in, which fields analysts complete, and what it creates. When the step is committed, the work is recorded against the samples, materials, and instruments involved.
Live View shows running workflows and the queue waiting at each task, so supervisors can see what's in progress and what needs to happen next without opening individual workbooks.
HOW IT WORKS
01
Map the SOP in BPMN using Designer: user tasks, decision gateways, and nested workflows for sub-processes, in the lab's own terminology.
02
The deployed workflow runs in Lab Ops. Analysts complete each task in its workbook, required signatures are captured at the step, and committed work is linked to the step that produced it.
03
Live View shows progress across the lab. When the process needs to change, the update ships as a versioned changeset through change control.
IN PRACTICE
DIAGNOSTIC TESTING
Sequencing workflows from library prep to sign-out
ANALYTICAL QC
Protocol through pull point to trend
GMP BIOMANUFACTURING
Vein-to-vein COI and batch execution
GMP BIOMANUFACTURING
Review by exception, not by binder
What is BPMN and why does Labbit use it?
BPMN (Business Process Model and Notation) is the industry-standard notation for mapping processes as diagrams. Labbit uses it as the execution layer, so the diagram your team approves is the workflow that runs, not a picture of it that a developer translates into code.
How does Labbit enforce SOPs?
Each SOP step is a task with a configured workbook, and decision gateways route samples along the approved path. Where a step needs sign-off, e-signatures can be required at that task, and every committed action is recorded against the work it belongs to.
Can Labbit handle complex workflows like NGS?
Yes. Workflows branch through decision gateways and call nested workflows for sub-processes, which is how Labbit models multi-step NGS pipelines and manufacturing processes. Helix runs high-volume genomic workflows on Labbit at up to 100,000 samples a day.
Can we change a workflow after go-live?
Yes. Changes are made in Designer as a draft, reviewed against the deployed version, tested in a non-production environment, and promoted to production as a versioned changeset.
Who builds and maintains the workflows?
Labbit implementation consultants configure workflows during rollout, and your trained system administrators maintain and extend them afterward. Workflows are built in Designer, a visual BPMN editor that requires no custom code. Teams that prefer to work directly in configuration files can do that too.
SEE IT RUN
Watch your SOP run as a workflow
Bring a procedure your lab runs today. We'll show you how it looks modeled in BPMN and executed step by step.