Project Management Plan Approval and Key Terms

The provided content is a collection of articles and books related to project management, along with appendices that include the Project Management Plan Approval, References, Key Terms, and Summary of Spending. The articles and books cover various aspects of project management, including proactive sampling approaches, learning-based optimization techniques, evolutionary algorithms, and resource-constrained scheduling. The appendices provide additional information, such as a summary of stakeholders involved in the project, scope management plan, change management plan, schedule, budget, deployment plan, and key terms relevant to the document.

VIC ROADS INFRASTRUCTURE DEVELOPMENT
PROJECT MANAGEMENT PLAN
Version <1.0>
<08/10/2017>
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
VERSION HISTORY
Version
#
Implemented
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0 <Author name> <mm/dd/yy> <name> <mm/dd/yy> <reason>
UP Template Version: 11/30/06
Page 1 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
TABLE OF CONTENTS
1 INTRODUCTION.....................................................................................................................4
1.1 Purpose of Project Management Plan........................................................................4
1.1.1 Definition of Project management........................................................................4
1.1.2 Definition of Project plan.....................................................................................6
1.1.3 Steps for developing the project plan...................................................................7
1.1.4 Defining purpose of the PMP...............................................................................8
2 EXECUTIVE SUMMARY OF PROJECT CHARTER.....................................................10
2.1 Purpose of project charter........................................................................................10
2.2 Assumptions/Constraints..........................................................................................14
2.2.1 Assumptions.......................................................................................................14
2.2.2 Constraints..........................................................................................................14
3 SCOPE MANAGEMENT......................................................................................................15
3.1 Work Breakdown Structure......................................................................................19
3.2 Deployment Plan......................................................................................................23
3.3 Change Control Management..................................................................................27
4 SCHEDULE/TIME MANAGEMENT..................................................................................31
4.1 Milestones................................................................................................................32
4.2 Project Schedule.......................................................................................................33
Page 2 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
4.2.1 Dependencies......................................................................................................45
5 COST/BUDGET MANAGEMENT......................................................................................56
6 QUALITY MANAGEMENT.................................................................................................68
7 HUMAN RESOURCE MANAGEMENT.............................................................................77
8 COMMUNICATIONS MANAGEMENT............................................................................79
8.1 Communication Matrix............................................................................................79
9 RISK MANAGEMENT..........................................................................................................82
9.1 Risk Log...................................................................................................................84
10 ISSUE MANAGEMENT........................................................................................................85
10.1 Issue Log..................................................................................................................85
11 PROCUREMENT MANAGEMENT....................................................................................85
12 COMPLIANCE RELATED PLANNING............................................................................87
13 REFERENCES........................................................................................................................89
APPENDIX A: PROJECT MANAGEMENT PLAN APPROVAL........................................98
APPENDIX B: REFERENCES..................................................................................................99
APPENDIX C: KEY TERMS...................................................................................................100
APPENDIX D: SUMMARY OF SPENDING........................................................................101
Page 3 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
1 INTRODUCTION
1.1 PURPOSE OF PROJECT MANAGEMENT PLAN
1.1.1 Definition of Project management
The target group of the VIC Roads Infrastructure Development PMP is all project partners
including the task support, senior initiative and the project group. Project administration
manages the arranging, sorting out and actualizing of a project. A task is an endeavor with
particular begin and end parameters intended to deliver a characterized result, for example,
another PC framework. A project is not the same as progressing forms, for example, an
administration program or a benefit administration program (Schwalbe 2015). The project
administration design is relied upon to viably and effectively manage all parts of a task
from beginning to end, with the perfect objective of conveying the result on time and on
spending plan. A task design regularly starts with a project contract, and it is required to
distinguish potential difficulties ahead of time and handle any barriers as they emerge so as
to keep the project on plan. Project Management is the craft of dealing with every one of
the parts of a project from origin to conclusion utilizing a logical and organized approach.
The term project might be utilized to characterize any attempt that is transitory in nature
and with a start or an end. The project must make something extraordinary whether it is an
item, administration or result and should be dynamically expounded (Kerzner 2013). As
the definition suggests, only one out of every odd errand can be viewed as a project. It is
advantageous to remember this definition while arranging projects and concentrate their
part in the accomplishment of the association.
Page 4 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Project Management Institute, Inc. (PMI) characterizes project administration as "the use
of learning, aptitudes, instruments and methods to an expansive scope of exercises keeping
in mind the end goal to meet the prerequisites of a specific task." The way toward
coordinating and controlling an undertaking through and through might be additionally
separated into 5 fundamental stages:
1. Project origination and start: A thought for an undertaking will be painstakingly
analyzed to decide if it benefits the association. Amid this stage, a basic leadership group
will recognize if the task can reasonably be finished.
2. Project definition and arranging: An undertaking design, project sanction and
additionally project extension might be explicitly stated, delineating the work to be
performed (Larson and Gray 2013). Amid this stage, a group ought to organize the project,
ascertain a financial plan and plan, and figure out what assets are required.
3. Project dispatch or execution: Resources' undertakings are conveyed and groups are
educated of obligations. This is a decent time to raise imperative project related data.
4. Task execution and control: Project managers will contrast extend status and advance
with the real arrangement, as assets play out the planned work. Amid this stage, project
directors may need to modify plans or do what is important to keep the undertaking on
track.
5. Undertaking close: After project assignments are finished and the customer has endorsed
the result, an assessment is important to feature extend achievement as well as gain from
project history.
Page 5 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Undertakings and task administration forms fluctuate from industry to industry; be that as
it may, these are more conventional components of a project. The general objective is
normally to offer an item, change a procedure or to take care of an issue so as to profit the
association.
1.1.2 Definition of Project plan
A project design is a formal record intended to manage the control and execution of a
project. A project design is the way to an effective project and is the most vital report that
should be made when beginning any business project. In IT, the term project design alludes
to a Gantt outline or whatever other record that showcases project exercises along a
timetable (Larson and Gray 2013). In any case, considering these reports alone as a project
design is erroneous. These specific reports can be all the more accurately named as project
plans, and might be viewed as just a piece of the real task design. Task start requires nitty
gritty and crucial documentation to track extend prerequisites, functionalities, planning and
spending plan. Poor documentation can prompt heartbreaking outcomes for all project
partners. Formal project designs build up point by point project prerequisites, including
human and money related assets, interchanges, anticipated courses of events and risk
administration. A project design is a formal assertion between the project procurer and
engineer. It records and guarantees shared task partner endorsement while helping
administration and specialized groups with project tracking.
The project director makes the task administration design following contributions from the
undertaking group and the key partners. A project administration design is a formal,
affirmed archive that characterizes how the task is executed, observed, and controlled. It
Page 6 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
might be a synopsis or a definite archive and may incorporate baselines, auxiliary
administration designs, and other arranging records. This record is utilized to characterize
the approach project group takes to convey the proposed project administration extent of
the task.
As the work continues, the execution of the task is measured against the execution
estimation pattern incorporated into the undertaking administration design. The degree
benchmark, plan standard, and the cost pattern are all in all alluded to as the execution
estimation gauge. In the event that there is a deviation from the standard while the work is
being done, the undertaking manager manages them by making acclimations to adjust the
deviation (Leach 2014). Besides that these modifications neglect to revise the deviations, at
that point formal change solicitations to the baselines wind up noticeably important.
Task managers invest a generous measure of energy guaranteeing baselines are
accomplished, guaranteeing the project support and the association get the full advantages
of their undertakings. Other than legitimate arranging, a task administrator's capacities
likewise lie in productively controlling the project and guaranteeing project expectations
are on time and that the undertaking is finished per the project administration design.
1.1.3 Steps for developing the project plan
As indicated by McNeil, Frey and Embrechts 2015, the accompanying exercises are related
with the advancement of the project administration arranging report:
Stage 1 - Providing a clarification of the task want to the partners: The initial step related
with the improvement of the project design report is to incorporate the subtle elements of
Page 7 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
the project, as the need of the task, the foundation points of interest of the project, the
project limitations and the baselines related with the same.
Stage 2 - Defining the parts and obligations of the project colleagues: Experts Svejvig and
Andersen 2015, are of the conclusion that the subsequent stage related with the
advancement of the project design is to recognize the assets chipping away at the task and
the distinguishing proof of the parts that they would play amid the life cycle of the project
(Burke 2013).
Stage 3 - Developing the Scope explanation: As specialists Mir and Pinnington 2014, that
the Scope articulation goes about as an assertion of between the project administration
group and the project supports, with the end goal that both the gatherings stay in agreement
in regards to what's in store from the task (Lock 2014).
Stage 4 - Identifying the timetable, Scope and cost baselines of the project: The
recognizable proof of the Scope administration methods would basically be trailed by the
action of distinguishing the calendar, Scope and cost baselines of the task.
Stage 5 - Identifying the risks and issues of the project: According to scientist Turner 2016,
the last snippet of data that must be incorporate into the task arranging record would
basically incorporate the risk investigation of the project.
1.1.4 Defining purpose of the PMP
All the expert bodies offer rules on the level and sort of data that ought to be characterized
in the beginning times of the project as a Project Management Plan. The motivation behind
such an archive is to give a complete benchmark of what must be accomplished by the
project, how it is to be accomplished, will's identity included, how it will be accounted for
Page 8 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
and measured and how data will be conveyed (Heldman 2015). It ought to be utilized as a
source of perspective for any choice that is made on the task and for elucidation of misty
ranges. Such an archive ought to be utilized as a kind of perspective all through the project
to guarantee that the administration of the task is done reliably and in accordance with
approach and techniques. In spite of the fact that the PMP is created as a major aspect of
the project start and definition, it ought to be a living report that develops as the task
advances and is refreshed with the most recent important data as required (Fleming and
Koppelman 2016). The PMP ought to be accessible to all extend individuals as it can give
basic project data and can be utilized to acquaint project individuals with the project. The
project administration design is most likely the principle correspondence record for the
project.
The motivation behind the task administration design (PMP) is a report that can be utilized
by everybody required with the project to help impart and detail data and depict forms that
the project will embrace. It will detail the degree, expectations, timescales and parts and
duties of people included and be gotten in frame from the business case made by the
Sponsor. It likewise frames part, or can be utilized as a part of the agreement between the
undertaking administrator and support, and if not utilized as a part of the contract, it
represents an agreement. Four designs/strategies inside the PMP are point by point
underneath:
1. Hazard Management Plan: It is utilized to detail the procedures and different techniques
for recognizable proof, appraisal, design reaction and execute reactions. It is utilized to
relieve any hazard to the undertaking and partners and recognize who the hazard has a
Page 9 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
place with and how it is to be overseen. The hazard enlist (log) would likewise be point by
point in the PMP.
2. Partner Management Plan: It is utilized to help distinguish, asses, impart and by and
large deal with the partners of the task. A partner examination would be definite to
recognize which partners are the most persuasive and position them in a various leveled
arrange.
3. Change Control Procedure: It is utilized to distinguish the procedures and techniques
that are to be attempted to oversee (control) and execute change. It will contain change ask
for structures and detail the required information, for example, cost, program and kind of
progress.
4. Correspondences Plan: The interchanges design clarifies what correspondence will be
attempted encompassing and amid the undertaking. It will feature techniques, for example,
reports and the normality of these, and furthermore rattle off the different structures
correspondence classifications that are acknowledged, for example, sorts of composed or
verbal.
2 EXECUTIVE SUMMARY OF PROJECT CHARTER
2.1 PURPOSE OF PROJECT CHARTER
A task contract (PC) is a record that expresses a project exists and furnishes the
undertaking administrator with composed specialist to start work. The record encourages
the task supervisor to convey his power and disclose to extend members and partners why
Page 10 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
the project is required, who it includes, to what extent the undertaking will take to finish,
the amount it will cost, what assets are required and how fruitful culmination of the
undertaking will help the association (Ma, Gu and Li 2015). Once made, the report is once
in a while (if at any point) changed. The Project Management Body of Knowledge
(PMBOK) characterizes a project sanction as a report that formally approves an
undertaking. The project contract is not made by the Project Manager. Rather, it is issued
by the support to engage the Project Manager with the expert to start the project and
acquire assets for project exercises. The project sanction ought to incorporate at the very
least the accompanying:
 business requirement for the undertaking which connects the project to the
association's general methodology
 stakeholders and their underlying prerequisites
 objectives or quantifiable criteria that must be met for the project to be viewed as
effective
 definition of what is in scope (at any rate at an abnormal state), and in addition out
of extension for the task
 constraints and presumptions
The target group of the VIC Roads Infrastructure Development PMP is all project partners
including the project support, senior authority and the task group. The project contract is a
report that formally begins a project or a stage. It formally approves the presence of the
project and gives a reference source to what is to come. The contract gives a heading and a
feeling of reason to the administration from begin to end (Maenhout and Vanhoucke
Page 11 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
2017). A project sanction names the task manager and characterizes the specialist of the
project manager (Nicholas and Steyn 2017). It gives the project manager the specialist to
use authoritative assets to finish the task targets. It must clarify the business require that
prompt the project being taken up. It likewise catches abnormal state arranging data
(scope, expectations, presumptions, and so forth.) about the project. The essential reason
for a task sanction is to approve the project manager to begin the endorsed project and
enable him to utilize hierarchical assets to fulfill the targets of the task.
Project Title VIC Roads Infrastructure Development
Project Location Australia
Brief Description of
the Project
This project is based on development of the existing infrastructure of
VIC Roads by implementation of 2000 additional mobile speed cameras.
The installation of the cameras will allow VIC Roads department and
the police stations of Victoria state government to maintain the safety
laws and capturing incidents as evidence of an infringement.
Prepared By SAMECH Team
Date [10-08-2017] Version 1.0
Aim of the Project: The essential point of the system advancement and execution task to
build up a protected association between the police headquarters and VIC Roads office
working in Australia. Notwithstanding that, the created organize and the framework will
give secure association and web administrations for the police headquarters and VIC Roads
office.
Page 12 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Scope of the project - The accompanying are the specific extent of the system execution
project for VIC Roads:
 To build up a system outline for associating the police headquarters and VIC Roads
 To outline the system foundation and plan
 To execute and plan the equipment and programming foundation for the system
association
 To actualize the blocking and screening offices of improper substance through the
created arrange
 To build up the office for information stockpiling and information exchange
 To guarantee 99.99% of the created system and framework accessibility
 To associate the police headquarters and VIC Roads over cloud administrations
Stakeholder Name Benefits
Project manager
The project manager will work for the timely completion of the project
within the allocated budget;
Development team
The development team in the project works for the establishment of the
network infrastructure and internet services in various locations;
Technical support
team
The technical support team provides assistance in implementing the
proposed network;
Implementation team Ensures the effective establishment of the network connectivity between
Page 13 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Stakeholder Name Benefits
the different schools and libraries;
Network engineer
The network engineer developed the network diagram while ensuring
secure connectivity and internet services through the established network;
2.2 ASSUMPTIONS/CONSTRAINTS
2.2.1 Assumptions
The assumptions in a task are characterized as the factor, criteria or occasions that are
thought to be sure, genuine or valid with no prerequisite for showing or verification. The
accompanying the suspicions considered for the VIC Roads Infrastructure improvement
project:
 The Australian Government will give the whole budgetary sponsorship to building
up the project.
 Efficient correspondence and transport offices has been accommodated finishing
the project.
 The project group dispensed for the advancement has proficient and noteworthy
learning of creating and fulfilling system availability.
2.2.2 Constraints
Limitations inside the projects are characterized as the factor and occasions that manages
and confines the work that are should have been done in the task. Each project is driven by
Page 14 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
the distinguished obliges accessible in the task. Basu (2014), demonstrated that each
project is bound by three noteworthy imperatives in particular Scope, cost and time.
Scope: The project scope decides the exercises and work that should have been finished for
the attempted task. The Scope are practical components that are measured for guaranteeing
the finishing of the project.
Cost: The cost of the project is characterized as the aggregate move required for finishing
the project. The cost of a project incorporates the work cost, equipment, programming,
organizing component and different assets. The decrease of the cost amid the project
impacts the quality and time required for project.
Time: Time in project administration is thought to be a standout amongst the most critical
factor in finishing the project. The time imperatives can be characterized as the aggregate
time required or allotted for project finish.
For the foundation of the protected system association in this project, the accompanying
are the significant requirements recognized:
 The foundation of the system availability should be finished inside evaluated time
span for the project.
 The project should be created with the given monetary assets distributed by the
Australian Government.
 The created arrange network and web administrations ought to give 99.99% of
accessibility over all the police headquarters and VIC Roads.
Page 15 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
3 SCOPE MANAGEMENT
Scope Management Plan is characterized as the accumulation of exercises and systems that
are required for finishing the project and guaranteeing the errand being done as indicated
by the characterized scope. The scope administration design contain five noteworthy stages
in particular, start organize, scope arranging stage, scope characterizing stage, scope check
stage and Scope change control stage (Verzuh 2015). The project manager that is has the
obligation and expert for creating and archiving the required scope administration get
ready for the system foundation of VIC Roads. The scope explanation alongside the WBS
word reference and EBS structure helps in characterizing the extent of the project. The
experts of VIC Roads and the state legislature of Australia has the specialist of exploring
and favoring the created scope explanation design. Upon the acknowledgment, the project
supervisor will start crafted by the system advancement (Lientz and Rea 2016). Then
again, upon the demand of change, the created Scope is adjusted and assessed once more.
The project manager uses the criticism and survey from the project support and VIC Roads
experts for rolling out the required improvements in the Scope administration design.
Project Scope Management alludes to the arrangement of procedures that guarantee an
undertaking's degree is precisely characterized and mapped. Extension Management
strategies empower project administrators and managers to assign only the perfect measure
of work important to effectively entire a task concerned principally with controlling what
is and what is not a piece of the undertaking's degree. The extent of an undertaking is the
unmistakable distinguishing proof of the work that is required to effectively entire or
convey a task. One of the task supervisor's duties is to guarantee that lone the required
Page 16 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
work (the degree) will be performed and that each of the expectations can be finished in
the dispensed time and inside spending plan.
The documentation of the extent of the task will clarify the limits of the undertaking, set up
the obligations of every individual from the group, and set up strategies for how function
that is finished will be confirmed and affirmed. This documentation might be alluded to as
the extension proclamation, the announcement of work, or the terms of reference. The
steps involved in project scope management are listed as below:
Characterize project needs: Defining the requirements of the undertaking is the initial
move toward the foundation of a task timetable, portion of undertaking assets and defining
project objectives. Just with these means characterized will you have the capacity to
comprehend the work that should be done – as it were, the extent of the task should be
characterized. Once that is done, colleagues can be allotted assignments, and gave
guidance to convey a task in the given time and spending plan.
Comprehend the project targets: To characterize the task scope, it is essential to first set up
the destinations of the undertaking, which may incorporate another item, making another
administration inside the association, or building up another bit of programming. There are
various destinations that could be integral to a project; the task administrator guarantees
the group conveys comes about as per the predefined highlights or capacities.
Characterize the task scope: The assets and work that goes into the formation of an item or
administration is basically what characterizes the extent of the project. The extension by
and large diagrams the objectives that will be met keeping in mind the end goal to
accomplish a tasteful outcome.
Page 17 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Project Scope Management Process
Regularly, when performing Scope Management, project administrators chance upon
issues in the way. The issues that may emerge when characterizing and archiving Project
Scope are:
Some regular issues with performing extension administration can prompt issues once the
project has started. It is prescribed to assess all degree administration documentation with
an eye toward:
Vagueness: Ambiguity in scope frequently prompts superfluous work and perplexity. To
maintain a strategic distance from this, the extension should be obviously characterized
and to the point.
Inadequate definition: Incomplete extensions prompt calendar slips which prompt cost
overwhelms. To stay away from this, the extension should be finished and precise.
Page 18 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Fleetingness: Transient extensions prompt degree crawl the essential driver recently
conveyances and "ceaseless" undertakings. To keep away from this, the degree record
should be finished and stay unaltered for the term of the project.
Un-community oriented extension: A degree that is not cooperatively arranged causes
misinterpretations in prerequisites and plan. To stay away from this, the extension report
ought to be imparted to all partners at each progression of the degree definition process.
Page 19 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
3.1 WORK BREAKDOWN STRUCTURE
WBS Task Name
0 VIC Roads Infrastructure Development
1 Project Startup
2 Initiation phase
2.1 Evaluation of the business case for VIC Roads
2.1.1 Determining the project requirements
2.1.2 Determining the business requirements
2.2 Conduction of feasibility study
2.2.1 Identification of the police stations
2.2.2 Identification of the accident prone zones
2.2.3 Acquisition of permit from police stations
2.2.4 Analysis of the existing network infrastructure
2.3 Identification of non-functional requirements
2.3.1 Determining the required resources
2.3.2 Estimating the required time
2.4 Identification of functional requirements
2.4.1 Technical requirements
2.4.2 Operational requirements
2.4.3 Legal requirements
Page 20 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
2.4.4 Defining the scope of project
2.4.5 Securing sponsorship of the project
2.4.6 Developing the preliminary budget
2.4.7 Developing the primary schedule
2.4.8 Obtaining approval from client
2.4.9 Closure of project initiation phase
3 Design phase
3.1 Preparing the rough draft of network infrastructure
3.2 Reviewing the functional specifications
3.3 Sending the project plan for approval
3.4 Obtaining the approval from the state government
3.5 Obtaining the approval of the state ministry department
3.6 Obtaining the permission from police stations
3.7 Developing the design specification
3.8 Development of the deployment plan
3.8.1 Planning for network setup
3.8.2 Planning for securing the data shared
3.8.3 Planning for data storage
3.8.4 Planning for blocking inappropriate facilities and content
3.8.5 Planning for interconnecting the police stations and VIC Roads
3.8.6 Planning for implementing cloud services
Page 21 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
3.8.7 Proposal of the network design
3.8.8 Obtaining approval of the design
3.8.9 End of project planning phase
4 Project development phase
4.1 Implementing the software and hardware requirements of the network
4.2 Establishing connection between the police stations and VIC Roads
4.3 Developing the network architecture
4.4 Implementing design for network and internet services
4.4.1 Implementation of infrastructural design for internet services
4.4.2 Connecting the established network via cloud services
4.4.3 Connecting the network with the state ministry department
4.4.4 Implementation of data storage facility
4.4.5 Implementing data security
4.4.6 Provide blocking and screening of inappropriate contents
4.4.7 Implementation of data security
4.4.8 Closure of development phase
5 Testing phase
5.1 Develop the testing module
5.2 Integrate the testing modules within the network
5.3 Test for effective communication
5.4 Test for content restriction
Page 22 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
5.5 Test for vulnerability attacks
5.6 Test module integration
5.7 End of project testing phase
6 Training phase
6.1
Developing the training specifications for the VIC Roads, Police personnel’s
and governmental authorities
6.2 Identification of the training procedure
6.3 Developing the materials for training
6.4 Conducting usability study
6.5 Provide training
6.6 Closure of training phase
7 Project closure phase
7.1 Developing documentation
7.1.1 Developing the network documentation
7.1.2 Reviewing the documentation
7.1.3 Developing user specific manuals
7.1.4 Audit of the project
7.2 Project handover
7.2.1 Implementation of the network and internet facilities
7.2.2 Development of network maintenance team
Page 23 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
7.2.3 Reviewing the designed network
7.2.4 Project team sign off
7.2.5 End of project closure phase
8 Stop project
3.2 DEPLOYMENT PLAN
An arrangement that portrays how the system will be actualized, including offices and
equipment. The Network Deployment Plan is arrange particular; it does not cover the client
planning and cut-over exercises. Planning of the Network Deployment Plan begins ahead
of schedule in the life cycle and the arrangement is extended at each ensuing stage. The
following diagram represents a complete Network design for the VIC Roads Infrastructure
Development project.
Page 24 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Figure 1: Network Infrastructure for VIC Roads
(Source: Created by Author)
The necessity was to plan and stage a situation to interconnect VIC Roads and police
headquarters in the province of Victoria, Australia. The innovation, including PCs, a LAN,
server, and programming, was to be designed and made prepared at a focal site, at that
point put in a compartment and warehoused until required. Whenever required, the holders
would be dispatched to a brief site, unloaded, and introduced by impermanent workers
with insignificant specialized information (Hill 2013). In the wake of being utilized for a
brief span, the establishment was repacked, dispatched back to the focal site, unloaded,
reconfigured, and repackaged to come back to the distribution center to anticipate the
following use. Preparing locales may utilize hardware that is eventually bound for other
lasting destinations. The task portrayed over that had gear introduced in transitory areas
Page 25 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
utilized the accompanying agenda for the expulsion which was finished by non-specialized
work force.
Today VIC Roads has a WLAN and remote visitor organize. At the point when numerous
clients associate with a similar access point availability is intruded. To maintain a strategic
distance from this issue, settled Ethernet jacks are utilized as a part of all meeting rooms.
This prompts issues with clients losing their web session while moving their PC from their
work area to a meeting room. There are additionally visit issues with links that are tangled
or not working. Having remote system scope all through the entire office would take care
of these issues and would rearrange life for the representatives. This requires adequate
limit with respect to the system and cautious arranging and position of access focuses.
Since VoIP is utilized it is vital that the remote association is steady and that media parcels
are not dropped, deferred, or ruined more habitually than a little portion of the movement
(under 5%). This would empower a client to move around in the workplace while in a
VoIP session without losing network or end of the session. Notwithstanding, unless
portable IP is to be upheld, this implies the system must be a solitary subnet, since
generally the client would move between subnet - henceforth her gadget would get another
IP address and the VoIP session would should be adjusted or the session would be ended.
Today the organization has a contract for their uplink with one ISP. Nonetheless, the
association with this ISP offers some repetition. Besides that the settled association with
the ISP ought to go down because of disappointment in the settled access organize, a 4G
switch set in the new office can be utilized as reinforcement. This implies at any rate the
most basic work can proceed.
Page 26 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
The IEEE 802.11 benchmarks are generally utilized WLAN gauges. Inside the IEEE
802.11 group of gauges are a few distinct norms, the most ordinarily utilized are 802.11a,
802.11b, 802.11g, and 802.11n. The fundamental contrasts are association speed and
working recurrence. Settled Ethernet associations are for the most part in light of utilizing
turned match (TP) Cat 5 links. Feline 5 links bolster transmission capacity of 100 MHz
which is adequate for Fast Ethernet speeds (up to 100 Mbps). Alternatively Cat 5e or CAT
6 links can be utilized to help higher paces. The IEEE 802 group of measures give point by
point details to most settle and remote LANs.
A critical standard in such manner is IEEE 802.3af Power over Ethernet (PoE) - as this
standard empowers the Ethernet change to convey energy to arrange appended gadgets, for
example, IP phones and access focuses. By conveying control over the system cabling
there is no compelling reason to find the gadgets close to an electrical outlet. Also, if there
is a requirement for working amid a power disappointment the system switch and the
system framework may be controlled by means of an uninterruptable power supply with
the goal that IP phones and different gadgets could keep on operating in spite of a power
blame of the general power mains. PoE is as often as possible utilized together with light
weight get to focuses and a WLAN controller (WLC) to diminish the cost and increment
the sensibility of huge quantities of access focuses. It is vital to take note of that in a little
setup that it may not be advantageous to use a WLC.
The most well-known sorts of security utilized as a part of a WLAN are Wired Equivalent
Privacy (WEP) and Wi-Fi Protected Access (WPA). WEP has been supplanted by WPA
since WEP was too simple to break. The present standard is WPA2, which utilizes a more
Page 27 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
drawn out key, henceforth it is thought to be more secure than WPA. Both WPA and
WPA2 can be utilized with either WPA-Personal or WPA-Enterprise. WPA-Personal is
intended for little office organizes and is likewise alluded to as WPA-PSK, where PSK
remains for Pre-shared key. WPAPSK does not require a validation server. A 256-piece
key, created from a secret word is utilized by the system gadgets to confirm when they
wish to utilize the administrations of the entrance point. WPA-Enterprise requires a more
entangled setup because of its utilization of a RADIUS (or DIAMETER) confirmation
server. Extensible Authentication Protocol (EAP) is utilized for validation between the
supplicant (the cell phone) and the confirmation server. Note that IEEE 802.1x and EAP
can likewise be utilized to validate gadgets connected to the settled LAN.
The underlying arrangement to change the system of the new office to basically WLAN
was dismissed because of expenses. To overhaul the APs to IEEE 802.11n standard was
nearly as costly as introducing LAN in the new office, in this way the WLAN was kept as
some time recently. The APs were recently checked to work appropriately and introduced
with the most recent programming to keep running on IEEE 802.11b/g as earlier and links
and jacks were introduced to the LAN in the new office. Amid the project, a ton of
learning was increased about WLAN with its distinctive gauges and security issues. When
arranging a system it is critical to focus on what limit will be required, what gadgets will
be utilized as a part of the system, and if there is a requirement for higher information rates
and utilization of later guidelines. With regards to security, whatever the system may
resemble, in the event that it is a huge business or only a little home system, the best
decision is WPA2 yet regardless, it is constantly better to pick WPA over WEP. The
Page 28 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
objectives of this undertaking were to design and to report the move of the organization to
the new office. The primary concentrate was on growing the current WLAN, yet despite
the fact that this was not executed at last, the material about the WLAN could be valuable
later on. This report could likewise be utilized as documentation for a move of another
office inside the organization. With a considerable measure of the preliminary work
effectively done, the choices about another system can be made a ton speedier.
3.3 CHANGE CONTROL MANAGEMENT
The change control administration is a procedure that builds up the development of a
powerful and savvy framework with essential changes in the association. The project is
8ymade for the improvement of system framework for VIC Roads that would enable them
to coordinate their information and data on a solitary stage.
Amid the system foundation for associating VIC Roads and police headquarters, different
changes and alteration will be required for alleviating the issues and difficulties while
finishing the task inside the predefined extension and due date (Leach 2014). The project
administrator has built up an itemized procedure for managing the progressions require
amid organize execution project.
A hearty record control administration process lies at the core of a quality administration
framework (QMS); practically every part of reviewing and consistence check is resolved
through the investigation of reported confirmation. Change administration is the procedure
in charge of controlling the lifecycle of all progressions inside a QMS framework. It is a
formal procedure used to guarantee there is an institutionalized strategy and methods set up
Page 29 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
to drive productive and provoke treatment of all progressions while viably conveying the
progressions to the affected zones preceding usage.
Demand a Change
A change ask for is the documentation used to ask for the genuine change to/for your
procedure, framework, and so on. Whoever is asking for the change claims the real
demand and needs to clarify the purpose behind the change and guarantee every affected
territory have been distinguished and incorporated into the audit and endorsement of the
change. When characterizing the change, it's important to have the demand close by with
every single supporting explanation. This ought to at least incorporate the accompanying:
Change Request Form: Clearly and compactly plot what should be changed, so the affected
regions can survey and break down.
Purpose behind the Request: Detail the general business or client affect, and distinguish the
anticipated time period of the undertaking.
Expected Completion/Implementation Date: The requester ought to give a normal due date.
This doesn't mean the change will be finished by this date. In any case, it proposes a
turnaround time for the group to finish their audit procedure taking into consideration
elective choices (if appropriate).
Expected Outcome: This ought to clarify the requirement for the demand. Blueprint the
coveted result/advantage anticipated from the change.
Submitting and Reviewing the Change Request
Once the change ask for is recorded, it's submitted to the change control organizer/project
director. The audit procedure changes reliant on your association's procedure. As a rule the
Page 30 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
demand is sent to all territories conceivably affected to survey the asked for changes. This
permits all individuals an opportunity to make inquiries, recommend extra changes, or give
exchange choices before settling on an official choice. The procedure should hold the
analysts to the normal info/input turnaround time.
Changing the Request Response Document
Once the demand has been inspected, the archive reaction ought to give
recommendation(s) from the commentators on which speaks to the best decision.
The reaction may include:
Proposed Solution: Should incorporate choices on the best way to react to the change ask.
Proposed Timeline: An expected timetable of exchange choices/decision displayed.
Effect: Minimally clarifies the cost of the progressions, the effect on the course of events
and potential quality outcomes or potentially any asset affect.
Ultimate choice and Approval
In a perfect world, the analyst gives an opportune reaction. In the occasion the change
control reaction record surpasses the laid out due date, and there is no reaction/input from
the commentator, it ought to be sent to assigned reinforcement analysts and another due
date ought to be set. By and large if the due date is in danger, the demand ought to be
rerouted before the due date to the reinforcement individual.
An ultimate conclusions/comes about must be formally logged and followed. It's vital that
when the change control process is characterized, it incorporates a rundown of patrons,
Page 31 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
partners and key managers who can say something and favor or deny the procedure or
potentially the choice.
Besides that endorsed, the change control organizer/project director will refresh the proper
change control log and additionally documentation to mirror the change(s).
Besides that rejected, the change control facilitator/project supervisor will refresh the
change control log.
Each change control demand ought to take after a comparative procedure. Having this sort
of process set up gives consistency and oversees desires.
When ask for has been affirmed/denied, the accompanying must be finished:
Report: Once a survey is directed, a report is composed. Every one of the discoveries, info,
input and hazard appraisals are recorded and put away for the life of that demand. This
backings and gives documentation of the procedure to future reviews, traceability or
consistence related assessments.
Change endorsement/foreswearing: Once the progressions have been inspected and
examined by requestor, change control facilitator, project manager, partners and
undertaking support, it is either affirmed or denied. In the event that it is affirmed, it takes
after the underneath steps, if denied it will finish up with a "change proposition refusal."
No different advances are required now other than recording the dissent and the reason in
the change log.
Partner bolster: All partners who have been included straightforwardly with the change
procedure need to sign the change control report in help of the change. Moreover, change
control organizer/project manager will sign the record.
Page 32 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
The last archive will then be given a powerful date/new compelling date. An adaptation
control number will be allocated to guarantee the new form is being used. The report will
then be made accessible before the successful date and housed in a controlled framework,
enabling all clients to see. This is critical so appropriate preparing can be finished.
4 SCHEDULE/TIME MANAGEMENT
Time administration is another key part of dealing with a project. Task time administration
is the effective utilization of time by methods for good association, proficient profitability,
and appropriate arranging. Project administrators, who are entrusted with directing
activities from beginning to end, use these time administration abilities to finish their work
in the most productive, practical ways that could be available.
For instance, a project supervisor may build up a sequenced rundown of projects that
should be finished, at that point track worker advance through those means. Task
administrators may even actualize changes to projects when important to improve
utilization of time, and they may keep notes on what went well or what needs change to
use for future projects. Amid the arranging procedure, yields are made to represent how
project errands will be sequenced and allotted (Snyder 2014). The controlling and
observing procedure is worried about following and writing about the advance of work,
and also altering time yields to address moves and changes in the project design. At long
last, the end process includes a review of time targets.
Page 33 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
4.1 MILESTONES
The table below lists the milestones for this project, along with their estimated completion
timeframe.
Milestones Estimated Completion Timeframe
VIC Roads Infrastructure Development Thu 16-08-18
Start of the project Mon 21-08-17
Completion of Initiation phase Tue 19-09-17
Completion of planning phase Wed 25-10-17
Completion of design phase Fri 19-01-18
Completion of development phase Thu 10-05-18
Completion of implementation phase Thu 10-05-18
Completion of testing phase Fri 15-06-18
Completion of training phase Tue 17-07-18
Completion of closure phase Thu 16-08-18
Project closeout Thu 16-08-18
4.2 PROJECT SCHEDULE
WBS Task Name Duration Start Finish Predecessors Resource Names
Page 34 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
0
VIC Roads
Infrastructure
Development
259 days
Mon
21-08-
17
Thu
16-08-
18
1 Project Startup 0 days
Mon
21-08-
17
Mon
21-08-
17
Business Analyst, Project
Manager
2 Initiation phase 48 days
Mon
21-08-
17
Wed
25-10-
17
2.1
Evaluation of the
business case for
VIC Roads
9 days
Mon
21-08-
17
Thu
31-08-
17
2.1.1
Determining the
project requirements
2 days
Mon
21-08-
17
Tue
22-08-
17
1
Business Analyst, Project
Manager
2.1.2
Determining the
business requirements
3 days
Tue
29-08-
17
Thu
31-08-
17
Business Analyst
2.2
Conduction of
feasibility study
20 days
Wed
23-08-
17
Tue
19-09-
17
2.2.1 Identification of 4 days Wed Mon 4 Business Analyst, Project
Page 35 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
the police stations
23-08-
17
28-08-
17
Manager
2.2.2
Identification of
the accident prone
zones
2 days
Tue
29-08-
17
Wed
30-08-
17
7 Project Manager
2.2.3
Acquisition of
permit from police
stations
7 days
Thu
31-08-
17
Fri 08-
09-17
8 Project Manager
2.2.4
Analysis of the
existing network
infrastructure
7 days
Mon
11-09-
17
Tue
19-09-
17
9 Networking Team
2.3
Identification of
non-functional
requirements
3 days
Wed
20-09-
17
Fri
22-09-
17
2.3.1
Determining the
required resources
2 days
Wed
20-09-
17
Thu
21-09-
17
10 Project Manager
2.3.2
Estimating the
required time
1 day
Fri 22-
09-17
Fri 22-
09-17
12 Project Manager
Page 36 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
2.4
Identification of
functional
requirements
23 days
Mon
25-09-
17
Wed
25-10-
17
2.4.1
Technical
requirements
3 days
Mon
25-09-
17
Wed
27-09-
17
10,13
Development Team,
Networking Team
2.4.2
Operational
requirements
4 days
Thu
28-09-
17
Tue
03-10-
17
15 Design Team
2.4.3
Legal
requirements
3 days
Wed
04-10-
17
Fri 06-
10-17
16 Business Analyst
2.4.4
Defining the
scope of project
4 days
Mon
09-10-
17
Thu
12-10-
17
13,17 Project Manager
2.4.5
Securing
sponsorship of the
project
2 days
Fri 13-
10-17
Mon
16-10-
17
18
Business Analyst, Project
Manager
2.4.6
Developing the
preliminary budget
2 days
Tue
17-10-
17
Wed
18-10-
17
19 Project Manager
2.4.7 Developing the 3 days Thu Mon 20 Project Manager
Page 37 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
primary schedule
19-10-
17
23-10-
17
2.4.8
Obtaining
approval from client
2 days
Tue
24-10-
17
Wed
25-10-
17
21 Project Manager
2.4.9
Closure of
project initiation
phase
0 days
Wed
25-10-
17
Wed
25-10-
17
22
Business Analyst,
Networking Team, Project
Manager
3 Design phase 62 days
Thu
26-10-
17
Fri
19-01-
18
3.1
Preparing the
rough draft of network
infrastructure
7 days
Thu
26-10-
17
Fri 03-
11-17
23
Design Team, Networking
Team
3.2
Reviewing the
functional
specifications
3 days
Mon
06-11-
17
Wed
08-11-
17
25 Networking Team
3.3
Sending the
project plan for
approval
1 day
Thu
09-11-
17
Thu
09-11-
17
26 Networking Team
3.4 Obtaining the
approval from the
2 days Fri 10- Mon
13-11-
27 Business Analyst, Project
Page 38 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
state government 11-17 17 Manager
3.5
Obtaining the
approval of the state
ministry department
4 days
Tue
14-11-
17
Fri 17-
11-17
28 Business Analyst
3.6
Obtaining the
permission from
police stations
2 days
Mon
20-11-
17
Tue
21-11-
17
28,29 Project Manager
3.7
Developing the
design specification
7 days
Wed
22-11-
17
Thu
30-11-
17
29,30 Design Team
3.8
Development of
the deployment plan
36 days
Fri
01-12-
17
Fri
19-01-
18
3.8.1
Planning for
network setup
8 days
Fri 01-
12-17
Tue
12-12-
17
31
Design Team, Networking
Team
3.8.2
Planning for
securing the data
shared
7 days
Wed
13-12-
17
Thu
21-12-
17
33 Development Team
3.8.3 Planning for
data storage
2 days Fri 22-
12-17
Mon
25-12-
34 Development Team
Page 39 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
17
3.8.4
Planning for
blocking inappropriate
facilities and content
3 days
Tue
26-12-
17
Thu
28-12-
17
35 Networking Team
3.8.5
Planning for
interconnecting the
police stations and
VIC Roads
5 days
Fri 29-
12-17
Thu
04-01-
18
36 Design Team
3.8.6
Planning for
implementing cloud
services
6 days
Fri 05-
01-18
Fri 12-
01-18
37
Design Team,
Development Team
3.8.7
Proposal of the
network design
3 days
Mon
15-01-
18
Wed
17-01-
18
38,31 Networking Team
3.8.8
Obtaining
approval of the design
2 days
Thu
18-01-
18
Fri 19-
01-18
39
Networking Team, Project
Manager
3.8.9
End of project
planning phase
0 days
Fri 19-
01-18
Fri 19-
01-18
40
Business Analyst, Project
Manager
4 Project
development phase
79 days Mon
22-01-
Thu
10-05-
Page 40 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
18 18
4.1
Implementing the
software and hardware
requirements of the
network
16 days
Mon
22-01-
18
Mon
12-02-
18
41
Design Team,
Development Team
4.2
Establishing
connection between
the police stations and
VIC Roads
9 days
Tue
13-02-
18
Fri 23-
02-18
43 Networking Team
4.3
Developing the
network architecture
12 days
Mon
26-02-
18
Tue
13-03-
18
44
Design Team, Networking
Team
4.4
Implementing
design for network
and internet services
42 days
Wed
14-03-
18
Thu
10-05-
18
4.4.1
Implementation
of infrastructural
design for internet
services
14 days
Wed
14-03-
18
Mon
02-04-
18
45
Design Team,
Implementation Team
Page 41 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
4.4.2
Connecting the
established network
via cloud services
20 days
Tue
03-04-
18
Mon
30-04-
18
47
Implementation Team,
Networking Team
4.4.3
Connecting the
network with the state
ministry department
6 days
Tue
03-04-
18
Tue
10-04-
18
47
Implementation Team,
Networking Team
4.4.4
Implementation
of data storage facility
4 days
Wed
11-04-
18
Mon
16-04-
18
49
Development Team,
Implementation Team
4.4.5
Implementing
data security
3 days
Tue
17-04-
18
Thu
19-04-
18
50
Development Team,
Implementation Team
4.4.6
Provide blocking
and screening of
inappropriate contents
7 days
Fri 20-
04-18
Mon
30-04-
18
51 Implementation Team
4.4.7
Implementation
of data security
8 days
Tue
01-05-
18
Thu
10-05-
18
52 Implementation Team
4.4.8
Closure of
development phase
0 days
Thu
10-05-
18
Thu
10-05-
18
53
Business Analyst, Project
Manager
Page 42 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
5 Testing phase 26 days
Fri
11-05-
18
Fri
15-06-
18
5.1
Develop the
testing module
6 days
Fri 11-
05-18
Fri 18-
05-18
54 Development Team, Tester
5.2
Integrate the
testing modules within
the network
5 days
Mon
21-05-
18
Fri 25-
05-18
56 System Analyst, Tester
5.3
Test for effective
communication
6 days
Mon
28-05-
18
Mon
04-06-
18
57 Development Team, Tester
5.4
Test for content
restriction
2 days
Tue
05-06-
18
Wed
06-06-
18
58 System Analyst, Tester
5.5
Test for
vulnerability attacks
4 days
Thu
07-06-
18
Tue
12-06-
18
59 Development Team, Tester
5.6
Test module
integration
3 days
Wed
13-06-
18
Fri 15-
06-18
60 System Analyst, Tester
5.7 End of project 0 days Fri 15- Fri 15- 61 Business Analyst, Project
Page 43 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
testing phase 06-18 06-18 Manager
6 Training phase 22 days
Mon
18-06-
18
Tue
17-07-
18
6.1
Developing the
training specifications
for the VIC Roads,
Police personnel’s and
governmental
authorities
5 days
Mon
18-06-
18
Fri 22-
06-18
62
Design Team, Technical
Writer
6.2
Identification of
the training procedure
6 days
Mon
25-06-
18
Mon
02-07-
18
64
Business Analyst,
Development Team
6.3
Developing the
materials for training
4 days
Tue
03-07-
18
Fri 06-
07-18
65
Business Analyst,
Development Team,
Technical Writer
6.4
Conducting
usability study
3 days
Mon
09-07-
18
Wed
11-07-
18
66 Business Analyst
Page 44 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
6.5 Provide training 4 days
Thu
12-07-
18
Tue
17-07-
18
67,66
Development Team,
Networking Team, Project
Manager
6.6
Closure of training
phase
0 days
Tue
17-07-
18
Tue
17-07-
18
68
Business Analyst, Project
Manager
7
Project closure
phase
22 days
Wed
18-07-
18
Thu
16-08-
18
7.1
Developing
documentation
14 days
Wed
18-07-
18
Mon
06-08-
18
7.1.1
Developing the
network
documentation
4 days
Wed
18-07-
18
Mon
23-07-
18
69
Networking Team,
Technical Writer
7.1.2
Reviewing the
documentation
2 days
Tue
24-07-
18
Wed
25-07-
18
72
Business Analyst,
Technical Writer
7.1.3
Developing user
specific manuals
6 days
Thu
26-07-
18
Thu
02-08-
18
73
Development Team,
Technical Writer
7.1.4 Audit of the 2 days Fri 03- Mon 74 Business Analyst, Project
Page 45 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
project 08-18
06-08-
18
Manager
7.2 Project handover 8 days
Tue
07-08-
18
Thu
16-08-
18
7.2.1
Implementation
of the network and
internet facilities
2 days
Tue
07-08-
18
Wed
08-08-
18
75
Development Team,
Implementation Team
7.2.2
Development of
network maintenance
team
1 day
Thu
09-08-
18
Thu
09-08-
18
77
Networking Team, Project
Manager
7.2.3
Reviewing the
designed network
3 days
Fri 10-
08-18
Tue
14-08-
18
78
Business Analyst,
Networking Team
7.2.4
Project team
sign off
1 day
Wed
15-08-
18
Wed
15-08-
18
79
Business Analyst, Project
Manager
7.2.5
End of project
closure phase
1 day
Thu
16-08-
18
Thu
16-08-
18
80 Project Manager
8 Stop project 0 days Thu
16-08-
Thu
16-08-
81 Business Analyst, Project
Page 46 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
18 18 Manager
Page 47 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
4.2.1 Dependencies
WBS Task Name Duration Start Finish Predecessors
WBS
Predecessors
0
VIC Roads
Infrastructure
Development
259 days
Mon
21-08-
17
Thu 16-
08-18
1 Project Startup 0 days
Mon
21-08-
17
Mon 21-
08-17
2 Initiation phase 48 days
Mon
21-08-
17
Wed 25-
10-17
2.1
Evaluation of the
business case for VIC
Roads
9 days
Mon
21-08-
17
Thu 31-
08-17
2.1.1
Determining the
project requirements
2 days
Mon
21-08-
17
Tue 22-
08-17
1 1
2.1.2
Determining the
business requirements
3 days
Tue
29-08-
17
Thu 31-
08-17
Page 48 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
2.2
Conduction of
feasibility study
20 days
Wed
23-08-
17
Tue 19-
09-17
2.2.1
Identification of
the police stations
4 days
Wed
23-08-
17
Mon 28-
08-17
4 2.1.1
2.2.2
Identification of
the accident prone
zones
2 days
Tue
29-08-
17
Wed 30-
08-17
7 2.2.1
2.2.3
Acquisition of
permit from police
stations
7 days
Thu
31-08-
17
Fri 08-
09-17
8 2.2.2
2.2.4
Analysis of the
existing network
infrastructure
7 days
Mon
11-09-
17
Tue 19-
09-17
9 2.2.3
2.3
Identification of
non-functional
requirements
3 days
Wed
20-09-
17
Fri 22-
09-17
2.3.1
Determining the
required resources
2 days
Wed
20-09-
17
Thu 21-
09-17
10 2.2.4
2.3.2 Estimating the 1 day Fri 22- Fri 22- 12 2.3.1
Page 49 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
required time 09-17 09-17
2.4
Identification of
functional
requirements
23 days
Mon
25-09-
17
Wed 25-
10-17
2.4.1
Technical
requirements
3 days
Mon
25-09-
17
Wed 27-
09-17
10,13 2.2.4,2.3.2
2.4.2
Operational
requirements
4 days
Thu
28-09-
17
Tue 03-
10-17
15 2.4.1
2.4.3
Legal
requirements
3 days
Wed
04-10-
17
Fri 06-
10-17
16 2.4.2
2.4.4
Defining the
scope of project
4 days
Mon
09-10-
17
Thu 12-
10-17
13,17 2.3.2,2.4.3
2.4.5
Securing
sponsorship of the
project
2 days
Fri 13-
10-17
Mon 16-
10-17
18 2.4.4
2.4.6 Developing the
preliminary budget
2 days Tue
17-10-
Wed 18-
10-17
19 2.4.5
Page 50 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
17
2.4.7
Developing the
primary schedule
3 days
Thu
19-10-
17
Mon 23-
10-17
20 2.4.6
2.4.8
Obtaining
approval from client
2 days
Tue
24-10-
17
Wed 25-
10-17
21 2.4.7
2.4.9
Closure of project
initiation phase
0 days
Wed
25-10-
17
Wed 25-
10-17
22 2.4.8
3 Design phase 62 days
Thu
26-10-
17
Fri 19-
01-18
3.1
Preparing the rough
draft of network
infrastructure
7 days
Thu
26-10-
17
Fri 03-
11-17
23 2.4.9
3.2
Reviewing the
functional
specifications
3 days
Mon
06-11-
17
Wed 08-
11-17
25 3.1
3.3 Sending the project
plan for approval
1 day Thu
09-11-
Thu 09-
11-17
26 3.2
Page 51 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
17
3.4
Obtaining the
approval from the state
government
2 days
Fri 10-
11-17
Mon 13-
11-17
27 3.3
3.5
Obtaining the
approval of the state
ministry department
4 days
Tue
14-11-
17
Fri 17-
11-17
28 3.4
3.6
Obtaining the
permission from police
stations
2 days
Mon
20-11-
17
Tue 21-
11-17
28,29 3.4,3.5
3.7
Developing the
design specification
7 days
Wed
22-11-
17
Thu 30-
11-17
29,30 3.5,3.6
3.8
Development of
the deployment plan
36 days
Fri 01-
12-17
Fri 19-
01-18
3.8.1
Planning for
network setup
8 days
Fri 01-
12-17
Tue 12-
12-17
31 3.7
3.8.2
Planning for
securing the data shared
7 days
Wed
13-12-
17
Thu 21-
12-17
33 3.8.1
3.8.3 Planning for data 2 days Fri 22- Mon 25- 34 3.8.2
Page 52 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
storage 12-17 12-17
3.8.4
Planning for
blocking inappropriate
facilities and content
3 days
Tue
26-12-
17
Thu 28-
12-17
35 3.8.3
3.8.5
Planning for
interconnecting the
police stations and VIC
Roads
5 days
Fri 29-
12-17
Thu 04-
01-18
36 3.8.4
3.8.6
Planning for
implementing cloud
services
6 days
Fri 05-
01-18
Fri 12-
01-18
37 3.8.5
3.8.7
Proposal of the
network design
3 days
Mon
15-01-
18
Wed 17-
01-18
38,31 3.8.6,3.7
3.8.8
Obtaining
approval of the design
2 days
Thu
18-01-
18
Fri 19-
01-18
39 3.8.7
3.8.9
End of project
planning phase
0 days
Fri 19-
01-18
Fri 19-
01-18
40 3.8.8
4 Project development
phase
79 days Mon
22-01-
Thu 10-
05-18
Page 53 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
18
4.1
Implementing the
software and hardware
requirements of the
network
16 days
Mon
22-01-
18
Mon 12-
02-18
41 3.8.9
4.2
Establishing
connection between the
police stations and VIC
Roads
9 days
Tue
13-02-
18
Fri 23-
02-18
43 4.1
4.3
Developing the
network architecture
12 days
Mon
26-02-
18
Tue 13-
03-18
44 4.2
4.4
Implementing
design for network
and internet services
42 days
Wed
14-03-
18
Thu 10-
05-18
4.4.1
Implementation
of infrastructural design
for internet services
14 days
Wed
14-03-
18
Mon 02-
04-18
45 4.3
4.4.2
Connecting the
established network via
cloud services
20 days
Tue
03-04-
18
Mon 30-
04-18
47 4.4.1
4.4.3 Connecting the 6 days Tue Tue 10- 47 4.4.1
Page 54 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
network with the state
ministry department
03-04-
18
04-18
4.4.4
Implementation
of data storage facility
4 days
Wed
11-04-
18
Mon 16-
04-18
49 4.4.3
4.4.5
Implementing
data security
3 days
Tue
17-04-
18
Thu 19-
04-18
50 4.4.4
4.4.6
Provide blocking
and screening of
inappropriate contents
7 days
Fri 20-
04-18
Mon 30-
04-18
51 4.4.5
4.4.7
Implementation
of data security
8 days
Tue
01-05-
18
Thu 10-
05-18
52 4.4.6
4.4.8
Closure of
development phase
0 days
Thu
10-05-
18
Thu 10-
05-18
53 4.4.7
5 Testing phase 26 days
Fri 11-
05-18
Fri 15-
06-18
5.1
Develop the testing
module
6 days
Fri 11-
05-18
Fri 18-
05-18
54 4.4.8
5.2 Integrate the testing 5 days Mon Fri 25- 56 5.1
Page 55 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
modules within the
network
21-05-
18
05-18
5.3
Test for effective
communication
6 days
Mon
28-05-
18
Mon 04-
06-18
57 5.2
5.4
Test for content
restriction
2 days
Tue
05-06-
18
Wed 06-
06-18
58 5.3
5.5
Test for
vulnerability attacks
4 days
Thu
07-06-
18
Tue 12-
06-18
59 5.4
5.6
Test module
integration
3 days
Wed
13-06-
18
Fri 15-
06-18
60 5.5
5.7
End of project
testing phase
0 days
Fri 15-
06-18
Fri 15-
06-18
61 5.6
6 Training phase 22 days
Mon
18-06-
18
Tue 17-
07-18
6.1 Developing the
training specifications
for the VIC Roads,
5 days Mon
18-06-
Fri 22-
06-18
62 5.7
Page 56 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Police personnel’s and
governmental
authorities
18
6.2
Identification of the
training procedure
6 days
Mon
25-06-
18
Mon 02-
07-18
64 6.1
6.3
Developing the
materials for training
4 days
Tue
03-07-
18
Fri 06-
07-18
65 6.2
6.4
Conducting
usability study
3 days
Mon
09-07-
18
Wed 11-
07-18
66 6.3
6.5 Provide training 4 days
Thu
12-07-
18
Tue 17-
07-18
67,66 6.4,6.3
6.6
Closure of training
phase
0 days
Tue
17-07-
18
Tue 17-
07-18
68 6.5
7
Project closure
phase
22 days
Wed
18-07-
18
Thu 16-
08-18
Page 57 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
7.1
Developing
documentation
14 days
Wed
18-07-
18
Mon 06-
08-18
7.1.1
Developing the
network documentation
4 days
Wed
18-07-
18
Mon 23-
07-18
69 6.6
7.1.2
Reviewing the
documentation
2 days
Tue
24-07-
18
Wed 25-
07-18
72 7.1.1
7.1.3
Developing user
specific manuals
6 days
Thu
26-07-
18
Thu 02-
08-18
73 7.1.2
7.1.4
Audit of the
project
2 days
Fri 03-
08-18
Mon 06-
08-18
74 7.1.3
7.2 Project handover 8 days
Tue
07-08-
18
Thu 16-
08-18
7.2.1
Implementation
of the network and
internet facilities
2 days
Tue
07-08-
18
Wed 08-
08-18
75 7.1.4
7.2.2 Development of
network maintenance
1 day Thu
09-08-
Thu 09- 77 7.2.1
Page 58 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
team 18 08-18
7.2.3
Reviewing the
designed network
3 days
Fri 10-
08-18
Tue 14-
08-18
78 7.2.2
7.2.4
Project team sign
off
1 day
Wed
15-08-
18
Wed 15-
08-18
79 7.2.3
7.2.5
End of project
closure phase
1 day
Thu
16-08-
18
Thu 16-
08-18
80 7.2.4
8 Stop project 0 days
Thu
16-08-
18
Thu 16-
08-18
81 7.2.5
5 COST/BUDGET MANAGEMENT
WBS Task Name Duration Start Finish Predecessors
Resource
Names
Cost
0
VIC Roads
Infrastructure
Development
259 days
Mon 21-
08-17
Thu 16-
08-18
$309,560.00
1 Project
Startup
0 days Mon 21-
08-17
Mon 21-
08-17
Business
Analyst, Project
$0.00
Page 59 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Manager
2
Initiation
phase
48 days
Mon 21-
08-17
Wed 25-
10-17
$41,960.00
2.1
Evaluation of
the business case
for VIC Roads
9 days
Mon 21-
08-17
Thu 31-
08-17
$4,960.00
2.1.1
Determining
the project
requirements
2 days
Mon 21-
08-17
Tue 22-
08-17
1
Business
Analyst, Project
Manager
$2,800.00
2.1.2
Determining
the business
requirements
3 days
Tue 29-08-
17
Thu 31-
08-17
Business Analyst $2,160.00
2.2
Conduction
of feasibility
study
20 days
Wed 23-
08-17
Tue 19-
09-17
$16,480.00
2.2.1 Identification of
the police stations
4 days
Wed 23-
08-17
Mon 28-
08-17
4
Business
Analyst, Project
Manager
$5,600.00
2.2.2
Identification of
the accident
2 days Tue 29-08-
17
Wed 30-
08-17
7 Project Manager $1,360.00
Page 60 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
prone zones
2.2.3
Acquisition
of permit from
police stations
7 days
Thu 31-08-
17
Fri 08-09-
17
8 Project Manager $4,760.00
2.2.4
Analysis of
the existing
network
infrastructure
7 days
Mon 11-
09-17
Tue 19-
09-17
9
Networking
Team
$4,760.00
2.3
Identification
of non-
functional
requirements
3 days
Wed 20-
09-17
Fri 22-09-
17
$2,040.00
2.3.1
Determining
the required
resources
2 days
Wed 20-
09-17
Thu 21-
09-17
10 Project Manager $1,360.00
2.3.2
Estimating
the required time
1 day
Fri 22-09-
17
Fri 22-09-
17
12 Project Manager $680.00
2.4
Identification
of functional
requirements
23 days
Mon 25-
09-17
Wed 25-
10-17
$18,480.00
2.4.1 Technical
requirements
3 days Mon 25-
09-17
Wed 27-
09-17
10,13 Development
Team,
$3,960.00
Page 61 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Networking
Team
2.4.2
Operational
requirements
4 days
Thu 28-09-
17
Tue 03-
10-17
15 Design Team $2,080.00
2.4.3
Legal
requirements
3 days
Wed 04-
10-17
Fri 06-10-
17
16 Business Analyst $2,160.00
2.4.4
Defining the
scope of project
4 days
Mon 09-
10-17
Thu 12-
10-17
13,17 Project Manager $2,720.00
2.4.5
Securing
sponsorship of
the project
2 days
Fri 13-10-
17
Mon 16-
10-17
18
Business
Analyst, Project
Manager
$2,800.00
2.4.6
Developing
the preliminary
budget
2 days
Tue 17-10-
17
Wed 18-
10-17
19 Project Manager $1,360.00
2.4.7
Developing
the primary
schedule
3 days
Thu 19-10-
17
Mon 23-
10-17
20 Project Manager $2,040.00
2.4.8
Obtaining
approval from
client
2 days
Tue 24-10-
17
Wed 25-
10-17
21 Project Manager $1,360.00
2.4.9 Closure of
project initiation
0 days Wed 25- Wed 25- 22 Business
Analyst,
$0.00
Page 62 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
phase 10-17 10-17
Networking
Team, Project
Manager
3 Design phase 62 days
Thu 26-10-
17
Fri 19-01-
18
$53,520.00
3.1
Preparing the
rough draft of
network
infrastructure
7 days
Thu 26-10-
17
Fri 03-11-
17
23
Design Team,
Networking
Team
$8,400.00
3.2
Reviewing the
functional
specifications
3 days
Mon 06-
11-17
Wed 08-
11-17
25
Networking
Team
$2,040.00
3.3
Sending the
project plan for
approval
1 day
Thu 09-11-
17
Thu 09-
11-17
26
Networking
Team
$680.00
3.4
Obtaining the
approval from the
state government
2 days
Fri 10-11-
17
Mon 13-
11-17
27
Business
Analyst, Project
Manager
$2,800.00
3.5 Obtaining the
approval of the
state ministry
4 days Tue 14-11-
17
Fri 17-11-
17
28 Business Analyst $2,880.00
Page 63 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
department
3.6
Obtaining the
permission from
police stations
2 days
Mon 20-
11-17
Tue 21-
11-17
28,29 Project Manager $1,360.00
3.7
Developing
the design
specification
7 days
Wed 22-
11-17
Thu 30-
11-17
29,30 Design Team $3,640.00
3.8
Development
of the
deployment plan
36 days
Fri 01-12-
17
Fri 19-01-
18
$31,720.00
3.8.1
Planning for
network setup
8 days
Fri 01-12-
17
Tue 12-
12-17
31
Design Team,
Networking
Team
$9,600.00
3.8.2
Planning for
securing the data
shared
7 days
Wed 13-
12-17
Thu 21-
12-17
33
Development
Team
$4,480.00
3.8.3
Planning for
data storage
2 days
Fri 22-12-
17
Mon 25-
12-17
34
Development
Team
$1,280.00
3.8.4 Planning for
blocking
inappropriate
facilities and
3 days Tue 26-12-
17
Thu 28-
12-17
35 Networking
Team
$2,040.00
Page 64 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
content
3.8.5
Planning for
interconnecting
the police stations
and VIC Roads
5 days
Fri 29-12-
17
Thu 04-
01-18
36 Design Team $2,600.00
3.8.6
Planning for
implementing
cloud services
6 days
Fri 05-01-
18
Fri 12-01-
18
37
Design Team,
Development
Team
$6,960.00
3.8.7
Proposal of
the network
design
3 days
Mon 15-
01-18
Wed 17-
01-18
38,31
Networking
Team
$2,040.00
3.8.8
Obtaining
approval of the
design
2 days
Thu 18-01-
18
Fri 19-01-
18
39
Networking
Team, Project
Manager
$2,720.00
3.8.9
End of
project planning
phase
0 days
Fri 19-01-
18
Fri 19-01-
18
40
Business
Analyst, Project
Manager
$0.00
4
Project
development
phase
79 days
Mon 22-
01-18
Thu 10-
05-18
$115,640.00
4.1 Implementing
the software and
16 days Mon 22- Mon 12- 41 Design Team,
Development
$18,560.00
Page 65 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
hardware
requirements of
the network
01-18 02-18 Team
4.2
Establishing
connection
between the
police stations
and VIC Roads
9 days
Tue 13-02-
18
Fri 23-02-
18
43
Networking
Team
$6,120.00
4.3
Developing
the network
architecture
12 days
Mon 26-
02-18
Tue 13-
03-18
44
Design Team,
Networking
Team
$14,400.00
4.4
Implementing
design for
network and
internet services
42 days
Wed 14-
03-18
Thu 10-
05-18
$76,560.00
4.4.1
Implementation
of infrastructural
design for
internet services
14 days
Wed 14-
03-18
Mon 02-
04-18
45
Design Team,
Implementation
Team
$17,920.00
4.4.2 Connecting 20 days Tue 03-04- Mon 30- 47 Implementation $28,800.00
Page 66 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
the established
network via cloud
services
18 04-18
Team,
Networking
Team
4.4.3
Connecting
the network with
the state ministry
department
6 days
Tue 03-04-
18
Tue 10-
04-18
47
Implementation
Team,
Networking
Team
$8,640.00
4.4.4
Implementation
of data storage
facility
4 days
Wed 11-
04-18
Mon 16-
04-18
49
Development
Team,
Implementation
Team
$5,600.00
4.4.5 Implementing
data security
3 days
Tue 17-04-
18
Thu 19-
04-18
50
Development
Team,
Implementation
Team
$4,200.00
4.4.6
Provide
blocking and
screening of
inappropriate
contents
7 days
Fri 20-04-
18
Mon 30-
04-18
51
Implementation
Team
$5,320.00
4.4.7
Implementation
8 days Tue 01-05-
18
Thu 10-
05-18
52 Implementation
Team
$6,080.00
Page 67 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
of data security
4.4.8
Closure of
development
phase
0 days
Thu 10-05-
18
Thu 10-
05-18
53
Business
Analyst, Project
Manager
$0.00
5 Testing phase 26 days
Fri 11-05-
18
Fri 15-06-
18
$38,240.00
5.1
Develop the
testing module
6 days
Fri 11-05-
18
Fri 18-05-
18
54
Development
Team, Tester
$8,640.00
5.2
Integrate the
testing modules
within the
network
5 days
Mon 21-
05-18
Fri 25-05-
18
56
System Analyst,
Tester
$7,600.00
5.3
Test for
effective
communication
6 days
Mon 28-
05-18
Mon 04-
06-18
57
Development
Team, Tester
$8,640.00
5.4
Test for
content restriction
2 days
Tue 05-06-
18
Wed 06-
06-18
58
System Analyst,
Tester
$3,040.00
5.5
Test for
vulnerability
attacks
4 days
Thu 07-06-
18
Tue 12-
06-18
59
Development
Team, Tester
$5,760.00
5.6 Test module 3 days Wed 13- Fri 15-06- 60 System Analyst, $4,560.00
Page 68 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
integration 06-18 18 Tester
5.7
End of project
testing phase
0 days
Fri 15-06-
18
Fri 15-06-
18
61
Business
Analyst, Project
Manager
$0.00
6 Training phase 22 days
Mon 18-
06-18
Tue 17-
07-18
$31,760.00
6.1
Developing
the training
specifications for
the VIC Roads,
Police
personnel’s and
governmental
authorities
5 days
Mon 18-
06-18
Fri 22-06-
18
62
Design Team,
Technical Writer
$5,600.00
6.2
Identification
of the training
procedure
6 days
Mon 25-
06-18
Mon 02-
07-18
64
Business
Analyst,
Development
Team
$8,160.00
6.3 Developing
the materials for
training
4 days Tue 03-07-
18
Fri 06-07-
18
65 Business
Analyst,
Development
Team, Technical
$7,840.00
Page 69 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Writer
6.4
Conducting
usability study
3 days
Mon 09-
07-18
Wed 11-
07-18
66 Business Analyst $2,160.00
6.5
Provide
training
4 days
Thu 12-07-
18
Tue 17-
07-18
67,66
Development
Team,
Networking
Team, Project
Manager
$8,000.00
6.6
Closure of
training phase
0 days
Tue 17-07-
18
Tue 17-
07-18
68
Business
Analyst, Project
Manager
$0.00
7
Project closure
phase
22 days
Wed 18-
07-18
Thu 16-
08-18
$28,440.00
7.1
Developing
documentation
14 days
Wed 18-
07-18
Mon 06-
08-18
$18,000.00
7.1.1
Developing
the network
documentation
4 days
Wed 18-
07-18
Mon 23-
07-18
69
Networking
Team, Technical
Writer
$5,120.00
7.1.2
Reviewing
the
documentation
2 days
Tue 24-07-
18
Wed 25-
07-18
72
Business
Analyst,
Technical Writer
$2,640.00
7.1.3 Developing 6 days Thu 26-07- Thu 02- 73 Development $7,440.00
Page 70 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
user specific
manuals
18 08-18
Team, Technical
Writer
7.1.4
Audit of the
project
2 days
Fri 03-08-
18
Mon 06-
08-18
74
Business
Analyst, Project
Manager
$2,800.00
7.2
Project
handover
8 days
Tue 07-08-
18
Thu 16-
08-18
$10,440.00
7.2.1
Implementation
of the network
and internet
facilities
2 days
Tue 07-08-
18
Wed 08-
08-18
75
Development
Team,
Implementation
Team
$2,800.00
7.2.2
Development of
network
maintenance team
1 day
Thu 09-08-
18
Thu 09-
08-18
77
Networking
Team, Project
Manager
$1,360.00
7.2.3
Reviewing
the designed
network
3 days
Fri 10-08-
18
Tue 14-
08-18
78
Business
Analyst,
Networking
Team
$4,200.00
7.2.4 Project team
sign off
1 day Wed 15-
08-18
Wed 15-
08-18
79 Business
Analyst, Project
$1,400.00
Page 71 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Manager
7.2.5
End of
project closure
phase
1 day
Thu 16-08-
18
Thu 16-
08-18
80 Project Manager $680.00
8 Stop project 0 days
Thu 16-08-
18
Thu 16-
08-18
81
Business
Analyst, Project
Manager
$0.00
6 QUALITY MANAGEMENT
For observing the work and execution of the task regarding the underlying created course
of events, the project manager has created and set benchmark in the project time created in
Microsoft Project. As far as observing the initial two months of the task, the gauge for the
initial two month was set and their separate fluctuation were computed (Anantatmula and
Webb 2016). From figuring the fluctuation, it has been discovered that aggregate 9% of
whole work have been finished. The project has been observed frequently and the data of
the task is refreshed in the project planned inside each two days.
WBS Task Name Duration Start Finish
% Work
Complete
0 VIC Roads Infrastructure Development 259 days Mon 21-08-17 Thu 16-08-18 9%
1 Project Startup 0 days Mon 21-08-17 Mon 21-08- 100%
Page 72 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
17
2 Initiation phase 48 days Mon 21-08-17
Wed 25-10-
17
68%
2.1
Evaluation of the business case for
VIC Roads
9 days Mon 21-08-17 Thu 31-08-17 100%
2.1.1 Determining the project requirements 2 days Mon 21-08-17 Tue 22-08-17 100%
2.1.2
Determining the business
requirements
3 days Tue 29-08-17 Thu 31-08-17 100%
2.2 Conduction of feasibility study 20 days Wed 23-08-17 Tue 19-09-17 100%
2.2.1 Identification of the police stations 4 days Wed 23-08-17 Mon 28-08-17 100%
2.2.2
Identification of the accident prone
zones
2 days Tue 29-08-17 Wed 30-08-17 100%
2.2.3
Acquisition of permit from police
stations
7 days Thu 31-08-17 Fri 08-09-17 100%
2.2.4
Analysis of the existing network
infrastructure
7 days Mon 11-09-17 Tue 19-09-17 100%
2.3
Identification of non-functional
requirements
3 days Wed 20-09-17 Fri 22-09-17 100%
2.3.1 Determining the required resources 2 days Wed 20-09-17 Thu 21-09-17 100%
Page 73 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
2.3.2 Estimating the required time 1 day Fri 22-09-17 Fri 22-09-17 100%
2.4
Identification of functional
requirements
23 days Mon 25-09-17
Wed 25-10-
17
29%
2.4.1 Technical requirements 3 days Mon 25-09-17 Wed 27-09-17 100%
2.4.2 Operational requirements 4 days Thu 28-09-17 Tue 03-10-17 50%
2.4.3 Legal requirements 3 days Wed 04-10-17 Fri 06-10-17 0%
2.4.4 Defining the scope of project 4 days Mon 09-10-17 Thu 12-10-17 0%
2.4.5 Securing sponsorship of the project 2 days Fri 13-10-17 Mon 16-10-17 0%
2.4.6 Developing the preliminary budget 2 days Tue 17-10-17 Wed 18-10-17 0%
2.4.7 Developing the primary schedule 3 days Thu 19-10-17 Mon 23-10-17 0%
2.4.8 Obtaining approval from client 2 days Tue 24-10-17 Wed 25-10-17 0%
2.4.9 Closure of project initiation phase 0 days Wed 25-10-17 Wed 25-10-17 0%
3 Design phase 62 days Thu 26-10-17 Fri 19-01-18 0%
3.1
Preparing the rough draft of network
infrastructure
7 days Thu 26-10-17 Fri 03-11-17 0%
3.2 Reviewing the functional specifications 3 days Mon 06-11-17 Wed 08-11-17 0%
3.3 Sending the project plan for approval 1 day Thu 09-11-17 Thu 09-11-17 0%
Page 74 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
3.4
Obtaining the approval from the state
government
2 days Fri 10-11-17 Mon 13-11-17 0%
3.5
Obtaining the approval of the state
ministry department
4 days Tue 14-11-17 Fri 17-11-17 0%
3.6
Obtaining the permission from police
stations
2 days Mon 20-11-17 Tue 21-11-17 0%
3.7 Developing the design specification 7 days Wed 22-11-17 Thu 30-11-17 0%
3.8 Development of the deployment plan 36 days Fri 01-12-17 Fri 19-01-18 0%
3.8.1 Planning for network setup 8 days Fri 01-12-17 Tue 12-12-17 0%
3.8.2 Planning for securing the data shared 7 days Wed 13-12-17 Thu 21-12-17 0%
3.8.3 Planning for data storage 2 days Fri 22-12-17 Mon 25-12-17 0%
3.8.4
Planning for blocking inappropriate
facilities and content
3 days Tue 26-12-17 Thu 28-12-17 0%
3.8.5
Planning for interconnecting the
police stations and VIC Roads
5 days Fri 29-12-17 Thu 04-01-18 0%
3.8.6
Planning for implementing cloud
services
6 days Fri 05-01-18 Fri 12-01-18 0%
3.8.7 Proposal of the network design 3 days Mon 15-01-18 Wed 17-01-18 0%
Page 75 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
3.8.8 Obtaining approval of the design 2 days Thu 18-01-18 Fri 19-01-18 0%
3.8.9 End of project planning phase 0 days Fri 19-01-18 Fri 19-01-18 0%
4 Project development phase 79 days Mon 22-01-18 Thu 10-05-18 0%
4.1
Implementing the software and
hardware requirements of the network
16 days Mon 22-01-18 Mon 12-02-18 0%
4.2
Establishing connection between the
police stations and VIC Roads
9 days Tue 13-02-18 Fri 23-02-18 0%
4.3 Developing the network architecture 12 days Mon 26-02-18 Tue 13-03-18 0%
4.4
Implementing design for network and
internet services
42 days Wed 14-03-18 Thu 10-05-18 0%
4.4.1
Implementation of infrastructural
design for internet services
14 days Wed 14-03-18 Mon 02-04-18 0%
4.4.2
Connecting the established network
via cloud services
20 days Tue 03-04-18 Mon 30-04-18 0%
4.4.3
Connecting the network with the state
ministry department
6 days Tue 03-04-18 Tue 10-04-18 0%
4.4.4 Implementation of data storage 4 days Wed 11-04-18 Mon 16-04-18 0%
Page 76 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
facility
4.4.5 Implementing data security 3 days Tue 17-04-18 Thu 19-04-18 0%
4.4.6
Provide blocking and screening of
inappropriate contents
7 days Fri 20-04-18 Mon 30-04-18 0%
4.4.7 Implementation of data security 8 days Tue 01-05-18 Thu 10-05-18 0%
4.4.8 Closure of development phase 0 days Thu 10-05-18 Thu 10-05-18 0%
5 Testing phase 26 days Fri 11-05-18 Fri 15-06-18 0%
5.1 Develop the testing module 6 days Fri 11-05-18 Fri 18-05-18 0%
5.2
Integrate the testing modules within the
network
5 days Mon 21-05-18 Fri 25-05-18 0%
5.3 Test for effective communication 6 days Mon 28-05-18 Mon 04-06-18 0%
5.4 Test for content restriction 2 days Tue 05-06-18 Wed 06-06-18 0%
5.5 Test for vulnerability attacks 4 days Thu 07-06-18 Tue 12-06-18 0%
5.6 Test module integration 3 days Wed 13-06-18 Fri 15-06-18 0%
5.7 End of project testing phase 0 days Fri 15-06-18 Fri 15-06-18 0%
6 Training phase 22 days Mon 18-06-18 Tue 17-07-18 0%
6.1 Developing the training specifications
for the VIC Roads, Police personnel’s and
5 days Mon 18-06-18 Fri 22-06-18 0%
Page 77 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
governmental authorities
6.2 Identification of the training procedure 6 days Mon 25-06-18 Mon 02-07-18 0%
6.3 Developing the materials for training 4 days Tue 03-07-18 Fri 06-07-18 0%
6.4 Conducting usability study 3 days Mon 09-07-18 Wed 11-07-18 0%
6.5 Provide training 4 days Thu 12-07-18 Tue 17-07-18 0%
6.6 Closure of training phase 0 days Tue 17-07-18 Tue 17-07-18 0%
7 Project closure phase 22 days Wed 18-07-18 Thu 16-08-18 0%
7.1 Developing documentation 14 days Wed 18-07-18
Mon 06-08-
18
0%
7.1.1
Developing the network
documentation
4 days Wed 18-07-18 Mon 23-07-18 0%
7.1.2 Reviewing the documentation 2 days Tue 24-07-18 Wed 25-07-18 0%
7.1.3 Developing user specific manuals 6 days Thu 26-07-18 Thu 02-08-18 0%
7.1.4 Audit of the project 2 days Fri 03-08-18 Mon 06-08-18 0%
7.2 Project handover 8 days Tue 07-08-18 Thu 16-08-18 0%
7.2.1
Implementation of the network and
internet facilities
2 days Tue 07-08-18 Wed 08-08-18 0%
7.2.2 Development of network maintenance 1 day Thu 09-08-18 Thu 09-08-18 0%
Page 78 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
team
7.2.3 Reviewing the designed network 3 days Fri 10-08-18 Tue 14-08-18 0%
7.2.4 Project team sign off 1 day Wed 15-08-18 Wed 15-08-18 0%
7.2.5 End of project closure phase 1 day Thu 16-08-18 Thu 16-08-18 0%
8 Stop project 0 days Thu 16-08-18 Thu 16-08-18 0%
Quality Control: So as to control the required standard and nature of the created system
and application, the project manager consistent screens and reviews the project status.
Aside from that the system design conducts general test and examination for following the
proposed organize have achieved the required measures (Kerzner 2017). All the procedure
and practices will be recorded in points of interest by the project director. Further, the
project manager uses the timetable and behaviors normal cost examination for
guaranteeing appropriate income for fruitful consummation.
Process Acceptable Standard Project Phase Interval of
Evaluation
Network
Designing
The network would provide 99.99%
availability and seamless connectivity
between the schools and libraries;
The network will integrate age filtering
Planning Phase As required
Page 79 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Process Acceptable Standard Project Phase Interval of
Evaluation
logic;
The students will be able to access
internet through the proposed system;
Network
Deployment
The network will effectively implement
“virtual private network” for ensuring
security and reliability through the
network;
The network will be implemented with
robust security measurement and
firewall for securing the system from
external attack and virus.
Deployment
Phase
During Testing
and analysis
Project
Management
The project needs to be completed and
deployed within one year time and
allocated budget.
Throughput the
project
As required
7 HUMAN RESOURCE MANAGEMENT
As indicated by the Project Management Institute, human asset administration (HRM)
comprises of the considerable number of procedures that help a project administrator in
sorting out, overseeing and driving the task group. Human Resource Management is about
"staff administration". It is the arranged vital way to deal with dealing with an association's
Page 80 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
most important resources the general population required with the distinctive projects
keeping in mind the end goal to accomplish the different business destinations. By
definition, HRM includes the procedures engaged with overseeing individuals to address
the issues of the association.
As per the PMI the four Project HR administration forms are:
Develop human asset design: It includes the ID and archiving of task parts and obligations,
required aptitudes, hierarchical connections, and making a staffing plan. This is a piece of
the Planning procedure gathering.
Acquire project group: This includes searching for the accessibility of the required HR and
amassing the group important to effectively total the undertaking. It is a piece of the
Executing procedure gathering.
Develop project group: This is tied in with enhancing the group progression and its
competency to perform better as a feature of the general undertaking group. It is a piece of
the Executing procedure gathering.
Manage project group: It includes assessing singular colleague execution, giving criticism,
overseeing and settling clashes, and overseeing changes to streamline the group's
execution. This is additionally a piece of the Executing procedure gathering.
In view of the project extension and work breakdown examination, the fitting group for
project usage will be sorted out and distributed including Project Managers, Technical
Leads, Engineering Leads, Technical Experts, and other help faculty relying upon the
extent of work required. For this particular project, the required human resources are listed
as below along with the associated costs.
Page 81 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Resource Name Type Initials
Max.
Units
Std. Rate
Description
Business Analyst Work BA 100% $90.00/hr
This person is associated with the business
related activities in the project.
Project Manager Work PM 100% $85.00/hr
This person is responsible for management of
the project.
Development
Team
Work DT 600% $80.00/hr
This will include the human resource required
for development of network infrastructure and
there will be 6 members.
Networking
Team
Work NT 500% $85.00/hr
This will involve 5 members for networking
concepts.
Design Team Work DST 400% $65.00/hr
This involves the designing team and there
will be 4 members.
Implementation
Team
Work IMT 500% $95.00/hr
The implementation team will comprise of 5
members.
Tester Work TS 100% $100.00/hr
The tester will be responsible for testing of
the hardware and networking equipment.
System Analyst Work SA 100% $90.00/hr
This person will be responsible for testing the
entire network.
Technical Writer Work TW 100% $75.00/hr This person will be responsible for
documentation of technical information and
Page 82 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
project documentation.
8 COMMUNICATIONS MANAGEMENT
This section comprises of correspondence design improvement, planning and imparting
project data with the client, and execution revealing. Amid project arranging,
correspondence administration assignments will characterize advance revealing calendars,
techniques, configuration, partners, and substance so all parts of task data is conveyed in
the correct route and in a productive and smooth form.
8.1 COMMUNICATION MATRIX
In this project for the improvement of the VIC Roads organize association, the task
supervisor would independently speak with each of the partners required to distinguish the
required and favored correspondence time and medium. Task supervisor should fuse the
data inside the "project communication matrix" and partner enrollment.
Stakeholder Messages Vehicles Frequency Communicators Feedback
Mechanisms
Project
manager
Changes or
information
regarding the
project
Conference
Calls, Electronic
mails, group
meetings, letters,
personal
Whenever
required
The project team Formal e-mail
or personal
meetings.
Page 83 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Stakeholder Messages Vehicles Frequency Communicators Feedback
Mechanisms
meetings, phone
calls
Implementati
on
coordinator
Changes,
modification or
information
regarding the
progress of
implementation
procedure
Conference
Calls, Electronic
mails, group
meetings, letters,
personal
meetings, phone
calls
Whenever
required
Network
Engineer, project
manager,
implementation
team,
development
team, technical
support team
Electronics
mails
Development
team
Information
regarding the
efficient
implementation
of the proposed
network
diagram
Electronic mails,
group meetings,
letters.
Twice a
month
Project manager,
network
engineer,
implementation
team.
The feedback
will be provided
through phone
calls, meetings,
electronic mails
and conference
calls
Technical
support team
Regarding the
changes and
Electronic mails,
group meetings,
Wherever Project manager,
network
The feedback
will be provided
Page 84 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Stakeholder Messages Vehicles Frequency Communicators Feedback
Mechanisms
information
required in the
software and
hardware
implementation
of the proposed
network
letters, phone
calls.
required engineer,
development
team
implementation
team
through the
emails,
meetings and
conference calls
Implementati
on team
Regarding the
information of
change in the
proposed model
and procedure
used for the
implementation
of the network
Electronic mails,
group meetings,
letters, and
phone calls
Twice a week Network
engineer, project
manager,
development
team, Technical
support team and
electronic
worker
The feedback
will be provided
to the
implementation
team through
the electronic
mail, group
meetings and
conference call
Network
engineer
Regarding the
changes in the
requirements
Conference
Calls, Electronic
mails, group
Once a week The project
manager,
implementation
Electronic
mails, direct
meetings, group
Page 85 of 107
[Insert appropriate disclaimer(s)]

VIC Roads Infrastructure Development
Stakeholder Messages Vehicles Frequency Communicators Feedback
Mechanisms
and the
proposed
diagram for the
network
connection
meetings, letters,
personal
meetings, phone
calls
team,
development
team
meetings and
conference calls
9 RISK MANAGEMENT
Risk administration is the way toward distinguishing risk, surveying risk, and finding a
way to decrease risk to a worthy level. The risk administration approach decides the
procedures, methods, instruments, and group parts and obligations regarding a particular
project. The risk administration design portrays how chance administration will be
organized and performed on the project. As an administration procedure, risk
administration is utilized to recognize and maintain a strategic distance from the potential
cost, timetable, and execution/specialized risks to a framework, adopt a proactive and
organized strategy to oversee negative results, react to them in the event that they happen,
and distinguish potential open doors that might be covered up in the circumstance
(Martinelli and Milosevic 2016). The risk administration approach and plan operationalize
these administration objectives. Since no two tasks are precisely indistinguishable, the risk
administration approach and plan ought to be customized to the extension and many-sided
Page 86 of 107
[Insert appropriate disclaimer(s)]