Broadcom SAM. VMware, Symantec, and CA in one frame.

Broadcom now sells VMware cores, Symantec endpoints, and CA mainframe capacity under one commercial culture, and one SAM framework has to track all three meters or the renewals will.

What does effective SAM cover across the Broadcom portfolio?

Effective Broadcom SAM maintains a measured baseline for each franchise meter: VMware per core subscriptions, Symantec endpoint and user counts, and CA mainframe and distributed capacity. The portfolio is laid out on the Broadcom products page.

Why can one SAM function not just track spend?

Spend tracking shows what you pay, not what you owe or own. Only measured deployment against documented entitlement supports a renewal counterposition or an audit defense.

How do you rebuild entitlement records after the acquisitions?

Start from contracts, not invoices. Symantec and CA agreements predate Broadcom ownership, and the entitlement chain runs through ordering documents, amendments, and assignment notices across entities.

1. Collect ordering documents, amendments, and renewal confirmations for each franchise.
2. Map each entitlement to current legal entities, including divested and acquired units.
3. Reconcile support renewals against the entitlements they claim to renew.
4. Store everything in one repository with named ownership.

Where records are missing, the Broadcom support portal holds the contract and site ID data that anchors a reconstruction. Request it before a renewal cycle, not during one.

How do you negotiate a Broadcom renewal from a SAM position?

Negotiate from your measured baseline, franchise by franchise, before letting Broadcom bundle the conversation. Bundling benefits whoever has the better data, and that should be you.

• VMware: recount cores against live hosts, price VVF against VCF, and protect exit tooling.
• Symantec: reconcile endpoint counts against the management console, not procurement history.
• CA: bring current SCRT capacity data for the mainframe portfolio and a credible workload migration story.

Should you co term the three franchises?

Co term only when your position is strong in all three at once. Staggered dates preserve annual leverage moments. Aligned dates concentrate risk and reward into one negotiation.

What does the ongoing SAM operating rhythm look like?

Quarterly measurement, annual deep reconciliation, and a renewal runway that starts 12 months out. Broadcom's commercial motion is renewal driven, so the SAM calendar is the defense calendar.

• Quarterly: refresh core, endpoint, and MSU measurements against the baseline.
• Annually: full entitlement reconciliation and shelfware review per franchise.
• At 12 months out: open the renewal file with measured data and target outcomes.

Who owns the Broadcom SAM file?

One named owner across all three franchises, reporting into vendor management. Splitting VMware, Symantec, and CA across teams recreates the data gaps Broadcom negotiates against.

Where the common advice on Broadcom SAM is wrong

The standard advice treats Broadcom SAM as three separate vendor files inherited from three separate vendors, each managed by whoever historically owned the relationship. We disagree. In roughly 15 of the 25 plus Broadcom estates we reviewed, the fragmented model meant nobody saw the portfolio leverage Broadcom applied at renewal, and concessions in one franchise were paid for with silence in another. The buyer side move is one Broadcom file, one owner, three measured meters, and a deliberate choice about which renewal dates align. Broadcom negotiates the portfolio. A buyer who negotiates products will lose the portfolio math every time.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Name a single owner for the consolidated Broadcom SAM file.
2. Build the entitlement repository across VMware, Symantec, and CA contracts.
3. Measure all three meters: core topology, endpoint counts, and SCRT capacity.
4. Reconcile measured deployment against entitlement and flag every gap.
5. Map renewal dates and decide deliberately on co terming or staggering.
6. Open the next renewal file 12 months out with targets per franchise.

White Paper · Broadcom / VMware

Symantec Enterprise Licensing Guide

Read it free.

Read the white paper

Frequently asked questions

What changed in SAM terms when Broadcom acquired VMware?

VMware moved to per core subscriptions with a 16 core minimum per CPU, sold in bundles, and Broadcom's renewal driven commercial motion replaced the old transactional model. Core topology evidence became the central SAM artifact.

How is Symantec licensed under Broadcom?

Primarily per endpoint or per user, depending on product line. The reliable baseline comes from endpoint management console exports reconciled against entitlements, not from procurement purchase history.

What is the CA licensing meter?

CA mainframe products bill mainly against MSU capacity, evidenced by SCRT reports, alongside named distributed products. Capacity data and a credible workload migration story are the negotiation levers.

Does Broadcom run formal license audits?

Broadcom's compliance pressure arrives mostly through renewals rather than standalone audit letters. The renewal preparation is the audit defense: measured meters, documented entitlements, and gaps closed in advance.

Should we negotiate Broadcom franchises together or separately?

Negotiate from franchise level baselines first, and only accept portfolio bundling when your data position is strong across all three. Co terming concentrates leverage into one event, which cuts both ways.

How long does entitlement reconstruction take?

In our 2024 to 2025 reviews, rebuilding proof for pre acquisition Symantec and CA contracts took 4 to 10 weeks where no repository existed. Doing it outside a renewal window is dramatically cheaper than inside one.