① Syncsort (Precisely) · Renewal advisory
A Syncsort (Precisely) MFX renewal commonly moves on capacity the sort workload never asked for. We baseline what you actually consume, price the ZPSaver offload, and build the alternative that resets the number.
The sort did not get bigger. The renewal did.
Syncsort MFX, now part of the Precisely portfolio, has been one of the most widely installed third party products on the mainframe for decades, valued as a faster alternative to IBM DFSORT. It is commonly licensed on a machine capacity basis, sized to the MSU or MIPS rating of the systems it runs on. ZPSaver, a separately licensable MFX feature, offloads sort, copy, and SMS compression work to zIIP processors, which lowers the general purpose MSU that the rest of your software is billed on.
The capacity basis is exactly where a renewal can drift away from reality. When a hardware refresh or organic growth lifts machine capacity, the MFX entitlement tier can move with it even though the volume of data being sorted is unchanged. Add an uplift applied to the prior contract value without reference to actual consumption, and the renewal number rises for reasons that have nothing to do with the work the product does.
None of this is unique to Precisely; it is the standard shape of capacity based mainframe licensing. The buyer side job is to separate the part of the renewal that reflects real consumption from the part that reflects capacity the sort never used, and to make sure the value of ZPSaver offload is counted on your side of the ledger, not just the vendor's.
The MFX entitlement is matched to the machines it actually runs on and the capacity those machines actually use. Any tier that was set by a hardware refresh rather than by sort workload is flagged as recoverable at renewal.
The MSU that ZPSaver moves to zIIP is measured and valued, because that offload reduces the general purpose capacity other software is billed on. The renewal is weighed with that downstream saving in view, not as an isolated line item.
DFSORT ships with z/OS, so a baseline sort capability is already entitled. We document and cost what an MFX exit would actually require, feature by feature, so the alternative is credible whether or not you ever use it.
Features and add ons that are licensed but not used are identified and removed from the renewal base, so you are not paying forward for capability the estate retired years ago.
The renewal is locked with a capacity cap, uplift limits, and consumption protections, so the next hardware refresh does not quietly reset the baseline against you all over again.
20 to 35% off the opening number. From data, not from asking.
With a corrected capacity baseline, measured ZPSaver economics, and a costed DFSORT alternative on the table, the renewal stops being a take it or leave it uplift and becomes a negotiation with evidence. Across our engagements, buyer side preparation commonly delivers a 20 to 35 percent reduction against the vendor's opening position, built from baseline correction and scope right sizing rather than a single headline discount.
For the product itself, see the MFX licensing page. To go deeper on the publisher, start at the Syncsort (Precisely) hub. For the underlying mechanics, the MIPS explainer covers why capacity ratings move the bill, and our renewal advisory service covers the discipline end to end.
On a machine capacity basis, sized to the MSU or MIPS rating of the systems it runs on, with ZPSaver as a separately licensable zIIP offload feature. Because entitlement tracks capacity, a refresh can move the number even when the sort workload is unchanged.
Capacity growth that lifts the licensed tier, a hardware refresh that resets the baseline, and uplift applied to the prior value without reference to actual consumption. ZPSaver offload cuts the other way by lowering billable general purpose MSU.
IBM DFSORT ships with z/OS, so a baseline sort capability is already entitled. Whether it substitutes depends on the MFX features and ZPSaver offload in use. A documented, costed alternative changes the conversation even when the decision is to stay.
12 to 18 months out. Capacity baselines, offload measurement, and alternative evaluation take time, and the leverage they create only exists if it is ready before the vendor controls the clock.
Buyer side preparation commonly delivers a 20 to 35 percent reduction against the opening position, through baseline correction, scope right sizing, and credible alternative leverage rather than a single discount.