Does third-party maintenance restore IBM firmware or IBM i support?

No. Third-party maintenance can provide hardware parts and labor. It does not change the machine's IBM i release ceiling or recreate IBM's software support lifecycle.

When does Power6 third-party maintenance make sense?

It can make sense when the server is stable and the business needs time to prepare a replacement. The contract still needs exact hardware coverage, a parts plan, clear response terms and a tested recovery handoff.

How do I compare an IBM service extension with third-party maintenance?

Ask IBM whether an extension is available for the exact machine and location. Then compare the written parts coverage, response commitment, software boundary and end date with the third-party quote.

What should a Power6 TPM quote identify?

It should identify the exact machine type and serial number. It should also name covered parts, response commitments, escalation terms, exclusions, and the recovery handoff.

IBM Power6 Third-Party Maintenance Buying Guide

IBM Power6 third-party maintenance works best when the job is clear: keep known hardware repairable while you prepare the next move. It can cover parts and labor. It does not renew IBM software entitlement, lift the IBM i release ceiling, or replace a recovery plan.

Choose an IBM service extension, third-party maintenance, or migration by the job

Start with the result the business needs

Choice	Best fit	What it can cover	What still needs a plan
IBM Hardware Service Extension	IBM confirms that the exact machine and location are eligible	Remote help, onsite repair, and covered parts under IBM's written terms	Software entitlement, application recovery, and the extension end date
Third-party maintenance	The Power6 server is stable and the business needs a controlled bridge	Parts, remote diagnosis, and onsite labor named in the contract	Firmware access, IBM i support, backups, and workload recovery
Migration	Old hardware limits support, growth, or recovery confidence	A move to a newer support and hardware lifecycle	Application fit, data transfer, testing, downtime, and rollback

IBM may offer a Hardware Service Extension after standard support ends, but availability depends on the product and location. Ask IBM for the exact terms. Then compare that written answer with the third-party contract rather than comparing brand names.

The five questions a Power6 TPM contract must answer

1. Which machine is covered?

The contract should identify the server and the site where it runs. Include the machine type, serial number, and every attached drawer.

2. Which parts are covered?

List the assemblies included in coverage. Confirm stock for power and cooling failures. Check storage, processor, memory, and I/O separately.

3. What response is promised?

The agreement should separate telephone response, remote diagnosis, parts arrival, and on-site labor. One response number does not answer all four.

4. What is excluded?

Hardware-only coverage may exclude firmware and the operating system. Application recovery, backups, and data restoration may also sit outside the agreement.

5. Who owns the recovery handoff?

The contract should say where hardware repair ends and operating-system or application recovery begins. That gap is where an outage can stall.

Strong contract language versus vague promises

Read the promise as if the server were already down

Contract item	Useful detail	Weak wording
Covered equipment	Machine type, serial number, site, and attached drawers	IBM Power systems
Parts	Named assemblies or a written all-parts definition	Parts subject to availability
Response	Separate times for diagnosis, shipment, and on-site arrival	Four-hour response
Escalation	Named contact route and an after-hours process	Priority support
Recovery	Written boundary between hardware repair and workload restoration	Customer responsibility

Build the Power6 quote worksheet before comparing prices

System list

Record the machine type, serial number, location, attached drawers, and storage before requesting a quote.

Coverage line

Mark each covered assembly. Do not treat all-parts coverage as clear until the contract defines what all parts means.

Response clock

Write down the promised time for telephone response, diagnosis, parts arrival, and onsite labor.

Parts plan

Ask where critical parts are stocked and what happens when the needed assembly is not in local inventory.

Escalation owner

Name the person or team that owns an after-hours escalation when the normal process stalls.

Recovery boundary

State who returns IBM i, applications, interfaces, and data to service after the hardware repair.

Decision date

Set the renewal date and the migration decision date now. A bridge without an end date can quietly become the plan.

What Power6 TPM cannot change

Third-party maintenance can keep physical hardware covered after IBM service ends. It cannot make Power6 support a newer IBM i release. It also cannot promise IBM will create a new firmware or software fix for this generation.

That does not make third-party maintenance a bad decision. It makes the contract a bridge with a defined job: keep the hardware repairable while the business maintains a tested recovery plan and a dated replacement decision.

Turn the Power6 contract into a dated decision

Run the TPM risk checker with the quote in front of you. Compare the result with the end-of-support timeline and the current vendor directory. The goal is not the cheapest monthly line. It is knowing who fixes the hardware, who restores the workload, and when the business will move.

Check the TPM Contract Review Power6 TPM Vendors Review the Power6 Timeline

IBM Power6 Third-Party Maintenance: When It Works and What the Contract Must Cover