Purple Globe
A new name and a (slightly) new direction. Telco talk will add Business Process Management within the Telco OSS/BSS arena to the potential subjects we'll cover here. The old Industry Business Partner Technical Strategy Enablement (IBPTSE) team's role remains an important part of IBM's Telecom strategy, so I will probably still cover partner capabilities and content here. I know the blog is pretty much about telco, but I reserve the right to comment on other industries as well :-) I plan to talk about resources that are available to IBM Business Partners, some of the latest issues we are seeing in Telecom, some discussion of IBM software technology and some thoughts on IBM's Smarter Planet initiatives.

  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 Alan Flower commented Permalink

Andrew, <div>&nbsp;</div> Good points. I would add that the problem with the Telco standards that you mention is one of consumption - very few developers want to use them. Whilst it can be argued that many of them are over engineered the overriding reason for lack of adoption is simply that there is no compelling commercial reason to do so. The APIs you mention offer limited capability, they can be ridiculously expensive to consume and don't offer the network coverage required - no one wants to customise their code for each and every operator and the commercial hoops you often need to jump through to get access to APIs are too painful to make it worthwhile. We tried to fix some of these issues at WAC - but developers were not interested, the lack of interest in telco APIs from ISVs etc. is staggeringly low. <div>&nbsp;</div> Whether these interfaces are based on standards or not makes no difference when there is no compelling reason to implement them. The networking standards were absolutely necessary for interoperability - yet the failures are the opposite - they were easily circumvented and lack sufficient commercial rationale for many telcos to make them mandatory. <div>&nbsp;</div> Alan (ex. IBM, ex. WAC)

2 Andrew_Larmour commented Permalink

Thanks for your comment Alan - long time no speak. <br /> . <br /> I think the WAC has some additional issues, with an application model that only supported HTML5 apps and not also supporting native apps - HTML5 just hasn't taken off as a mobile app platform like everyone was predicting two years ago. Developers who had pre-existing apps just didn't see the business justification to port their apps to HTML5 from native iOS/Android/Symbian/Blackberry apps - that would have been a really significant effort and cost for them.

3 CharlesRivet commented Permalink

Hi Andrew, <div>&nbsp;</div> Thanks for the comprehensive posting. <div>&nbsp;</div> One of the reason why the "new" apis have problems may also reside in the continued availability of the existing one - to mirror your HTML5 comment (although HTML5 also has other issues...). There is also the question as to who are the users of these original apis? If we are talking corporations, there is also some entropy there in that they would not want to re-write their comm apps and risk impacting their business. In this day and age, the risk associated with any type of communication problem can be rather large. <div>&nbsp;</div> On the plus side, I have seen some movement on the OneAPI side of things, especially with REST services, even though the actual support may not be explicitly stated and still be present (e.g., the OneAPI developer gateway in Canada, BlueVia). I think there is hope ahead, even if GSMA only lists 29 supporters at this point. <div>&nbsp;</div> And by the way, IBM Rational does currently provide developers with tooling for ParlayX and OneAPI and yes, we plan on continuing to support these standards.

Add a Comment Add a Comment