Implementation Planning

To ensure a smooth transition to the new network service, each site requires careful planning. The following is provided as an example of how to identify tasks, assign owners, and track the progress of actual versus planned activities. This is offered as a starting point for when you consider what activities are necessary to ensure a proper working installation at each site. This documentation exists for the following phases of the network transition:

• Phase 1 Pre-cutover to ensure that all planning documents are complete and distributed

• Phase 2 Connecting major sites to the new network

• Phase 3 Cutover on a site-by-site basis

• Phase 4 Post-cutover activities and sign-off

Phase 1

Phase 1 contains documentation that resembles Table 10-1.

Table 10-1. Typical Phase 1 Implementation Planning Tasks

Sequence	Due (by EoB)	Owner	Action
1	1/27/2006	Adam	Team approval that all risks have been identified.
2	1/27/2006	Samantha	Create a plan for Tuesday the 31st to introduce core IDCs into production.
3	1/31/2006	Michael	Operations approves IDC connectivity.
4	1/31/2006	Adam	Routing team approves documentation.
5	1/31/2006	Michael	QoS team approves documentation.
6	1/31/2006	Samantha	Multicast team approves documentation.
7	1/31/2006	Mo	Documentation approved by providers.
8	1/31/2006	Samantha	Support document for engaging provider's support groups.

Phase 2

Phase 2, which is the stage of planning a major site (such as an IDC) connection to the new production network, must be completed. This could be monitored via a document like that shown in Table 10-2.

Table 10-2. Typical Phase 2 Implementation Planning Tasks

Sequence	Due (By EoB)	Owner	Action
1	1/31/2006	Team 1	Check out-of-bound access/dial for all IDCs.
2	1/31/2006	Team 1	Shut and make passive all Gigabit Ethernet links to the corporate network from the respective MAN gateways connecting to IDCs.
3	1/31/2006	Team 1	Ensure that the MPLS cloud learns only expected routes, such as core IDCs.
4	1/31/2006	Team 1	Issue no shut and no passive commands on one Gigabit Ethernet link to leak the corporate address into the new MPLS network.
5	1/31/2006	Team 1	Ensure that the MPLS cloud learns only expected routes, such as core IDCs and corporate routes.
6	1/31/2006	Team 1	Check that internal support can reach all devices (monitor at P6).
7	1/31/2006	Team 1	Commence operations to drive cleanup and accept configs.
8	1/31/2006	Team 1	Tweak metrics for MPLS cutover so that routing works as expected during the transition.
9	1/31/2006	Team 1	Document and report change/variance (including the procedure to isolate the core).
10	1/31/2006	Team 1	Conduct a team status meeting to discuss the success so far. Assign remedial actions to address any issues that may be apparent.
11	1/31/2006	Team 1	Decide whether to proceed with the current plan or amend it.
12	2/1/2006	Team 1	Perform a health check of the network during a maintenance window.

Phase 3

Phase 3 involves rolling out the network implementation to all locations. There may be many sets of procedures for sites of differing sizes and complexity; however, the aim is to produce a reasonable set of procedures that can be replicated in each site with similar requirements. Some suggested details for this phase appear in the section "On-Site Implementation."

Phase 4

Phase 4, the final phase, defines the activities to be completed post-cutover and includes the items covered in Table 10-3. This phase should be executed as a rolling activity because the installation progresses through all geographies and sites the new network will reach.

Table 10-3. Typical Phase 4 Implementation Planning Tasks

Sequence	Due (by EoB)	Owner	Action
1	2/15/2006	Team 2	Routing team verifies operation and signs off.
2	2/15/2006	Team 2	QoS team verifies operation and signs off.
3	2/15/2006	Team 2	Multicast team verifies operation and signs off.
4	2/15/2006	Team 2	Network management team verifies operation and signs off.
5.	2/14/2006	Team 1	Conduct a daily/weekly technical review with service providers.
6	2/15/2006	Team 2	Document and summary report from each technology team lead (assess whether more time is needed).
6.1	2/15/2006	Team 1	Conduct a network performance call with the provider.
7	2/15/2006	Team 1	Compile a migration report and assess the migration strategy with respect to moving forward.
8	2/16/2006	Team 2	Health check by the operations team.
9	2/16/2006	Team 2	Outstanding testing that may be required.