MATARAT Holding stewards Saudi Arabia's airports. Its P&TA division sets and governs the National Capital Projects Portfolio — every capital project across five operating companies, from first idea to board approval. I lead digital enablement for that division through Egis: first by building the CAPEX platform that took the 2026 budget cycle off email, then by architecting CIMS, the system that governs the entire project life cycle of which CAPEX is one chapter.
Five operating companies submit capital proposals upward. P&TA reviews, endorses, and consolidates them into one annual investment plan aligned to the National Aviation Strategy — 27 airports in scope.
The 2026 CAPEX cycle had to run before any enterprise system existed. So I built one on the ground already under our feet — the Microsoft 365 estate MATARAT already owned. No new platform, no new vendor, no additional licence cost.
Auto-detects what changed between business-case versions and judges whether reviewer comments were actually addressed — fully, partially, or not at all. Reviewers read only the delta, not the whole document again.
Generates signature-ready PDF business cases from validated data. Templates auto-populate — formatting inconsistency and manual drafting stop existing as a category of work.
Continuous visibility of submission progress, iterative reviews, and pending tasks across every OpCo and department — which removed the follow-up email as an instrument of project management.
Business-case preparation and technical review went from days to minutes. Real-time consultation replaced email delay. The measurable win was cost and time; the structural win was that the portfolio finally had one governed record.
Submitted to Egis' internal innovation competition, the platform advanced through the first and second rounds and was presented in the final. It didn't take a podium place — but the work it proved became the mandate for something much larger.
The CAPEX platform governed one chapter of the story: the annual budget cycle. CIMS governs the whole book — the PMO's system of record across the full airport project life cycle, from first idea to board report. Thirteen modules, built on Dataverse behind an Entra ID sign-in and a single-licence secured gateway, with server-side data scoping per company and a full audit trail. Delivered as a 71-item, Jira-tracked program with a live client-facing dashboard.
The interim platform was never the destination. It proved — on live national data, under a real board deadline — that governed automation works here. That proof is what made the case for the full life-cycle system.
Dataverse as the record layer, Entra ID for identity, one secured gateway licence rather than per-user seats — built entirely on the estate MATARAT already owns.
Server-side data scoping per operating company, full audit trail, and separation of duties — five companies in one system without seeing each other's portfolios.
A 71-item Jira-tracked program with a live client-facing progress dashboard — the delivery of the governance system is itself governed and visible.
Team Leader, promoted from Geospatial Solutions Architect — delivering a work package under THEOS-2, the programme in which Airbus built Thailand's second Earth-observation satellite for GISTDA. The package delivered the flagship applications that turn future imagery into decisions: national land-use and flood-risk forecasting, automated hydrological modeling across 30 interconnected reservoirs, and live dashboards for national decision-makers.
This section will follow the same structure as the Egis case study above — the problem underneath the brief, the architecture, and what changed once it ran.
GIS/CAD Engineer on hydropower programs across Southeast Asia — topographic mapping, relief models, and conceptual design in ArcGIS Pro and AutoCAD; GIS-based hydropower potential studies and dam-break flood-impact scenarios; photogrammetry and remote-sensing environmental monitoring; and the regional GIS databases underneath it all.
Selected projects from five years of hydropower and flood-risk work — the technical foundation everything later was built on.
Happy to walk through the architecture decisions behind any of this.