Your SlideShare is downloading. ×
Premium Services Forum 2014
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Premium Services Forum 2014


Published on

Published in: Economy & Finance

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Premium Services Forum Americas New York March 3, 2014 Achieving operational excellence and harvesting the rewards of collaboration
  • 2. Achieving operational excellence and harvesting the rewards of collaboration Welcome back to New York Danny Smedley March 3, 2014
  • 3. Welcome Back
  • 4. Three subcommittees: • Cash & Trade • Securities • Technology Benefits of being a member • Gain insight • Influence • Hear from SMEs Open to U.S. SWIFT Users Announcements 11:00 am – 12 noon Royale Room Business Forum Session To join, contact: • Danny Smedley at • John J Masterson at
  • 5. 18 35 9.6 57 41 Number of Premium and Premium Plus Customers in the Americas Years SWIFT has been in business Latest Premium Plus Survey Results PSF 2013 Attendees Inches of snow on February 13th
  • 6. Agenda 09:00 – 09:10 Welcome Danny Smedley, Director Customer Support, Americas 09:10 – 09:40 SWIFT in Your Region Chris Church, CEO - Americas, Global Head of Securities Danny Smedley, Director Customer Support, Americas 09:40 – 10:15 One step further in documentation Bikash Mishra, Service Manager 10:15 – 10:45 About in 2014 Cindy Wonsang, Service Manager Ivania Martinez, Support Engineer 10:45 – 11:00 Coffee Break 11:00 -12:00 Security challenges – HSM and Services Michael Girboux, Service Manager Suk Rawat, Product Manager 12:00 – 13:00 Lunch
  • 7. 13:00– 14:00 The community approach to crisis – In the news Becky Almodovar, Head of Key Client Support and Service Management Mariela Atanassova, Senior Facilitator 14:00 – 15:00 Knowing your SWIFTNet recovery features Arnaud Boulnois, Head of Messaging Product Management Prakash Lele, Head of SWIFTNet Delivery 15:00 – 15:30 Coffee Break activity – Discover more about your PSF 15:30 – 16:00 Integration Portfolio and Alliance Messaging Hub Juan Martinez, Head of Applications, Integration & Partner Marketing David Fergie, System Integration Expert 16:00– 17:00 Managing your information security challenges Michael Fish, CIO, Head of Information Technology and Operations 17:00 – 17:15 Closing Becky Almodovar, Head of Key Client Support and Service Management 17:30 Dinner
  • 8. Interactive Polling Stations
  • 9. SWIFT in Your Region Chris Church, CEO – Americas, Head of Securities Danny Smedley, Director Customer Support, Americas Achieving operational excellence and harvesting the rewards of collaboration
  • 10. SWIFT and Regional Update Chris Church Danny Smedley
  • 11. One further step into documentation Bikash Mishra – Service Manager Integration of new features into the support system
  • 12. Session objectives • Provide insights as to what has been done so far to documentation and what the future looks like • Explain what has changed • Give insights how to get required information
  • 13. You had 3 main recommendations “Where would you spend your money?” Last year’s PSF
  • 14. Links and references UHB Homepage Newsletter enhancements Four areas improved Search improvements
  • 15. PSF 2013 Recommendations… “The search does not find what we’re looking for!”1
  • 16. Search Improvements Improved relevance Increased performance User Interface SMART Highlighting
  • 17. Improved relevance Increased performance User Interface SMART Highlighting Algorithm refined KB preview snippets before login
  • 18. Improved relevance Relevance algorithm based on date, source, content…
  • 19. Improved relevance Increased performance User Interface SMART Highlighting Search Results faster
  • 20. Improved relevance Increased performance User Interface SMART Highlighting More intuitive Improved filter system Increased character limits
  • 21. Improved relevance Increased performance User Interface SMART Highlighting Context specific Books Products
  • 22. Smart highlights – context specific information
  • 23. Smart highlights – Another example
  • 24. PSF 2013 Recommendations… “We need hyperlink references!”2
  • 25. The platform is now ready as well! As of now, all « new » and « updated » books will have hyperlinked cross references.  Security Officer Guide  Self Help Guide  Release letters  Knowledge base tips
  • 26. Topic references: Example Pricing tip Pricing tip before Topic references How to calculate the price of the FIN user-to-user messages? Description This tip is useful if you are interested to know how SWIFT invoices your everyday FIN user-to-user traffic. Main Reference: SWIFT User Handbook > Pricing and Invoicing > Price List ( January 2013): 1 Definitions, Price List 2.1.1 FIN User-to-User Traffic, Price List The following parameters are to devise the fees of your sending FIN user-to-user messages: Message Type and Chargeable Units Global Tier Geographical routes Any applicable discount / rebate, such as high volume FIN intra- institution discount. Any geographical surcharge Other parameters when applicable, such as, Message priority and delivery monitoring options,Test and Training traffic, etc. Information Message Type FIN reporting Message Types: MT535. MT536, MT537, MT548, MT569, MT940, MT941, MT942, MT950. FIN non-reporting Message Types: All other non-system FIN messages (categories 1- 9). Chargeable unit The fee for the transmission of a message is based on the chargeable unit. The number of chargeable units of a message is computed by dividing its actual length by the message base length. Minimum is at 1 chargeable unit, even if the message length is less than the base length. Before AfterPricing tip after Topic references How to calculate the Price of the FIN user-to-user Messages Introduction This tip provides examples to illustrate how to calculate the price for the FIN user-to-user messages that you send. This tip is based on information from the Price List for SWIFT Messaging and Solutions document. To find this document, go to>Support>Documentation (User Handbook). Calculation of FIN user-to-user message fees The following parameters are used to define the fees of the FIN user-to-user messages that you send:  Message Types  Chargeable Units  Global Tier  Geographical Routes  Any applicable discount / rebate such as high volume FIN intra-institution discount  Any geographical surcharge  Other parameters when applicable such as message priority, delivery monitoring options, Test and Training traffic Illustrative examples of message fee calculation The tariff used in the following examples is referenced in the Price List for SWIFT Messaging and Solutions document, section User-to-User Traffic. Example 1: International inter-institution message Scenario: BBBBGB2L sends an MT 700 to a CCCCATPP. Work out the following before calculation:  message type: MT 700 (non-reporting message)  message length: 3,500 characters (3,500 / 325 = 10.7692 chargeable units)  geographical route: international inter-institution  priority: urgent message with delivery notification and non-delivery warning  global tier: 5 This is a non-reporting, international inter-institution message with priority options. The calculation of the fee for this message is as follows: EUR 0.0824 (unit price at Global Tier 5) x 10.7692 + EUR 0.56 (priority) = EUR 1.45 If this same message is sent from BBBBGB2L to ABCDMOMX, then the unit price is surcharged at 100 percent (that is, the unit price is doubled) due to GEO premium (see Note).
  • 27. New UHB Homepage
  • 28. UHB revamp: Homepage tab
  • 29. UHB revamp: Search driven
  • 30. UHB revamp: Information banner
  • 31. UHB revamp: Quick links
  • 32. PSF 2013 Recommendations… “We need to be notified about documentation changes!”3
  • 33. Abstracts of new publications UHB BI-Monthly newsletter What? Changes? An overview of the updates on the User Handbook Change synopsis for updates Preview on next month’s publications schedule Overview of content and direct links to Release letters If Knowledgebase tips relating to documentation
  • 34. For non RSS subscribers, enhancements have been made to the UHB Newsletter to address this request.
  • 35. Thank you
  • 36. 2014 Cindy Wonsang – Service Manager Ivania Martinez – Support Engineer Coming changes and new applications
  • 37. What we heard from you Better Tracking Easy to find Easy to use Usability More …..
  • 38. What happens now ? 1. New profiles will go live on March 22nd 2014 2. What will happen to already registered users? 3. What will happen to pending request for registration and change of profile?
  • 39. Centralized Access Easy to Find: All in one place Case Manager Knowledge Base Operational Status User Handbook Download Center Lease Line Utilization SWIFTNet Services Directory
  • 40. Help every step of the way ! Easy to Find Help !
  • 41. Standardized Profiles Easier Administration Standard Profile Standard Application Accesses – Ordering and Billing Applications –
  • 42. Delegation Easier Administration
  • 43. Delegations B C A SWHQUSUS 123456 S.W.I.F.T.
  • 44. Delegate your e-ordering Remove delegation Delegate e-ordering to another institution
  • 45. Delegate your e-ordering
  • 46. Delegate your e-ordering
  • 47. Our ‘Before’ Training page OLD Usability
  • 48. What is new here ?
  • 49. Session details
  • 50. Reporting Better Tracking Who are the users ? Who delegated what ? Audit reports ?
  • 51. What next?
  • 52. The results – 2 concept prototypes Just examples Which one do you want first?
  • 53. Scenario 1
  • 54. Scenario 2
  • 55. Thank you • Questions? Comments? • Just want to chat about how could be of help? • Please contact
  • 56. Networking Game Picture Skills/ interests/ knowledge Connect!
  • 57. Coffee Break
  • 58. Security: HSMs and Services Suk Rawat– Product Manager, Security Product Portfolio Michael Girboux – Key Clients Service Manager Addressing the challenges
  • 59. Why refresh HSMs? “Current HSM boxes are ageing and reaching end of product life. They must be refreshed to ensure safe and continuous operations”
  • 60. Two-phase project Will address the most urgent issue: ageing hardware HSM Hardware Refresh New features will be introduced after the hardware refresh Objective is to simplify HSM operations HSM Usability Evolution
  • 61. Where are we now? HSM Selection Program preparation SN Ph 2 Program Launch Large certificate capacity 3 to 4 boxes cluster Remote PED 2004 2005 2006 2007 2008 2009 2013 2014 2015 New HSM Selection 201..2010 2011 2012 Key Clients Consultation PSF 2013 Refresh Kick-off Collection of Customer feedback Program Preparation Shipment & Delivery Usability enhancements
  • 62. HSM box rollout timeline 201520142013 SWIFT readiness Customer shipment schedule communication Ship refresh boxes Install HSM box or implement ARG Leftover shipments Complete refresh End of Support Sept 30th End of support of current boxes Nov 15th New box ordering open May-June Shipment schedule communication Oct Early adopter phase Jan HSM Refresh shipment starts Prepare Install Complete
  • 63. Rollout process 1 2 3 SWIFT has contacted all customers with shipment schedule SWIFT will send prefilled eOrder forms Boxes will be shipped as per the shipping window 4 Customers have 6 months to install new IS6 HSM box T Shipment month T-16 Weeks Refresh Reminder Email T-12 Weeks Prefilled eOrder form via email T+6 months End of Install Window Old box replacement ends T-6 Weeks Cust confirms eOrder for customers to review and accept [12 weeks before shipment window]
  • 64. New PED required for IS6 HSM box New PED backward compatible with IS5 HSM IS5 HSM box New hardware with enterprise class server-grade components Standard 1U rack mount chassis Weight is 12.7kg (28lbs) USB to serial adapter packaged along with the boxSensor output via SNL script and SNL events (patch 7.0.25) New PED can be used locally or remotelyCurrent PED keys still valid will be refreshed with IS6 HSM box Redundancy for critical components Dual hot-swappable power supply units (450W) New decommission buttonVisual indicator (led) and an audio alarm Backward compatible with IS5 HSM box clusters  Can interoperate with old boxes  No software upgrade or certificate migration
  • 65. Ordering Things to consider  Know the shipment timeline  How many boxes and PEDs are needed  Terminate unwanted contracts  Place order 6 weeks before shipment  No PEDs shipped by default; Must be ordered Implementation Prepare  Enough rack space  2nd power supply  Familiarize with procedure  Choose refresh approach  Create plan Deploy  Collect PED keys and passwords; verify  Power on boxes before “use by” date  Refresh within 6 months  Destroy old boxes  Reboot every 12 months
  • 66. Where to find more info HSM refresh page @ HSM Refresh User Guide @ UHB
  • 67. HSM Usability Evolution Objective is to manage HSM operations more effectively by: – Simplifying day-to-day management of HSM boxes – Reducing cost & risk associated with complex processes Improve HSM usability … without compromising on security C O N S O L I D AT E D F E E D B A C K C U S T O M E R C O N S U LT A T I O N H I G H - L E V E L D E S I G N R E V I E W P O T E N T I A L C H A N G E S I N P U T O N P R I O R I T I E S
  • 68. Certificate management Manual PED operations Teams coordination Scheduling changes Installation Manual process Switching PED keys Configuring each box What did you tell us? Administration Password expiry Accounts/pwd per box Monitoring Pre-installation Limited physical access
  • 69. Remote PED Workstation USB Connection Remote PED HSM Initial Remote PED key shipped by SWIFT Initial Remote PED Secret configured by SWIFT Remote access pre-configuration by SWIFT Benefits • Allow new boxes to be remotely accessed without locally configuring a Remote PED secret • Avoid delays due to organizing on-site intervention • Enable initial Remote PED access by pre-configuring a default secret • Included in Premium+ service Initial Remote PED Access Available P+
  • 70. Unified PED token • If segregated responsibilities for each PED role, continue with current multi-keys scheme • If centralized responsibility for all PED roles, consolidate all separate keys on one unified PED token, with distinct roles • Migration to Unified PED token without re-initializing HSM box Benefits • Reduce number of keys to manage • Reduce manual operations: no need to switch between keys Two models Operational simplicity In Design Phase
  • 71. Configurable password expiry Account password expiry period currently fixed to 90 days Admin Operator Configurable password expiry period • As part of SWIFTNet Link/HSM installation and configuration, prompt user for password lifetime • Command to configure password lifetime at any time after the installation • Generate appropriate password expiry events to allow user to monitor this HSM accounts In Design Phase Benefits • Adapt password expiry to actual usage frequency & to customer policy • Reduce risk of expired password when needed in emergency
  • 72. Benefits • Simplify configuration changes • Limit risk of password de- synchronisation Accounts synchronisation between HSM boxes in cluster Synchronization between all cluster members of: • User accounts & passwords • Policies such as password • SNL registration information Accounts Synchronisation Accounts Sync Reduce risk In Design Phase
  • 73. Simplify & integrate certificate management Enhance Alliance Gateway Admin GUI • Integrate partition management with certificate management • Make it possible to initialize a partition without a PED operation • Option to combine Delete certificate with Initialize partition Alliance Gateway Admin GUI Remote PED HSM Certificate management In Design Phase
  • 74. Health Check “SWIFT audits the set-up of our platforms and operating procedures “ Recommendations to maintain or to improve availability, reliability and performances Health Check Assessment
  • 75. Application: A2A, U2A, Data storage, Transfer software … Data protection, Backups, Resiliency … Access to application (users, profiles) … Network :Routers, switches, ports & IP filtering… HSM & Certificates management processes Health Check Assessment
  • 76. HSM Training Resources 1. Tips and Tricks (Knowledge database) 2. Web Class (Operating your HSM) 3. HSM 101 – Everything you wanted to know but were afraid to ask (hands on / become an expert) 4. We can come to you (On site services)
  • 77. • Finalize your HSM refresh project plan & be ready for the pre-filled e-form from SWIFT Conclusions • Discuss with your Account Manager or your Service Manager about security improvements Refer to the HSM Refresh pages and to the guide • HSM evolution roadmap to be defined • Session materials will be available on
  • 78. Thank you
  • 79. Auditorium and Interest Sessions
  • 80. Auditorium and Interest Session • While having lunch, starting at 12:30 you can choose to participate in the following interest sessions: In Chrysler In UN
  • 81. Networking Game Find new connections (people with different colored dots than yourself, representing years attending a PSF)
  • 82. Lunch Break
  • 83. The community approach to crisis Becky Almodovar– Head of Key Client Support and Service Management Mariela Atanassova – Senior Facilitator Simulation
  • 84. Agenda • Objectives & Introduction • Team Activity • Rules of the Game • Kick-off - Report back & debrief 3
  • 85. Collaborate kəˈlabəreɪt/ - to work jointly on an activity towards a shared outcome
  • 86. The whole is greater than the sum of it’s parts
  • 87. • Sharing best practices in disaster recovery • Discussing approaches to assessing impact and prioritizing recovery actions • Exploring internal and external communication strategies • Developing community-coordinated response to crisis Session Objectives
  • 88. 1. You will be presented with a scenario. There will be different types of information that you will receive one at a time. 2. At each step of the scenario discuss in your group how each of your institutions would react at this point 3. Note down the key points you will share in the debrief 8 Rules of the game
  • 89. Three questions to discuss with your team: • Does this affect you? • What do you do? • Who do you tell? To discuss at each step of the scenario
  • 90. At the end of the scenario summarize on your report sheet: • One thing you learned • One thing that surprised you • One thing you feel was missing from the discussion • What would you now recommend to your organization to do differently? Debrief at the end
  • 91. It’s Tuesday, February 25th 2014. 8 AM GMT
  • 92. ws….Breaking News….Breaking News….Break 8:05 AM, London
  • 93. 8:35 GMT, London
  • 94. 11:30 GMT, Frankfurt
  • 95. ws….Breaking News….Breaking News….Break14:12 GMT, US
  • 96. ws….Breaking News….Breaking News….Break14:12 GMT, US
  • 97. ws….Breaking News….Breaking News….Break14:53 GMT, New York
  • 98. 14:57 GMT, New York
  • 99. ws….Breaking News….Breaking News….Break15:23 GMT
  • 100. ws….Breaking News….Breaking News….Break 17:05 GMT New York
  • 101. At the end of the scenario summarize on your report sheet: • One thing you learned • One thing that surprised you • One thing you feel was missing from the discussion • What would you now recommend to your organization to do differently? Debrief at the end
  • 102. Thank you
  • 103. Knowing your SWIFTNet recovery features Arnaud Boulnois, Head of Messaging Product Management Prakash Lele, Head of SWIFTNet Delivery Challenges with recovery procedures
  • 104. Agenda • Recovery problems • Recovery problems and retrieval options • What happens in SWIFTNet when you need to recover
  • 105. Your recovery problems, our retrieval options My interface just failed I’ve lost some messages I need to go to my DR site
  • 106. Retrieval Options on SWIFTNet • Message retrieval • generic message(s) retrieval - similar to FIN • to support investigations or message recovery • Short-term bulk retrieval • Message replay • retrieves all S&F traffic in bulk (max last 24 hrs) • allows to "fill the gap" in case of unplanned site takeover with missing traffic • ("replays") messages in an easy way • allows to "fill the gap" in case of unplanned site takeover with missing traffic
  • 108. Message retrieval • SWIFT stores message traffic in an archive when customers send traffic via a store-and-forward service • Customers can retrieve a copy of their traffic sent and/or received from the archive • Find a message e.g. dispute between sender/receiver, question from regulator, ... • lost traffic e.g. after an interface crash Typical use
  • 109. Message Retrieval Process Trigger Selection Processing Delivery Use 1 2
  • 110. Message retrieval O2M GUI 1 Will search from “Start Time” to the next 24 hours Max 10.000 messages
  • 111. Message retrieval xsys.015.001.01 Retrieval Request 2
  • 112. Features: • Each customer can retrieve their traffic (sent or received) • Production: 124 days. Pilot / ITB: 4 days • Input or output retrieval, with various selection criteria • Access control using an RBAC role Interfaces: • Interface release to submit and process retrieval requests and responses ( Alliance Access 7.0.75) Message retrieval Highlights
  • 114. Short-term bulk retrieval What • Retrieve all InterAct/FileAct of max 24 hours old • Allows to "fill the gap" if customer lost data in transit • Subscription based How • Request via system message • Delivery of traffic is bulked inside files delivered via FileAct • Requires specific development to process file contents Ongoing sync Site disaster – possible data loss SWIFT Bulk retrieval request to "fill the gap"
  • 115. SWIFTNet short-term bulk retrieval Highlights • Covers (max) last 24hrs of traffic • Single retrieval criterion: time range • Retrieves all store-and-forward traffic sent and received • usage o Customer sends a Bulk Retrieval Request system message (xsys.013.001.01). o Central system returns a Bulk Retrieval Report system message that lists the files that have been generated (xsys.014.001.01). o Files are delivered through FileAct store-and-forward in a notification queue.
  • 116. Message retrieval xsys.013.001.01 Bulk Retrieval Request
  • 118. Message replay (with MI Channel) SWIFT site1 site2 Async. copy Normal traffic delivery SWIFT site1 site2 Switch to site2 SWIFT site1 site2 Automatically resume normal traffic deliveryActivate replay to close gap
  • 119. Message replay (with MI Channel) Highlights • Integrated "replay" recovery feature: o Potential duplicate indication o Fill the gap o Normal delivery resumes automatically o Preserves message delivery order • Parameters for replay: o Timestamp o Optional: OSN(s) per SnF queue o Triggered through SAG: o Manual mode (GUI) o On-line command
  • 120. In summary Message Retrieval • Investigation or Interface recovery • Flexible • 124 days • All customers • System message or O2M screen • InterAct Store and Forward Bulk Retrieval • Recovery to other site • 24 hours • Subscribed customers • System message • InterAct and FileAct Store and Forward Replay • Recovery to other site • MIs service • Last 8 hours • Alliance Gateway GUI (or command line) • InterAct Store and Forward
  • 121. How do we support your recovery?
  • 122. The Layers of SWIFTNet SWIFT Site User SiteUser Site Network 1 ITL 2 Application 3 Service Provider User Applications SWIFTNet Components VPNVPN FW FW SWIFT OPC MV-SIPN MV-SIPN ITL: Interact Transport Layer
  • 123. SWIFTNet Messaging Platform Base PlatformServers & Storage Databases Core Messaging InterAct FileAct Added Messaging Services XML Message Validation (MVAL) Store & Forward (S&F) PublicKeyInfrastructure OperationsManagement EnterpriseDirectory OPC network MV-SIPN FIN Network
  • 124. SWIFTNet Store and Forward - Operational Topology Active DB Site-1 Site-2 Store and Forward SnF App SnF DB Standby DB Store and Forward SnF App SnF DB Replication SWIFTNet SWIFTNet MV-SIPN Store and Forward SnF App SnF DB DRI SWIFTNet Cold-start DB
  • 125. Takeover scenarios Store and Forward SWIFTNet Store and Forward - Resiliency Active DB Site-1 Site-2 Store and Forward SnF App SnF DB Standby DB Store and Forward SnF App SnF DB Replication SWIFTNet SWIFTNetSWIFTNet SWIFTNet Store and Forward SnF App SnF DB Store and Forward SnF App SnF DB 1. SWIFTNet and SnF in same site 2. Independent SWIFTNet Takeover 3. Independent SnF Takeover MV-SIPN
  • 126. Store and Forward SnF App SnF DB Store and Forward SnF App SnF DB Store and Forward - Resiliency Standby DB Site-1 Site-2 Active DB Replication SWIFTNet SWIFTNetSWIFTNetSWIFTNet Store and Forward SnF App SnF DB Store and Forward SnF App SnF DB SWIFTNet Takeover scenarios 1. SWIFTNet and SnF in same site 2. Independent SWIFTNet Takeover 3. Independent SnF Takeover 4. SWIFTNet and SnF Takeover MV-SIPN
  • 127. SWIFTNet MI Channel Gateway Active DB Site-1 Site-2 Store and Forward SnF App SnF DB Standby DB Store and Forward SnF App SnF DB Replication SWIFTNet SWIFTNet MI GTW MI GTW Store and Forward SnF App SnF DB DRI SWIFTNet MI GTW MV-SIPN Cold- start DB
  • 128. Supporting message retrieval M1 M2 M3 Sender Receiver Message(s) sent to receiver (M1, M2, M3) SWIFT Message stored in receivers Q Message(s) delivered (M1, M2, M3) c M1 M2 M3 Delivery Queue Input Archival Output Archival Message stored in input archival M1 M2 M3 Message stored in output archival Q Delivery Queue StoreDeliverProcess Pull / Push de-queues message from Q Process M1 M2 M3
  • 129. Supporting message retrieval Sender ReceiverSWIFT Retrieval Messages extracted from Input Archival Message stored in requested output Q Retrieval request M1 Input Archival Output Q Output Q File ready for delivery M1 M2 M3 Message(s) ready for delivery Message delivered BulkRetrieval Bulk Retrieval request M1 M2 M3 Messages extracted from Output Archival Message stored as file in output Q Output Archival F1 Message(s) delivered in file
  • 130. Operational Monitoring
  • 131. By SWIFT Support Americas Discover more about your PSF Americas 2014
  • 132. Download the on your smartphone Download and Search •Download Aurasma from the app store on your smartphone •Open the app & swipe through the tutorial •Do not create an account! Click ‘Skip’ at the bottom right hand corner to continue (creating an account may impact your ability to find the PSF Americas 2014 channel). Follow us •The application opens by default in camera mode; click on the “A” icon to access the menu •After a minute, click on search icon and search for “PSF Americas 2014” •Select PSF Americas 2014 channel •Click follow Watch our Videos •In the Forum, some images are defined as ‘triggers’; using the app to view these trigger images will launch a video for you to see. •Open Aurasma. You will be in ‘camera mode’. Just point your phone at the trigger image. •Double tap the image to make it full screen •Once the content is displayed full screen, it will continue playing even if you move away from the trigger image. •If you do not make the content full screen, it will stop playing as soon as you move your device away from the trigger image.
  • 133. Test It ! Once the download is completed use this picture Open Aurasma on your smartphone Point the camera at it and find more about our Forum Premium Services Forum Americas
  • 134. See more about our Products ! Follow us in and find our Auras
  • 135. Coffee Break
  • 136. Integration Portfolio and Alliance Messaging Hub Juan Martinez, Head of Applications, Integration & Partner Marketing David Fergie, System Integration Expert SWIFT direction going forward
  • 137. SWIFT Alliance Family Key evolution Alliance Access Alliance Lite2 Base Setup Parameterization Configuration Alliance Messaging Hub Ability to adapt to individual customer needs New Customization Ability to combine highly flexible platform and complex integration New Going from generic interface products to flexible platforms for delivering unique solutions Simple Medium Complex Integration capabilities Integration complexity Integration PlatformConverter
  • 138. Integration PlatformConverter SWIFT Alliance Family Product & Integration Domains Alliance Access Alliance Lite2 Integration Domain  Interface can be adapted to customer needs  Specialized integration skills required, available from SWIFT  Highly flexible and based on standard integration modelling  Faster to adapt and lower TCO compared to back-office change process  Powerful solution to replace legacy systemsIntegration capabilities Base Setup Parameterization Configuration Customization Integration complexitySimple Medium Complex Alliance Messaging Hub Product Domain  Out of the box product that can be configured to customer needs  Quick deployment and time-to-market to start adding value to business lines  All functions available at fingertips  New product release required for new functions
  • 139. SWIFT Alliance Family Integration options Customer SWIFT SWIFTNet core services (FIN + IA/FA) Lite2 Gateway HSM / SNL Access IPLA ORAuto Client Converter Alliance Messaging Hub Gateway HSM / SNL OR Access IPLA OR Alliance Remote Gateway IPLA: Alliance Access Integration Platform
  • 140. New Portfolio Positioning for high-end segment e.g. AMH for FileAct & InterAct AMH as Messaging Hub High-end or beyond Alliance Messaging Hub Alliance Messaging Hub Alliance Access --- Another SWIFT interface IntegrationRequirements Base Setup Parameterization Configuration Customization
  • 141. AMH IPLA Converter • Modular architecture • Highly customizable • Embedded in Access • Rich and flexible • Combined with cloud solution • Minimal footprint A SWIFT solution for each requirement
  • 142. AMH IPLA Converter • FileAct active/active load-balancing • FIN and SWISS domestic connectivity • SOA: AMH component for Message Entry and Validation • Funds MT/MX marketplace • Interface to RTGS & AML systems • SOA middleware to middleware integration • Corporate SAP integration for FileAct • TCO reduction by migrating existing interface to cloud • Branches to central location reporting based on FINInform A SWIFT solution for each requirement
  • 143. Alliance Integration Platform (IPLA) Payment Flow – single payment routing storage queues Alliance Access Integration Platform Ordering Bank Correspondent bank IPLA API FIN Interface store validate transform send Payment application MT103 Payment in CSV format MT103 ACK receivetransformwrite read ACK in CSV format FIN ACKProp ACK
  • 144. Alliance Messaging Hub Key Features
  • 145. Questions
  • 146. Thank you
  • 147. Managing your information security challenges Mike Fish, CIO 3 March 2014
  • 148. Closing Remarks Becky Almodovar March 3rd, 2014
  • 149. Stay in touch! Your one-stop-shop for SWIFT Training Aurasma Mobile App – “PSF Americas 2014” Using SWIFT – Certification Programme Course descriptions Course schedule eTraining portfolio Twitter @swiftcommunity - #SWIFTtraining SWIFT Training newsletter
  • 150. Let’s dine!