Automating executive reporting on a giga-scale expansion program
- Finding
- Weekly and monthly executive reporting on the Makkah Holy Mosque Expansion ran on manually assembled feeds across progress, IPCs, bundles, quality tests, and manpower.
- Evidence
- End-to-end ETL pipelines in Power BI, Power Query, and Python replaced the manual steps on all five feeds; dashboards are delivered directly to the COO, the lead consultant, and the client PMO.
- Standard
- PMO reporting practice — single source of truth across project packages.
- Consequence
- Executives, the lead consultant, and the client PMO review the same current figures every reporting cycle.
- Provenance
- Role R-SBG — Saudi Binladin Group, April 2025 to present. Owner-verified account.
A governed project data hub on cloud infrastructure
- Finding
- Construction asset records and site visual-tracking streams needed one governed store with controlled access.
- Evidence
- An integrated data hub on Supabase and Cloudflare R2 serves the asset records and tracking streams under role-scoped access rules.
- Standard
- Data governance — row-level access control on a centralized store.
- Consequence
- Teams query the same governed dataset instead of exchanging files.
- Provenance
- Role R-SBG — Saudi Binladin Group, April 2025 to present. Owner-verified account.
Interval-versus-cumulative schedule performance intelligence
- Finding
- Executives needed schedule-variance visibility at two horizons — the reporting interval and the cumulative position.
- Evidence
- A VBA and Excel dynamic-arrays system produces both SPI perspectives and consolidates output to PDF without manual assembly.
- Standard
- Earned value trend analysis — SPI measured at interval and cumulative horizons.
- Consequence
- Schedule variance is read directly from consolidated packs each cycle.
- Provenance
- Role R-SBG — Saudi Binladin Group, April 2025 to present. Owner-verified account.
One data language for a corporate PMO
- Finding
- Corporate reporting fragmented across Planning, Cost Control, Procurement, Technical Office, and one further department; the same items carried different codes in different stores.
- Evidence
- A cross-functional audit diagnosed the fragmentation; a unified WBS/CBS/materials coding framework standardized the shared data language; automated ETL and multi-tiered dashboards consolidated the streams into one CEO-facing interface.
- Standard
- WBS/CBS standardization — one code system across departments.
- Consequence
- Reconciliation gaps between site procurement, warehouses, and engineering closed; routine data-preparation time fell by an estimated 40 percent.
- Provenance
- Role R-GMC — Green Modeling Contracting, September 2024 to March 2025. Owner-verified account.
A Python-to-Power BI pipeline for Primavera P6 XER analytics
- Finding
- Schedule-update analytics for consultancy deliverables ran on manual XER extraction.
- Evidence
- A custom Python pipeline parses and models XER datasets into Power BI, producing configurable reporting on execution progress, baseline variances, and critical-path tracking.
- Standard
- Primavera P6 XER data model — activity, relationship, and WBS fields.
- Consequence
- Executives and clients review current schedule analytics without manual re-extraction.
- Provenance
- Role R-RP — Rutherford + Partners LLC, April 2020 to April 2024. Owner-verified account.
Bidirectional Excel-to-P6 integration for forensic support
- Finding
- Schedule update cycles and forensic delay analyses across a multi-project consultancy portfolio carried heavy manual re-entry between Excel and P6.
- Evidence
- A bidirectional integration tool computes progress updates, remaining durations, and forecast dates; automated reconstruction models keep baseline-versus-actual variance tracking current.
- Standard
- Forensic schedule analysis support — extension-of-time substantiation inputs.
- Consequence
- Update cycles and forensic analyses complete faster with fewer transcription defects.
- Provenance
- Role R-RP — Rutherford + Partners LLC, April 2020 to April 2024. Owner-verified account.
Progress-monitoring systems across four mega-projects
- Finding
- Raw site production records had to become executive reporting — S-curves, labor histograms, lookahead schedules — on a fixed weekly and monthly cycle.
- Evidence
- Automated Excel and database systems converted site records into the required outputs for project directors and client PMOs; P6 schedule updates integrated WBS logic, resources, and CPM analysis to surface slippage trends and check baseline compliance.
- Standard
- Project controls reporting lifecycle — weekly and monthly cadence.
- Consequence
- Reporting cycles ran with reduced discrepancies between field execution, procurement, and commercial management.
- Provenance
- Role R-CCIC — CCIC Qatar, February 2007 to March 2020. Owner-verified account.