Planning A Cloud Implementation


Published on

Organizations need a plan for moving from their current state toward cloud models based on standardized and consolidated platforms, shared services, self-service and metered use. How can organizations get started on the evolution to cloud computing? This webcast explores how enterprises can create a roadmap to cloud computing, including developing the business case; financial models; governance considerations; security considerations; organizational, policy and process considerations; and technical architecture considerations.

Published in: Technology, Business
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • IDC Cloud Services Survey from the last two years group of these motivations into two area - Reduce costs / increase business agility.Interestingly last survey (Oct2009), pay per use passed easy to deploy as the top benefit.most enterprises want to do both And in most enterprises have multiple cloud projects or initiatives In each case (whether small project or major transformation) first decide what is the business goal
  • There is a lot knowledge about existing public cloudsBut internal enterprise private clouds may be different.Consider the 5 NIST characteristics - On-demand self-service, Resource pooling, Rapid elasticity, Measured service, Broad network access.For each of these characteristics an enterprise private cloud may be quite different from what comes to mind for public cloudsConsider ‘on-demand self service’ - at AWS it may take minutesto deploy an instance of Oracle database 11g - there is no IT department controlling that deployment But an enterprise has enterprise standards, authority and budget requirements,governance issues, etc. So enterprise private cloud user self service may mead hours instead of minutesBut that’s better than weeks of the old wayEach characteristic may have it’s own ‘enterprise cloud’definitionSecurity another one. – e.g., customer data subject to regulatory issues, private clouds different from public clouds
  • And these differences are why organizations choose private cloudsSecurity (and related compliance issues) is at the top of that list of concerns, along with QoS issues / reliability / availability. For these reasons it may be easier to turn existing services into an internal cloud, Creating shared resource pools is faster path to cloud than moving applications and data outsideAnd ultimately most enterprises want to able to deploy hybrid clouds
  • What are common use cases we seeAugmentation – handling peak load or anticipated spikes in demand for services in the cloud. Attractive , but may be difficult.dependent on the statefulness of the application and the interdependence Shared Services –the logical extension of SOA movement, shared databases, middleware, security services, Development and Test –perhaps the easiest cloud use-case Shared Infrastructure – Cloud Computing modern evolution of IT consolidation projects, with the Cloud’s capabilities for self service.
  • cloud computing for shared services drill downmany different levels from a shared portal and front end infrastructure to shared data services. you’ve heard about Oracle’s Middleware as a Service and Database as a Service capabilities ExaLogic and Exadata. You’ll hear later about Shared Security and Identity Infrastructure. In each area there are specific trade-offs to achieve the potential benefits.
  • What kind of opportunities are we talking about for cost savings from moving to consolidated shared services.Credit Suisse a Private Cloud using Oracle technology for Middleware and Database.220 applications on pool of 400 servers,just 15% of the previous of 2800 line with industry surveys that show 12-15% IT utilization.this architecture precededengineered systems but the end result and the architecture are comparable.
  • Let’s drill down a bit further on Database as a Service as a consolidation target. Here we have illustrated 3 different architectures You have seen in the keynote three different architectures mentioned Shared Server, Shared database and Shared Schema. There are potential benefits in both cost saving, the ability to rapidly scale and the self service nature of the database cloud. Each architecture has specific advantages. For an enterprise with common database standards, consolidation to a shared single database instance, may be relatively easy With large database heterogeneity a shared server design provides freedom of choice but there is more administrative overhead and scaling is limited to the server size.A shared operating system design on a database cluster model provides increased scaling and availability, coupled with the ability to run multiple database instances for performance or versioning requirements.Choose the right one or more for your needs
  • The key considerations Savings in HW and licenses reduced system management – though you still have db mgmtShared Database is appropriate where there already exists a common hardware/operating system and db version mixed workloads may be better served by deployment of individual VMs in a shared server consolidation.The Shared operating system design is appropirate for Mission critical applications they benefit from the availability architecture of a RAC cluster, while still having the advantage of independent database instances.there is no single best DB consolidation architecture, it depends on the workload and related application architecture, and most enterprises are likely to want to run more than one of these models.
  • Having decided which cloud architecture for which applications – what is the migration planGiven that there are usually some migration costs – apps may be selected by assessing suritability, difficulty and ROIa common general strategy is to migrate apps that are peaky, have potentially frequent changes and are likely to see future investment.those applications are probably the early targets for migration as it is easier to demonstrate a positive ROI for the resulting shared infrastructure. Of course all the new development can be moved to the cloudAnd this can happen even it there are migration delays for existing apps
  • Achieving cost reduction implies some model for measuring and tracking costs, both direct and indirect costs. power, cooling, and real estate costs, may be allocated in facilities budgets outside the IT organization.And achieving business flexibility implies existing measures of agility, such as the overall time-to-deploy new functions.where adequate models don’t exist or aren’t tracking current costs … - consideration should be given to implementing cost measurement and tracking before begin the cloud implementation. - to achieve the maximum benefits of cloud computing model may mean changing the way the enterprise calculates and allocates costs of services. Perhaps first consider a new more comprehensive cost model and how cloud computing charge backs could be distributed across the IT user base. Oracle’s Enterprise Management cloud infrastructure products are evolving to support not just the management of the cloud, but also the reporting to achieve cloud efficiency and cost allocation.
  • direct savings of reduced hardware investment are obvious, but the biggest benefits may be in operations and licensingSimilarly it can be difficult to measure indirect service level benefitsMore importantly - These benefits may be beyond the enterprises current measurement or cost allocation schemas. Moving to higher cost and performance visibility can be a parallel project to the actual physical implementation of the proposed cloud infrastructure. Where these service levels aren’t being currently tracked, then a pilot sample can be done by tracking a current implementation workflow.
  • this Oracle customer saved almost 400,000$ over 5 years in hardware and environmental costs by implementing a database as a service over their existing database operations, but as previously noted this is dwarfed by the savings on software and operations.
  • Having developed an ROI case what is a desirable pricing model for an enterprise cloud?The simplest model is simply to take cost and amortize it out to the participating business units or applications.On the other hand many enterprises may choose to go farther in implementing a more involved ‘pricing’ or cost allocation model.This could include some form of market rate pricing. Esp if there is a plan to move to some form of hybrid cloud Then the pricing/cost model could then accommodate the rationalization of internal vs external resources.This may go farther to provide some form of value pricing that provides a tax or base to accommodate future investment. This of course would imply a price advantage to an external cloud, unless the enterprise cloud pricing model provided a similar tax on external hosting contracts
  • As noted cloud computing may require transforming existing operational procedures, Is the organization readyFor example cloud self-service implies automating operational procedures. Are the existing procedures well documented? Are there existing planning models and tools? Similar consideration should be given to other areas such as IT governance and architecture. Does the current security model support adequate user permission for the proposed cloud model?The enterprise should consider a framework for evaluating the current organizational readiness
  • Given a business case and planned architecture – how will the cloud be rolled out – including organizational changesCloud computing implies ‘sharing’. Sharing across applications, department and business units.For example - Will you start with a project and then extend it across the enterprise
  • Whichever cloud strategy is selected it is apparent that cloud computing represents some key changes in IT culture. Architecture -Up front vs late bindingIT operations focussesvs self serviceManagement of systems vs cloud control plane (ie., hybrid ready
  • The process of creating a roadmap to move to cloud typically involves phases that are parallel to traditional IT consolidationFirst standardizeIdentify all the current implementations of asolution and then Architect a single solution / versionSecond Consoidate – Analyse and review all instances running on the same platform version – plan and then carry out the migrationUse Oracle migration planning services and integration products – GoldenGate, ETL tools etc.May deployment and migration to Exalogic and Exadata or the use of OVM and associated servicesThird AutomateIdentify the deployable units and meta-data, develop the required scripts, and then implement the supporting provisioning tools and workflowe.g., development of custom automated deployments for OVM images and MW platforms, and perhaps the use of SOA and BPM tooling for workflow Finally OptimizeDeploy tools and dashboards and present usage, Capture the metrics and relate to usage, Adapt pricing to demand and evolve new business modelsThis phase may include the deployment of CRM and billing apps to manage charging for usageThis is non-linear / continual
  • Here is a customer example implementing a Platform as a ServiceThe company is Norther Trust and their example illustrates a multi-year journey to build this cloud serviceThe result is called“JavaArch” and currently supports 200 applications in 90 WebLogic groups across three separate WebLogic clusters duplicated in 2 live/live data centersThis architecture is designed to provide Improved Time to Market – with a hosting pre-build shared services that every applicationBetter Service Levels – with one model and one set of tools across the enterpriseReduced Costs – the 12 year graph shows % investment in App Dev vs. Infrastructure.The inflection point mid graph is where the JavaArch platform picks up, and infrastructure spend takes a nose diveGetting to this Java based shared services multi-year journey rather than an overnight phenomenon.The four phases depicted are:JavaArch 1.x - The first component JavaArch1.x shared service Web SSO.Web2000 - introduced co-hosting and additional services beyond security.JavaArch8 - Based on WebLogic introduced Automation,templating and scriptingJavaArch11 - the newest environment – adds virtualization for true elastic resource demand withfully automated environment creation. Architecture, repeatable design patterns and platform metrics were essential to this multi-phase roadmap
  • Finally let’s summarize the points we have made today :Decide what kind of cloud is under consideration – Infrastructure, Platform… , Private, Hybrid….Identify few select, measurable benefits…. And the potential risks and challengesUse what models may be appropriate to evaluate ROI Evaluate the required areas of organizational readinessDevelop a clear roadmap for organizational deploymentIdentify key transformations
  • Speaker Notes:Message #1:Oracle offers you an examination of your most vital data center processes. The Oracle Insightfor Data Center Technology is a program that links leading industry advisors with yourexecutive team to develop a comprehensive process-oriented approach to achieve Data Centerexcellence. Oracle Insight for Data Center Technology provides a consistent, consultativeprocess to assess current state of IT database foundation and the optimum path forward. Thiscomplimentary service to Oracle’s customers brings to bear Oracle’s extensive technology andindustry experience in a highly focused activity that provides a catalyst for data centertransformations.Oracle Insight delivers a strategic assessment of process capability, prioritized roadmap basedon multiple scenarios, and quantifiable economics of strategic decisions. This powerfulcombination delivers a common vision to your executive team with a pragmatic plan ofexecution. With Oracle Insight for Data Center Technology, you have a partner in acceleratingvalue identification and benefits capture from your Data Centers.Message #2:Oracle Insight for Data Center Technology utilizes benchmark practices and an analysisframework based on the industry’s leading standards and practices. We will work with yourexecutive team to customize the program to achieve your objectives. The typical OracleInsight for Data Center Technology has the following steps.1. Data center industry perspective. Oracle facilitates an interactive discussion withyour executives about Oracle’s data center experiences and key industry trends. Inthis phase a scope of analysis and key hypothesis of your data center is developed.2. Discovery. Collaboratively analyze your current business processes and review yoursupporting applications technology through a series of one-on-one and workshopsessions. Opportunities are mapped to technology and process enablers to illustratethe effort required to attain higher-level capabilities. These findings are summarizedin the solution priority map. Oracle identifies the highest-value opportunities anddevelops a prioritized business case with both qualitative and quantitative benefits.3. Solution design. Oracle recommends best-practice business processes andsupporting technology with a road map that includes time-to-benefit analysis and ahigh-level implementation plan for the areas we jointly agree upon.4. Solution presentation. In partnership with you, the Insight team prepares anddelivers a presentation that includes industry trends and key supporting technology,business benefits, and value drivers, as well as a phased implementation plan androad map for the highest- priority opportunities.Message #3:The Oracle Insight program is a global program and leverages the same methodology globally for the benefit of key strategic customers. Message #4:It is also no-cost program for the customer.
  • Planning A Cloud Implementation

    1. 1. Planning a Cloud Implementation<br />Dr. James Baty<br />VP, Oracle Global Enterprise Arch. Pgm.<br />
    2. 2. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remain at the sole discretion of Oracle.<br />
    3. 3. Cloud Business Case<br />Cloud Computing Capabilities<br />Cloud Computing Effectiveness<br />Cloud Computing Roadmap<br />
    4. 4. What is Your Cloud Business Case?Top Private Cloud Challenges Reported: 2010 IOUG Survey*<br />Creating the business case & funding model<br />Adequately provisioning server capacity<br />Implementing process, policy and role changes<br />Gaining cross-organization support or participation<br />Building awareness of available services<br />Adequately provisioning Storage capacity<br />Loss of visibility / control<br />%<br />* IOUG ResearchWire member study on Cloud Computing, conducted in August-September 2010. <br />
    5. 5. Cloud Drivers<br />Reduce Complexity <br />Reduce time to Market<br />$<br />Green<br />Change IT Cost Structure<br />Strategic<br />Tactical<br />Scale on Demand<br />Optimizing dev / test environments<br />Metering and Chargeback<br />Virtualization<br />
    6. 6. Cost Reduction? Business Agility? …Both? IDC Cloud Service Survey Results <br />Benefits<br />From 2008 to 2009 ‘Pay for use’ passes ‘Easy to deploy’ as top benefit.<br />Consider …<br /><ul><li>What specific benefits are you trying to achieve? (be selective)
    7. 7. Where do you fall on cost savings vs business agility? (just one or both and if both, what priority?)</li></ul>Pay only for what you use<br />Source: IDC eXchange,”New IDC IT Cloud Services Survey: Top Benefits and Challenges“ <br />( December 15, 2009<br />
    8. 8. ‘Enterprise’ Private Clouds are Different<br />SaaS<br />Saa<br />I<br />N<br />T<br />R<br />A<br />N<br />E<br />T<br />NIST identifies 5 essential cloud characteristics<br />On-demand self-service, Resource pooling, Rapid elasticity, Measured service, Broad network access<br />But private clouds are different from public clouds…<br />E.g., On-demand self service<br />Public developer cloud – unrestricted resources provisioned in minutes, but with no controls or corporate governance<br />Enterprise private cloud – need provisioning controls, standards enforcement, prioritization, approvals, etc. <br />I.e., Enterprise cloud faster to deploy than traditional IT, but probably slower that public cloud <br />There are other criteria with similar differences<br />Security, governance, high availability, global access ….<br />PaaS<br />Paa<br />IaaS<br />Iaa<br />
    9. 9. Why Choose Private Cloud vs. Public?Results from IOUG Survey<br />Respondents cite Security, QoS & Long-term Cost as key reasons to choose a Private Cloud over Public Clouds <br />* IOUG ResearchWire member study on Cloud Computing, conducted in August-September 2010. <br />
    10. 10. Cloud Business Case<br />Cloud Computing Capabilities<br />Cloud Computing Effectiveness<br />Cloud Computing Roadmap<br />
    11. 11. Profile Applications & Workloads First Inventory Your Applications<br />Suitable for cloud now <br />Time based<br />Very parallel (i.e. batch)<br />Spiky traffic<br />Capital intensive (especially startup)<br />Proof of Concept<br />Low utilization<br />Less deployment costs<br />High bandwidth costs / high real estate<br />Not as suitable for cloud<br />Vertically scaled applications<br />Consistent load levels<br />Latency sensitive applications<br />Insecure applications<br />Hardware device dependent (e.g. fax server, SNA gateway)<br />ISV unsupported<br />Per CPU licensed applications<br />
    12. 12. What Do You Want the Cloud to Do?Start with Common Use Cases<br />Augmentation<br />(Elastic scaling)<br />Shared Services<br />Development<br />and Test<br />Resource sharing<br />(consolidation)<br /> Most enterprises are trying<br /><ul><li>Shared development and test environments
    13. 13. Hardware & Services consolidation</li></li></ul><li>X<br />X<br />X<br />X<br />X<br />X<br />X<br />Shared Services – Many Possibilities<br />Shared Functions<br /><ul><li>Sharing Applications across org
    14. 14. Enabled by SOA, BPM </li></ul>Java PaaS<br /><ul><li>Build & deploy to common platform
    15. 15. Enterprise Private Cloud</li></ul>Shared SOA<br /><ul><li>Application services integration
    16. 16. Centralized authorization for all apps</li></ul>Shared Security<br /><ul><li>Rapid access to all enterprise data
    17. 17. Parallel Processing of Transactions</li></ul>DBaaS<br />
    18. 18. case<br />Shared Services – Private PaaS ExampleCredit Suisse <br /><ul><li>Hosts 220 applications on 400 servers
    19. 19. Replaced 2800 servers
    20. 20. Standardized operating process
    21. 21. Only 3 platform releases in parallel</li></ul>study<br />
    22. 22. Private Database Cloud Architectures Common Building Blocks are Shared Server & Storage Pools<br />CRM<br />DW<br />ERP<br />ERP<br />DW<br />CRM<br />ERP<br />DW<br />CRM<br />OS<br />OS<br />OS<br />DB<br />DB<br />DB<br />DB<br />DB<br />DB<br />DB<br />Hypervisor<br />Hypervisor<br />OS<br />OS<br />OS<br />OS<br />Operating System<br />Share server pool<br />Real Application Clusters<br />Server<br />Deploy in dedicated VMs<br /> Server virtualization<br /> Database<br />Share database instance <br /> Real Application Clusters<br />
    23. 23. Which Apps for Which DB Cloud? Each Architecture Serves Different Workloads <br />
    24. 24. Database Cloud PlanningIdentification of Applications to Migrate<br />New applications are deployed to the Cloud<br />Existing applications are migrated based on:<br />Difficulty<br />ROI<br />Suitability<br />The benefits and difficulties of consolidating existing applications in the Cloud will vary<br />Applications with highly varying peaks will show greatest benefit<br />The “lowest hanging fruit” should be migrated to the Cloud first<br />
    25. 25. Take delivery of Oracle Database Machine<br />case<br />Build from Scratch vs. ExadataCommonwealth Bank of Australia<br />Build From Scratch with Components<br />Oracle Exadata Database Machine<br />Reference Configurations<br />Testing and<br />Validation<br /><ul><li>Server Pool pre-configured
    26. 26. Faster deployment
    27. 27. Lower Risk</li></ul>Testing and<br />Validation<br />Installation and <br />configuration<br />Acquisition of<br />components<br />Installation and <br />configuration<br />Pre-implementation<br />System sizing<br />Testing and Validation<br />Acquisition of<br />components<br />Configuration<br />Weeks to Months<br />< 1 Week after Delivery<br />Weeks to Months<br /><ul><li>DB deployment time reduced from 3 months to < 1 week</li></ul>study<br />
    28. 28. Cloud Business Case<br />Cloud Computing Capabilities<br />Cloud Computing Effectiveness<br />Cloud Computing Roadmap<br />
    29. 29. Cloud Computing Effectiveness An Evolution of IT Consolidation <br /><ul><li>Use basic ROI model for improved cost efficiency?
    30. 30. May be organizational issues in measuring other costs
    31. 31. Who ‘owns’ licensing, power, financing, support, etc.?
    32. 32. Biggest benefit could be business agility
    33. 33. Is there an existing model of TTD (time to deploy)?
    34. 34. Are IT culture shifts required to achieve benefits?
    35. 35. E.g., New development process to achieve self-service goal</li></li></ul><li>Consider Direct, Indirect & Intrinsic ROI Some Are Harder to Measure<br />Direct cost savings<br />Reduced cost of consolidated HW is obvious…<br />But savings on operations costs can be 5X the HW savings<br />Service level improvement<br />Increased uptime from shared services<br />Plus reduction in faults from standardization<br />Business agility<br />Basic time to deploy reductions<br />Biggest win may be new business application possibilities<br />
    36. 36. case<br />ROI Example – U.S. State Government Major Savings in Staffing & Software<br />study<br />
    37. 37. Cost +Share out the amortized cost to internal tenants<br />Maybe a minimum floor price since there is an ultimate fixed cost of internal assets<br />Market RateMatch the open market rate e.g. compare with AWS<br />Market rate+Since private cloud offers added benefits e.g. security<br />Value+What is estimated value to the internal customer?<br />Provides additional tax/profit to pay for platform investment<br />May lose out to external competition<br />Private Cloud Pricing Models<br />
    38. 38. Cloud Business Case<br />Cloud Computing Capabilities<br />Cloud Computing Effectiveness<br />Cloud Computing Roadmap<br />
    39. 39. Cloud Computing Readiness May Require Diverse Business Changes<br /><ul><li>Consider, for example, IT governance & risk management, information modeling & ownership, operations & service management.
    40. 40. How are these areas managed today?
    41. 41. identified responsibilities, documented processes, etc.
    42. 42. Do you have a mechanism for assessing capabilities in each area?
    43. 43. How will you identify needs for changes or improvements to support cloud computing?</li></li></ul><li>Example Cloud Capabilities by Domain Areas Important to Cloud Readiness<br /><ul><li>Business & IT drives
    44. 44. Costs & Benefits
    45. 45. Reference architecture
    46. 46. Standards
    47. 47. Executive sponsorship
    48. 48. Roles & responsibilities
    49. 49. Model templates
    50. 50. Data ownership
    51. 51. Model packaging
    52. 52. Service monitoring
    53. 53. Risk management
    54. 54. Cloud change management
    55. 55. Services portfolio management
    56. 56. Services engineering approach
    57. 57. Capacity management
    58. 58. Operational tools & processes
    59. 59. To succeed at Cloud services adoption, an organization must adequately progress in all the appropriate domains. </li></li></ul><li>Cloud Computing RoadmapHow Will Your Cloud Be Introduced? <br />Cloud computing efforts range from small ‘experiment’ projects to major strategic initiatives.<br />Most companies have multiple projects underway or anticipated.<br /><ul><li>Separate from the new architecture, is there a plan for how the new model will be rolled out?
    60. 60. E.g., by application, by business unit, by geography…
    61. 61. Is cloud viewed as a limited tactical deployment, major strategic initiative, or both?</li></li></ul><li>Focused Implementation Vs. Wide Diffusion<br />Optimized<br />Cloud<br />Strategic<br />Managed<br />Cloud<br />Exploiting<br />Cloud Maturity<br />Systematic<br />Cloud<br />Expanding<br />Opportunistic<br />Cloud<br />Tactical<br />Exploring<br />Ad Hoc<br />Cloud<br />Application<br />Level<br />Suite<br />Level<br />Region<br />Level<br />Data Center<br />Level<br />Enterprise <br />Level<br /><ul><li>Strategic – Complete migration for a given architecture/application, often focusing on revenue enhancement
    62. 62. Tactical – Wide deployment of a limited technology (e.g. virtualization), often focusing on cost reduction</li></ul>Cloud Adoption<br />
    63. 63. Key Business/IT Transformations<br />Current Approach<br />Cloud Approach<br />IT Architecture designed up front (early binding)<br />IT operations developed and performed by the IT department<br />Systems and application management was specific to select systems and applications<br />Build out infrastructure up-front, expand later <br />IT will move to building up-front operational functions for a self-service model. <br />The cloud ‘control plane’ has to be architected as a general service <br />
    64. 64. Key Logical Abstractions to Consider Clouds Require New ‘Models’<br />Separation of roles (e.g., Cloud Provider vs Service Developer)<br />.<br />Deployable Entities (aka VDCs) include Service Templates and Service Context (e.g. – OVAB ‘Assemblies’)<br />Logical resource ‘pools’ abstraction of physical resources <br />
    65. 65. Roadmap to CloudMulti-Dimensional Journey<br />Optimize<br />Automate<br /> Consolidate<br />Standardize<br />Achieve new operational models & greatest efficiency <br />Reduce the manual tasks for managing IT<br />Reduce the footprint of deployed applications<br />Define a single solution for a given problem<br />Individual enterprises or applications may join the roadmap at different points<br />
    66. 66. case<br />Cloud is a Multi-Year Journey Northern Trust PaaS Example<br /><ul><li>Each release of an architecture platform evolves into what the industry now calls PaaS
    67. 67. JavaArch1.x – Web SSO Security
    68. 68. Web2000 – Co-Hosting applications, enterprise logging, templated environment, scripted builds
    69. 69. JavaArch8 – Messaging API’s, scripted deployments, app metrics, monitoring
    70. 70. JavaArch11 – Virtualized, automated creation, on-demand resources, end-to-end experience </li></ul>PaaS has allowed the business to invest in developing new capabilities rather than Infrastructure<br />study<br />
    71. 71. Some Final Thoughts….<br />
    72. 72. Planning Your Cloud – Summary <br />Decide what kind of cloud is under consideration<br />Infrastructure, Platform… , Private, Hybrid….<br />Identify measurable benefits<br />Use appropriate ROI models<br />Evaluate organizational readiness<br />Develop a clear roadmap for deployment<br />Identify key IT and business transformations<br />
    73. 73. Oracle Insight For Data Center Technology A Structured Approach To Address Improvements<br />1. Typical Data Center Challenges<br />2. Tailored Process<br />3. Impactful Deliverables<br />A. DC Performance Improvements <br /><ul><li>How to manage the increased demand?
    74. 74. How to improve data center operations?
    75. 75. How to optimize technology?
    76. 76. What is the business case (ROI)?</li></ul>B. DC ECONOMICS<br />C. DC Technology roadmap<br />D. Workload analysis<br />Oracle Insight for Data Center Technology<br /> aims to resolve these challenges and create impactful deliverables using a tailored process<br /><br />
    77. 77. For More Information….<br /><br />