1. © Talaris Limited 2011 Slide 1 The benchmark in teller connectivity software

2. © Talaris Limited 2011 >Agenda –Roadmap Review –Review of Deployment Scenarios –Integration Options –Licensing –Competitive Overview –Level 3 Support

3. © Talaris Limited 2011 CashInsight Assure Roadmap

4. © Talaris Limited 2011 Version Numbering System >Three digit numbering system –Major.Minor.Patch i.e. 1.4.5 >Major –Significant Feature Content and/or Database Structure Change >Minor –Additional Feature content –Defect corrections >Patch –Defect corrections for customer impacting defects >Four digit releases (i.e. 2.0.0.5) are internal test releases and should never be given to a customer

5. © Talaris Limited 2011 Roadmap >Version 1.0 - April 2010 >Version 1.1 - July 2010 >Version 1.2 - August 2010 >Version 1.3 - February 2011 >Version 1.4 - August 2011 >Version 2.0 - November 2011 >Version 2.1 - target January 2012 >Version 3.0 - target 1H 2012

6. © Talaris Limited 2011 >Stand alone >Extensive transaction set –Deposit, Dispense, Count, Exchange, Vault Buy/Sell, Audit, Empty, Load >Branch wide with database –Reporting & visibility of all workstations >Innovative GUI –Sidebar & activity windows allow multiple activities >Remote transactions –Locations in the branch without a device can still benefit from teller automation >Plus –Role based configuration –Reports for User and Supervisor –Rapid Audit process –Citrix support & more –Denominate Coin dispenses –Multi-currency Exchange –Multi-language support –Third Terminal support >Client API Roadmap – Version 1.0 Through Version 1.2

7. © Talaris Limited 2011 Major Features Summary – Version 1.3 >Active Directory Integration >SQL Server Database support >Manager API >XML message format in Client API >Linux >Time sensitive Dispense limits

8. © Talaris Limited 2011 Minor Features Summary – Version 1.3 >Current Username displayed in sidebar and activity windows >Automatic logout after period of inactivity (configurable) >Installation and upgrade improvements –Moved data files out of ‘Program Files’ >Additional permissions for Client API to limit transactions originated from sidebar >Improved error recovery >Subtotals in the Balance Report

9. © Talaris Limited 2011 Roadmap – Version 1.4 >LDAP >Recalculate the mix on second screen of Withdrawal >Egypt Customer Requests –Back button on second screen of Withdrawal –Note Counts on final deposit screen –Transaction detail, added ‘Amount Requested’ –Print buttons on transaction Summary Screens –‘Select All’ RSMs on Empty & Audit transactions >Installation improvements

10. © Talaris Limited 2011 Roadmap – Version 2.0 >Major features –STC Limited to Multi-denomination cassette –Continue additions to Manager API –Compact Vertera –Engineering support for next generation Recycler –Password rules >Minor features –Limit number of entries in selection field on Balance sessions –Display device Firmware version on the system status screen –User-defined names for mixes –Screen positions saved by workstation (Citrix)

11. © Talaris Limited 2011 Roadmap – Version 2.1 (expected name) >Coin recycler support >Redesigned My Transactions report >On Audit screen, highlight RSMs with possible accounting errors >MySQL support >LDAPS support >Silent install

12. © Talaris Limited 2011 Roadmap – Version 3.0 (expected name) >Redesign Properties screen >Enterprise deployments –Introduce concept of a branch –Load balance the server side components >Export and Import role definitions >Search My Transactions/All Transactions >HTTPS >STC, single denomination cassette >License expiration warnings and renewal grace period

13. © Talaris Limited 2011 Roadmap – Summary >Version 1.0 – 1.2 –Core capabilities >Version 1.3 –Large release introducing new core capabilities (AD, SQL Server, Manager API) –Continue enhancement of the previous core based on feedback >Version 1.4 –Minor enhancements for regional requests –Installation improvements >Version 2.0 –Major new features (STC, Password rules, Compact Vertera) –Continue minor enhancements and bug fixes >Version 2.1 –Coin Recycler >Version 3.0 –Enterprise Level Deployments

14. © Talaris Limited 2011 Deployment Scenarios

15. © Talaris Limited 2011 Architecture Components

16. © Talaris Limited 2011 Architecture Benefits >Designed to grow with our needs in the future >N-tier vs. Client-Server –Flexibility to distribute components as needed –Will provide the framework for fully scalable system >Cleanly supports multiple integration options >Supports single PC, single device to Branch-wide system >Allows us to support multiple Client applications concurrently

17. © Talaris Limited 2011 Deployment Scenarios >Workstations Only >Branch Server Deployment >Branch Server with RS232 >Branch Server Deployment With Active Directory >Enterprise Deployment >Citrix

18. © Talaris Limited 2011 Workstation Only Deployment

19. © Talaris Limited 2011 Analysis of Workstation Only Deployment >Why? –No branch server available –Quick installation and configuration for pilot or proof of concept –Bank will not allow the non-certified software on their network >Drawbacks –Main PC is powered down or goes into sleep mode takes down branch –Effort to replace the main PC –Firewalls on PCs will require extra configuration work >Other Considerations –Dual-core PC has plenty of capacity to support multiple devices (2-3) and workstations (4-8), while running the Bank’s teller application –Easy for branch staff to restart services –Easy to support RS232 connections

20. © Talaris Limited 2011 Branch Server Deployment

21. © Talaris Limited 2011 Branch Server (RS232) Deployment

22. © Talaris Limited 2011 Branch Server Deployment With Active Directory

23. © Talaris Limited 2011 Analysis of Branch Server Deployment >Preferred Solution >Benefits –Eliminates accidentally powering down the “Application Server” –Typically puts services on most powerful computer in the branch –Fits IT models for branch level applications –IT can support application without interrupting a teller workstation –Using AD, user’s assigned role follows them from branch to branch –Simple to install and configure with all components on one system >Drawbacks –Requires IT to restore the application IT needs to understand the impact of restarting services –Dedicated IP for device connections –Application is down if the network is down

24. © Talaris Limited 2011 Enterprise Deployment – Current Version

25. © Talaris Limited 2011 Analysis of Enterprise Deployment >Similar to Preferred Solution >Benefits –Eliminates accidentally powering down the “Application Server” –Partitions load by branches –Fits IT models for branch level applications, including virtual servers –IT can support a single branch without interrupting service to all branches >Drawbacks –Potential latency of network communications (bandwidth to branch) –More opportunities for configuration errors Branches no longer logically grouped by physical locations Consider components that need to properly match up (client -> managers, workstations -> devices, managers -> databases) –Number of servers required >Not aware of any installations following this model

26. © Talaris Limited 2011 Enterprise Deployment – Projected

27. © Talaris Limited 2011 Analysis of Enterprise (Future) Deployment >Positives –Eliminates single points of failure –Components scale to meet the performance demands –Enterprise data in single database –Easily add branches and new devices –Users data follows the user from branch to branch –Centrally managed Role permissions >Drawbacks –User Management is more complex –Upgrade process will be more complex –Branch Staff may be less autonomous in supporting themselves

28. © Talaris Limited 2011 Enterprise Deployment – Current Version

29. © Talaris Limited 2011 Citrix Deployment

30. © Talaris Limited 2011 Analysis of Citrix Deployment >Benefits –Eliminates accidentally powering down the “Application Server” –Fits IT models for Citrix applications, including virtual servers and client as published application –IT can support application without interrupting a teller workstation >Drawbacks –Data reports show all branches and devices –Limit on the number of clients that the CashInsight Manager can support –Single CashInsight Manager or DeviceController failure affects all branches Limited to single DeviceController in this configuration –Potential latency of network communications (bandwidth to branch) –Socket interface to Client API

31. © Talaris Limited 2011 Integration Options

32. © Talaris Limited 2011 CashInsight Assure Flexible Delivery Graphical Interface Assure transaction screens driven by your banking system Manager Programming Interface Transactions, Cash Management and Report functions integrated in to your banking system Your Banking System Cash management, Reports, Configuration, Device management Full Software Application Configuration and Device management Lutzwolf DeviceController J/XFS Middleware Layer Cash management, Reports, Configuration, Device management Configuration and Device management

33. © Talaris Limited 2011 Where do the APIs Connect Device Starter Device DeviceController CashInsight Manager CashInsight Client API Sockets File Bank’s Software Manager API

34. © Talaris Limited 2011 Client API Options >CashInsight Assure Graphical API has two different channels of communication: –TCP/IP Sockets –Text Files Semi-colon separated values (deprecated) XML >TCP/IP Sockets: Bank Application opens a network connection with Assure, and then sends the Command Data through it. Assure receives the Data, performs the transaction, and then responses back to the Bank Application through the same connection with the Result Data of the operation. >Text Files: Bank Application creates a text file with the Command Data in it, and copies the file to a specific folder on a workstation. Assure gets it, performs the transaction, and then creates another text file in the same folder with the Result Data of the operation as a response to the Bank Application. >In both cases, Command Data and Result Data have the same format, in order to simplify the work of SW Development & Support. >Client API off by default

35. © Talaris Limited 2011 Client API >Why? –Quick and Simple –Limited programming within the Teller application –Takes advantage of the built-in error handling within Assure –Roles, Permissions, Reports, Balancing and Device Management are all immediately available –Sidebar still visible >Disadvantages –Different look & feel from Teller application –Teller is still switching between applications for some functions –Balancing not tightly integrated –User accounts maintained in two systems –Application has limited control over transactions Bottom Line: Customer is still receiving 90+% of the benefits of TCA

36. © Talaris Limited 2011 Manager API >Why? –Bank wants single look & feel in the user interface –Provides more control over the transaction flow –Business logic for Roles, Permissions, and Reports is reused –Balancing can be tightly integrated –Sidebar can still be available for Device Management and administrative functions >Disadvantages –Larger investment in time and resources to get system running –User accounts maintained in two systems –Same performance & data concerns as the Deployment models

37. © Talaris Limited 2011 DeviceController API >Why? –Bank wants single look & feel in the user interface –Provides full control over the transaction flow and error handling –Fully integrates with Teller system’s roles and permissions –All TCA functions tightly integrated with Bank’s Teller Application –Lower licensing cost –DeviceController scaling >Disadvantages –Much larger investment in time and resources to get system running –Can prove difficult for integrators to get error handling and transaction processes correct

38. © Talaris Limited 2011 Licensing System

39. © Talaris Limited 2011 Licensing – Why Do We Need It? >Talaris has made a large investment in creating our own software solutions >Company expects a return on this investment >Software adds value to the TCA Solution >Software is a key component for Talaris’ growth strategy >License and software maintenance revenue funds continued development and support of the solutions

40. © Talaris Limited 2011 Licensing Model >CashInsight Assure is licensed per device –Unlimited clients IN THE BRANCH >Model of Key and Activation –Similar to model used by Microsoft and other commercial software applications >2 Keys required for properly licensed installation –License Key –Activation Key

41. © Talaris Limited 2011 Licensing – License Key >License key per customer/location >Data embedded in the key –Customer ID –Maximum number of devices (only applies until activated) –Expiration date >Intended to support pilots and initial installation –Key set to expire in 90 days –Renew for 90 days

42. © Talaris Limited 2011 Licensing – Activation Key >Linked to specific License Key >Linked to Hostname of DeviceController computer >Enterprise Keys available for large purchases

43. © Talaris Limited 2011 Licensing – Acquiring Keys >License Key –Provide number of devices distinguishing between recyclers and dispensers –Provide Customer information Name Address >Activation Key –License Key –Hostname of DeviceController >Email Eric Favaretto and Doug Wielard –eric.favaretto@uk.talaris.com, doug.wielard@us.talaris.comeric.favaretto@uk.talaris.comdoug.wielard@us.talaris.com >ACTIVATION KEY REQUEST WILL TRIGGER INVOICE TO THE REGION –Eric may request proof of customer order

44. © Talaris Limited 2011 Competitive Comparison

45. © Talaris Limited 2011 CashInsight Assure COMPETITIVE ANALYSIS - Global CashInsight™ Assure NCR TCC™Compuflex WinTCR Wincor ProAKT Development Language JavaC++C/C++C++ BRF/Multi currency Yes NoYes Thin-client support YesLimited Yes Standards Based Yes (J/XFS, JDBC) No Active Directory YesLimitedNoYes Data Storage Derby (SQL) Database or MS SQL Server Flat files – 30 day cycle Flat filesSQLite or PostgreSQL Screen Scraping YesNoYes Step In YesNo 3 rd Workstation Yes NoYes Multi-language Yes NoYes Multi- OS YesNo

46. © Talaris Limited 2011 CashInsight Assure Comparisons – North America CashInsight™ AssureNCR TCC™Compuflex WinTCR Cash Inventory visibility Individual device and all branch devices Individual deviceRequires added cost Cashview application Multiple balancing options Yes No Flexible, robust permissions Yes No Optimized audit process YesNo Supports thick/thin clients (Citrix) YesLimited Denominated coin dispense Yes No Imbedded Talaris Best Practices YesLimitedNo Auto finish Yes Database files YesNo (flat files, 30 day storage)No (flat files with no limit) Active directory Yes No Supports integration w/out additional license purchase Yes No

47. © Talaris Limited 2011 CashInsight Assure Comparisons (2) – North America CashInsight™ AssureNCR TCC™Compuflex WinTCR GUI w/cascading style sheets (HTML) YesNo Operating system(s) Windows or LinuxWindows Multi Vendor Support Yes (Special License)LimitedYes (Special License Req’d) Automix Yes Yes (1 only) Custom mix Yes Hot keys Yes Multi language Yes No Multi currency Yes No Part of application suite YesNo

48. © Talaris Limited 2011 Level 3 Support

49. © Talaris Limited 2011 Level 3 Support Organization >James Long – Manager >Wes Love – Support Analyst >Open Position – Actively recruiting person in North America –Seeking Spanish or Portugese speaker

50. © Talaris Limited 2011 Level 3 Support Services >Escalation point for customer issues >Support for Pre-sales questions >Training Program >Mantis Administration

51. © Talaris Limited 2011 Mantis >Our defect tracking system >Development team uses for feature planning and release planning >Project set up for each Region –Enter customer issues –Submit Feature requests –Track your regional open issues >What Mantis is NOT –Is not the system for entering Pre-sales questions. Use email to L3. –Is not the system for asking questions about how CashInsight Assure functionality

52. © Talaris Limited 2011 Miscellaneous

53. © Talaris Limited 2011 Installation and Operational Items to Watch >High capacity vs Low capacity Vertera –Now in configurator –Configurator now in Start menu >Configuring non-adjacent workstations >DeviceController name in the Properties tab >Defining mixes in older releases use currency code from devicecontroller.properties >Transaction screens close immediately when queuing transaction >Currency list changes after installation >Installing two devices with different currencies (Coin & TCD) >Firewalls >Client requires network connection, even on single PC installation –Microsoft loop-back adapter as work-around >Role Permissions

54. © Talaris Limited 2011 Other Projects >Security / Vulnerability Testing >Network measurements (needed) >Performance Testing >CashInsight Station –Mix definition tool –Configuration management –Database management tools

55. © Talaris Limited 2011 Simple, Flexible, Comprehensive