Why Vision 2030 programmes need integrated delivery, not more contractors
The gaps between the physical asset, the technology inside it and the organisation that runs it are where budgets and schedules go. Closing them is a procurement decision.
The Kingdom is delivering more built and digital infrastructure per year than most countries deliver in a decade. The constraint is rarely capital. It is coordination.
Where the cost actually sits
On a typical programme the owner procures an engineering consultant, a main contractor, a systems integrator, a transformation advisor and a PMO — separately. Each is competent. Each has a contract that ends at its own boundary. Interface risk sits with the owner, who is least equipped to manage it.
Most projects do not fail inside a discipline. They fail in the hand-offs between disciplines.
What integration changes
- One programme and one risk register across engineering, technology and operations.
- Design decisions made with knowledge of the systems and the operating model they must serve.
- A single party accountable for the asset working on day one — not for a certificate of completion.
What it does not mean
Integration does not mean one firm self-performing everything. Specialist subcontractors and OEMs remain essential. It means the owner has one accountable partner managing them under a single management system, with interface responsibility contractually inside the team rather than left to the client.
For programme owners, the practical step is to structure procurement so that integration is bought, not assumed.