Service Delivery Platform


Published on

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

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Service Delivery Platform

  1. 1. Service Delivery Platforms Bridging the Gap Between ISVs and Service Providers
  2. 2. 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
  3. 3. 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 Application Architecture Business Architecture Delivery Architecture SaaS challenges Application Architecture Business Delivery Architecture Architecture
  4. 4. 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 Application Architecture • Delivery promise is somewhat dependent upon ISV’s software SaaS challenges • Emphasis is on addressing delivery architecture Business Architecture Delivery Architecture
  5. 5. Business “Architecture” Challenges Application Architecture SaaS challenges Business Delivery Architecture Architecture
  6. 6. Business “Architecture” Challenges ISV Service Provider • Understanding the cost of entry • Getting away from “price wars” to • Calculating costs per subscriber win business • Finding appropriate pricing models • Shortening the time between a • Creating appropriate marketing lead and a relevant volume of ISV strategies subscribers • Revising Sales compensation • Generating “Demand Pull” • Introducing SaaS without • Reducing costs associated with cannibalizing the need for cash manual labour to support benefits of existing model numerous ISVs and their subscribers • Determining impact on existing Channels, and developing new ones
  7. 7. Delivery “Architecture” Challenges Application Architecture SaaS challenges Business Delivery Architecture Architecture
  8. 8. Delivery “Architecture” Challenges ISV Service Provider • Fully reliant on Service • Core competency Providers • May not have solved • Offloads “pains” of SaaS scalability issues hosting technologies, • Difficult to show typologies, uptimes, etc. uniqueness or strategic • Demands 100% SLAs value • Regards hosting as a commodity service
  9. 9. Application “Architecture” Challenges Application Architecture SaaS challenges Business Delivery Architecture Architecture
  10. 10. Application “Architecture” Challenges ISV Service Provider • Existing architecture • Can only pursue ISVs makes SaaS price- that have the correct prohibitive application architecture • May not have the • Limited percentage of engineering skill to make ISVs are strong required architecture changes candidates for SaaS • Critical time passes trying • Need to widen their net of to solve this issue – 3 prospects months, 6 months, 12 months?
  11. 11. Bridging the Gap
  12. 12. Service Delivery Platforms What 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
  13. 13. Service Delivery Platforms Provides 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
  14. 14. Platforms Types General Purpose Horizontal Oriented Product Oriented
  15. 15. Service Delivery Platforms An SDP should provide: • Configurability • Scalability/High Availability • Multi-Tenancy
  16. 16. C onfig urability • convenient manag ement interface • tenant metadata config uration • cus tomizable us ag e reporting • releas e and update manag ement
  17. 17. S calability/ Hig h Availability automated provis ioning of application ins tances tenant-load balancing , s o s ervers are added as required when us ers increas e g raceful, real-time failover if infras tructure becomes unavailable
  18. 18. Virtual Multi-Tenancy • Increas ed s peed to market • R educed cos ts No need to re-architect the application to produce multi-tenancy means :
  19. 19. Virtual Multi-Tenancy Enhanced reliability — Us ers g et their own The activity or failure of one tenant application ins tances does not affect other tenants means :
  20. 20. SDP: Bridging the Application Architecture Gap
  21. 21. Application Architecture ISV Service Provider • SaaS offering within • Can truly be a “turn-key” 30 days ISV partner, solving both the delivery and • Reduce or eliminate application architecture expensive challenges development costs • Cast a wider net to • Leverage existing attract ISVs technologies
  22. 22. SDP: Bridging the Business Gap
  23. 23. Business “Architecture” ISV Service Provider • Get to market in less • Expand existing service than 30 days offering to include benefits of an SDP • Leverage existing technologies • Substantial competitive advantage • Allow Channel Partners to resell • Shorten sales cycle and SaaS offering time to market
  24. 24. SDP: Bridging the Delivery Gap
  25. 25. Delivery Architecture ISV Service Provider • Subscriber Account • Efficiency and Profit Management gains through: Automation of • Software Release customer provisioning Management and product releases • SLA Monitoring and Enforcement
  26. 26. Which Service Delivery Platform(s) is right for you?
  27. 27. Q&A