Third-Party Maintenance for IBM Power: When It's Smart and When It's a Trap in 2026
Should you move IBM Power hardware maintenance to a third-party provider?
It depends almost entirely on one thing: whether IBM is still developing machine code for your machine. IBM releases firmware and Licensed Internal Code updates only to machines under warranty or under an IBM hardware maintenance agreement, so leaving IBM freezes that stream. On a Power9 scale-out server that left standard support in January 2026, IBM has already stopped producing new machine code, so you give up very little and typically save 30 to 70 percent on the repair contract. On a machine still inside standard support, you are trading current firmware and security fixes for a discount, which is rarely a good trade on a production workload. Operating system fixes are a separate question: keep IBM Software Maintenance and your IBM i PTFs and AIX service packs keep flowing regardless of who repairs the hardware.
At a glance
Key takeaways
One rule decides most of it
IBM provides Machine Code updates only for machines under warranty or an IBM hardware maintenance agreement. Whether that stream still exists for your model is the single biggest input to the decision.
TPM is strongest after end of support
Once IBM stops developing machine code for a model, as it did for Power9 scale-out servers on January 31, 2026, the firmware objection to TPM mostly evaporates and the comparison becomes price, parts, and people.
Your OS fixes are a separate contract
IBM i PTFs and AIX service packs come through Fix Central under Software Maintenance (SWMA), not hardware maintenance. Keep SWMA and the operating system stays patched no matter who fixes the hardware.
Savings are real but model-specific
Quoted ranges run from 30 to 40 percent below an IBM renewal up to 50 to 70 percent off OEM list on older systems. Treat every published percentage as a prompt to get your own quotes, not as a forecast.
What Third-Party Maintenance Actually Is
Third-party maintenance, usually shortened to TPM, is hardware break-fix service bought from an independent firm rather than from IBM. The provider takes the calls, dispatches an engineer, and supplies replacement parts from its own inventory. For IBM Power, AS/400, iSeries, System i, and AIX estates, the established names include Service Express, Park Place Technologies, Curvature, and Evernex, alongside regional specialists. Many of their field engineers are ex-IBM or IBM-trained, and their parts depots are stocked with the same field-replaceable units IBM ships.
What TPM covers is genuinely mechanical: processor and memory failures, power supplies, fans, disks, backplanes, adapters, and the response time commitment around all of it. Contracts are usually structured much the same way IBM structures its own, with a coverage window (business hours or 24x7), a target response time, and an on-site or depot model. Good providers will also cover machines IBM has stopped servicing entirely, which is often the reason a shop calls them in the first place.
What TPM does not cover is the software layer, and this is where the marketing on both sides gets slippery. A TPM contract is not a replacement for IBM Software Maintenance, it does not give you IBM i or AIX upgrades, and it cannot deliver new IBM firmware. The next two sections explain why that last point is the one that should drive your decision.
The Machine Code Rule That Decides the Question
IBM Machine Code, which includes system firmware and the Licensed Internal Code that sits beneath IBM i, is IBM intellectual property licensed to you for use on a specific machine. IBM makes Machine Code updates available only for machines that are under warranty or covered by an IBM hardware maintenance service agreement. A third-party provider cannot legally create, supply, or install it, and no amount of shopping around changes that.
Read that rule the right way round and it stops being a reason to avoid TPM and becomes a timing question. If your machine is still inside IBM standard support, IBM is actively producing firmware and security fixes for it, and leaving IBM hardware maintenance means voluntarily switching that stream off in exchange for a discount. On a production Power system that is usually a bad trade.
If your machine has passed end of standard support, IBM has already stopped developing new machine code for it. The Power9 scale-out models, the S914, S922, S924, H922, H924, and L922, crossed that line on January 31, 2026. From that day forward, staying with IBM hardware maintenance buys you repair service and access to fixes that already exist, not a stream of new ones. The gap between IBM and a competent TPM provider narrows to parts, engineers, response times, and price, which is exactly the comparison TPM is built to win.
One practical caveat: get your firmware and HMC code to the level you want before you leave IBM hardware maintenance, not after. Once the entitlement lapses, the download door closes, and bringing a machine up to a required firmware level later can force you back onto an IBM contract at the worst possible moment.
SWMA vs. HWMA: The Distinction Most Comparisons Miss
IBM sells hardware maintenance (HWMA) and software maintenance (SWMA) as separate agreements, and conflating them is the most common error in TPM conversations. Operating system fixes for IBM i and AIX, the PTFs, service packs, and technology levels you pull from Fix Central, are delivered under SWMA. Firmware and Licensed Internal Code are delivered under hardware entitlement. They are two different taps, and you can turn one off without touching the other.
That means the usual arrangement is not the all-or-nothing choice vendors on both sides describe. Most shops that move to TPM keep IBM Software Maintenance and move only hardware break-fix. The operating system keeps receiving fixes, including security fixes, at full IBM cadence. The firmware underneath it freezes at whatever level you were on when you left. For a machine already past hardware end of support, that firmware level was going to be the last one anyway.
Check one thing before you assume this works for you: whether any upgrade you have planned in the next two or three years carries a minimum firmware requirement. IBM i and AIX releases routinely specify a minimum system firmware level, and a frozen machine cannot always meet it. If a release upgrade is on your roadmap, price the firmware constraint into the decision now rather than discovering it during a change window.
When Third-Party Maintenance Is Smart
Best fit
The machine is past IBM end of support
Power9 scale-out, Power8, and older systems get no new machine code from anyone. Paying IBM a premium for a service extension on a machine it has stopped developing for is the clearest case for shopping the contract.
Best fit
You are running a deliberate 12 to 24 month bridge
A dated bridge to a planned Power11 refresh or cloud migration is TPM's best use. It converts a rushed six-figure decision into a scheduled one, and the discount pays for part of the destination.
Best fit
Non-production, isolated, or archive systems
Development boxes, reporting LPARs, and read-only archive machines rarely justify OEM pricing. Break-fix cover from an independent provider with tested spares is proportionate to the risk.
Best fit
A mixed-vendor estate you want on one contract
Shops running Power alongside x86, storage, and network gear from several vendors often consolidate all of it under one TPM agreement. The single support desk is worth real money in operational time, separate from the discount.
When Third-Party Maintenance Is a Trap
Use caution
The machine is still in standard support
Leaving IBM on a Power10 or Power11 under warranty or standard maintenance switches off a firmware and security fix stream that is actively being produced. The discount is real and so is the exposure. On production workloads this rarely pencils out.
Use caution
An OS upgrade with a firmware floor is on the roadmap
If IBM i 7.6 or a newer AIX technology level is in your plan, confirm the minimum system firmware level first. A frozen machine that cannot meet it turns a planned upgrade into an unplanned IBM contract.
Use caution
It becomes the strategy instead of the bridge
Year one saves money. Year four is an unsupported, firmware-frozen machine running the general ledger, with parts getting scarcer and an auditor asking questions. A bridge needs a written destination and a written date.
Use caution
Compliance, cyber-insurance, or audit pressure
Underwriters and auditors increasingly ask directly whether infrastructure is vendor-supported and receiving security fixes. A TPM contract answers the first half of that question and not the second. Find out how your assessors score it before you sign, not during renewal.
The Four Support Options Compared
Ranges below are directional and drawn from published third-party figures and typical quotes. Pricing on Power maintenance is quote-driven and varies enormously by model, age, coverage window, and geography, so treat these as a way to structure the comparison rather than as a forecast for your machine.
| Option | Typical cost | Who does the repair | Firmware and machine code | Best used for |
|---|---|---|---|---|
| IBM standard hardware maintenance (HWMA) | IBM list, renewed annually; rises as the machine ages | IBM engineers and IBM parts | Full: new firmware, Licensed Internal Code, and security fixes while the model is in standard support | Machines still inside standard support running production workloads |
| IBM post-support service extension | By quote, generally at a premium to what standard maintenance cost | IBM engineers and IBM parts | None new: IBM has stopped developing machine code for the model; existing fixes only | Shops that want a single-vendor relationship on an end-of-support machine |
| Third-party maintenance (TPM) | Commonly quoted 30 to 40 percent below an IBM renewal, with analysts citing up to 50 to 70 percent off OEM list on older systems | Independent provider's engineers and its own spare parts inventory | None: no third party can legally create, supply, or install IBM Machine Code | End-of-support machines, dated bridges, non-production systems, mixed-vendor estates |
| No hardware contract at all | Zero until a failure, then emergency time-and-materials repair plus parts sourcing | Whoever you can find on the day | None | Isolated, non-critical, or end-of-life machines with tested backups and executive sign-off |
What to Ask Before You Sign
- 1
Where are the spare parts for my exact model?
Ask for the depot location relative to your site and the specific field-replaceable units stocked for your machine type and model, not a general statement about inventory value. Parts proximity is what a response-time commitment actually rests on.
- 2
Who is the engineer, and have they touched Power?
IBM Power and IBM i are not generic x86 skills. Ask how many Power-certified engineers cover your region, whether they are employees or subcontractors, and what happens at 2am on a holiday weekend.
- 3
What is the response time commitment, in writing?
Distinguish response from resolution, confirm the coverage window, and get the remedy for a missed SLA on paper. A cheap contract with a soft SLA is not cheaper than an IBM contract, it is just a different risk.
- 4
Confirm in writing that firmware is out of scope
Any honest provider will say so plainly. If a salesperson implies they can keep your machine code current, that is a reason to walk, because it means either they are wrong or they are planning to do something they are not licensed to do.
- 5
Get the firmware and HMC code current first
Update to the level you want while you still hold IBM hardware entitlement, then document exactly what level every machine and HMC is sitting on. This is the step shops most often skip and most often regret.
- 6
Keep SWMA separate, and confirm it is unaffected
Your IBM i or AIX software maintenance should continue untouched. Verify the renewal is invoiced independently and that your Fix Central entitlement still resolves after the hardware contract moves.
- 7
Ask IBM what it costs to come back
IBM can require an inspection before it will place an off-contract machine back under maintenance, and can charge for it. If TPM is a bridge, price the return trip before you cross.
- 8
Write down the date you revisit the decision
A bridge with no end date is just a slower version of doing nothing. Put the refresh or migration decision on the calendar at the same time you sign the maintenance contract.
Risks and Common Mistakes
Use caution
Comparing a TPM quote to an IBM quote that covers more
Normalize the coverage window, response time, on-site versus depot, and whether HMC support and predictive call-home are included. A price difference that shrinks under scrutiny was never a saving.
Use caution
Assuming TPM keeps you compliant
A supported-hardware answer and a receiving-security-fixes answer are different answers. Ask your auditor and your cyber-insurance broker how they score a firmware-frozen machine before you commit.
Use caution
Letting the discount postpone the real decision
TPM is a legitimate way to buy planning time on a Power9 or older machine. It is not a substitute for deciding between a Power11 refresh, PowerVS, and managed hosting. The discount should fund that decision, not replace it.
Key decision
The real question is what the machine is for
A production ERP system and a reporting LPAR deserve different answers, and a mixed estate can legitimately run IBM maintenance on some machines and TPM on others. Decide workload by workload rather than signing one policy for everything.
Frequently Asked Questions
Is third-party maintenance for IBM Power hardware legal?
Yes. Buying hardware break-fix service from an independent provider instead of IBM is legal and common, and large TPM firms have supported IBM Power, AS/400, iSeries, and AIX systems for decades. What is not legal is a third party creating, supplying, or installing IBM Machine Code or Licensed Internal Code it has no license to distribute. That is an intellectual property boundary, not a service boundary, and any reputable TPM provider will tell you the same thing.
How much does third-party maintenance actually save on IBM Power?
Published figures range widely. Providers commonly cite 30 to 40 percent below an IBM renewal, industry analysts have cited 50 to 70 percent off OEM support list pricing, and the deepest discounts show up on older, fully depreciated machines that IBM prices aggressively at renewal. The honest answer is that the savings depend almost entirely on the age and model of the machine, so get a written IBM renewal quote and at least two TPM quotes for the same coverage window and service level before you assume a number.
If I switch to TPM, do I lose access to firmware and security fixes?
For the hardware, yes. IBM makes Machine Code updates available only for machines under warranty or under an IBM hardware maintenance service agreement. Leave IBM hardware maintenance and the firmware and Licensed Internal Code stream stops. This matters far less on a machine IBM has already declared end of support, because IBM has stopped developing new machine code for it anyway, and far more on a machine still inside its standard support window.
Will I still get IBM i PTFs or AIX service packs on a TPM machine?
Yes, provided you keep IBM Software Maintenance (SWMA). Operating system fixes for IBM i and AIX are delivered through Fix Central under your software maintenance entitlement, which is a separate contract from hardware maintenance (HWMA). Keeping SWMA and moving only hardware break-fix to a TPM provider is the most common arrangement, and it is the one that keeps the OS patched while the firmware freezes.
Can I go back to IBM support later if I change my mind?
Usually, but not automatically and not for free. IBM can require an inspection or recertification of a machine that has been off contract before it will take it back under a maintenance agreement, and it can charge for the inspection and for the lapsed coverage period. Ask for the re-entry terms in writing before you leave, especially if TPM is meant to be a short bridge rather than a permanent decision.
Does third-party maintenance make sense on a Power9 after January 2026?
This is TPM's strongest case. Power9 scale-out models left IBM standard support on January 31, 2026, so IBM is no longer developing new machine code for them. The firmware argument that normally counts against TPM largely disappears, and what remains is a straight comparison of parts, engineers, and response times at a lower price. The caveat is unchanged: a maintenance contract keeps hardware repairable, it does not give the platform a future.
What is the difference between IBM's service extension and third-party maintenance?
IBM's post-end-of-support hardware service extension is IBM continuing to repair the machine, priced by quote and generally at a premium to what standard maintenance cost. Third-party maintenance is an independent firm doing the repair work using its own engineers and spare parts inventory, typically at a lower price. Neither one produces new firmware for an end-of-support machine. The practical differences are price, parts sourcing, engineer availability in your geography, and whether you value the single-vendor relationship.
Sources
- IBM planning notice: Upcoming Changes to Power9 Maintenance Services (September 2024)
- IBM Support: Machine Code and licensed internal code terms
- IBM Fix Central (software fixes require an active software maintenance entitlement)
- Park Place Technologies: What is third-party maintenance
- Curvature: Evaluating server maintenance options for IBM Power Systems
- Verify contract scope, response times, and re-entry terms in writing with IBM and each provider
Related pages
- Power9 End of Support Has Arrived: Your 4 Options in 2026
- AIX End of Life: The Real 7.2 and 7.3 Support Timeline
- IBM i 7.4 End of Support: Upgrade to 7.5, 7.6, or the Service Extension?
- Power Hardware Refresh vs. Moving to Cloud
- Power10 vs. Power11 for IBM i Shops in 2026
- IBM Power Virtual Server (PowerVS)
Weighing a Maintenance Renewal Against a Refresh?
Get an independent read on whether third-party maintenance buys you useful time on your machines, or just postpones a decision you would be better off making now.