Getting the right tools for the job

We find it interesting that service providers typically have multiple tools performing the same functions (such as provisioning, configuration, assurance and billing) but differentiated by technology. Many OSS vendors push for standardisation of models and interfaces to address this issue but this is to solve their problem not yours. Have you ever implemented one of these systems only to have that remaining critical 10% of functionality not supported by your OSS vendor's solution?

As you move down the hierarchy from Customer to Network Element the support systems required become increasingly specialised. Often this leads to organisations implementing generic Sales, Ordering, CRM and Billing systems, while running separate Network Management (NMS) and Network Element Management Systems (NEMS).

Customer to Element

Don't assume this has to be the case. See if you can run a single NMS and NEMS - this might require choosing a single technology vendor (but you might find this to be worthwhile). Similarly, consider running separate billing rating systems for different service types. This may be more effective than trying to "shoe horn" all rating capabilities into a generic rating system.

The point we want to make is that sometimes you need to dismiss conventional wisdom and just choose the best tool for the job.

Comments

Post a Comment

Popular posts from this blog

Quality Metrics for OSS Projects

Last week a colleague asked about software quality metrics for Operational Support System (OSS) projects. A large telecommunications provider was complaining that the system that they had delivered contained too many bugs. The question that she needed answered was "How many bugs is too many?" . In answer to this question she wanted some benchmarks for industry best practice in terms of bugs per lines of code (LOC). Before examining this question, we thought we should look at some of the characteristics of OSS projects, including: Typically they are large in terms of code base and time to deliver; They are complex ; They are highly customised ; They are expensive and; They deliver strategic benefits to the service provider. In situations such as these we start by looking at the customer's real concerns - there is usually an underlying problem that elicits the response "Your system contains too many bugs" . Here is a quick checklist:
Read more

The Service Catalog

Image
Following on from our previous post on Service Modelling , we thought we would discuss the service catalog. Wait, is that a service catalog or a product catalog? If you remember, a product is something we sell to a customer. Most businesses would be familiar with a product catalog. At a restaurant the product catalog is called a menu. For some reason, telecommunications service providers struggle with the concept of the product catalog and this is usually because they confuse the definitions of products and services. The product catalog should contain all the items you advertise and sell to your customers. There are usually many more products than service types, as each product has a unique set of pricing information. If you sign customers up for fixed term contracts for example, each contract length defines a different product, even though the type of service provided to the customer is the same. The service catalog on the other hand is what drives the operational side of the
Read more

We're back

After a long hiatus of just on 12 months we're back. We will be continuing our series of weekly posts on service management for service providers. Stay tuned.
Read more