Talha Asif — Infrastructure & PMO Executive

Category: Case Studies

  • Crossrail: The £4.1 Billion Overrun That Taught the World About Mega-Project Controls

    The Scale of the Problem

    Crossrail — now the Elizabeth Line — is London’s newest and most celebrated rail link. 100 kilometres of route, 41 stations, a 21-kilometre central tunnel section under the city, and the capacity to carry 200 million passengers annually. When it finally opened to the public in May 2022, it was genuinely transformational for London’s mobility.

    It was also, by the time of opening, £4.1 billion over its 2010 budget and three and a half years behind its original completion target. The story of how that happened is one of the most instructive case studies in mega-project delivery available to infrastructure professionals anywhere in the world.

    The Original Budget and Schedule

    The 2010 budget for Crossrail was £14.8 billion. By the time the project reached its 2018 construction completion milestone — the point at which the new stations had been built and the central section tunnelling was complete — the cost had grown to approximately £17 billion. The project management team advised Transport for London and the government that the project would open in December 2018.

    It did not open in December 2018. The systems integration phase — the process of integrating train control software, rolling stock, station fit-out, and signalling infrastructure into a functioning operational system — proved far more complex and time-consuming than the programme had anticipated. Opening was deferred, then deferred again, through 2019, 2020, and into 2021 before supply chain disruption from the pandemic added additional complications. The final cost was approximately £18.9 billion.

    The Optimism Bias Problem

    The first failure mode in Crossrail’s delivery was optimism bias — the systematic tendency for infrastructure programs to underestimate cost and schedule at inception. The UK’s Treasury Green Book has incorporated optimism bias adjustments into its guidance for infrastructure investment appraisal since 2004. Despite that guidance, Crossrail’s original cost estimates and schedule were developed with insufficient allowance for the complexity and uncertainty that a program of this scale inevitably contains.

    The 2010 budget was a point estimate — a single number — rather than a range reflecting the genuine uncertainty of a program that would not be complete for 12 years. The construction cost growth that occurred between 2010 and 2018 was not random. It was the systematic resolution of scope uncertainty in ways that added cost: utility diversions that proved more complex than the survey data indicated, ground conditions that varied from geotechnical assumptions, contractor performance that did not meet programme expectations, and design development that added scope as the technical requirements of the central section became better understood.

    The Systems Integration Underestimate

    The most significant single source of delay in Crossrail was the systems integration phase — and it is the lesson most directly applicable to Saudi Arabia’s mega-project programs. Systems integration on a complex railway involves testing and validating the interaction of train control software, rolling stock software, signalling infrastructure, station systems, and network control systems in a sequence that must demonstrate operational safety before passengers can be carried.

    On Crossrail, the systems integration challenge was compounded by the sheer novelty of the central section — a purpose-built tunnel environment with technical systems that had not previously been integrated in this combination. Testing revealed issues that required software modifications, which required re-testing. The cycle of test-find-fix-retest consumed far more time than the programme had allocated.

    The lesson for Saudi Arabia’s rail and transit programs — where new systems are being commissioned at pace and scale — is clear: the systems integration phase must be planned with adequate time, resources, and contingency from the beginning of the programme. It is not a compression opportunity. It is a sequence that cannot be rushed without safety consequence.

    The Governance Failure

    Independent reviews of the Crossrail overrun consistently identified a governance failure in how the project team and the sponsor bodies — Transport for London and the government — communicated about programme status. The project team was aware of integration challenges and schedule risk well before the December 2018 opening was publicly committed to. The information did not reach the programme’s governance structure in a way that enabled timely decision-making.

    This is the governance lesson that translates most directly to the Saudi context: major programmes need honest schedule and cost assessment that reaches the decision-making level, not filtered reporting that tells sponsors what they want to hear. Building that honesty into the reporting culture — which requires sponsors who are genuinely willing to receive difficult news — is as important as building the technical systems that generate accurate data.

  • Riyadh Metro: What the World’s Largest Metro Construction Program Teaches About Multi-Package Delivery

    The Scale of the Ambition

    When Saudi Arabia’s government awarded the Riyadh Metro contracts in 2013, the program represented one of the most ambitious urban transit delivery decisions in history. Six metro lines. 176 kilometres of route. 85 stations. More than SAR 60 billion of construction contracts awarded simultaneously to five international consortia. And a delivery timeline that required a significant portion of the network to be operational within a decade.

    The delivery structure divided the network by corridor. The BACS consortium — a joint venture bringing together Bechtel, Almabani, CCC, and Siemens — took responsibility for Lines 1 and 2, the north-south and east-west spines of the network. The ANM consortium covered Line 3, the northern connector. The FAST consortium — combining FCC, Alstom, Samsung, Strukton, and Freyssinet — delivered Lines 4, 5, and 6.

    This multi-package structure was a deliberate choice. A single program management contractor managing the full network would have been the alternative — but the scale was too large and the timeline too compressed for a single entity to absorb the delivery risk. Dividing by corridor distributed the execution risk while maintaining a unified technical standard managed by the Royal Commission for Riyadh City as the program authority.

    What Made It Work

    The technical integration challenge — six lines from five consortia that needed to work as a seamless operational network — was addressed through a rigorous interface management framework. System-wide standards for track gauge, electrification, signalling, and rolling stock compatibility were established before the contracts were awarded. Each consortium built to those standards. The integration was achieved at the level of technical specification, not through a single delivery entity.

    The scale of international expertise brought to the program was exceptional. The consortium structure allowed Riyadh to draw on the combined experience of firms that had delivered metro systems across Europe, Asia, and the Americas. That expertise was not available in a single company. The multi-package approach made it accessible.

    The speed of delivery — from ground-breaking to initial operations on Lines 1-3 in under a decade — was enabled by parallel construction across all six lines simultaneously. A sequential delivery approach — complete one line, then start the next — would have been operationally simpler but would have extended the program by years. Parallel delivery required exceptional program management capability from the Royal Commission, but it achieved a network opening timeline that would have been impossible through any other approach.

    The Lessons That Apply Beyond Riyadh

    Interface management at program scale requires a dedicated function, adequate authority, and pre-agreed resolution mechanisms. When five consortia are building systems that need to work together, interfaces between their work packages are the single most dangerous source of delay and dispute. The Riyadh Metro program established an interface management framework that identified interface events, assigned ownership, and tracked resolution. That function needs to be resourced as a first-class program management activity, not a secondary coordination role.

    Owner capability must grow with program scale. The Royal Commission for Riyadh City developed substantial program management capability through the Metro delivery. That institutional growth — in commercial management, technical oversight, and stakeholder management — was a program outcome as valuable as the physical infrastructure. It positioned the Kingdom for the next generation of urban transit programs with a depth of institutional experience that did not exist before.

    Rolling stock and systems integration timelines control operational readiness more than civil works timelines. The most common source of metro opening delays globally is the integration of train control systems, rolling stock, and civil infrastructure into a functioning operational system. Building the systems integration timeline into the master program schedule from the beginning — with appropriate float and staged commissioning sequences — is essential for realistic operational readiness planning.

    The Western Station — Riyadh Metro’s most architecturally significant station, now complete and operational — represents the program’s highest-profile delivery. Its opening marks a milestone in a program that has genuinely transformed the mobility infrastructure of one of the world’s fastest-growing cities. The lessons of how it was delivered will inform transit programs across the region for the next generation.

  • From PFI to PF2: What the UK’s Public Private Partnership Correction Teaches Saudi Arabia

    The PFI Model and What It Was Trying to Solve

    The UK’s Private Finance Initiative was launched in 1992 as a response to a genuine problem: the government wanted to invest in public infrastructure but was constrained by public sector borrowing limits. PFI offered a solution — private sector capital finances the construction of public assets, which are then leased back to the government over long concession periods in exchange for availability payments. The private sector bears construction and performance risk. Government avoids upfront capital expenditure. The public gets new hospitals, schools, and transport infrastructure.

    The logic was sound in principle. By 2018, the UK had signed more than 700 PFI contracts with a combined capital value of approximately £170 billion. Contracts spanning hospitals, schools, prisons, defence facilities, and transport infrastructure. Some of the world’s most complex infrastructure P3 transactions were structured under the PFI banner.

    What Went Wrong

    The problems that eventually undermined PFI’s political credibility were not accidental. They were structural features of the original model design that produced predictable outcomes over time.

    The refinancing windfall problem emerged clearly within the first decade of PFI contracts. Many early PFI transactions were financed at relatively high interest rates reflecting the uncertainty of a new and untested model. As the model proved itself and lender confidence grew, consortia refinanced their project debt at lower rates — generating significant financial gains that under the original contracts flowed entirely to the private sector. The National Audit Office documented cases where refinancing gains ran to tens of millions of pounds on individual transactions. Public perception of these gains — representing public subsidy being converted to private profit — created significant political damage.

    Flexibility constraints created operational problems that compounded over time. A hospital PFI signed in 1997 under a 30-year concession needed to manage the introduction of new medical technologies, changing clinical models, infection control requirements, and evolving maintenance standards. The contract’s variation mechanism — designed for occasional changes of limited scope — was not equipped to manage the pace and scale of change that healthcare delivery underwent. Simple changes that could be accomplished in a directly managed public facility in days required weeks of formal variation process and often resulted in pricing disputes. The transaction cost of managing contract variations became a significant operational burden on NHS trusts.

    The financing premium — the difference between PFI financing costs and equivalent public borrowing — proved larger and more persistent than the model’s architects anticipated. The National Audit Office estimated financing costs approximately 2-4% higher than public sector equivalent borrowing across the program. Across £170 billion of commitments, that differential compounds to an enormous aggregate cost over concession lifetimes.

    The PF2 Reform and Why It Fell Short

    The government’s 2012 PF2 reforms were a genuine attempt to address the most documented PFI problems. Public sector equity participation of 25% would give government a share of refinancing gains and a governance presence in consortium management. Risk transfer was to be refined toward risks the private sector could genuinely manage. Standardized contracts would reduce transaction costs. Benchmarking requirements would keep facilities management pricing competitive.

    The reforms were technically sound. But the political environment around PFI had deteriorated beyond the point where technical reforms could restore confidence. By 2012, PFI had become politically toxic in a way that transcended the specific structural problems. The announcement that no new PFI contracts would be signed effectively ended the program before PF2’s innovations could be tested at scale.

    Lessons for Saudi Arabia’s National Privatization Strategy

    Saudi Arabia’s NPS is structuring a P3 program with the full visibility of what went wrong in the UK. That visibility should be used deliberately, not merely acknowledged.

    Design risk allocation around what the private sector can actually control. Construction execution, lifecycle maintenance, and operational performance are risks the private sector manages well when the contract gives them genuine control. Regulatory risk, policy change, and public sector interface risks should be retained or shared — not transferred at a premium the concession cannot absorb.

    Build refinancing sharing from the beginning. This problem is entirely preventable through contract drafting. Revenue sharing, clawback provisions, and equity participation arrangements exist as well-documented contract structures. There is no reason for Saudi P3 contracts to recreate the UK’s refinancing windfall problem.

    Invest in contract flexibility architecture. The variation mechanisms in Saudi P3 contracts need to be designed for the pace of change in their sectors — particularly in health, education, and technology-dependent infrastructure. Pre-agreed pricing methodologies and structured variation procedures reduce the transaction cost of managing change throughout the concession period.

    The UK’s experience is not an argument against P3. It is an argument for structuring P3 correctly. Saudi Arabia has that opportunity. The question is whether the pace of the NPS program allows time to apply these lessons carefully as each sector is brought into the framework.

  • Australia’s PPP Maturity Journey: 30 Years of Lessons for Saudi Arabia’s P3 Program

    The Early Failures: Demand Risk and the Toll Road Experience

    Australia was among the first countries to develop a substantial P3 program for infrastructure delivery, beginning in earnest in the 1990s. The early transactions were focused on toll roads — an asset class where the demand risk case for private sector financing seemed clear. Build a road, charge users, let the private sector earn a return from the traffic it generates.

    Several of these early transactions produced serious financial problems. The Sydney Cross City Tunnel, the Lane Cove Tunnel, and the Brisbane Airport Link all experienced demand shortfalls severe enough to push concession companies into administration or financial restructuring. Traffic forecasts — used to justify the project’s financial structure — proved significantly optimistic. The private sector had accepted demand risk under the assumption that traffic would follow the infrastructure. In several cases it did not, at least not quickly enough to service the project’s debt.

    The political response was significant. Governments had guaranteed minimum revenue on some transactions and were called upon to make payments that had not been budgeted. Public perception shifted toward skepticism about whether private sector involvement produced value for taxpayers or simply shifted risk to them through the back door.

    The Adaptation: Availability Payments and Social Infrastructure

    Australia’s response to the toll road failures was to shift P3 activity toward social infrastructure — hospitals, schools, courts, correctional facilities, and public transport — using availability payment structures rather than user fee concessions.

    The availability payment model addressed the demand risk problem directly. Instead of the private sector earning revenue from users — and bearing the risk that user demand would not materialize — the government paid a service fee conditional on the asset being available and performing to standard. Demand risk stayed with government. The private sector bore construction risk and performance risk — risks they could actually manage.

    This shift produced much more stable outcomes. Social infrastructure PPPs delivered under availability payment structures in New South Wales, Victoria, and Queensland delivered assets on time and on budget at rates significantly better than equivalent public procurement. Performance monitoring frameworks kept concessionaires accountable through the operational phase. The experience built institutional confidence on both sides — government procurers who understood how to structure transactions and concessionaires who understood how to deliver them.

    The National PPP Guidelines

    One of Australia’s most significant contributions to global P3 practice was the development of standardized national procurement guidelines — the National Public Private Partnership Policy and Guidelines — establishing a consistent framework across all Australian jurisdictions.

    These guidelines established standard risk allocation positions across infrastructure types, reducing the transaction cost of P3 procurement by giving bidders predictable starting points. They required public sector comparator analysis — demonstrating that private finance produced genuine value relative to public procurement — as a discipline against optimistic assumptions about the cost of risk transfer. They established market engagement principles requiring government to consult with potential bidders during transaction development to test market appetite and identify structural barriers to competition.

    The standardization produced genuine efficiency gains. Transaction costs fell as bidders became familiar with the framework. Bid preparation costs declined as document formats and due diligence requirements became predictable. Competition improved as the market developed a class of experienced bidders who could assess and price P3 risk reliably.

    The Financing Market Depth

    One of the most significant differences between a mature P3 market and an emerging one is the depth of the domestic financing market. Australia’s P3 program developed alongside a deep superannuation fund sector — large institutional investors managing retirement savings with long investment horizons and preference for stable, inflation-linked returns that align well with availability payment P3 cash flows.

    This domestic capital base reduced Australia’s P3 dependence on international financing markets and produced more competitive financing terms than programs that rely primarily on bank debt. It also created a class of sophisticated infrastructure investors who understand the asset class and can deploy capital efficiently on new transactions.

    The Most Valuable Lesson

    The most important lesson from Australia’s P3 maturity journey is that getting the framework right takes iteration. No market gets it perfectly right the first time. What distinguishes markets that develop strong P3 programs is not that they avoided mistakes — Australia made significant mistakes — but that they learned from them systematically and adapted their frameworks in response.

    Saudi Arabia is moving faster than Australia ever did. The 220-transaction NPS target by 2030 is an ambitious pace that creates opportunity and risk simultaneously. The opportunity is transformational public asset delivery. The risk is scaling faster than the institutional capability to manage the program develops. Australia’s experience suggests that investment in institutional capability — in the people, systems, and frameworks that govern P3 programs through their operational phase — is as important as investment in the transactions themselves.

  • The OnCorr Model: What Metrolinx’s Mega Transit Contracts Teach About Large-Scale Delivery

    The Background

    To understand what OnCorr was designed to solve, you need to understand what came before it. Metrolinx had spent more than a decade delivering transit infrastructure through traditional procurement models — design-bid-build contracts, consultant-led design with contractor construction, sequential delivery stages. The results were mixed. Some projects delivered within budget and schedule. Many did not. And the scale of the programs being contemplated under Ontario’s transit expansion commitments — GO Regional Express Rail, the Ontario Line, the Eglinton Crosstown extensions — exceeded the capacity of traditional procurement to manage efficiently.

    OnCorr — the Corridor and Station Infrastructure programs — was Metrolinx’s response. Rather than procuring individual projects through traditional competitive tendering, the agency structured large-scale, long-term contracts covering entire transit corridors. The theory was that corridor-scale contracts would produce better outcomes: deeper contractor investment in the program, more efficient supply chain development, better coordination across interdependent work packages, and more meaningful risk transfer to parties with the capacity to manage it.

    The Consortium Structure

    OnCorr contracts were structured as joint ventures between major infrastructure firms with complementary capabilities. The corridor contracts attracted some of the most significant infrastructure companies active in the Canadian market.

    For Lines 1 and 2 (now identified as the Bloor-Danforth and Yonge-University subway corridors), the BACS consortium — bringing together major contractors with deep subway rehabilitation experience — took on the program. For Line 3, the ANM consortium led delivery. For Lines 4, 5, and 6 — the Sheppard, Eglinton, and Finch corridors — the FAST consortium structured the delivery approach.

    The consortium model was intended to concentrate capability. A single consortium responsible for a full corridor could develop systems knowledge, supplier relationships, and workforce capacity that individual project contractors could not. The theory was sound. The execution created challenges that were not fully anticipated at the time of contract structuring.

    What the Model Revealed

    Large transit programs are not merely engineering challenges. They are commercial, financial, and governance systems that need to function together across very long delivery horizons. The OnCorr model revealed several structural tensions that deserve serious analysis, particularly for anyone structuring ambitious transit programs in the Gulf.

    Corridor-scale contracts create market concentration in ways that reduce the competitive discipline that large programs normally benefit from. When a single consortium controls the delivery of an entire corridor — potentially across a decade or more of work — the owner’s leverage in commercial negotiations progressively diminishes as the program advances. The consortium has made significant system investments. Replacing them creates disruption that the owner cannot easily absorb. The contract must be designed to maintain commercial tension in the absence of competitive market pressure.

    Scope uncertainty in transit rehabilitation programs — where the condition of aging underground infrastructure is only fully understood once the work starts — creates systematic change order pressure that the commercial framework needs to be designed to manage. In a corridor-scale contract, that pressure accumulates across a very large scope base. Change management frameworks that work for individual projects may not scale to program-level delivery without modification.

    Governance at the program level is structurally more complex than project-level governance. The interfaces between the consortium’s delivery approach and Metrolinx’s operational requirements — maintaining service during construction, coordinating with other transit agencies, managing community impacts — require governance mechanisms that were still evolving as the programs advanced.

    Lessons for Saudi Arabia’s Transit Ambitions

    Saudi Arabia’s rail and transit programs — including Riyadh Metro’s ongoing expansion, Saudi Railway Organization programs, and the transit elements of giga-project delivery — face analogous structuring challenges. The scale is larger. The timeline is more compressed. And the institutional experience with transit P3 and progressive delivery is less developed than Canada’s, which itself was still learning.

    The lessons from OnCorr that apply most directly to the Saudi context: ensure that contract scope is as well-defined as possible before award, build structured change management frameworks that can handle scope evolution without creating adversarial dynamics, design governance structures that match the pace of progressive delivery rather than the cadence of traditional procurement review, and maintain commercial mechanisms that keep consortium performance incentivized across the full program duration.

    The OnCorr model’s ambition was correct. The execution challenges it encountered were instructive, not disqualifying. Saudi Arabia’s program authorities have the advantage of this experience to draw on as they structure their own corridor-scale delivery programs.

Powered by
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Powered by