Process Foundation · Not an Application
The process, object and action foundation the rest of the family assumes
Independent portfolio architecture inspired by publicly documented SAP clinical-supply concepts; not an SAP product or SAP-endorsed solution.
The three intelligence prototypes in this family all reason about the same things — studies, kits, depots, shipments, shelf life, sites. None of them defines those things. This page does: the clinical-supply lifecycle they sit on top of, and the SAP-aligned object and action vocabulary they borrow rather than invent.
It is an architecture and positioning view, not a prototype. There is no application, no runtime and no dataset behind this page — which is exactly why it can describe the shared foundation without competing with the experiences built on it.
Layer 3
Decision Intelligence
Forecasting, risk prioritization and explainable recommendations for human review.
Layer 2
Governed Data
Consistent study, demand, kit, inventory, shelf-life and shipment information.
Layer 1
Operational Foundation
Standard clinical-supply processes across study, planning, manufacturing and distribution.
Intelligence sits above the foundation. It interprets governed data; it does not replace the systems that produce it.
Why the foundation matters
Clinical-trial supply combines study design, enrollment uncertainty, country requirements, kit configuration, manufacturing, packaging, distribution, shelf life and site operations. Analytics cannot compensate for inconsistent study structures, incomplete master data, disconnected enrollment actuals or weak kit traceability. A governed foundation creates the reliable context that forecasting, risk detection and scenario analysis depend on.
Common operating pattern
Target operating pattern
A foundation improves the conditions for good decisions. It does not by itself resolve every constraint.
Role in the Family
This page establishes the process and object foundation. The family gateway shows how the three active intelligence prototypes use different parts of that foundation — the decision journey and the routing live there, not here.
This foundation owns
This foundation does not own
For the end-to-end family decision chain and which experience owns each stage, see the Clinical Trial Supply Chain Intelligence gateway.
Four foundation pillars
Each area produces data the intelligence layer depends on.
Pillar 01
Establish the governed study structure that downstream processes depend on.
Defines what is studied, where supplies are needed and how treatments are administered.
Pillar 02
Translate study design and enrollment assumptions into time-phased demand.
Creates an auditable baseline linking enrollment change to supply need.
Pillar 03
Coordinate production, packaging, labeling and identification of finished goods.
Connects planned demand to manufacturable, traceable, country-appropriate supplies.
Pillar 04
Move supplies from production through depots to sites with visibility and control.
Produces the events needed to detect continuity and expiry risk.
Connected clinical-supply ecosystem
Clinical-supply operations rarely sit in one system. The foundation earns its value through how consistently these sources are integrated and governed.
Operational foundation
Supporting platform context
Connected systems exchanging data with the foundation
CTMS
Study, protocol, country and site information
IRT / RTSM
Enrollment actuals, subject status, visits and dispensing
RIMS
Country regulatory and shelf-life information
3PL / EWM
Depot inventory, handling units, shipments and returns
Clinical Sites
Site inventory, dispensing, visit demand and returns
Decision-intelligence layer
Analytics, forecasting, scenario comparison and explainable recommendations built on governed foundation data.
From operations to decision intelligence
Layer 1 · Operational foundation
Governed operational signals interpreted business risk prioritized decisions
Layer 2 · Decision-intelligence accelerators
SAP-Aligned Object Model
These are the objects a clinical-supply conversation actually turns on. Naming them consistently is what lets three separate prototypes talk about the same study, the same kit and the same depot without inventing three vocabularies. The naming is SAP-aligned in style; it is not a copy of any SAP data model.
SAP-Aligned Action Vocabulary
An analytical output only becomes reviewable when it is phrased as something a person could actually authorize. These are the action concepts the prototypes borrow so their proposals read as enterprise work rather than as scores. Naming an action is not performing it — nothing in this family executes any of them.
Built on This Foundation
A short orientation only. The full decision journey, the ownership map and the routing between these experiences live on the family gateway.
Foundation context it leans on
Foundation context it leans on
Foundation context it leans on
Each experience is an independent synthetic-data prototype. None is an SAP application, none extends SAP software, and none connects to a live system. This page describes the foundation they assume — for how their decisions connect into one sequence, see the family gateway.
Honest Status
This is a written architecture and positioning view. Unlike the three sibling experiences, there is no application behind it — and it does not pretend otherwise.
The absence of an application here is deliberate. A foundation page that shipped screenshots would be competing with the experiences it is supposed to support.
Professional capability perspective
This portfolio demonstrates an approach for connecting standard clinical-supply processes with analytics, scenario modeling and human-reviewed decision support. The focus is understanding the operational foundation, identifying the decisions that stay difficult for business users, and designing explainable intelligence that complements governed processes rather than bypassing them.
Independent portfolio concept. This prototype uses synthetic data and independently developed process and architecture representations informed by publicly available enterprise and clinical-supply practices, including SAP Intelligent Clinical Supply Management documentation. It is not an SAP product and is not affiliated with or endorsed by SAP. SAP, SAP S/4HANA and SAP Joule are trademarks or registered trademarks of SAP SE or its affiliates.
Clinical trial family