Anything as a Service (XaaS) –Factors to Consider

Stephen NewellClient Technical Advisor – Illinois Public Sector

IBM Corporationsrnewel@us.ibm.com

Since 2009

http://www.google.com/trends

Fewer questions

2009 2014

Hype declining

2010 2011 2012 2013 2014

#1 Cloud Cloud

#2 Cloud

#3 Cloud

#4 Cloud

#5

Annual NASCIO State CIO SurveyPriority Technologies

Top priority

And, in Illinois - it’s the law

Based on Federal guidelines

Anything as a Service (XaaS)

XaaS is the essence of cloud computing, and these days almost anything can

be delivered as a service: software, infrastructure, storage, platforms, data, you

name it. The concept is no longer new but it’s far from settled. Challenges

remain in building the business case and determining the risks and rewards.

This session explores the factors to consider when

deciding if, when and how to pull the trigger.

Today

The Good The Bad

SaaS Business / Productivity ToolsMinimal staffingReady to useBrowser / app / APIMobile

Predefined serviceSaaS silosIntegrationLock-inWait on outage

PaaS Innovative / ProgrammabilityLeverage APIs / Sell APIsSocial / MobileDevOps

Constrained by stackExpensive at scaleLock-inThrottledWait on outage

IaaS Control / Resource ProvisioningPerformance / scale / transactionsSensitive data / regulatory complianceSupport complex integrationDesign to avoid outage

Limited configurationsMore skills / new skillsMore staffBeware of porting existing

Considerations - service models

Note: None of these are hard and fast. Taking best case for The Good. Taking worst case for The Bad

The Good The Bad

Public Low costSimple and quick to start• Easy to buy• No contractMinimal staffingUnlimited scaling

SLAs not sufficientProvider supply chainNetwork performanceNo control / transparencySecurity concernsLimited flexibilityExit strategy

Hybrid Use private for sensitive dataUse public as much as possibleChoice and flexibility

Interconnect multiple cloudsMismatch of toolsets / securityMore complex

Community Lower cost due to larger scaleShared service

Governance effortCoordination effort

Private Behind your firewallSingle tenantControl• Security• Compliance• D/R• Configurations

Higher costFacilities investmentCapacity ceilingUpfront investmentTime to establish / buildAdministration cost

Considerations - deployment models

Note: None of these are hard and fast. Taking best case for The Good. Taking worst case for The Bad

Example

Private community cloud for state public sector entities

Hosted and administered in two (for D/R) state data centers

Runs on state network

Complies with state security standards plus compliance for each workload

Offered by California Department of Technology Office of Technology Services (OTech)

Infrastructure supplied and managed by a cloud service vendor (IBM).

Otech manages all other aspects of the offering.

Custom architecture to fit with state IT tools and processes.

Usage based with no initial cost to the state.

IaaS now. PaaS / DaaS / STaaS next. SaaS third.

Up to 70% lower cost than current rates.

Details at: http://www.servicecatalog.dts.ca.gov/services/cloud/calcloud/overview.html

Considerations - moving forwardCreate a vision / policy / strategy / roadmap

Establish governance

Lead the organizational change

Select a partner

Think big. Start small.

Range of offerings – our suite of offerings give us many ways to implement your strategyIaaS / PaaS / SaaSPrivate / Community / Hybrid / PublicYou build and manage / IBM build and manageOpen standards

Enterprise class – our offerings include 99.95% SLAs with disaster recovery for critical applications

Control – our offerings can give you extensive control of your service

Expertise – over 100,000 advisors on cloud worldwideConsultingServices

IBM