Centralized Lab Analytics for the ELN Suite.
LabVista is the reporting and analytics layer built into ELabELN Suite. Dashboards, scheduled reports, and live metrics drawn from the notebook, the data layer, the instruments, and the business systems the lab already runs. The questions the lab asks itself, answered in seconds instead of afternoons.
Included with ELabELN Suite
Unlimited users
- Pre-built lab templates included
The questions a lab cannot answer about itself.
Most research labs cannot answer simple operational questions about their own work without significant manual effort. How many experiments did each member of the lab run last quarter. Which protocols are producing reproducible results and which are not. How much of which reagent is being burned through and by which project. How is the grant progressing against the data deliverables we promised. The data exists. It is in the notebook, the file layer, the instrument PCs, the freezer inventory, the chargeback sheet, the HR system. Pulling it together to answer a single question is an afternoon, sometimes a week.
Generic business intelligence tools do not solve this. Tableau, Power BI, Looker, and the open-source equivalents are powerful platforms, but they are built for sales pipelines, web analytics, and finance teams. They do not know what an experiment is, what a sample is, what a protocol version is, or that the data behind a published figure should be auditable years later. Building a research-lab dashboard in a generic BI tool requires a data-engineering project before the first chart appears, and once the dashboard exists, every schema change in the lab's underlying tools breaks it. LabVista is the analytics layer of ELabELN Suite. It already speaks lab.
Lab analytics, built for how research actually runs.
Five capabilities define what makes LabVista different from a general-purpose BI tool. The first four are the day-to-day mechanics. The fifth is what those mechanics add up to.
01 Cross-system dashboards
One view across every system.
LabVista pulls metrics from ELabELN notebook entries, LabDrive files and datasets, LabVia instrument runs, and the connected business systems the lab already uses (inventory, HR, finance, chargeback). The dashboards combine them so a PI can see the lab's actual state without opening four tools. The same metric, asked from any angle, is the same number everywhere it appears.
02 Pre-built lab templates
Reports the lab already needs.
Out-of-the-box dashboards for the questions research labs ask most: experiment throughput by researcher, instrument usage by month, reagent consumption trend, protocol success rate, grant deliverable progress, core-facility usage and chargeback, sample turnaround time. Each template is filtered by project, PI, date range, or any metadata field that exists in the underlying data. New labs start with the templates that fit their work and grow into the rest.
03 Self-serve report builder
Custom views without a data team.
A drag-and-drop builder for new dashboards and reports. Anyone with the right permission can assemble a view from the same data sources, without writing SQL and without filing a ticket. PIs build the views they want to see. Lab managers build the views they need for operations. Trainees build the views that help them work. The builder uses the same lab vocabulary the notebook and data layer already use, so a "sample" is a sample everywhere.
04 Scheduled reports and alerts
The report lands before you ask.
Reports are scheduled and delivered automatically by email, by Slack, or to the dashboard. Alerts trigger when a threshold is crossed: reagent below par level, instrument downtime above the rolling average, experiment failure rate spiking on a specific protocol, grant deliverable behind schedule. The lab knows about the problem before someone has to go looking, and the weekly PI summary arrives without anyone compiling it.
05The compounding outcome
Decisions backed by what the lab is actually doing.
When the data behind every decision is the data the lab already produces, decisions stop being gut-feel exercises. Capacity planning, grant scope, hiring, instrument purchases, and publication strategy all become anchored in what the lab is actually generating, not what someone remembers from the last lab meeting. LabVista holds the data in that form from the day it is plugged in, which means the analytics work is the work the lab is already doing, not a separate quarterly project.
How LabVista fits inside the ELN Suite.
ELabELN
The notebook layer. Captures the experimental record.
LabDrive
The files, datasets, and documents the notebook references, with metadata and versioning.
LabVia
Direct connectivity to instruments over serial, USB, and network. AI anomaly detection.
LabVista
Dashboards and reports across the ELN, LIMS, and connected business systems.
Together, they replace the patchwork of spreadsheet exports, ad-hoc pulls, and weekly slide decks that most research labs are running today.
What lab-native analytics does that Tableau cannot.
Generic business intelligence tools are excellent at being generic. For research data, generic is the problem. The capabilities below are not faster or cheaper versions of a BI dashboard. They are different categories of work.
| Capability | Spreadsheets and one-off pulls | Generic BI tools (Tableau, Power BI, Looker) | LabVista |
|---|---|---|---|
| Data freshness | As of the last manual export. Stale within hours. | Refreshed on schedule, but the schemas were modeled once and drift as the lab changes. | Live from the systems the lab uses, with the lab's vocabulary already mapped. |
| Lab-native vocabulary | Whatever the researcher named the columns in the file. | Generic columns ("user_id_3," "event_type_7") unless a data engineer rebuilds the model. | Experiment, sample, protocol, instrument, researcher, project, already understood. |
| Cross-system view | Each pull is from one tool at a time, then stitched in a spreadsheet. | Possible after a data-engineering project. Breaks when any source schema changes. | Built in across ELabELN, LabDrive, LabVia, and connected business systems. |
| Time from question to answer | Hours to days. | Minutes after the dashboard is built. Days to weeks before. | Seconds on the pre-built templates, minutes in the self-serve builder. |
| Reports the lab actually wants | Built by whoever asks loudest. | Built by whoever has BI access. | Pre-built for the common research-lab questions, configurable for the rest. |
| Permission model | Whoever has the file. | User and group access on dashboards. | Role-based access by project, PI, lab, or core facility. |
| Grant and audit reporting | Someone compiles the figures in the last week before submission. | Possible, but separate from the data of record. | Generated from the data of record on demand. |
| Maintenance burden | Recreate the pull every time the underlying data changes. | Maintain the data pipeline, the model, and the dashboards as three separate projects. | Maintained as part of the Suite, no separate data engineering. |
| User accounting | Limited by who has spreadsheet access. | Per-seat BI license fees that scale with the lab. | Unlimited users on every Suite plan. No per-seat fees. |
When the lab grows past walking around to ask.
Small labs run on the PI walking around and asking. That works at three people. It works less well at six. It does not work at fifteen, and it has not worked for a long time at a core facility serving thirty PIs. The breaking points are predictable, and most labs hit several before they act on them.
LabVista is the analytics layer for labs at that point. It does not replace the conversations. It makes sure the conversations are about the right things, with the data already on the table when they start.
The PI cannot get a current picture of the lab without scheduling a meeting.
"How much did we run last quarter" turns into someone's afternoon.
Grant reports are compiled by hand in the last two weeks before submission.
Core facility chargebacks take a quarter of someone's job.
Failed experiments get noticed one at a time, never in aggregate.
See LabVista inside ELabELN Suite.
Questions, answered.
If a question isn't here, the demo answers it. The questions are ordered roughly by how often they come up before a decision.