PROJECT REPORT

PROJECT NAME: IMPLEMENTATION OF BANK DATA CENTERS AND NETWORK

INFRASTRUCTURE REDESIGN

DEPARTMENT: NETWORK/ IT

PREPARED BY
Document Owner(s) Project/Organization Role

Project Management Office The HATS Bank

Confidential

Project Report The HATS Bank

Last printed on 3/23/2004 11:48:00 AM

 Project Report

TABLE OF CONTENTS
DEVELOP PROJECT CHARTER.....................................................................3

STAKEHOLDER ANALYSIS ........................................................................10

PROJECT SCOPE MANAGEMENT PLAN.......................................................11

COLLECT REQUIREMENTS .......................................................................17

PROJECT SCOPE STATEMENT DOCUMENT .................................................25

CREATE WBS AND WBS DICTIONARY........................................................37

PROJECT TIME MANAGEMENT PLAN .........................................................63

ACTIVITY DEFINITION..............................................................................68

ACTIVITY ATTRIBUTES ............................................................................69

PROJECT NETWORK DIAGRAM ...............................................................104

ACTIVITY DURATION ESTIMATES ............................................................105

RESOURCE CALENDAR ..........................................................................107

RESOURCE WORK CALENDAR 108

PROJECT SCHEDULE 109

Confidential Page 2 3/13/2017

 Project Report

DEVELOP PROJECT CHARTER

PROJECT CHARTER VERSION CONTROL
Version Date Author Change Description

1.0 5th April 13 Tariq Khanani Document created

2.0 20thApril 13 Afnan Memon, Sameem Document Updated, Roles & Responsibilities
Subhani updated

2.0 20thApril 13 Tariq Khanani, Hassan Document Approved

Ahmed

PROJECT PURPOSE
The objective of our project is to build agile and flexible data centers and connect them in a way that
maximizes the up-time for the transactions that will be followed, minimizing the overall down-time in case
of disaster events.

PROJECT EXECUTIVE SUMMARY

The HATS Bank was facing serious network and data integrity issues for the past few months. Root cause
of which was identified to be the overall information infrastructure. The project therefore was initiated to
revamp the entire data storage, retrieval and network connectivity infrastructure to offer more reliability,
security and failure recovery options, thus improving customer satisfaction by minimizing downtime and
ensuring proper customer data handling and security.

Confidential Page 3 3/13/2017

 Project Report

PROJECT OVERVIEW
The HATS Bank was losing customer trust due to recent network failures and inconsistencies in customer
data and timely execution of customer requests. This could lead to customer base loss and thus ending up
in revenue loses for bank. Project was needed to improve the situation and bring bank and all its branches
and ATM network across the country to track by improving uptime and ensure data integrity and security.

PROJECT SCOPE
GOALS AND OBJECTIVES
Goals Objectives

The completion of the project must provide

1. Implement a distributed architecture for the overall network of
99% up-time to the services of HATS Bank
the Bank
(Pvt.) Ltd.
2. Implement efficient back up restoration techniques by having
redundant data servers that are running in parallel to keep the
down time to its minimum
Achieve maximum customer satisfaction by
1. Implement fool-proof security protocols including encryption
providing data security and integrity to the
techniques and robust firewalls so as to achieve maximum data
customers data.
security and integrity
Protect the banks image and reputation
1. Implement distributed data architecture to speed up the rate of
transactions that will be processed in a certain period of time.
This architecture will also help to ensure maximum data
availability and maximum up-time and response time of the
nodes

Confidential Page 4 3/13/2017

 Project Report

PROJECT DELIVERABLES
Milestone Deliverable

1. Milestone 1 Build data centers all over the country to improve the up-time and response
time of transactions
Build redundant data centers to ensure minimum down time and efficiency in
back up plan
2. Milestone 2 Build a distributed network architecture for the Banks overall operations to
be processed
3. Milestone 3 Develop distributed database architecture for the Banks overall data
management and availability.
4. Milestone 4 Develop a robust security infrastructure.

DELIVERABLES OUT OF SCOPE

The location where these Data centers will be built is behind the Project scope.
Vendors of the devices and materials that constitute a complete Data center are also behind the
Project scope.
The Quality of service of Internet, as it is served by some internet provider, is also behind the
overall scope of this Project.
The quality of software that the bank is using currently is also behind the consideration of this
Project Scope.

PROJECT CONDITIONS

Confidential Page 5 3/13/2017

 Project Report

PROJECT ASSUMPTIONS
METHODOLOGY
The project will be completed using tools and techniques prescribed by the Bank methodology. The
details of which would be taken from the organizational process assets that include the policies and
procedures approved by the Banks Senior Management.
PERFORMANCE
The traditional styles of measuring performance, where users enter data into a screen, press enter or
a function key wait for a response and measure the time to complete the function is no longer
applicable for client/server applications.
The Bank recommends that these be replaced by modified performance estimates that reflect the
client/server model.
USER ACCEPTANCE TESTING
Bank will supply the necessary equipment, place and work force to the project team to assist with
the preparation and execution of the Acceptance Test.
BETA TESTING
All approved vendors will provide 5 days per week, 16 hours per day on-call support to the project
development team during the beta test period.
STAGING RESPONSIBILITIES
The Banks staging responsibilities are limited to the unpacking of hardware units, the installation,
configuration and testing of the software, and repacking the hardware units ready to be shipped to
the deployment sites.

PROJECT CONSTRAINTS
CONVERSION
Conversion of data, either automated or manual, is not included. The Windows or pilot system will
be replaced not converted.

Confidential Page 6 3/13/2017

 Project Report

PROJECT TEAM ORGANIZATION PLANS

Project Team Role Responsibilities

Project Manager To Facilitate and guide the Information Technology and Electrical Services in such a way
that both would work simultaneously and project could be delivered on time, within the
budget in accordance with the approved scope of the project. Maintain the specified
standards of quality with keeping an eye on risks associated with the project.

Team Lead (IT) To Facilitate and guide the Information Technology team in such a way that they work
simultaneously. And to Maintain the specified standards of quality.

Team Lead To Facilitate and guide the Electrical team in such a way that they work simultaneously.
(ELECTRICAL) And to Maintain the specified standards of quality.

Design Engineer Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs), for the
(Electrical) Electrical part of the project.

IMPLEMENTATION Implementation of the approved High level diagrams (HLDs) and Low Level diagrams
ENGINEER (LLDs), for the Electrical part of the project.
(ELECTRICAL)

Design Engineer (IT) Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs) for the
Electrical part of the project.

Implementation Implementation of the approved High level diagrams (HLDs) and Low Level diagrams

Confidential Page 7 3/13/2017

 Project Report

Engineer (IT) (LLDs), for the IT related part of the project.

Network Engineers Implementation/ revamping of the network all over the region.

Construction Team Construct all the data centers along with the backup data centers as per the
specifications & standards specified.

Security analysts Analyze the current security threats and assist in modifying the security architecture.

Ethical Hackers Implementing robust security architecture to ensure maximum integrity and
confidentiality for customers data.

Client Services Team Identifying the new customer requirements and having an insight onto the feedback
gained from customers. Ensuring that the customers are always happy.

Audit Team Internal audit for the compliance of defined policies and procedures.

QA/ AC Team Ensure assurance of validation of quality of the completed tasks. Implement controls to
reduce the deviation, if any, has occurred.

MAJOR STAKEHOLDERS
The HATS Bank 0900-78601
Customers
Interbank network and switch service providers
o MNET
o 1 Link 11 11 1LINK (15465)
o Orix 111 24 24 24

Confidential Page 8 3/13/2017

 Project Report

APPROVALS
Prepared by __________________________________

Project Manager

Approved by__________________________________

Project Sponsor

__________________________________

Executive Sponsor

__________________________________

Client Sponsor

STAKEHOLDER ANALYSIS

Confidential Page 9 3/13/2017

 Project Report

PROJECT SCOPE MANAGEMENT PLAN

Confidential Page 10 3/13/2017

 Project Report

VERSION HISTORY
Version Date Author Change Description

1.0 15th April 13 Tariq Khanani Document created

INTRODUCTION
The Scope Management Plan provides the scope framework for this project. This plan documents the
scope management approach; roles and responsibilities as they pertain to project scope; scope definition;
verification and control measures; scope change control; and the projects work breakdown structure. Any
project communication which pertains to the projects scope should adhere to the Scope Management
Plan.

The objective of our project is to build agile and flexible data centers and connect them in a way that
maximizes the up-time for the transactions that will be followed, minimizing the overall down-time in case
of disaster events.

SCOPE MANAGEMENT APPROACH

Since this project was identified and initiated internally, scope management majorly will rely on input from
project sponsors which are Bank owners. However, the responsibility of keeping the scope under control
will be of Project Manager. The scope for this project is defined by the Scope Statement, Work Breakdown
Structure (WBS) and WBS Dictionary. The Project Manager, Sponsor and Stakeholders will establish and
approve documentation for measuring project scope which includes deliverable quality checklists and work
performance measurements. Proposed scope changes may be initiated by the Project Manager,
Stakeholders or sponsors. All change requests will be submitted to the Project Manager who will then
evaluate the requested scope change. Upon acceptance of the scope change request the Project Manager

Confidential Page 11 3/13/2017

 Project Report

will submit the scope change request to the Change Control Board and Project Sponsor for acceptance.
Upon approval of scope changes by the Change Control Board and Project Sponsor the Project Manager will
update all project documents and communicate the scope change to all stakeholders. Based on feedback
and input from the Project Manager and Stakeholders, the Project Sponsor is responsible for the
acceptance of the final project deliverables and project scope. Project manager will have authority to take
necessary measures to introduce any essential changes or improvements as the project executes.

ROLES AND RESPONSIBILITIES

The Project Manager, Sponsor and team will all play key roles in managing the scope of this project. As
such, the project sponsor, manager, and team members must be aware of their responsibilities in order to
ensure that work performed on the project is within the established scope throughout the entire duration of
the project. The table below defines the roles and responsibilities for the scope management of this
project.

Confidential Page 12 3/13/2017

 Project Report

Role Responsibilities

Sponsor - Approve or deny scope change requests as appropriate

- Evaluate need for scope change requests
- Accept project deliverables
Project Manager - Measure and verify project scope
- Facilitate scope change requests
- Facilitate impact assessments of scope change requests
- Organize and facilitate scheduled change control meetings
- Communicate outcomes of scope change requests
- Update project documents upon approval of all scope changes
Team Lead (IT) - To assessing and analyzing all scope changes related to IT infrastructure
- To manage scope boundaries related to Network, security, data storage.
Team Lead (Electrical) - All change requirements related to electrical infrastructure of project,
including power supplies, backup and restoration, fault management will be
handled by Electrical Lead.
- Propose electrical design suggestions, analyze and asses suggestions from
team members, and approve changes.

SCOPE DEFINITION
The HATS Bank was facing serious network and data integrity issues for the past few months. Root cause
of which was identified to be the overall information infrastructure. The project therefore was initiated to
revamp the entire data storage, retrieval and network connectivity infrastructure to offer more reliability,
security and failure recovery options, thus improving customer satisfaction by minimizing downtime and
ensuring proper customer data handling and security.

Hence, an internal project was initiated to save bank reputation and increase customer satisfaction.
Requirement therefore were provided by related IT department and while proposing the solutions to faced
challenges, inputs from people handling power needs of branches and ATM locations across the country.

Confidential Page 13 3/13/2017

 Project Report

Number of datacenters and bandwidth requirements was finalized by gathering data related to operational
branches and ATMs and the consumer base utilizing these facilities. Customer trends were also considered
to decide maximum thresholds and performance benchmarks.

SCOPE VERIFICATION
As this project progresses the Project Manager will verify interim project deliverables against the original
scope as defined in the scope statement, WBS and WBS Dictionary. Scope will be verified for each regional
data centre and the connectivity between them. Quality requirements will be strictly considered to ensure
product quality being met during the implementation.

Upon reaching a milestone or completion of a deliverable, Project Manager will verify that the scope meets
the requirements defined in scope. If deliverable passes verification, project manager and sponsor will
meet for formal acceptance the deliverable.

There will be a data centre acceptance document duly signed by sponsor and project manager to accept
that data centre has been completely delivered in functional state and its operation efficiently as per
quality and security requirements.

SCOPE CONTROL
The Project Manager and the project team will work together to control of the scope of the project. The
project team will leverage the WBS Dictionary by using it as a statement of work for each WBS element.
The project team will ensure that they perform only the work described in the WBS dictionary and generate
the defined deliverables for each WBS element. The Project Manager will oversee the project team and the
progression of the project to ensure that this scope control process if followed.

Leads of IT and Electrical will be responsible to control scope in their areas and they will be expected to
propose any action to control scope if it is going out of the line.

Confidential Page 14 3/13/2017

 Project Report

If a change to the project scope is needed the process for recommending changes to the scope of the
project must be carried out. Any stakeholder involved in the Project can identify changes.

Changes will be classified and prioritized as per the criteria defined in the Corporate Change Control
System:

- Impact (Major, Medium, Minimal)

- Severity (High, Medium, Low)

All change requests must be submitted to the Corporate Change Control System, using the standard
Change Request Form. The Project Manager will then review the suggested change to the scope of the
project. The Project Manager will then either deny the change request if it does not apply to the intent of
the project or convene a change control meeting between the project team and Sponsor to review the
change request further and perform an impact assessment of the change. If the change request receives
initial approval of the Project Manager and Sponsor, then the Project Manager will then formally submit the
change request to the Change Control Board. If the Change Control Board approves the scope change the
Project Sponsor will then formally accept the change by signing the project change control document.

Confidential Page 15 3/13/2017

 Project Report

Upon acceptance of the scope change by the Change Control Board and Project Sponsor the Project
Manager will update all project documents and communicate the scope change to all project team
members stakeholders.

SPONSOR ACCEPTANCE
Approved by the Project Sponsor:

_______________________________________________ Date:________________________

<Project Sponsor>

COLLECT REQUIREMENTS
PROJECT REQUIREMENTS DOCUMENT

Confidential Page 16 3/13/2017

 Project Report

DOCUMENT REVISION HISTORY

Version Date Changes Updated By
1.0 4/20/13 Original document Afnan Memon
1.0 4/22/13 Revised: modified Tariq Khanani

PURPOSE OF THE DOCUMENT

In order to meet the needs and expectations of the customers of HATS bank it is imperative that the HATS
Bank project team has a clear and defined set of business requirements to follow. The purpose of this
document is to outline and prioritize the functional and non-functional requirements for the
implementation of Bank Data Centers and network infrastructure redesign.

PROJECT OBJECTIVE
The objective of our project is to build agile and flexible data centers and connect them in a way that
maximizes the up-time for the transactions that will be followed, minimizing the overall down-time in case
of disaster events.

PROJECT SCOPE
As we discussed earlier, the ultimate goal of the project, for the HATS Bank, will be to achieve a minimum
amount of down time plus having a maximum amount of up-time in terms of the transaction that will be
processed. Previously, there used to be a concept of conventional banking but now the era of modern

Confidential Page 17 3/13/2017

 Project Report

banking has already emerged and the clients will turn to your competitors if they are not getting anything
that will not satisfy them.

In order to sustain and achieve a good reputation in the client audience, the proposed solution will serve as
a backbone to the organization, by improving the up-time/ response time of transactions by 99%. In order
to achieve this goal, the project has set a number of its objectives that will eventually help in achieving
greater customer satisfaction plus reputation.

The Primary objective is to build agile and flexible data centers. As we are a bank named as THE HATS
bank, we require data centers all over the country so as to meet the requirements of the increasing
audience of our clients. The main purpose of these data centers is to ensure the necessary backend
environment for making the stored data, always accessible online at any time of the day and night no
matter wherever you are. This includes providing a reliable infrastructure for running the routine IT
operations and setting high security standards for keeping the stored information intact all the time. The
business that we are doing is highly critical, as it involves a big client audience to be served, and it must
ensure high level of customer satisfaction so we cannot tolerate any such down time in case of
transactions. We also want to ensure our clients, if incase of any disasters, that the proposed solution will
exhibit a zero delay backup restoration with the help of redundant nodes, distributed architecture and load
balancers/backup power. They are responsible for keeping the data stored on the server machines safe.
Special security devices that will be added are meant to protect the servers against hacking attacks and
viruses.

The proposed solution will implement a distributed architecture for the data/ network, so that even if a
single node which is responsible for transactions within a region goes down, there will always be other
nodes with which we can connect and ensure our transactions are never suffered. There will also be
redundant servers that will be implemented and such servers will be running in parallel with the
transactional servers so as to achieve load balancing and zero level of down time in case of failures.

Confidential Page 18 3/13/2017

 Project Report

ASSUMPTIONS
METHODOLOGY
The project will be completed using tools and techniques prescribed by the Bank methodology. The
details of which would be taken from the organizational process assets that include the policies and
procedures approved by the Banks Senior Management.

PERFORMANCE
The traditional styles of measuring performance, where users enter data into a screen, press enter or
a function key wait for a response and measure the time to complete the function is no longer
applicable for client/server applications.
The Bank recommends that these be replaced by modified performance estimates that reflect the
client/server model.

USER ACCEPTANCE TESTING

Bank will supply the necessary equipment, place and work force to the project team to assist with
the preparation and execution of the Acceptance Test.

BETA TESTING
All approved vendors will provide 5 days per week, 16 hours per day on-call support to the project
development team during the beta test period.

STAGING RESPONSIBILITIES
The Banks staging responsibilities are limited to the unpacking of hardware units, the installation,
configuration and testing of the software, and repacking the hardware units ready to be shipped to
the deployment sites.

Confidential Page 19 3/13/2017

 Project Report

CONSTRAINTS
CONVERSION
Conversion of data, either automated or manual, is not included. The Windows or pilot system will
be replaced not converted.

MAJOR PROJECT MILESTONES

Milestone Deliverable

1. Milestone 1 Build data centers all over the country to improve the up-time and response time of
transactions
Build redundant data centers to ensure minimum down time and efficiency in back up plan
2. Milestone 2 Build a distributed network architecture for the Banks overall operations to be processed
3. Milestone 3 Develop distributed database architecture for the Banks overall data management and
availability.
4. Milestone 4 Develop a robust security infrastructure.

PROJECT ROLES AND RESPONSIBILITIES

Project Team Role Responsibilities

Project Manager To Facilitate and guide the Information Technology and Electrical Services in such a way that both
would work simultaneously and project could be delivered on time, within the budget in accordance
with the approved scope of the project. Maintain the specified standards of quality with keeping an

Confidential Page 20 3/13/2017

 Project Report

eye on risks associated with the project.

Team Lead (IT) To Facilitate and guide the Information Technology team in such a way that they work
simultaneously. And to Maintain the specified standards of quality.
Team Lead To Facilitate and guide the Electrical team in such a way that they work simultaneously. And to
(ELECTRICAL) Maintain the specified standards of quality.

Design Engineer Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs), for the Electrical part
(Electrical) of the project.

IMPLEMENTATION Implementation of the approved High level diagrams (HLDs) and Low Level diagrams (LLDs), for
ENGINEER the Electrical part of the project.
(ELECTRICAL)

Design Engineer (IT) Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs) for the Electrical part
of the project.
Implementation Implementation of the approved High level diagrams (HLDs) and Low Level diagrams (LLDs), for
Engineer (IT) the IT related part of the project.

REQUIREMENTS
The requirements should be prioritized with respect to the importance of the customers so that the HATS
bank will not lose the trust of the customers which was due to the recent network failures and
inconsistencies in customer data and timely execution of customer requests so in order to maintain the
interest of the customers, quality requirements, human resource requirements, hardware and software
requirements, approval requirements etc should be required to fulfill the customers trust.. Requirement
priorities are defined as:

Confidential Page 21 3/13/2017

 Project Report

High The application cannot function properly without this requirement.

Medium The efficiency of the application would be greatly improved by this requirement.
Low This feature would be nice to have it.

Req. # Requirement Description Priority

1 Theft-safe data storage: Data should be secure enough to be accessible only by permitted High
viewers of data.

2 No data corruption in case of any failure (Error handling) High

Disaster proof infrastructure: Data centers should incorporate backup mechanism to ensure fail- Medium
3 safe infrastructure in case of any sort of damage to the network or devices.

4 There should be minimum occurrences of power failures and fluctuations Medium

5 Power cables & structured cables should be ISO certified Medium

Confidential Page 22 3/13/2017

 Project Report

6 High
Department should be consist of supervisors and skilled engineers

7 Storage architecture should be specially designed for distributed data persistence. Medium

8 Flexible robust networks should be comprised of multi-path connectivity between nodes using Medium
routers, switches etc.

9 Main and backup internet backbone with enough bandwidth is required to service peak consumer High
activity.

10 PCs and terminals should be configured and monitored. Medium

11 Network analysis and monitoring software, for pre-emptive detection of failures and external High
attacks.

12 Easily maintainable and replaceable Zero-delay UPS should be required for immediate power Medium
recovery.

Confidential Page 23 3/13/2017

 Project Report

13 Backup Generators to support each data center to its full capacity including Air conditioning High
systems.

14 Approval of the Project Proposal document. High

15 Budget Approval should be required. High

16 Approval of the Distributed Architecture will be required to propose. Medium

17 Approval of the human resources by the functional managers will be required to carry out this High
project.

18 Approval for the timelines should be shared among the management. High

Confidential Page 24 3/13/2017

 Project Report

PROJECT SCOPE STATEMENT DOCUMENT

VERSION HISTORY
Version Date Author Change Description

1.0 15th April 13 Tariq Khanani Document created

2.0 20thApril 13 Tariq Khanani, Afnan Memon Resource Breakdown Structure, Roles & Responsibilities
updated

PRODUCT DESCRIPTION
The objective of our project is to build agile and flexible data centers and connect them in a way that
maximizes the up-time for the transactions that will be followed, minimizing the overall down-time in case
of disaster events.
A data center or computer center is a facility used to house computer systems and associated
components, such as telecommunications and storage systems. It generally includes redundant or backup
power supplies, redundant data communications connections, data servers, environmental controls (e.g.,
air conditioning, fire suppression) and security devices.
In order to build data centers we must turn our data centers in to a flexible cloud infrastructure with the
performance and reliability to run the most demanding enterprise applications with the platform trusted by
the top data centers worldwide.

PROJECT GOALS, OBJECTIVES

GOALS

Confidential Page 25 3/13/2017

 Project Report

The below stated points will put a light on the high level goals of this Project:

The completion of the project must provide 99% up-time to the services of THE HATS Bank (Pvt.)
Ltd.

The completion of the project must provide minimum amount of down-time to the services of THE
HATS Bank (Pvt.) Ltd.

Achieve maximum customer satisfaction.

Provide data security and integrity to the customers data.

Protect the banks image and reputation.

OBJECTIVES
The below stated points will serve as the objectives of the project and such objectives will allow us to
achieve the overall goals of the Project:

Implement a distributed architecture for the overall network of the Bank.

Implement efficient back up restoration techniques by having redundant data servers that are
running in parallel to keep the down time to its minimum.

Implement fool-proof security protocols including encryption techniques and robust firewalls so as to
achieve maximum data security and integrity.

Implement distributed data architecture to speed up the rate of transactions that will be processed in
a certain period of time. This architecture will also help to ensure maximum data availability and
maximum up-time and response time of the nodes.

Confidential Page 26 3/13/2017

 Project Report

DETAILED SCOPE DESCRIPTION

As we discussed earlier, the ultimate goal of the project, for the THE HATS Bank, will be to achieve a
minimum amount of down time plus having a maximum amount of up-time in terms of the transaction that
will be processed. Previously, there used to be a concept of conventional banking but now the era of
modern banking has already emerged and the clients will turn to your competitors if they are not getting
anything that will not satisfy them.

In order to sustain and achieve a good reputation in the client audience, the proposed solution will serve as
a backbone to the organization, by improving the up-time/ response time of transactions by 99%. In order
to achieve this goal, the project has set a number of its objectives that will eventually help in achieving
greater customer satisfaction plus reputation.

The Primary objective is to build agile and flexible data centers. As we are a bank named as THE HATS
bank, we require data centers all over the country so as to meet the requirements of the increasing
audience of our clients. The main purpose of these data centers is to ensure the necessary backend
environment for making the stored data, always accessible online at any time of the day and night no
matter wherever you are. This includes providing a reliable infrastructure for running the routine IT
operations and setting high security standards for keeping the stored information intact all the time. The
business that we are doing is highly critical, as it involves a big client audience to be served, and it must
ensure high level of customer satisfaction so we cannot tolerate any such down time in case of
transactions. We also want to ensure our clients, if incase of any disasters, that the proposed solution will
exhibit a zero delay backup restoration with the help of redundant nodes, distributed architecture and load
balancers/backup power. They are responsible for keeping the data stored on the server machines safe.
Special security devices that will be added are meant to protect the servers against hacking attacks and
viruses.

Confidential Page 27 3/13/2017

 Project Report

The proposed solution will implement a distributed architecture for the data/ network, so that even if a
single node which is responsible for transactions within a region goes down, there will always be other
nodes with which we can connect and ensure our transactions are never suffered. There will also be
redundant servers that will be implemented and such servers will be running in parallel with the
transactional servers so as to achieve load balancing and zero level of down time in case of failures.

DELIVERABLES & ACCEPTANCE CRITERIA

DELIVERABLES
The project will deliver the following:

Design distributed network architecture for the Banks overall operations to be processed.

Design distributed database architecture for the Banks overall data management and availability.

Implement the distributed architecture for the Bank to conduct its services and operation to its
clients.

Build data centers all over the country to improve the up-time and response time of transactions.

Build redundant data centers to ensure minimum down time and efficiency in back up plan.

Build a cooling environment in the data centers so as to ensure that the data servers may not stop
functioning or may not get over heated.

ACCEPTANCE CRITERIA

Confidential Page 28 3/13/2017

 Project Report

The project will be a complete success once it will achieve the following criteria, this criteria will be the
indicator of success of the Project:

The up-time of the overall transactions is improved and achieves a rate of 99%.

The down time in case of disasters and power failures is reduced and kept to its minimum.

The redundant sites of the data servers are running in parallel so that load balancing must be
achieved and down time is kept at minimum.

The backup power supplies consisting of UPS and generators must be functional all the time.

PROJECT ORGANIZATION STRUCTURE

Confidential Page 29 3/13/2017

 Project Report

ROLES & RESPONSIBILITIES

Roles Responsibilities

Project Manager To Facilitate and guide the Information Technology and Electrical Services in
such a way that both would work simultaneously and project could be delivered
on time, within the budget in accordance with the approved scope of the
project. Maintain the specified standards of quality with keeping an eye on risks

Confidential Page 30 3/13/2017

 Project Report

associated with the project.

Team Lead (IT) To Facilitate and guide the Information Technology team in such a way that they
work simultaneously. And to Maintain the specified standards of quality.

Team Lead (Electrical) To Facilitate and guide the Electrical Services team in such a way that they work
simultaneously. And to Maintain the specified standards of quality.

Design Engineer Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs), for
(Electrical) the Electrical part of the project.

Implementation Implementation of the approved High level diagrams (HLDs) and Low Level
Engineer (ELECTRICAL) diagrams (LLDs), for the Electrical part of the project.

Design Engineer (IT) Design all the High level diagrams (HLDs) and Low Level diagrams (LLDs) for
the Electrical part of the project.

Implementation Implementation of the approved High level diagrams (HLDs) and Low Level
Engineer (IT) diagrams (LLDs), for the IT related part of the project.

Network Engineers Implementation/ revamping of the network all over the region.

Construction Team Construct all the data centers along with the backup data centers as per the
specifications & standards specified.

Security analysts Analyze the current security threats and assist in modifying the security
architecture.

Ethical Hackers Implementing robust security architecture to ensure maximum integrity and
confidentiality for customers data.

Confidential Page 31 3/13/2017

 Project Report

Client Services Team Identifying the new customer requirements and having an insight onto the
feedback gained from customers. Ensuring that the customers are always
happy.

Audit Team Internal audit for the compliance of defined policies and procedures.

QA/ AC Team Ensure assurance of validation of quality of the completed tasks. Implement
controls to reduce the deviation, if any, has occurred.

ASSUMPTIONS AND CONSTRAINTS

The schedules, estimates and costs related to the project are based on the assumptions and constraints
identified below. If any of these assumptions are incorrect, then the Bank reserves the right to re-estimate
both the schedule and the cost for this project.

ASSUMPTIONS
Below stated are the assumptions related to this Project:

METHODOLOGY

The project will be completed using tools and techniques prescribed by the Bank methodology. The details
of which would be taken from the organizational process assets that include the policies and procedures
approved by the Banks Senior Management.

PERFORMANCE

Confidential Page 32 3/13/2017

 Project Report

The traditional styles of measuring performance, where users enter data into a screen, press enter or a
function key wait for a response and measure the time to complete the function is no longer applicable for
client/server applications.

The Bank recommends that these be replaced by modified performance estimates that reflect the
client/server model.

USER ACCEPTANCE TESTING

Bank will supply the necessary equipment, place and work force to the project team to assist with the
preparation and execution of the Acceptance Test.

BETA TESTING

All approved vendors will provide 5 days per week, 16 hours per day on-call support to the project
development team during the beta test period.

STAGING RESPONSIBILITIES

The Banks staging responsibilities are limited to the unpacking of hardware units, the installation,
configuration and testing of the software, and repacking the hardware units ready to be shipped to the
deployment sites.

CONSTRAINTS
Below stated are the constraints related to this Project:

CONVERSION

Confidential Page 33 3/13/2017

 Project Report

Conversion of data, either automated or manual, is not included. The Windows or pilot system will be
replaced not converted.

QUALITY REQUIREMENTS
Considering the critical nature of operations data center is supposed to handle, it is important to comply
with Quality standards like mentioned below:

Theft-safe data storage: Data should be secure enough to be accessible only by permitted viewers of
data.
No data corruption in case of any failure (Error handling)
Disaster proof infrastructure: Data centers should incorporate backup mechanism to ensure fail-safe
infrastructure in case of any sort of damage to the network or devices.
Minimum occurrences of Power failures and fluctuations

Power cables & structured cables should be ISO certified.

RESOURCE REQUIREMENTS
HUMAN
The following will come under the human resource requirements:

IT INFRASTRUCTURE DEPARTMENT

Department consisting of supervisors and skilled engineers

Confidential Page 34 3/13/2017

 Project Report

ELECTRICAL SERVICES DEPARTMENT

Department consisting of supervisors and skilled engineers

IMPLEMENTATION , SUPPORT AND MAINTENANCE STAFF

Including 24/7 support team

HARDWARE
The following will come under the resource requirements of hardware:

DATA STORAGE DEVICES

Storage architecture specially designed for distributed data persistence.

NETWORK INFRASTRUCTURE DEVICES (ROUTERS, SWITCHES , FIREWALLS )

Flexible yet robust networks comprising of multi-path connectivity between nodes using routers,
switches etc.

DATACENTER SUPPORT

Main and backup internet backbone with enough bandwidth to service peak consumer activity.
PCs and terminals for configuration and monitoring
High-end systems that meet requirement of operating, executing and supporting complex networks
and software.

Confidential Page 35 3/13/2017

 Project Report

S OFTWARE

Network analysis and monitoring software, for pre-emptive detection of failures and external attacks.
Remote administration and communication tools

POWER BACKUPS
Easily maintainable and replaceable Zero-delay UPS for immediate power recovery.
Backup Generators to support each data center to its full capacity including Air conditioning systems.

APPROVAL REQUIREMENTS
As the project of implementing data centers will progress, it revolves around a number of decisions to be
made after going through a detailed analysis. Initially this project will be based upon a number of
immediate approvals that are required from the upper level of management that includes:

Approval of the Project Proposal document.

Budget Approval.
Approval of the Distributed Architecture that is being proposed.
Approval of the human resources by the functional managers, who will carry out this project.
Approval for the timelines shared among the management.

AREAS OUT OF SCOPE

There are a few elements that need to be considered as out of scope with respect to this Project.
Below stated points share a light on those areas that will not be considered throughout this Project:

The location where these Data centers will be built is behind the Project scope.

Confidential Page 36 3/13/2017

 Project Report

Vendors of the devices and materials that constitute a complete Data center are also behind the
Project scope.
The Quality of service of Internet, as it is served by some internet provider, is also behind the
overall scope of this Project.
The quality of software that the bank is using currently is also behind the consideration of this
Project Scope.

SPONSOR ACCEPTANCE
Approved by the Project Sponsor:

_______________________________________________ Date:________________________
<Project Sponsor>

Confidential Page 37 3/13/2017

 Project Report

CREATE WBS AND WBS DICTIONARY

VERSION HISTORY
Version Date Author Change Description

1.0 5th April 13 Tariq Khanani Document created

1.0 7th April 13 Afnan Memon, Sameem Subhani Document Updated

1.0 7th April 13 Tariq Khanani, Hassan Ahmed Document Approved

WORK BREAKDOWN STRUCTURE (WBS)

Confidential Page 38 3/13/2017

 Project Report

PLANNING

DESIGN

Confidential Page 39 3/13/2017

 Project Report

IMPLEMENTATION

CONSTRUCT DATA CENTERS

Confidential Page 40 3/13/2017

 Project Report

COMMISSIONING

CLOSING

Confidential Page 41 3/13/2017

 Project Report

WBS ELEMENT DEFINITIONS

WBS Code WBS Element

1.1 Planning

WBS Element Description

In Planning phase we will plan all the activities to be performed we will

document the project plans, project deliverables and requirements. Planning
also involves creating a set of plans to help guide your team through the
execution and closure phases of the project.

WBS Code WBS Element

1.1.1 Estimate total time

WBS Element Description

In Estimate total time we will estimate all the activities that how much time they will take to
complete the whole project.

WBS Code WBS Element

1.1.1.1 Evaluate the timelines of project activities

WBS Element Description

In this particular element we will estimate that how much time will each activity takes to
complete.

Confidential Page 42 3/13/2017

 Project Report

WBS Code WBS Element

1.1.1.2 Identify major activities/milestones

WBS Element Description

In this particular element we will identify the major activities /milestones and
objectives to be performed to complete the final deliverable.

WBS Code WBS Element

1.1.1.3 Evaluate the HR needed

WBS Element Description

In this particular element we will identify that how much human resource we will need
to accomplish the different activities of the project.

WBS Code WBS Element

1.1.2 Calculate total budget

WBS Element Description

In this element we will calculate that how much budget we will require to complete the
whole project.

WBS Code WBS Element

1.1.2.1 Estimate total cost of the project

Confidential Page 43 3/13/2017

 Project Report

WBS Element Description

In this particular element we will evaluate how much cost each activity will take to
complete the project.

WBS Code WBS Element

1.1.2.2 Evaluate the materials/machines needed

WBS Element Description

In this wbs element we will estimate that how much materials/machines will be required
for each activities to complete the whole project.

WBS Code WBS Element

1.1.3 Asses overall risks in project

WBS Element Description

In this wbs element we will have to assess the overall risks which might occur anytime in
any phase of the whole project and we can assess the risk through estimating the probability
and impact, severity of the risk.

WBS Code WBS Element

1.1.3.1 Identify the risk that can occur

WBS Element Description

In this wbs element we will have to identify the risks that can occur anytime in any
phase of the whole project and we can identify the risk through brain storming ,group

Confidential Page 44 3/13/2017

 Project Report

creativity techniques.

WBS Code WBS Element

1.1.3.2 Identify strategies to minimize risk impacts

WBS Element Description

In this wbs element we will identify the risk strategies that will minimize the risk impacts.
The strategies which we implement on each risk will depend on the situation as we can
accept, transfer, mitigate and avoid the particular risk.

WBS Code WBS Element

1.1.3.3 Evaluate impact on our business

WBS Element Description

In this particular element we will evaluate the impact on our business strategies that
how the risks or any other contributing factors make an impact on our business. We can find
out the impact by checking the severity of the risk (Low, Medium, and High).

WBS Code WBS Element

1.1.4 Identify quality requirements standards to meet

WBS Element Description

In this particular element we will identify the quality requirements that were given by the
clients/sponsors. We will work on the quality requirements to meet the satisfaction of our

Confidential Page 45 3/13/2017

 Project Report

clients/sponsors.

WBS Code WBS Element

1.1.4.1 Identify customer quality needs

WBS Element Description

In this particular element we will identify the customer quality needs that what quality
requirements the customers want and we will try to fulfill the customer needs so that we can
satisfy the customers and maintain good image of the organization.

WBS Code WBS Element

1.1.4.2 Define a minimum and maximum baseline of quality

WBS Element Description

In this particular element we will define the minimum and maximum baseline of quality
needs that what minimum quality criteria the customers want and what maximum criteria
the customers want so that to meet the quality standards of the final deliverable .

WBS Code WBS Element

1.1.4.3 Identify criteria to judge quality

WBS Element Description

In this particular element we will identify the criteria to judge quality by the help of
quality baseline that what standards organizations have made to judge the quality of that
final deliverable.

WBS Code WBS Element

Confidential Page 46 3/13/2017

 Project Report

1.1.5 Plan for the procurement of machines/materials

WBS Element Description

In this particular element we will plan for the procurement of machines/materials that
what machinery or materials we will require on the activities to complete the final
deliverable.

WBS Code WBS Element

1.1.5.1 Identify vendors/suppliers

WBS Element Description

In this particular element we will identify vendors/suppliers. We will identify

vendors/suppliers through brain storming, expert judgment etc that which vendor is better
then other.

WBS Code WBS Element

1.1.5.2 Identify the number of labor resources needed

WBS Element Description

In this particular element we will identify the number of labor resources we required to
complete the following activity. We will identify it through brain storming, expert judgment
etc that how much labor we required to complete the following activity.

Confidential Page 47 3/13/2017

 Project Report

WBS Code WBS Element

1.2 Design

WBS Element Description

In the design phase element the phase will start with the requirement document
delivered by the requirement phase and maps the requirements into an architecture.
The architecture defines the components, their interfaces and behaviors. The design
document describes a plan to implement the requirements.

WBS Code WBS Element

1.2.1 Design electrical and power structure

WBS Element Description

In the design electrical and power structure element we will design the power and
electrical structure of the new data center which we constructed.

WBS Code WBS Element

1.2.1.2 Identify the backup supply infrastructure

WBS Element Description

In this particular element we will identify backup supply infrastructure so that with the
help of identifying backup infrastructure we can have the data of our customers in tact with
us our data cannot be lost.

Confidential Page 48 3/13/2017

 Project Report

WBS Code WBS Element

1.2.2 Design the network structure

WBS Element Description

In this particular element we will design the network structure of the data center that
what topology we will use. We will gather the requirements and make a plan to avoid from
future issues and shape a secure and reliable computer network.

WBS Code WBS Element

1.2.2.1 Identify the network topology to be implemented

WBS Element Description

In this particular element we will identify that what network topology is to be

implemented in the data center. It will be identified through brain storming, group creativity
technique etc.

WBS Code WBS Element

1.2.3 Design the database architecture

WBS Element Description

In this particular element we will design the architecture of database it is the process of
producing a detailed data model of a database. A fully attributed data model contains
detailed attributes for each entity.

Confidential Page 49 3/13/2017

 Project Report

WBS Code WBS Element

1.2.3.1 Identify the databases backup recovery infrastructure

WBS Element Description

In this particular element we will identify the database backup recovery infrastructure so
that the customers data remains intact.

WBS Code WBS Element

1.2.3.2 Identify the databases connectivity infrastructure

WBS Element Description

In this particular element we will identify the databases connectivity infrastructure

choosing the right data connectivity can dramatically reduce the time spent developing,
testing, and deploying critical applications.

WBS Code WBS Element

1.2.4 Design the security infrastructure

WBS Element Description

In this particular element we will design the security infrastructure we can gain
maximum benefit while making ongoing management less draining. Having a clear
architecture, and making the most appropriate use of products and services we can reduce
our exposure to risk of having data hack etc.

Confidential Page 50 3/13/2017

 Project Report

WBS Code WBS Element

1.2.4.1 Design network security infrastructure

WBS Element Description

In this particular element we will design the network security infrastructure the purpose
of designing the secure network architecture is to defend against complex threats and
malicious attacks.

WBS Code WBS Element

1.2.4.2 Design data security infrastructure

WBS Element Description

In this particular element we will design the data security infrastructure the purpose of
designing the data security infrastructure is to protect the data from hacking etc.

WBS Code WBS Element

1.2.4.3 Design integration of data security components

WBS Element Description

In this particular element we will design the integration of data security components
the purpose of designing the integration of data security components is to creates an easy
way to integrate tighter security in different applications.

WBS Code WBS Element

Confidential Page 51 3/13/2017

 Project Report

1.2.4.4 Design integration of network security components

WBS Element Description

In this particular element we will design the integration of network security components
it plays an important role in implementing the overall security of the organization. An overall
security solution includes design elements and components such as firewalls, VLANS etc.

WBS Code WBS Element

1.3 Implementation

WBS Element Description

In the implementation phase we will construct the data centers and implement the
backup supply and efficient cooling environment system etc

WBS Code WBS Element

1.3.1 Construct data centers

WBS Element Description

In this particular element we will construct the data centers which can maximize the
usage of our own networking assets to improve company's internal network operations. It
will increase the network reliability and scalability.

WBS Code WBS Element

1.3.1.1 Construct primary data centers

WBS Element Description

Confidential Page 52 3/13/2017

 Project Report

In this particular element we will construct primary data centers which give you
continuous operation, continuous support, security, flexibility and will increase the network
reliability and scalability.

WBS Code WBS Element

1.3.1.2 Implement power backup supply systems

WBS Element Description

In this particular element we will implement power backup supply systems so that the
data will remain intact in case of electricity failure.

WBS Code WBS Element

1.3.1.3 Implement efficient cooling environment systems

WBS Element Description

In this particular element we will implement efficient cooling environment systems so

that the data will remain intact in case of servers failure due to overheating.

WBS Code WBS Element

1.3.1.4.1 Construct backup data centers

WBS Element Description

In this particular element we will construct backup data centers so that in case of data
loss we can recover our data through backup data centers.

Confidential Page 53 3/13/2017

 Project Report

WBS Code WBS Element

1.3.1.4.2 Implement efficient cooling environment systems

WBS Element Description

In this particular element we will implement efficient cooling environment systems so

that the data will remain intact in case of servers failure due to overheating.

WBS Code WBS Element

1.3.1.4.3 Implement an efficient backup restoration system

WBS Element Description

In this particular element we will implement efficient backup restoration system so that
if the data is encrypted it will be recovered through backup systems.

WBS Code WBS Element

1.3.2 Implement the distributed network infrastructure

WBS Element Description

In this particular element we will implement the distributed network infrastructure

which will improve user productivity and satisfaction, and drive down the cost of operating
and maintaining the network infrastructure.

WBS Code WBS Element

Confidential Page 54 3/13/2017

 Project Report

1.3.2.1 Dig the ground to introduce fiber optics

WBS Element Description

In this particular element we will dig the ground to introduce fiber optics because fiber
optic is the reliable cable.

WBS Code WBS Element

1.3.2.2 Introduce fiber-optic for connectivity

WBS Element Description

In this particular element we will introduce fiber optic for connectivity because it is the
reliable cable it dont produce distortion and eliminates spark hazards etc.

WBS Code WBS Element

1.3.2.3 Connect all regional data centers together

WBS Element Description

In this particular element we will connect all the regional data centers together it will
help in optimization strategies that will benefit the whole organization

WBS Code WBS Element

1.3.2.4 Connect to a main head office node

Confidential Page 55 3/13/2017

 Project Report

WBS Element Description

In this particular element we will connect to main head office node where all the data of
the regions data center is kept on the servers.

WBS Code WBS Element

1.3.3 Implement security infrastructure

WBS Element Description

In this particular element we will implement security infrastructure so that the data
remains safe and confidential.

WBS Code WBS Element

1.3.3.1 Implement firewall within the network

WBS Element Description

In this particular element we will implement firewall with in the network so that the
data remains safe and confidential. Fire walls are used to protect us from outside intruders.

WBS Code WBS Element

1.3.3.2 Develop efficient access controls for each data centre

WBS Element Description

Confidential Page 56 3/13/2017

 Project Report

In this particular element we will develop efficient access controls for each data center
so that outside intruders cant access the controls and our data remains confidential.

WBS Code WBS Element

1.3.3.3 Develop encryption mechanism for data integrity

WBS Element Description

In this particular element we will develop encryption mechanism for data integrity
because it is an important tool in addressing specific security threats.

WBS Code WBS Element

1.3.4 Implement distributed database infrastructure

WBS Element Description

In this particular element we will implement distributed database infrastructure that will
increase reliability, performance and availability.

WBS Code WBS Element

1.3.4.1 Develop connectivity of regions with a central head office database

WBS Element Description

In this particular element we will develop connectivity of regions with a central head office
so that the data of all the regions are transferred to the head office that will increase
reliability, performance and availability of data.

Confidential Page 57 3/13/2017

 Project Report

WBS Code WBS Element

1.3.4.2 Develop data connectivity of bank branches with regional data centers

WBS Element Description

In this particular element we will develop connectivity of bank branches with regional data
centers so that the information from the bank will be transferred on time to the regional data
centers.

WBS Code WBS Element

1.4 Commissioning

WBS Element Description

In the commissioning phase we will inspect/test connectivity between data centers,

branches, head office etc.

WBS Code WBS Element

1.4.1 Pilot test the connectivity between data centers

WBS Element Description

In this particular element we will inspect/test the connectivity between data centers that
what we have implemented is working fine or not.

WBS Code WBS Element

1.4.2 Pilot test the connectivity between branches

Confidential Page 58 3/13/2017

 Project Report

WBS Element Description

In this particular element we will inspect/test the connectivity between branches that what
we have implemented is working fine or not.

WBS Code WBS Element

1.4.3 Pilot test the connectivity with central head office

WBS Element Description

In this particular element we will inspect/test the connectivity between head office that
what we have constructed the regional data center has the connectivity with the head office
or not.

WBS Code WBS Element

1.4.4 Verify that the security controls provide maximum data security and integrity

WBS Element Description

In this particular element we will verify that the security controls are providing the
maximum data security and integrity or not by keeping the data confidential.

WBS Code WBS Element

1.4.5 Verify that the backup restoration systems for data provide minimum

Confidential Page 59 3/13/2017

 Project Report

downtime

WBS Element Description

In this particular element we will verify that the backup restoration system which we have
implemented provide the minimum downtime response or not.

WBS Code WBS Element

1.4.6 Verify that the load balancers provide maximum uptime

WBS Element Description

In this particular element we will verify that the load balancers which we have
implemented provide the maximum uptime response or not.

WBS Code WBS Element

1.4.7 Pilot test the switching between primary and backup data centers

WBS Element Description

In this particular element we will test that the switching between primary and backup data
centers are working fine or not.

WBS Code WBS Element

1.4.8 Pilot test the switch between servers for load balancing

WBS Element Description

Confidential Page 60 3/13/2017

 Project Report

In this particular element we will test that the switching between servers for load
balancing are working fine or not.

WBS Code WBS Element

1.5 Closing

WBS Element Description

In the closing phase we will develop the lessons learned document and will develop the
success and failure stories of the project.

WBS Code WBS Element

1.5.1 Develop lessons learned document

WBS Element Description

In the lessons learned element we will develop the lessons learned document that what we
have learned from the mistakes and will try not to follow any mistakes in the future.

WBS Code WBS Element

1.5.2 Develop success stories for the project

WBS Element Description

In this particular element we will develop the success stories of the project that what went
well in the whole project.

Confidential Page 61 3/13/2017

 Project Report

WBS Code WBS Element

1.5.3 Review project terms of time, cost & scope at each end of phase

WBS Element Description

In this particular element we will review the triple constraints at each end of the phase to
see that if we are behind/above scope, time and cost.

PROJECT TIME MANAGEMENT PLAN

PROJECT SCHEDULE MANAGEMENT PLAN VERSION CONTROL
Version Date Author Change Description

1.0 15th April 13 Tariq Khanani Document Created & Approved

INTRODUCTION
PURPOSE OF THE SCHEDULE MANAGEMENT PLAN
The Schedule Management Plan has the following purposes:

To present the schedule of the project;

To identify factors that will tend to delay the schedule; and

Confidential Page 62 3/13/2017

 Project Report

To describe the effective monitoring & control procedures for the Project schedule;

PROJECT SCHEDULE
The detailed project schedule is provided in Appendix A. The following table provides the major milestones
of the project.

Milestone Deliverable(s) Date

Milestone 1 Build data centers all over the country to improve Thursday 20/Mar/2014
the up-time and response time of transactions
Build redundant data centers to ensure minimum
down time and efficiency in back up plan
Milestone 2 Build a distributed network architecture for the Thursday 07/Aug/2014
Banks overall operations to be processed
Milestone 3 Develop distributed database architecture for the Monday 22/Sept/2014
Banks overall data management and availability.
Milestone 4 Develop a robust security infrastructure. Thursday 28/Aug/2014

Confidential Page 63 3/13/2017

 Project Report

POTENTIAL CAUSES OF SCHEDULE SLIPPAGES

Following is a list of some of the factors that could lead to a slippage in the schedule.

Project status meetings are not properly conducted, hence less information of project progress
Project activities require more effort than planned;
Project staff require more training or experience to meet the estimates;
Additional activities beyond those planned are required;
Specific technical skills were assumed in the plan that are not available;
Customer quality needs are not delivered in a timely manner; or
The review and approval of deliverables takes longer than planned.

PROJECT SCHEDULE MONITORING & CONTROL PROCEDURES

MONITORING PROCEDURES
The Project of HATS bank will include effective procedures so as to timely monitor the schedule variances.
A set of instructions & procedures have been defined for this purpose which are stated as follows:

Weekly/Monthly review of activity status and estimates to complete work packages.

Each current activity will be reviewed and an estimate to complete (ETC) it will be made. The
estimate to complete will be added to the effort already spent. A potential slippage occurs when that
total (EAC) exceeds the original estimate.

Weekly/Monthly review of unplanned requirements such as equipment, staff, or consulting resources.

The adequacy of current resources, human and equipment will be reviewed. A potential schedule
slippage occurs when the need for additional resources is identified.

Confidential Page 64 3/13/2017

 Project Report

Weekly/ Monthly review of customer activities and performance. The response of the customer team
will be reviewed, particularly for current activities. A potential slippage occurs when there are delays
in responsiveness or customer decisions.

Weekly/ Monthly review of risks and changes to risks. The current status of risks will be reviewed. A
potential slippage occurs when existing risks have become riskier or when new risks have been
identified.

Weekly/ Monthly review of changes to scope, approved or otherwise. The current status of scope
compliance will be reviewed as described in the Scope Management Plan. A potential slippage occurs
when unapproved scope changes are being carried out.

CONTROL: RESOLUTION OF SCHEDULE PROBLEMS

A number of strategies can be implemented so as to overcome the schedule variances. Possible strategies
include:

Accept the slippage

If, in case, the impact of slippage of planned schedule is not severe then it can be accepted also but this
acceptance requires additional monitoring control also. The schedule slippage will be accepted by The
HATS Bank and the Project Manager.

Resolve the slippage

The schedule slippage will be resolved by either adding more resources or authorizing overtimes or in a
case by engaging consultants. The overall impact of this approach will be to incur more increased costs.

Reduce the scope

Confidential Page 65 3/13/2017

 Project Report

The project manager will consult with the Project Sponsor (The HATS Bank) to determine if the scope
can be alternatively reduced and, if so, what items of functionality can be eliminated or deferred.

Apply contingency
If there is no possible solution available then alternatively contingency budget can also be used in this
purpose. Below is the procedure to authorize & apply contingency to a schedule slippage.

APPLYING CONTINGENCY
Following is the procedure for applying contingency to cover cost increases or schedule slippages.

Contingencies are under the sole control of the management of The HATS Bank. The application of
contingency will be transparent to Project Management Office (PMO) and will occur when the project
manager makes a request to company management to apply it.
Contingencies are expressed in Pakistani Rupees (PKR). When they are applied to schedule slippages, They
will cover the costs of extra resources, overtimes, or additional external consulting.
The steps for applying contingencies are as follows:

Identify the reason for the schedule slippage and the expected total impact.
Present the contingency request to the management of The HATS Bank.
Upon approval, update the project plan, reducing the schedule contingency available.
If the request is not approved, follow managements directions for dealing with the schedule
slippage.

SCHEDULE MANAGEMENT PLAN ACCEPTANCE

Confidential Page 66 3/13/2017

 Project Report

Approved by__________________________________

Project Manager

__________________________________

Project Sponsor

__________________________________

Executive Sponsor

ACTIVITY DEFINITION

Confidential Page 67 3/13/2017

 Project Report

Confidential Page 68 3/13/2017

 Project Report

ACTIVITY ATTRIBUTES
Activity ID: 5 Activity: Evaluate the WBS No: 1.1.1.1
timelines of project activities
Activity Description: In this particular element we will estimate that how much
time will each activity takes to complete.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[33%],Project Manager[33%],Team Lead
(Electrical)[33%]
Activity Predecessors: 21,22 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Confidential Page 69 3/13/2017

 Project Report

Activity Successors: 10 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: Headquarter
Activity Assumptions: This activity assumes all activities are identified and resources and
vendors are also selected
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 6 Activity: Identify major WBS No: 1.1.1.2

activities/milestones
Activity Description: In this particular activity we will identify the major
activities /milestones and objectives to be performed to complete the final
deliverable.
Activity Responsibility: Team Lead (IT),Team Resources and Skill Sets Required:
Lead (Electrical),Project Manager
Activity Predecessors: None Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 17,13 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: Headquarters
Activity Assumptions:
Activity Constraints: Critical activity. Must complete within expected duration.
Activity ID: 8 Activity: Evaluate the HR WBS No: 1.1.1.3
needed
Activity Description: In this particular activity we will identify that how much

Confidential Page 70 3/13/2017

 Project Report

human resource we will need to accomplish the different activities of the

project.
Activity Responsibility: Project Resources and Skill Sets Required:
Manager[33%],Team Lead (Electrical)
[33%],Team Lead (IT)[33%]
Activity Predecessors: 18,19 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 22 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Headquarter
Activity Assumptions: Resource requirements are complete. Timelines are known
Activity Constraints: None

Activity ID: 10 Activity: Estimate total cost of WBS No: 1.1.2.1

project
Activity Description: In this particular activity we will evaluate how much cost
each activity will take to complete the project.
Activity Responsibility: Project Resources and Skill Sets Required:
Manager[40%],Team Lead (IT)[40%],Team
Lead (Electrical)[40%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
5,15,14 Finish-to-Start FS None

Activity Successors: Successor Scheduling: Successor Dependency: None

25,28,31,33,34 Finish-to-Start

Confidential Page 71 3/13/2017

 Project Report

Activity Duration (Days): 5

Location of Activity: Headquarter/Finance dept.
Activity Assumptions: Resource requirements are complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 11 Activity: Evaluate the WBS No: 1.1.2.2

materials/machines needed
Activity Description: In this activity we will estimate that how much
materials/machines will be required for each activities to complete the
whole project.
Activity Responsibility: Project Resources and Skill Sets Required:
Manager[17%],Team Lead (Electrical)
[17%],Team Lead (IT)[17%]
Activity Predecessors: 18,19 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 21 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: IT Dept/Headquarter
Activity Assumptions: Scope document is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 13 Activity: Identify the risks that WBS No: 1.1.3.1
can occur
Activity Description: In this activity we will have to identify the risks that can

Confidential Page 72 3/13/2017

 Project Report

occur anytime in any phase of the whole project and we can identify the
risk through brain storming ,group creativity techniques.
Activity Responsibility: Design Engineer Resources and Skill Sets Required:
(Electrical)[10%],Construction
Team[10%],Design Engineer (IT)
[10%],Electrician Team[10%],Ethical
Hackers[10%],Implementation
Team[10%],Network Engineers[10%],Security
Analysts[10%],Client Services
Team[10%],Project Manager[10%]
Activity Predecessors: 6 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 15,14 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: Headquarter
Activity Assumptions: Scope document is complete. Basic team is available to brainstorm for
risks
Activity Constraints: None

Activity ID: 14 Activity: Identify strategies to WBS No: 1.1.3.2

minimize risk impacts
Activity Description: In this activity we will identify the risk strategies that will
minimize the risk impacts. The strategies which we implement on each risk

Confidential Page 73 3/13/2017

 Project Report

will depend on the situation as we can accept, transfer, mitigate and avoid
the particular risk.
Activity Responsibility: Design Engineer Resources and Skill Sets Required:
(Electrical)[8%],Client Services
Team[8%],Construction Team[8%],Design
Engineer (IT)[8%],Electrician
Team[8%],Ethical
Hackers[8%],Implementation
Team[8%],Network Engineers[8%],Project
Manager[8%],Security Analysts[8%],Team
Lead (Electrical), Team Lead(IT)
Activity Predecessors: 13 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 10 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Headquarter
Activity Assumptions: All risks are identified
Activity Constraints: None

Activity ID: 15 Activity: Evaluate impact on WBS No: 1.1.3.3

our business
Activity Description: In this particular activity we will evaluate the impact on
our business strategies that how the risks or any other contributing factors

Confidential Page 74 3/13/2017

 Project Report

make an impact on our business. We can find out the impact by checking
the severity of the risk (Low, Medium, and High).
Activity Responsibility: Project Manager Resources and Skill Sets Required:

Activity Predecessors: 13 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 10 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Headquarter
Activity Assumptions: All risks are identified
Activity Constraints: None

Activity ID: 17 Activity: Identify customer WBS No: 1.1.4.1

quality needs
Activity Description: In this particular activity we will identify the customer
quality needs that what quality requirements the customers want and we
will try to fulfill the customer needs so that we can satisfy the customers
and maintain good image of the organization.
Activity Responsibility: Client Services Resources and Skill Sets Required:
Team[50%],Project Manager[50%]
Activity Predecessors: 6 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 18,19 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Confidential Page 75 3/13/2017

 Project Report

Activity Duration (Days): 2

Location of Activity: QA Dept/IT Dept
Activity Assumptions: Problem statement is fully understood. Scope document is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 18 Activity: Define a minimum WBS No: 1.1.4.2

and maximum baseline of
quality
Activity Description: In this particular activity we will define the minimum and
maximum baseline of quality needs that what minimum quality criteria the
customers want and what maximum criteria the customers want so that to
meet the quality standards of the final deliverable .
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(Electrical)[25%],Project Manager[25%],Team
Lead (IT)[25%],QA/QC Team[25%]
Activity Predecessors: 17 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 8,11 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: QA Dept/IT Dept
Activity Assumptions: Scope document is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 19 Activity: Identify criteria to WBS No: 1.1.4.3

judge quality
Activity Description: In this particular activity we will identify the criteria to

Confidential Page 76 3/13/2017

 Project Report

judge quality by the help of quality baseline that what standards

organizations have made to judge the quality of that final deliverable.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(Electrical)[25%],Project
Manager[25%],QA/QC Team[25%],Team Lead
(IT)[25%]
Activity Predecessors: 17 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 8,11 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: QA Dept/IT Dept
Activity Assumptions: Scope document is complete
Activity Constraints: None

Activity ID: 21 Activity: Identify WBS No: 1.1.5.1

vendors/suppliers
Activity Description: In this particular activity we will identify
vendors/suppliers. We will identify vendors/suppliers through brain
storming, expert judgment etc that which vendor is better then other.
Activity Responsibility: Project Manager Resources and Skill Sets Required:

Confidential Page 77 3/13/2017

 Project Report

Activity Predecessors: 11 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 5 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: Procurement Dept
Activity Assumptions: Resource plan is complete, procurement requirements and timelines are
know. Cost plan is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 22 Activity: Identify the number WBS No: 1.1.5.2

of labor resources needed
Activity Description: In this particular activity we will identify the number of
labor resources we required to complete the following activity. We will
identify it through brain storming, expert judgment etc that how much
labor we required to complete the following activity.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[33%],Team Lead (Electrical)[33%],Project
Manager[33%]
Activity Predecessors: 8 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 5 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: HR Dept

Confidential Page 78 3/13/2017

 Project Report

Activity Assumptions: Detailed requirements are known, number of locations, data centers
required are finalized
Activity Constraints: None

Activity ID: 25 Activity: Identify the structure WBS No: 1.2.1.1

with which to place the
electrical components
Activity Description:
Activity Responsibility: Electrician Resources and Skill Sets Required:
Team,Team Lead (Electrical)
Activity Predecessors: 10 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 26,41,45 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Implementation Dept
Activity Assumptions: Requirements are completely known, locations are finalized
Activity Constraints: None
Activity ID: 26 Activity: Identify the backup WBS No: 1.2.1.2
supply infrastructure
Activity Description: In this particular activity we will identify backup supply
infrastructure so that with the help of identifying backup infrastructure we
can have the data of our customers in tact with us our data cannot be lost.
Activity Responsibility: Design Engineer Resources and Skill Sets Required:
(Electrical)[67%],Team Lead (Electrical)
[67%],Project Manager[67%]

Confidential Page 79 3/13/2017

 Project Report

Activity Predecessors: 25 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 40,46 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Implementation Dept
Activity Assumptions: Electrical design requirements are known
Activity Constraints: None

Activity ID: 28 Activity: Identify the network WBS No: 1.2.2.1

topology to be implemented
Activity Description: In this particular activity we will identify that what
network topology is to be implemented in the data center. It will be
identified through brain storming, group creativity technique etc.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(IT),Project Manager
Activity Predecessors: 10 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 39,44,48 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: IT Dept
Activity Assumptions: Problem is completely analyzed, possible nodes and locations are
identified
Activity Constraints: Critical activity. Must complete within expected duration.

Confidential Page 80 3/13/2017

 Project Report

Activity ID: 30 Activity: Identify the WBS No: 1.2.3.1

databases backup recovery
infrastructure
Activity Description: In this particular activity we will identify the database
backup recovery infrastructure so that the customers data remains intact.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(IT),Project Manager
Activity Predecessors: 31 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 59 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: IT Dept
Activity Assumptions: Network design details are known
Activity Constraints: None

Activity ID: 31 Activity: Identify the WBS No: 1.2.3.2

databases connectivity
infrastructure
Activity Description: In this particular activity we will identify the databases
connectivity infrastructure choosing the right data connectivity can
dramatically reduce the time spent developing, testing, and deploying
critical applications.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(IT),Project Manager

Confidential Page 81 3/13/2017

 Project Report

Activity Predecessors: 10 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 30 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: IT Dept
Activity Assumptions: Requirements are finalized
Activity Constraints: None

Activity ID: 33 Activity: Design network WBS No: 1.2.4.1

security infrastructure
Activity Description: In this particular activity we will design the network
security infrastructure the purpose of designing the secure network
architecture is to defend against complex threats and malicious attacks.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[67%],Network Engineers[67%],Security
Analysts[67%]
Activity Predecessors: 10 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 36 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: IT Dept
Activity Assumptions: Design details are drafted and available
Activity Constraints: None

Confidential Page 82 3/13/2017

 Project Report

Activity ID: 34 Activity: Design data security WBS No: 1.2.4.2

infrastructure
Activity Description: In this particular activity we will design the data security
infrastructure the purpose of designing the data security infrastructure is
to protect the data from hacking etc.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(IT),Security Analysts
Activity Predecessors: 10 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 35 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: IT Dept
Activity Assumptions: Network designs are final
Activity Constraints: None

Activity ID: 35 Activity: Design integration of WBS No: 1.2.4.3

data security components
Activity Description: In this particular activity we will design the integration of
data security components the purpose of designing the integration of data
security components is to creates an easy way to integrate tighter security
in different applications.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(IT),Security Analysts

Confidential Page 83 3/13/2017

 Project Report

Activity Predecessors: 34 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 56 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: IT Dept
Activity Assumptions: Network designs are final
Activity Constraints: None

Activity ID: 36 Activity: Design integration of WBS No: 1.2.4.4

network security components
Activity Description: In this particular activity we will design the integration of
network security components it plays an important role in implementing
the overall security of the organization. An overall security solution
includes design activitys and components such as firewalls, VLANS etc.
Activity Responsibility: Security Resources and Skill Sets Required:
Analysts,Design Engineer (Electrical),Team
Lead (Electrical)
Activity Predecessors: 33 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Confidential Page 84 3/13/2017

 Project Report

Activity Successors: 54,55,56 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: IT Dept/Implementation Dept
Activity Assumptions: Requirement details are available
Activity Constraints: None

Activity ID: 39 Activity: Construct primary WBS No: 1.3.1.1

data centers
Activity Description: In this particular activity we will construct primary data
centers which give you continuous operation, continuous support, security,
flexibility and will increase the network reliability and scalability.
Activity Responsibility: Construction Team, Resources and Skill Sets Required:
Project Manager[67%]
Activity Predecessors: 28 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 40,41,43 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 93

Location of Activity: Regional main data centre location/HQ
Activity Assumptions: Data centers required equipments are available
Activity Constraints: None

Activity ID: 40 Activity: Implement power WBS No: 1.3.1.2

backup supply systems

Confidential Page 85 3/13/2017

 Project Report

Activity Description: In this particular activity we will implement power backup

supply systems so that the data will remain intact in case of electricity
failure.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(Electrical),Electrician Team
Activity Predecessors: 26,39 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 50 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 20

Location of Activity: IT dept
Activity Assumptions: Power devices are available/ Hardware is available
Activity Constraints: None

Activity ID: 41 Activity: Implement efficient WBS No: 1.3.1.3

cooling environment systems
Activity Description: In this particular activity we will implement efficient
cooling environment systems so that the data will remain intact in case of
servers failure due to overheating.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(Electrical),Electrician Team
Activity Predecessors: 39,25 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 50 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Confidential Page 86 3/13/2017

 Project Report

Activity Duration (Days): 10

Location of Activity: Implementation Dept
Activity Assumptions: Hardware requirements are procured
Activity Constraints: None

Activity ID: 44 Activity: Construct backup WBS No: 1.3.1.4.1

data centers
Activity Description: In this particular activity we will construct backup data
centers so that in case of data loss we can recover our data through
backup data centers.
Activity Responsibility: Construction Team Resources and Skill Sets Required:

Activity Predecessors: 28 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 45,46,43 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 45

Location of Activity: Regional backup locations
Activity Assumptions: Hardware requirements are procured, location is ready
Activity Constraints: None

Activity ID: 45 Activity: Implement efficient WBS No: 1.3.1.4.2

cooling environment systems
Activity Description: In this particular activity we will implement efficient
cooling environment systems so that the data will remain intact in case of
servers failure due to overheating.

Confidential Page 87 3/13/2017

 Project Report

Activity Responsibility: Electrician Resources and Skill Sets Required:

Team,Team Lead (Electrical)
Activity Predecessors: 25,44 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 50 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 10

Location of Activity: Data Center locations
Activity Assumptions:
Activity Constraints: None

Activity ID: 46 Activity: Implement an WBS No: 1.3.1.4.3

efficient backup restoration
system
Activity Description: In this particular activity we will implement efficient
backup restoration system so that if the data is encrypted it will be
recovered through backup systems.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:

Activity Predecessors: 26,44 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 50 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Confidential Page 88 3/13/2017

 Project Report

Activity Duration (Days): 7

Location of Activity: Regional backup center locations
Activity Assumptions:
Activity Constraints: None

Activity ID: 48 Activity: Dig the ground to WBS No: 1.3.2.1

introduce fiber optics
Activity Description: In this particular activity we will dig the ground to
introduce fiber optics because fiber optic is the reliable cable.
Activity Responsibility: Construction Team Resources and Skill Sets Required:

Activity Predecessors: 28 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 49 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 90

Location of Activity: Data center locations
Activity Assumptions: Cables are available
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 49 Activity: Introduce fiber-optic WBS No: 1.3.2.2

for connectivity
Activity Description: In this particular activity we will introduce fiber optic for
connectivity because it is the reliable cable it dont produce distortion and
eliminates spark hazards etc.

Confidential Page 89 3/13/2017

 Project Report

Activity Responsibility: Electrician Resources and Skill Sets Required:

Team[1%],Network Engineers[1%],Team Lead
(Electrical)[1%]
Activity Predecessors: 48 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 50 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 70

Location of Activity: Data center locations
Activity Assumptions: Fiber optic lines are being laid
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 50 Activity: Connect all regional WBS No: 1.3.2.3

data centers together
Activity Description: In this particular activity we will connect all the regional
data centers together it will help in optimization strategies that will benefit
the whole organization
Activity Responsibility: Electrician Resources and Skill Sets Required:
Team[1%],Team Lead (IT)
[1%],Implementation Team[1%],Network
Engineers[1%],Team Lead (Electrical)[1%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
40,41,45,46,49 Finish-to-Start None

Confidential Page 90 3/13/2017

 Project Report

Activity Successors: 51s,68 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 45

Location of Activity: Data center locations
Activity Assumptions: Data center are completely implemented
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 51 Activity: Connect to a main WBS No: 1.3.2.4

head office node
Activity Description: In this particular activity we will connect to main head
office node where all the data of the regions data center is kept on the
servers.
Activity Responsibility: Implementation Resources and Skill Sets Required:
Team[2%],Team Lead (IT)[2%],Network
Engineers[2%],Team Lead (Electrical)[2%]
Activity Predecessors: 50 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: Successor Scheduling: Successor Dependency: None

54,55,56,68 Finish-to-Start

Activity Duration (Days): 30

Location of Activity: Headquarter and main data center location
Activity Assumptions: Head office data center is implemented and complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 54 Activity: Implement firewall WBS No: 1.3.3.1

within the network

Confidential Page 91 3/13/2017

 Project Report

Activity Description: In this particular activity we will implement firewall with

in the network so that the data remains safe and confidential. Fire walls
are used to protect us from outside intruders.
Activity Responsibility: Implementation Resources and Skill Sets Required:
Team[4%],Network Engineers[4%],Team Lead
(IT)[4%]
Activity Predecessors: 36,51 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 59,53 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 15

Location of Activity: Data center locations
Activity Assumptions: Networks are interconnected and online
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 55 Activity: Develop efficient WBS No: 1.3.3.2

access controls for each data
centre
Activity Description: In this particular activity we will develop efficient access
controls for each data center so that outside intruders cant access the
controls and our data remains confidential.
Activity Responsibility: Ethical Resources and Skill Sets Required:
Hackers[4%],Security Analysts[4%],Team Lead
(IT)[4%]
Activity Predecessors: 36,51 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Confidential Page 92 3/13/2017

 Project Report

Activity Successors: 59,53 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 15

Location of Activity: IT Dept/Data center locations
Activity Assumptions:
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 56 Activity: Develop encryption WBS No: 1.3.3.3

mechanism for data integrity
Activity Description:
Activity Responsibility: Ethical Resources and Skill Sets Required:
Hackers[7%],Security Analysts[7%],Team Lead
(IT)[7%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
51,36,35 Finish-to-Start None

Activity Successors: 59,53 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 10

Location of Activity: IT Dept/Data center locations
Activity Assumptions: Security needs are identified
Activity Constraints: None

Activity ID: 58 Activity: Develop WBS No: 1.3.4.1

connectivity of regions with a
central headoffice database
Activity Description: In this particular activity we will develop connectivity of

Confidential Page 93 3/13/2017

 Project Report

regions with a central head office so that the data of all the regions are
transferred to the head office that will increase reliability, performance and
availability of data.
Activity Responsibility: Implementation Resources and Skill Sets Required:
Team[67%],Team Lead (IT)[67%],Network
Engineers[67%]
Activity Predecessors: 59 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 69 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 7

Location of Activity: IT Dept/Data center locations
Activity Assumptions: Regional and central data centers are complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 59 Activity: Develop data WBS No: 1.3.4.2

connectivity of bank branches
with regional data centers
Activity Description: In this particular activity we will develop connectivity of
bank branches with regional data centers so that the information from the
bank will be transferred on time to the regional data centers.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[67%],Implementation Team[67%],Network
Engineers[67%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
54,55,56,30 Finish-to-Start None

Confidential Page 94 3/13/2017

 Project Report

Activity Successors: 58,69 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 10

Location of Activity: IT Dept/Regional data center locations
Activity Assumptions: Regional data centers are complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 61 Activity: Pilot test the WBS No: 1.4.1

connectivity between data
centers
Activity Description: In this particular activity we will inspect/test the
connectivity between data centers that what we have implemented is
working fine or not
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[25%],Implementation Team[25%],QA/QC
Team[25%],Audit Team[25%]
Activity Predecessors: 69 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 62 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 7

Location of Activity: QA Dept/IT Dept
Activity Assumptions: Network and data centers are up and running
Activity Constraints: Critical activity. Must complete within expected duration.

Confidential Page 95 3/13/2017

 Project Report

Activity ID: 62 Activity: Pilot test the WBS No: 1.4.2

connectivity between branches
Activity Description: In this particular activity we will inspect/test the
connectivity between branches that what we have implemented is working
fine or not.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[19%],Implementation Team[19%],QA/QC
Team[19%],Audit Team[19%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
61,67,70 Finish-to-Start None

Activity Successors: 63 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 7

Location of Activity: Regional and central locations
Activity Assumptions: Network and data centers are up and running
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 63 Activity: Pilot test the WBS No: 1.4.3

connectivity with central head
office
Activity Description: In this particular activity we will inspect/test the
connectivity between head office that what we have constructed the
regional data center has the connectivity with the head office or not.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[21%],Implementation Team[21%],QA/QC
Team[21%],Audit Team[21%]

Confidential Page 96 3/13/2017

 Project Report

Activity Predecessors: 62 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 64,65,66 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 30

Location of Activity: QA Dept/IT Dept/HQ.
Activity Assumptions: Network and data centers are up and running
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 64 Activity: Verify that the WBS No: 1.4.4

security controls provide
maximum data security and
integrity
Activity Description: In this particular activity we will verify that the security
controls are providing the maximum data security and integrity or not by
keeping the data confidential.
Activity Responsibility: Implementation Resources and Skill Sets Required:
Team[20%],Project Manager[20%],QA/QC
Team[20%],Team Lead (IT)[20%],Audit
Team[20%]
Activity Predecessors: 63 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 74 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 7

Confidential Page 97 3/13/2017

 Project Report

Location of Activity: IT Dept/QA Dept

Activity Assumptions: Network and data centers are up and running
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 65 Activity: Verify that the WBS No: 1.4.5

backup restoration systems for
data provide minimum
downtime
Activity Description: In this particular activity we will verify that the backup
restoration system which we have implemented provide the minimum
downtime response or not.
Activity Responsibility: Implementation Resources and Skill Sets Required:
Team[3%],Project Manager[3%],QA/QC
Team[3%],Team Lead (IT)[3%],Audit
Team[3%]
Activity Predecessors: 63 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 74 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 7

Location of Activity: IT Dept/Branches/Regional and central locations
Activity Assumptions: Network and data centers are up and running
Activity Constraints: Critical activity. Must complete within expected duration.

Confidential Page 98 3/13/2017

 Project Report

Activity ID: 66 Activity: Verify that the load WBS No: 1.4.6
balancers provide maximum
uptime
Activity Description: In this particular activity we will verify that the load
balancers which we have implemented provide the maximum uptime
response or not.
Activity Responsibility: Project Resources and Skill Sets Required:
Manager[20%],Audit
Team[20%],Implementation
Team[20%],QA/QC Team[20%],Team Lead
(IT)[20%]
Activity Predecessors: 63 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 74 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 5

Location of Activity: IT Dept/Regional and central locations
Activity Assumptions: Network and data centers are up and running
Activity Constraints: None

Activity ID: 67 Activity: Pilot test the WBS No: 1.4.7

switching between primary
and backup data centers
Activity Description: In this particular activity we will test that the switching
between primary and backup data centers are working fine or not.
Activity Responsibility: Audit Resources and Skill Sets Required:
Team[8%],Team Lead (IT)
[8%],Implementation Team[8%],Network

Confidential Page 99 3/13/2017

 Project Report

Engineers[8%],QA/QC Team[8%]

Activity Predecessors: 69 Predecessor Scheduling: Predecessor Dependency:

Finish-to-Start None

Activity Successors: 62 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 5

Location of Activity: IT Dept/Regional and central locations/QA Dept
Activity Assumptions: Network and data centers are up and running
Activity Constraints: None

Activity ID: 70 Activity: Pilot test the switch WBS No: 1.4.8
between servers for load
balancing
Activity Description: In this particular activity we will test that the switching
between servers for load balancing are working fine or not.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[4%],Audit Team[4%],Implementation
Team[4%],Network Engineers[4%],QA/QC
Team[4%]
Activity Predecessors: 69 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 62 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 5

Confidential Page 100 3/13/2017

 Project Report

Location of Activity: IT Dept/QA Dept/Regional and central locations

Activity Assumptions: Network and data centers are up and running
Activity Constraints: None

Activity ID: 72 Activity: Develop lessons WBS No: 1.5.1

learned document
Activity Description: In the lessons learned activity we will develop the lessons
learned document that what we have learned from the mistakes and will
try not to follow any mistakes in the future.
Activity Responsibility: Team Lead Resources and Skill Sets Required:
(Electrical)[20%],Client Services
Team[20%],Implementation
Team[20%],Project Manager[20%],Team Lead
(IT)[20%]
Activity Predecessors: 73 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 75 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 2

Location of Activity: Headquarter
Activity Assumptions: Project implementation is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 73 Activity: Develop success WBS No: 1.5.2

stories for the project
Activity Description: In this particular activity we will develop the success
stories of the project that what went well in the whole project.

Confidential Page 101 3/13/2017

 Project Report

Activity Responsibility: Project Resources and Skill Sets Required:

Manager[33%],Team Lead (Electrical)
[33%],Team Lead (IT)[33%]
Activity Predecessors: 74 Predecessor Scheduling: Predecessor Dependency:
Finish-to-Start None

Activity Successors: 72 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Activity Duration (Days): 1

Location of Activity: Headquarters
Activity Assumptions: Project implementation is complete
Activity Constraints: Critical activity. Must complete within expected duration.

Activity ID: 74 Activity: Review project WBS No: 1.5.3

terms of time, cost & scope at
each end of phase
Activity Description: In this particular activity we will review the triple
constraints at each end of the phase to see that if we are behind/above
scope, time and cost.
Activity Responsibility: Team Lead (IT) Resources and Skill Sets Required:
[44%],Team Lead (Electrical)[44%],Project
Manager[44%]
Activity Predecessors: Predecessor Scheduling: Predecessor Dependency:
64,65,66 Finish-to-Start None

Activity Successors: 73 Successor Scheduling: Successor Dependency: None

Finish-to-Start

Confidential Page 102 3/13/2017

 Project Report

Activity Duration (Days): 3

Location of Activity: Headquarters
Activity Assumptions: Project implementation is complete
Activity Constraints: Critical activity. Must complete within expected duration.

PROJECT NETWORK DIAGRAM

Confidential Page 103 3/13/2017

 Project Report

ACTIVITY DURATION ESTIMATES

Confidential Page 104 3/13/2017

 Project Report

Confidential Page 105 3/13/2017

 Project Report

RESOURCE CALENDAR

Confidential Page 106 3/13/2017

 Project Report

RESOURCE WORK CALENDAR

Confidential Page 107 3/13/2017
 Project Report

PROJECT SCHEDULE

Confidential Page 108 3/13/2017