IBM zSystems Mainframe-Hardware Maintenance
side by side.
TechCare TPM vs. TLS / Hardware Maintenance Services. Cost range, EOSL advantages, migration path and DACH compliance at a glance — for IT leadership and procurement.
Cost comparison
Example Power S922 with 4-year HMS 24×7×4: TechCare TPM roughly 35–56% below the OEM price.
Active EOSL lines
- z13 / z13s (machine type 2964/2965) · EOSL 2022-06-30
- z14 / z14 ZR1 (machine type 3906/3907) · EOSL 2024-06-30
- z15 / z15 T01-T02 (machine type 8561/8562) · EOSL 2027-06-30
- z16 (machine type 3931 / 3932) · EOSL 2030-12-31
Which IBM mainframe generations we service
- IBM z16 · current generation (Telum processor)
- z16 A01 (single-frame) · z16 A02 (multi-frame, sysplex-scaled) · IBM Telum processor with on-chip AI acceleration · launched 2022
- IBM z15 · z15 T01 / T02
- z15 T01 (high-end, 19-inch frame, IBM z15 processor) · z15 T02 (mid-range, single-frame) · launched 2019
- IBM z14 · z14 ZR1 / z14 M01-M05
- z14 ZR1 (mid-range, single-frame) · z14 M01-M05 (multi-frame, up to 170 PUs) · launched 2017 · many install bases in DACH banks still productive
- IBM z13 · z13 / z13s
- z13 (high-end, 5-frame) · z13s (single-frame, mid-range) · launched 2015 · IBM ESS for z13 expires 2025/2026 — TPM strongly recommended
- IBM zEC12 / zBC12 · legacy generation
- zEnterprise EC12 (zEC12) · zEnterprise BC12 (zBC12) · launched 2012/2013 · IBM ESS already expired — TPM standard case in regulatory long-term setups
ESS status of IBM mainframe generations
| Generation | Released | End of vendor support | TechCare TPM |
|---|---|---|---|
| zEnterprise EC12 (zEC12) | 2012 | 2021 | Recommended |
| zEnterprise BC12 (zBC12) | 2013 | 2022 | Recommended |
| z13 / z13s | 2015 | 2025-2026 | Recommended |
| z14 ZR1 / z14 M01-M05 | 2017 | ca. 2027-2028 | Supported |
| z15 T01 / T02 | 2019 | ca. 2029-2030 | Supported |
| z16 A01 / A02 | 2022 | ca. 2031+ | Supported |
Why TPM for IBM mainframes instead of IBM ESS
IBM Enterprise Server Support for mainframes bundles hardware maintenance, microcode updates, ECA engineering change activities and software subscription into one package. For pure hardware maintenance — which is often the majority case for stable mainframe install bases — you pay for components rarely used in normal operation. We separate the layers: we handle hardware with OEM original parts and mainframe-certified CEs at 30 to 60 percent lower cost. z/OS and z/VM subscriptions plus microcode updates stay contractually with IBM, since they remain necessary for active software licenses.
For generations where IBM raises ESS renewal cost steeply or discontinues it altogether — zEC12, zBC12 are already out of support, z13 expires 2025/2026 — TPM becomes the only economical option for regulatorily forced continued operation. We deliver the documented maintenance process required for BAIT, MaRisk, DORA and VAIT audits in DACH banks and insurers: SLA reports, asset tracking, change management, incident response — all auditable and in German language.
OEM vs. TechCare — where the switch pays off
The full OEM-vs-TPM matrix (spare parts, SLA tiers, language, sub-outsourcing, compliance docs, reporting) is the same for every IBM line — see the IBM battle card.
Stays with IBM zSystems
- AIX / IBM i / z/OS software licenses + updates
- PowerSC / IBM Cloud / Storage Insights subscriptions
- IBM TAC software tickets + microcode subscription
Moves to TechCare
- Hardware defects (memory, disk, PSU, mainboard, modules)
- 24×7×4 on-site SLA with German-speaking field service
- Spare-parts logistics DACH + global hub network
- Fixed-price contract in 48 h, one inventory — one contract
DACH compliance by design.
BAIT/MaRisk documentation package, DORA Art. 28 contract template, ISO 27001 and GDPR-compliant media handling apply identically to every IBM line — details on the IBM battle card.
Migration path from first contact to hand-over.
Same four steps for every IBM line: inventory → fixed-price quote in 48 h → contract (BAIT/MaRisk/DORA hooks) → hand-over with spare-parts provisioning. Details on the IBM battle card.
FAQ on IBM zSystems mainframe maintenance
- Which IBM mainframe generations do you service?
- We service all current and older IBM zSystems generations: z16 (A01 single-frame, A02 multi-frame with Telum processor), z15 (T01 high-end, T02 mid-range), z14 (ZR1 single-frame, M01-M05 multi-frame), z13/z13s plus legacy generations zEnterprise EC12 (zEC12) and zEnterprise BC12 (zBC12). Older frames like z12 or z196 we cover on request, subject to OEM parts availability.
- What does TPM cost for an IBM mainframe vs. IBM Enterprise Server Support?
- In the DACH banking and insurance mid-market we typically see 30 to 60 percent hardware-layer savings vs. IBM Enterprise Server Support. For EOSL generations like zEC12 or zBC12 up to 70 percent. Important: the IBM ESS bundle also includes microcode updates and ECA engineering change activities — these can be retained separately via IBM, which in sum is significantly cheaper than a full ESS contract. Specific figures we deliver after receiving CPU IDs and frame configuration.
- Does TPM meet regulatory requirements for banks and insurers (BAIT, MaRisk, DORA, VAIT)?
- Yes. Our maintenance process is designed for BAIT, MaRisk, DORA and VAIT audits. We deliver: documented asset tracking with serials and CPU IDs, ITIL-aligned change management, incident response logs, monthly SLA reports, subcontractor registers and on request an audit compendium in German. The maintenance itself constitutes an outsourcing matter under MaRisk AT 9 — accordingly we review contract clauses, termination rights and audit access rights with you prior to contract conclusion.
- What happens to our z/OS or z/VM subscription when switching to TPM?
- Nothing. We touch only hardware maintenance. z/OS, z/VM, z/VSE, z/TPF and all software PTFs (Program Temporary Fixes) continue contractually with IBM. You retain all update rights, software compliance, MLC licensing (Monthly License Charge) and CMG service. IBM tools like HCD, HCM, RACF or Db2 continue functioning without restriction — the software layer stays completely untouched.
- How do microcode updates and ECA engineering change activities work without IBM ESS?
- Microcode updates and ECA activities can be obtained separately from IBM — either via a reduced IBM contract covering only these components, or ad-hoc on concrete need. In stable production operation microcode is rarely changed; for critical security patches or compliance-relevant changes we coordinate the IBM procurement path together. The hardware maintenance portion — the most expensive item in IBM ESS — shifts to TPM, the software and microcode portion stays selectively with IBM.
- Can you also service zEC12 and zBC12 even though IBM ESS has already expired?
- Yes, this is even one of our core areas in the mainframe segment. zEC12 has been out of IBM ESS support since 2021, zBC12 since 2022. We continue servicing both generations with OEM original parts from our own warehouse — especially in regulatorily forced long-term setups in DACH banks where migration to z14/z15/z16 is planned but not yet completed. The maintenance meets the same BAIT/MaRisk requirements as for current generations.