Service delivery best practices: Translating customer needs into network services

Staff Writer
30 Jun 2008
00:00

 

Essentials for painless implementations
Painless implementations start with proper up-front planning. No matter how beneficial a customer's new network services will be implementation problems can erode financial benefits and create doubt regarding the true capabilities of the new services. Implementations usually require installation and configuration of new equipment. Without proper planning this can be a disaster both from a timeline perspective and an actual integration perspective. Delays and adverse impact to the network should be avoided at all cost.

Deployment planning should focus on the following areas:

  1. Robust architecture
  2. Standardized configurations and detailed design
  3. Procurement
  4. Site readiness
  5. Scheduling and resourcing
  6. Change management
  7. Site turn-up
  8. Site testing
  9. Operational handover

Each of these areas in itself can contribute to implementation missteps and problems so clearly understanding the essential areas of focus in each is important.

Robust architecture
A robust architecture is one that defines all aspects of the architecture including the desired features functionality and capabilities as well as integration into the current network and visibility from a management perspective. If the new network services are enabled via a new technology with which the organization has no prior experience it is highly recommended that proof-of-concept lab testing or piloting of the solution take place prior to deployment.

Standardized configurations and detailed design
If possible standard configurations should be created for the network elements delivering the network services. Many installation efforts fail due to inconsistencies in the configuration of the gear during deployment and difficulty in troubleshooting within a non-standard environment.

A detailed design should be developed that outlines the configuration specifics for each site. This should be done prior to deployment so that equipment-specific or site-specific information can be tied directly to the design details of the sites including port mappings interface naming host naming IP addressing VLAN addressing dial plans and other numerous site-specific configuration parameters. In all cases providing specific site configuration details and standard configuration templates up front reduces errors during deployment.

Procurement
There is nothing like botching an installation due to the equipment not arriving on time receiving the wrong equipment or having equipment dead on arrival. The procurement process must include contingencies for all of the above and robust communication channels to notify of delays prior to the implementation window.

Site readiness
No matter how well the architecture has been defined and the configuration details sorted out if the site where the changes are being made is not ready for the change none of the other implementation plans matter. Site readiness should consider space power and HVAC requirements port availability and demark extensions at a minimum. There is nothing more frustrating than failing to turn up a site because no one at least eyeballed the equipment room to ensure there is space for the equipment.

Scheduling and resourcing
Getting the right resources to the right place at the right time doing the right tasks is essential to any successful deployment. Implementations are resource dependent and do not happen on their own. Poor planning in this area is a recipe for failure.

Change management
Most organizations require that some form of change management process take place to review schedule and communicate changes within the environment. Change management can be process intensive and in some cases constrained to certain windows of time. However not adhering to the process can bring the scheduled installation to a screeching halt.

Site turn-up
Site turn-ups require resources to install and configure the network elements to deliver new network services. Having a well documented installation and configuration script (list of tasks) is essential to guiding the turn-up resources through the installation in a predefined manner.

Pages

Follow Telecom Asia Sport!
Comments
No Comments Yet! Be the first to share what you think!
This website uses cookies
This provides customers with a personalized experience and increases the efficiency of visiting the site, allowing us to provide the most efficient service. By using the website and accepting the terms of the policy, you consent to the use of cookies in accordance with the terms of this policy.