Innovative distribution + enabling services…

Share |

With the June 24 TM Forum webinar and Team Action Week sessions (interest groups, SDF next phase), we’ve announced a direction and priority scope for the TM Forum’s Enabling New Services Initiative.  Work remains to be done in tuning it and our execution plans, but it feels great to me to now be started.  The initiative includes a dual focus: product trading between businesses (e.g., part of B2B space), and management of new enabling services.

On July 13, industry visionary Alan Quayle blogged about some of the same themes that lead the TM Forum Enabling New Services Initiative's focus.  I was delighted to read Alan’s insights and strongly agree with his views in this post.  Such resonating agreement includes most views found in other posts he links back to (e.g., developer needs).  I especially support the point that Service Providers cannot effectively monetize enabling services by nickel and diming businesses and developers using the atomic enabling services ("dips"/usage).  That's true now especially in a market phase of investing in market share/goodwill, developer relationships, and fostering third party innovation.

Digital product distribution solutions are also essential for getting apps and third-party services wired to--and hosted by--Service Provider’s enabling services in the cloud.  Amazon and eBay-like distribution business models (like portals & app stores) are an important two-sided value-add for providers to win share of monetized business.  IT customer buying decisions, from sole proprietor developers to the largest business corporations like banks, will be made during both build-time and run-time (across the lifecycle) of apps, content, and top-level services that rely on SP enabling services from hopefully interoperable platforms in the cloud.

I encourage everyone to read Alan’s blog post and most links in it.  Alan has said very important things much better than I can again. 

However, in adding to Alan’s closing example in his blog, many TM Forum member companies supply solid commercial parts of the enabling platform solution space.  However, CSP executive leaders and all of us in the industry have collaborative and procurement work to do on realizing qualities of web-facing interoperability, simplicity, and unity.  Reducing fragmentation facing third party developers on the web is absolutely critical for CSPs and their supply ecosystem to grow new industry share.  I applaud the efforts of the Wholesale Apps Community (WAC) in this area.  We must go further in the distribution and enabling services areas to address fragmentation for upstream businesses and tech developers. If we do not, new types of Service Providers doing distribution may get most of the new enabling services business share.  These new SPs have advantages by having over 500,000,000 downstream users (including valuable user information) today on their proprietary platform.

 


Posted 07-30-2010 9:59 AM by Stephen Fleece

Comments

Jenny Huang wrote re: Innovative distribution + enabling services…
on 08-02-2010 10:29 AM

Stephen,

Thanks for the fine posting again and your efforts to bring SDF in context for the Enabling New Services initiative.

After reading Alan Quayle's blog post and his white paper on API Management,  I'm wondering what is your view  on  his interpretation of API management capabilities and SDF SMI.  While I don't think they are entirely equal, but  I found this can be another way of explaining the core essence of what SDF is to enable, might also help to reduce the confusion on what is in-scope and out-of-scope for the SDF and its main objective/target audiences.   Although "API management" has a connotation in the software industry that it is purely software management,   perhaps we can call it "business aware" API mgmt.

Jenny

Stephen Fleece wrote re: Innovative distribution + enabling services…
on 08-02-2010 10:37 AM

Jenny, I think the potential of the SDF SMI is one part of a larger API management business landscape.  I agree Alan's views on the business landscape and the architectural concept of SDF SMI are not entirely equal.  

I think there's a big market strategy and "go to market" issue for CSPs to succeed in capturing business from third party developers (and the businesses that employ them) that Alan's views help emphasize.

Tal Givoly wrote re: Innovative distribution + enabling services…
on 08-02-2010 4:57 PM

Read both this post and Alan's.

I believe the critical aspects are indeed those that are being addressed by WAC right now. Will it be successful? Time will tell. Until then service providers will try different approaches (including the one cited by Alan as impressing him).

In either case, I believe the external interfaces are far more important than the internal structures to manage and run them. Each service provider's service delivery framework will differ quite dramatically, and that, perhaps, is by design. Standardization is useful when they are critical for adoption of a technology. When they are not critical, they are not only not helpful, they are unlikely to take footing. Examples of this are endless.

That's one of the reason internal interface standards, wholly within a service provider boundary, are of the lowest priority to service introduction. Unfortunately, much of the work TMF has been engaging in so far has been focused on this area - which is the least critical for service providers despite the difficulties it imposes upon them over time.

Once a technology is rolled out, fixing the management interfaces of it seems hardly the right thing to focus on.

A great example is IPTV - standardization way after the fact. On the other hand, IP, HTML, USB, BD, and WiFi are examples where standardization are critical for market creation.

Where do our current activities fall? Put this test to any standardization we work on to consider how effective it might become.

Tal

Stephen Fleece wrote re: Innovative distribution + enabling services…
on 08-02-2010 5:07 PM

Tal, thanks for the comments.  The external enablingment aspect is one reason the SDF project is prioritizing an initial "alpha" specification of the SDF SMI since this will be an external interface facing third-party developers of service apps (e.g., service enablers, SaaS/PaaS apps, etc.).  

Stephen

We welcome your feedback! To comment on this blog post please either Log-In or Register to the TM Forum Community

Paid Advertisement
About TM Forum
Introduction, History, Board, Management Team...
Membership
How to Join, Benefits, Member List...
Community
Community Home, Groups & Teams, Blogs...
Conferences
Event Calendar, Management World, Supported Events...
Training & Webcasts
Upcoming Training Courses, Upcoming Webinars, Podcasts, On-Demand Webcasts...
Initiatives
Cable, Enabling Cloud Services, Government and Defense...
Best Practices & Standards
Frameworx, Business Process Framework (eTOM), Information Framework (SID)...
Resources
Document Library, Case Studies, White Papers
Research & Publications
Business Benchmarking, Newsletters, Insights Research...
Copyright © 1988-2012, TeleManagement Forum. All Rights Reserved
Contact Us
Careers with TM Forum
News Room
Privacy Policy
Terms of Use
Sitemap