saas technical-business overview

35
SOFTWARE AS A SERVICE

Upload: pritam-parija

Post on 01-Jul-2015

2.719 views

Category:

Technology


0 download

DESCRIPTION

SaaS Business and Technology Overview

TRANSCRIPT

Page 1: SaaS Technical-Business Overview

SOFTWARE AS A SERVICE

Page 2: SaaS Technical-Business Overview
Page 3: SaaS Technical-Business Overview

Enter Google

Page 4: SaaS Technical-Business Overview

ZOHO Docs

Page 5: SaaS Technical-Business Overview
Page 6: SaaS Technical-Business Overview

So What ??

Page 7: SaaS Technical-Business Overview
Page 8: SaaS Technical-Business Overview

Why SaaS: Why did we change? What was lacking ?

Failure of large percentage of IT implementation in 1990‟s

• KPMG Canada Survey; 1997 - 1450 organization;61% failed

• Chaos Report ; 1995; Standish Group – 31.1% project canceled before completion; 52.7% -> cost overrun by 189%

Emergence of SME: Main bottleneck was huge initial Investment

IT solution – Not a competitive advantage anymore

IT implementation – Demand for faster Deployment .

Training and maintenance of IT staff – Huge Liability.

Page 9: SaaS Technical-Business Overview

“Computer based applications and services deployed as a hosted

service and accessed over the Internet rather than a packaged product to

be purchased and installed by the end user."

What is Software as a Service?

Page 10: SaaS Technical-Business Overview
Page 11: SaaS Technical-Business Overview

Categories of SaaS Applications

• Offered to enterprises & organizations

• Large & Customizable Solutions

• Facilitates business processes e.g. finances, supply-chain-management, customer relation etc.

• Sold to customers on a subscription basis

Line-of-Business Services

• Offered to general public

• Mostly provided to customers at no cost

• Funding by advertizing

Customer-oriented Services

Page 12: SaaS Technical-Business Overview

SaaS Maturity Model

Page 13: SaaS Technical-Business Overview

Choosing a Maturity Level

A continuum between isolated data and code and shared

data and code

Page 14: SaaS Technical-Business Overview

High-Level Architecture

Page 15: SaaS Technical-Business Overview

Metadata Services

Provides customers with the primary means of customizing and configuring

the application to meet their needs. Typically, customers can make

configuration changes in four broad areas:

User interface

and branding

Workflow and

business rules

Extensions to the data

model

Access control

Page 16: SaaS Technical-Business Overview

From an application architect's point of view, there are three key

differentiators that separate a well-designed SaaS application

from a poorly designed one.

Scalability ConfigurabilityMulti-tenant-efficiency

Changing the Business Model

Page 17: SaaS Technical-Business Overview

Changing the Business Model

- Shifting the "ownership" of the software from the customer to an external provider

- Reallocating responsibility for the technology infrastructure and management

- Reducing the cost of providing software services by specialization and economy of scale

- Targeting the "long tail" of smaller businesses

Page 18: SaaS Technical-Business Overview

Advantages of SaaS approach

Low cost of entry, Cost effective and infinite scalability

Zero Infrastructure - Reduced Overheads

Single Instance, Multi-Tenant Efficiency

Increased Accessibility and Productivity

Higher quality offerings at lower costs

Page 19: SaaS Technical-Business Overview

…Contd.

Easy to implement

Improved Security

Defined Predictable Spends

Platform Independence

Focus internal IT initiatives only on direct, line of business technology

Page 20: SaaS Technical-Business Overview

ROI of SaaS

Page 21: SaaS Technical-Business Overview

Disadvantages/ Challenges of SaaS

Disadvantages

Customers relinquish control over software versions or changing requirements.

„Vendor lock-in‟ : Current industry lacks portability and interoperability between vendors.

SaaS is not suitable for innovative or highly specialized niche systems.

Dependency on external potential weak links, such as a connection to a database at a remote

site not under your control.

Challenges

Limited Information on SaaS Offerings

Hesitancy to Trust Vendor Recommendations

Fear of the Unknown

Lack of Technical Understanding

Control Issues

Architectural Limitations for Implementation.

Page 22: SaaS Technical-Business Overview

SaaS Market Trends

Global SaaS market expected to grow to $19.3 billion by 2011.

In APAC, estimated CAGR annual growth rate of 59% during 2007-2011, reaching an estimated $1.8 billion by 2011.

Key verticals of SaaS adoption are Manufacturing and Financial services in ASEAN , China and India.

SaaS appealing to SMBs, with 5.1 percent of PC-owning small firms and 15.2 percent of PC-owning medium sized companies planning to adopt a SaaS solution.

CRM continues to dominate Asia's SaaS application market with a 42% market share, followed by on-demand collaboration tools and core enterprise applications like ERP and Supply Chain Management (SCM).

Other SaaS applications are On-demand email, desktop applications, security/compliance, HR payroll, accounting tools, and e-procurement platforms.

Page 23: SaaS Technical-Business Overview

SaaS Market Trends

Page 24: SaaS Technical-Business Overview

Salesforce.com

From Salesforce.com Site

“The Salesforce Foundation was created through

unique 1/1/1 integrated philanthropy model: 1%

time, 1% product, and 1% equity. This Global vision

is the power of us.”

4,000 non-profit organisations currently participating in

the Salesforce CRM product .

Sales Force Automation

Marketing Automation

Customer Service & Support

Partner Relationship Management

Page 25: SaaS Technical-Business Overview

Salesforce.com Offerings

Security Trust & Transparency

True Multi

tenancyProven Scale

High Performance

Complete Disaster Recovery

Based on SaaS Approach

Page 26: SaaS Technical-Business Overview

Salesforce.com Statistics

Page 27: SaaS Technical-Business Overview

SaaS – In The Future…..

Page 28: SaaS Technical-Business Overview

SaaS – In The Future…..

Page 29: SaaS Technical-Business Overview

SaaS – In The Future…..

Page 30: SaaS Technical-Business Overview
Page 31: SaaS Technical-Business Overview
Page 32: SaaS Technical-Business Overview

Level I : Ad Hoc/Custom

Traditional client-server applications can be moved to this level

Relatively little development effort

Rearchitecturing of entire system not required

Levels of benefits limited

Reduce cost by consolidating hardware & Administration

Page 33: SaaS Technical-Business Overview

Level II : Configurable

Repositioning

Traditional application as SaaS at the second

maturity level can require significantly more

re-architecting than at the first level, if the

application has been designed for individual

customization rather than configuration

metadata.

Page 34: SaaS Technical-Business Overview

Level III : Configurable, Multi-Tenant

Provides much more efficient use of computing resources than the second level,

resulting to lower costs.

A significant disadvantage of this approach is that the scalability of the application is limited.

Unless partitioning is used to manage database performance, the application can be scaled only by moving it to a more powerful server (scaling up), until diminishing returns make it impossible to add more power cost-effectively.

Page 35: SaaS Technical-Business Overview

Level IV : Scalable, Configurable,

Multi-Tenant-Efficient

At the fourth and final level of maturity, the vendor hosts multiple customers on a load-balanced farm of identical instances, with each customer's data kept separate, and with configurable metadata providing a unique user experience and feature set for each customer.

A SaaS system is scalable to an arbitrarily large number of customers, because the number of servers and instances on the back end can be increased or decreased as to match demand.