The signals sit in different teams
Site operations, clinical operations and clinical supply each hold part of the picture. The handover between them is where planning problems are usually discovered too late to act on cheaply.
Four independent experiences, one connected clinical-supply decision journey
Clinical-supply decisions are rarely undone by a single bad number. They are undone by a signal that never travelled — a site quietly under-recruiting, an enrollment curve bending away from plan, and a depot that finds out too late to matter.
This family follows that chain deliberately. Four independent synthetic-data experiences each own one specialist decision domain, and together they show how site execution becomes an enrollment outlook, how an enrollment outlook becomes clinical-supply requirement, and how that requirement resolves into a resupply response a person still has to approve.
Why This Family Exists
Site execution shapes enrollment. Enrollment shapes patient demand. Patient demand becomes kit demand, which then has to be reconciled against depot and site inventory, expiry exposure, shortage risk, shipment conditions and resupply timing. Each link is a specialist decision — and each one inherits the quality of the link before it.
Site operations, clinical operations and clinical supply each hold part of the picture. The handover between them is where planning problems are usually discovered too late to act on cheaply.
Nobody measures kit demand directly. It is inferred from how many patients are expected, which is inferred from how sites are actually recruiting — so an error early in the chain arrives late and amplified.
Collapsing site performance, enrollment forecasting and supply planning into one view loses the depth each decision needs. The answer is connected experiences, not a merged one.
Every path in this family ends at a qualified reviewer. Nothing here approves, releases or executes a clinical-supply action.
How to read this family
The four experiences are independent — none contains another, none is a parent of another, and each can evolve on its own. They are also connected: the business signals genuinely flow across them in one direction, from process foundation through site execution and enrollment outlook into clinical supply planning. Independent experiences, one connected decision journey. Everything shown across the family is built on synthetic data.
Decision Framework
One sequence across the whole family, with the owning experience named at every stage. This is the contract that keeps the four experiences from telling the same story twice.
The Four Experiences
Each card states the decision domain that experience owns — and, where the boundary matters, what it deliberately leaves to a sibling.
The process and object context the rest of the family assumes.
An architecture and positioning page rather than a prototype application — no runtime, no dataset, no screenshots. It describes the clinical-supply process backbone across study and supply setup, planning, manufacturing and packaging, distribution and traceability, plus the SAP-aligned object and action vocabulary the three experiences borrow rather than invent.
Boundary
Not an application. Site analytics, enrollment forecasting and supply planning all belong to the three active experiences.
How sites are executing now.
Site ranking and selection support, site profiles, observed recruitment performance, and site-level operational-risk indication across dropout, protocol deviation and data quality — with country and region comparison, operational scenarios and reason-carrying recommendations on synthetic data.
Boundary
Forward enrollment forecasting belongs to the next experience. Risk here is site-level operational indication, never patient-level prediction.
Where enrollment is heading, and how much to trust it.
Forward enrollment trajectory with the forecast method kept on screen — a naive baseline, an ML model, and one-step-ahead rolling-origin evaluation deciding which one becomes operational. On this synthetic dataset the baseline won, and the page says so rather than promoting the model.
Boundary
Site operations depth belongs to Site Performance Intelligence. Error figures are synthetic-data evaluation only, not validated accuracy.
How forecasted patient demand becomes a supply response.
Enrollment-to-kit-demand translation, depot, country and site inventory position, stockout and expiry exposure, shipment and cold-chain risk, exception prioritization, scenario review and SAP-oriented action proposals — all on synthetic data, all ending at a planner.
Boundary
Enrollment is a consumed input here, not a forecasting capability this experience owns. Resupply is threshold and rule-based candidate logic, not mathematical optimization.
Connective Tissue
The handovers, stated plainly. Each experience keeps its own depth; what travels between them is a signal, not a duplicated capability.
The foundation supplies the shared process and object language. The three prototypes reference it rather than redefining it.
Observed site execution is the evidence the forward trajectory is built on. One measures what happened; the other projects what follows.
The enrollment outlook is the input that becomes kit demand. Supply planning consumes the forecast; it does not produce a competing one.
Each experience ends at a proposal with its evidence attached, and a qualified reviewer decides what happens next.
These handovers are a portfolio decision flow, not a technical integration. The prototypes are separate applications on separate synthetic datasets; no signal moves between them at runtime.
Family Scope & Governance
This is a clinical-operations and clinical-supply planning family. It supports operational decisions about sites, enrollment outlook and supply position. It does not touch clinical, medical or regulatory decision-making, and these boundaries apply to every experience within it.
Possible Future Direction
Concepts under consideration for the family. These are directions of interest, not completed work and not part of the current family.
This family sits alongside the flagship experiences and the Applied Supply Chain Intelligence prototypes in the Applied AI Supply Chain Lab.