10/24/2006

What does Convergent Billing Mean?

“First things First” . What does Convergent Billing Mean?.
Convergent Billing is an old topic, but we are going to explain for all the people that are newbie to the billing systems.

To cover this topic we are going to refer to the article “The Who, What, and Why of Convergent Billing” By Lisa Phifer

This article was wrote a long time ago, but it´s enough to understand the meaning. Reading this article we also can take an idea that the meaning of the name of the product Singl.eView

The Who, What, and Why of Convergent Billing
By Lisa PhiferCore Competence, Inc.
Carriers know that billing is where the rubber meets the road. Service turn-up and delivery mean nothing if customer payment cannot take place. Billing sounds so simple: send an invoice, collect payment. In reality, considerable network infrastructure and systems integration is required to deploy an effective billing operations support system.
Take a quick look at billing systems today, and one word keeps popping up: convergence. What is convergent billing? Why do competitive local exchange carriers (CLECs) need it? And who can CLECs turn to for convergent billing solutions?
What Is Convergent Billing and Why Should CLECs Care?
At its core, convergent billing is the integration of all service charges onto a single customer invoice. Convergent billing means creating a unified view of the customer ― and all services provided to that customer ― for single-point customer care.
CLECs understand the value proposition behind convergent services: becoming a one-stop shop for multiple services, delivering voice, data, video, and Internet access over wireline, wireless, DSL, cable, and dial-up. But why convergent billing?
Studies like one by Price Waterhouse conducted in 1997 indicate that customers want to purchase many communications services from single provider. And, when doing so, customers want all services invoiced on a single consolidated bill. Receiving a single bill simplifies processing and payment for the customer. And a unified bill enables cross-service discounts, so that customers who order multiple services can receive preferential pricing.
Even those customers who are ambivalent about a unified bill most certainly appreciate single-point customer care -- difficult, if not impossible, without convergent billing. Customers want to call a single number to resolve billing problems. They don't want to call different numbers for local and long distance service, much less for data or video services purchased from the same provider. They expect customer service representatives to have access to their entire account record, not just that portion of their account associated with a single service.
Who among us hasn't experienced the frustration of being shunted from one department to another and back again when trying to resolve a problem, ask a question, or add, modify, or delete a telecommunications service? Multi-service providers who successfully create a unified view of each customer gain a competitive edge that helps them hold onto existing customers and attract new ones.
What's Good For The Goose Is Good For The Gander
Multi-service CLECs also stand to benefit internally from convergent billing through improved operational efficiency, flexibility, and economy of scale.
Convergent billing enables multi-service packaging and pricing, whereby existing customers are enticed to add new services and new customers are attracted by innovative service bundles. In a highly competitive market, providers must seek new service differentiators to stand out from the crowd. Convergent billing helps a CLEC leverage its position as a next generation service provider by allowing distinctly different services to be priced and invoiced together, with new combinations created quickly to reflect market changes. Unified customer account records allow a CLEC to easily view the big picture, spotting cross-service relationships and buying patterns that spell out new opportunities.
Traditional billing systems are tied to individual technologies. Call detail records (CDRs) are generated by wireline voice switches. IP flow records are generated by Cisco routers. PVC traffic history is gathered from ATM and Frame Relay devices. RADIUS accounting records monitor switched dial-up or ISDN Internet access.
Traditional "stovepipe" billing systems gather one type of data, aggregate it, apply rates appropriate for the type of service, and generate single-service invoices that may include both one-time fees and recurring flat-rate, usage sensitive, distance-based, time-sensitive, and class-of-service charges. Billing systems are also responsible for applying promotions, discounts, tax calculations, credits and adjustments, handling collections, account suspension/reactivation due to non-payment, and reporting. And billing systems are closely tied to customer care systems that enable customer acquisition, service order entry, and contact management.
Investing in a new "stovepipe" billing system for each type of service is an expensive and obviously suboptimal proposition. But note how many "back office" billing system responsibilities are common across service types. The extent to which a CLEC can reuse the same billing system components reduces systems cost, leverages prior investment, and simplifies end-to-end processing. Common systems increase operational efficiency and produce unified customer views -- for example, by creating a common multi-services repository of billing data that can be leveraged by single-point customer care systems. And once a convergent billing system is in place, it may help the CLEC deploy new services more rapidly.

At the lowest level, convergent billing involves gathering data in various formats, originating from diverse systems, and mediating it into a common format. One industry effort that may facilitate this is the standard IP detail record (IPDR) format being defined by
IPDR.org.
The IPDR is intended to be an extensible format that captures meaningful usage information and cost components for any IP-based service. A common IPDR would reduce the need for mediation ― at least within the IP world ― by pushing consistent representation down to the device level. A common format for raw data is a step in the right direction, but it is only one piece of a complex puzzle.
It may seem natural for a single-service CLEC to start with a single-service billing system. As the CLEC branches out into new services, it may be forced to adopt new "stovepipe" billing systems. By the time the CLEC becomes interested in convergent billing, there's already a legacy to contend with. And that legacy may influence who the CLEC looks to for convergent billing solutions.
Lisa is vice president of Core Competence, a network consulting firm located in Chester Springs, PA. She has been involved in OSS design and development for local and inter-exchange carriers for nearly a decade "


Labels:

10/17/2006

News - IBM Benchmarks Intec Convergent Billing

Intec Telecom Systems and IBM have completed a performance benchmark of Intec Convergent Billing v6, the latest version of the market-leading customer care and billing system, on IBM System p5 servers, demonstrating the capability to handle a sustained throughput equivalent to the needs of a customer base of 60 million pre-paid subscribers. The benchmark was based on a current customer implementation and reflected realistic operating conditions and data.

You can read the new at http://www.ossnewsreview.com/telecom-oss/ibm-benchmarks-intec-convergent-billing/

Labels:

10/11/2006

The main purpose of this blog

The main purpose of this blog is to serve as a point of connection for the users, developers, architects or any kind of people around Singl.eView. The idea is try to create a virtual web community to exchange problems, ideas, solutions or news about Singl.eView. The number of implementations of a particular billing product for a Telco operator in the world is not greater than...? I have heard that the implementations of Singl.eView in the world is about 70 (can anyone from Intec verify this?). I think that we are going to be few people in this virtual community, but I hope that between all of us this will be a great point to exchange information. This web is mainly for the people of the Telco operator or consultants that in a day basis are doing maintenance tasks or configuring new functionalities or why not, doing new implementations. The help, advices and information that the experts of Intec could add to this blogs will be also very welcome... We invite to all the people interested in this to post any comment...

Labels:

10/10/2006

What is Singl.eView?

Singl.eView is one of the most famous Convergent Billing Systems. In other words is a billing System for telco operators. This software is provided for Intec. From the Intec website "Intec develops, implements and supports Business and Operations Support Systems (BSS/OSS) for the majority of the world’s largest communications providers, including leaders in fixed, mobile and next-generation networks (i.e. WLAN, 3G and IP)". Although I think that if you have achieved this web...you know exactly what Singl.eView is. But perhaps you, like me,would like to know more about some topics around Singl.eView.
For example, the first in this text...What does Convergent Billing mean?
We try to solve in the next comments...

Labels: