Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sability SaaS Implementations


Published on

SaaS based Workforce Management (WFM) systems are here. You or someone in your organization may be considering this option. Many organizations do appreciate the advantages of SaaS systems, but have questions about how they can be deployed.

This presentation by James Shryock, Sability Principal and Practice Director for SaaS Implementations, will help you understand why SaaS implementations are different and what your organization needs to know before you commit to a solution. James will be presenting information based on his experience with dozens of real-world SaaS implementations with companies of varying size and industry.

You can watch a full video presentation here:

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

  • Be the first to like this

Sability SaaS Implementations

  1. 1. Workforce Management Implementation SeriesSaaS Implementations – Top Ten Considerations Scott Brown President, Sability James Shryock Principal, Sability
  2. 2. Introduction• Introductions• What is SaaS?
  3. 3. Traditional Implementations Operational ModelsOn Premises Hosted ClientWeb SaaS ASP Full Server Client Strict Pseudo Web Server
  4. 4. 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
  5. 5. Software as a Service: +/-Advantages Disadvantages• Minimal Infrastructure • No data access• No IT resources required • No customizations - configuration only• Upgrades are almost a non-issue • Slower turnaround for any system• Vendor has hosting expertise request• Scalability • No control over upgrade timing• Pay as you go• No large Cap-Ex• Typically not a large implementation cost• Regulatory Changes quickly reflected within Software
  6. 6. Software as a Service: Y/N Yes No Culture of Special Integration innovation/business driven Requirements decisions Unique security requirements High growth (CIA) Willing to redefine processes High degree of customizations Dispersed/remote workforce Very Large Enterprise
  7. 7. On Premises • Applications run in your company’s Operational Models data center • Company manages complete stackOn Premises – Hardware Hosted – Systems software Client • Operating systemWeb SaaS & ApplicationASP • Web Full Server servers • Database servers – Application software Client Strict Pseudo Web Server
  8. 8. On Premises: +/-Advantages Disadvantages• Ultimate flexibility • Scalability limited by• Customizable your hardware• Absolute control • Deep expertise required• Interface flexibility • Tendency is to over-• Direct database access customize • Upgrades require a lot of resources
  9. 9. On premises: Y/N Yes No Likelihood of Large enterprise AcquisitionsCorporate restriction for Limited technical distribution of data resources Predictable/moderate Distributed organization growthVery complex functional Limited capital requirements
  10. 10. 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?
  11. 11. 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
  12. 12. 3 - SaaS – Internal Resources• Resource requirements• Application knowledge• Interface requirements• Vendor vs. Third party
  13. 13. 4 - SaaS – Can I do this without help?• How much time do you have?• Is it worth it?• Will the vendor let you?• Expertise
  14. 14. 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
  15. 15. 6 - SaaS – Interfacing• Standard interfaces – HR – Payroll• Other – Cost systems – Single sign on
  16. 16. 7 - SaaS – Uptime• Uptime measurements – The 9’s• Our experiences
  17. 17. 8 - SaaS – Customizations• What? No customizations?
  18. 18. 9 - SaaS – Configuring• I configure the system WHERE??? Production Test system
  19. 19. 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.
  20. 20. 11 - SaaS – Life Cycle• Periodic Releases – Timing is dictated by the vendor• Upgrades• New Car
  21. 21. 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
  22. 22. 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
  23. 23. Thank you 404-521-2001 404-521-2001 x2092 twitter: #sability