Is TFP Software or TFP Hardware the better choice?

It is not an either or choice. The Software Consumption Solution, formerly the Enterprise Consumption Solution, is a software licensing model that replaces the rolling four hour average with cloud like, consumption based pricing for your IBM z/OS software stack. The Hardware Consumption Solution is a separate, usage based corridor of pay for use processor capacity that sits on top of purchased hardware to absorb short, unplanned spikes. IBM typically makes the Hardware Consumption Solution available only to customers who already run a Software Consumption Solution on z15 or later general purpose processors. So the real question is not which one, it is whether to add the hardware corridor once you are on the software model. Treat them as a base and an option, not as rivals.

Does the Hardware Consumption Solution require the Software Consumption Solution?

In the patterns we commonly observe, yes. IBM positions the Hardware Consumption Solution as an add on available to customers with z15 or later, z/OS general purpose processors, and an existing Software Consumption Solution. The hardware corridor gives you an always on, subscription based band of additional capacity you pay for only as you use it, which is most useful where workload peaks are short, sharp, and hard to forecast. Because it presumes you are already on the software consumption model, the sequence matters: model and negotiate the Software Consumption Solution first, then decide whether the hardware corridor earns its place. Confirm the current prerequisites with IBM against your own machine generation before you plan.

When does the Hardware Consumption Solution actually pay off?

When your peaks are genuinely unpredictable and expensive to provision for in purchased capacity. If your estate runs close to its installed capacity only during rare, short spikes, a month end batch surge, a seasonal trading peak, an unplanned recovery event, then a pay for use corridor can be cheaper than buying and carrying hardware you use a few hours a year. If your peaks are predictable and sustained, buying the capacity outright is usually the better economic answer, and the corridor adds a recurring subscription you do not need. The discipline is to look at the shape of your demand curve over a full cycle before you opt in, not the marketing framing. We model the corridor against your own SCRT and capacity data so the decision rests on your numbers.

TFP Software vs TFP Hardware Consumption

TFP Software vs TFP Hardware: a base and an option, not a choice.

IBM Tailored Fit Pricing for IBM Z comes in distinct solutions. The Software Consumption Solution, formerly the Enterprise Consumption Solution, is how your z/OS software is licensed. The Hardware Consumption Solution is a pay for use corridor of processor capacity that sits on top of it. They are not rivals. The Hardware Consumption Solution typically presumes you already run the software model. Here is what each prices, and when to add the second.

Stop framing this as a versus. The Software Consumption Solution is the foundation: it replaces the rolling four hour average and prices your z/OS software on consumption. The Hardware Consumption Solution is an add on, an always on, pay for use corridor of processor capacity for short, unplanned spikes, and IBM typically offers it only to customers already on the software model with z15 or later general purpose processors. So the sequence is fixed. Model and negotiate the Software Consumption Solution first, on its own merits. Then, separately, decide whether your demand curve is spiky enough that a metered hardware corridor beats buying the capacity outright. For most estates the answer to the first question is the strategic one; the corridor is a narrower, situational call.

Software Consumption Solution vs Hardware Consumption Solution
Dimension	Software Consumption Solution	Hardware Consumption Solution
What it prices	z/OS software licensing	Additional processor capacity
Former name	Enterprise Consumption Solution	Introduced as a hardware solution, no prior name
Replaces	The rolling four hour average and sub capacity capping	Nothing; it adds a corridor on top of purchased capacity
Model	Cloud like, consumption based software charge	Always on, subscription based, pay for use capacity band
Best for	Estates wanting predictable software cost without capping drag	Estates with short, unpredictable demand spikes
Typical prerequisite	A Tailored Fit Pricing agreement with IBM	z15 or later, z/OS GP processors, and a Software Consumption Solution
Relationship	The base model	An option layered on the base

Software Consumption Solution vs Hardware Consumption Solution

Dimension

Software Consumption Solution

Hardware Consumption Solution

What it prices

z/OS software licensing

Additional processor capacity

Former name

Enterprise Consumption Solution

Introduced as a hardware solution, no prior name

Replaces

The rolling four hour average and sub capacity capping

Nothing; it adds a corridor on top of purchased capacity

Model

Cloud like, consumption based software charge

Always on, subscription based, pay for use capacity band

Best for

Estates wanting predictable software cost without capping drag

Estates with short, unpredictable demand spikes

Typical prerequisite

A Tailored Fit Pricing agreement with IBM

z15 or later, z/OS GP processors, and a Software Consumption Solution

Relationship

The base model

An option layered on the base

Because one sits on the other, the decision is really two decisions taken in order:

Move to the Software Consumption Solution if

Sub capacity capping is constraining responsiveness or putting service levels at risk during peaks
You want software cost that tracks consumption rather than a four hour average you spend effort gaming
You can model a full year of SCRT data and show the consumption baseline lands in your favor, not IBM's

Add the Hardware Consumption Solution if

You already run the software model on z15 or later general purpose processors
Your peaks are short, sharp, and genuinely hard to forecast, so buying capacity for them wastes money most of the year
The metered corridor, priced over a full demand cycle, beats the carrying cost of purchased capacity you would use only a few hours a year

If your peaks are predictable and sustained, buy the capacity and skip the corridor; the subscription only adds recurring cost. The trap is letting the entry into Tailored Fit Pricing become a moment where IBM sets a generous consumption baseline and bundles the hardware corridor before you have modeled either. Sequence it: software model first, on your numbers, then the corridor as a separate, evidenced call.

Which is better?Neither, because they are not rivals. The Software Consumption Solution prices software; the Hardware Consumption Solution adds a capacity corridor on top. Choose the software model first, then decide on the corridor.

Does hardware require software?Typically yes. IBM offers the Hardware Consumption Solution to customers with z15 or later, z/OS GP processors, and an existing Software Consumption Solution.

When does the corridor pay off?When peaks are short and unpredictable enough that metered capacity beats buying and carrying hardware you rarely use. Predictable, sustained peaks favor purchased capacity.

What is the first move?Model a full year of SCRT and capacity data before entering either, so the consumption baseline and the corridor decision rest on your numbers, not IBM's framing.

One model prices the software. The other meters the metal. Sequence beats either.

Explainers: Tailored Fit Pricing and the hardware consumption solution and hardware refresh and software cost, the z16 to z17 question. Related comparison: Tailored Fit Pricing vs sub capacity. Hub: the IBM buyer side guide. Commercial: mainframe cost optimization and mainframe license negotiation.

TFP Software vs TFP Hardware: a base and an option, not a choice.

The verdict

Head to head

Who should pick which

Frequently asked

Entering Tailored Fit Pricing? Set the baseline before IBM does.