① Product · IBM OMEGAMON
IBM OMEGAMON is an IPLA family priced in Value Units against your MSU tier, with an annual Subscription and Support stream that runs forever once you own the licenses. It is not billed on the Rolling 4-Hour Average like CICS or Db2, and unlike core runtimes it has credible competitors, which makes it one of the few IBM products where displacement is a real lever.
OMEGAMON is IBM's long running performance and availability monitoring family for the IBM Z platform. Separate agents watch the operating system, networks, storage, and the major middleware: CICS, IMS, Db2 for z/OS, MQ, and Java runtimes. In current packaging it is sold inside the IBM Z Monitoring Suite and the IBM Z OMEGAMON AI line. For most estates it is the primary lens operators use to see consumption, which is the same consumption that sets the bill on every MLC product, so OMEGAMON sits close to the money even though it is not billed the same way.
OMEGAMON is an International Program License Agreement (IPLA) product, not a Monthly License Charge product. You buy a one time charge license sized in Value Units, where the Value Unit position is derived from your MSU capacity tier through the Value Unit Exhibit, and you then pay an annual Subscription and Support charge on the perpetual licenses. On qualifying machines OMEGAMON is eligible for sub-capacity Value Unit pricing, so the position can be set against measured capacity rather than full machine capacity. The recurring cost is the annual S&S, and that stream, not a monthly peak, is what you negotiate.
| Attribute | Detail |
|---|---|
| Charge model | IPLA one time charge plus annual S&S |
| Metric | Value Units, set by MSU capacity tier |
| Sub-capacity | Eligible on qualifying machines |
| Recurring cost | Annual Subscription and Support |
| Packaging | Point agents or IBM Z Monitoring Suite |
IPLA and MLC are two separate cost streams on the same machine. OMEGAMON sits in the IPLA stream alongside products like the CICS Tools, which is why it is modeled apart from the R4HA driven MLC bill. See the IPLA one time charge model.
The first driver is the Value Unit band, which moves with your MSU capacity tier: a machine upgrade can lift the OMEGAMON position even though no new agents were deployed. The second is breadth, the number of monitored subsystems and agents you license, since each middleware monitor (CICS, IMS, Db2, MQ) is its own entitlement. The third is whether you are positioned full capacity or sub-capacity, which on a large machine is a material difference. The fourth is suite versus point product packaging: a bundle can be cheaper at list but commonly carries monitors you do not use, and the annual S&S compounds on the whole bundle year after year.
Monitoring agents spread quietly, and the spread is where exposure builds. Common traps we see at pattern level:
Where exposure hides
Because OMEGAMON has credible competition and a separable cost stream, the levers are real. The five that pay:
Buyer side levers
Unlike a core runtime, OMEGAMON has genuine substitutes. BMC MainView and Broadcom SYSVIEW are mature monitoring platforms that cover much of the same ground, and either can anchor a credible competitive evaluation. The cost of switching is not zero: dashboards, automation hooks, runbooks, and operator familiarity all carry over poorly, so a full displacement is a project, not a renewal tactic. The practical play is to price the alternative honestly and let that number set the ceiling on what you will pay to stay, which is leverage you do not have on products with no substitute.
Two streams, two negotiations.
Metric explainers: the IPLA one time charge model that OMEGAMON sits in, the MIPS to MSU conversion question, and sysplex vs standalone pricing. Sibling products: CICS Transaction Server licensing and Linux on IBM Z licensing. Hub and commercial: the IBM buyer side guide and IBM renewal advisory.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.