Bank of America's 'higher standards' for VoIP
By
Phil Hochmuth
,
Network World
, 12/20/2004
- Share/Email
- Tweet This
- Print
If any corporation is ready for VoIP, it's Bank of America. The bank has spent three years building an all-optical, multigigabit
WAN backbone with Broadwing and Sprint, and upgrading its LAN switches to support QoS and in-line power. Now the company plans
to deploy 180,000 Cisco IP telephones and replace 363 PBXs across 5,000 branches with centralized IP PBXs, with the help of
Electronic Data Systems. Steve Venezia, managing director of the network computing group and network services at Bank of America, spoke recently with Network World Senior Editor Phil Hochmuth. Here is an edited transcript:
What will be the big payoff with VoIP?
We have done projections, but I don't want to get into the dollar amounts. The key is to give the business the opportunity
to utilize technology on a fully converged network. With all-data endpoints [PCs and phones], there are vast capabilities
that are possible for improving productivity with new applications. I've been going out to the businesses and talking about
what the possibilities are for how this network will be used. It will really be their decision.
Secondly, cost is a factor. The operational cost savings are there with VoIP. The voice world has always been complex and
harder to manage than the data world. Convergence gives us the ability to look at our whole technology entity. It will let
us be more predictive of failures and other network events, which gives us the ability to keep system availability at a certain
level.
Why Cisco?
We have a huge outsourcing agreement with EDS. EDS and our architecture group came up with some stringent and thorough metrics for the decision-making processes; we looked
at it from the angles of security and products themselves to the financial viability and technical support offerings of the
vendor. Everything got weighted out, and Cisco was the choice. We're being careful about how we're going through our proof-of-concept
and pilots sites right now. By the end of this year or early next year, we'll look at the results. The answer will be binary
- either yes or no, as to whether we're going ahead.
So there is a chance you'll scrap the whole VoIP plan?
I wouldn't say there is a strong chance that it won't go forward. We've had very few setbacks.
How are you conducting your pilots?
We're in the back-office, branch facilities and high-end office space. There are about 1,000 IP phones, and it will be about
1,500 when the pilots are completed. We're doing different scenarios of the various types of sites we'll deploy. We'll have
a model for each of the areas we'll be rolling out, not that it's cookie cutter.
It's a really collaborative effort among Cisco, EDS and ourselves. My architecture team is driving the technology and how
we're approaching it. The mitigation of any issues is driven by my team through EDS and Cisco.
How do you feel about the fact that Dow Chemical hired EDS in 2001 for an equally ambitious VoIP project, which didn't work
out? They switched integrators and are now basically starting over.
Dow outsourced to EDS, but [EDS] didn't know [Dow's] customer base. I knew we had to do this in incremental steps, which we
are doing. We have risk mitigation, in terms of each step we go through. We won't go ahead until this testing and proof of
concept are checked off on all criteria.
Dow made a couple of significant failures; they went for the whole ball of wax. Plus, the technology was not as mature as
it is today. Other folks who either had difficulty or failed with VoIP either tried to boil the ocean themselves or just gave
all the project management to their outsourcer. These are usually not the wisest things to do.
Comment