1. Slide 1 Filename_Vx.ppt SWIFTNet Migration DE/AT DIDUG, 12. - 14. May 2003 Claudia König Regional Account Manager

2. Slide 2 SWIFTNet Migration - DIDUG 2003 SWIFTNet FIN Migration  Overview  Planning  Ordering  Summary

3. Slide 3 SWIFTNet Migration - DIDUG 2003 FIN and SWIFTNet FIN: main components FIN CBT X.25 SAP X.25 SWIFT Operating Centre Modem IP FIN SWIFTNet FIN Bridge FIN CBTM-CPE SNL FW Network Partner POP VPN box

4. Slide 4 SWIFTNet Migration - DIDUG 2003 SWIFTNet Migration Approach Country Window Approach +/- 5000 BICs Country Window Approach +/- 5000 BICs Hand-holding Approach ~ 200 locations Hand-holding Approach ~ 200 locations  Road shows  Configurator for planning and budgeting  Ordering via SWIFT.com  Support national market infrastructure plans SWIFTNet Migration All 7200+ BICs SWIFTNet Migration All 7200+ BICs “Facilitated” ~ 150 locations “Facilitated” ~ 150 locations “Complex” ~ 50 locations “Complex” ~ 50 locations Criteria:  Largest accounts  Target more than 100,000 Messages/day  All qualifying BICs for single institution grouped Criteria:  Large accounts  Target 40K-99K Messages/day  All qualifying BICs for single connection grouped

5. Slide 5 SWIFTNet Migration - DIDUG 2003 SWIFTNet FIN migration overview  Q4 2002: Early adopters  December 2002New FIN customers Cut-over:on SWIFTNet FIN  2003 - 2004:Main migration period  2Q 2003:Start MVIP Early Adopter Phase  4Q 2004:Penalty period  End 2004:End of X.25 support 2002 2003 2004

6. Slide 6 SWIFTNet Migration - DIDUG 2003 Worldwide Status until end of March 2003 worldwide 159 BICs migrated during the 1st Quarter 2003 peak day 119,312 messages a total of 911,046 messages were transferred over SWIFTNet FIN vs. 165,685,791 total FIN messages DE/AT Status until end of April 2003 6 out of 20 DE1 BICs switched live traffic 5 out of 9 AT1 BICs switched live traffic SWIFTNet FIN migration status

7. Slide 7 SWIFTNet Migration - DIDUG 2003 Access networksLocal loops SIPN Access Multi-Vendor network connectivity Customer premisesBackbone Customer A Customer B Backbone Access Points OPCs SIPN Backbone Network Partner n Network Partner 2 Network Partner 1 VPN box One logical network at the VPN level VPN box VPN box M-CPE Modem/TA

8. Slide 8 SWIFTNet Migration - DIDUG 2003 Network PartnerSWIFT SIPN Access Management responsibilities CustomerSWIFT Customer A Customer B M-CPE Backbone Access Points OPCs SIPN Backbone Network Partner 2 Network Partner 1 VPN box VPN box Network Partner n VPN box IPSec tunnels provide end-to-end protection through the ‘untrusted’ Network Partner IP networks Modem/TA

9. Slide 9 SWIFTNet Migration - DIDUG 2003 SWIFTNet FIN Migration  Overview  Planning  Ordering  Summary

10. Slide 10 SWIFTNet Migration - DIDUG 2003 Setting the Scene 7 stage SWIFTNet migration process for CMW Customers Project initiation Design, planning and approval Ordering Provisioning and installation Test (including stress test) Live and staged ramp up X. 25 decommissioning 1 2 3 4 5 6 7 Project team and plan in place : 2 weeks Solution fully planned and approved : 8-12 weeks Clean order, accepted by COS : 2-3 weeks Products and services provisioned and installed : 14 weeks Customer ready to migrate live FIN traffic : 4 weeks All FIN traffic migrated to SWIFTNet : upto 12 weeks Dismantling of X.25 infrastructure Deliverable / Typical duration

11. Slide 11 SWIFTNet Migration - DIDUG 2003 0510# Weeks 3-4 w Preparation and installation of SW 12 w Line & CPE delivery, CPE installation SWIFT systems provisioning 2 w (Installation of service specific SW) 1 w 12 w Customer preparation h/w, s/w, Firewall, NAT and staff training Order creation (Telecom partner) 1 w SWIFT validates forms Order forms sent to SWIFT 4 w Managed Dial-up 3-4 w SWIFT systems provisioning Preparation and installation of SW 2 w Customer preparation customer activation The SWIFTNet implementation timelines Decide on your configuration

12. Slide 12 SWIFTNet Migration - DIDUG 2003 SWIFTNet FIN Migration  Overview  Planning  Ordering  Summary

13. Slide 13 SWIFTNet Migration - DIDUG 2003 How to Order  1. The Order Flow for: - Dial-up Connection - Managed Connection  2. Ordering Tools: - e-Ordering: SWIFTNet FIN Migration - Paper forms: Other Services (+ special cases) - Ordering VPN Box (only for dial-up)  3. Service Bureaux & Shared Connections

14. Slide 14 SWIFTNet Migration - DIDUG 2003 Customer SWIFT Local telecom (1) Order SWIFTNet (2) Order ISDN or PSTN line from local provider (3) Order VPN box directly from VPN box reseller VPN boxes VPN Box reseller Network partner (5) Activate port for dial-up (6) Provision & activate VPN device (4) Provide VPN provisioning information SWIFT’s Customer Order Flow Dial-up Connection

15. Slide 15 SWIFTNet Migration - DIDUG 2003 Customer SWIFT Network Partner (2) Order service to network partner Local telecom (3) Order ISDN line and TA (if necessary) (1) Order SWIFTNet (4) Order local loop (5a) Install router, VPN and local loop (5b) Provide VPN provisioning information (6) Provision & activate VPN device SWIFT’s Customer Order Flow Managed Connection

16. Slide 16 SWIFTNet Migration - DIDUG 2003 E-Ordering Migration Toolbox Overview SWIFTNet Migration Toolbox ConfigurationOrderingSupportStatus Knowledge base & Case manager SWIFTNet Migration Ordering Tool Key Activity Manager SWIFTNet Migration Configuration Tool

17. Slide 17 SWIFTNet Migration - DIDUG 2003 E-Ordering How do I get access ? Toolbox - Valid BIC - anybody within your institution Ordering - Limited to one user per institution clip

18. Slide 18 SWIFTNet Migration - DIDUG 2003 E-Ordering SWIFTNet Migration Configuration Tool

19. Slide 19 SWIFTNet Migration - DIDUG 2003 E-Ordering SWIFTNet Migration Ordering Tool

20. Slide 20 SWIFTNet Migration - DIDUG 2003 Ordering portal Paper Forms How do I get access to paper forms?

21. Slide 21 SWIFTNet Migration - DIDUG 2003 Ordering the VPN Box from TELINDUS www.telindus.com/swift

22. Slide 22 SWIFTNet Migration - DIDUG 2003 Service Bureaux & shared connections

23. Slide 23 SWIFTNet Migration - DIDUG 2003 DE2 01.04.-29.04.03: ordering 19.08.-08.09.03: migration window 09.09.-08.12.03: move live traffic to SWIFTNet 08.12.03: switch off x.25 connection Next steps: customer to monitor delivery and installation SWIFTNet FIN Migration Next steps

24. Slide 24 SWIFTNet Migration - DIDUG 2003 DE3 01.10.-27.10.03: ordering 16.02.-05.03.04: migration window 06.03.-05.06.04: move live traffic to SWIFTNet 04.06.04: switch off x.25 connection Next steps: attend SWIFTNet training sessions plan the migration SWIFTNet FIN Migration Next steps

25. Slide 25 SWIFTNet Migration - DIDUG 2003 DE4 12.02.-11.03.04: ordering 01.07.-21.07.04: migration window 22.07.-19.10.04: move live traffic to SWIFTNet 20.10.04: switch off x.25 connection Next steps: stay informed and consider additional SWIFTNet Services SWIFTNet FIN Migration Next steps

26. Slide 26 SWIFTNet Migration - DIDUG 2003 AT2 05.01.-04.02.04: ordering 26.05.-30.06.04: migration window 01.07.-28.09.04: move live traffic to SWIFTNet 29.09.04: switch off x.25 connection Next steps: stay informed and consider additional SWIFTNet services SWIFTNet FIN Migration Next steps

27. Slide 27 SWIFTNet Migration - DIDUG 2003 Monthly surcharges and penalties for remaining X.25 connections Monthly surcharge for remaining X.25 connections: LocationDial-up linePermanent line Western EuropeEUR 300EUR 600 on 1 October 2004: EUR 5,000 per connection on 1 November 2004: EUR 10,000 per connection on 1 December 2004: EUR 20,000 per connection Penalty for remaining X.25 connections

28. Slide 28 SWIFTNet Migration - DIDUG 2003 SWIFTNet FIN Migration  Overview  Planning  Ordering  Summary

29. Slide 29 SWIFTNet Migration - DIDUG 2003 What to do? If you are not already in the process start your preparations Create a project team Assign a project manager Clarify roles, responsibility and communication channels within your organisation Train key staff on SWIFTNet Decide on your configuration (SN Services, Throughput, Connectivity Packs, Security…) Check out for you migration dates If you are already in the migration process respect your deadlines

30. Slide 30 SWIFTNet Migration - DIDUG 2003 Customer Tasks Get in Contact with Network Partners AT&T - email: swiftnet@emea.att.com Colt - email: swiftnet@colt-telecom.com - Website: www.colt.net/swift Equant - email: swift_orders@equant.com - Website: www.equant.com/swift Infonet - email: swift@infonet.com - Website: www.infonet.com/swift_ip_solutions Local Contacts AT&T: Michael N. Weigel +49 69-15306-254 mweigel@emea.att.com Colt: Gerhard Lange +49 69 56606 - 4860 Gerhard.Lange@colt.de Equant: Christoph Doerr +49 69 92901 515 Christoph.Doerr@equant.com Infonet/Telekom Dr. Heinrich Rudolph +49 69 665315750 Heinrich.Rudolph@t-systems.com

31. Slide 31 SWIFTNet Migration - DIDUG 2003 Customer Tasks Get in Contact with SWIFT Service Partners Provide the following services locally: SWIFTAlliance implementations SWIFTNet migration assistance Connectivity implementations Regular upgrades of SWIFT interfaces and other SWIFT software products Addresses, Infos about their Service, Pricing Overview are available on swift.com

32. Slide 32 SWIFTNet Migration - DIDUG 2003 Customer View Where to find help www.swift.com  On line customer services (OLCS): your first stop to find help  SWIFTNet ordering portal  Migration toolbox –Network partner information –Online support - Frequently Asked Questions (FAQs) –Configurator tool for connectivity and budgeting information –e-ordering tool including the KAM (key activity management tool)  Order preparation checklist For any other questions: Customer Services Centre

33. Slide 33 SWIFTNet Migration - DIDUG 2003 Contacts in Germany  Simone Weyhenmeyer 069 - 7541 - 2220 Simone.Weyhenmeyer@swift.com  Claudia König 069 - 7541 - 2260 Claudia.Koenig@swift.com

34. Slide 34 SWIFTNet Migration - DIDUG 2003