- Centralized Product Catalog for offer creation, pricing, discounts, service specification and resource specifications
- Single teams, managing OSS and BSS applications
- Ease in Version Management
- Centralized view of product offer, service specifications, pricing attributes and resource alignment through web based GUI from where plans can be easily added and modified.
- Centralized configuration driven architecture, automated push of product data to CRM & downstream applications to reduce manual work and costly development
- Reusable and Generic Product Model support current and future services
- Faster Time to Market for new offers, products and services
- Reduced total cost of product development and maintenance
- Improved data quality & data integrity between all applications by removing old & redundant data
- It helps multiple product owners to seamlessly collaborate and manage product with one view functionality.
- It helps operators to create new market differentiations and further fine-tunes market segmentations.
Operators can rationalize and prepare for a agile product management.
Posted By :
In today’s real-time data driven operator scenario, every telecom service must create next generation products and services in shorter time to push ability of differentiating products and services, and gain headstart advanatge against competitors while maximizing their revenue streams. Business processes are feeling the heat to optimize and rationalize different layers within the BSS system. Maintaining multiple product catalogues and related customer plans data is one such drain on resources. There are many operators still using their legacy systems to create next generation plans which turns out to be a nightmare for the product managers particulalry. So the question is, are all operators equipped with next gen centralized product catalogue? The answer is NO. Here are the few reasons why creating a next generation plan with old age legacy system is a pain for the operator: Multiple systems, increased complexities In a typical legacy BSS ecosystem, one has to deal with multiple product catalogs, as products are defined and maintained in multiple systems from different vendors, which increase service complexity. Multiple products, multiple departments Product offers and definition constitutes many elements like target group, price, distribution channel and time validity. And as an operator has multiple products created, managed and offered by different departments, managing the entire product portfolio may become very complex and difficult to manage. Delay in launch of new services A Separate product model is created in legacy systems to configure different types of services. When a new product or offer is designed the product specialist has to repeat and configure the same work multiple times in different applications for different departments. Complex Product mapping across application results in delay in launch of new services. Multiple systems, multiple databases Multiple legacy system results in managing product data in their respective databases, which becomes quite complex. Only through a centralized product catalog the operator will be able manage products centrally that speak the same language. Today’s BSS/OSS vendors have become smarter and realized the full potential that a centralized product catalog has to offer: