> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/mpd/fed-batch/time-the-induction-on-cell-state.md).

# Time the induction on cell state

Explore induction points on the cell count and cell size, and link each to the product per cell it gives.

In an induced process, the induction point is one of the biggest choices. Induce too early, and there are too few cells to make product. Induce too late, and the cells may be in a poorer state to make it. Once a process moves into production, it usually runs on the clock. Finding the right time is development work, and that is where BactoBox® helps.

## Same OD, different cultures

In shake flasks, induction is often set at a fixed optical density (OD), such as OD<sub>600</sub> 0.6. In a bioreactor, it is more often set by the clock, by OD or by the end of the batch phase. The number of cells behind one OD unit, and their size, depend on the medium and on the state of the cells. Two cultures induced at the same OD can therefore hold different numbers of cells, of a different size, and give a different titer.

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2FnDBtKLOxkzsD5P4P8Viu%2Ff1-od06-v4.svg?alt=media" alt="Two bar charts for E. coli in four media in shake flasks at OD600 0.6. Cells/mL: chemically defined (CD) medium 3.5 × 10^8, LB 3.4 × 10^8, Terrific broth 2.1 × 10^8, TSB 0.7 × 10^8. CIZE: 1.38, 1.47, 1.67 and 1.90 µm."><figcaption><p><em>E. coli</em> in four media, shake flasks, followed through their growth curves in the study behind <a href="https://help.sbtinstruments.com/mpd/workflows/best-medium.md">Screen growth media</a>. These cultures were not induced. The values are interpolated between the samples on either side of OD<sub>600</sub> 0.6.</p></figcaption></figure>

## What BactoBox® shows

The count gives the number of cells at induction. CIZE gives their state. Testing induction points on both shows how much the number of cells and their state affect titer. That knowledge gives a better understanding of the process, and a firmer basis to optimize it. It also lets induction points be compared across runs and scales.

## When cell state matters more than OD

OD and the count move together only while the growth rate is constant and the cells keep the same size. There, inducing at a fixed OD means inducing at about the same count.

Cell state matters when the cells change. That happens when the medium, the feed, the clone or the scale changes. It can also happen within one run, at the end of the batch phase.

## Check the end of the batch phase

Many fed-batch processes induce at the dissolved oxygen (DO) spike, the sharp rise in dissolved oxygen when the batch substrate runs out. Cell division can stop before that. In our shake flasks, *E. coli* stopped dividing hours before optical density stopped rising, while the cells kept taking up carbon. See [Find when growth stops](https://help.sbtinstruments.com/mpd/batch/find-when-growth-stops.md). If a batch phase behaves the same way, cells induced at the DO spike may not have divided for some time. A few counts across the end of the batch show whether the cells still divide at induction.

## Step by step

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2F9e9GoXIyNP3GR4sIQK4e%2Ff1-steps-v3.svg?alt=media" alt="Four steps. 1, map cells/mL and CIZE through a reference run. 2, read cells/mL and CIZE at the current induction point. 3, test other induction points, marked A, B and C. 4, plot product per cell for each induction point, and find the best."><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Map a reference run

Follow the count and CIZE through the batch phase and the feed, and on past induction. Sample every hour or every two hours, and more often around the induction point. See [Track a growth curve](https://help.sbtinstruments.com/mpd/track-growth-curve.md).
{% endstep %}

{% step %}

### Read the state at induction

Note the count and CIZE at the current induction point. That is the starting reference.
{% endstep %}

{% step %}

### Test other induction points

In further runs, induce at other cell states. Try a higher or a lower count, or other points on the CIZE curve. Measure product as usual.

One place to start is the point where CIZE is stable, or just before it starts to change.
{% endstep %}

{% step %}

### Link the state to product per cell

For each run, divide the titer at harvest by the cell count at harvest to get the product per cell. Compare it across the induction points. The best one shows which count and CIZE to induce at.
{% endstep %}
{% endstepper %}

## The result

An induction point defined by the cells, and the product per cell it gives. Production can keep running on the clock, at the time that reaches this cell state, checked with a count when the medium, clone or scale changes. See [Compare cell state across scales](https://help.sbtinstruments.com/mpd/fed-batch/compare-cell-state-across-scales.md).

If two runs reach induction with different cells, look upstream first. The inoculum is a common cause. See [Design the seed train](https://help.sbtinstruments.com/mpd/seed-train/design-the-seed-train.md).

{% hint style="info" %}
The process owner runs the experiments and makes the decisions. We help read what happens in the culture. [Contact us](https://sbtinstruments.com/contact) to plan a study.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/mpd/fed-batch/time-the-induction-on-cell-state.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
