Cisco Blogs

Cisco Blog > SP360: Service Provider

SDN and NFV Use Cases in EPN

My last post reviewed some of the building blocks of SDN (Software Defined Networking) and positioned the protocols and APIs (Application Programming Interface) into categories so that the multitude of technologies associated with SDN can be positioned in a coherent framework. This month I’d like to start looking at some use cases where some of these things are used to deliver benefit in a service provider network.

I will review a consumer oriented offering and next month, one targeted at enterprise services.

As always, it is important to define the business outcome we are trying to affect when making a change to the network infrastructure. This case will consider an operator Read More »

Tags: , , , , , , , , , , , , , ,

The Cisco – SP Partnership: How Proactive Planning Drives Service Quality

By Carlos Cordero, Director, Service Provider Internet Business Solutions Group

In my previous blog I explained the importance of collaborative testing between telecommunications service providers (SPs) and their network vendors in order to achieve higher service quality levels. I’d like to start where I left off and move on to exploring how this type of collaboration can extend into the planning process.

SPs with the highest service quality tend to have a strong planning capability within both their Network Engineering and Operations organizations, which is directly coordinated with their vendors. Leading SPs establish a joint Program Management Office (PMO) with their network equipment vendor, whose scope of responsibility includes early bug identification, bug remediation, and new feature deployment. This includes structured, joint planning meetings and performance reviews which are attended by VP-level engineering and operations executives, as well as senior members of the vendor’s account team, services organization, and the development organization.

The joint SP-vendor PMO performs several critical activities.  First, it drives requirements gathering with senior network designers, and then works with them until actual code is released.  The PMO also develops network architectures with the vendor and the SP’s engineers using “Plan-of-Record” (POR) documentation.  Next, the PMO jointly prioritizes feature functionality with the vendor, keeping track of critical features needed by specified timeframes.  It works closely with the vendor’s development organization to understand any design limitations, testing issues, and special conditions.  In addition to performing classic management functions, the PMO makes use of “Bug Workbooks” to track all major, critical, and minor bugs and trends.

For example, Read More »

Tags: , , , , , , , , ,