Sability SaaS Implementations
•Transferir como PPTX, PDF•
0 gostou•530 visualizações
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: http://ity.vc/webi100
Recomendados
Recomendados
Mais conteúdo relacionado
Último
Último (20)
Destaque
Destaque (20)
Sability SaaS Implementations
- 1. Workforce Management Implementation Series SaaS Implementations – Top Ten Considerations Scott Brown President, Sability James Shryock Principal, Sability
- 2. Introduction • Introductions • What is SaaS?
- 3. Traditional Implementations Operational Models On Premises Hosted Client Web SaaS ASP Full Server Client Strict Pseudo Web Server
- 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. 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. 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. On Premises • Applications run in your company’s Operational Models data center • Company manages complete stack On Premises – Hardware Hosted – Systems software Client • Operating system Web SaaS & ApplicationASP • Web Full Server servers • Database servers – Application software Client Strict Pseudo Web Server
- 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. On premises: Y/N Yes No Likelihood of Large enterprise Acquisitions Corporate restriction for Limited technical distribution of data resources Predictable/moderate Distributed organization growth Very complex functional Limited capital requirements
- 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. 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. 3 - SaaS – Internal Resources • Resource requirements • Application knowledge • Interface requirements • Vendor vs. Third party
- 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. 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. 6 - SaaS – Interfacing • Standard interfaces – HR – Payroll • Other – Cost systems – Single sign on
- 16. 7 - SaaS – Uptime • Uptime measurements – The 9’s • Our experiences
- 17. 8 - SaaS – Customizations • What? No customizations?
- 18. 9 - SaaS – Configuring • I configure the system WHERE??? Production Test system
- 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. 11 - SaaS – Life Cycle • Periodic Releases – Timing is dictated by the vendor • Upgrades • New Car
- 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. 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. Thank you scott.brown@sability.com 404-521-2001 x2090 james.shryock@sability.com 404-521-2001 x2092 twitter: #sability
Notas do Editor
- Software Architecture definition: An architecture is the set of significant decisions about the organization of a software system, the selection of structural elements and their interfaces by which the system is composed, together with their behavior as specified in the collaborations among those elements, the composition of these elements into progressively larger subsystems, and the architectural style that guides this organization -- these elements and their interfaces, their collaborations, and their composition. [Kruchten]4
- No control over upgrades: insure your vendor is sensitive to any blackout periods of your industry. If a SaaS provider is typically providing service to manufacturers, may be surprised by an upgrade during your blackout season, which may typically be a slow time for manufacturers.
- No control over upgrades: insure your vendor is sensitive to any blackout periods of your industry. If a SaaS provider is typically providing service to manufacturers, may be surprised by an upgrade during your blackout season, which may typically be a slow time for manufacturers.
- No control over upgrades: insure your vendor is sensitive to any blackout periods of your industry. If a SaaS provider is typically providing service to manufacturers, may be surprised by an upgrade during your blackout season, which may typically be a slow time for manufacturers.
- According to SaaS Customers:Foresterhttp://bit.ly/hogI3mMay 5, 2010Real-World Insights Into SaaS ImplementationSuccessSatisfied SaaS Buyers Share Their Dos And Don’tsby Liz Herbertwith Christine Ferrusi Ross and Elizabeth RoseSaaS Clients Validate Anticipated Benefits — And Then SomeClients we spoke with were generally satisfied across areas they had initially cited as concerns:· Speed to deploy. Firms found that speed-to-delivery met their expectations. Initial deploymentwas fast, and, moreover, once the software was up and running, SaaS models allowed for rapidupgrade cycles to roll out new functionality.· Attention from vendor. Most interviewees felt that their SaaS vendors were responsive andproactive. Because some SaaS vendors are fairly new and fairly small, clients have greatlybenefited from the opportunity to help drive development of these SaaS vendors’ road maps.· Cost. Most clients were satisfied with initial costs around subscriptions and implementation.Many SaaS clients were still determining whether the long-term TCO made sense for them, butseveral customers felt that they were saving millions based on a net present value model.· Innovation. One key benefit that firms highlighted was their vendor’s ability to drive fast-pacedinnovation. SaaS vendors are often small and nimble, which allows them to react quickly toclient demand or changing market trends. In many cases, SaaS vendors also foster a culture ofinnovation — from employees as well as from partners and customers.· Security. The majority of the customers we interviewed revealed that their SaaS vendors weredoing more to secure their data than their own IT departments could do. One reference said,“Our greatest fear became our biggest confidence.”· User interface and accessibility. Most clients felt that the visibility and access across businessunits for SaaS applications is great; typically, all you need is an Internet connection in order toaccess the application. Many clients also highlighted the ease of use and the modern look andfeel of SaaS interfaces, which drive adoption and reduce the learning curve.But SaaS Clients Also Warn Of Concerns And ChallengesWhile the customers we interviewed were happy overall, they also cited key areas for improvement:· Ability to follow through on functional requests. Some SaaS clients felt there was a gapbetween input into road maps and the vendors’ ability to follow through. While most clientsfelt that SaaS vendors were very responsive, and some perceived the added benefit of helpingto drive the road map by being an early customer, some SaaS clients felt that smaller vendorsstruggled to follow through on all their requests in a short time frame.Integration issues. Some clients complained that they lost prior functionalities and tools they’dbeen using when they transitioned to SaaS. Although integration is possible in most cases, someclients struggled to find tools, prebuilt connectors, and skilled developers, compared with on premiseintegration capabilities.· Breadth of functionality. Many SaaS vendors are newer and therefore are still building out corefunctionality. In many application areas, there is still a gap between functionality available on premiseand SaaS options. On the flip side, some firms find that SaaS functionality is enough tomeet their needs and that reduced functionality can simplify and streamline implementationand eliminate expensive rollouts of features that ultimately go unused.Recommendationskey areas of due diligence To gain anticipated benefits of SaaSThe customers Forrester interviewed decided that the potential benefits of going with SaaSoutweighed their concerns — but only after a careful selection process. Critical success factorsinclude:· Closely assessing vendor management teams and strategies. SaaS clients advise takinga close look at vendors’ management teams, including their vision of the company andtheir go-to-market strategy. While this is a good idea for on-premise purchases as well, SaaSinvestments are even more dependent on ongoing service, upgraded road maps, andgrowth of the ecosystem of partners and other customers.· Requesting detailed documentation around security. SaaS vendors should be able toshare security documentation. One customer requested a 45-page treatise outlining thevendor’s approach to data security. SaaS vendors should also provide proof and details ofrelevant audits, like the SAS 70 Type II (at both application and data center layer) or the ISO27001.· Evaluating APIs and relevant documentation. One seasoned cloud customer expressedhis partiality to vendors with open application planning interfaces (APIs) that were welldocumented to ensure smooth integration. Some firms also investigated integrationpartners, such as Informatica, Boomi, and Cast Iron Systems, as well as depth of prebuiltconnectors. Beyond application and data integration, SaaS clients also advised investigatinghow the product integrates with your firm’s approach to identity management and singlesign-on, such as Lightweight Directory Access Protocol (LDAP) and Active Directory Integration.
- Foresterhttp://bit.ly/hogI3mMay 5, 2010Real-World Insights Into SaaS ImplementationSuccessSatisfied SaaS Buyers Share Their Dos And Don’tsby Liz Herbertwith Christine Ferrusi Ross and Elizabeth RoseSaaS Clients Validate Anticipated Benefits — And Then SomeClients we spoke with were generally satisfied across areas they had initially cited as concerns:· Speed to deploy. Firms found that speed-to-delivery met their expectations. Initial deploymentwas fast, and, moreover, once the software was up and running, SaaS models allowed for rapidupgrade cycles to roll out new functionality.· Attention from vendor. Most interviewees felt that their SaaS vendors were responsive andproactive. Because some SaaS vendors are fairly new and fairly small, clients have greatlybenefited from the opportunity to help drive development of these SaaS vendors’ road maps.· Cost. Most clients were satisfied with initial costs around subscriptions and implementation.Many SaaS clients were still determining whether the long-term TCO made sense for them, butseveral customers felt that they were saving millions based on a net present value model.· Innovation. One key benefit that firms highlighted was their vendor’s ability to drive fast-pacedinnovation. SaaS vendors are often small and nimble, which allows them to react quickly toclient demand or changing market trends. In many cases, SaaS vendors also foster a culture ofinnovation — from employees as well as from partners and customers.· Security. The majority of the customers we interviewed revealed that their SaaS vendors weredoing more to secure their data than their own IT departments could do. One reference said,“Our greatest fear became our biggest confidence.”· User interface and accessibility. Most clients felt that the visibility and access across businessunits for SaaS applications is great; typically, all you need is an Internet connection in order toaccess the application. Many clients also highlighted the ease of use and the modern look andfeel of SaaS interfaces, which drive adoption and reduce the learning curve.But SaaS Clients Also Warn Of Concerns And ChallengesWhile the customers we interviewed were happy overall, they also cited key areas for improvement:· Ability to follow through on functional requests. Some SaaS clients felt there was a gapbetween input into road maps and the vendors’ ability to follow through. While most clientsfelt that SaaS vendors were very responsive, and some perceived the added benefit of helpingto drive the road map by being an early customer, some SaaS clients felt that smaller vendorsstruggled to follow through on all their requests in a short time frame.Integration issues. Some clients complained that they lost prior functionalities and tools they’dbeen using when they transitioned to SaaS. Although integration is possible in most cases, someclients struggled to find tools, prebuilt connectors, and skilled developers, compared with on premiseintegration capabilities.· Breadth of functionality. Many SaaS vendors are newer and therefore are still building out corefunctionality. In many application areas, there is still a gap between functionality available on premiseand SaaS options. On the flip side, some firms find that SaaS functionality is enough tomeet their needs and that reduced functionality can simplify and streamline implementationand eliminate expensive rollouts of features that ultimately go unused.Recommendationskey areas of due diligence To gain anticipated benefits of SaaSThe customers Forrester interviewed decided that the potential benefits of going with SaaSoutweighed their concerns — but only after a careful selection process. Critical success factorsinclude:· Closely assessing vendor management teams and strategies. SaaS clients advise takinga close look at vendors’ management teams, including their vision of the company andtheir go-to-market strategy. While this is a good idea for on-premise purchases as well, SaaSinvestments are even more dependent on ongoing service, upgraded road maps, andgrowth of the ecosystem of partners and other customers.· Requesting detailed documentation around security. SaaS vendors should be able toshare security documentation. One customer requested a 45-page treatise outlining thevendor’s approach to data security. SaaS vendors should also provide proof and details ofrelevant audits, like the SAS 70 Type II (at both application and data center layer) or the ISO27001.· Evaluating APIs and relevant documentation. One seasoned cloud customer expressedhis partiality to vendors with open application planning interfaces (APIs) that were welldocumented to ensure smooth integration. Some firms also investigated integrationpartners, such as Informatica, Boomi, and Cast Iron Systems, as well as depth of prebuiltconnectors. Beyond application and data integration, SaaS clients also advised investigatinghow the product integrates with your firm’s approach to identity management and singlesign-on, such as Lightweight Directory Access Protocol (LDAP) and Active Directory Integration.