How a Mega Metro Program Held the Line on Cost Forecasting When the Ground Itself Was the Risk
In January 2005, T.C. Istanbul Buyuksehir Belediyesi (IETT) awarded the Kadikoy-Kartal Rayli Toplu Tasima Sistemi, an underground metro program traversing one of the most densely built corridors on the Asian side of Istanbul, to a five-firm joint venture (Yapi Merkezi, Dogus, Yuksel, Yenigun, Belen). The contract covered station-box excavation, tunnel construction, mechanical and electrical systems, and finishing works across a multi-year horizon. Cash flow was forecast through 5 years visibility requirement.
Underground metro work is uniquely exposed to discovery risk. Soil profiles, groundwater elevation, rock depth, and the requirement for ground improvement (jet grouting) are estimated from preliminary boreholes, and revised the moment excavation begins. In April 2006, the program's earned value position dropped to BLACK status: Schedule Performance Index (SPI) at 0.254 (actual progress at one-quarter of plan) and Cost Performance Index (CPI) at 0.779. Five contracting firms, dozens of subcontractors, and the owner's board needed to know, within thirty days, what the project would cost at completion if April performance continued, and whether May was a recovery or a deeper fall.
How does the management board of a mega metro joint venture know, every month, with verifiable arithmetic, what the project will cost at completion when a single material unit rate (say, a one-cent shift in the price of jet grout cement) can ripple through thousands of linked activities and reshape the forecast?
A seven-discipline Project Management Plan (Time, Cost, Contract, Quality, Safety, Risk, Communication), documented in 2005, established governance. A unified Master Coding System assigned a single alphanumeric ID to every activity, every cost line, and every quantity record so that Primavera, ERP, SAP, and the site's quantity surveys all spoke the same language. And an Integrated Cost Control System closed the loop: when a unit cost moved by one cent, the master code propagated the change through every linked activity, recomputed CPI, and re-derived the Estimated Cost at Completion (EAC = BAC / CPI). The 2006 CPI of 0.779 implied a forecast running 28% over baseline; one month later, with CPI at 1.317, the forecast tracked under baseline by 24%, a 52-percentage-point swing visible within thirty days of the discovery event.