A global logistics group navigated Brocade end of life and cut support 38 percent.

The group runs Brocade Fibre Channel fabric as the storage backbone across nineteen data centres globally, supporting a logistics operation that processes high volumes of structured transactional data twenty four hours a day. The fabric had grown across eight years of capital investment. A significant portion of the installed base was on hardware that Brocade had already designated as end of life, with announced end of support dates inside the proposed renewal term. The Broadcom support renewal quote landed at twelve million eight hundred thousand dollars across three years, calculated on full support for the entire installed base regardless of EoL status. The director of network and storage saw the quote, observed that the group had a documented retirement schedule for roughly forty percent of the EoL hardware inside the term, and asked us to align the support contract with the retirement plan.

The engagement ran four months. The signed contract closed at seven million nine hundred thousand dollars across three years, with a tiered support model that matched the support level to the retirement schedule of each asset class and contracted spares provision for the EoL gear that needed to stay in production for the remainder of its lifecycle. The thirty eight percent reduction against the trajectory was the visible outcome. The structural outcome was an explicit linkage between the support contract and the retirement plan, which removed the need to renegotiate when the retirement milestones were hit.

The Quote

The twelve million eight hundred thousand quote was built on a single position. Full support, on the full installed base, across the three year term. The position did not respect the EoL designations. It did not respect the retirement schedule. It did not distinguish between hardware that needed full support and hardware that needed minimal support to function until retirement. The position was the seller's default. The buyer side had to surface the alternatives.

The alternatives existed in the Broadcom support catalogue. A reduced support tier was available for designated EoL hardware. A spares only tier was available for hardware in late lifecycle. A wind down tier was available for hardware with a contracted retirement inside the support term. None of the three tiers had been proposed in the renewal. The full support tier had been the only option presented.

The Find

The internal work was the retirement plan itself. The group's network and storage team had been managing the retirement schedule across two years and had a documented asset by asset retirement timeline. The timeline was not visible to the Broadcom account team because nobody had shared it. The first action of the engagement was to share the retirement timeline with the account team, in writing, with the support tier ask for each asset class clearly stated.

"The account team had no way of knowing what we were retiring and when. We had not told them. The quote was full support on everything because that was the only thing the account team could quote without our retirement plan in hand."Director of network and storage

The second finding was on spares. The hardware that was staying in production until retirement needed assured access to replacement parts. The Broadcom support catalogue carried a spares provision but it had to be requested and contracted separately. Without the spares contract, the reduced support tiers carried risk that the buyer side was not willing to accept. The spares contract was negotiable on volume and on term. The buyer side could specify exactly which assets needed spares coverage and for what duration. The economic difference between blanket spares coverage and asset specific spares coverage was material.

The third finding was on the contract term itself. The original proposal was a three year term aligned to the calendar. The retirement schedule did not align to the calendar. A term that aligned to the retirement milestones, with anniversary points at the major retirement events, was a better structural fit. Broadcom had not proposed it. The buyer side asked for it.

The Restructure

The restructure proposal was tabled in writing. It made four asks. First, the installed base segmented into four support tiers matched to the retirement schedule. Full support on the assets staying in production through the term. Reduced support on the assets retiring inside the term. Spares only on a defined subset where the retirement was certain and the timeline was inside twelve months. Wind down support on the assets being decommissioned in the first six months. Second, an asset specific spares contract for the reduced support and spares only tiers. Third, a term structured around two anniversary milestones aligned to the retirement events. Fourth, a contracted reduction in the support fee at each retirement milestone, set in advance rather than negotiated at the event.

The account team's response on the tier segmentation was constructive. The tier model was available in the catalogue and the segmentation work needed the buyer side's retirement schedule, which the buyer side had now provided. The pricing for each tier was set against the catalogue rates with a defined discount applied across the bundle. The asset specific spares contract was the longest conversation and took two rounds across six weeks. The term restructuring was agreed in a single round. The contracted milestone reduction took the final round and was agreed on the basis that it removed a renegotiation risk for both sides.

The final contract closed at seven million nine hundred thousand dollars across the restructured term, with each support tier and each spares element documented at the asset class level. The contract is operationally usable as a working document for the network and storage team.

The Outcome

The signed contract delivered a thirty eight percent reduction against the trajectory while giving the group operational certainty across the EoL transition. The retirement plan continues to execute against its documented schedule. Each retirement milestone triggers a contracted support fee reduction without requiring a renegotiation. The spares coverage is in place where it is needed and absent where it is not, and the savings from removing the spares coverage on assets that did not need it were material to the overall reduction.

The pattern applies to most Brocade engagements we have worked on this year. The Broadcom support catalogue contains tiers and provisions that benefit buyers with managed EoL estates if the buyers ask for them. The default quote is full support on the full installed base. The buyer side has to surface the retirement plan, propose the tier segmentation, and contract the spares element separately. The economics that result are substantially below the default. The work is structured and takes a quarter to do properly.

The takeaway

• Brocade support quotes default to full support on the full installed base regardless of EoL status. Tier segmentation is available in the catalogue but the buyer side has to ask for it and has to bring a retirement schedule to the conversation.
• Spares coverage is negotiable on asset specificity, volume and term. Blanket spares coverage across the installed base is almost never the right structure for an EoL estate.
• Term structuring around retirement milestones, with contracted fee reductions at each milestone, removes renegotiation risk on both sides and converts retirement events into priced contract events.