Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
SaaS PowerPoint Presentation

SaaS

10 Views Download Presentation
Download Presentation

SaaS

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SaaS

  2. What is SaaS • Imagine a system • where you don't have to buy new hardware or update software • where you pay nothing or pay as much as you use • where everything is done as a service: Infrastructure, computing, storage and usage • where you don't worry about your resources spent on Infrastructure security and operational security • where you cut your IT spending by 99% • where you have freedom of usage from anywhere with internet connectivity • which is eco-friendly

  3. SaaS is directly consumable by the end-user. More specifically, SaaS provides the full stack of cloud services, and ideally presents these to end-user in a fashion that is not radically different from how users expect to use their applications.

  4. Characteristics of SaaS • The application is hosted and operated by the software developer themselves. • Can access, manage, and personalize software over the internet • Functionality enhancements are completely controlled by the vendor. Frequent upgrade cycles occur with new features being introduced multiple times per year. • More

  5. Delivery Model

  6. SaaS - Pros • Stay focused on business processes • Change software to an Operating Expense instead of a Capital Purchase, making better accounting and budgeting sense. • Create a consistent application environment for all users • No concerns for cross platform support • Easy Access • Reduced piracy of your software • Lower Cost • For an affordable monthly subscription • Implementation fees are significantly lower • Continuous Technology Enhancements

  7. SaaS - Cons • Initial time needed for licensing and agreements • Trust, or the lack thereof, is the number one factor blocking the adoption of software as a service (SaaS). • Centralized control • Possible erosion of customer privacy • Absence of disconnected use

  8. Traditional vs. SaaS Traditional Software On-DemandUtility Plug In, SubscribePay-per-Use Build Your Own

  9. Traditional packaged software Software as a serivce Comparison of Business Model • Designed from the outset up for delivery as Internet-based services • Designed for customers to install, manage and maintain. • Architect solutions to be run by an individual company in a dedicated instantiation of the software • Designed to run thousands of different customers on a single code

  10. Traditional packaged Software Software as a serivce • Infrequent, major upgrades every 18-24 months, sold individually to each installed base customer. • Frequent, "digestible" upgrades every 3-6 months to minimize customer disruption and enhance satisfaction. • Version control • Upgrade fee • Fixing a problem for one customer fixes it for everyone • Streamlined, repeatable functionality via Web services, open APIs and standard connectors • May use open APIs and Web services to facilitate integration, but each customer must typically pay for one-off integration work.

  11. Hidden Cost

  12. Applicability of SaaS • Enterprise Software Application • Perform business functions • Organize internal and external information • Share data among internal and external users • The most standard type of software applicable to Saas model • Example: Saleforce.com CRM application, Siebel On-demand application

  13. Applicability of SaaS (Continue) • Single-User software application • Organize personal information • Run on users’ own local computer • Serve only one user at a time • Inapplicable to SaaS model • Data security issue • Network performance issue • Example: Microsoft office suite

  14. Applicability of SaaS (Continue) • Infrastructure software • Serve as the foundation for most other enterprise software application • Inapplicable to SaaS model • Installation locally is required • Form the basis to run other application • Example: Window XP, Oracle database

  15. Applicability of SaaS (Continue) • Embedded Software • Software component for embedded system • Support the functionality of the hardware device • Inapplicable to SaaS model • Embedded software and hardware is combined together and is inseparable • Example: software embedded in ATM machines, cell phones, routers, medical equipment, etc.

  16. SaaS Architecture • Fueled by • Bandwidth technologies • The cost of a PC has been reduced significantly with more powerful computing but the cost of application software has not followed • Timely and expensive setup and maintenance costs • Licensing issues for business are contributing significantly to the use of illegal software and piracy.

  17. High-Level Architecture • There are three key differentiators that separate a well-designed SaaS application from a poorly designed one • scalable • multi-tenant-efficient • configurable • Scaling the application - maximizing concurrency, and using application resources more efficiently • i.e. optimizing locking duration, sharing pooled resources such as threads and network connections, caching reference data, and partitioning large databases.

  18. High-Level Architecture (con’t) • Multi-tenancy – important architectural shift from designing isolated, single-tenant applications • One application instance must be able to accommodate users from multiple other companies at the same time • All transparent to any of the users. • This requires an architecture that maximizes the sharing of resources across tenants • is still able to differentiate data belonging to different customers.

  19. High-Level Architecture (con’t) • Configurable - a single application instance on a single server has to accommodate users from several different companies at once • To customize the application for one customer will change the application for other customers as well. • Traditionally customizing an application would mean code changes • Each customer uses metadata to configure the way the application appears and behaves for its users. • Customers configuring applications must be simple and easy without incurring extra development or operation costs

  20. Saas Financials • 4 ways software companies are pricing their products • Open Source – free basic products but charge a fee for the upgrade to the premium product (i.e. Apache, Linux, etc) • License software – main way its being done. Customer like this way because they own the software as an asset • Leased Software – deployed at customer site but leased for a time period. Used in the days of the mainframe • SaaS – subscription pricing. Like leasing is considered and expense but upgrades and maintenance is free and seamless

  21. Saas Financials (con’t) • Legal activities should be involved in the acquisition of mission-critical SaaS software • Companies are losing control of their data in the SaaS model • Depending on the service provider for security and data access. • Need to setup contractual relationship with the SaaS provider • Setup escrow account • With conditions of being able to run application in house • Ability to move data from current provider to new location • Also Service Level Agreements (SLAs) for • Availability, response times, notifications of outages • Data integrity, data privacy, frequency of backup, support and disaster recovery

  22. Saas Financials (con’t) • CIO decides if SaaS software will benefit IT while CFO decides if it is economical for the whole firm • Leasing vs Buying • Similar to decision of leasing or buying a car • Need to compare costs that effect cash flows such as depreciation, interest on financing, tax and opportunity cost • Use an experience Accountant

  23. Software renting example • Some company provides casual or long term software application rental, enterprise wide software deployment and management • Offerings • No contracts to sign - rent for as long as you want • Manage, deploy and track leased software resources more effectively in real-time. • No cost software upgrades • Systems administrators can allocate application software to users in real time • Change the allocation of licenses as required and reduce the number of licenses that the company needs to buy. • Save work to local hard drives, or on their servers if you are a pay by-the-month user. • Allow users to rent software on an hourly, daily, weekly or monthly basis

  24. Software offering & Pricing

  25. Cost Per Usage Chart of MS Word

  26. User Benefit • Lower Cost of Ownership • The software is paid when it is consumed, no large upfront cost for a software license • Low cost per user per month, with no upfront • Since no hardware infrastructure, installation, maintenance, and administration, budgeting is easy • The software is available immediately upon purchasing • Focus on Core Competency • The IT saving on capital and effort allows the customer to remain focused on their core competency and utilize resources in more strategic areas. • Access Anywhere • Users can use their applications and access their data anywhere they have an Internet connection and a computing device • This enhances the customer experience of the software and makes it easier for users to get work done fast • Freedom to Choose (or Better Software) • The pay-as-you-go (PAYG) nature of SaaS enables users to select applications they wish to use and to stop using those that no longer meet their needs. Ultimately, this freedom leads to better software applications because vendors must be receptive to customer needs and wants. • New Application Types • Since the barrier to use the software for the first time is low, it is now feasible to develop applications that may have an occasional use model. This would be impossible in the perpetual license model. If a high upfront cost were required the number of participants would be much smaller. • Faster Product Cycles • Product releases are much more frequent, but contain fewer new features than the typical releases in the perpetual license model because the developers know the environment the software needs to run • This new process gets bug fixes out faster and allows users to digest new features in smaller bites, which ultimately makes the users more productive than they were under the previous model. • Additionally, it is not necessary for the customer to continually upgrade the software. Each time the user accesses the software, it is the “latest and greatest” version that’s available.

  27. Vendor Benefits • Increased Total Available Market – • Lower upfront costs and reduced infrastructure capital translate into a much larger available market for the software vendor, because users that previously could not afford the software license or lacked the skill to support the necessary infrastructure are potential customers. • A related benefit is that the decision maker for the purchase of a SaaS application will be at a department level rather than the enterprise level that is typical for the perpetual license model. This results in shorter sales cycles. • Enhanced Competitive Differentiation • The ability to deliver applications via the SaaS model enhances a software company’s competitive differentiation. It also creates opportunities for new companies to compete effectively with larger vendors. The tangible value that customers can realize from the SaaS model versus the perpetual license model is a compelling selling point. • On the other hand, software companies will face ever-increasing pressure from their competitors to move to the SaaS model. • Those who lag behind will find it difficult to catch up as the software industry continues to rapidly evolve. • Lower Development Costs & Quicker Time-to-Market – • The main saving is at testing (35%). • Small and frequent releases – less to test • Application is developed to be deployed on a specific hardware infrastructure, far less number of possible environment – less to test. • This, in turn, provides the software developer with overall lower development costs and quicker time-to-market. • Effective Low Cost Marketing • Between 1995 and today, buyers’ habits shifted from an outbound world driven by field sales and print advertising to an inbound world driven by Internet search. The SaaS delivery model is perfect for marketing programs that exploit this shift. • Predictable MRR Revenue • Traditionally, software companies rely on one major release every 12-18 months to fuel a revenue stream from the sale of upgrades (long tail theory). This puts a lot of pressure on the organization to hit an arbitrary date to meet corporate financial commitments. • In the SaaS model the revenue is typically in the form of Monthly Recurring Revenue (MRR), which is far more predictable and less tied to the development schedule of the next release of the software. • Improved Customer Relationships • SaaS contributes to improved relationships between vendors and customers. In the traditional model once the software is sold, it is largely up to the customer to make it work. The SaaS model creates a more symbiotic relationship between vendors and customers and provides vendors with greater opportunities to please their customers • Protection • Difficult to obtain illegal copies • Price is low, making getting an illegal copies totally unnecessary

  28. Concerns • Integrate into existing enterprise applications, architectures, and databases. • Supporting complex business processes and cross-enterprise tasks is beyond current products. • Protecting their proprietary data • How is the data protected from unauthorized access? • How is the customer assured access to the data? • How much effort is necessary to migrate data back to the enterprise or to another SaaS provider? • Service outages

  29. SaaS • Get over initial hurdles • Adopting SaaS in the enterprise has to be analyzed for economic and efficiency reasons • A lot of initial planning and negotiating with the solution provider- security, data access, legal, etc • Long term Benefits • Easy Access • Reduced piracy of your software • Lower Cost • Continuous Technology Enhancements

  30. SaaS Steps • Understand your business objectives and definition of a successful outcome (idea) • Select and staff your services delivery team (people) • Define and understand the infrastructure needed to deliver your SaaS application (hardware) • Select your hosting facility and Internet Service Providers (ISPs) • Procure the infrastructure and software required to deliver your SaaS application (your platform) • Ready to Run • Deploy your SaaS delivery infrastructure • Implement disaster recovery and business continuity planning • Integrate a monitoring solution • Establish a Network Operations Center (NOC), Client Call Center and ticketing system • Design and manage Service Level Agreements • Document and manage the solution while open your business

  31. Customer Relationship Management One of the most popular and most publized areas of SaaS is CRM. It includes functions such as account management, opportunity tracking, and marketing campaign administration. A well known example in this category is Salesforce.com

  32. Salesforce.com provides the following modules as services: Sales, Service & Support, Partner Relationship Management, Marketing, Content, Ideas and Analytics. It can be accessed from almost any browers and multiple mobile platforms such as iPhone, Android, Windows Mobile, and Blackberry

  33. Users can customize the application to some degrees - add user-defined customized fields, - add customized tabs for specific vertical or function-level features. Salesforece.com offers a Web Service API for data manipulation (Select, Insert, Update, and Delete).

  34. NetSuite is another popular CRM package It provides the following software modules as services - Pipeline and opportunity management - Order management - Advanced forecasting - Incentive management - Upsell manager - Account management

  35. NetSuite has also launched a global business management system called OneWorld, which offers on-demand international support to mid-market companies, or multi-national organizations. NetSuite also has an online marketplace for third party developers to sell their NetSuite extensions.

  36. Tools to build, integrate and deliver applications for the NetSuite platform: • SuiteFlex • SuiteBuilder • SuiteScript • SuiteTalk • SuiteScripte D-Bug • SuiteBundler

  37. SugarCRM - SugarCRM itself is not an on-demand service. Rather it is an open-source software solution based on a “LAMP” stack. - It is very easy and cheap to build SaaS solution on top of an IaaS by downloading SugarCRM and installing it on a virtual machine.

  38. Human Resources HR administrates processes to support personnel functions such as recruiting, developing, retaining and motivating employees. Workday provides the following functions as services: - Absence, Compensation, Benefits, Staffing, Development, Performance management.

  39. Taleo A well-known SaaS provider in the HR space. It provides the following functions as services - Recuritment, Performance Management, Employee Lifecycle, career management, and succession planning

  40. Financial Workday: Payroll, spend management, financial accounting, customer accounts, supplier accounts, and cash management, procurement. Netsuite: Financial management, financial planning, inventory and supply chain, order management, services resource planning, human capital management, business intelligence and analytics.

  41. Intuit (The company who develops TurboTax, Quicken) provides online service include accounting, payroll and payment solutions.

  42. Collaboration Google provides Gmail, Google Calendar, Google Talk, Google Doc, and Google Sites. Microsoft Online Services: Windows Live (Email, Mesh, Messenger, Movie Maker, Photo Gallery, Writer, SkyDrive), Office Web Apps, Office 365 (Exchange Online, SharePoint Online, Lync Online)

  43. Cisco Webex: combines real-time collaboration with phone conferenceing.

  44. Backup and Recovery Cloud-based backup has an intrinsic benefit over on-site alternatives that the physical stroage is generally very far from the users and their source data. As such, it is resilient to many of the risks of natural disasters and other localized outrages. This type of service can also fall into Storage as a Service, but from the end-user interaction perspective, it is a typical SaaS.

  45. Mozy - backup can be scheduled - it automatically detects the change of the folders and files and backup the most recent version - all files are encrypted. - It can backup buisness applications such as SQL and Exchanges - Data can be restored through the web, as a Mozy virtual drive on Windows, or via ordering a DVD restore.

  46. Zmanda - Is not a service running on cloud. - It can backup data to disk, tape, and Amazon S3. The user can specify hosts, paths, and backup destination at a central console.

  47. Industry Specific SaaS Healthcare Transportation Logistics