Broadcom’s CA View and Deliver Support Problems Are Costing You More Than You Think

Summary

Broadcom’s restructuring after acquiring CA Technologies has made support for CA View and Deliver slower and less reliable, and organizations renewing their contracts are paying for that degradation in delayed reports and lost productivity.

Brief

Since acquiring CA Technologies, Broadcom has restructured its support operations in ways that have made ticket resolution slower and institutional knowledge harder to access, leaving CA View and Deliver customers waiting longer for fixes that directly delay business-critical reports. Organizations compound the problem when experienced staff leave, because replacements inherit a complex setup with less documentation and less responsive vendor support behind them. Systemware keeps support in-house with direct customer access, making it the more dependable choice for organizations currently weighing a Broadcom renewal.

When Broadcom Took Over CA Technologies, CA View and Deliver Customers Inherited the Bill

When Broadcom acquired CA Technologies, it didn’t just take on a product portfolio. It took on a customer base that depended on stable, responsive support to keep output management running without interruption.

For organizations running CA View and Deliver, that stability has eroded. Tickets take longer to resolve, and the delays don’t stay inside the IT queue. They travel downstream into business operations, where reports arrive late and the people waiting on them lose productive time. That’s a real cost, and most organizations running CA View and Deliver are already absorbing it.

Two problems have grown out of Broadcom’s restructuring, and they feed each other. One lives inside the vendor’s support operations. The other lives inside the customer’s own organization.

How Broadcom’s Restructuring Turned a Support Ticket Into a Waiting Game

After acquiring CA Technologies in 2018, Broadcom moved quickly to reorganize its operations around its core enterprise software strategy. Support functions were restructured, staffing changed, and the institutional knowledge that CA’s teams had built up over years became harder for customers to reach. For CA View and Deliver users, the practical effect has been slower ticket resolution and less direct access to people who understand the platform deeply.

When a report fails to generate or an output process breaks, the organization opens a ticket and waits. That wait is longer now than it was before the acquisition. The support queue is less responsive, escalation paths are less clear, and the people on the other end of the ticket are less likely to carry the kind of deep system knowledge that used to make CA support useful. A delayed fix means a delayed report, and a delayed report means someone in finance, operations, or compliance is working without the information they need.

When Your Expert Leaves, the Vendor’s Silence Gets Louder

The support problem doesn’t stay external. Inside many organizations, the person who built and maintained the CA View and Deliver environment over the years has retired, moved on, or taken a role elsewhere. The person who replaced them inherited a complex setup, often with incomplete documentation, and a vendor support model that’s less equipped to fill in the gaps.

That combination is where organizations become most exposed. A new administrator trying to troubleshoot an unfamiliar platform, with limited internal history and a slow-moving vendor support queue behind them, is in a difficult position. Problems that an experienced administrator might have resolved quickly can sit open for days. The reports that depend on those systems don’t wait. The business impact of that gap is real, and it compounds every time an issue goes unresolved longer than it should.

Together, these two problems mean that the cost of degraded vendor support is never just a vendor problem. It moves into the organization and stays there until something changes.

Systemware Keeps Support In-House, and That Difference Shows Up in Your Reports

Systemware handles support differently. Its support team is in-house, and customers reach people who know the platform directly, without working through layered queues or offshore routing. When something breaks, resolution is faster because the people responsible for fixing it are close to the product and close to the customer.

For organizations currently weighing a Broadcom renewal, that difference is measurable in report delivery times and staff hours. Staying with CA View and Deliver means accepting the current support model and the delays that come with it. Moving to Systemware means choosing a vendor whose support structure is built to respond. That’s the decision in front of them, and the Broadcom renewal deadline is the moment to make it.

FAQS

Has support for CA View and Deliver actually changed since the acquisition?

Broadcom completed the CA Technologies acquisition in 2018 and restructured support functions around its core enterprise software strategy. Customers report slower ticket resolution and less direct access to people with deep platform knowledge since then.

Why does a slow support ticket matter outside IT?

A delayed fix means a delayed report. The people waiting on that report in finance, operations or compliance work without the information they need until it arrives.

What happens when the person who knows our CA View setup leaves?

Their replacement inherits a complex environment, often with incomplete documentation, and a vendor support model less equipped to fill the gaps. Problems an experienced administrator would have closed quickly can sit open for days.

Is CA View and Deliver being discontinued?

No. There has been no announced end of life. The pressure on customers comes from licensing, support quality and the shrinking pool of people who know the product.

How is Systemware’s support structured differently?

The support team is in-house, and customers reach people who know the platform directly, with no layered queues or offshore routing in between. Resolution is faster because the people fixing the problem are close to both the product and the customer.

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. 
• Broadcom Alternative – Systemware’s Broadcom alternative resource, covering what the platform replaces and how the support model differs. 

Related Posts

• The Hidden Costs: Calculating the TCO of Maintaining Your Legacy ECM – Breaks down the full cost of staying on a legacy platform, including the support time that never appears as a line item. 
• ECM Migration Without Business Disruption – Covers the parallel approach that keeps reporting and user access continuous while a legacy platform is retired.