Multi-Year Infrastructure Modernization (1,200+ Employees)
Case study 02 · IT Project Manager & Infrastructure Lead · Applied Materials · 2023–2026

Context
Overhaul of R&D and production IT infrastructure supporting a facility of 1,200+ employees.
Challenge
High-stakes delivery across R&D, IT, Finance, and external contractors, with strict production schedules and long-lead hardware bottlenecks.
My role
- I owned
- Delivery of the infrastructure portfolio: requirements into bills of materials, procurement and long-lead tracking, schedules, and the dashboards leadership used to follow it.
- Scope
- 15 projects, 7 vendors, a 1,200+ employee facility
Actions
- Translated R&D technical requirements into bills of materials and procurement schedules.
- Tracked dozens of long-lead items end to end, from vendor sourcing through installation and handover.
- Built one automated SQL and Tableau dashboard per project, giving tens of executives live visibility into milestones, risks, and budget.
- Moved server workloads to a colocation site.
Results
- 30% lower compute cost after moving servers to a colocation site.Measured as yearly running costs before and after the move.
- On-time milestones with no downtime to R&D schedules during the upgrade.
- Full executive visibility: Manual status reporting replaced by real-time KPI dashboards.Used at every project checkpoint and in the biweekly stakeholder meetings.
- Streamlined forecasting: Recurring budget cycles run in step with Finance and Purchasing.
The hard call
Speed or security on the install schedule. The project sponsor and the facilities lead wanted IT equipment installed on every floor at once to pull the schedule in. With contractor crews still working in the building, that meant leaving expensive equipment exposed without a written security sign-off. I held the installs and put the conflict on the table for both sides. We agreed on extra physical security and a sign-off from the security manager after an on-site check, then installed. Theft and vandalism by contractor crews did hit the site later, so the sensitive equipment was staged in secured rooms.
What I’d do differently
I’d assign an owner to every dashboard input on day one. A dashboard is only as reliable as the data feeding it, and keeping inputs current turned out to be its own ongoing effort, not a one-time build.
Artifacts
An illustrative program view reconstructed from the format actually used, not the real dashboard, all on synthetic sample numbers: schedule risk by workstream (Finance, IT, R&D, contractor teams), a multi-workstream timeline, and budget utilization over time. Click a workstream to see its status detail.
Schedule risk by workstream
Click a workstream for its status detail.
Q3 forecast submitted on schedule, no open budget risks.
Network-gear procurement for the new office is running about two weeks behind.
Lab buildout milestones are tracking to plan.
General contractor flagged a schedule slip on the core office buildout.
Multi-workstream timeline
Dashed line marks today; bars are each team's active build phase.
Budget utilization over time
Illustrative reconstruction of the format on synthetic sample numbers, not the real dashboard or real figures.
