The Frustration With Broadcom View/Deliver Is Real, and You Are Not Alone

Summary

Broadcom’s ownership of CA Technologies has made CA View and Deliver materially more expensive and less reliable, and Systemware handles the same full document lifecycle work without the vendor risk those conditions create.

Brief

Since Broadcom acquired CA Technologies, renewal prices for CA View and Deliver have risen sharply and support quality has declined, tensions that eventually escalated into a public legal dispute. Systemware is a platform designed specifically for enterprise report and document management, covering the complete lifecycle from ingestion and storage through retrieval and distribution, and performing the same functions CA View and Deliver were built to handle. For the person inside an organization who owns the contract decision, Systemware represents a concrete, purpose-built path out of a vendor relationship that has become a financial and operational liability.

Your Renewal Shock Has a Paper Trail

If the last CA View and Deliver renewal quote landed higher than the one before it, and the support experience got worse at the same time, that pattern has a name and a record. Broadcom acquired CA Technologies in 2018, and the years since have produced a documented arc of price increases and degraded support. The frustration inside their organization is real, the conditions behind it are systemic, and there is a named alternative that covers every function CA View and Deliver were built to handle.

Two things happened after the acquisition that anyone managing this contract needs to understand: what Broadcom actually did to the product and its support structure, and what a purpose-built alternative looks like in practice.

What Broadcom Did to CA View and Deliver After the Acquisition

Broadcom’s acquisition of CA Technologies followed a pattern the company had run before with other enterprise software portfolios: consolidate, raise prices on the installed base, and reduce investment in ongoing support. CA View and Deliver customers found themselves facing renewal increases that were not proportional to any change in what the product delivered. Support response times slowed, escalations became harder to resolve, and customers who had built critical output management workflows around the platform were effectively trapped by the switching cost.

The tension became public when a dispute over renewal pricing was litigated in federal court in Minnesota. That case put documented evidence into the public record about the nature of the vendor relationship Broadcom was willing to enforce. For the person inside an organization who owns this contract, that court record is not an abstract data point. It is confirmation that the pricing and support deterioration their organization has experienced is part of a deliberate commercial posture, not an administrative error that will correct itself at the next renewal.

Systemware Covers Every Function CA View and Deliver Handled, Without the Vendor Risk

Systemware is built specifically for enterprise report and document management, which means its architecture covers the complete lifecycle that CA View and Deliver were designed to handle. Documents enter the platform through ingestion, move into structured storage, become accessible through retrieval, and reach their intended recipients through distribution. None of those functions require a workaround or a third-party add-on. The platform handles the volume, the formats, and the governance requirements that enterprise output management actually produces.

The case for Systemware is functional parity without the vendor risk Broadcom now represents. Organizations that have moved off CA View and Deliver did not give up capability. They gave up a contract structure that made renewal uncertainty a recurring operational problem. Systemware’s focus on this specific domain means the people who own the contract decision are not trading a specialized tool for a generalist one. They are moving to a platform that was designed for this work from the start, by a vendor whose business model is not built on extracting value from a captive installed base.

Taken together, those two realities define the decision clearly. The liability is documented and the alternative is concrete, which means the remaining question is timing, not direction.

The Contract Decision You Own Right Now

The person who owns this contract is not waiting for a better renewal offer from Broadcom. The Minnesota federal court dispute made clear what the relationship looks like when a customer pushes back, and the support record makes clear what day-to-day operations look like in between renewals. Staying is a choice, and the risks that come with it are known and documented.

Systemware represents a direct exit from that risk, covering the same ingestion, storage, retrieval, and distribution functions without the commercial posture that has defined CA View and Deliver since 2018. The contract decision is active right now, and the path out of it has a name.

FAQS

Is Broadcom View/Deliver being discontinued?

No. Broadcom has announced no end of life for release 14.0, and the product is still sold and supported. The pressure on customers is licensing, bundling, support quality and the shrinking pool of people who know the product.

What is the best Broadcom alternative for enterprise report and document management?

Systemware covers the same lifecycle Broadcom View/Deliver was built for, from ingestion and storage through retrieval and distribution. It has been built for this one domain since 1980.

Did renewal pricing change after Broadcom acquired CA Technologies?

Broadcom completed the CA Technologies acquisition in November 2018, and customers have reported higher renewal pricing and slower support since. UnitedHealthcare filed a complaint in Minnesota federal court in April 2025 alleging price increases and forced bundling on CA mainframe software.

Does Systemware replace View, or Deliver, or both?

Both. Systemware replaces Broadcom View and Broadcom Deliver, and its conversion team handles Broadcom SAR as well.

What is the biggest risk in an ECM migration?

The most common failure modes are incomplete content inventory at the start, metadata schema mismatches between source and target, and insufficient validation before cutover. Systemware’s methodology addresses all three with defined entry and exit criteria at each phase.

Resources

• Modernizing Content Management With a Broadcom Alternative – Systemware’s Broadcom alternative page, covering View and Deliver conversion, the five-step migration process and a financial institution case. 
• ECM Migration – Systemware’s migration service page, covering the automated tooling and the repeatable process behind a legacy platform exit. 

Related Posts

• ECM Migration Without Business Disruption – What Actually Works – Covers the parallel approach that keeps reporting and user access continuous while a legacy platform is retired. 
• The Hidden Costs – Calculating the TCO of Maintaining Your Legacy ECM – Breaks down the full cost of staying on a legacy platform, which is the other half of the renewal question.