Network Upgrade
Project Management Plan
Revision Status: Draft
Document Control Information
Document Author: Irving Treviño
Project: Network Upgrade
Project Manager: Irving Treviño
Project Phase: Project Management Plan
Document Approver(s):
Approver Name
Arturo Manrique
Role
Program Manager
Summary of Changes:
The Document Author is authorized to make the following types of changes to the
document without requiring that the document be re-approved:


Editorial, formatting, and spelling
Clarification
Changes to this document are summarized in the following table in reverse
chronological order (latest version first).
Revision
1.0
Date
Created by
25/02/2013 Irving Treviño
Short Description of Changes
Initial Version of approved document
2
Table of Contents
1. Introduction ............................................................................................................... 4
1.1 Purpose .......................................................................................................... 4
1.2 Scope.............................................................................................................. 4
1.3 Intended Audience .......................................................................................... 5
1.4 Overview ......................................................................................................... 5
2. Roles......................................................................................................................... 5
3. Plans ......................................................................................................................... 6
3.1 Project charter................................................................................................. 6
3.2 Project scope management ............................................................................ 7
3.2.1 Work product list ........................................................................................ 7
3.2.2 High-level Work breakdown structure (WBS)............................................. 8
3.3 Project Time Management .............................................................................. 9
3.4 Project cost management ............................................................................... 9
3.7 Project communications management .......................................................... 10
4. Procedures ............................................................................................................. 11
4.1 Action management ...................................................................................... 11
3
1.
Introduction
1.1
Purpose
Upgrading the network is a necessary prerequisite to prepare both for the future
growth of the company and the upcoming convergence of voice and data
communications.
By building scalability into the project, NetCom as chief of the technological
development department is helping the company stay ahead of the technological
curve.
With the increased day-to-day use of the network for communications, research, and
information sharing, having a modern, reliable, and secure network becomes even
more critical in order to fulfill today’s challenging world.
The purpose of this project management plan summary is to:
 Provide a “table of contents” for the project management plan.
 Help ensure that all members of the project team understand how the
project will be managed and their roles within the management process.
 Document the agreement between the project manager and the program
manager regarding how the project will be managed.
 Document any agreed deviations from constituency policy and practice that
have been agreed with program manager.
 Provide a starting point for project audits or compliance reviews.
1.2
Scope
The Network Upgrade Project will produce the company network with improved
reliability, faster data transfer speeds, increased security, and the ability to grow to
meet the changing needs of the market.
As computer usage and the demands on the company network have increased
exponentially in the past years, we are looking forward to make our systems more
scalable, efficient and versatile by accomplishing the next goals:



Company backbone operating at 10 Gigabits per second (Gbps).
1 Gbps connections to each facility from the backbone network.
100 Megabits per second (Mbps) connections from desktop stations.
4





1.3
Adequate each building (An appropriate HVAC system, dedicated 120v, 20
amp electrical circuits, and secure, limited access for network administrators).
Category 6 cabling to replace all Category 5 data cabling.
New conduit, raceway, and cable tray to allow for easy installation of new and
improved cabling in future decades.
Implement wireless in two of our buildings.
New equipment.
Intended Audience
This document is intended for all technical personnel associated with the project as
well as program managers, co-project managers, workers, stakeholders and
auditors.
1.4
Overview
The following is a list of the people involved in the project, as well as the
development of the project in detail.
We will also review everything about costs, time, and scope, quality procedures,
among other important things.
Everything is structured so that it can be interpreted as a guideline, seeking to
establish best practices through the project development.
2.
Roles
Arturo Manrique, CEO and Chief of Technology Development.
Arturo is our program manager, he will not only be managing the day-to-day financial
aspects of the project, but Arturo is taking charge of the communication strategy,
which will be executed by other collaborators.
Irving Treviño, Director of Information Technology Services.
Irving is managing the project, as well as managing the construction that is required
to install the new equipment in the closets around the company sites.
5
Billy Steaker, Director of Network & Systems Services.
Billy will be the ‘on-the-ground’ co-project manager for the project, working with
Irving Treviño in the day-to-day operations of the network implementation.
Trey Williams, Networking Engineer.
Trey is our lead technical team member for the network upgrade. He will be
shadowing the tech team during the implementation and will be in charge of training
the rest of the group in some specific areas. Chief at the PMO.
Janice Walker, Systems Engineer.
She will be part of the systems team that will oversee the transition of the server fleet
from the old network to the new. Janice is also well-versed in data center
management and power requirements, key components of the network upgrade
project.
John Gallager, Database Administrator.
John is an important cog in the inner workings of the network & systems team. He
will be supporting all of the team members during this project in order to maintain
excellence in our current systems, convey timely technical information, and to help
out wherever he is needed.
Daniel Shultz, Senior Security Engineer.
The most technical aspect of deploying wireless is getting a good, secure
connection. Daniel is one of the most successful professionals in the field of security
and wireless.
3.
Plans
3.1
Project charter
Name
Arturo Manrique
Irving Treviño
Billy Steaker
Trey Williams
Janice Walker
Daniel Shultz
Role
CEO, Program Manager
Project Manager
Co-Project manager
Technology Development
Chief
Technical Chief
Design Chief
Consultant
ID
TSRS-2937
986689-ES
986-HSHSJ
8770-SHSH
HHS-39632
SSS-22022
6
3.2
Project scope management
The planning of the network upgrade begins after the initial site survey and reports
are complete. It consists of:





Requirements Gathering
o The design team in contact with the ISP analyzes the information to
determine network requirements and then generates an analysis
report.
o If insufficient information is available to properly determine the best
network upgrade path to follow,
o This team may request additional information.
Selection and Design
o When the analysis report is complete, devices and cabling are
selected. The design team creates multiple designs and shares them
with other members on the project.
o It is during this step that any weaknesses of the design can be
identified and addressed. Also during this phase, prototypes are
created and tested. A successful prototype is a good indicator of how
the new network will operate.
Implementation
o A good implementation schedule must allow time for unexpected
events and also schedules events to keep disruption of the company’s
business to a minimum.
o Staying in constant communication with the people involved in the
business objectives and services during the installation is critical to the
project’s success.
Operation
o When the network implementation phase is complete, the network
moves into a production environment.
o If all steps up to this point have been properly completed, very few
unexpected incidents should occur when the network moves into the
operation phase.
Evaluation
o After the network is operational, the design and implementation must
be reviewed and evaluated against the original design objectives.
It is important that, at each phase, careful planning and review occur to ensure that
the project goes smoothly and the installation is successful.
7
3.2.1 Work product list
Requirements Gathering



Purchasing network devices and the installation of cabling for a network
upgrade is only the beginning.
Networks must be both reliable and available. Reliability is usually achieved
by adding redundant components to the network. After all this considerations
being gathered, the network design team must determine the level of
redundancy to incorporate to achieve the necessary reliability.
Planning for the network installation must include planning the logical
addressing, which is considered at the very beginning.
Selection and Design

Cabling Considerations
o When planning the installation of network cabling, the team will
consider different physical areas, such as user work areas,
telecommunications rooms, backbone area and distribution area.

Structured Cable
o When designing the cabling part of the project, the first step is to obtain
an accurate floor plan. The floor plan allows the technical team to
identify possible wiring closet locations, cable runs, and which electrical
areas to avoid.

Selecting Network Devices
o The design staff recommends the appropriate network devices to
connect and support the new network functionality.

Selecting LAN Devices
o The design staff will have to consider certain number of factors before
presenting an order to purchase the LAN equipment, two of the most
critical factors regarding to this project are the expandability and cost.
o It is also important to consider the features each vendor provides and
the impact on the costs, as the following:
 Security
 Quality of service (QoS)
 Voice over IP (VoIP)
8





Network Address Translation (NAT)
Dynamic Host Configuration Protocol (DHCP)
Wireless access
Virtual private network (VPN)
Intrusion detection
Implementation
Operation
The two above will be described in the procedures section.
3.2.2 High-level Work breakdown structure (WBS)
9
3.3
Project Time Management
Milestone
Generate analysis of requirements
Finish reports, complete gathering of information
Sign final contracts and purchasing of all equipment
Final choice of ISP
Final Design and technical review process
Install new network hardware
Configure network hardware
Start implementation planning schedule
Implementation phase kick off
Determine possible points of failure before continuing with
operation, make reports and testing
Start operation process and testing
Monitor and review possible issues
Finalizing any outstanding issues
Declare project finished
3.4
Date
04/05/2013
05/05/2013
09/05/2013
10/05/2013
12/05/2013
15/05/2013
20/05/2013
24/05/2013
26/05/2013
29/05/2013
02/06/2013
05/06/2013
10/06/2013
15/06/2013
Project cost management
Global items
Equipment purchasing or leasing
IT Staffing
Training costs
Multiple vendor costs and building
Hardware repairs and upgrades
Software release upgrades
Telephone line charges
Redundancy and reliability
Additional requirements
%
50
15
10
10
2
1
2
9
1
10
3.5
Project communications management
Meeting name
Frequency
Quick review of Daily
Objectives
Program
Manager
meetings
Weekly
4.
Procedures
4.1
Action management
Purpose
Chairperson
Attendees
Set remainder of Irving Treviño
Team Chiefs
scope every
single day
Deliver reports, Arturo Manrique Irving Treviño,
costs reports
Team Chiefs
Implementation








Verify that the design meets the key business objectives and technical.
Validate both LAN and WAN and their devices.
Check that the ISP provides the service agreed.
Identify bottlenecks or connectivity problems.
Test the network redundancy.
Analyze the effects on performance if there are failures in the network link.
Determine the performance optimization techniques to meet the objectives.
Identify any risks that may prevent the application and determine a
contingency plan.
The Technology Development Department is in charge of fulfilling these tasks,
working along with the Technical Team.
Operation


In this environment, the network is considered live and performs all the tasks
it has been designed to accomplish.
The technical team monitors the performance of the network and systems of
the company, ensuring that everything runs according to the project
objectives.
11
Irving Treviño
Project Manager NetCom
End of document–Project Management Plan
12
13