The Legacy Application Modernization Benchmark Report. Transforming Mainframe, AS/400, and Unix Applications in an SOA World

Transcription

1 The Legacy Application Modernization Benchmark Report Transforming Mainframe, AS/400, and Unix Applications in an SOA World September 2006

2 Publication Partners This research report was made possible, in part, with assists from the following media organizations that helped distribute the survey to their readers and web site visitors. Through its industry-respected publications Insider Weekly for iseries Managers and iseries 400 Experts Journal, and now with an exclusive series of in-depth technical anthologies covering topics like i5/os, security, WebSphere, SQL, and RPG, iseries 400 Experts provides you with practical, how-to advice and important management data and insight you need to keep your technical skills and market knowledge up to date. For more information, call or visit Business Integration Journal is the only publication that focuses on using technology to optimize business processes, which include both human and application interactions, from process analysis to end-to-end monitoring. For more information, visit: z/journal is the leading publication that focuses solely on providing how-to information for users of IBM mainframe computer systems. For more information, visit: Aberdeen Group i

3 Executive Summary B usinesses have discovered the service-oriented architecture (SOA) as the future technological underpinning of enterprise information technology. In fact, 90% of respondents to Aberdeen s survey for the recent benchmark report, Enterprise Service Bus and SOA Middleware, said they will end this year with experience in SOA planning, design, or programming. While SOA is revolutionizing how distributed computing is organized and delivered, it opens up both opportunities and challenges in extending the life of legacy application investments. The global economy runs on legacy systems both the software and hardware that represent hundreds of billions of dollars in investments that enterprises have made over decades. This leads to two major pressures on technology executives: They want to squeeze all the value they can out of this technology, especially those that are mission-critical, and They need to integrate legacy applications to improve business process visibility. However, the first pressure complicates the second. And enterprises face additional pressures, such as extending business processes over the Internet to B2B customers, suppliers, and business partners, as well as pressures associated with competition, globalization, and regulatory compliance. Yet, the key reasons for moving to SOA, as well as the approaches companies use in incorporating their legacy applications in an SOA, vary depending on the hardware platforms they use: IBM System z mainframes, mid-range System i and AS/400, and Unix. As a point of clarification for this report, legacy modernization has two different meanings: (1) modernizing a legacy application s software so that it s no longer considered a legacy, and (2) the SOA enablement of a legacy application. While the chief focus of this report is on the second definition, readers must be aware that some in both the user and vendor communities can treat these meanings as being mutually exclusive. Key Business Value Findings Here are some notable findings from Aberdeen s survey: Two-thirds of Best in Class companies are working on incorporating legacy applications and data into their SOAs, compared with only 37% of all survey respondents. The Best in Class also exhibit a stronger commitment to SOA as an IT strategy, as well as a commitment to keeping as much of the SOA enablement work inhouse as possible. The ROI for Best in Class companies is more than two-thirds higher than that of Industry Average performers. Close to 30% of enterprises running on mainframe platforms reported very good results in modernizing their applications for SOA while only 6% reported poor ii Aberdeen Group

4 results. However, none of the survey participants in mainframe shops reported very good results in overall service delivery improvement to the business. Among mid-range System i and AS/400 companies, one-quarter cited very good results in modernizing their applications for SOA and 43% reported very good results in overall IT service delivery. More than a quarter of System i respondents delivered very good service delivery results to the business, the best of the three platforms examined. About half of survey respondents whose companies use Unix platforms reported very good results in modernizing their applications at the IT level, with 29% achieving very good results in service delivery. Implications & Analysis Most enterprises, especially in the mid-market, opt for an extend/surround legacy approach. In this strategy, applications that cannot be modernized for economic, technological, or risk reasons, are extended or surrounded with new SOA middleware. Enterprises must measure success through the metrics that correspond closest to the chief drivers behind their strategies. SOA modernization challenges and lessons learned relate to company size and industry segment. Recommendations for Action Enterprises must tailor their legacy application strategies based on their applications hardware platform and maturity level within Aberdeen s Competitive Framework. There is no one size fits all modernization strategy. Best in Class companies must focus application modernization on lowering longterm IT integration costs as those costs represent 40% of the IT budget. Industry Average companies need to prioritize their modernization initiatives by the value an application delivers to the business. Laggard companies must determine whether they re allocating enough budget. Close to half of the companies represented in the survey will spend at least $500,000 of their IT budgets on legacy application modernizations. Aberdeen Group iii

5 Table of Contents Publication Partners... i Executive Summary... ii Key Business Value Findings... ii Implications & Analysis...iii Recommendations for Action...iii Chapter One: Issue at Hand... 1 Legacy Modernization Strategies... 2 Technology Modernization... 2 Replace... 3 Aberdeen s Maturity Framework for Legacy Modernization... 3 Learning from the Best in Class... 4 Chapter Two: Key Business Value Findings... 5 Modernization Strategies by Platform... 8 Mainframes... 8 Mid-Range System i and AS/ Midrange Unix Chapter Three: Implications & Analysis What s the Defining IT Metric for SOA Modernization? Modernization Project Challenges by Company Size and Industry Modernization Lessons Learned How Application Modernization Experiences Differ Chapter Four: Recommendations for Action Technology Considerations by Approach Recommended Actions by Organizational Maturity Appendix A: Research Methodology Aberdeen Group

6 Table of Contents Figures Figure 1: Timeframes for Finishing Legacy Application and Data Modernizations... 5 Figure 2: Top Business Processes Targeted for Initial Legacy Modernizations... 6 Figure 3: Strategic Actions in Addressing and Implementing Legacy SOA... 7 Figure 4: Respondents Choices of Legacy Modernization Approaches Figure 5: Key Legacy Modernization Drivers, by Industry Group Figure 6: Success Ratings in Service Improvements Figure 7: Modernization Project Challenges by Company Size Tables Table 1: Top Drivers for Embracing SOA... 1 Table 2: Top Drivers by Hardware Platform (Multiple Choice)... 2 Table 3: Competitive Framework for Legacy Application Modernization for SOA... 7 Table 4: Legacy Modernization Strategies for IBM System z Mainframe Platforms... 8 Table 5: Legacy Modernization Strategies for IBM System i and AS/400 Platforms... 9 Table 6: Legacy Modernization Strategies for Unix Platforms Table 7: Lessons Learned by Company Size and Challenged Industry Table 8: Comparison of Legacy Application Technology Approaches Aberdeen Group

7 Chapter One: Issue at Hand Key Takeaways Most respondents cite improving IT delivery of changes to the business and lowering integration costs as the top drivers in embracing SOA. Enterprises want to squeeze all the value they can get out of their legacy IT systems, especially those that are mission-critical. The key reasons for moving to SOA vary depending on the hardware platforms enterprises use. Thus, approaches will also vary depending on the platform. B usinesses are moving en masse toward the service-oriented architecture (SOA) as the technological underpinning of enterprise information technology. In fact, 90% of respondents to Aberdeen s survey for its recent report, Enterprise Service Bus: An SOA Middleware Foundation, said they will end this year with experience in SOA planning, design, or programming. While SOA is revolutionizing how distributed computing is organized and delivered, it opens up both opportunities and challenges in extending the life of legacy application investments. The global economy runs on legacy systems both the software and hardware that represent hundreds of billions of dollars in investments that enterprises have made over decades. This leads to two major pressures on technology executives: They want to squeeze all the value they can out of this technology, especially those that are mission-critical, and They need to integrate legacy applications to improve business process visibility. However, the first pressure complicates the second. And enterprises face additional pressures: extending business processes over the Internet to B2B customers, suppliers, and business partners, as well as pressures associated with competition, globalization, and regulatory compliance. The cure, at least from the vantage point of most global enterprises, is the SOA, which most survey respondents for this report see as a path to improving IT time to deliver changes to the business and lowering IT integration costs (Table 1). Table 1: Top Drivers for Embracing SOA Drivers % of Respondents Improving IT time to deliver changes to the business 66% Lowering IT integration costs 53% Lowering IT application maintenance costs 44% Consolidation of IT infrastructure 37% Aberdeen Group 1

8 But priorities can change depending on the hardware and operating system platform in use. The survey that formed the basis of this report asked respondents which hardware platforms their organizations use. We found that among users of these three major platforms IBM System z mainframe, IBM System i and AS/400, and Unix (Fujitsu/Siemens, HP, IBM, SGI, Sun, etc.) there are different emphases among the key business drivers (Table 2). Table 2: Top Drivers by Hardware Platform (Multiple Choice) Drivers Mainframe System i, AS/400 Improving IT time to deliver changes to the business 58% 61% 80% Lowering IT integration costs 65% 45% 55% Lowering IT application maintenance costs 45% 39% 50% Consolidation of IT infrastructure 35% 26% 55% Unix As a point of clarification for this report, legacy moderinzation has two different meanings: (1) modernizing a legacy application s software so that it s no longer considered a legacy, and (2) the SOA enablement of a legacy application. While the chief focus of this report is on the second definition, readers must be aware that some in both the user and vendor communities can treat these meanings as being mutually exclusive. Legacy Modernization Strategies For this report, Aberdeen took a different approach in examining enterprises strategies in incorporating legacy applications into their SOAs. We asked separate questions for respondents in each of the three major hardware platform groups. To respond to the drivers listed in Table 2 and extend the productive lives of their legacy applications, enterprises use one or more of four technology strategies: modernize, extend, surround, or replace legacy platforms into Services-Oriented Legacy Applications (SOLA). Technology Modernization Modernizing legacy applications to SOAs means opening them up to web services and SOA middleware such as an enterprise service bus (ESB) and services registration in an SOA repository. The implication is that the applications stay on their current platform and are refurbished as composites in application services, including web services, which may be distributed on or off the legacy platform. However, modernization is also used with replacement (see below) strategies to port an application to a new platform. The first step in modernizing to SOA is often the modernization of pre-relational databases and file structures such as IMS, VSAM, IDMS, Adabas and Datacom, along with their proprietary programming languages, to relational database processing and newer languages. This modernization is accomplished with automation to convert the existing program logic from one programming language to another, and to port data (and databases) to a new operating environment and database manager. Organizations benefit greatly when the conversion also includes the exposure of the new database layers and logic layers as services in their SOAs. 2 AberdeenGroup

9 Modernization to open applications and data access to web services and SOA middleware can be achieved by programmers using tools or manually. Extend and Surround Applications that cannot be modernized for economic, technological, or risk reasons, can be extended or surrounded with new SOA middleware. They may be implemented on the legacy platform as extensions, or off the platform. For companies looking to extend on the current platform, the message is clearly an increased investment in the legacy platform. However, the alternative surround approach to extension largely leaves the existing application and platform intact by doing the legacy-to-soa translation work off the legacy platform. In both the on- and off-platform approaches, the solution is a software translation engine that communicates with the legacy application using native and existing technology. These technology approaches include: Messaging, such as IBM s MQ, CTG, and IMS Connect or enterprise application integration (EAI) technology. APIs: legacy application programming interfaces. Files and databases: communication via files or transactions left in a database. Data Adaptation: typically uses user interface screens of data instead of messages to manipulate information to and from the legacy application. For many larger companies with legacy applications that literally define the business and the business process, extend or surround approaches present a powerful business case, primarily because they can leave the existing application and platform in place. Replace A common perception is that it s patently impossible to replace the billions of lines of code that represent the business processes of the Global 5000 companies. If those programs are to be rewritten by human programmers, even offshore, we would be leading a chorus of naysayers. The solution for some companies and their applications is automated logic and data definition extraction from existing applications, or full automated conversion of the databases and programs to new technologies and languages. Replacements can be off the current hardware platform if a platform migration is included with the application modernization. Replacement can also include replacing obsolescent custom applications with new third-party applications to perform the same business functions. Aberdeen s Maturity Framework for Legacy Modernization In this survey, we asked targeted questions of respondents in each of the three hardware platform categories about the four strategies they were using, the reasons behind the strategies, the challenges in executing those strategies, and the responses to those challenges. This will replace the PACE framework Aberdeen uses for most of its benchmark reports. Through these findings, we hope to offer not only broad insight on moving legacy applications into an SOA, but more specific insight readers can use to assist in their Aberdeen Group 3

10 strategic planning or compare their experiences with those of the companies represented in the survey. Learning from the Best in Class Aberdeen s Competitive Framework for this report can help companies benchmark their business processes, organization, internal knowledge, and performance metrics against those of companies called Best in Class that exhibit best current practices and yield the best results in migrating legacy applications to their service-oriented architectures. From the results of this survey, Aberdeen came to the following conclusions about Best in Class enterprises: 1) They re achieving moderately or very satisfactory results in their modernizations; 2) Beyond resources, they see no major barriers to re-architecting applications under an SOA; 3) Their key metric is lowering IT integration costs; and 4) They re achieving at least 29% ROI on legacy application investments and averaging 42%. Competitive Framework Key The Aberdeen Competitive Framework defines enterprises as falling into one of the three following levels of practices and performance: Best in Class (20%) practices that are the best currently being employed and significantly superior to the Industry Average Industry Average (50%) practices that represent the average or norm Laggards (30%) practices that are significantly behind the average of the industry Readers of this report will also be able to gauge what kinds of tools enterprises are using or planning to use to assist in their migration strategies, as well as the deployment scope of those tools. 4 AberdeenGroup

11 Chapter Two: Key Business Value Findings Key Takeaways Two-thirds of Best in Class companies are working on modernizing legacy applications and data into their service-oriented architectures, compared with only 37% of all survey respondents. Best in Class companies are more likely to include multi-process applications as part of their migration strategies. The Best in Class also exhibit a stronger commitment to SOA as an IT strategy, as well as a commitment to keep as much of the SOA enablement work in-house as possible. The ROI for Best in Class companies is more than two-thirds higher than that of Industry Average performers. A s we noted in Chapter One, nearly every organization has discovered the SOA and just about all are moving rapidly toward adoption. In fact, 37% respondents to this survey said they plan to complete modernizing their legacy applications and data to their SOAs within a year (Figure 1), and another 50% will follow within five years, leaving 13% of respondents companies with no firm plans for a legacy migration strategy. Still, more than 80% of respondents companies plan to finish within three years. Figure 1: Timeframes for Finishing Legacy Application and Data Modernizations 50% 45% 40% 35% 30% 25% 20% 15% 10% 5% 0% 15% Within 6 months 44% 22% 13% 6% Within 1 year Within 3 years Within 5 years No firm plans Best in Class organizations are a step ahead in their SOA plans. Half of Best in Class respondents plan to complete their SOA modernizations within six months; two-thirds within a year. And, they are more apt to modernize applications that cover a wide range of business processes rather than take a more granular approach (Figure 2). And, the Best Aberdeen Group 5

12 in Class are more than twice as likely to modernize applications used in quality control work. However, the Best in Class place just as equal an emphasis as all other companies on customer service processes. This reflects a prevalent business trend of using information technology to improve customer retention and grow the customer base to boost revenue. The fact that nearly half of the Best in Class are targeting a wide swath of business processes is evidence that they place a slightly higher emphasis on managing and monitoring business processes as a way to react quickly and more efficiently to changing market dynamics. (See Aberdeen s recent Business Process Management Benchmark Report for more details.) Figure 2: Top Business Processes Targeted for Initial Legacy Modernizations 60% 50% 40% 30% 20% 10% 0% 36% 53% Many applications for many business processes 43% 35% Customer service 29% 29% 29% 25% 25% 26% 24% To further meet the legacy application migration drivers listed in Chapter One, enterprises can utilize sev- Good development and migration software tools for programmers are as imeral strategic actions, the most common among them the choosing of portant as radar to an air traffic controller. You won t be very job-effective with- SOA development and modernization tools and creating a composite out them. services architecture and roadmap. Best in Class organizations lean toward two other strategies: engaging ~ Chemical company executive an IT services partner and choosing strategic SOA technology vendors (Figure 3). But about one-third of Best in Class respondents to Aberdeen s survey cite the creation of a separate SOA development environment while largely eschewing outsourcing the work. This indicates that these leading organizations would rather keep the work inhouse as a strategic IT project. Recent Aberdeen studies that focused on IT outsourcing found that many companies especially the Best in Class tend to outsource tactical work (e.g., one-time application language or database migrations) and leave the strategic stuff in-house. 11% Procurement Finance Supply chain Quality control All Respondents Best in Class 6 AberdeenGroup

13 Figure 3: Strategic Actions in Addressing and Implementing Legacy SOA Increase training and staff skills 31% 42% Create a composite services architecture and roadmap Create a separate SOA development environment 25% 18% 44% 52% Engage an IT services partner to assist 38% 32% Choose SOA development and migration tools 55% 63% Choose strategic SOA technology vendors 44% 39% All Respondents Best in Class 0% 10% 20% 30% 40% 50% 60% 70% These findings, as well as those in Table 3, reflect a stronger commitment to SOA by Best in Class organizations and a preference to rely on internal skills to execute their legacy migration strategies. That has paid off in better financial performance over those of Industry Average and Laggard organizations. In this study, Best in Class organizations are achieving better than a 28% ROI and averaging 42%. Other recent Aberdeen IT studies show the Best in Class achieving application maintenance cost reductions of 15% of the IT budget and dedicating 11% more of the IT budget to line-of-business innovations. Table 3: Competitive Framework for Legacy Application Modernization for SOA Best in Class Industry Average Laggards Barriers Some cite barriers, but 44% cite only a lack of resources to execute on their commitment to SOA Performance Metrics ROI for legacy SOA application projects 42% on average IT software maintenance costs as % of IT budget 24% on average Expense decrease from SOA 15% on average Close to half cite lack of skills and training in SOA ROI for legacy SOA application projects 22% on average IT software maintenance costs as % of IT budget 22% on average Expense decrease from SOA 8% on average Half cite lack of skills and training in SOA, as well as resistance due to the cost of enabling services ROI for legacy SOA application projects 12% on average IT software maintenance costs as % of IT budget 22% on average Expense decrease from SOA 5% on average Aberdeen Group 7

14 Best in Class Industry Average Laggards Technology Approach Most will acquire new SOA development tools. There is also a strong preference to use internal programmers to make changes manually Split between using internal programmers to make changes manually and bringing in contractors or consultants to help. Slightly less than half will acquire new SOA development tools Strongest approach is to use software adapters that come with SOA software middleware products to connect to legacy applications. They re less likely to invest in SOA development tools or use automated migration tools. Modernization Strategies by Platform For the rest of this chapter, we examine the legacy modernization strategies undertaken by companies with mainframe System z, mid-range System I (i.e., AS/400), and Unix platforms. In each section, we summarize: Approaches: The technology strategies in each platform and the proportion of respondents that chose each approach; Key Reasons: Why they chose the approaches; Challenges: The key challenges survey respondents cited in undertaking an approach; and Responses: How they overcame the challenges. Mainframes Close to one-third of survey participants report very good results in achieving their mainframe modernizations; none report poor results. About 45% report very good results in the database/information management part of their migrations. About 20% had problems and report poor results with SOA development tools, compared with the 11% that had very good results (Table 4) What stands out was that none of the survey participants reported very good results in the overall service delivery improvement to the business as a result of modernization work, which contrasts with the better results reported by companies using System i and Unix platforms. In follow-up interviews, application and business process complexity was cited as the key reason it may be difficult to change IT delivery to line-of-business units in mainframe migrations that do not also include business process transformation. Table 4: Legacy Modernization Strategies for IBM System z Mainframe Platforms Approaches Key Reasons Challenges Responses 8 AberdeenGroup

15 Approaches Key Reasons Challenges Responses Extend/surround on mainframe (31% of respondents using mainframes) Extend/surround off mainframe (19%) Replace on or off mainframe (35%) Modernize with automation or manually (15%) Management and control facilities for existing applications are better on mainframe Performance is better doing it this way Economics are better We keep loads off the mainframe if we can avoid it Mainframe replacement strategy Modernize home-grown apps off the mainframe Replace databases or old languages during migration Management and control facilities for existing applications are better on mainframe Applications are key composite piece of SOA strategy Unknown value for ROI/ROA Too many different application systems to integrate Lack of staff skills, best practices, or lessons learned Limited vision/support or understanding from executive management Lack of staff skills, best practices, or lessons learned Too much technology retraining anticipated Too much complexity to manage or inadequacy of our development tools Too much technology retraining anticipated Systematic planning approach and close project management Implement a small pilot service to show success Systematic planning approach and close project management Contract for IT services or project integration services Establish migration oversight program office Choose strategic and IT services vendor to work with Increase technical education Mid-Range System i and AS/400 Nearly one-quarter of survey participants report very good results in their midrange modernizations, while 9% reported poor results. About 43% report very good results in the IT integration stages of their migrations (Table 5). Meanwhile, about 14% reported problems and poor results with SOA development tools; 17% had poor results with application migration tools, compared with 13% that had very good results in each category. Importantly, 27% of the survey participants running mid-range System i and AS/400 reported very good results in overall IT service delivery to the business as a result of the migration. Users cite the integrated nature of the System I hardware and operating system facilities as an accelerator to business process changes. Table 5: Legacy Modernization Strategies for IBM System i and AS/400 Platforms Approaches Key Reasons Challenges Responses Aberdeen Group 9

16 Approaches Key Reasons Challenges Responses Extend/ surround on System i (46% of respondents using i Series or AS/400) Modernize (18%) Surround off System i (11%) Replace (25%) System i economics are better System i is our platform of choice when possible Applications are key composite of SOA strategy System i economics are better System i is platform of choice when possible Economics are better System i replacement strategy Modernize home-grown applications off the System I and buy new apps Application consolidation: no longer needed by the business Too much complexity for employees to cope with Too many different applications systems to integrate Too much complexity to manage or inadequacy of development tools Unknown value for ROI/ROA Too many different applications to integrate Limited acceptance on implementation schedule or budget Change management around people or existing processes Implement a small pilot service to show success Systematic planning approach and close project management Implement a small pilot service to show success Increased technical education Increased investment in IT infrastructure Implement a small pilot service to show success Midrange Unix Slightly more than 40% of survey respondents whose companies use Unix platforms reported achieving very good results in overall modernizations at the IT level, with 17% achieving very good results in the service delivery to the business (Table 6). However, Unix migrations were marred by a high level of poor results: 15% were dissatisfied with database and information management; one-quarter with IT integration; 17% with application migration tools; and 45% reported poor results with the IT services providers they used. 10 AberdeenGroup

17 Table 6: Legacy Modernization Strategies for Unix Platforms Approaches Key Reasons Challenges Responses Extend/surround on Unix platform (58% of respondents using Unix) Modernize (16%) Surround off Unix platform (16%) Replace (11%) Performance is better doing it this way Unix is platform of choice when possible Applications are key composite of SOA strategy Performance is better doing it this way Performance is better doing it this way Economics are better Unix platform replacement strategy Modernize home-grown applications off the Unix platform Lack of staff skills, best practices, or lessons learned Unknown value for ROI/ROA Conflicts with other business technology/process initiatives Change management around people or existing processes Change management around people or existing processes Unix platform replacement strategy Modernize home-grown applications off Unix platform Implement small pilot service to show success Choose strategic and IT vendors to work with Systematic planning approach and close project management Implement small pilot service to show success Standardized or will standardize on one ERP package across the company Systematic planning approach and close project management Increased investment in IT infrastructure Systematic planning approach and close project management Aberdeen Group 11

18 Chapter Three: Implications & Analysis Key Takeaways Most enterprises, especially in the mid-market, opt for an extend/surround approach to modernizing their legacy applications for SOA. Measure success through the metrics that correspond closest to the chief drivers behind your company s migration strategies. Migration challenges and lessons learned relate to company size and industry segment. G iven a choice of legacy modernization approaches, most companies opt for the more economical, less complicated extend/surround option (Figure 4). In fact, close to 90% of mid-size companies in our survey said they chose that option over replacing and modernizing, not a surprise given the pressures on the midmarket to keep an eye on costs while eyeing growth. However, replace and modernize are not far behind. Figure 4: Respondents Choices of Legacy Modernization Approaches 16% 26% Replace Extend/Surround 58% Technology Modernization What s the Defining IT Metric for SOA Modernization? Given a choice of improving IT time to delivery, lowering IT integration costs or application maintenance costs, or consolidating IT infrastructure as the key IT drivers to focus on during a legacy modernization, the majority chose IT time to delivery (Figure 5). But note that Best in Class companies concentrate on lowering IT integration costs, which has a collateral positive effect in speeding time to deployment and lowering application maintenance costs. 12 AberdeenGroup

19 Figure 5: Key Legacy Modernization Drivers, by Industry Group 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% 43% 38% 33% 27% Consolidation of IT infrastructure 48% 45% 40% 38% Lower IT application maintenance costs 49% 41% 52% 69% Lower IT integration costs Discrete/Process CPG Services Public Sector 68% 67% 62% 85% Improve IT time to deliver changes to the business Whatever the primary driver behind a modernization strategy, it should match the primary metric to determine the success of the strategy. However, most respondents reported only moderate success when asked about overall application service improvement outside the IT department and overall SOA application service results, with the best results coming from companies running IBM System i and AS/400 platforms (Figure 6). Figure 6: Success Ratings in Service Improvements Overall application "service" improvement outside IT department Mainframe Series I, AS/400 Unix 27% 17% 89% 59% 67% 11% 14% 17% Overall IT SOA application "service" results Mainframe Series I, AS/400 Unix 29% 23% 42% 65% 68% 50% 6% 9% 8% 0% 20% 40% 60% 80% 100% Very good Moderate Poor Aberdeen Group 13

20 Modernization Project Challenges by Company Size and Industry When asked what factors impeded their migration efforts, survey participants cited an unknown value for ROI and ROA; too many different application systems to integrate easily; lack of staff skills, best practices, and lessons learned; and people-process change management (Figure 7). ROI/ROA challenges are most prevalent at large companies and in the public sector (64%). Application integration issues are most commonly found in discrete/process manufacturing. Human capital change management challenges are especially prevalent (63%) in CPG manufacturing. Figure 7: Modernization Project Challenges by Company Size 60% Small Mid-Size Enterprise 57% 50% 45% 40% 30% 40% 24% 25% 36% 29% 40% 39% 40% 32% 20% 13% 10% 0% 29% 31% 36% 45% Change management around people or existing processes Lack of staff skills, best practices, lessons learned Too many different applications systems to integrate Unknow n value for ROI/ROA Modernization Lessons Learned The most common miscalculation in an initial legacy application modernization project is having too aggressive a project schedule (Table 8). This problem is especially prevalent (53%) in the services industry and in large companies (53%). Technical problems with development tools impeded 40% of survey respondents overall, and half of discrete/process manufacturing companies. Training issues most affected public sector organizations. Mid-size companies (48%) were most impeded by unanticipated development and testing problems, especially among manufacturers. 14 AberdeenGroup

21 Table 7: Lessons Learned by Company Size and Challenged Industry Lesson Overall Small Mid- Size Large Challenged Industry Schedule was too tight 39% 46% 35% 56% Services Problems with development/migration tools 39% 23% 50% 32% Mfg Training issues 36% 15% 38% 40% Public Sector Unanticipated development or testing problems 32% 23% 46% 20% CPG How Application Modernization Experiences Differ We analyzed survey responses by two different technology approaches, combining replacement and modernization into one and surround and extend into the other. The extend/surround approach essentially says the existing application logic and data are to be preserved and extended by reengineering with SOA technology. In contrast, modernize/replace is about technology replacement of the application logic and data. Table 8 summarizes the contrasts between the two approaches. Importantly, companies are making equal investments in each technology approach and seeing about equal and significant returns on their investments. Table 8: Comparison of Legacy Application Technology Approaches Comparison Key Reasons Extend/ Surround Modernize/ Replace Key Drivers Top Migration Challenges Lessons Learned Improve IT time to deliver changes to the business 74% 71% Lower IT integration costs 67% 40% Consolidation of IT infrastructure 26% 46% Our applications are antiquated 21% 26% We have no plans for SOA 0% 3% Limited vision/support or understanding from executive management Limited agreement on how to measure mainframe migration success Conflicts with other technology/business process initiatives 33% 23% 2% 11% 14% 37% Schedule was too tight 26% 41% Problems with SOA development/migration tools 42% 28% Training issues 42% 34% Aberdeen Group 15

22 Comparison Key Reasons Extend/ Surround Modernize/ Replace Barriers to SOA Adoption Technology Strategy Runtime performance, capacity, or stability problems 34% 21% Only barrier is resources; we are committed to SOA 45% 28% Resistance due to cost of enabling services 35% 16% Unproven business case and/or no executive buy-in 15% 31% Use our own programmers to make the changes largely by hand 54% 44% Acquire new SOA development tools 46% 53% Use an automated migration tool(s) 13% 16% Use software adapters from SOA software middleware products to connect to legacy applications 46% 19% 16 AberdeenGroup

23 Chapter Four: Recommendations for Action Key Takeaways Tailor your legacy application modernization projects based on the application s computer platform and your company s maturity level within Aberdeen s Competitive Framework. There is no one size fits all modernization strategy. Best in Class companies focus on lowering long-term IT integration costs that represent 40% of the IT budget. Automated software tools may allow a broader choice of migration targets, faster implementation, and higher quality than a manual application project. T he cost of IT integration activities is enormous about 40% of the entire IT budget. SOA is attractive because it can lower IT integration costs, freeing funds for greater innovation and transformation at the line-of-business level. SOA is also allowing IT departments to deliver applications and changes more quickly, so time-tovalue is lowered. That s why progressive IT organizations are triaging their existing application portfolios to find those legacy applications that should be incorporated into an SOA strategy. Technology Considerations by Approach About one-third of survey respondents plan to engage service providers to assist with the legacy application modernizations for SOA. Here are top-level considerations for each of the four approaches discussed in Chapter Two: Modernize: (1) Look to automated software products and services that can abstract and extract the application s logic and data definitions, combining these with SOA technology to create a modernized application that can run on the same or a different platform (e.g., re-hosting). (2) Programmer labor is a critical resource, so wholesale modernization by hand is cumbersome and expensive. (3) Consider opportunities for incorporating modern technology beyond SOA: Business process management (BPM), business activity monitoring (BAM), and rich user interfaces are three popular choices while creating composite applications. Replace: First, ask whether the application be replaced with a third-party software package? Custom application replacement projects should consider (1) software tools and approaches that incorporate BPM technology so that future process changes are close to the line-of-business and (2) high-power software generators that provide excellent programmer productivity while generating the target platform s native Java or.net low-level code. Extend: (1) Choose the Message, API, File and Database, or Data Adaptation approach discussed in Chapter Two. (2) Look for SOA middleware and application development tools that can be integrated quickly and effectively with the existing code base. Our research shows a majority looking at SOA middleware suites consisting of an Enterprise Service Bus (ESB), registry/metadata repository, security, management, Aberdeen Group 17

24 and governance components. (3) Consider an automated or semi-automated conversion of common tasks such as API, user screens, or message replacements. (4) Model the performance and capacity changes brought about by the new middleware software. Surround: The same considerations as Extend, with additional considerations for being on a different computer in a loosely-coupled SOA messaging configuration. Model failure scenarios for either the host or the surround server. Note that development tools are an important choice. New development technology delivering a rich Internet experience is one such example. Recommended Actions by Organizational Maturity Whether a company is trying to gradually move its legacy application SOA modernization efforts from Laggard to Industry Average, or from Industry Average to Best in Class, the following actions will help spur the necessary performance improvements over time: Best in Class Next Steps 1. Focus on radical modernization as the preferred strategy for mission-critical applications. Application programs are basically logic and data. To support the lines of business, lower IT integration costs, and speed time to change, look to extract the logic from mission-critical applications and re-implement it as part of a business process management system. The data belongs as part of an information management strategy that delivers information as a service in an SOA. If the current software languages are proprietary or outdated, or if the current database management system is pre-relational, consider automated conversion of the applications or databases to newer technology and to SOA in a single migration project. 2. Weed out the old, tired, and unneeded applications. One CIO told us, I m tempted to turn off one of our (many) mainframes just to see if anyone complains. He s getting at a root problem: not knowing what all your applications do and who is using them. Look to deactivate as many applications or programs as possible from your application portfolio. Consider enlisting the help of highly automated tool vendors that can provide details quickly on what your applications do and how they are integrated. 3. Require broad participation by IT technicians to foster SOA training and experience. All of your IT staff must become technically proficient in SOA technologies. Instead of creating a dedicated legacy modernization team, consider broad participation in concert with SOA training. This shares the pain, prevents morale issues with a dedicated migration team, and moves modernization along in parallel with standard application maintenance. 18 AberdeenGroup

25 4. Focus on IT integration costs as a key performance metric. Using IT integration costs as a key performance metric in an SOA environment will also lower application maintenance costs and speed time to change implementation. Best in Class companies are freeing up about 15% of the IT budget with this strategy and using most of the savings to drive innovation with the lines of business. Industry Average Steps to Success 1. Prioritize application migration by service value. The shortest path from cost to value is to know what services in your SOA will deliver the greatest and earliest value to your organization. The prioritized list should have a major influence in the order of application migration. 2. Industrialize the modernization process. A total modernization will take years at most large and upper mid-size organizations (at least $500 million in annual revenue). Therefore, manual, laborintensive migrations will cost more over the migration period than choosing modernization tools (including automated migration) and best-in-class SOA development software tools. Training investments will pay back several times over during the modernization period through higher productivity and faster completion. 3. Consider outsourcing the legacy application modernization. The services arm or services partners of application modernization technology companies are experts in modernization projects. An outsourcing strategy is worth a cost-benefit analysis, considering the skills diversion, training, and related IT management issues for a migration that is a one-time but major occurrence. 4. Merge legacy application modernization planning with IT consolidation strategies. The combination of a new services-oriented re-architecture and application modernization has created a once-a-decade opportunity to consolidate IT hardware and operating system platforms with new storage and networking technologies. Service-oriented software architecture planning should be coordinated with a service-oriented hardware infrastructure architecture. Laggard Steps to Success 1. Realize that resistance to spending on IT results in higher IT costs. Aberdeen research consistently shows Laggard companies as being resistant to spend money on IT to make money with IT. This is an organizational and managerial issue. Avoiding necessary spending on automation, SOA modernization tools, SOA development tools, training, and IT services results in a less efficient operation with lower quality and longer time to delivery. Aberdeen Group 19

26 More than 45% of our survey respondents will spend at least $500,000 on legacy application modernization. Well-spent funds on IT, such as those earmarked for legacy modernization, show a demonstrably strong return. 2. Determine the highest long-term paybacks. Two-thirds of our Laggard company respondents report that their companies have not analyzed their platform (i.e., hardware and operating system) operating costs versus those of alternate platforms. Meanwhile, 24% report antiquated applications, and 36% have applications that are not well mapped to business processes. Modernizing an application that does not meet the business needs will not add value, but simultaneously modernizing business fit applications to new technology and SOA can add much value. Consider using an automated solutions vendor to make this transition versus a manual migration. Consider modernization, including the acquisition of new third-party SOAenabled application software, where practical. Look to high-productivity development tools as replacements for third-generation languages, which have a high life-cycle labor cost component, for custom application development going forward. 3. Carefully select modernization and SOA development tools, and IT services providers. Laggard companies are likely to report poor results with migration and development tools and with migration services providers because of inadequate funding (see the first recommendation) and inadequate training. 4. Consider automation versus a manual legacy application modernization strategy. Automated application language and database projects can modernize an application, extend its life, and make the application ready for an SOA. Consider using an automated solution vendor to complete this process quickly, and with less risk and less cost than a manual conversion. 20 AberdeenGroup

27 Appendix A: Research Methodology I n August and September 2006, Aberdeen Group examined the approaches, challenges, strategies, benefits, and performance improvements companies and their IT organizations are experiencing in enabling their legacy applications for serviceoriented architectures (SOAs). The research effort began with an online survey that was filled out by respondents from about 120 companies in various enterprises from different industries around the world. In the survey, respondents answered questions designed to determine the following: The factors causing their companies to embrace SOA; The technological options companies considered and eventually chose based on their respective hardware platforms to enable their legacy applications; Company spending plans for legacy SOA enablement through 2007; The challenges companies face in legacy migration projects and how they respond to those challenges; The technology vendors and service providers they use to assist them in their SOA enablement efforts; and Performance improvements linked to their legacy SOA enablement projects. Aberdeen supplemented this online survey effort with telephone interviews with select survey respondents, gathering additional information on legacy SOA enablement strategies, experiences, and results. The study aimed to identify emerging best practices for SOA enablement and provide a framework by which readers could assess their own capabilities. Responding enterprises included the following: Job title/function: The research sample included respondents with the following job titles: manager (23%), director (20%), internal consultant (14%), CIO/IT leader (11%), senior management, such as CEO, CFO, or COO (10%), and vice president or senior vice president (5%). Thirteen percent identified themselves as staff while 4% came from other positions within their organizations. Industry: The research sample included respondents from several industries. High technology/software companies represented 19% of the survey field, followed by finance/banking/accounting (11%), health/medical/dental services (9%), public sector (9%), retail (6%), automotive (6%), industrial equipment manufacturing (4), and insurance/real estate/legal services (4). Other respondents came from the following industries: aerospace/defense, apparel, chemicals, computer equipment and peripherals, construction/architecture/engineering, consumer durable goods, consumer electronics, consumer packaged goods, distribution, education, food/beverage, health and beauty aides, metals and metal prod- Aberdeen Group 21

28 ucts, paper/lumber/timber, telecommunications services, transportation/logistics, and utilities. Geography: Most study respondents 52% were from North America; 28% were from Europe, 8% from Asia/Pacific, 7% from the Middle East and Africa, and 6% from Central and South America. Company size: About 43% of respondents were from large enterprises (annual revenues above US$1 billion); 42% were from mid-size enterprises (annual revenues between $50 million and $1 billion); and 15% from small businesses (annual revenues of $50 million or less). Solution providers recognized as featured underwriters of this report were solicited after the fact and had no substantive influence on the direction of The Legacy Application Migration Benchmark Report. Their underwriting has made it possible for Aberdeen Group to make these findings available to readers at no charge. 22 AberdeenGroup

29 Appendix B: Related Aberdeen Research & Tools Related Aberdeen research that forms a companion or reference to this report includes: The Business Process Management Benchmark Report (August 2006) The Business Value of IT Outsourcing Benchmark Report (July 2006) Enterprise Service Bus and SOA Middleware (June 2006) Achieving More Value from Enterprise Applications Benchmark Report (May 2006) The SOA in IT Benchmark Report (December 2005) Enterprise Applications: Build or Buy? (June 2006) Information on these and any other Aberdeen publications can be found at Aberdeen Group, Inc. 260 Franklin Street Boston, Massachusetts USA Telephone: Fax: Aberdeen Group, Inc. All rights reserved September 2006 Founded in 1988, Aberdeen Group is the technologydriven research destination of choice for the global business executive. Aberdeen Group has over 100,000 research members in over 36 countries around the world that both participate in and direct the most comprehensive technology-driven value chain research in the market. Through its continued fact-based research, benchmarking, and actionable analysis, Aberdeen Group offers global business and technology executives a unique mix of actionable research, KPIs, tools, and services. The information contained in this publication has been obtained from sources Aberdeen believes to be reliable, but is not guaranteed by Aberdeen. Aberdeen publications reflect the analyst s judgment at the time and are subject to change without notice. The trademarks and registered trademarks of the corporations mentioned in this publication are the property of their respective holders.