① Product · Broadcom (CA) MICS
MICS Resource Management is Broadcom (CA) performance data management, the warehouse that turns SMF data into capacity and chargeback reporting. It is licensed on system capacity in MIPS or MSU and moving toward consumption, so the lever is the capacity baseline and the component set, not the size of the data store.
MICS Resource Management is Broadcom (CA) performance and capacity data management software. It collects SMF and other system instrumentation data, organizes it into a structured warehouse, and turns it into the performance analysis, capacity planning, and chargeback reporting that operations and capacity teams rely on. It is one of the long standing data warehouses on the platform, deeply wired into reporting and billing processes that have run for years, which makes it both valuable and hard to move. That embedded position shapes how its licensing should be approached.
MICS is licensed on capacity, not on the volume of data its warehouse holds. Historically that has meant a MIPS or MSU based charge tied to the machines or LPARs where the product runs, and Broadcom has been moving its mainframe customers toward Mainframe Consumption Licensing (MCL), which prices on measured MSU consumption reported through SCRT across the production environment. MICS also ships as a base product with optional component units for different data sources, so the entitlement is really a base plus a set of components. Whether your MICS license is a legacy capacity entitlement or sits under a consumption agreement depends on your contract, and the component mix needs to be read alongside the capacity basis.
| Attribute | Detail |
|---|---|
| Publisher | Broadcom (CA) |
| Function | Performance and capacity data warehouse from SMF data |
| Charge model | Capacity license, MIPS or MSU based |
| Structure | Base product plus optional component units |
| Direction | Mainframe Consumption Licensing (MCL), MSU consumption |
The first driver is the licensed capacity baseline, which can drift above current need when it was set before a hardware upgrade and never revisited. The second is the component set, because MICS components for different data sources accumulate over time and some end up entitled but unused. The third is portfolio context, since Broadcom renews its mainframe products together and uplift pressure on the full CA estate flows through to MICS. The MIPS to MSU conversion underlies all three, because a transition done on the vendor's assumptions can quietly raise the licensed position. The size of the warehouse itself is a storage concern, not a license driver.
MICS exposure comes from its component structure and its breadth. Common traps we see at pattern level:
Where exposure hides
MICS responds to the portfolio levers, applied with its component structure in mind. The five that pay:
Buyer side levers
Performance data warehousing has a real alternative market, most notably MXG, the SAS based performance database that many shops run instead of or alongside MICS, plus other capacity and reporting platforms. Displacement is credible leverage, but it is not free: years of historical data, the reports built on the warehouse, and the chargeback and capacity processes that consume them all have to be rebuilt or repointed, and that is a project with its own cost and risk. The practical move is usually to prune unused components and use a credible alternative as a reference point in the Broadcom renewal, reserving a full migration for cases where the long term saving clearly justifies the effort.
Prune the components, validate the capacity, then renew.
Concept explainers: the 18 month renewal runway and what auditors test. Sibling products: OPS/MVS licensing and CA View licensing. Hub and commercial: the Broadcom (CA) buyer side guide and Broadcom (CA) renewal advisory.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.