Investigating a CHO process transfer across manufacturing sites

Across sites, programs and functions

A product program brings together historical and incoming batch evidence from development, the sending site and the receiving site. Cohorts are separated by clone, medium, process version, scale and equipment. A process investigation can support transfer review; it does not itself demonstrate formal product comparability. Evidence is assembled in an authorized program project from approved exports. Portfolio reuse means reviewed methods across separate projects; no automatic cross-project or cross-company view is assumed.

Continuity as new campaigns arrive

New campaigns use the same reviewed field mappings where their source layouts remain compatible. A changed layout returns for mapping review. The scientific team can see the data cut behind an investigation and distinguish a newly available batch from a change to an earlier source record.

Reconstruct the incident before ranking performance

Initial signal

The receiving site reports lower harvest titer and a higher upstream aggregate result in selected campaigns. The investigation opens with those two endpoints, then checks whether sample stage, method and process version permit a defensible sending/receiving comparison.

What makes it enterprise work

The sending site compares against its most recent campaigns; the receiving site compares against transfer reference batches; analytical reviewers use a different sample-stage convention. A single pooled chart could make all three views appear contradictory.

The decisive comparison

The team retains only cohorts with a defensible comparison basis. It plots titer and upstream aggregate results alongside the recorded temperature-transition timing, keeping original elapsed time and sample stage visible. Unmatched campaigns remain an evidence gap.

The comparison is scoped by business and scientific context. Data volume is not used as a proxy for comparability, relevance or evidence quality.

Check cohort overlap and the temperature-timing hypothesis

Overlap before matching

Check whether sending and receiving sites have overlapping process versions and comparable conditions. If site and version are completely confounded, matching cannot separate their effects. Report the gap and plan a bridging comparison rather than claiming an adjusted site effect.

Event timing without hiding the difference

If temperature-transition timing is the hypothesis, realigning every run to that transition can hide the difference under investigation. Retain the original time axis, show event markers and inspect any phase-relative view alongside it.

A product-specific quality panel

Harvest titer and upstream aggregate results anchor this use case, but they are not a complete product-comparability assessment. Include the relevant glycan, potency, downstream, stability and analytical-method evidence according to the program question.

A defined confirmation question

Check whether the candidate timing association persists in new, comparable evidence with predeclared responses. Historical association is not a causal result. Any scenario model needs a suitable project-data basis and intended-use evaluation before informing that test.

A focused conclusion and a confirmation plan

Interpret the evidence through explicit decision paths, then confirm the hypothesis with the agreed study.

The decision output is a matched-cohort transfer comparison, a list of non-comparable campaigns and a specific timing hypothesis. Reviewers distinguish data-definition issues from process associations and agree the next confirmation study. A source-linked process investigation supports transfer review; formal product comparability remains a separate product-specific assessment.

Make the method repeatable across the enterprise

Program data stewardship

Own source inventory, mapping decisions, unit conventions and reconciliation of changed source records.

Scientific review

Process development and MSAT own the analysis question, cohort logic, interpretation and confirmation plan.

Quality and transfer review

Review the evidence relevant to the intended decision. Approval of a report does not substitute for product-release procedures.

IT and platform ownership

Define identity, access, retention and integration requirements for the specific deployment. Verify these with the implementation team before rollout.

Operating-model requirements are deployment-specific. Validate role/access behavior, reviewer workflows, retention, model governance and source delivery for the intended environment; this scenario does not assert certification or production readiness.

Measure transfer investigation and decision readiness

The enterprise value is a consistent way to investigate process comparability across a manufacturing network while keeping the scientific differences between programs visible.

A credible benefit assessment

Choose a baseline period and comparable investigation or campaign scope. Record how elapsed time, review effort or process response is measured. Separate improvement in data preparation from improvement in scientific interpretation, and separate both from any measured manufacturing result. Include adverse, inconclusive and unchanged outcomes.

What leadership receives

A defined investigation scope; a common evidence basis for the participating teams; a documented conclusion with remaining uncertainty; and a confirmation plan with owners. Portfolio expansion follows demonstrated reuse and the required deployment checks, rather than an assumption that one successful analysis establishes every use case.