"Today project controls capability is embedded within delivery workstreams across Development, Construction, Commercials. While effectively local, this creates:"
→ Inconsistent control standard across lifecycle stages
→ Limited independence in reporting time, cost, risk
→ Reactive rather than predictive insights
→ Fragmented data across development, construction & contracts
"As scale and complexity increase, control must be enterprise grade, not project centric."
Quality — Miller Missha
Time — Wayland Jian
Risk — Moataz Mahmoud
Cost — Chris Swann
Contracts — Sarah Southall
Safety — Isaac Soper
Sarah Southall holds "Snr Director, Development Governance & Operational Excellence" within the Commercial team. Chris Swann holds "Director, CAPEX Controls + Risk and Resilience" also under Commercial. Both titles contain "governance" and "controls" language that overlaps with Portfolio Controls' enterprise governance mandate.
This creates ambiguity about who owns governance and controls at an enterprise level — particularly when onboarding new regions or resolving cross-functional disputes about standards and methodology.
Cost and Contracts reporting is owned by the teams accountable for commercial delivery. Portfolio Controls cannot independently verify cost or contracts data without relying on the commercial team to provide it.
New regions (KSA, Mumbai) need consistent controls across all 6 pillars. Current split requires coordination across two VPs and three Director-level teams to establish baseline governance.
Watch Tower and Scorecard are designed for enterprise-wide oversight across all 6 pillars. Currently in prototype — but Cost and Contracts data feeding them is controlled outside Portfolio Controls' line. The build is only as effective as the data governance around it.
Portfolio Controls sets the enterprise framework, but cost and contracts governance operates in a separate lane. Handover risk at phase transitions (pre-flight → in-flight → Cx → handover) where controls methodology should be continuous but ownership is split.
"Establish an independent Project Controls function that operates horizontally across development, providing a single, authoritative source of truth for Safety, Quality, Time, Cost, Contracts."
"This function does not deliver projects — it assures, integrates and informs them."
Accenture's global research identifies four action areas that distinguish top-performing capital project organisations:
Become data-driven. Treat data as an asset. Spot trends earlier, anticipate challenges.
AirTrunk alignment: Watch Tower (emerging risk detection), Project Scorecard (leading/lagging/readiness indicators), Primavera P6 for schedule intelligence. These tools require organisational ownership of data across all pillars — including Cost and Contracts.
Structured collaboration across functional boundaries. Hard handover gates at phase transitions.
AirTrunk alignment: RF Milestones as hard gates across the lifecycle. Customer Integration embedding requirements into governance. Requires a single orchestrator across all 6 pillars.
Upskilling, outcome-driven partnerships, pipeline for project leaders.
AirTrunk alignment: Knowledge Hub, Training & Capability Centre, playbook-driven onboarding. The functional vs operational separation (see Tab 4) is the structural enabler.
Structured gate reviews at phase transitions. No progression without formal confirmation.
AirTrunk alignment: RF Milestones (Market Entry → Site Selection → Due Diligence → Business Case → Design → Contract → Commissioning → Operations → Service). Quality Milestones QM01–QM11. Must be governed by an independent controls function.
Centralised platform aggregating planning, scheduling, cost, safety, risk, engineering data into actionable insights. Directly analogous to Watch Tower + Project Scorecard.
"Organisations must institutionalise ownership for building the right operating environment to collate and deploy useful data."
The structural case for Portfolio Controls having authority over all 6 pillar data streams — whether direct or dotted-line.
Global EPC firms and hyperscaler owner-operators separate functional authority (global standards, methodologies, frameworks — time-zone independent) from operational authority (regional execution — time-zone aligned). This is the model that enables scaling without degrading the functional team's capacity to build and maintain the enterprise framework.
See Tab 4: Functional vs Operational for the full analysis of how this applies to Portfolio Controls.
Accenture acquired Soben (project management, scheduling, cost & commercial management for hyperscalers) and DLB (DC engineering, commissioning, construction quality). Both signal: integrated controls spanning cost, schedule, quality under a single governance framework — commercial disciplines operating within that framework, not alongside it.
What they own: Standards, methodologies, frameworks, KPI definitions, scoring calibration, playbooks, data governance, system architecture, escalation protocols, RF gate criteria.
How they work: Time-zone independent. Set the rules once, apply everywhere. Doesn't grow linearly with regions.
Portfolio Controls functional roles: Construction Governance & Assurance (Matt), Project Controls & Intelligence (Brett), Programme (Wayland), Customer Integration methodology (future AD).
What they own: Execution within the global framework. Inspections, audits, customer interface, site verification, data entry, regional reporting.
How they work: Time-zone aligned. Deployed per region. Empowered within delegated authority. Grows with each new region.
Operational roles today: Regional Quality Managers, QC Inspectors (CSA/MEP) under Miller. Customer Integration Managers (CIMs) executing directly with customers in RFP teams.
All of Chris Goldsworthy's direct reports operate as functional roles: Matt (Construction Governance), Brett (Project Controls & Intelligence), Wayland (Programme), Shiva (Systems & Transformation). They set standards, build frameworks, define methodologies. This is correct.
Miller Missha (Director, Quality) is the functional lead: GMS-Q, ITP/ITC frameworks, KPI methodology, CI governance. His direct reports — Regional QMs, QC Inspectors — are the operational layer executing per region. This is the model that needs to extend as the portfolio scales.
Currently regional CIMs both define methodology and execute with customers. As new regions come online:
Functional: AD Customer Integration writes the rules — methodology, templates, customer deliverables register, RFP process standards, interface protocols.
Operational: Regional CIMs sit in RFP teams and execute directly with the customer, applying the functional playbook.
Singapore, Johor Bahru, Sydney, Melbourne, Tokyo, Osaka, Hong Kong
Manageable but stretched. Functional leads are building the enterprise framework (Watch Tower, Scorecard, GMS, playbooks) while supporting governance across active locations.
Without functional/operational separation
Framework development stalls. Watch Tower and Scorecard can't progress from prototype to production because builders also run operations. New regions onboard slowly — each functional lead must personally deploy.
Functional stays fixed; operational scales with regions
Functional leads focus on standards, frameworks, calibration, tool build-out. Operational resource per region executes within the framework. Adding KSA/Mumbai means adding regional headcount — not stretching functional capacity.
The team designing methodology and tooling (Matt, Brett, Shiva) would also need to operate it daily once live. Without separation: build slows, production is under-resourced, no dedicated analyst to run Watch Tower once live.
With separation: Functional team completes build, owns methodology and calibration. Operational resource (dedicated analysts, regional data contributors) runs production.
Both resolve the core problem. They differ in Cost & Contracts integration. VP layer and CDO retained. Systems & Transformation moves to Technology team in both. Customer Integration splits into functional (methodology) and operational (regional CIMs).
Cost & Contracts retain solid-line to VP Commercial. Structured dotted-line to Portfolio Controls for framework compliance, data standards, scorecard methodology.
Lower disruption. Respects delivery accountability. Commercial retains ownership. Faster to implement. Aligned with "works inside the framework, owns their lane."
Dual governance remains. Dotted-line can be weak without VP endorsement. Data quality enforcement depends on relationship. Title overlap not fully resolved.
Cost & Contracts governance moves under Portfolio Controls. VP Commercial retains commercial strategy, negotiations, claims — but controls governance sits within Portfolio Controls.
Eliminates dual governance. Single source of truth with direct authority over all 6 pillars. Maximum reporting independence. Cleanest scalability. No title ambiguity. Watch Tower and Scorecard have direct data authority.
Significant disruption. VP Commercial scope reduction. Over-centralisation risk into commercial decisions (pricing, negotiation, claims must stay with commercial). Careful boundary definition required.