Project charter on

VOIP- MPLS based voice data Networking of IIM

Software Project Management- Term Project

Indian Institute of Management, Lucknow

Submitted to

Prof. Pradeep Kumar

By

Group No: 9 - GMP 11

Members
Gurtej ()

Nilesh Zope (11030)

P Barathy (11031)

Pawan Kumar (11033)

1|Page
 TABLE OF CONTENTS

1. Introduction…………………………………………………………….3

2. Project Management Approach……………………………….3

3. Scope of the Project………………………………………………….4

4. Milestones .…………………………………………………………………4

5. Role and responsibilities………………………………………….5

6. Cost Management Plan……………………………………………..7

7. Approximate cost estimation…………………………………..8

8. Change management plan………………………………………..9

9. Communication Plan………………………………………………..9

10. Training Plan…………………………………………………………….9

11. Process of testing and certification……………………10

12. Work Breakdown structure……………………………………11

INTRODUCTION

2|Page
 When computer networking technology was developed, it was based on Packet
Switched Networks (PSNs). Instead of dedicating a circuit of a predetermined
bandwidth to two endpoints, packets are sent with little messages inside as each party
has something to convey. This utilizes the bandwidth much more effectively. Instead of
slicing it up into little pieces that are reserved but not being used half of the time, it is all
consolidated in one big pipe that is only used when data actually needs to be sent. As
the computer revolution evolved and the Internet grew exponentially so did the market
for PSN technology products. This caused prices to fall by orders of magnitude.

As high speed wide area networks (WANs) became more affordable and Voice
over IP technology developed to become a commercial product. Thanks to standards by
the organizations like the ITU and IETF. It has led to modernize high speed data
connections between offices and inter-office phone service over these links. Also many
Internet Telephony Service Providers (ITSPs) started selling low cost long distance
service over the Internet.

This project aims at providing a voice data network to connect IIM Lucknow and
IIM Noida campus on MPLS and VOIP technology through BSNL owned fiber and
wireless Campus Area Network.

PROJECT MANAGEMENT APPROACH

This project will be sponsored by the administration of IIM Lucknow and

monitored by a team of representatives from each IIM. The complete project team will
consist of 5 members from each IIM for executing the tasks of Planning of network, On
site coordination for equipment installation and configuration, user integration, testing
and documentation. The responsibility of termination of OFC from BSNL point of
presence (POP) will be of JTO, BSNL of respective region. The installation and
configuration of networking equipment, Cat 6 structure cabling, and last mile
connectivity to the IP telephones and data points will be executed by HCL info systems.
The IIM system administrator will be responsible for the integration of application
servers, configuration of IPS/IDS, antivirus up gradation, creation of voice directory and
e mail Id for users and maintenance of internal network connectivity. Onsite training will
be provided by the representatives of HCL and BSNL to the IIM maintenance team to
address the faults in future.

SCOPE OF THE PROJECT

3|Page
 The scope of this project is to create a voice data intra network to connect IIM
Lucknow and IIM Noida. This network will support voice with VOIP technology and the
data will be transferred through Multi-Protocol Label Switching (MPLS) technology.
Between the states the connection will be established by the BSNL owned Fibers and
the connectivity inside IIM campuses will be through either by the of Fibers owned by
the sponsors or through Wireless connectivity and at places where redundancy or more
number of connections required it will be through the combination of both.

The last mile delivery on wireless is typically structured with one or more
repeaters serving the surrounding customers which need LOS or Near LOS (NLOS) to a
repeater. In order to account for rain fade and get better range each repeater in the
system has a one watt amp to boost the transmit and receive signals. For the repeater
antennas 8dBi Omnis are chosen. These seemed to be a good balance between gain
and a radiation pattern which wasn't too flat. In cases where there is one CPE site way
off by itself, it would be preferable to use an existing repeater if possible. There are
variations on this scheme where the CPE sites all talk to each other using 802.11b "ad
hoc" mode and or a meshing protocol, but the available bandwidth typically goes down
quite a bit and eventually a repeater will be needed somewhere to get back to the
backbone. 

Induction of this project will provide dedicated, secured and uninterrupted

communication facilities between both the IIMs. It will keep the Management, professors
and students directly linked and enhance the process of knowledge sharing also
improve the competency of the users. It will have its massive advantage on audio video
conferencing facilities which will be a blessing to the students and faculty to reduce the
distance between the knowledge seekers. Financially, this self-owned network will
reduce a huge amount of expense which otherwise will be paid to various service
providers who extend these communication facilities.

MILESTONES

The project may be divided into 4 phases.

Phase 1:

 Discussion and finalization of user requirement by BSNL, HCL and IIM

 Site survey to assess the feasibility of achieving user requirement by the
respective service provider
 Design of overall network structure, Power resources layout and cost estimation

4|Page
  Formation of teams, clarification of roles and responsibilities, finalization of rules
and regulations and drafting of complete execution plan.

Phase 2:

 Completion of procurement of fiber(OFC), equipment, software and VOIP

licenses
 Laying of fibers by BSNL from Point of Presence (POP) to the campus
 Erection of BTS (Base Transmission station) and CPE (Customer Premises
Equipment) for campus connectivity
 Training of project execution team on respective technology

Phase 3:

 Installation of STM by BSNL

 Installation and configuration of networking equipment by HCL
 Provision of main and stand by Power resources by IIM and its integration
 Integration of application servers and services

Phase 4:

 Extension of last mile connectivity

 Creation of e mail ids and voice directory
 Demonstration to users on new services and procedures
 Documentation of project activities, specifications and compilation of connectivity
data base with relevant diagrams and pictures
 Testing and certification

ROLES AND RESPONSIBILITIES

Project
manager

BSNL JTO
Site coordinator HCL area
LUCKNOW &
IIM L & N Manager
Noida

Supervisor Supervisor Supervisor Supervisor User Supervisor

Networking Documentation Resource Mgt integration Cost Mgt

Portfolio Name Responsibilities Reports to

5|Page
 Project Manager Will be the overall in charge The Project Control
for all activities related to the Board. IIM
project.
Site coordinator IIM L Monitor and control activities Project Manager
& at respective IIM as per the
Site coordinator IIM N instructions of Project
manager
BSNL Junior Coordinates Technical and DGM, BSNL:
Technical Officer administrative activities related In Liaison with site
to BSNL. coordinator. Answerable
to Project Manager
HCL Area Manager Responsible for procurement, Manager HCL.
staffing of HCL on this project Answerable to Project
and overall control on the Manager.
project
HCL Site Engineers- Responsible for Equipment HCL Area Manager &
IIML &IIM N installation, configuration and IIM site coordinator
all technical activities at the
site
System Administrator For the local configuration of Site coordinator. Works
application servers and design in Liaison with HCL site
of security requirements engineer
Supervisor Responsible for Site coordinator
(Documentation) documentation of project
activities, technical details,
agenda and minutes of PMG
and correspondences
Supervisor Responsible for the physical Site coordinator
(Networking) networking plan, design,
establishing connectivity and
Maintenance Hardware and
fault rectification
Supervisor Plans and monitors Site coordinator
(Cost management) expenditure. Prepares CPI
and SPI. Appraises PM and
sponsor. Proposes budgetary
changes and decisions.
Negotiates with service
provider and does payments.
Supervisor Collects the data from user for Site coordinator
(User integration) creating user profiles and Ids.
User integration process and
customer handling on Voice
data service requirements
from users
Supervisor In charge for inventory Site coordinator

6|Page
 (Resource Mgt) management, transportation
forecasting additional
demands, handling warranty
clause, repair and
replacement etc

COST MANAGEMENT PLAN

The Project Manager will be responsible for managing and reporting on the
project’s cost throughout the duration of the project. The Project Manager will present
and review the project’s cost performance during the monthly project status meeting.
Using earned value calculations, the Project Manager is responsible for accounting for
cost deviations and presenting the Project Sponsor with options for getting the project
back on budget. All budget authority and decisions, to include budget changes, reside
with the Sponsor, the IIM management.

Work started on work packages will grant that work package with 50% credit;
whereas, the remaining 50% is credited upon completion of all work defined in that work
package. Costs may be rounded to the nearest Rupee and work hours rounded to the
nearest whole hour.

Cost and Schedule Performance Index (CPI and SPI respectively) will be
reported on a monthly basis by the Project Manager to the Project Sponsor. Variances
of 10% or +/- 0.1 in the cost and schedule performance indexes will change the status
of the cost to yellow or cautionary. These will be reported and if it’s determined that
there is no or minimal impact on the project’s cost or schedule baseline then there may
be no action required. Cost variances of 20%, or +/- 0.2 in the cost and schedule
performance indexes will change the status of the cost to red or critical. These will be
reported and require corrective action from the Project Manager in order to bring the
cost and/or schedule performance indexes back in line with the allowable variance. Any
corrective actions will require a project change request and be must approved by the
CCB before it can be implemented.

Earned value calculations will be compiled by the Project Manager and reported
at the monthly project status meeting. If there are indications that these values will
approach or reach the critical stage before a subsequent meeting, the Project Manager
will communicate this to the Project Sponsor immediately.

APPROXIMATE COST ESTIMATION

7|Page
 Nomenclature
Amount
(Equipment/ Service) Specification Provided by

OFC cost from POP to Single mode 24 25,00,000.00

Campus core fiber
Cost of BTS and CPEs 35,00,000.00

Cisco Access routers, L3 12000 ARS series HCL Info 2,85,00,000.00

Switches, L2 switches, for access, 3500 XL Systems
DSLAMs, AVGs, Radware series of L2
IDS IP phones and analog switches,3550/3770
phones. series L3 s/w
7420,7490,7460
model of IP phones
Bandwidth allocation Qty 2000 licenses Project control 50,00,000
Expenditures, Cost of VOIP IOS, Cat OS, NX- Board
licenses and procurement of OS operating
software systems
Cost of structure cabling and Approximately 12 HCL info 6,00,000.00
end connectors including Kms inside the systems
labour charges building and road
crossing.
Cost of accessories like Fiber LX, ZX, TX series HCL info 15,00,000.00
termination box, Pig tails, for SFPs, 2’ 3 slab systems
SFPs, FDF and switch racks for s/w and
mounting Racks UPS
Project implementation & Complete HCL info 30,00,000.00
training contract with HCL implementation and systems
configuration, 7
days training
Procurement of test OTDR, IIM- Project 4,50,000.00
equipment Light source and Manager
splicing Kits
Annual Maintenance Contract Payable biannually.
To BSNL and 10,00,000.00
for both OFC and Networking HCL
Equipment
AMC charges for power For DG set, UPS, To Cummins 3,00,000.00
equipment Stabilizers, Float
chargers air
conditioners
Total 4, 63,50,000.00

CHANGE MANAGEMENT PLAN

8|Page
 All project and subsidiary management plans will be reviewed and approved by
the project sponsor. All funding decisions will also be made by the project sponsor. Any
delegation of approval authority to the project manager should be done in writing and be
signed by both the project sponsor and project manager. The project team will be a
matrix in that team members from each organization continue to report to their
organizational management throughout the duration of the project. The project manager
is responsible for communicating with organizational managers on the progress and
performance of each project resource.

COMMUNICATION PLAN

The Project Monitoring Group (PMG) will be formed with the representatives from
BSNL, HCL and both the IIMs. PMG will assemble on third Friday of every month to
assess progress & status. The agenda points will be forwarded 3 working days in
advance by the site coordinators. The minutes of meeting will be put up to the Project
Control Board on the second working day after the meeting and status report of
previous meeting will be put up after 15 Days of the PMG meeting

The Media of communication will be classified into the forms of E mail, in person
telephonic and letters in hard copy with dispatch details etc. The technical and
administrative complications may be addressed on priority through audio video
conferencing on internet. However the event report and the decisions taken on such
conferences should be documented without any lapse.

The norms in this regard will be decided by the project Manager and further
instructions will be given to the supervisor (Documentation). Site coordinators to ensure
standardized filing system in soft and hard as per the differentiation of verticals.

TRAINING PLAN

The technical team involved in this project will require more experience with
setting up different configurations of radios, and trouble shooting. This would involve
learning about the different menus/tools available to test and monitor the network.

9|Page
 The Technicians need a deeper understanding of IP addressing, and how to put
subnets together and add static routes for them. Because the Cisco radios do bridging
well but apparently do less well at routing, the network is an 'interesting' combination of
bridging and routing. If the network configuration becomes broken during an upgrade
then they would most likely be the ones to drive to the remote sites and fix it using a
laptop and serial cable. They would be more prepared to handle these tasks if they had
a better understanding of networking.

Last but not least they need more experience with the UNIX command line
environment. There are several reasons for this. Windows has been found to not always
be reliable platform to trouble shoot from so the laptops tend to be set up to also boot
Linux. Most of the useful tools that are used for trouble shooting are Unix/Linux based
for similar reasons. Several of the routers in use are Unix/Linux based and to set them
up properly one needs to know the local editor and command line syntax. Also the
knowledge in this area would come in handy when coordinating work with Druknet (if
that's needed) since Druknet has several Unix based servers. Other routers like Cisco's
have environments that were derived from UNIX systems so that knowledge should
transfer easily to these platforms as well.

The complete syllabus for training should be put up in writing and concurred by
the users. The project coordinator of IIM will short list the candidates to undergo training
as per the qualifications required. BSNL will provide training for 3 working days and
HCL will train on equipment and configuration for 7 working days. End of training, all
participants will be provided with the certificate from HCL info systems.

PROCESS OF TESTING AND CERTIFICATION

The process of testing will address the following aspects before certification.

1. The suitability of overall system design including software and hardware to

meet the purpose.
2. Can the equipment meet the requirements of BT as well as the DIT?
3. Reliability of the router, switches, security modules, customer premise
gateways and other equipment installed.
4. Functionality test for security, authentication, privacy, Least Cost Routing
(LCR), call flow monitoring, call tracing, Test call facility etc.
5. Simulation of faults and system response on standard rectification
procedures.
6. Checking of alarms and warning system

10 | P a g e
 7. Simulation checks for functionality of IPS and IDS and auto up gradation of
antivirus.
8. Power consumption and reliability of the power supplies, lightning arresters,
captive supply, UPS, power stabilizers, earthing parameters and suitability of
solar power supplies employed at most sites.
9. System flexibility and capacities. Is it easily scalable and flexible enough to
introduce new services or changes if we want to?
10. Cable layout discipline and display of standard operating procedures at
appropriate locations.
11. Feasibility for Installation and testing methods for the hardware expansion of
the project in future.
12. Accuracy of documentation of port utilization details of L2 switches, DSLAM,
Analog Voice gateways and VLAN details.
13. Feedback of people using this system as compared to using the traditional
systems.
14. Completion of training and testing of competency of technicians
15. Scrutinizing of project execution documents for any lapse in procedure.

The testing will be carried out in the presence of BSNL, HCL and IIM representatives
and the draft format of completion certificate will be concurred by all before making the
final documents.

WORK BREAKDOWN STRUCTURE

1. Project VoIP and Intranet for IIML & IIM Noida campus

1.1. Initiation

1.1.1. Meet with BSNL, HCL and IIM representatives for kick-off meeting
1.1.2. Define project charter
1.1.2.1. Define specific functionality requirement for both IIM
1.1.2.2. Define overall system requirements
1.1.3. Completion of site survey for requirement analysis
1.1.4. Define scope statement for Project VoIP & Intranet
1.1.5. Determine appropriate resource allocation & Cost
1.1.6. Discuss project implementation structure
1.1.6.1. Determine potential risks
1.1.7. Define exit strategy in emergency situation
1.1.8. Sign-off initiation phase

11 | P a g e
 1.2. Planning
1.2.1. Create team contracts with BSNL and HCL
1.2.2. Finalize stakeholder register & strategy
1.2.2.1. Analyze and distribute to appropriate teams
1.2.3. Create work breakdown structure for various teams
1.2.4. Create cost baseline
1.2.4.1. Analyze required OFC, networking and power resources and
associated cost
1.2.4.1.1. Analyze and approximate implementation cost
1.2.4.1.2. Analyze and approximate customer service cost during and
after implementation
1.2.4.2. Analyze Tail plant and software costs
1.2.4.3. Analyze license cost of VoIP
1.2.5. Create Network diagram with mile stones, communication plan,
change management plan and Staff management plan
1.2.6. Generate a resource usage report
1.2.7. Generate an issues and assumptions log
1.2.8. Sign-off planning phase

1.3. Executing
1.3.1. Create a roles and responsibilities assignment matrix
1.3.2. Meeting with BSNL for POP allocation and OFC termination
1.3.2.1. Schedule for STM installation and Integration
1.3.3. Create a milestone check report
1.3.4. Meeting with HCL for Installation & configuration of access networking
components
1.3.4.1. Coordinate HCL & IIM employees/teams for installation of Access
router, L3,L2 switches, DSLAM and AVGs as per site survey
1.3.4.2. Installation of power resources
1.3.4.3. CAT 6 Structure cabling at IIMs
1.3.4.4. Completion of Initial configuration of hardware and creation of
VLANs
1.3.4.5. Collection of user data for ID creation and design telephone
directory
1.3.4.6. Creation of user profiles
1.3.4.7. Installation & configuration of IPS & IDS
1.3.4.8. Deployment of IP telephones and PC connectivity
1.3.4.9. Train employees about new system
1.3.4.10. Demonstration to users for voice data services and utilities
1.3.4.11. Create and review team reports based on installation success
1.3.5. Test new system for functionality and security

12 | P a g e
 1.3.6. Sign-off executing phase

1.4. Monitoring and Controlling

1.4.1. Create progress reports (recurring task)
1.4.2. Create change request form
1.4.3. Update any possible deliverables that needs to be altered (recurring
task)
1.4.3.1. Update budget
1.4.3.2. Update project charter
1.4.3.3. Update scope statement
1.4.3.4. Update list of prioritized risks
1.4.3.5. Update WBS/Gantt chart
1.4.3.6. Create/update project closeout checklist
1.4.3.7. Sign-off monitoring and controlling phase

1.5. Closing
1.5.1. Update project website with all final and up to date deliverables
1.5.2. Create and Review Lessons Learned
1.5.3. Analyze project closeout checklist
1.5.4. Clear observations of testing report
1.5.5. Create completion certificate by the representatives from BSNL, HCL
and IIM representatives
1.5.6. Hand over/ Taking over certificate of equipment and documents
1.5.7. Sign-off closing phase

13 | P a g e