Checking the case and its evidence…MODEL SCENARIO
Compare service retained with the same demand and resources.
—
Planned dose obligations / original demand
Inspect the response and evidence →Search and audit status appear after verification.
VACCINE ACCESS × COLD CHAIN × DISRUPTION RESPONSEMake vaccines more accessible.
Make vaccines more accessible.
Keep cold chains resilient.
One plan connects household demand, service sessions, transport and cold-chain resources. When conditions change, see how the plan adapts and how much service it retains.
Measured through accessibility and resilience. Model scenarios; field effectiveness is not yet established.
Loading and verifying the latest accepted results…
ACCESSIBILITY & RESILIENCE
Who can receive service. How much survives disruption.
All charts update together for the same case, scenario and original demand.
ACCESSIBILITY
Plan service. Keep gaps visible.
—Loading planned service and unmet demand.
Groups, household travel and extra burden →RESILIENCE
Every adjustment, backed by evidence.
—The fixed plan and optimization use the same demand denominator.
Explore the response, costs and remaining gaps →ONE CONNECTED SOLUTION
Three barriers. One connected plan.
Bring service within reach
Demand, session locations, household travel and time windows determine who can be served. Separate the travel target from the declared acceptance limit, and retain every unmet obligation.
Demand and household conditions → session plansMake resources work together
Coordinate inventory, cold boxes, cooling packs, vehicles and staff. Match routes, weight and capacity to the original cold-chain protection clock.
Existing resources and cold supply → feasible deliveryRespond when conditions change
Compare three policies for changes known before dispatch. A separate in-transit recovery example checks tasks, positions, resources and remaining protection time.
Declared event and state → adapt, recover or retain gapsACCESSIBILITY / HOUSEHOLDS AND SERVICE
Look beyond totals to the burden on households.
Read coverage alongside each group’s demand. Household burden counts planned household/session visits; unmet obligations remain separate.
Service and group fairness
—Planned dose obligations
—Unmet original demand
Household travel and burden
Targets and acceptance limits follow the declared case rules.
Inspect household results and evidence →C2 household access evidence: Checking household burden under rain conditions.
RESILIENCE / DISRUPTION RESPONSE
See the response. Count the service retained.
Results vary by disruption and search status; some scenarios retain gaps.
Three policies. The same disruption.
Compute this scenario ↗WHAT CHANGED
—
HOW THE PLAN RESPONDED
—
RUNNING COST CHANGE
—INR_ESTIMATE · post-solve activity cash estimate
—
Where it stops: resources, missing evidence and search limits
ENABLING THE TWO GOALS
What makes access and resilience possible.
People and training
Staffing and skills
Clinical, transport, custody and monitoring roles support a plan that can be carried out.
Staffing and implementation assumptions
- Schedules use only declared staff and availability.
- Training is a proposed measure and estimated input, not evidence of completed training or field qualification.
- Existing staff time value is separate from new wage payments.
Transport and cold chain
Vehicles and equipment
Vehicles, cold boxes, net available cooling packs and cold supply enable delivery and disruption response.
Equipment and supply requirements
- Alternative roads and backup resources must already exist in the configuration.
- Heat stress tests use declared synthetic parameters. Ambient temperature does not create new equipment-performance evidence.
- Insufficient cold supply leaves gaps. Missing evidence remains unassessed.
Cost and data requirements
Accounting and evidence
Separate run cash, first-year cash, later annual cash and economic cost to understand the price of retaining service.
Accounting and proposed funding
Current activity cash appears after result verification.
The annual workload assumes 48 rounds. Rupee costs are calculated after solving and do not reselect routes. Payers are proposed; full clinical and procurement costs remain incomplete.
Compare annual costs and investment →JHARKHAND / CASE EXPLORER
Three cases. Three tests of one planning method.
These structured demonstrations make the algorithm’s decisions and computational feasibility inspectable: one village, difficult household access, and a shared multi-village network. Each tests the same method under a different planning challenge.
An independently audited plan shows feasibility for its declared inputs and constraints. Explore how the method responds, which service it can retain and where gaps remain. The synthetic cases have different purposes and scales; service totals do not rank them, and their outcomes do not predict another village’s results.
Dots use your supplied place coordinates; they do not identify surveyed service facilities. Solver sites and roads remain synthetic.
Relief: USGS / Mapzen · Boundary: Natural Earth · Locality cross-check: GeoNames (CC BY 4.0)Map sources & scope ↗
Relief: USGS / Mapzen · Boundary: Natural Earth · Locality cross-check: GeoNames (CC BY 4.0)Map sources & scope ↗
Choose a case on the map or in the list.
01 Choose a place→02 Enter your demand→03 Inspect the plan
A REUSABLE METHOD / LOCAL CONFIGURATION
How another village can build on these cases.
Use a matching case as a planning structure. Replace it with local conditions, then compute and validate a fresh result.
01 / MATCH THE CHALLENGE
Choose a starting structure
Use C1 for a single service location, C2 when household access is the main constraint, or C3 when several villages share resources. These patterns can be combined when local needs overlap.
02 / CONFIGURE THE PLACE
Replace the local conditions
Supply local demand, session locations and windows, road travel and closures, household journeys, stock, staff, vehicles, cold-chain performance and budget assumptions.
03 / COMPUTE AND VERIFY
Test a new plan
Recompute against a matching reference with the same local resources and disruption. Audit feasibility, inspect access and remaining gaps, check search limits and scale, then validate execution in a local pilot.
What can I change here, and what needs a new village configuration?
The current workspace lets you change demand, near/remote splits, session windows, ambient conditions and declared acceptance limits within each preset. Roads, stock, vehicles, staff and equipment still belong to that case. A real new-village deployment requires a complete local configuration through the model integration process; changing a place name does not replace those conditions.
- Demand, sites and session windows
- Define who needs service, where it can happen and when.
- Supply points, roads, travel times and closures
- Define which routes can actually connect supply and service.
- Inventory, staff, vehicles and cold-chain evidence
- Define physical availability, schedules, loading and protection limits.
- Household journeys, targets and acceptance
- Test whether planned service is reachable and what burden remains.
- Budget, prices and operating responsibility
- Assess resource affordability, cash requirements and implementation conditions.
Local input verification and a pilot are needed before claiming comparable field effects. Larger configurations also need runtime and search-capability checks. Unknown inputs remain missing; they are not filled with zero or copied outcomes.
Read the configuration and transfer scope →The transferable result is the planning method. Another village receives its own calculation and evidence.
MODEL & EVIDENCE
Trace every important result to its evidence.
Current case: inputs and outputs
Download this scenario’s core result ↓Download the matching cost receipt ↓Inspect inputs, assumptions and unmet demand →Model and independent checks
Version, audit and search scope
All three policies share the original demand, resource pool, household rules, budget cap and known disruption. Search completion applies only to declared finite candidates; an audit pass does not establish field effectiveness.
Checking result bindings…
Costs, limits and missing data
Estimate scope and field-data gaps
Planned doses are not observed vaccinations. Household acceptance rules are declared assumptions. A temperature excursion does not automatically mean discard; loss-value sensitivity is not realized procurement saving.
The browser verifies the reviewed runtime parameter JSON. The complete original source snapshot is checked locally; workbooks and internal source documents are not published.