Delivery
Delivery is a separate operational stream that operates independently from the training process.
Delivery Components
A Program Certificate is required to obtain delivery eligibility. At the same time, fulfillment starts only after license payment and the presence of a commercial entitlement, site binding, and completed technical checkpoints for preparing executable modules and keys.
| Component | Owner | Purpose |
|---|---|---|
| Commercial Entitlement | Entitlement Service | Contract, payment evidence, SKU (license line item), and site binding validation. |
| Delivery Pack | Fulfillment Service | Signed manifest, bundle assembly, and download session. |
| Hardware Key | Key Operations Service (KeyOps) | Site-bound lifecycle from assignment to activation, rotation, suspension, or revocation. |
| Paper Certificate | Logistics | Physical program certificate shipment, separate from executable-module fulfillment. |
| Audit Lineage | Audit Service | Signed event chain from learning through activation. |
Process
- The training platform (LMS) issues the Program Certificate.
- Commercial Entitlement becomes active for an organization and site set.
- The Fulfillment Service validates the matching delivery profile and builds the Delivery Pack.
- The Key Operations Service (KeyOps) assigns site-bound hardware keys.
- The customer confirms the checksum and completes the activation test.
Boundary
A Program Certificate confirms training. It does not unlock executable-module fulfillment — that requires a separately paid license, commercial entitlement, site binding, and completed technical checkpoints.
Documents
- Research Aggregation Delivery — delivery for multicenter evidence workflows
- On-Prem Multi-Site Delivery — one entitlement, several site bindings
- Delivery FAQ — certificate, keys, reissue
Discuss delivery terms for your organization. Contact us