Project Description
Employer case study · Cognizant · 2015–2020
The SAP years: five years as the single point of contact
For five years and four months, Alex was the person an enterprise called when anything touched their SAP infrastructure — the consultant on every Severity-1 call, the lead in every weekly status meeting, the name on every infrastructure document.
The work
Blueprint & sizing
Infrastructure blueprinting for an on-premises S/4 HANA implementation — as-is and to-be documentation, sizing requirements coordinated across multiple team leads.
Cloud-to-cloud migration
Oversaw the migration of live SAP systems between cloud vendors, working vendor best practices into the plan — the move nobody notices when it goes right.
Severity-1 operations
Strict SLAs, customer calls on every Sev-1, and a small technical team managed for long-term application support.
Early-warning automation
Automated error detection for recurring jobs — business-critical issues caught before production felt them. The AZ Tech instinct, years early.
Requirements → delivery
Cross-functional teams marshalled to capture business-critical data requirements, translated for the technical teams building the solution.
Knowledge that transfers
Full knowledge transfer of an entire SAP landscape, documented best practices, and every revision managed through design approval.
5.3
years on the account
Sev-1
every call answered, on SLA
S/4 HANA
on-prem blueprint delivered
0
surprises reaching production
The blueprint-first discipline, the documentation habit, the automation-before-outage instinct — this is where the operations half of AZ Tech’s method was drilled. Enterprise SAP doesn’t forgive improvisation, and neither do we.
