Truly Convergent Billing

Truly Convergent Billing

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