Livewire

One direct impact of this would be an incoherent implementation and customization of a package to the requirements. This makes the system complex, un-maintainable and counters the advantages provided by the package implementation. This could also potentially result in a revenue leakage due to various software issues of any complex system. These are coming from either a huge customization (of more than 50%) or in trying to make the existing older versions of package work for those brand-new, future-focused requirements. How would operators solve such issues when the package inplace doesn’t scale up to their new requirements and a forcible application of the same potentially results in a revenue loss?

A better approach for the operators would be to componentize their BSS systems as much as possible. While doing so, the entire functionality of BSS would get scattered to these multiple modules and thereby we can avoid the first risk of having to depend only on one core billing system for everything. The components could include separate systems for Product Master Data, Revenue Reconciliation, Billing, Invoicing etc. Once componentization is done, a good modular architecture should be crafted to integrate these various systems. Thus, new product launches could only impact the relevant components and not the core billing system, most of the times. One more advantage with this approach is that the operator will have the liberty to have a low-end billing system that is not very complex in functionality, easily maintainable and not heavy on license-costs.