Use cases
Five planning problems Provenesis is built for.
Each one starts with a question supply chain and manufacturing leaders ask every week. Provenesis answers it with a plan, the trade-offs behind it, and what is at stake in dollars.
Use case 01
Commercial slot planning and patient scheduling
Which patient takes which slot, and when should we collect?
The situation
Commercial demand arrives one patient at a time. Treatment centers want firm dates, and manufacturing wants full suites without overloading operators or QC.
Decisions Provenesis makes
- Collection date and apheresis site for each patient
- Manufacturing site, suite, and slot for each batch
- Release and infusion dates the treatment center can plan around
What you get
A patient-level schedule and a suite-level slot plan, with the constraints that set them.
Use case 02
Capacity expansion and network design
Where do we add capacity, and what is it worth?
The situation
Demand is growing faster than the network. The options include another suite, another shift, more QC analysts, a new site, or a contract manufacturer, each with its own cost and lead time.
Decisions Provenesis makes
- Which capacity to add, where, and when
- How to split demand across sites and markets
- Which bottleneck to relieve first
What you get
Network scenarios compared in dollars, with the value of each added unit of capacity.
Use case 03
Vector and materials planning
Will we have released vector for the patients we plan to treat?
The situation
Lentiviral and retroviral vector lots are slow to make and release, and they are shared across products and markets. A shortfall surfaces later as patients who cannot be scheduled.
Decisions Provenesis makes
- Vector campaign timing and lot sizes against patient demand
- Allocation of vector and critical materials across sites and products
- Safety margins sized to real failure and retest rates
What you get
A materials plan tied to the patient plan, so supply and demand are planned together.
Use case 04
Clinical-to-commercial scale-up
What does the network need to look like at launch?
The situation
Clinical supply runs on a few slots and a lot of manual coordination. At approval, volume, sites, and markets all change at once, and the spreadsheet does not scale with them.
Decisions Provenesis makes
- Slot, staff, and QC capacity needed by launch phase
- Which sites and markets to bring online, and in what order
- Where clinical and commercial demand compete for the same capacity
What you get
A launch plan built on the same model you will run commercially.
Use case 05
Disruption response
A batch failed release. A courier is late. What now?
The situation
In advanced therapies a disruption lands on a specific patient. The response has to protect that patient's path without breaking everyone else's.
Decisions Provenesis makes
- Re-collection and re-manufacturing options for the affected patient
- Which slots and shifts to rearrange, and which patients move
- Courier and release alternatives when a lane or a test is delayed
What you get
Re-planning options compared side by side, each with its effect on other patients and its cost.
Questions
Common questions.
- Does Provenesis handle allogeneic therapies?
- Allogeneic programs plan batch campaigns, dose inventory, and expiry rather than one batch per patient. That is close to the batch process planning Mizahn was built for. Tell us about your program in the demo and we will be specific about fit.
- Does it replace our ERP, MES, or chain of identity platform?
- No. Provenesis is a planning system. It decides what should happen and when. Your ERP, MES, and orchestration systems still execute and record it.
- Do we need a demand forecast?
- Provenesis works from your existing demand forecast and patient pipeline. It does not produce the forecast.
- How does it get our data?
- We start from the data your team already maintains, such as slot calendars, staffing rosters, QC schedules, and the patient pipeline. [TODO: approve wording on data connections]
- Is it a black box?
- No. It is mathematical optimization on a model of your network. Sites, suites, constraints, and costs are named and inspectable, so your team can see why the plan chose what it did.
- What about GxP and validation?
- [TODO: approve a GxP and validation statement before publishing anything here]
Next step
See Provenesis on a network like yours.
Book a working session with the founder. Bring your hardest planning week and we will show how Provenesis would plan it.