A Novasign demo is 30 minutes on your dataset, not a slide deck
Most software demos show the vendor’s data behaving well. This one builds a model on data from a campaign you have already run.
Loading available times…
Pick a time in the calendar, then confirm it from your inbox. There is no qualification step in front of the session.
In a full engagement, Bespark*bio reached the same process decisions with 8 runs instead of 22, 64% fewer experiments. Read the study.
The compliance program, including what it does not yet cover, is published in full on Trust, with nothing behind a form.
How Novasign handles what you submit is described in the privacy notice.
The agenda
What happens in the 30 minutes?
- Part one: a specialist wires a dataset reader, a preprocessor, a reactor and a hybrid model into a workflow, on a dataset from a campaign you have already run.
- Part two: the trained model is simulated forward, and its trajectory is put next to the measurements from the run that was actually done. The axes are qualitative, because the session uses your numbers, not ours.
- Part three: your data sources are mapped onto Studio, and the four places Studio can run are named (on-premise, in your cloud, on an appliance, or air-gapped).
- 1 · Model
Build a hybrid model
A specialist loads a real bioprocess dataset into Studio and trains a model on it.
- 2 · Prediction
Show it against the experiment
The trained model is simulated forward and its trajectory put next to the measured one.
- 3 · Fit
Map Studio onto your setup
Which of your data sources arrive live, which arrive as files, and where Studio would run.
Who joins
Who joins the session?
A modeling specialist runs every demo and answers all three of these in the session itself.
- Modeling
How the model is built
How a hybrid model is authored, and what intensified design of experiments changes.
- Deployment
Where Studio runs
The four deployment options, and what an air-gapped installation involves.
- Compliance
What a reviewer can check
What the compliance program covers, and which Part 11 building blocks Studio ships.
From your side, two people are enough: the engineer who owns the campaign and, if where the software runs matters to you, whoever answers for your IT constraints. Nobody needs to prepare anything beyond the three items below.
Preparation
What should you bring?
One campaign, one question, and the constraint on where the software runs.
- A dataset
One completed campaign
Offline and process data from runs you have run, as CSV, Parquet, Excel or JSON.
- A question
The decision you are stuck on
A media formulation, a scale-up step, a transfer, or an unexplained deviation.
- A constraint
Where the software must live
Whether the platform runs on your infrastructure, in your cloud, on an appliance or air-gapped.
No dataset yet? Novasign brings one of its own. The agenda does not change; only the dataset does.