Vertical Program Integration Studio

01 · Set up

Scenario setup

Enter each vertical program and its shared capacity and funding limits, then, for every component category, what each program spends and draws today. Flag components that can never merge as non-negotiable so the optimizer never proposes them.

Vertical programs

Capacity & funding limits

Hard limits — bundles that breach them are excluded

Total funding$k/yr available

Status quo $1,765k (100%) · leanest $1,521k

Staff-hourshrs/yr

Status quo 3395 (89%) · leanest 2400

Vehicle-daysveh-days/yr

Status quo 568 (84%) · leanest 390

Field-daysfield-days/yr

Status quo 551 (86%) · leanest 400

Funding defaults to the current total program cost. Lower it to model a budget cut — the status quo then breaks the ceiling and only integration options that fit the reduced envelope survive.

Component categories

Integrated

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

If merged into one shared instance (combined standalone today: $270k/yr). Enter these as ranges — the point estimate drives shortlisting, the low/high bound the robustness sweep.

Government funded when mergedThe country / health system pays the shared instance — it leaves the program’s books as a saving but becomes a country liability.

Integrated cost $k/yr

Low$Point$High$

Transition cost $k (one-time)

Low$Point$High$

Shared-instance resource drawStaff-hoursVehicle-daysField-days

Integrated

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

If merged into one shared instance (combined standalone today: $390k/yr). Enter these as ranges — the point estimate drives shortlisting, the low/high bound the robustness sweep.

Government funded when mergedThe country / health system pays the shared instance — it leaves the program’s books as a saving but becomes a country liability.

Integrated cost $k/yr

Low$Point$High$

Transition cost $k (one-time)

Low$Point$High$

Shared-instance resource drawStaff-hoursVehicle-daysField-days

Integrated

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

If merged into one shared instance (combined standalone today: $440k/yr). Enter these as ranges — the point estimate drives shortlisting, the low/high bound the robustness sweep.

Government funded when mergedThe country / health system pays the shared instance — it leaves the program’s books as a saving but becomes a country liability.

Integrated cost $k/yr

Low$Point$High$

Transition cost $k (one-time)

Low$Point$High$

Shared-instance resource drawStaff-hoursVehicle-daysField-days

Integrated

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

If merged into one shared instance (combined standalone today: $300k/yr). Enter these as ranges — the point estimate drives shortlisting, the low/high bound the robustness sweep.

Government funded when mergedThe country / health system pays the shared instance — it leaves the program’s books as a saving but becomes a country liability.

Integrated cost $k/yr

Low$Point$High$

Transition cost $k (one-time)

Low$Point$High$

Shared-instance resource drawStaff-hoursVehicle-daysField-days

Integrated

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

If merged into one shared instance (combined standalone today: $205k/yr). Enter these as ranges — the point estimate drives shortlisting, the low/high bound the robustness sweep.

Government funded when mergedThe country / health system pays the shared instance — it leaves the program’s books as a saving but becomes a country liability.

Integrated cost $k/yr

Low$Point$High$

Transition cost $k (one-time)

Low$Point$High$

Shared-instance resource drawStaff-hoursVehicle-daysField-days

Remain separate

Program	Standalone $k/yr	Staff-hours	Vehicle-days	Field-days
Program 1	$
Program 2	$

Non-negotiable: this component can never merge regardless of cost logic. Each program keeps its own instance.