Distribution: Cold-Chain Prediction and Demand Forecasting

📍 Where we are: Part V · Fill-Finish & Release, Learned — Chapter 20, the last of the manufacturing spine. The previous chapter, packaging and serialization, gave every vial of BATCH-2026-001 an SGTIN that can be verified anywhere in the chain. Now the product leaves the factory entirely, and the learning problem leaves with it: keep DP-001 cold enough, route it past the risky lanes, and make the right number of doses in the first place — so the molecule that began as a target in Chapter 4 finally reaches a patient with its quality intact.

The whole genealogy — WCB-CHO-001 → SEED-001 → BATCH-2026-001 → CLAR-001 → PApool-001 → DS-001 → DP-001 — has been about building a molecule and proving it is what we say it is. None of that matters if the vial spends six hours on a hot tarmac in July. Distribution is the one stretch of the process the manufacturer does not physically control: the product is in the hands of couriers, customs, wholesalers, and pharmacies, and the only thing travelling with it is a temperature logger and a label claim that says "store at 2 to 8 degC." The learning problem here is unusual for this book because it leaves the bioreactor behind and looks like a logistics problem — and yet it inherits the same discipline every prior chapter built: a deterministic, auditable core that decides, with the learned model scoring risk around it rather than in the path of release.

Two ML-shaped jobs live in the last mile, and they are as different from each other as the two halves of packaging were. The first is per-shipment: given a temperature trace that has already happened (or is happening live), how much of the product's stability budget has been spent, and has the label claim been breached? The second is per-lane and per-period: before a shipment leaves, which routes are likely to breach, and how many doses should we have made and positioned so the right product is in the right place at the right time? The first job is anchored by a fixed piece of chemistry — the Mean Kinetic Temperature — and the second is where forecasting and risk-scoring models earn their keep.

The simple version

Think of shipping ice cream across the country. You do not actually care about the average temperature of the trip — you care that it never got warm enough to melt, and a few minutes warm cost you far more than a few minutes extra-cold ever helped. A Mean Kinetic Temperature is the honest single number that captures that asymmetry: it is the temperature the trip "felt like" to the chemistry inside, weighted so the warm spells count for more. Once you can put a number on how much a trip costs the product, two more questions follow naturally: which delivery routes tend to get warm (so you pack those ones in a better cooler), and how many tubs to make and where to stock them so you are never short and never throwing melted ones away. Cold-chain ML is those three questions, in order.

What this chapter covers

• The stability budget and Mean Kinetic Temperature (MKT): the Arrhenius-weighted equivalent temperature of a thermal history, why it is a fixed equation rather than a model, and how the excursion verdict rides on it.
• Temperature-excursion prediction: forecasting a breach before the logger proves it, from the live trace and the shipment context.
• Lane-risk scoring: a learned classifier that ranks routes, carriers, and seasons by their probability of a future breach, so scarce premium packaging and audits go where they matter.
• Demand forecasting and supply-chain analytics: predicting how many doses to make and position, and why the bullwhip effect makes this its own hard problem.
• The anatomy of one cold-chain shipment record, the GMP and Annex 22 angle that keeps the physics deterministic, and the honest limits of forecasting a chain you do not control.

The stability budget: what a shipment actually spends

Every biologic carries a shelf life earned in a formal stability study — DS-001 and DP-001 were placed on stability at the recommended 2 to 8 degC and at accelerated conditions, and the data fixed an expiry date and a label storage claim under ICH Q1A(R2), the guideline that governs stability testing of new drug substances and products [1]. That shelf life is a budget: it assumes the product stays inside its label claim. Every minute a shipment spends warmer than 8 degC draws down that budget faster than the study assumed, and — this is the subtlety — it draws down faster than the average temperature would suggest, because chemical degradation is exponential in temperature, not linear.

This is why distribution is not just "did it stay cold." A shipment that sat at 5 degC for three days and a shipment that averaged 5 degC but spiked to 15 degC for five hours have the same arithmetic mean and wildly different effects on the product. To account for that honestly you need a temperature metric that weights the warm hours the way the chemistry does — and that metric is the Mean Kinetic Temperature.

Mean Kinetic Temperature: the deterministic physics core

The Mean Kinetic Temperature (MKT) is the single, constant temperature that would cause the same amount of Arrhenius-driven chemical degradation as the actual, fluctuating temperature history of a shipment. It comes straight from the Arrhenius equation — reaction rate scales as exp(-Ea / (R·T)), where Ea is an activation energy, R is the gas constant, and T is absolute temperature in kelvin — and Haynes' formula inverts the time-average of that rate back into an equivalent temperature:

MKT (in kelvin) = -(Ea / R) / ln( mean over i of exp( -Ea / (R · T_i) ) )

with each T_i a temperature reading in kelvin. The convention from ICH Q1A(R2)'s worked stability examples uses an activation energy of Ea = 83.144 kJ/mol, which is why MKT is reproducible across companies rather than a tuning knob [1][2]. The MKT is always at or above the arithmetic mean of the trace, and the gap grows with the size of the warm excursions — exactly the asymmetry the budget needs.

The single most important property of MKT, for this book, is that it is not a machine-learning model. It is a deterministic equation with no fitted parameters: feed it a thermal history and an activation energy and it returns one number, the same number every time, derivable on paper. That makes it the physics core of the cold-chain decision, the cold-chain analogue of the deterministic GS1 rules that carried the critical decisions in the packaging chapter. The release-relevant verdict — is this shipment inside its label claim, and is its accumulated thermal stress within the qualified budget? — rides on this deterministic core, not on a learned classifier. The learned models in this chapter score risk; they never overrule the arithmetic that decides whether a shipment is acceptable.

Evidence

MKT and excursion accounting against a label claim are (production) practice across regulated cold-chain distribution — the metric is defined in the USP general chapter on MKT and underpins ICH Q1A(R2) stability storage statements; the calculation itself is fixed chemistry, peer-reviewed and standardized, not a vendor model [1][2]. What is learned — excursion prediction and lane-risk scoring — sits one layer out and is (pilot) in most of the industry: cold-chain platforms (Controlant, Sensitech, Tive, and the temperature-monitoring vendors) collect the logger data at scale, but predictive lane-risk models layered on top are an applied, mostly vendor-self-reported capability rather than a settled, validated one. Treat the MKT/excursion arithmetic as production-grade and the predictive scoring as advisory.

Temperature-excursion prediction: catching the breach before the logger proves it

The simplest cold-chain ML question is reactive: a shipment arrives, you download the logger, you compute MKT and the time-above-8 degC, and you decide. That is valuable but late — the product is already at the wholesaler. The predictive version is more useful: from the live trace so far, plus the shipment's context (where it is, how many legs remain, the qualified shipper's remaining hold time, the forecast weather along the route), estimate the probability that the shipment will breach its label claim before it does, so the receiving site can intervene — expedite, reroute, or quarantine on arrival.

This is a time-series classification problem with a familiar bioprocess shape, and it shares the small-data, mostly-normal character of the serialization anomaly problem: the vast majority of shipments arrive clean, breaches are rare, and confirmed product-impacting excursions are rarer still. The features that matter are not exotic — the trace's recent slope and variance, the qualified packaging's remaining thermal hold time (a qualified shipper is rated to hold 2 to 8 degC for, say, 96 hours; how much of that budget is left is the single strongest predictor), the number of remaining handoffs, ambient conditions, and the lane's own history. The model is advisory: a high predicted-breach probability triggers a human decision and a closer watch, exactly as the FDA's 2023 Artificial Intelligence in Drug Manufacturing discussion paper and the draft EU GMP Annex 22 expect of ML that touches a quality-relevant outcome [3][4].

Lane-risk scoring: where the learned model actually pays off

The highest-value learned layer in distribution is not per-shipment at all — it is per-lane. A lane is a route-plus-mode-plus-carrier combination (Frankfurt to São Paulo, air freight, carrier X, summer), and across a year a manufacturer ships thousands of times over a few hundred lanes. Some lanes breach far more often than others — long-haul air with multiple customs handoffs in a hot season, short-margin packaging, an unreliable ground leg at the destination. If you can score each lane by its probability of a future breach before you ship, you can do something genuinely cost-effective: send the expensive active-cooled containers and the redundant data-loggers down the risky lanes, and ship the safe lanes in cheaper passive packaging. Scarce mitigation goes where the risk is.

This is a supervised classification problem with real labels — a past shipment either breached its label claim or it did not — so unlike the serialization anomaly case it does not have to be unsupervised. The features describe the lane and the shipment plan: total distance, number of handoffs, season, the lane's historical excursion rate, and the qualified shipper's hold-time margin against the planned transit time. A gradient-boosted tree ensemble is a good fit here for the same reasons it dominates tabular risk-scoring everywhere — it handles mixed feature scales and non-linear interactions (a long distance is only dangerous when the hold margin is also tight) without much tuning, and it yields feature importances a logistics team can read. The output is a probability, ranked, and the model is again advisory: it prioritises which lanes get an upgraded shipper or a data-logger audit, it never decides that a specific shipment is safe to release.

The last mile, learned: a deterministic Mean Kinetic Temperature core (cyan) accounts every shipment trace against the 2-to-8 degC label claim and decides the in-claim verdict, while a learned layer (violet) scores risk around it — predicting a breach before the logger proves it and ranking lanes so scarce premium packaging goes where the risk is — with every learned output advisory and a human deciding. Original diagram by the authors, created with AI assistance.

A runnable model: coldchain.py

The example module examples/platform/ml/coldchain.py builds both layers and keeps them deliberately separated. The deterministic core computes MKT and excursion accounting on a shipment trace; the learned layer trains a gradient-boosted lane-risk classifier. Because the trilogy's simulator does not model logistics — there is no committed shipping or weather dataset — the shipment trace is synthesised and the lane history is synthetic and clearly labelled illustrative; but the running example's identity is kept (the product is mAb-A, the lot is DP-001 from BATCH-2026-001, the label claim is 2 to 8 degC), and the MKT arithmetic itself is exact chemistry, not a model. It runs standalone with no services.

# examples/platform/ml/coldchain.py (excerpt)
import numpy as np
from sklearn.ensemble import GradientBoostingClassifier

R_GAS = 8.314462618e-3          # gas constant, kJ/(mol*K)
EA_DEFAULT = 83.144            # activation energy, kJ/mol (ICH Q1A worked example)
KELVIN = 273.15
LABEL_LOW_C, LABEL_HIGH_C = 2.0, 8.0   # DP-001 label claim: store 2-8 degC


def mean_kinetic_temperature(temps_c: np.ndarray, ea: float = EA_DEFAULT) -> float:
    """Haynes' MKT: the single equivalent temperature (degC) of a thermal history.

    MKT_K = -(Ea/R) / ln( mean_i exp(-Ea/(R*T_i)) ), T_i in kelvin. Always >= the
    arithmetic mean because Arrhenius weighting penalises the warm excursions.
    """
    t_k = np.asarray(temps_c, float) + KELVIN
    weighted = np.mean(np.exp(-ea / (R_GAS * t_k)))
    mkt_k = -(ea / R_GAS) / np.log(weighted)
    return float(mkt_k - KELVIN)


def excursion_summary(temps_c, minutes_per_step=10.0, ea=EA_DEFAULT) -> dict:
    """Account a shipment trace against the 2-8 degC label claim — deterministic."""
    t = np.asarray(temps_c, float)
    step_h = minutes_per_step / 60.0
    warm, cold = t > LABEL_HIGH_C, t < LABEL_LOW_C
    return {"mean_c": round(float(t.mean()), 3), "max_c": round(float(t.max()), 3),
            "mkt_c": round(mean_kinetic_temperature(t, ea), 3),
            "hours_above_8C": round(float(warm.sum() * step_h), 2),
            "excursion": bool(warm.any() or cold.any())}


def train_lane_risk(seed: int = 2026) -> dict:
    """Gradient-boosted breach-probability model over a synthetic lane history."""
    X, y = synth_lane_history()                       # ILLUSTRATIVE: no logistics data ships
    Xtr, Xte, ytr, yte = train_test_split(X, y, test_size=0.3,
                                          random_state=seed, stratify=y)
    clf = GradientBoostingClassifier(n_estimators=200, max_depth=3,
                                     learning_rate=0.05, random_state=seed).fit(Xtr, ytr)
    auc = roc_auc_score(yte, clf.predict_proba(Xte)[:, 1])
    return {"clf": clf, "auc": round(float(auc), 3)}

Running python platform/ml/coldchain.py prints the following. The MKT and excursion arithmetic on the trace is exact (deterministic given the synthesised trace); the lane-risk ROC-AUC and the two scored lanes are deterministic given the seed but rest on a synthetic, illustrative lane history, not real shipment outcomes:

cold-chain stability budget for DP-001 (label claim 2-8 degC):
  trace: 432 points over 72 h  mean=5.466 degC  max=14.999 degC  min=3.703 degC
  arithmetic mean 5.466 degC  <  MKT 5.734 degC (Arrhenius weights the warm hours harder)
  time above 8 degC = 4.17 h ; below 2 degC = 0.0 h ; excursion flagged = True

lane-risk classifier (ILLUSTRATIVE synthetic lane history):
  GradientBoosting on 840 train / 360 test lanes (base breach rate 0.347)  ->  held-out ROC-AUC = 0.807
  feature importances: {'distance_km': 0.274, 'n_handoffs': 0.134, 'summer': 0.058, 'hist_excursion_rate': 0.191, 'shipper_hold_margin_h': 0.343}
  scored lane A (600 km, 2 legs, winter, spare shipper): breach prob = 0.020  -> ship as-is
  scored lane B (8200 km, 6 legs, summer, tight shipper): breach prob = 0.971  -> upgrade shipper / add logger

Read this output the way a cold-chain quality lead would. The deterministic core does the load-bearing work: the trace averaged 5.466 degC and would have passed a naive average-temperature check, but it spiked to nearly 15 degC and spent 4.17 hours above 8 degC, so the excursion is flagged and the MKT of 5.734 degC sits above the arithmetic mean — the Arrhenius weighting making the warm hours cost more, exactly as the chemistry demands. That gap is the whole reason MKT exists, and it is computed, not learned. Only then does the advisory layer run: the lane-risk model recovers a real signal from the synthetic history (ROC-AUC = 0.807), and its feature importances put the qualified shipper's hold-time margin (0.343) and distance (0.274) at the top — the two physically obvious drivers. The two scored lanes show the payoff: a short winter lane with spare packaging scores a 0.020 breach probability and ships as-is, while a long-haul summer lane with six handoffs and a tight shipper scores 0.971 and gets an upgraded container and a logger. Rules-and-physics decide; the model prioritises where to spend mitigation.

Demand forecasting: making the right number of doses

Cold-chain risk is the downstream half of distribution. The upstream half — and the one with the largest financial stake — is demand forecasting: predicting how many doses of mAb-A to make and where to position them, far enough ahead that the long biomanufacturing lead time (a batch is months from seed to release) can actually meet the demand. Forecast too low and patients go without; forecast too high and product expires unused, which for a 2-to-8 degC biologic with a finite shelf life is pure write-off.

The forecasting problem has a particular structure that shapes the model choice. Pharmaceutical demand is a mix of a slow trend (a drug's adoption curve), seasonality (some therapies are seasonal; manufacturing and ordering have their own calendar rhythms), and sharp, hard-to-predict shocks (a competitor withdrawal, a guideline change, a pandemic). Classical statistical forecasters — exponential smoothing, ARIMA, and their seasonal variants — remain strong baselines and are often hard to beat for a single, stable product line. Machine-learning forecasters earn their place when there are many related series to learn across (every product, every region, every distribution centre), where gradient-boosted regressors on lag-and-calendar features and, increasingly, global deep sequence models can borrow strength across series that a per-series ARIMA cannot.

The hard part is not the algorithm; it is the bullwhip effect. Small fluctuations in patient-level demand amplify into large swings in factory orders as each tier of the supply chain (pharmacy, wholesaler, distributor) adds its own safety stock and reordering logic. A forecast that fits the factory order history is fitting the bullwhip, not the underlying demand, and it will overreact. The supply-chain analytics that work pull the forecast back toward true consumption signals — point-of-dispense data, prescription trends — and treat the order stream as a distorted observation of demand rather than demand itself. This is where ML supply-chain platforms concentrate their effort, and where the honest evidence is thinnest.

Evidence

Named demand-forecasting and supply-chain ML deployments are real but their headline numbers are single-company self-reported and must be labelled as such. Sanofi's plai supply-chain platform (built with Aily Labs) is reported at roughly 80% accuracy for predicting low-inventory positions and around 65% for tracing a risk to its root cause — but the 80% figure traces to a June 2023 release and the 65% to a separate undated corporate page, and neither is independently verified (self-reported) [5]. Merck & Co. with Aera Technology and Merck KGaA with Palantir run comparable supply-chain "control tower" programs (vendor/self-reported). A 2024 survey found roughly 65% of pharma supply-chain leaders have limited confidence in AI for disruption prediction — the honest counterweight to the vendor headlines [5]. Treat demand-forecasting ML as a real, value-generating (production) capability and every specific percentage as illustrative/self-reported, never as established fact.

Anatomy of one cold-chain shipment record

A cold-chain shipment, like every artifact in this series, is not a bare "arrived OK" — it is a structured record that ties the lot to its full thermal history, the deterministic stability verdict, the advisory risk scores, and the lineage back to the batch and forward to the dispensing site. Dissect one DP-001 shipment the way a distribution-quality reviewer would.

One cold-chain shipment, fully unpacked: the label claim and ICH Q1A shelf life it must protect, the deterministic stability core (cyan) — full trace, mean, MKT, hours out of band, and the in-claim verdict that is physics not ML — the advisory learned layer (violet) — predicted breach probability and lane-risk score, marked illustrative — the qualified packaging and its remaining hold margin, the chain-of-custody handoffs, the deterministic integrity verdicts, and the lineage tying the shipment to DP-001 and forward to the pharmacy where the patient finally receives the dose. Original diagram by the authors, created with AI assistance.

Read the card top to bottom and the chapter is laid out as fields. The label-claim block states what the shipment must protect — store 2 to 8 degC, the ICH Q1A shelf life and expiry — the budget every later field is measured against. The deterministic stability core (cyan, marked deterministic) is the heart: a reference to the full temperature trace, the arithmetic mean, the max, the MKT, the hours_above_8C and hours_below_2C, and the in-claim-or-out verdict — each marked physics, not ML, because this is the critical-decision logic a regulator reads. The learned layer (violet, marked advisory and illustrative) holds the predicted breach probability for this shipment and the lane-risk score for its lane with the top feature contributions — useful, but never the decider. The qualified-packaging block records the shipper type, its rated hold time, and the remaining hold-time margin against planned transit — the single field the lane-risk model leans on most. The chain-of-custody block lists the handoffs with timestamps. The integrity block holds the deterministic verdicts (within label claim, within qualified hold time, logger continuous), each deterministic. The violet relationships panel records lineage: this shipment derivedFrom DP-001, is reported-to the temperature-monitoring platform, and is verified-at the dispensing pharmacy — the final node in the running example's genealogy, where the molecule that began as a target reaches a patient.

The unsolved part: forecasting a chain you do not control

Be honest about why the last mile resists machine learning more than any other step in this book. The first difficulty is observability. Once DP-001 leaves the loading dock it is in systems the manufacturer does not own — couriers, customs, third-party logistics, wholesalers — each with its own data, much of it arriving late, incomplete, or not at all. A model can only learn from the excursions it sees, and the most dangerous ones (a logger that failed silently, a leg with no data) are precisely the ones it cannot. Unlike a bioreactor, where every second is captured in the historian, the cold chain is a partial-observation problem, and a model trained on the visible excursions systematically under-counts the invisible ones.

The second difficulty is rare, consequential, and partly non-stationary. Real product-impacting excursions are rare, so the labelled positive class is tiny — the same small-data ceiling that constrains the rest of bioprocess ML, made worse here because the events that matter most are the rarest. And the chain is non-stationary in ways no historical model anticipates: a new carrier, a rerouted lane, a heatwave outside the training distribution, a pandemic that breaks every demand pattern at once. A lane-risk model is a snapshot of a chain that is always changing, and its decay can be both fast and silent — the MLOps discipline of monitoring and retraining under change control is not optional here, it is the only thing standing between a confident model and a stale one.

The third difficulty is the demand-forecasting accountability gap. A forecast is a decision under uncertainty whose consequences — a stockout that denies a patient a dose, or a write-off of expired product — land months later and far from the model. The bullwhip effect means the very data the model is trained on (order history) is a distorted shadow of the demand it is trying to predict, and the cleanest signal (point-of-dispense consumption) is the hardest to get. The result is that demand-forecasting ML genuinely adds value at the margin but is structurally incapable of the accuracy its vendors' headline numbers imply — which is why this chapter labels every one of those numbers illustrative and self-reported, and why the honest framing is decision support under deep uncertainty, not prediction.

What this chapter adds to the model suite

This chapter contributes examples/platform/ml/coldchain.py to the Book 5 example suite: a standalone module with two deliberately separated layers. The deterministic stability core computes the Mean Kinetic Temperature (with the ICH Q1A Ea = 83.144 kJ/mol convention) and accounts a shipment trace against the 2-to-8 degC label claim — the MKT arithmetic is exact chemistry, asserted to exceed the arithmetic mean and to flag the synthesised warm excursion. The learned advisory layer trains a gradient-boosted lane-risk classifier on a synthetic lane history and scores the breach probability of a future shipment, asserted to be predictive (ROC-AUC > 0.75) and to rank a hot, long, multi-leg lane riskier than a short, cool one. The module makes the chapter's central architectural point executable: the physics core decides, the learned layer advises. It coordinates with — and does not duplicate — the drift module (drift.py), which supplies the monitoring discipline a deployed lane-risk model would need, and the serialization anomaly module (serialization_anomaly.py), which handles the integrity of the supply-chain event stream while this module handles its thermal and demand risk. The shipment trace and lane history are clearly labelled synthetic/illustrative because no logistics dataset ships with the trilogy; the running example's identity (DP-001, BATCH-2026-001, the 2-to-8 degC claim) and the MKT chemistry are real.

Why it matters

Distribution is where the entire investment of the manufacturing spine is either preserved or thrown away in the open air. A biologic that passed every release test in QC is worthless if it spends an afternoon above its label claim, and the difference between a shipment that is fine and one that is ruined is often invisible to the naked eye and to the arithmetic mean — which is exactly why the Mean Kinetic Temperature, a piece of fixed chemistry rather than a clever model, is the load-bearing tool here. The learned layers add genuine value at the margins: lane-risk scoring sends scarce premium packaging where breaches actually happen, excursion prediction buys time to intervene, and demand forecasting keeps doses flowing without write-offs. But the discipline this chapter insists on — the deterministic MKT/excursion core decides the release-relevant verdict, the learned models only score risk around it — is the same architecture the regulators are converging on, and it is what lets a manufacturer deploy ML in the one stretch of the process it does not control without putting a probabilistic model in the path of a patient's dose.

In the real world

Cold-chain monitoring itself is fully (production): every regulated biologic shipment carries a temperature logger, and platforms from Controlant, Sensitech, Tive, and others collect that data at scale, with MKT and excursion accounting computed against the label claim as standard, USP-defined practice [1][2]. The predictive layer on top — excursion prediction and lane-risk scoring — is more (pilot) than productized: the data exists and the models are credible, but validated, deployed lane-risk prediction is an applied capability vendors are adding rather than a settled standard, and the published numbers are vendor/self-reported.

Demand forecasting and supply-chain analytics are a real (production) value source with honestly soft evidence. Sanofi's plai (with Aily Labs) is the most-named example — roughly 80% accuracy on low-inventory prediction and around 65% on risk-to-root-cause, both single-company self-reported and traceable to different, partly undated sources [5]; Merck & Co. with Aera Technology and Merck KGaA with Palantir run comparable supply-chain control-tower programs (vendor/self-reported). The honest counterweight is the survey finding that around 65% of pharma supply-chain leaders have limited confidence in AI for disruption prediction [5] — and the broader frame this whole book keeps returning to: the ISPE Pharma 4.0 reality is that production ML clusters in monitoring and human-in-the-loop decision support, not autonomous control. A cold-chain risk score or a demand forecast is squarely advisory under the FDA's 2023 Artificial Intelligence in Drug Manufacturing discussion paper and the draft Annex 22, which keeps the deterministic stability verdict — not a learned model — as the thing that decides whether a dose is fit for a patient [3][4].

Key terms

• Cold chain — the temperature-controlled distribution path that keeps a biologic within its label storage claim (here 2 to 8 degC) from fill-finish to the patient.
• Stability budget — the degradation allowance implied by an ICH Q1A shelf life, which assumes the product stays in its label claim; warm excursions draw it down faster than the average suggests.
• Mean Kinetic Temperature (MKT) — the single constant temperature that would cause the same Arrhenius-weighted chemical degradation as a fluctuating thermal history; a fixed equation, always at or above the arithmetic mean, not a machine-learning model.
• Arrhenius equation — the physical law that reaction rate scales as exp(-Ea/(R·T)), the basis for weighting warm excursions more heavily than the arithmetic mean would.
• Excursion — any period a shipment spends outside its label claim; accounted deterministically as hours above 8 degC or below 2 degC.
• Excursion prediction — forecasting that a shipment will breach its label claim before the logger proves it, from the live trace and shipment context; advisory, not a release decision.
• Lane — a route-plus-mode-plus-carrier combination; the unit at which risk-scoring is most cost-effective.
• Lane-risk scoring — a supervised classifier ranking lanes by future-breach probability so scarce premium packaging and audits go where breaches actually happen.
• Qualified shipper hold time — the validated number of hours a passive or active container holds 2 to 8 degC; the remaining margin against planned transit is the strongest single breach predictor.
• Demand forecasting — predicting how many doses to make and position, far enough ahead to meet the long biomanufacturing lead time without stockouts or expiry write-offs.
• Bullwhip effect — the amplification of small demand fluctuations into large factory-order swings as each supply-chain tier adds safety stock; the reason fitting order history fits distortion, not demand.
• Deterministic-core / advisory-layer split — the cold-chain analogue of the packaging chapter's rules-first design: MKT and excursion accounting decide the release-relevant verdict, learned models only score risk.

Where this leads

The manufacturing spine is complete — DP-001 has reached a patient, its label claim intact, the last node of the genealogy closed. Every chapter from here on steps back from a single unit operation to look at the whole system. The next chapter, Hybrid Models and Digital Twins: The Dominant Paradigm, gathers the thread that has run quietly through the entire book — the union of mechanistic physics and learned components that has been winning at every step, from the bioreactor soft sensor to the chromatography twin to the very MKT-plus-classifier split this chapter just built — and names it as the dominant practical paradigm of ML in biomanufacturing.