Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Broadcom’s reported post-acquisition strategy was to simplify the systems and data definitions behind its analytics—not just add dashboards to a sprawling collection of legacy applications. After acquiring VMware, the company says it consolidated ERP systems, sharply reduced product SKUs, established common data structures, and standardized analytics on Incorta across 26 business units. The case offers a useful lesson for large organizations: a shared analytics platform works best when the underlying operations and definitions are made coherent first.
Why Broadcom faced an integration problem
Acquisitions bring more than new customers and revenue. They can also bring separate applications, enterprise resource planning (ERP) systems, product catalogs, reporting practices, and definitions of basic business entities such as customers, suppliers, contracts, and orders. Two business units may use the same word for different things—or different words for the same thing. Analytics built across those systems can then require extensive mappings and reconciliation before a report is trustworthy.
The scale described after Broadcom’s acquisition of VMware illustrates the challenge. In a March 2025 VentureBeat interview, Broadcom CIO Alan Davidson described VMware as having roughly 1,800 applications, seven ERP systems, and 187,000 product SKUs. These are figures reported in the interview, not independently audited counts. Broadcom’s reported response was to consolidate rather than preserve every system and reconcile all of them indefinitely.
Free tools Windows power users keep installed
One-click scans. No signup required.
Davidson said the VMware environment was brought to one ERP platform and about 500 SKUs. The precise scope and definition of a SKU are not detailed in the interview, so the numbers should be understood as reported measures of rationalization—not proof that every product variant or technical distinction disappeared.
#1 Best Overall
The strategy: simplify before scaling analytics
A common response to acquisition complexity is to keep most existing systems, copy their data into a warehouse or lake, and reconcile differences through extraction, transformation, mapping tables, and separate reporting layers. That can preserve local autonomy and avoid immediate migrations, but it also creates a durable integration burden: every new report may depend on understanding which systems and definitions to trust.
Broadcom’s reported approach put more emphasis on reducing that burden at its source. It can be understood as four connected decisions:
- Reduce application duplication. Retire or consolidate applications that no longer need to operate independently. Davidson described aggressive application deprecation; the interview does not establish that every VMware application across every domain was eliminated.
- Consolidate ERP. The reported reduction from seven VMware ERP systems to one was intended to reduce the number of operational sources that must be reconciled.
- Rationalize product records. Reducing the reported SKU count from 187,000 to around 500 makes product definitions more manageable, but requires decisions about which offerings, bundles, editions, and exceptions remain distinct.
- Standardize master data and business relationships. Common structures for entities such as products, customers, suppliers, procurement, and contracts help connect commercial activity to orders, fulfillment, provisioning, entitlements, and usage.
The final step is analytics standardization: provide a common platform and governed data model through which teams can work with the resulting information. The platform supports the program; it does not itself decide which applications to retire, which products to merge, or what a business metric means.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Why standardize on one analytics platform?
According to the VentureBeat interview, Broadcom uses Incorta across 26 business units, with more than 17,000 internal users and over 200 TB of operational data in the described environment. Those figures are reported by the interview and should not be read as independently audited measurements.
A common platform can reduce duplicated analytical logic and give teams a more consistent way to explore data across functions. It can also make cross-business-unit reporting easier, limit the number of competing interfaces, and help business users answer questions without waiting for every report to be built by a central IT team. This matters when a useful analysis needs to follow a transaction across systems—for example, from a contract or order through fulfillment and provisioning to an entitlement or observed usage.
“One platform” does not mean every employee gets unrestricted access to every record or that every unit must use identical dashboards. Davidson emphasized the need to connect disparate data while segmenting access. A shared environment needs controls that reflect business-unit boundaries, role requirements, and sensitive commercial information. The available sources do not specify whether Broadcom uses one tenant, a shared instance with separate domains, or another deployment arrangement across the 26 units.
Incorta’s role—and what its product claims mean
Incorta describes its platform as using Direct Data Mapping to connect detailed data from source systems, add business context through a semantic layer, and support governed analytics. Its platform materials also describe capabilities such as role-based security, lineage, and audit trails. These are vendor descriptions of its technology, not an independent technical audit of Broadcom’s implementation.
Recommended Free Tools
Incorta is the analytics layer in the reported story; it should not be credited with Broadcom’s ERP consolidation or SKU rationalization. Nor do the public accounts supply a complete map of Broadcom’s data architecture. They do not establish that Broadcom eliminated all warehouses, all ETL, or every other integration technology.
Rank #3
Incorta’s Broadcom case study describes a particular use case drawing on sources including Workday, Oracle, Model N, Oracle Demantra, and Microsoft Excel. That example helps show the sort of cross-system analysis the platform is intended to support, but it should not be confused with a full inventory of the later 26-business-unit deployment.
What results have been reported?
The available figures come from different sources and appear to describe different scopes or periods. They should not be combined into a single audited performance record:
- Scale in the 2025 interview: 26 business units, more than 17,000 internal users, and over 200 TB of operational data, alongside the reported VMware ERP and SKU reductions. See VentureBeat’s interview.
- Incorta’s broader customer-marketing claims: the company advertises approximately 500,000 daily queries with response times under one minute for Broadcom. These are vendor-published figures; the public material does not fully explain the measurement period, workload, or methodology. See Incorta’s site and its Broadcom success-story PDF.
- A specific case-study example: Incorta’s Broadcom case study reports a 50% reduction in inventory waste and describes report creation that previously took 8–12 weeks becoming effectively immediate through self-service. It also cites access to 100 billion records in minutes. These are vendor claims tied to a particular use case or case-study context, not necessarily enterprise-wide outcomes for every unit.
The public accounts do not provide implementation cost, migration duration, payback period, staffing, adoption rates, error rates before and after, or a full account of migration incidents. The scale figures show ambition and reported usage, but are not enough on their own to calculate Broadcom’s return on investment.
Self-service analytics still needs rules
Putting analytics in the hands of thousands of users can reduce report-development queues, but self-service without shared definitions can create metric sprawl. Teams may produce conflicting versions of revenue, backlog, inventory, margin, or active entitlement while all believing their numbers are correct.
A workable self-service model therefore needs more than a query interface. It needs:
- Named owners for core data entities and business metrics.
- Common, documented definitions and reusable models for frequently used measures.
- Role-based and, where necessary, row-level or business-unit-level access controls.
- Data-quality checks and a process for handling incomplete, late, or conflicting records.
- Monitoring for platform use and query performance, plus support and training for users.
- A way to resolve disputes when local processes do not fit a shared definition.
The point is not to force every unit into the same analysis. It is to make shared definitions and permissions dependable enough that local exploration does not undermine enterprise reporting or expose data to the wrong audience.
Why data quality comes before AI
Broadcom’s reported data-first emphasis has direct relevance to AI projects. A natural-language interface can make it easier to ask questions of business data, but it cannot make inconsistent product records, missing contract details, or competing metric definitions correct. If source data or permissions are wrong, AI can make incorrect answers easier and faster to produce.
Reliable AI use therefore depends on a trustworthy semantic model, clear access rules, and known data ownership. Incorta describes its Nexus capabilities as supporting natural-language access and work such as data cleansing and model building. Those are vendor-described capabilities; the public sources do not establish that Broadcom has deployed generative AI broadly in production or validate the accuracy of AI-generated answers there.
Best Value
What other companies can learn—and where the model can fail
Broadcom’s approach is most plausible when acquisition-created fragmentation is a genuine operating problem, leaders can make system-retirement decisions, and the organization is willing to accept migration work in exchange for lower long-term complexity. It is not a universal prescription to replace every system or buy one analytics product.
The main trade-offs are material:
- Consistency versus local autonomy: common systems and definitions can simplify reporting but constrain business units with genuinely different workflows or regulatory needs.
- Simplification versus migration risk: retiring applications can strand historical records or disrupt contracts, tax rules, entitlements, procurement, sales, or support if edge cases are missed.
- Fewer product records versus commercial flexibility: a smaller catalog can remove duplication, but the enterprise must preserve distinctions that affect customer rights, pricing, or technical delivery.
- One platform versus vendor concentration: standardization can reduce tool sprawl while increasing dependence on one vendor’s price, roadmap, connectors, performance, and portability.
- Freshness versus source-system load: direct or near-real-time access can improve timeliness, but the exact Broadcom refresh design is not publicly detailed. Buyers should establish whether data is live, replicated, cached, or refreshed on a schedule.
Alternatives such as Power BI, Tableau, Snowflake, and Looker occupy different positions across visualization, data platforms, and semantic modeling. The available interview does not document a formal Broadcom proof-of-concept or a definitive rejection of those products. A buyer should first identify whether the core bottleneck is source-system complexity, data engineering, metric governance, dashboarding, operational analytics, adoption, or cloud-platform alignment.
A practical sequence for post-acquisition data integration
- Inventory the estate. Map applications, ERPs, data domains, owners, critical workflows, and system dependencies before deciding what to consolidate.
- Find conflicts that matter. Identify duplicate systems and inconsistent definitions for high-value entities such as products, customers, suppliers, contracts, and orders.
- Choose canonical records and owners. Define which source is authoritative for each entity and who can approve changes to its definition.
- Decide what survives. Classify systems as retire, consolidate, retain, or isolate; document the business capability and historical data each one supports.
- Validate exceptions before migration. Test regional rules, legacy contracts, entitlements, customer-specific arrangements, and audit requirements rather than assuming a simplified model covers them.
- Establish governance and access. Set metric definitions, data-quality expectations, role permissions, and escalation paths before broad self-service access.
- Pilot a cross-system use case. Choose a valuable workflow that requires connecting operational sources, then test data correctness, security, usability, and performance.
- Measure outcomes beyond query speed. Track report lead time, adoption, reconciliation effort, data-quality issues, operating cost, and business impact.
- Expand in stages. Add units and domains only after the common definitions and access model have been validated.
- Introduce AI against governed data. Treat AI as an interface or productivity aid, not a substitute for data ownership, quality controls, or permissions.
Broadcom’s reported example is best understood as an operating-model and data-governance decision supported by an analytics platform. Its most transferable lesson is not simply to standardize on Incorta: it is to address the applications, product records, and definitions that make analysis difficult before expecting any platform to deliver consistent enterprise-wide insight.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
