Workforce Management Implementation Series

SaaS Implementations – Top Ten Considerations Scott BrownPresident, Sability

James ShryockPrincipal, Sability

Introduction

• Introductions• What is SaaS?

Traditional Implementations

Operational ModelsOn

Premises

WebClient Serve

r

Hosted

SaaS

Strict Pseudo

ASP

Web Client Server

Full

SaaS - Defined

• Software as a Service• Characteristics

– Off premises– Hosted or Managed by software vendor– Typically one code base (no customizations)– Architecture - Controversial

• Revolves around Multitenancy• App servers and databases

Software as a Service: +/-

Advantages• Minimal Infrastructure• No IT resources required• Upgrades are almost a non-issue• Vendor has hosting expertise• Scalability• Pay as you go• No large Cap-Ex• Typically not a large implementation

cost• Regulatory Changes quickly reflected

within Software

Disadvantages• No data access• No customizations - configuration only• Slower turnaround for any system

request• No control over upgrade timing

Software as a Service: Y/N

Yes No

Very Large Enterprise

High degree of customizations

Unique security requirements (CIA)

Special Integration Requirements

Dispersed/remote workforce

Willing to redefine processes

High growth

Culture of innovation/business driven

decisions

On Premises

Operational ModelsOn

Premises

WebClient Serve

r

Hosted

SaaS

Strict Pseudo

ASP

Web Client Server

Full

• Applications run in your company’s data center

• Company manages complete stack– Hardware– Systems software

• Operating system• Web & Application servers• Database servers

– Application software

On Premises: +/-

Advantages• Ultimate flexibility• Customizable• Absolute control• Interface flexibility• Direct database access

Disadvantages• Scalability limited by

your hardware• Deep expertise required• Tendency is to over-

customize• Upgrades require a lot of

resources

On premises: Y/N

Yes No

Limited capital

Distributed organization

Limited technical resources

Likelihood of Acquisitions

Very complex functional requirements

Predictable/moderate growth

Corporate restriction for distribution of data

Large enterprise

1 - SaaS – Am I ready?

• Do we need a new system?– Current System Issues– Missing Functionality

• Is our Company Ready?• Will our Company support a SaaS model?

2 - SaaS – How long will this take?

• Short Answer – It Depends• SaaS Implementations typically are much

shorter then Hosted Implementations• Timelines tend to be more predictable then

traditional implementations

3 - SaaS – Internal Resources

• Resource requirements• Application knowledge• Interface requirements• Vendor vs. Third party

4 - SaaS – Can I do this without help?

• How much time do you have?• Is it worth it?• Will the vendor let you?• Expertise

5 - SaaS – Onsite or Offsite Resources?

• Traditional model – all onsite resources– Little or no remote access

• Offsite model– Communications

• It’s ALL remote access• WebEx• Conference calls

6 - SaaS – Interfacing

• Standard interfaces– HR– Payroll

• Other– Cost systems– Single sign on

7 - SaaS – Uptime

• Uptime measurements– The 9’s

• Our experiences

8 - SaaS – Customizations

• What? No customizations?

9 - SaaS – Configuring

• I configure the system WHERE???

Production Test system

10 - SaaS – Backups

• Be sure to have a mechanism in place to get a copy of your data.

• Determine how frequently that a backup will be possible.

• Determine if that frequency will meet your needs.

• Insure you backup your configuration as well as your data.

11 - SaaS – Life Cycle

• Periodic Releases – Timing is dictated by the vendor

• Upgrades• New Car

SaaS – What Works?• Speed/cost to deploy/implement

– Shared responsibility– Fixed cost

• Vendor service– Built in incentive for vendors to provide high level of service

• Fees: simple model• Innovation

– Vendors tend to be technical leaders– Foster a culture of innovation internal to vendors, and reaching out to customers

• Security– Vendors tended to be more proactive than their IT departments

• User interface and accessibility• Scalability

– Close to a non-issue for customers– Only concern is scalability of mobile infrastructure and internet in general

SaaS – Do your Homework• SaaS is not a slam-dunk• SaaS adopters advised extra attention be paid to these key areas:

– Evaluate vendor roadmap and enhancement history• Did the vendor meet targets in the past?• Are planned enhancements pertinent to your requirements?• What have the vendors customers experienced when upgraded?

– Assess vendor management teams• Does the management team have a successful track record?

– Request detailed documentation around security• SAS 70 Type II or ISO 27001

– Evaluate integration capabilities closely• Capabilities need to be designed into the API• Represents a large part of implementation effort

Thank you

scott.brown@sability.com404-521-2001 x2090

james.shryock@sability.com404-521-2001 x2092

twitter: #sability