Design Network Services with Automated Provisioning
Network Performance Innovations (NPI) will help you make the most of Network Service design by creating detailed release packages, implementing automated provisioning that will greatly reduce unexpected service disruptions due to change and realize a ROI.
NPI has worked with several multi-billion dollar corporations to help them improve their network management processes. Utilizing state-of-the-art network management philosophies, NPI has helped improve network reliability, availability, and ROI. With over 30 years of hands-on experience, NPI is a must for corporations concerned about ITIL and other network management issues.
[su_spacer size=”10″] [div style=”clear:both;”] [/div]
[pagewidth background=”#222″ color=”#fff” id=”theclose”][su_spacer size=10]
ITIL Service Design:
[evp t=thirditem img=”http://www.networkperformanceinnovations.com/wp-content/uploads/2013/02/info.png” last=0 title=”Engineering”]Conventional engineering processes are often disregarded when working with COTS products. The engineering department is more often focused on provisioning and troubleshooting.[/evp]
[evp t=thirditem img=”http://www.networkperformanceinnovations.com/wp-content/uploads/2013/02/info.png” last=0 title=”Release Package”]The release package for a service should be so thorough that implementation becomes a turn-key operation with certainty of outcome. Risks are more manageable.[/evp]
[evp t=thirditem img=”http://www.networkperformanceinnovations.com/wp-content/uploads/2013/02/info.png” last=1 title=”Designed for Automation”]When the design has the necessary detail, automated provisioning becomes a reality that significantly improves availability and reduces the provisioning and operations LOE.[/evp]
[su_column size=”2-3″ last=0]
Its Time For A Paradigm Shift
There is a paradigm associated with designing a network using COTS products that causes network engineering workcenters to disregard the conventional engineering process. Consider the design for an aircraft. Engineers don’t go out and build aircraft from scratch and create them differently every time. Engineers design a blueprint that addresses all aspects of the design and system lifecycle. The production team takes that blueprint and fits the factory to build many aircraft using this design. Retrofits follow a similar process. Consider a software engineering project. The developer considers each platform the application is to be released on, develops for each target platform and creates installation packages. That installation package takes into account any variation in the platform. This has been thoroughly tested prior to release. The installation package installs with high degree of certainty and doesn’t require a software engineer to install. Enhancements and fixes are packaged and released on a schedule. Imagine if an application was released a collection of executables, libraries, and support files and the installer was expected to install it correctly based on the system it was being installed on. The results wouldn’t be very certain and there would be a large number of incidents reported for failed installations. That sounds absurd, but this is how most network engineering work centers operate.
The ITIL service design process treats a service similar to the way the aircraft or application are handled in the above examples. When the network is treated as a service that must be subject to this same rigorous engineering process, the result is improved efficiency a high degree of predictability that reduces service disruptions caused by unexpected behavior encountered during changes. This requires a great deal more engineering effort during the design and release processes, but the ROI is improved availability and reduction effort during implementation. Implementing the release package becomes a turn-key operation that should be performed by the operations or provisioning team rather than engineering. This paradigm shift often takes some time for an organization to grasp and function efficiently in, but will improve performance and efficiency and paves the way toward automated provisioning.
The transition to a network engineering process that functions in this manner is extremely difficult if no one on the engineering team has produced design in this manner. NPI has the experience to guide you through this transition and can develop the network automation tool to provision the network using this design package.
1. Are all the configurable items on your network equipment standardized?
2. If so, are the standards version controlled?
3. Do you know what version each of the network devices are using?
4. Do you release changes on a schedule or ad-hock?
5. Can a change be made to the network without changes made to the standard first?
6. Could a Tier 2 technician provision network equipment using the approved standard?
Contact us to find out the correct answers to these questions and get on the path to ITIL compliant network design and automated provisioning.
[evp t=saleitem img=”http://www.networkperformanceinnovations.com/wp-content/uploads/2013/02/Beker.png” last=0 title=”A Case Study – DTS-PO: the ISP for the Department of State field offices.”] When a customer required a change to service, the time from service order to delivery averaged about three months. The technology refresh for the next generation network, FASTNET, resulted in a very complex design due to the unique nature of the requirements. ITIL processes were implemented, and they were continually improved until they became effective and efficient. The Supplier developed an Operational Support System (OSS) that automated service to delivery. The result was service to delivery in minutes without unexpected service disruption. All aspects of FCAPS were also addressed by OSS as part of the system lifecycle. They realized a ROI as well. The OSS automation was key to this achievement.[/evp]
[su_column size=”1-3″ last=1]
Find out how to implement a Service Design strategy that leads to automated provisioning.
[gravityform id=”1″ name=”LinkedIn Form” title=”false” description=”false” ajax=”true”]