 |
|
|
 |
||
 |
||
 |
||
 |
||
 |
||
 |
 |
|
 |
||
 |
||
 |
||
 |
||
 |
||
|
||
 |
Your independent resource on business integration and network computing through middleware and message brokering
Using a message broker to deliver the Euro at NAB
Tim Willis
Manager, International Systems
National Australia Group, Europe
Management introduction
The NAB is an international financial services group which is headquartered in Melbourne, Australia. It has subsidiaries in Australia (National Australia Bank), New Zealand (the Bank of New Zealand), the US (Michigan National) and in Europe.
In common with many other banks, it has spent time in recent years reviewing its business strategy for supporting and delivering payments, not only with third parties but also within the global organization itself. The need to accommodate and work with the Euro was another factor which 'concentrated' attention.
In this case study, Tim Willis - an IT Architect turned business manager - discusses how the NAB evolved a Payments Broker solution using MINT software technology. Not only was this intended to rationalize the NAB's payments infrastructure, but it also enabled the NAB to be fully prepared for January 4th, 1999 when the Euro came into being.
Figure 4.1: Component flow for STP payments
Figure 4.2: Global Payments Broker
Figure 4.3: Payments Broker Architecture
Management conclusion
NAB in Europe has used a message broker to deliver three different objectives:
- the deployment of a flexible inter-system middleware architecture
- the introduction of the Euro
- consolidation of its Payments processes (including rationalization of an excess of S.W.I.F.T. interfaces).
This has been achieved by acquiring MINT's middleware to operate as a hub sitting between external networks (like S.W.I.F.T.), internal networks (NAB's valued added network) and the various front and back office systems. As Mr. Willis describes, this has enabled NAB to separate responsibilities - without needing to make major changes to existing applications.