Professional Documents
Culture Documents
Brett Ward
Jon Kealy
Mark Robinson
Henry Baxter
PROJECT
Student Numbers
C3175979
C3101368
COMMUNICATIONS
C3214379
C3249822
Due 11.59pm, 19th October 2015
PLAN - GLENBAWN
DAM PROJECT
Assignment 1 Group 3
Document Control
Title
Position
Signed/Approved Date
Originator
Brett Ward
Associate
BW
11/10/15
Originator
Jon Kealy
Associate
JK
11/10/15
Review
Mark
Robinson
Senior Associate
MR
13/10/15
Approval
Henry Baxter
Director
HB
14/10/15
Details of Revisions
Rev
Date
Description
Approved
23/09/15
JK/BW
29/09/15
JK
10/10/15
For Approval
JK/BW
11/10/15
For Issue
JK
4
5
6
7
Contents
1.
1.2
2.
Definitions ................................................................................................................................................. 3
3.
4.
5.
Objectives ...................................................................................................................................... 4
4.2
4.2.2
4.2.3
5.2
5.3
6.
7.
8.
9.
7.1
7.2
8.2
Objectives ....................................................................................................................................17
8.3
Structure .......................................................................................................................................18
8.4
Templates ...............................................................................................................................................20
9.1
Complaint Form............................................................................................................................20
9.2
9.3
9.4
List of Figures
Figure 1: Project Location .. .....................................................................................................................2
Figure 2: Project Organisation Chart........................................................................................................ 6
List of Tables
Table 1: Proposed Glenbawn Dam Project Communication Tools.....10
Table 2: Priority Definition .13
Table 2: Key Stakeholder Issues Analysis Functional Issues...............................14
1.
1.1
Project Description
Background for Glenbawn Dam Project
The New South Wales Government has been extensively planning to secure long term water
supplies for the Upper Hunter region that has endured high unemployment, minimum
existing local industry and a shrinking agriculture industry. Following a feasibility study
conducted by Pricewaterhouse Coopers Pty Ltd it was indicated that if the supply of
sufficient water is guaranteed, the private sector will invest significant amounts of money
into new industries. As well, the private sector will invest in the redevelopment of existing
industries and significantly upgrade the regions agricultural base. Further feasibility studies
indicate that a Government investment of approximately $150million will result in significant
economic, social and community benefits. The Government will also have opportunity for
significant reform to its water resources policy and the sale of water rights.
1.2
The proposed site of the Project is approximately 20 kilometres east of Scone, 30 kilometres
west of the Barrington Tops National Park.
The Lake Glenbawn Dam Project, will result in regional employment during construction and
long term regional employment growth. It will also assist the New South Wales Government
in reaching its regional policy objectives. The project is located in an area that minimises the
dams environmental impact and the amount of private land that will be flooded. However,
the project requires the support of four local government areas and there are vocal sections
of these communities that do not support the construction of a dam.
2.
Definitions
Acronym/Word
Definition
CM
Communications Manager
COB
Close of Business
CT
Communications Team
Communications
Team
Project
Project Team
3.
The purpose of this Communications Management Plan (Plan) is to present the community
engagement objectives, delivery framework and the potential issues the project needs to
manage. It also provides information on the communication tools and protocols which will
support implementation and descriptions of how community stakeholders will be kept
informed of and consulted about the Glenbawn Dam Project throughout the delivery and
commissioning phases.
This Plan provides the framework for communication between the Project Team, the local
community and key external stakeholders. In particular, it details the following elements:
Procedures and mechanisms for providing information to the community and key
stakeholders
Procedures and mechanisms for how the Project Team will receive and respond to
community feedback, enquiries and complaints
3.1
All communication developed and distributed throughout the Glenbawn Dam Project is
intended to achieve the following goals:
Stakeholders are aware and informed: stakeholders receive timely information about
what is happening, why, when and how, and what it means to them. This information
starts at a generic level (which is repeated throughout the programme/Project), and
becomes more detailed, specific and targeted as the programme/ Project progresses.
This information enables stakeholders to think about, understand, plan for and be
prepared for the change.
4.
4.1
The Communication Teams (CT) main function is to support the Project in the delivery of
works. The CT works in parallel with the Environment Management team to manage and
resolve construction issues including the event of a pollution incident, environmental impacts
(noise, water dust).
The Community Manager (CM) liaises, as required with the projects nominated
Environmental Manager to ensure issues relating to the management of environmental
complaints/enquiries have been satisfactorily addressed. The CM will report directly to the
Project Manager as seen below in the Organisation Chart.
Project Director
Steve Jones
Project Manager
Brad Smith
Communications
Manager
Erin Brown
Environmental
Manager
Danielle Green
Construction
Manager
John Andrews
4.2
5.
Strategic Approach
For the purpose of this plan, the projects community comprises a diverse range of
stakeholders that have a direct interest in and or will be affected by the project. For further
information please read the Stakeholder Management Plan.
During the project stakeholder identification, it will be the responsibility of the Project
Manager to undertake stakeholder engagement in order to determine the frequency and
deliver method of the communications to meet their needs. Once all stakeholders have been
identified and the establishment of communications requirements are finalised, this
information will be transferred into the Projects Stakeholder Register and retained for the
duration of the project.
Project communication will be undertaken in line with the identified key areas as outlined in
the Communication Matrix at 5.2. There may be times when individual communication is
required to achieve any project constraints, however these must be clearly documented and
retained for future referencing if required.
5.2
Communication
Type
Objective of
Communication
Medium
Frequency
Kickoff Meeting
- Face to
Face
Technical Design
Meetings
Community information
sessions
Owner
Deliverable
Format
- Project
Project
Sponsor / Client Manager
- Project Team
- Stakeholders
- Agenda
- Meeting Minutes
- Face to
Weekly
Face
- Conference
Call
- Project Team
Project
Manager
- Agenda
- Soft copy
- Meeting Minutes archived
- Project Schedule
- Face to
Face
- Project
Technical Staff
Technical
Lead
- Agenda
- Meeting Minutes
- Soft copy
archived
- Soft copy
archived
Monthly
- Project
Project
Sponsor / Client Manager
- Project Team
- Stakeholders
- PMO
- Project Status
- Soft copy
Report
archived
- Project Schedule
Once
-Project Team
-Stakeholders
-Government
representatives
Once
Audience
As Required
10
Project
- Agenda
Manager & - Meeting Minutes
Sponsor
- Soft copy
archived
- Soft copy
archived
Project Notifications
Update on project
status and up and
coming works
-Web page
-Email
-Letter box
drops
-Client
-Project Team
-Stakeholders
Project
Manager
Targeted notifications
Residents / tenants
notification of works in
close proximity to them
Works identified as
noisy or causing
traffic/pedestrian
changes
-Letter box
As required and
drops
identified in the
-Face to face project programme
-Email
-Project Web
page
-Stakeholders
-residents
-Business
Project
Manager
As received
Project
Manager
Response to
sender
-Soft Copy
archived
Advertisements
Update on project
status
During critical project
stages
-Local
Monthly
newspapers At critical stages
-Stakeholders
-residents
-Business
Project
Manager
Confirm
publication
-Soft Copy
archived
Project information
and frequently asked
questions
Project
Manager
Provision of key
contacts for
emergency or general
contact
-Letter box
As required
drops
-Face to face
-Email
-Project Web
page
-Part of
Advertiseme
nts
-Stakeholders
-residents
-Business
Project
Manager
Create cards in
preparation
-Soft copy
archived
Translation service
-Letter box
As required
drops
-Face to face
-Email
-Project Web
page
-Any party
requiring
translation
services
associated with
the project
Project
Manager
-Soft copies of
translation
service
engagement
-Soft copies of
medium used to
Monthly
11
-Part of
Advertiseme
nts
get the
information out
Project
Manager
Confirm locations
that are identified
as key to message
transmission
Weekly
Any Party
Project
Manager
Website
Any party
Project
Manager
Enquiries/complaints
procedures
Formulate the
procedure for
management of project
enquiries and
complaints
Have the
procedure finalised
and sign off at the
outset of the
planning phase
As required
Web
Phone
Face to
Face
Written and
emailed
Corresponde
nce
12
Update the
communication
s plan to reflect
agreed
locations
Electronic
copies retained
in the project
folders
5.3
As the project progresses there may be occasions when issues or complications arise with
regards to project communications. This may require these to be escalated if resolution
cannot be achieved within the project team. While escalations are a normal part of project
management, there must be a documented process that defines how those escalations will
take place.
Communications need to be managed efficiently and in a timely manner to ensure the project
is not adversely impacted upon. It is therefore imperative that disputes, conflicts, or
discrepancies regarding project communications are resolved in a way that is conducive to
maintaining the project schedule, ensuring the correct communications are distributed, and
preventing any ongoing difficulties. In order to ensure projects stay on schedule and issues
are resolved, we intend to use a standard escalation model to provide a framework for
escalating communication issues. The table below defines the priority levels, decision
authorities, and timeframes for resolution.
Priority
Definition
Decision
Authority
Within 4 hours
Project
Sponsor
Project
Manager
Project
Manager
13
6.
Functional
Issues
Stakeholders Impacted
Relocation of
residence
Residents
Reduction in
residential property
Residents
Road closures
Environmental
Flora / Fauna
Construction noise
Residents / Businesses
Higher vehicle
movements
14
7.
7.1
Key Messages
Project Positioning Key Messages
Due to the requirements for long term water supply in the region, the government has been
lobbied extensively to ensure that the region remains sustainable into the future.
The government has completed a feasibility study which indicates an investment for the
project of approximately $150million. The delivery of this project will allow the Government
the opportunity to meet sustainability and growth opportunities and achieving its regional
policy objectives. In additional, there will be an opportunity for a return on investment with
the sale of water rights after the project is complete.
The key messages pertaining to the new dam project are:
a) A boost to regional employment during and after the project through the use of local
resources and businesses. Currently the region has a high rate of unemployment with
local industry unable to support the existing growth.
b) The area selected will have minimal impact on residential dwellers, and Flora &
Fauna.
c) Provide future growth opportunities to regional agricultural industry that over the
previous years has been reducing due to restrictions on water
d) The supply of water after the project has been finished will be guaranteed as indicated
in the feasibility study. This in turn will provide continued investment in the region.
7.2
From the outset and throughout all stages of this project there will be a need to clearly
engage with the local community impacted upon by this project. The project team intends to
manage these specific issues effectively and efficiently to allow the project objectives to be
met with the least amount of impact to the local community, infrastructure and Flora and
Fauna. This will be achieved through:
a) Regular Stakeholder forums to allow open discussion around the project and its
deliverables.
15
16
8.
The Glenbawn Dam Project will seek to engage and receive feedback from all community
stakeholders who are impacted by the project design and construction activities. Feedback
is important to ensure that the project benefits from local input and knowledge and causes
minimal disruption to the local community.
Two key tools which will be used to engage the community; receive and respond to feedback
are:
a)
Objectives
General and issue-specific information sessions will ensure that community members have
the opportunity to discuss with the project team issues that are of most interest/concern to
them. Specific objectives of community information sessions are to:
a) Establish personal contact with the community and reduce potential for prolonged
antagonism;
b) Encourage participation from relevant community members or groups affected by the
issue/s;
c) Respond to the particular needs and concerns of the community; and
d) Ensure an open and transparent way of sharing information.
Glenbawn Dam Project | Communications Management Plan
17
Structure
8.3
Information sessions managed by the Communications Team are open to all members of
the community. To encourage community participation, invitations to information sessions
are distributed in a variety of ways including via newsletters/monthly project updates, in local
newspapers, and on the Project website.
One information session will be held primarily midweek (subject to community consensus
for alternate days) and one on the weekend. Information sessions will run for between two
and three hours depending on the issue and the level of community interest.
Where relevant and possible, the location of information sessions will be held nearby the
location of the topic being discussed.
Every effort is made to ensure community information sessions are open and accessible
and encourage maximum community attendance and participation. One of the information
sessions will preferably be held in the early evening (4pm to 7pm) and another on a Saturday
morning (10am to 12pm) to allow the widest cross-section of audiences to attend (eg. people
arriving home from work, elderly residents and business representatives).
Enquiries/Complaints Management
8.4
The Communications Team will be responsible for the management of all complaints and
enquiries received either via the /24-hour Complaint Line, project email, correspondence or
direct contact from stakeholders.
The key processes involved in recording complaints and enquiries are as follows:
Complaints
a) All complaints will be recorded daily;
b) All complaints received for the duration of the project will be responded to verbally by
the Communications Team within two (2) hours from the time contact is received;
and
c) A complaints report will be distributed to Project Team by COB;
Enquiries
a) All enquiries will be recorded daily;
18
b) All email enquiries will be responded to by the Communications Team within one (1)
business day of receipt; and
c) All phone enquiries will be responded to by the CLT by phone within two (2) business
hours from the time contact is received.
19
9.
Templates
9.1
Complaint Form
FIRST NAME:
LAST
NAME:
RESIDENTIAL ADDRESS:
POSTAL ADDRESS:
No
No:
Street
Street
Suburb
Postcode
:
Telephone (work):
Fax:
Suburb
Same
residential
Postcode:
After hours
mobile:
Email:
Name:
Date
Time:
Contact No:
Facsimile:
&
Details of Concern:
Where? What? & When?
Sign:
Date
:
Sign:
Date
:
20
as
Meeting Agenda
9.2
Meeting Number:
xxxxxxxxx
Title / Purpose:
Date:
[INSERT]
Time:
[INSERT]
Location:
[INSERT]
Invitees:
[INSERT]
[INSERT]
Item
1.
Introduction
2.
3.
4.
5.
6.
7.
8.
Other business
9.
21
Meeting Minutes
9.3
Document
ref No:
xxxxxxxx
Title / Purpose:
Date:
[INSERT]
Time:
[INSERT]
Location:
[INSERT]
Attendees:
[INSERT]
[INSERT]
Apologies
[INSERT]
[INSERT]
Distribution
Item
1.
Action (by)
Introduction
1.1
2.
3.
4.
4.1
5.
6.
Comments
Comments from the Floor
6.1
7.
8.
Other Business
Next Meeting:
22
9.4
Contact
o
o
o
o
23