Service Delivery Platform
-
Upload
rinky25 -
Category
Technology
-
view
1.341 -
download
6
description
Transcript of Service Delivery Platform
![Page 1: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/1.jpg)
Service Delivery PlatformsBridging the Gap Between ISVs
and Service Providers
![Page 2: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/2.jpg)
SaaS Realities• “Tsunami-like” software industry shift• Most software companies will need to have a SaaS
offering in order to survive and thrive over the coming years
• According to Gartner, “the scale of change involved in moving to a SaaS approach is proving hard for many vendors to manage.”
• Most applications were not designed for SaaS delivery• Service (Hosting) Provider space is getting crowded,
between Leaders, and those claiming to have SaaS experience
![Page 3: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/3.jpg)
ISV Realities• Independent Software Vendors (ISVs) have not
traditionally relied on Service Providers for market success
• Uncharted territory• ISVs must solve 3 key challenges in order to enter and
excel in the SaaS space
Business Architecture
Delivery Architecture
Application Architecture
SaaS challenges
Business Architecture
Application Architecture
DeliveryArchitecture
![Page 4: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/4.jpg)
Service Provider Realities• Must grow and expand outside traditional
business model• Currently attracting ISVs with commoditized
service offerings• Reputation, price
• Doesn’t solve ISV’s application architecture problem
• Lengthy sales cycle
• Delivery promise is somewhat dependent upon ISV’s software
• Emphasis is on addressing delivery architecture
SaaS challenges
Business Architecture
Application Architecture
DeliveryArchitecture
![Page 5: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/5.jpg)
SaaS challenges
Business Architecture
Application Architecture
DeliveryArchitecture
Business “Architecture” Challenges
![Page 6: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/6.jpg)
Business “Architecture” ChallengesISV• Understanding the cost of entry• Calculating costs per subscriber• Finding appropriate pricing models• Creating appropriate marketing
strategies
• Revising Sales compensation
• Introducing SaaS without cannibalizing the need for cash benefits of existing model
• Determining impact on existing Channels, and developing new ones
Service Provider• Getting away from “price wars” to
win business
• Shortening the time between a lead and a relevant volume of ISV subscribers
• Generating “Demand Pull”
• Reducing costs associated with manual labour to support numerous ISVs and their subscribers
![Page 7: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/7.jpg)
SaaS challenges
Business Architecture
Application Architecture
DeliveryArchitecture
Delivery “Architecture” Challenges
![Page 8: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/8.jpg)
Delivery “Architecture” ChallengesISV• Fully reliant on Service
Providers
• Offloads “pains” of hosting technologies, typologies, uptimes, etc.
• Demands 100% SLAs
• Regards hosting as a commodity service
Service Provider• Core competency
• May not have solved SaaS scalability issues
• Difficult to show uniqueness or strategic value
![Page 9: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/9.jpg)
SaaS challenges
Business Architecture
Application Architecture
Application “Architecture” Challenges
DeliveryArchitecture
![Page 10: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/10.jpg)
Application “Architecture” ChallengesISV• Existing architecture
makes SaaS price-prohibitive
• May not have the engineering skill to make required architecture changes
• Critical time passes trying to solve this issue – 3 months, 6 months, 12 months?
Service Provider• Can only pursue ISVs
that have the correct application architecture
• Limited percentage of ISVs are strong candidates for SaaS
• Need to widen their net of prospects
![Page 11: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/11.jpg)
Bridging the Gap
![Page 12: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/12.jpg)
Service Delivery PlatformsWhat is an SDP?• The term Service Delivery Platform (SDP) was
originally used in the telecommunications industry• Today, an SDP represents a vehicle to enable rapid
development and deployment of online services, including software and multimedia content
• An SDP typically provides a service creation environment, and a service execution environment; as well as metering, monitoring, and reporting capabilities
![Page 13: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/13.jpg)
Service Delivery PlatformsProvides positive business impact by:• Taking advantage of existing software
investments• Getting a new or existing application SaaS-
enabled within 30 days• Enabling ISVs to focus on the features and
functionality of their products• Solving the architectural barriers to SaaS
![Page 14: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/14.jpg)
General Purpose
Horizontal Oriented
Platforms Types
Product Oriented
![Page 15: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/15.jpg)
Service Delivery PlatformsAn SDP should provide:
• Configurability
• Scalability/High Availability
• Multi-Tenancy
![Page 16: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/16.jpg)
Configurability
� tenant metadata configuration
� convenient management interface
� customizable usage reporting
� release and update management
![Page 17: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/17.jpg)
tenant-load balancing, so servers are added as required when users increase
automated provis ioning of application instances
S calability/High Availability
graceful, real-time failover if infrastructure becomes unavailable
![Page 18: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/18.jpg)
No need to re-architect the application to produce multi-tenancy means:
Virtual Multi-Tenancy
� Increased speed to market
� Reduced costs
![Page 19: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/19.jpg)
Users get their own application ins tances means:
Virtual Multi-Tenancy
Enhanced reliability —
The activity or failure of one tenant does not affect other tenants
![Page 20: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/20.jpg)
SDP: Bridging the Application Architecture Gap
![Page 21: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/21.jpg)
Application ArchitectureISV
• SaaS offering within 30 days
• Reduce or eliminate expensive development costs
• Leverage existing technologies
Service Provider
• Can truly be a “turn-key” ISV partner, solving both the delivery and application architecture challenges
• Cast a wider net to attract ISVs
![Page 22: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/22.jpg)
SDP: Bridging the Business Gap
![Page 23: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/23.jpg)
Business “Architecture”ISV
• Get to market in less than 30 days
• Leverage existing technologies
• Allow Channel Partners to resell SaaS offering
Service Provider
• Expand existing service offering to include benefits of an SDP
• Substantial competitive advantage
• Shorten sales cycle and time to market
![Page 24: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/24.jpg)
SDP: Bridging the Delivery Gap
![Page 25: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/25.jpg)
Delivery ArchitectureISV
• Subscriber Account Management
• Software Release Management
Service Provider
• Efficiency and Profit gains through: Automation of customer provisioning and product releases
• SLA Monitoring and Enforcement
![Page 26: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/26.jpg)
Which Service Delivery Platform(s) is right for you?
![Page 27: Service Delivery Platform](https://reader034.fdocuments.net/reader034/viewer/2022051411/54794455b37959532b8b4703/html5/thumbnails/27.jpg)
Q&A