Truly Convergent Billing

4,339 views

Published on

Part of a keynote address that I gave to the 10th Annual Asia Billing and Revenue Assurance Conference, held in Bangkok March 2010.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,339
On SlideShare
0
From Embeds
0
Number of Embeds
106
Actions
Shares
0
Downloads
238
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Truly Convergent Billing

  1. 1. Truly Convergent Billing Asia Billing and Revenue Assurance 2010 Doug Newdick 09 March 2010
  2. 2. The Promise of Convergence? <ul><li>The single software package view of convergence </li></ul><ul><ul><li>“I hear you have billing problems – our billing software will solve them.” </li></ul></ul><ul><ul><li>A promise that is unlikely to be fulfilled. </li></ul></ul><ul><li>We need to move to a complete view of converged billing architecture. </li></ul><ul><ul><li>One that encompasses the totality of billing. </li></ul></ul><ul><ul><li>One that is likely to deliver on the promise. </li></ul></ul>
  3. 3. Convergent Architecture <ul><li>A view of what a truly convergent billing architecture might look like </li></ul><ul><ul><li>One that uses Enterprise Architecture best practice. </li></ul></ul><ul><ul><li>One that uses industry standards. </li></ul></ul><ul><ul><li>One that builds on practical experience both at delivering - and failing to deliver - convergent billing. </li></ul></ul><ul><ul><li>The good news: it is achievable! </li></ul></ul><ul><ul><li>The bad news: there is no silver bullet, no magic billing application. </li></ul></ul>
  4. 4. What is Convergence? <ul><li>The customer view: </li></ul><ul><ul><li>The ability to use, access, purchase or experience as one, something that previously had to be used, accessed, purchased or experienced separately. </li></ul></ul><ul><li>The operator’s view: </li></ul><ul><ul><li>Those things that we must do and be in order to provide convergence to the market place. </li></ul></ul><ul><ul><li>If there is no customer impact, there is no meaningful convergence. </li></ul></ul>
  5. 5. Different Kinds of Convergence <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  6. 6. How Did We Get Here? A Hypothetical Billing Landscape <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  7. 7. Converging The Billing Landscape: This Is Not The Answer! <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  8. 8. How Did We Get Here? Convergence Anti-Patterns 1 <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  9. 9. How Did We Get Here? Convergence Anti-Patterns 2 <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  10. 10. Architectural Levels <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  11. 11. Architectural Levels: Cycles of Problems and Solutions <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  12. 12. What’s Architecture Got To Do With Convergence? <ul><li>Each level can be convergent or divergent independently. </li></ul><ul><ul><li>Divergent higher level views can be supported by convergent lower levels. </li></ul></ul><ul><ul><li>Convergent higher level views can be supported by divergent lower level views – though this isn’t easy! </li></ul></ul><ul><li>Truly convergent architecture is when all levels align on a convergent model – supporting a truly convergent customer experience. </li></ul><ul><li>How convergent you become should be determined by business capacity for investment and desire for convergence. </li></ul>
  13. 13. Convergence at Different Levels <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  14. 14. Considering All of Billing <ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul><ul><li>Enter introduction text here use the highest level bullet style here for this effect. </li></ul>
  15. 15. The Extended Enterprise or Telco 2.0 <ul><li>The boundaries of the enterprise are no longer rigid. </li></ul><ul><li>The effects of the enterprise extend outwards beyond the traditional borders of the enterprise. </li></ul><ul><ul><li>Into traditional suppliers and partners </li></ul></ul><ul><ul><li>Out to customers </li></ul></ul><ul><li>Convergence is a key enabler of the extended enterprise. </li></ul>
  16. 16. Billing and LTE <ul><li>LTE produces no new challenges. </li></ul><ul><li>LTE does intensify existing challenges. </li></ul><ul><ul><li>The commodification of data </li></ul></ul><ul><ul><li>Cannabilisation of voice revenue </li></ul></ul><ul><ul><li>Increased importance of VAS </li></ul></ul><ul><ul><li>Potential for “bill shock” </li></ul></ul>
  17. 17. Convergence: LTE and the Extended Enterprise <ul><li>The challenges for billing from LTE and the Extended Enterprise are similar. </li></ul><ul><ul><li>Real time charging and postpaid credit limits can prevent bill shock and reduce financial risk for the service provider and any partners. </li></ul></ul><ul><ul><li>Real time charging of VAS gives partners certainty. </li></ul></ul><ul><ul><li>Converged charging makes management of charging for partners simpler. </li></ul></ul>
  18. 18. Telecom NZ: A Case Study In Convergence <ul><li>Telecom NZ is undergoing a significant programme of business transformation. </li></ul><ul><li>We’ve recently launched a new 3G WCDMA mobile network. </li></ul><ul><li>Billing has been a key aspect of these initiatives. </li></ul><ul><li>The billing architecture team has identified convergent billing architecture as central to allowing us to deliver the required business capabilities. </li></ul>
  19. 19. Telecom NZ: Where We Are <ul><li>Key features of rating convergence: </li></ul><ul><ul><li>Prepaid and postpaid mobile rated on the one platform in real time: Voice, SMS, Data, VAS. </li></ul></ul><ul><ul><li>Fixed line broadband rated on the same platform. </li></ul></ul><ul><ul><li>Other products and services rated on other platforms. </li></ul></ul><ul><li>One bill for all products and services. </li></ul><ul><li>Bill calculation split between two platforms. </li></ul><ul><li>Postpaid A/R in the one platform. </li></ul><ul><li>Convergent offerings without necessarily convergent technologies. </li></ul><ul><li>Logically separate billing for each business unit. </li></ul>
  20. 20. Telecom NZ: Areas of Architectural Development <ul><li>Build on convergent rating by adding additional services. </li></ul><ul><li>Focus on convergent A/R and balance management to support one view of the customer. </li></ul><ul><li>Build capability once and re-use across product lines, customer segments and business units. </li></ul><ul><li>Converge as much as possible within the system and technology levels, leaving non-convergence at the business level. </li></ul>
  21. 21. Thank You <ul><li>Body copy here </li></ul><ul><ul><li>Choose half page column design from the design taskpane </li></ul></ul>

×