① Journal · Cost Optimization
Development, test, QA, training, and disaster recovery do not run the business, and publishers commonly price them lower than production for exactly that reason. Yet most estates license non production capacity at the full production rate by default and never go back to separate it. The discount is sitting there. Here is how to claim it.
The discount is real. The reason it goes unclaimed is inertia, not eligibility.
A production LPAR runs the business and is priced accordingly. A development LPAR compiles code, a test LPAR runs regression, a training LPAR teaches operators, and a disaster recovery LPAR sits cold until it is needed. None of these run the business in the way production does, and publishers commonly recognize that with reduced rate vehicles, because they would rather keep the workload on the platform at a lower rate than lose it to a cheaper alternative environment. On IBM that includes reduced pricing of the z New Application License Charge family for qualifying new and non production workloads, and the z/OS Development and Test Environment (zD&T), which runs z/OS on x86 hardware specifically for development and test. Independent software vendors frequently offer separate dev and test pricing or environment based discounts on their own products too.
So why is the discount so widely unclaimed? Because non production capacity gets folded into one number at signing and nobody separates it afterward. Dev, test, QA, training, and disaster recovery LPARs are licensed at the production rate by default, the reduced rate vehicles are never applied, and the overpayment repeats every renewal. Claiming the discount is not exotic. It is an inventory of workloads by environment, a match of each environment to the right vehicle, and clean separation so the reduced rate holds at audit. The buyers who do this routinely find a meaningful slice of the estate was eligible all along. Read this with our explainer on soft capping and defined capacity and the cost optimization service.
Environments and the reduced rate vehicle · what we commonly observe
| Environment | Typical default | Where the discount lives |
|---|---|---|
| Development | Production rate capacity | Reduced rate new application vehicles, zD&T on x86 for IBM stack |
| Test and QA | Production rate capacity | ISV dev and test pricing, environment based discounts, separate LPAR licensing |
| Training | Folded into production | Non production designation, capped capacity, reduced rate where offered |
| Disaster recovery | Often fully licensed | Cold or warm DR provisions, reduced or zero charge until invoked |
| Sandbox and POC | Unlicensed or production rate | Time boxed trial terms, evaluation licensing, sub-capacity isolation |
These are patterns we commonly observe, not guaranteed entitlements. Eligibility, definitions, and rates vary by publisher and contract; confirm the contractual definition of non production and the specific vehicle terms before relying on any rate.
You cannot claim a non production rate on capacity you have not separated. Map every LPAR and every product to its environment, production, development, test, QA, training, disaster recovery, and quantify the MSU or capacity each consumes. The inventory is the evidence. It tells you how much of the estate is eligible and gives you the document that holds the reduced rate at audit.
Separate the environments before you price them.
Every reduced rate vehicle has eligibility rules, and the saving comes from matching the environment to the right one rather than applying a blanket discount. Reduced rate new application vehicles, zD&T for IBM development and test, ISV dev and test pricing, and disaster recovery provisions each fit different workloads. Match them deliberately and the discount is defensible. Apply them loosely and the audit unwinds it.
Right vehicle per environment, not a blanket discount.
The single trap that voids a dev test discount is production work running on capacity licensed at the reduced rate. Publishers commonly define non production narrowly, and one production transaction touching a discounted environment can trigger a true up. Keep environments cleanly separated, document what runs where, and audit your own boundary before the vendor does. See our note on the renewal that became an audit.
The discount holds only while the boundary holds.
④ Why the discount goes unclaimed
Non production does not run the business. Most estates pay as if it does. Inventory by environment, match the vehicle, hold the boundary.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Because those workloads do not run the business and the publisher would rather keep them on the platform than lose them. IBM options include reduced rate new application vehicles and the z/OS Development and Test Environment (zD&T) on x86 hardware. ISVs frequently offer separate dev and test pricing on their own products too.
Because non production capacity is licensed at the production rate by default and nobody goes back to separate it. Dev, test, QA, training, and disaster recovery get folded into one number, the reduced rate vehicles never get applied, and the overpayment repeats every renewal. See negotiating dev test discounts.
Running production work on capacity licensed at the reduced non production rate. Publishers commonly define non production narrowly, and any production transaction touching a discounted environment can void the discount and trigger a true up. Keep environments separated, document what runs where, and confirm the contractual definition before relying on the rate.
It depends on how much of the estate is non production and how it is currently licensed, but the eligible slice is frequently larger than buyers expect once environments are separated. Our cost optimization service inventories the estate by environment and our license negotiation service applies the right vehicle at renewal.
Related: negotiating dev test discounts · soft capping explained · MSU optimization quick wins · cost optimization · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →