OMG Homepage MDA Homepage CORBA Homepage MOF Homepage UML Homepage CWM Homepage XMI Homepage DDS Homepage OMG MARTE BPMN Homepage SysML Homepage banner



Banking/Finance

Wells Fargo Bank

Return to Success Story List

Contact:
Wells Fargo Bank
420 Montgomery St.
San Francisco, CA 94163

Tools Used:
DEC's ObjectBroker™, CORBA®, IBM mainframes, DEC's VAX/VMS Systems, Tandem System, HP 9000 Unix server

Description:
Wells Fargo Bank felt that distributed object-oriented middleware would allow them to have a customer information system that would allow them to "see" a customer's entire bank relationship, with the existing systems they had. With The Cushing Group and Digital Equipment Corporation (DEC)/COMPAQ, the bank created its Customer Relationship System (CRS) in three months. The rollout to service customers was completed in another three weeks. Wells Fargo call center representatives were able to retrieve a "customer view" using the customer's TIN (social security number or employer tax number).

Wells Fargo used DEC's ObjectBroker, which complies with the Common Object Request Broker Architecture(CORBA) standards. The bank's various source applications were mostly IBM mainframe-based, except mutual funds (based on DEC VAX/VMS systems) and brokerage (outsourced on a Tandem system). The bank constructed/mapped a business object model to capture processes and data associated with each source application and call center's business requirements. Wells Fargo used an HP 9000 Unix server to host/serve "customer" and "account" objects, which were executed on the mainframe to retrieve customer relationship and account data.

When the initial TIN inquiry window is activated and requests a "customer" (TIN), the "customer" object returns data from each accounting system. Each account had a unique icon, which when double-clicked, launched an associated "account" object. This event opens a terminal emulation session of the appropriate accounting application. The call center representative could process any transactions or account queries in the native interface for the accounting application.

Wells Fargo did not create a separate customer information file. Consequently, if a record change (e.g., new address) that affects all accounts must be processed, the bank must change each accounting application. Wells Fargo has continued to evolve its business object models, dedicating tow to three experienced IT staff members to support other development efforts in addition to CRS. Peak volume for the ObjectBroker servers is growing and can reach 200,000 business object innovations per day.

Wells Fargo expanded its Customer Relationship System to include access form the bank's Interactive Voice Response Unit, ATMs, and Internet Banking application. These extensions benefited from the re-use of "customer" and "account" objects. The bank's architecture also enables real-time connectivity to appropriate accounting applications, for example, to pay bills. The 1996 acquisition of First Interstate Bank expanded the system to support 2000 call center seats in two locations.

Copyright © 1997-2013 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact webmaster@omg.org For TECHNICAL questions, please contact webtech@omg.org This site is best viewed  with Netscape Navigator, Mozilla Firefox or Internet Explorer versions 6.0 or later or any browser
 capable of viewing JavaScript and CSS 2.0. The site is using
DHTML JavaScript Menu By Milonic.com.