Keane Value Proposition to IRS Indiana Digital Government

Keane Value Proposition to IRS Indiana Digital Government Summit Bill Clarke, Director, Legacy Modernization June 22, 2009 Australia | Canada | France | India | New Zealand | Singapore | Switzerland | United Arab Emirates | United Kingdom | United States www. keane. com. © 2008 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited.

Agenda • • • Definition – What is LM? High Level Techniques When is each Technique Appropriate? Generic Program Steps Application Disposition Quadrant Success Factors Why Do LM? Success Stories Questions & Answers © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 2

What is Legacy Modernization? “The process of assessing, measuring, prioritizing and executing various techniques designed to upgrade an organizations application portfolio to take advantage of leading edge technical platforms, languages and relational database engines. ” © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 3

Legacy Modernization Techniques Features Converts Legacy Green screen to GUI Re-hosting / Screen Scraping Screen functions can be wrapped to Java or . NET components Legacy Modernization Program Some would say “lipstick on a pig”, but may be appropriate intermediate step Migration / Conversion Platform Migration Database Migration Language Migration Web-enabling/ SOA / Wrapping Re-engineering / Re-writing New Development/ Package Implementation Creating a web-based interface for legacy applications Business logic retained in legacy environment Screen interface and business logic is extracted from existing system and re-coded in modern technology Modern technology adoption (off the shelf) Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 4

Legacy Modernization Techniques Re-Hosting / Screen Scraping Legacy Modernization Program Re-hosting / Screen Scraping Migration / Conversion Why? : • Leaves existing application alone • Relatively simple to do • Relatively quick to accomplish • Good choice for applications that have a limited shelf life • Impressive to end users Web-enabling/ SOA / Wrapping Why Not? : Re-engineering / Re-writing New Development/ Package Implementation • Viewed by many as “Lipstick on a pig” approach • Can be a performance nightmare • Doesn’t show demonstrable progress Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 5

Legacy Modernization Techniques Migration or Conversion Legacy Modernization Program Re-hosting / Screen Scraping Migration / Conversion Web-enabling/ SOA / Wrapping Why? : • Preserves the application as a valuable business asset • Transfers all the business knowledge to new technology • Complements other LM approaches • Demonstrable progress into new technologies Why Not? : Re-engineering / Re-writing New Development/ Package Implementation • Expensive and time consuming • Not a good choice for low-value applications • Requires business unit involvement in testing Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 6

Legacy Modernization Techniques Web-Enabling / SOA / Wrapping Legacy Modernization Program Re-hosting / Screen Scraping Migration / Conversion Web-enabling/ SOA / Wrapping Why? : • Leaves existing application alone • Broadens the access to the application • One framework, many applications • Promotes re-use • Leverages existing investment • Use to buy time Why Not? : Re-engineering / Re-writing New Development/ Package Implementation • Viewed by many as “Lipstick on a pig” approach • Can have performance implications • Still need to maintain LM technology – puts off problems Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 7

Legacy Modernization Techniques Re-Engineering / Re-Writing Legacy Modernization Program Re-hosting / Screen Scraping Migration / Conversion Why? : • Allows complete end user control of content • Existing application generally does not meet business needs • Re-write existing functionality AND add new content Web-enabling/ SOA / Wrapping Why Not? : Re-engineering / Re-writing New Development/ Package Implementation • Expensive and time consuming • Very difficult to mine the business rules completely • Requires large investment of IT resources – major initiative Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 8

Legacy Modernization Techniques New Development / COTS / Transfer Legacy Modernization Program Re-hosting / Screen Scraping Migration / Conversion Why? : • Traditional SDLC activity • Complete content control • COTS product has high degree of applicability • Transfers can be the quickest route to production and/or compliance Web-enabling/ SOA / Wrapping Why Not? : Re-engineering / Re-writing • COTS vendor marriage • Expensive and time consuming • The degree of applicability may not be high enough New Development/ Package Implementation Transfer Any Strategy has to be viewed as a combination of functional and technical modernization © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 9

Generic LM Program Steps • Assemble Business & Technical team members • Identify the scope (both in & out) • Gather application data • User acceptance, criticality, business rule reqm’ts • Complexity, platforms, languages, data stores • General ROI information • Determine which LM technique you plan to use for each application • Create mini ROI and feasibility studies • Create Project Charters where applicable • Sequence & launch projects • Monitor & evaluate progress © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 10

Legacy Technology, Cost & Age Application Disposition Matrix § Sunset or Replace § Mgmt Rpts Convert or Migrate / Rehost Re-Host AP § § Child Support Replace or Re-Write § CMS § Billing Tax Maintain & Monitor § Shipping Functional Value & User Acceptance © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 11

Success Factors • The selected solution should be highly automated to minimize manual effort and human error • The resulting code should be easily maintained with structured code, comments and meaningful data names • Conversion of non-relational data should include a normalized database design with logical and physical models. The new database should not just copy the non-relational design • Conversion of non-relational database access should produce efficient, quality code that takes advantage of the new database design • The selected vendor should have relevant experience with both relational database, platform and language migrations. © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 12

Why Do Legacy Modernization? • • • A safe, risk averse migration to new technologies Avoidance of proprietary hardware & software costs End of the mainframe strategies Change from hierarchical to relational DBMS’s Release from dependence on legacy vendors Avoidance of end-of-life support dates Utilization of newer, more available technical resources Ability to utilize COTS packages for end user analysis Relational access allows “web-enabling” to bring the end user experience to a browser-based user interface • Extension of the ROI for mission critical applications with their associated complex business rules. © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 13

Success Stories Commonwealth of Virginia Conversion on the mainframe IMS to DB 2 – Child Support Application • 1, 500 programs • 22 months • $3. 7 M • Solid relational design • IMS navigation replaced with efficient SQL • Batch window improved by 30%+ • Online prepped for Web. Sphere / Java conversion • Excellent IV&V report by North Highland Group © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 14

Success Stories GMAC Residential Finance Migration from mainframe COBOL IMS to Oracle /. Net • 500 programs • $900 k • UI (IMS DC) becomes ASP. net with C# code behind • Business logic contained within Fujitsu Net. COBOL • Very technical major migration • End of Mainframe project © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 15

Success Stories U. S. Air Force – ES-S Supply • Wrapping the existing Unisys DMS 1100, COBOL application • Presenting the system on the USAF’s GCSS-AF Framework • Standard SOA, J 2 EE technology with Web. Sphere MQ • Standard XML interfaces exposed by messaging/web service adapter • ES-S is a pattern based J 2 EE application that runs on Web. Sphere 6. 1 and Oracle 10 g • Delivers the ability to query, order, ship, and monitor items from anywhere in the world at over 300 USAF bases © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 16

Success Stories Geico Insurance PL/1 to COBOL – Billing System, language change • 600 programs • $1. 2 M • PL/1 to COBOL, IMS to DB 2 • PL/1 talent difficult to find, current staff retiring • PL/1 converted to structured, maintainable COBOL code • Hierarchical to relational DBMS • Delivered on time and on budget © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 17

Questions & Answers ? Thank You Bill Clarke Keane Federal Systems Director, Legacy Modernization Australia | Canada | France | India | New Zealand | Singapore | Switzerland | United Arab Emirates | United Kingdom | United States © 2007 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc. Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. April 10, 2008 18