① Product · BMC AMI Data for IMS
BMC AMI Data for IMS is the IMS database and system management suite under BMC's Automated Mainframe Intelligence brand. It is licensed on MSU capacity and packaged as an integrated bundle, so the renewal turns on the suite envelope, the MSU it sits on, and any MIPS to MSU restatement BMC applies.
BMC AMI Data for IMS is BMC's suite for managing IMS databases and systems on z/OS. It brings together change management, full function and HALDB database management, administration, recovery, and performance tooling under the Automated Mainframe Intelligence (AMI) brand, with automation and analytics layered in. For organizations running IMS in production, it is the operational toolset that keeps the databases available, recoverable, and tuned, which makes it core to the IMS estate and a recurring line in the BMC relationship.
AMI Data for IMS is licensed on capacity measured in MSU. BMC commonly prices its mainframe products per MSU under a consumption oriented model, and where older entitlements were written in MIPS, BMC has converted them to an MSU basis using a ratio stated in the order, reflecting the machines in use at the time. The tools are typically taken as an integrated suite rather than as wholly separate products, so the MSU basis applies across the components in the bundle. The capacity figure and the suite envelope are set in your agreement.
| Attribute | Detail |
|---|---|
| Charge model | Capacity license, consumption oriented |
| Metric | MSU of the licensed environment |
| Legacy basis | MIPS converted to MSU by stated ratio |
| Packaging | Integrated AMI suite, not single tools |
| Billed on | Licensed MSU, not IMS transaction volume |
The MIPS to MSU restatement is where BMC capacity contracts move. See the MIPS to MSU conversion question before accepting a rebased renewal.
The primary driver is the licensed MSU, since the bill scales with the capacity of the environment regardless of how hard the IMS tools are exercised. The second is suite scope: a bundle can fold in components you do not actively use, and the per MSU charge then applies across the whole envelope, so shelfware inside the suite is paid for on every MSU. The third is the capacity restatement, because a MIPS to MSU conversion or a capacity rebasing at renewal sets the baseline the suite is priced on for years, and accepting it without modeling can lift spend.
Capacity and suite scope are where exposure builds. Common traps we see at pattern level:
Where exposure hides
The levers work on MSU, on suite scope, and on the competitive option. The five that pay:
Buyer side levers
The IMS tools category is contestable. IBM fields its own IMS Tools covering database management, recovery, and performance, so a competitive evaluation against BMC is realistic leverage rather than a bluff. Switching means migrating utilities, batch jobs, and operational procedures, which is a project with real effort, so a full displacement is not a mid term flip. The effective play is to keep the IBM alternative priced and credible, use it to set the ceiling on the BMC suite renewal, and reserve an actual migration for when the economics or the relationship justify it.
MSU, suite scope, and a credible alternative.
Metric explainers: the MIPS to MSU conversion question and what audit clauses allow. Related reading: BMC renewal negotiation strategy and the BMC vs Broadcom portfolio decision. Hub and commercial: the BMC buyer side guide and negotiating BMC AMI suite bundles.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.