Over the course of the next 18 months, more than 7,000 of the world's largest banks will change the way that they communicate with one another.
On the surface, Swift's decision to migrate users of its FIN messaging service from the X.25 "store-and-forward" protocol to SwiftNet FIN, an Internet Protocol (IP) network, doesn't seem like the most exciting thing happening in financial services.
Indeed, from the perspective of David Dart, managing director and CIO of HVB America, the SwiftNet migration is just another project. "I'm not building strategy around the migration to SwiftNet," Dart says. "It's more like a move to decimalization. It's something I've been forced to do."
But the view from the home office may be quite different, he noted. HVB America is a member of HVB Group, a 680 billion euro financial institution headquartered in Munich. HVB uses the Swift network extensively for sending FIN payments and settlement messages to other banks, and even for messaging within the firm. "We are considered, as a financial institution, a fairly heavy user of Swift," says Dart.
Although the parent company likely has a strategic approach to the bank's SwiftNet deployment, HVB Americas, by itself, has enough of a business case to proceed without having to map out a grand plan. "Once we see what we can actually do with the IP-based network, then we may well seek to take advantage of that," Dart says. "But, at the moment, we use Swift to route messages. We will continue to use Swift to route messages day one, and there is no change."
HVB America is seeking to bolster its straight-through-processing efforts in money markets, foreign exchange, lending, fixed income and derivatives. To that end, the bank has deployed middleware from SeeBeyond to transmit messages throughout the organization. "Our STP initiatives have largely been the integration and automation of our internal processes," Dart says.
From the back office, virtually all of the bank's payments flow through Swift and FedWire. But, having an IP network will benefit the Swift organization just as much as it does its member banks. "The beauty of Swift is once (a message) leaves me, it's their responsibility," says Dart. "They underwrite the failure or misrouting of any particular messages, especially as it relates to payments."
Both the bank and Swift can benefit from the ability to track a transaction from start to finish, using the capabilities of the forthcoming Secure IP Network, or SIPN. Even though message delivery is Swift's responsibility, bankers have shown keen interest in the whereabouts of their payments instructions. "On the Swift network today, the most popular message is a status check," says Tim Lind, a senior analyst at TowerGroup based in Needham, Mass. "Is it failed? Is it settled?"
Formed in 1977 as a replacement for the unwieldy telex, Swift quickly became the preferred method for making international wire transfers. "Just to say you were a member of the Swift network made a statement about how serious you were in the international business, and whether or not you were a player," says Nelson F. Everhardt, senior vice president and corporate compliance executive (retired), Bank of America, Charlotte, N.C., and president of Everhardt & Associates, LLC.
Think of Swift as a members-only global Internet, to which only banks meeting strict security standards can join. Unlike encrypted Internet traffic, which travels in the digital equivalent of armored cars over public highways, SwiftNet messages travel in what, by comparison, would be protected aerial convoys through secured airspace.
In other words, it's an actual private network, not a virtual private network.
To get a full sense of the vision, just imagine an Internet where everyone's identity has been verified. No more denial-of-service attacks. No more spam. Pay-per-use pricing guarantees the timely delivery of important messages by knocking less-essential traffic out of the way.
Such a network also has the promise of maintaining secure operations during extremely adverse conditions. "Having an alternative to the public Internet is good, especially in view of the vulnerability of financial networks to disaster," says Frank Barbetta, research analyst, global carriers, for Probe Research, a telecom research firm based in Cedar Knolls, N.J.
SwiftNet FIN participants will have a choice between four telecom firms, all with dark-fiber capacity and regional router hubs: AT&T, Infonet, and Equant (which Barbetta describes as "traditional global carriers") and Colt, a pan-European carrier.
"Basically, all they're doing is carving out a small percentage of their existing network capacity and locking it down from a security perspective," says John Parker, vice president and general manager of financial markets for Vitria, a Sunnyvale, Calif.-based software firm. "That's much more economic than trying to build that from scratch, to deliver what is, in Internet terms, a miniscule amount of traffic."
Yet, in banking terms, Swift traffic isn't so shabby. In 2002, the Swift network carried over 1.8 billion messages, of which 1.1 billion were for payments, 550 million for securities settlement, and the rest split between treasury, trade finance and other messages.
Some 250 different types of FIN messages will soon travel over Swift's secure IP network. "There was one service - the FIN service - on one network," says Robin Cigman, director of strategy and development for Mercator, a Wilton, Conn.-based software company. "They're moving from the X.25 to an IP network, where multiple services can be run on the same network."
A relatively simple way to upgrade for many banks is to install the Swift Alliance Access (SAA) utility at each point within the organization that generates FIN messages. Alternatively, banks can install a Swift Alliance Gateway (SAG), which consolidates Swift traffic within an organization from disparate applications.
The gateway strategy can reduce the complexity of a bank's technology footprint. "This mandatory movement towards SwiftNet is causing strategic rethinking and tactical consolidation in the back office," says Mark Greene, general manager of global banking for IBM, who likened the SwiftNet FIN migration to the Y2K conversion. "You could convert your code and stop there, or, since you were looking at all your stuff anyway for Y2K, some banks reengineered things."
But most banks haven't taken that step towards consolidation yet. "Most of our customers, at least in the banking world, have multiple connections to the Swift network," says Vitria's Parker. "They're not yet to the point where they're managing their Swift network connectivity centrally, as they should be."
Reticence to consolidate may have its consequences down the line. "For any given migration, you can solve it faster and cheaper with a point-to-point transformation, Parker says. "But, if I change all the standards again, I have to throw out all of my previous transformation work, and it's a 'redo' from the start to do a second transformation."
Along with the reduced cost of future development, many banks hope to realize operational savings by reducing the number of points of contact with Swift.
In the past, each connection has typically required its own support staff, and thus duplication of efforts. So, if a London branch generates 80 percent of Swift traffic, it makes sense to use that location to concentrate the remainder of the traffic. "There are American banks (with) premises in London, which are managing a portion of their U.S. traffic from London just to optimize their use of the Swift network," says Fabian Vandenreydt, managing principal in the Brussels office of Capco.
Furthermore, adding a Swift gateway ensures that new services can be adopted as they become available. "Now, they'll have one network that offers much more than just the FIN, so a lot of the things that (financial institutions) would want to do would be available via SwiftNet," says Yossi Covo, vice president, SunGard Business Integration, New York. "The traffic cost would be less than actually connecting via alternative mechanisms."
A QUICK FIX
In order for SwiftNet to gain traction in the United States as a gateway for more than just FIN messaging, it needs to bring with it additional functionality. That's because U.S.-based banks typically do not rely upon Swift for clearing and settlement to the same extent as European banks. "The U.S. market is very well structured," Vandenreydt says. "Swift wants to move up towards the middle- and front-office traffic by supporting FIX services on its network."
The FIX service supports communication between buy-side and sell-side securities firms and investment managers, including pre-trade messages, indications of interest and trade messages. "We're not the only game in town - there are other services out there supporting FIX traffic," says Matt Fox, program manager, SwiftNet FIX, New York. "The biggest value we bring to the world of FIX is access to our community."
When SwiftNet FIX becomes available over the Secure IP Network, banks should be able to expand their range of trading partners. "The sell side's always interested in finding new buy-side clients they can service, and the buy side's always interested in finding the best execution out there," Fox says.
Indeed, FIX networks live and die by the number of participants they attract. "We have this very large community that we're making the FIX services available to, and a lot of these firms have not used FIX in the past," says Fox. "For a lot of firms on the network, Swift is really their only means of communicating electronic information. So, having the FIX services makes those services now accessible to firms who couldn't, for one reason or another, get to them before."
One reason that firms have been inaccessible is that FIX sessions had required point-to-point connections. "For FIX, you literally have to subscribe to seven different networks to talk to seven different customers," Fox says.
As a hub-based service, SwiftNet FIX will allow its users to communicate with the entire Swift community without such machinations. "We allow firms to connect into us through a single FIX session, and we manage their connectivity out to their endpoints," says Fox. "In a sense, they've outsourced the monitoring and maintenance of those connections through Swift."
This functionality requires installation of FIX engines from companies such as Financial Fusion. "We essentially built an application to deliver FIX messaging across the Swift network, instead of having to deal with all the point-to-point connections they would have to deal with if they used FIX as defined today," says Andrew Bergen, director of products, Financial Fusion, Concord, Mass.
The Swift-savvy firms new to FIX will have an easier time of it than FIX-fluent traders that have to get onto Swift. "(FIX) is just a TCP/IP-based protocol - it's implemented all over the place, in various forms, on various networks," Fox says. "Whereas Swift not only has its own messaging standard, but its own private network and its own services that support communication using its protocols."
Given the cost of adopting Swift, banks have shown an eagerness to find new applications for the network as they go. "When they look at how the front offices communicate today - which is not over a standardized network or a private network with the security, reliability, non-repudiation, guaranteed delivery, and those type of features in there, with a single customer-service organization supporting them - there's an argument that they can rationalize their infrastructure, and put their FIX traffic over the Swift network as well," Fox says.
SWIFT Hopes to Conquer Fear of "New Realities"
Now that host country Singapore has been given the "all-clear" signal by the World Health Organization, SWIFT's Sibos 2003 conference seems all set to proceed as scheduled, from October 20 to 24. The apropos theme: "New Realities."
This year, the speaker line-up includes Brett Goodin, President of Fidelity Investment Management Asia/Pacific; Tharman Shanmugaratnam, Singapore's Senior Minister of State, Trade and Industry; and Vincent Cheng, CEO of Hang Seng Bank and Group General Manager of HSBC. Sixty-six other speakers have also confirmed their participation.