Data-Center Construction Delay / Procurement War Game
A project-controls model connecting schedule slip, procurement bottlenecks, commissioning gates, owner dependencies, and recovery priorities.
Synthetic procurement/scenario prototype
Task: Keep estimates, quoted windows and actual commitments distinct while comparing bounded recovery assumptions.
Contribution: Project direction by Kamal; AI-assisted implementation of explicit commitment and recovery-review logic beside the original case.
Inputs → processing → output: Synthetic procurement evidence + timing/cost assumptions → freshness, commitment and commissioning checks → review issues and wait-versus-fallback arithmetic.
Technology: React · Pure JavaScript evaluator · JSON schema + fixtures · Date and cost validation
What the reviewer can do: Change evidence/reconfirmation dates, commitment fields or fallback inputs and inspect resulting review gates and cost comparisons.
Limits: No real vendor commitment, authorized purchase trigger, forecast, calibrated confidence probability or validated recovery result.
Try the inputs · Inspect implementation · View full case
What changes when you change an input?
Changing the reference date, evidence dates or commitment fields updates age, consistency and readiness checks. Changing wait duration, delay cost or fallback assumptions recalculates the cost comparison. Reconfirmation updates freshness without converting an estimate into a firm commitment.
Computed: Evidence age and date/readiness flags; wait-cost range; fallback cost including activation delay; expected wait-minus-fallback difference.
Published baseline: The original recovery/prerequisite views, charts and baseline figures above remain prepublished evidence. The extension computes a separate synthetic comparison.
Estimates and commitments remain distinct. Assumed costs are not approved purchase triggers; no delivery probability, operational forecast or expert-approved generator trigger is asserted.
Current portfolio résumé · Contact · Implementation evidence