Value Of Cloud Computing For Fed Governmen Oct 8 Tim May


Published on

Tim May of Apptis on Cloud Computing in the Federal space

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Value Of Cloud Computing For Fed Governmen Oct 8 Tim May

  1. 1. October 8, 2008 Tim May - Apptis
  2. 2. Agenda • What is It? • Potential Implementations • What are the Obstacles • Derived Value
  3. 3. What is It Many definitions – shapes – sizes… • “…a style of computing where massively scalable IT- related capabilities are provided „as a service‟ using Internet technologies to multiple external customers” – Gartner, September 30, 2008 • “ The internet as an operating system” – Reuven Cohen, CTO Enomaly • “It is a style of computing where IT-related capabilities are provided “as a service”, allowing users to access technology-enabled services from the Internet (quot;in the cloudquot;) without knowledge of, expertise with, or control over the technology infrastructure that supports them” - Wiki • HOWEVER – Internal “Cloudification” is occurring Conceptual comparison to utility services • Corporations created their own electrical power • The change: regional-based power suppliers provide ability to use power based on need 4
  4. 4. The More Things Change, The More They Stay The Same „60s „70s „80s „90s Present 5
  5. 5. A “Desired End Result” Perspective What is It? - A way of deploying and managing IT infrastructure that allows for greater utilization/effectiveness of the assets - Improved use and value of existing equipment What Problem am - Reduced capital budgets (no equipment purchases) I Looking to - Jettisoned responsibility (staff and facilities); outsourced Solve? accountability - Desire to stay current with technology and business models - Application Development APPLICATION - Single Application Deployment (w/ scalability) CONTEXT is - Multiple/hybrid Application Deployments KING! - Modernization of Legacy Applications 6
  6. 6. Potential Implementations Commercial/External Cloud • Application Design/Prototype/Test • Continuity of Operations • Increased Availability/Redundancy • Non-Refresh Comment: Not (initially) likely to be leveraged for most internal Agency applications 7
  7. 7. Potential Implementations Hybrid Cloud • Cloudbursting or Surge • Extension of existing IT infrastructure • Highly application specific Comment: Could be leveraged for some select internal Agency applications (with some work/modifications) 8
  8. 8. Potential Implementations Vertical Cloud • Application-specific (or related group of applications) • Serves a Line of Business • Usually pre-existing infrastructure • Constrained by cloud provider‟s features and functionality – limited customization Comment: Could be leveraged for some select internal Agency applications (with some work/modifications) 9
  9. 9. Potential Implementations “P” Cloud • Maximize efficiency of current infrastructure and assets • Use of virtualization and related technologies to increase utilization and metering/monitoring • Requires application, process, security and compliance modifications Comment: Most likely initial adoption of cloud for some internal Agency applications 10
  10. 10. Obstacle – Trust, Reliability… Employees Clients Information The Enterprise‟s Most Valuable Assets
  11. 11. Obstacle – Trust, Reliability… Employees Clients Information ADP Aplicor Ceridian Entellium FuseMail Deltek NetSuite Google MasterTax Oracle/Siebel Intermedia NetChex RightNow MailTrust Paychex Sage NetworkSolutions Perquest Simplicato Paylocity Soffront Sparklist SurePayroll eSalestrack RunBox The Enterprise‟s Most Valuable Assets
  12. 12. Other Obstacles • Already Spent $ • Application/Systems Readied • Knowledge • Proof Points • Providers • Acquisition • Licensing • Culture • Security 13
  13. 13. Value to the Government • Focus on the mission • Test – validate – prototype • Capital-ex reduction • Ability to disengage • Efficiency 14
  14. 14. So What‟s Next • Research, inquire and understand • Select appropriate situations and problems • Make technical and supporting organizational changes • Manage expectations – not a panacea • Embrace initial successes and expand accordingly 15
  15. 15. Questions 16