SDP Global Summit Highlights

7,122 views

Published on

A few of the interesting slides presented at the SDP Global Summit 2011.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
7,122
On SlideShare
0
From Embeds
0
Number of Embeds
5,210
Actions
Shares
0
Downloads
79
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SDP Global Summit Highlights

  1. 1. SDP Global Summit HighlightsSDP Global Summit20th-22nd September 2011www.alanquayle.com/blog © 2011 Alan Quayle Business and Service Development
  2. 2. Structure • Jose Valles, BlueVia o Best of the current API recipe • Michel Burger, Vodafone o Web Services oriented model for SDP, important step beyond SOA, prescient architecture • Medhat Amer, CIO Mobily o Sound advice on making an SDP project a success • Abdeljalil Boularab, STC o Impact of SDP is across all services and they are generating 100M Euro per year in new revenue and savings • Shira Levine, Infonetics o SDP is all about the services • Andreas Boose, Telefonica o Leading multi-national multi-layer SDP
  3. 3. Jose Valles, BlueVia• Some of the key points from Joses presentation: o Operators are not attractive to developers because of the sins of the past (e.g. Orange Partner), arrogance and self-interest in their out-reach, and being out of touch with internet technologies and business models. o SDP is a swear box, its sold as a panacea, when it is not. o The money is not in the long tail, its in the mid tail, telcos should focus there. o It takes time, even for the web-centric companies like Netflix to build momentum around their APIs. o Telco APIs are not cool, do not call them cool, its all about the business enabled through them, focus there. Its critical telcos know themselves and act accordingly. A forty-year-old acting like a twenty-year-old is just plain embarrassing. o Partnerships are key, telcos can not do this alone. o Copy APIs that are working, do not follow standards.• See http://www.alanquayle.com/blog/2011/09/sdp-global-summit-2011-light-a.html for more details BlueVias APIs have reached a point of simplicity and ease of use that an organization the size of Twitter (by messaging volume) preferred to use them, and critically this is an interface any developer can access. This is clear endorsement by the web-centric world that BlueVia has got it right - a seminal moment for Telco APIs and our industry.
  4. 4. Michel Burger, VodafoneGood diagram showing the breadth of API use across the ecosystem. The only gap is code- samples matter as much as the SDK, most operators keep missing the point, the best developers are cut and paste developers.
  5. 5. Michel Burger, VodafoneCore Services Layer architecture adopting a web services model than the classic SOA model. Similar to the model adopted by Amazon and Google for their BSS.
  6. 6. Michel Burger, VodafoneMichel refers to it as the Internet Service Ecosystem, I use the term Services Layer. This is prescient architecture, showing where operator IT systems will need to evolve.
  7. 7. Medhat Amer, CIO MobilyMadhat’s advice, through obvious is rarely followed in most SDP projects. CEO sponsorship is essential, else the project will fail. Talk with other operators, not suppliers, on their experiences. Have clear business objectives and metrics for each phase of the project.
  8. 8. Abdeljalil Boularab, STCImpact of SDP is across all services and they are generating 100M Euro per year in new revenue and savings
  9. 9. Shira Levine, InfoneticsSDP revenues are dominated by services: system integration, managed services and cloud services.
  10. 10. Andreas Boose, TelefonicaTelefonica is a great example of a multi-layer, multi-national SDP using off-the-shelf IT technology and architectures (SOA).
  11. 11. Andreas Boose, TelefonicaTelefonica is a great example of a multi-layer, multi-national SDP using off-the-shelf IT technology and architectures (SOA).
  12. 12. Andreas Boose, TelefonicaApproach of ESB integration rather than more abstract API definitions is required in SOA. Likely see this SOA versus web-services approach become a hot topic through 2012.

×