TM

Site Specific Implementation Plan

Version 3.0
Prerequisites
Satisfactory completion of the Planning Phase is required prior to developing the detailed
design.

Document Instructions
 This header page and partner cover page should be deleted; they are intended to
provide instructional value only.
 The below content is formatted using Styles: 1. Header One, 2. Text and 3. Bulleted
information.
 “Fields” are used in the following manner:
o TOC - Update the Table of Contents by right clicking in TOC and choosing
“Update Field”, “Update Entire Table”.
o “Title” and “SaveDate”– contained in the footer of the document.
 The “Title” is located in File, properties – change to match the
asset that is being created.
 Revised date is the “SaveDate” field.
 To update either field: switch to view header/footer mode; right click field,
choose update.
 Where applicable replace <Partner Logo> with your logo graphic, otherwise delete that
reference.
 Text that is in red and/or between <> symbols should be replaced by the Partner with
customer or implementation specific information.
 As appropriate, remove appendix information.
Document Owner
It is recommended that the owner of this document be the partner lead project engineer.
Version Control
This document will be kept current on the Lifecycle Services Web site. It is recommended that
rather than archiving this document, you download it each time you need it.

Document Owner(s) Version Number Date Nature of Update

Changes are logged in the revision history at the end of the document. A minor update involves minor corrections
or adjustments to language. A major update involves the introduction of new content, or a significant substantive
change to existing content.

Document History
Version Release Date Description of Change

March 2008
<Partner Logo>
TM

TABLE OF CONTENTS

Legal Disclaimer...............................................................................2
1 Implementation Overview..............................................................4
....................................................................................................................................................................................4
1.1 Implementation Objectives......................................................................................................................................4
1.2 Customer Requirements.........................................................................................................................................4
1.3 Customer Impact.....................................................................................................................................................4

2 Pre-Change Site Audit ...................................................................5

2.1 Identify and verify device list:..................................................................................................................................5
2.2 Identify power and cabling requirements:...............................................................................................................5
2.3 Existing infrastructure: (i.e. physical and logical diagrams)....................................................................................5
2.4 Current configurations: ...........................................................................................................................................5
2.5 Current software levels:..........................................................................................................................................5
2.6 Issues or potential problems:..................................................................................................................................6
2.7 Site security access (optional):...............................................................................................................................6

3 Step-by-Step Network Change Plan................................................7

3.1 Document proposed infrastructure .........................................................................................................................7
3.2 Proposed configurations ........................................................................................................................................7
3.3 Proposed software levels........................................................................................................................................7
3.4 Perform network change plan: (example below)....................................................................................................7

4 Systems Acceptance Testing..........................................................8

4.1 Perform step-by-step application/end-user system testing.....................................................................................8
4.2 Communicate with key players status of network change......................................................................................8
4.3 Closely monitor of health and stability of network post change..............................................................................8
4.4 Attach As-Built Diagram here (optional).................................................................................................................8

5 Back-Out Procedures......................................................................8
5.1 Develop step-by-step procedures...........................................................................................................................8
5.2 Communicate with key players status of network change......................................................................................8

March 2008 Page 1 of 9

<Partner Logo>
TM

Legal Disclaimer
The Templates that accompany this Terms of Use document may be used by a Cisco-authorized reseller solely in connection with
reseller’s activities to promote and sell Cisco services. Reseller’s use of such Templates is subject the reseller’s systems integrator
agreement or indirect channel partner agreement (ICPA), between reseller and Cisco.
Cisco owns and shall continue to own all right, title and interest in and to the Templates. Reseller may modify the templates to suit
particular business opportunities; however, Cisco assumes no responsibility for the accuracy of the information in the Templates or
of any modifications made by reseller to such templates. Cisco reserves the right to change the programs or products covered by
the Templates at any time without notice. Mention of non-Cisco products or services is for information purposes only and constitutes
neither an endorsement nor a recommendation.

ALL TEMPLATES ARE PROVIDED "AS IS" WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED INCLUDING, WITHOUT LIMITATION,
THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO’S LIABILITY WITH REPSECT TO THE TEMPLATES EXCEED THE AMOUNTS PAID FOR THE TEMPLATES BY
YOU. CISCO AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL
DAMAGES INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR REVENUES WHETHER ARISING IN CONTRACT, TORT (INCLUDING
NEGLIGENCE), OR OTHERWISE, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

March 2008 Page 2 of 9

<Partner Logo>
TM

Service Practice Templates for

Partners
For Partners

Security
Site Specific Implementation Plan
Version 3.0

<Customer Name>
<Insert Partner Logo>
<Partner Address>

<Partner Website>

Corporate Headquarters
Cisco
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100

March 2008 Page 3 of 9

<Partner Logo>
TM

Site Specific Implementation Plan

1 Implementation Overview
Published / Revised Version Author Section / Nature of Change
Date #

Maintenance Window Start

Date/Time:
Maintenance Window End
Date/Time:

Site Name
Address
State Countr
City
y

Key contacts / Escalation

Group Name Phone Pager / Cell

Primary Network Engineer
Project Manager
Network Operations Lead
Application System Admin
On-Site Network Support

1.1 Implementation Objectives

Objective Reason

1.2 Customer Requirements

1.3 Customer Impact

March 2008 Page 4 of 9

<Partner Logo>
TM

2 Pre-Change Site Audit

2.1 Identify and verify device list:

Place spreadsheet here

2.2 Identify power and cabling requirements:

Wiring Closet Requirements

2.3 Existing infrastructure: (i.e. physical and logical diagrams)

Place diagrams here

2.4 Current configurations:

Note: Configurations for relevant network devices should be collected in a central
repository prior to network change.

2.5 Current software levels:

Note: Software images for relevant network devices should be collected in a central
repository prior to network change.

Device Software

March 2008 Page 5 of 9

<Partner Logo>
TM

2.6 Issues or potential problems:

2.7 Site security access (optional):

Place company security procedures here.

March 2008 Page 6 of 9

<Partner Logo>
TM

3 Step-by-Step Network Change Plan

3.1 Document proposed infrastructure
Place proposed network diagram here.

3.2 Proposed configurations

Place new configurations here.

3.3 Proposed software levels

Identify any new software releases here.

Device Software

3.4 Perform network change plan: (example below)

Step 1: Back up the running-configuration to flash

Step 2: Copy configuration to centralized TFTP server
Step 3: Ensure flash size can support new IOS image
Etc…

March 2008 Page 7 of 9

<Partner Logo>
TM

4 Systems Acceptance Testing

4.1 Perform step-by-step application/end-user system testing
Note: System acceptance testing is customer specific. The steps below are provided as an
example only.

Steps
Example 1 Ensure connectivity to all servers
Example 2 Test network applications to ensure performance falls within expectations
Example 3 Test client connectivity from a variety of locations

4.2 Communicate with key players status of network change

Feedback from the project/engineer lead to key contact(s) is vital for proper communication
regarding the status of the network change.

Contact 1: ____________________
Contact 2: ____________________

4.3 Closely monitor of health and stability of network post change

After any significant network change, there should be a period of close monitoring of the new
network to ensure network stability and availability.

4.4 Attach As-Built Diagram here (optional)

Note: If your as-built network diagram differs from your proposed network diagram, include
the as-built drawing here.

5 Back-Out Procedures
5.1 Develop step-by-step procedures
Note: Identify steps to revert to original running configuration in the event of unforeseen
network issues

5.2 Communicate with key players status of network change

Feedback from the project/engineer lead to key contact(s) is vital for proper communication regarding
the status
of the network change.

Contact 1: ____________________

March 2008 Page 8 of 9

<Partner Logo>
TM

Contact 2: ____________________

March 2008 Page 9 of 9

<Partner Logo>
TM