Pipeline Publishing, Volume 3, Issue 1
This Month's Issue: 
Balancing Billing 
download article in pdf format
last page next page
Keeping it all in Check
back to cover

article page | 1 | 2 | 3 |

click of a mouse and enabled in as close to real time as possible. This level of detailed information and automated functionality is ultimately dependent, however, on the strength and end-to-end automation of the operations support systems (OSS) managing background processes and a combination of network technologies.

An Incremental Approach
Naturally, not all of the OSS functionality discussed will be necessary from day one, so any solution should be deployable in increments that grow in parallel with service complexity. Relying on a quick and dirty solution, however, that is not already designed for the future network state will simply lead the operator into a difficult cycle where operations is constantly trying to catch up with the network, but always seems to fall further behind. Such is the nature of most ILEC operations, so here sits an opportunity to gain competitive advantage by planning for the future service and OSS capability set from the start.

Working with an Experienced
OSS Partner

There are a number of vendors that offer integrated OSS functionality in MSOs production environments. To minimize the risks associated with a long term undertaking such as an incremental OSS build out, it is critical to speak with each vendor’s customers to gain a solid understanding about the vendor’s strengths and breadth of expertise.


Participation on the part of the MSO is also necessary to ensure success. The MSOs expertise and familiarity with its own operations must be captured and channeled into business and operational planning for product and service definition. The MSO must also participate in defining processes for order capture, order management, equipment procurement and installation, service provisioning, and service diagnostics. It is imperative that IS/IT, engineering, customer care and operations work together with the OSS partner to define these requirements as well as defining and deploying services jointly once the OSS environment is established.

If these groups operate with solid walls between them, or with distinct operations systems, the operator will unnecessarily delay every service roll out, add arbitrary costs to the equation and significantly increase the risk of either failing to deliver a new service or failing to beat competitors to market. Building an integrated OSS suite correctly from the start, with a clear road map of how it will grow in increments, will deliver advantages that competitors cannot match. Most competitors – including ILECs and CLECs - are themselves struggling to coordinate disparate systems and organizations that were neither designed nor tasked to play well together. All that is required is for the operator to remain in a forward-thinking mode, understand the specific needs of the IP services market, and recognize the relationship between the investment of time and effort in creating OSS automation and the distinct competitive advantages that will result.

article page | 1 | 2 | 3 |


last page back to top of page next page
 

© 2006, All information contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding
the use of this information. Any unauthorized use, such as copying, modifying, or reprinting, will be prosecuted under the fullest extent under the governing law.