1. © 2015 IBM Corporation Cost Benefit Analysis Workshop Consolidation of Disparate Environments Shantan Kethireddy April 28, 2015

2. © 2015 IBM Corporation 2 Cost Benefit Analysis Workshop: Consolidation of Disparate Environments  The Cost Benefit Analysis Workshop is designed to explore savings and efficiencies that can be gained by reducing data sprawl within an IT infrastructure.  The combination of DB2 for z/OS and the DB2 Analytics Accelerator may prove beneficial for addressing the costs associated with excessive disparate environments:  Multiple extract / transform / load processes consume expensive computing resources;  Multiple RDBMS/Hadoop instances proliferate costs and reduce usability through discrete silos of people/processes/infrastructure/storage/interfaces;  Numerous copies of data sourced from DB2 z/OS and spread across disparate environments increase the risk of data fraud / theft; and  Additional administrative workload is required to develop and maintain processes and data repositories.  The Workshop focuses on your specific environment and business requirements, and forges a partnership between application and infrastructure teams:  Application teams provide relevant insight into use cases and business usage  Infrastructure teams provide insight into current costs and technical configurations  The Workshop Recommendations provide a holistic approach to both technical architecture improvement and financial cost reduction.

3. © 2015 IBM Corporation 3 Cost Benefit Analysis Workshop: Deliverables  The Cost Benefit Analysis Workshop process is structured in four parts:  Pre-workshop activities: Completion of Socialization documents: IBM engages with both infrastructure and application teams, using documents that encourage exploration of current data consumption patterns, and to discover and validate future business needs Pre-workshop questionnaire: Infrastructure teams provide specific costs for the environment  Workshop: Half-day, on-site session to verify requirements gathered above, develop initial architectural approach, and develop cost benefit analysis (CBA)  Post-workshop refinement: Short consultative sessions with IBM to validate technical architecture collateral, refine proposed technical solutions, validate CBA assumptions, and provide proof points (within scope of the workshop)  Proposal: Validated architectural approach with cost benefit analysis containing: Documented findings, in both detail and summary form Documented flows and architecture (“paper demo”) Cost Benefit Analysis Spreadsheet Project Plan

4. © 2015 IBM Corporation 4 Cost Benefit Analysis Workshop: Samples

5. © 2015 IBM Corporation 5 Cost Benefit Analysis Workshop: Getting Started  Engage personnel who have a stake in the outcome of the study:  Application Teams (REQUIRED): Provide insight into business use of data Supply knowledge of processes associated with data Possess awareness of future application needs  Infrastructure Teams: Provide deep understanding of current environment Supply knowledge of costs associated with implementation of current processes  Executive Sponsorship: Raise awareness of workshop internally Articulate success criteria in business terms (workshop should be tailored to meeting key client initiatives) Identify key financial stakeholders and validate budget exists

6. © 2015 IBM Corporation 6 Cost Benefit Analysis Workshop: Getting Started  Schedule time for Workshop Preparation and Execution:  Pre-workshop discussions: 2 days (non consecutive): identify key workshop participants, broadcast key workshop objectives, disseminate and collect socialization documents/pre-workshop questionnaires, setup dates for workshop  Workshop Engagement: Half day to full day reviewing pre-workshop material and development of initial approach (onsite with Web-Ex)  Post-workshop refinement: Several iterative 1 hour sessions: Present workshop collateral/proposals, follow-up on outstanding questions, identify areas where deeper investigation required  Proposal: one to two hour meeting (often performed independently with different groups) to discuss / review recommendations. Infrastructure presentation may be different from application team presentation