implementation planning template dg

8/20/2019 Implementation Planning Template Dg

1/13

1

Implementation Planning Template

Assumptions

[example]

For this implementation to take place, the following assumptions have been made

• !ll sites are read" for e#uipment installation, and the has ensured that an" power, air

conditioning, circuit installation, or other work has been completed prior to the implementation team%sarrival.

• has ensured that all live circuits that are to connect to the e#uipment have been full" tested

and subse#uentl" proven to be suitable to carr" network traffic.

• has taken deliver" of all e#uipment and has installed power rails and circuit breakers in

cabinets where re#uired, connected power to them, and tested the power to ensure it is capable ofsuppl"ing the e#uipment to be installed.

• has ensured the availabilit" of grounding points for e#uipment&cabinets.

• !ll e#uipment is shipped in full working order and has a P$'$(! flash cop" of the image as well as

that is stored on the boot)flash.

• has assigned implementation technicians who are capable of following the implementation

plan with due care and skill and giving signoff to the re#uired parts of the partner or $iscoimplementation.

*uring implementation, it is assumed that one or more partner or $isco representatives&implementationengineers will be on site, and that a representative will also be present at all times.

(n this document, the term +implementation team+ refers to all parties. he terms +partner,+ or+$isco&partner,+ or +$isco implementation engineers+ refer to the $isco&partner personnel.

Tools Required


2/13

#

Implementation Plan

[example]

Table 1 Tools Required

Item Description

1. P$ with -// emulator, /0ase interface, FP server, FP client, 1-2ite, and lanbtld applications.

2. console port cable *03)4567&*087.

3. 9thernet transceiver.

4. /0ase 9thernet cable.

5. 1tandard toolkit including Phillips :o. and ; mm flat blade drivers.

6. $able ties.

7. $able labeling machine.

8. $able label holders ke")fob st"le=.

9. $lippers&knife to cut packaging materials.

10. ape measure.

11. *igital -olt 'eter *-'=.

12. 0P switch software 38b.img, associated files, and release notes.

13. 0$$6- bootcode ?.$.' and release notes.

14. (@1 image rpm)As)mB.8/)8.7. and release notes.

15. Personal electrostatic discharge 91*= strap.

16. 0PC;// installation documentation, including +(nstallation @verview,+ +Preliminar" 1teps 0efore(nstalling,+ +(nstallation in $ustomer $abinet,+ +(nstalling *$ 1helf,+ +(nstalling 0P 1witch $ards,+ and+$hecking and Powering)Dp.+

17. E7E; installation documentation8, including +Preparing for (nstallation,+ +(nstalling the $isco E7// 1eries4outer,+ +'aintaining the $isco E7E;,+ and +roubleshooting the (nstallation.+

18. $isco 1$88// installation documentation, including +Preparing the (nstallation 1ite,+ +?ardware(nstallation (nstructions,+ +Power and Grounding,+ +(nstalling a Preracked $onfiguration,+ and+'aintenance.+

Implementation Tas$s

9ach activit" is described in further detail below.

(ndicate the output of each activit" on the implementation record.

1hould be delivered with e#uipment. !lternativel", "ou can find it in the $isco Product *ocumentation athttp&&www.cisco.com&univercd&home&home.htm.

8 1hould be delivered with e#uipment. !lternativel", "ou can find it in the $isco Product *ocumentation at

http&&www.cisco.com&univercd&home&home.htm. 1hould be delivered with e#uipment. !lternativel", "ou can find it in the $isco Product *ocumentation athttp&&www.cisco.com&univercd&home&home.htm.


3/13

%

Implementation Plan

[example]

Table 2 Implementation Tasks

&tep Tas$

. $onfirm 91* procedures.

2. Prepare installation area.

3. 0uild cabinets.

4. (nstall cabinet power feeds, rails, and protective earthing.

5. Dnpack e#uipment.

6. Ph"sicall" install e#uipment in cabinet, including cables between new network devices.

7. 4ecord e#uipment serial numbers, and check against deliver" documentation.

8. -erif" that e#uipment card modules are inserted into the correct slot allocations.

9. (nstall intra)cabinet power and protective earth cabling.

10. (nstall intra) and inter)cabinet communications cables.

11. -erif" circuit termination in patch panel.

12. Power up $isco e#uipment.

13. -erif"&load s"stem software&firmware.

14. $onfigure e#uipment.

15. $omplete installation tests.

16. !dd e#uipment to the network.

17. $omplete commissioning tests.

18. $omplete implementation record.

1' Conirm &D Procedures

[example]

• 91* regulations dictate that 91* straps and lab coats must be worn at all times when in

the e#uipment room.

• to provide 91* coats and straps.

• to test 91* straps prior to use.

4ecord an" issues on the implementation hand)over certificate.


4/13

*

Implementation Plan

#' Prepare Installation Area

[example]

• personnel is to prepare the installation area in accordance with the 141 documentation.

• is to ensure that the build area is free from obstruction and that the cabinet area to be used

is clear of an" obstruction or other e#uipment.

• is to ensure that e#uipment is delivered to the location where it is to be installed.

• Partner or $isco is to confirm that rack&e#uipment location information is in accordance with

http://www.cisco.com/univercd/home/home.htm .


%' +uild Ca!inets

[example]

• Partner or $isco is to build e#uipment into $isco 14!' cabinets to the specifications.

• Partner or $isco is to install additional tapped angle strips at the rear of each cabinet.

•

Partner or $isco is to install 1'0 **F rails above and below the 'GCC7/ e#uipment.• Partner or $isco is to install *$ distribution rails at the top of the rear of each cabinet.

• Partner or $isco is to install additional fan tra"s at the top of each rack in accordance with the

manufacturer recommendations.


*' Install Ca!inet Po,er -eeds. Rails. and Protectie arting

[example]

*$ power rail la"outs

Power suppl" re#uirements


5/13

0

Implementation Plan

• (mplementation team is to follow local safet" re#uirements and those detailed in the installation

manuals.

• (mplementation team is to follow local e#uipment and cabinet)specific power, grounding, and bonding

re#uirements, as well as those detailed in the installation manuals.

• Partner or $isco is to ensure that the work carried out b" and on behalf of partner or $isco is done so

with due regard to the relevant regulations, standing instructions, working practices, and procedures atthe site.

• is to provide the correct power suppl". For !$ supplies, appropriate sockets to be

provided adAacent to the rack position. For *$ supplies, is to provide cabling toe#uipment position with an appropriate crimp connector. !n appropriate crimp tool can be obtainedfrom 41 $omponents at http&&rswww.com product code 667);.

• is to provide an isolated earth cable to the e#uipment position with an appropriate crimp

connector. ; mm earth cable at cabinet earth point.=

• Partner or $isco is to verif" %s installation of cabinet power rails, power feeds, and earthing

and ensure that all supplies are isolated. 7/! *$ supplies at each cabinet *$ distribution rail.=

• Partner or $isco is to label power suppl" cables of the form +Burcs/ psu live,+ where Burcs/ is

the node being connected to, psu is the power suppl", and live is the terminal termination point.


0' npac$ quipment

[example]

Jou can find details of the e#uipment order&s within the product%s documentation material. !lternativel","ou can reference the $isco documentation website.

Jou can find details of rack mounting of e#uipment in the later section +Ph"sicall" (nstall 9#uipment in$abinet, (ncluding $ables 0etween :ew :etwork *evices.+

• he implementation team is to check that packaging has not been damaged in transit. $heck tip and

shock indicators.=

• he implementation team is to check that e#uipment is in good condition when removed from

packaging.

• Partner or $isco is to assemble e#uipment adAacent to the installed position.

• Partner or $isco& is to retain all packaging until the implementation is complete. Hhere

e#uipment needs to be shipped in the original packing material, such as for 4'! purposes, thee#uipment and packing must be matched accuratel".

• is to arrange the removal of packaging from site when all implementation activities have

been completed.

4ecord an" issues on the (mplementation hand)over certificate.


6/13

2

Implementation Plan

2' P3sicall3 Install quipment in Ca!inet. Including Ca!les +et,eenNe, Net,or$ Deices


7/13

4

Implementation Plan


5' 6eri3 Tat Card 7odules Are Inserted into te Correct &lot Allocations

[example]

1lot allocations for each piece of e#uipment

• Partner or $isco is to verif" slot allocations.

• Partner or $isco is to correct an" incorrect slot allocations.


8' Install Intra9Ca!inet Po,er Ca!ling and Protectie art Ca!ling

[example]

*$ power rail la"outs are shown in http://www.cisco.com/univercd/home/home.htm .

Power suppl" re#uirements are shown in the 141.

• is to provide *$ power cables and cabinet earthing cabling and ground points. 1uitable

crimps can be obtained from 41 $omponents at http&&rswww.com with product codes of 7)/8 for a/ mm 8 cable and 3);/ for a ; mm 8 cable.

• is to confirm that power is from isolated supplies.

• Partner or $isco is to install prepared power cables between cabinet power rails and

e#uipment power entr" modules, as indicated in the documentation.

• Partner or $isco is to connect earth cables to cabinet earth points and e#uipment)specific bonding

locations. is to present a prepared cable to the cabinet position.=

• Partner or $isco is to neatl" tie and label cabling with ke" fob)st"le holders. $able labels should be ofthe form +Burcs/ psu live,+ where Burcs/ is the node being connected to, psu is the powersuppl", and live is the terminal termination point.

• Partner or $isco is to verif" that power cables and data cables are segregated.


1:' Install Intra9 and Inter9Ca!inet Communications Ca!les


8/13

5

Implementation Plan

[example]

$ables for e#uipment have been included in the order, as shown in the documentation

Jou can find device cabling end points in the product documentation material.

• is to provide intra)cabinet cables.

• Partner or $isco is to ensure that fiber cables are not wound so tightl" that damage might be caused to

the fiber itself.

• Partner or $isco is to install all provided cables between e#uipment used in the same rack in

accordance with the product documentation material.

• Partner or $isco is to neatl" tie and label cabling with ke" fob)st"le holders. $able labels should be of

the form +Burcs/ 8. K Burec/ E.,+ where Burcs/ and Burec/ are the nodes being connectedwith the cables connecting to line of card 8 and of E respectivel", and Burcs/ is the local node.

•Partner or $isco is to verif" that power cables and data cables are segregated.


11' 6eri3 Circuit Termination in

[example]

$ables for e#uipment have been included in the order, as shown in product documentation material.

Jou can find device cabling end points in product documentation material.

• is to confirm that circuit designations between patch panel and :D e#uipment are

correct.

• is to confirm that all cabling between :D e#uipment and the patch panel is correct and

has been tested.

• is to confirm that all circuits have been tested successfull".

• is to confirm circuit designation to partner or $isco.

• is to confirm that all cable runs are within cable and signal length specifications.

• Partner or $isco is to record circuit termination information in product documentation material.


1#' Po,er p Cisco quipment


9/13

8

Implementation Plan

[example]

• Partner or $isco is to confirm that *$ power supplies are within range using a *-'.

• Partner or $isco is to switch on all e#uipment power supplies. 4efer to an" local re#uirements to

power up in stages.=

• Partner or $isco is to confirm that all e#uipment begins power)up c"cle.

• Partner or $isco is to confirm that all e#uipment provides a user prompt when a -//)compatible

laptop is connected to the console, or e#uivalent, port.

• Partner or $isco is to log into each device in turn and verif" that there are no outstanding&unexplained

alarms or unexplained e#uipment failures following power)up.


1%' 6eri3/;oad &3stem &ot,are/-irm,are

[example]

1"stem software re#uirements are shown in product documentation material.

*etails of software upgrade procedures are detailed in product documentation material.

• Partner or $isco is to connect to each $isco H!: device in turn using a -//)compatible terminal

and verif" switch software, bootcode, and firmware versions.

• Partner or $isco is to connect to each $isco router in turn and verif" (@1 software versions.

• Partner or $isco is to correct an" variation to the defined releases.


1*' Conigure quipment

[example]

Jou can find special instructions that should be observed prior to loading configurations in productdocumentation material.

Jou can find device configurations in product documentation material.

• Partner or $isco is to input device configurations that will be used prior to testing.



10/13

1:

Implementation Plan

10' Complete Installation Tests

$omplete individual test sheets for each test.

(ndicate an" failures on the implementation hand)over certificate.

[example]

Table 3 Installation Tests

Test Description

+P

*'12'1 $ard visibilit"

*'12'# 9nvironmental checks

*'12'% !larm verification

*'12'* 9rror detection

*'12'0 Power suppl" failure

*'12'2 Fan failure

7=

*'12'4 $ard visibilit"

*'12'5 !larm verification

*'12'8 Power suppl" failure

*'12'1: Dnused service module line checks

*'12'11 1ervice module configuration verification

*'12'1# Firmware verification

*'12'1% $ard error detection

4#:*

*'12'12 P1Ds operational

*'12'14 !ll modules recogniBed

*'12'15 Flash boot register verification

*'12'18 ?ardware visibilit"

*'12'#: 'emor" availabilit"

40:4

*'12'#1 P1Ds operational

*'12'## !ll modules recogniBed

*'12'#% Flash boot register verification


11/13

11

Implementation Plan

Test Description

*'12'#* ?ardware visibilit"

*'12'#0 'emor" availabilit"

12' Add quipment to


12/13


13/13

1%

Implementation Plan

implementation planning template dg

Documents