[PDF]Project Scope Requirements Vol 1 - Rackcdn.comhttps://4a5b508b5f92124e39ff-ccd8d0b92a93a9c1ab1bc91ad6c9bfdb.ssl.cf4.rackcdn.c...
53 downloads
250 Views
8MB Size
Document for Release
EAST WEST LINK – STAGE ONE
PROJECT SCOPE AND REQUIREMENTS VOLUME 1 OF 3
CONTENTS
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 1 OF 294
CONTENTS
VOLUME 1 Part A 1. 2. 3. 4. 5. 6. Part B 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. Part C 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.
CONTENTS
Introduction ....................................................................................................................... 7 General ..................................................................................................................... 8 Reference Documents.............................................................................................. 8 Not Used................................................................................................................. 10 General requirements............................................................................................. 10 Project outline ......................................................................................................... 11 Glossary of Terms .................................................................................................. 16 Road and Bridge Requirements .................................................................................... 26 Design life and residual design life ......................................................................... 27 Structures ............................................................................................................... 29 Road Geometric Design ......................................................................................... 30 Drainage and flood control ..................................................................................... 33 Shared use paths and footpaths ............................................................................ 34 Traffic barriers ........................................................................................................ 35 Pavement, surfacing and linemarking .................................................................... 36 Settlement .............................................................................................................. 37 Road signing .......................................................................................................... 38 Intersection traffic signals ....................................................................................... 39 Freeway ramp signals ............................................................................................ 40 Street lighting ......................................................................................................... 40 Urban Design and Landscaping ............................................................................. 41 Conduit Systems .................................................................................................... 42 Emergency services facilities ................................................................................. 42 Tolling hardware ..................................................................................................... 42 Noise ...................................................................................................................... 43 Modifications to VicRoads Publications ................................................................. 45 Future EWL Stages ................................................................................................ 46 Tunnels ............................................................................................................................ 47 General ................................................................................................................... 48 Tunnel geometric design ........................................................................................ 48 Tunnel excavation and support .............................................................................. 49 Groundwater control and seepage requirements ................................................... 50 Drainage system .................................................................................................... 52 Tunnel finishes ....................................................................................................... 52 Fire and life safety requirements ............................................................................ 53 Fire suppression systems....................................................................................... 54 Fire resistance of tunnel infrastructure ................................................................... 55 Smoke management .............................................................................................. 56 Tunnel power system ............................................................................................. 58
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 2 OF 294
12. 13. 14. 15. 16. 17. Part D
Tunnel lighting systems .......................................................................................... 59 Tunnel ventilation system ....................................................................................... 59 Air quality monitoring .............................................................................................. 61 Emergency response facilities ............................................................................... 61 Operational requirements ....................................................................................... 62 State conduit system .............................................................................................. 62 Operations Management and Control System ............................................................ 63
1. 2. 3. 4. 5. 6. 7. Part E
General ................................................................................................................... 64 Traffic Management and Control Systems ............................................................. 66 Plant Management and Control System ................................................................ 74 Communication System ......................................................................................... 74 Asset Management System ................................................................................... 76 Lane Use Management and TMCS Integration ..................................................... 77 Traffic Devices Operating Protocols ....................................................................... 77 Property and Land .......................................................................................................... 79
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Part F
Property Access ..................................................................................................... 80 Fencing ................................................................................................................... 80 Demolition and Salvaged Materials ........................................................................ 82 Condition of Land ................................................................................................... 82 Land Availability ..................................................................................................... 83 Leased Area Plans ................................................................................................. 85 Maintenance Area Plans ........................................................................................ 86 Survey Plans .......................................................................................................... 86 Road and Authorised Access Points Gazettal Plans ............................................. 87 CML Lease Plans ................................................................................................... 87 Plan Types ............................................................................................................. 88 Progressive Development ...................................................................................... 88 GIS Data ................................................................................................................. 88 Process Requirements ................................................................................................... 90
Part F1 1. 2. Part F2 1. Part F3 1. 2. Part F4 1. 2. 3. 4. Part F5 1. 2.
CONTENTS
Project Strategies, Project Plans and O&M Manuals ............................................. 91 Introduction ............................................................................................................. 91 Project Plans and O&M Manuals ........................................................................... 97 D&C Program ....................................................................................................... 113 D&C Program ....................................................................................................... 113 Safety Audits ........................................................................................................ 116 Road Safety Audits ............................................................................................... 116 Safety Audit Reports ............................................................................................ 116 Site and Survey .................................................................................................... 117 Investigation, Condition Survey and Monitoring ................................................... 117 Condition surveys ................................................................................................. 117 Monitoring ............................................................................................................. 117 Site Reinstatement ............................................................................................... 117 Design .................................................................................................................. 119 General ................................................................................................................. 119 General Requirements for Design Documentation .............................................. 119
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 3 OF 294
Part F6 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Part F7 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Part G
Communications and Community Engagement ....................................................... 155
1. Part H
Community information ........................................................................................ 156 Specific Appendices .................................................................................................... 160
Part H1 Part H2 1. Part H3 1. Part H4 1. Part H5 1. Part H6 1. 2. 3. 4.
CONTENTS
Construction ......................................................................................................... 128 Working hours ...................................................................................................... 128 Construction Documentation ................................................................................ 128 Construction Review Meetings ............................................................................. 129 Notification of Incidents ........................................................................................ 129 Maintenance during Construction ........................................................................ 130 Construction staging ............................................................................................. 130 Traffic Management during Construction ............................................................. 130 Environmental Management during construction ................................................. 134 Testing and Commissioning ................................................................................. 135 Construction records ............................................................................................ 136 As-Built Records ................................................................................................... 137 Asset Inventory ..................................................................................................... 139 Defects List ........................................................................................................... 139 Records and Reporting ........................................................................................ 139 Operation and Maintenance ................................................................................. 144 General ................................................................................................................. 144 Operation .............................................................................................................. 144 Incident management ........................................................................................... 145 Environmental Management during operations ................................................... 145 Traffic management ............................................................................................. 146 Maintenance ......................................................................................................... 148 O&M Manuals ....................................................................................................... 149 Asset Management System ................................................................................. 149 Code of Maintenance Standards .......................................................................... 149 Condition monitoring of Assets ............................................................................ 151 Scheduling and Performance of O&M Activities .................................................. 151 O&M Phase Reports ............................................................................................ 152
Lane Requirements .............................................................................................. 161 Posted Speeds and Design Speeds .................................................................... 171 Posted speeds and design speeds ...................................................................... 171 Design Traffic Volumes ........................................................................................ 173 Design Traffic Volumes ........................................................................................ 173 Intersections and Interchanges ............................................................................ 184 Intersections and Interchanges ............................................................................ 184 Performance Criteria ............................................................................................ 186 Performance Criteria ............................................................................................ 186 Public Transport Facilities and Off Road Paths ................................................... 187 Eastern Freeway westbound Bus Lane at Hoddle Street .................................... 187 Hoddle Street north bound Bus Lane ................................................................... 187 Transit Lane ......................................................................................................... 187 Existing Bus, Tram and Train Services ................................................................ 188
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 4 OF 294
Part H7 1. Part H8 Part H9 1. 2. Part H10 1. 2. 3. 4. 5. Part H11 Part H12 1. 2. 3. 4. 5. Part H13 1. 2. 3. 4. 5. 6. 7. 8. 9. Part H14 1. Part H15 Part H16 Part H17 Part H18 Part H19 Part H20 1. 2. Part H21 1. 2. Part I
Freeway Ramp Signals ........................................................................................ 189 Freeway ramp signals .......................................................................................... 189 Variable Lane Configuration Management System ............................................. 191 Directional Signage ............................................................................................. 193 Directional Signage Area...................................................................................... 193 Directional Signage Destinations ......................................................................... 193 Road Safety Camera Hardware ........................................................................... 197 General ................................................................................................................. 197 Road safety camera sites ..................................................................................... 197 Centralised equipment room ................................................................................ 199 Road safety camera communication sub system. ............................................... 199 Performance Requirements ................................................................................. 199 VicRoads Communication Hardware ................................................................... 200 Tolling Hardware .................................................................................................. 201 General ................................................................................................................. 201 Tolling point sites .................................................................................................. 201 Centralised Tolling Room ..................................................................................... 202 Tolling communication sub system ...................................................................... 203 Tolling power sub system ..................................................................................... 204 Allowances for Future Infrastructure .................................................................... 205 General ................................................................................................................. 205 Upfield Rail Line ................................................................................................... 205 Clifton Hill Rail Line .............................................................................................. 205 Public Safety Barriers ........................................................................................... 205 CityLink Widening ................................................................................................. 205 Future Port Connection ........................................................................................ 205 Cooperative ITS functionality ............................................................................... 205 Freeway Control Centre ....................................................................................... 205 PAM #1 CityLink additional north bound lane option ........................................... 205 Over-Dimensional Route 3 ................................................................................... 206 Over-dimensional route 3 ..................................................................................... 206 Property Access ................................................................................................... 207 Lease Principles ................................................................................................... 208 Maintenance Principles ........................................................................................ 217 Operational Area .................................................................................................. 219 Performance Requirements ................................................................................. 220 CityLink Returned Works...................................................................................... 224 Introduction ........................................................................................................... 224 CityLink Returned Works Requirements .............................................................. 224 Environment and Urban Design ........................................................................... 226 Environmental Performance Requirements ......................................................... 226 Urban Design Principles ....................................................................................... 261
Pre Agreed Modifications and Community Enhancements ..................................... 268 Part I1 1. 2.
CONTENTS
Pre-Agreed Modifications (PAM’s) ....................................................................... 269 PAM #1: CityLink additional north bound lane option .......................................... 269 PAM #2: VicTrack Communication Conduits ....................................................... 273
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 5 OF 294
3. 4. 5. 6. 7. 8. 9. Part I2 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14.
PAM #3: Reinstatement and Enhancements of “Old Grass Hockey Fields” Royal Park ...................................................................................................................... 274 PAM #4: Eastern Freeway shared use path, Merri Creek to Chandler Highway . 276 PAM #5: Melbourne Zoo and SNHC Carpark ...................................................... 276 PAM #6: Truro Street path upgrade ..................................................................... 276 PAM #7: Eastern Freeway shared use overpass, east of Clifton Hill rail line ...... 277 PAM #8: Eastern Freeway shared use path, Ramp G to connect with PAM #4 .. 279 PAM #9: Shared use path, Moonee Ponds Creek trail to Capital City Trail through Ross Straw fields. ................................................................................................. 279 Community Enhancements .................................................................................. 280 Community Enhancement #1 – Trenerry Crescent .............................................. 281 Community Enhancement #2 – Royal Park shared use path connectivity .......... 282 Community Enhancement #3 – Moonee Ponds Creek Trail enhancements ....... 283 Community Enhancement #4 – Reggio Calabria Club car park and field upgrades .............................................................................................................................. 284 Community Enhancement #5 – Moonee Ponds Creek Trail enhanced connectivity and enhancements to Ormond Park and Holbrook Reserve ............................... 285 Community Enhancement #6 – Moonee Ponds Creek Trail enhanced connectivity and enhancements – Travencore Area. ............................................................... 286 Community Enhancement #7 – Flemington Bridge Station access and landscaping enhancements ...................................................................................................... 287 Community Enhancement #8 – Debney’s Park Redevelopment ......................... 288 Community Enhancement #9 – Indigenous Meeting Place ................................. 289 Community Enhancement #10 – Urban Camp Sustainability Initiatives .............. 290 Community Enhancement #11 – Eastern Freeway shared use path, Merri Creek to Chandler Highway ................................................................................................ 291 Community Enhancement #12 – Truro Street path upgrade ............................... 292 Community Enhancement #13 – Melbourne Zoo & SNHC car park .................... 293 Community Enhancement #14 – Eastern Freeway shared use path, Ramp G to connect with PAM#4/Community Enhancement#11 ............................................ 294
VOLUME 2 Part J
Land Plans
VOLUME 3 Part K
[Not disclosed – could disadvantage parties in future projects]
Part L
[Not disclosed – could disadvantage parties in future projects]
CONTENTS
PROJECT SCOPE & REQUIREMENTS – VOLUME 1
PAGE 6 OF 294
Part A
PART A
INTRODUCTION
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 7 OF 294
1.
General
1.1
Purpose and Interpretation 1.1.1
The Project Requirements set out the State's minimum requirements for the Works and the Project Activities (subject to clause 2.4 of the Agreement).
1.1.2
Subject to clause 2.4 of the Agreement, the Works and the Project Activities must, as a minimum, comply with: (a)
the Project Requirements; and
(b)
the Project Scope.
1.1.3
If there is any inconsistency, ambiguity or discrepancy within or between the Project Requirements and the Project Scope or between the PSR and any other State Project Document, clauses 2.2 - 2.5 of the Agreement will apply.
1.1.4
Project Co acknowledges and agrees that: (a)
the State and its Associates have not made and make no representation, and give no warranty or guarantee and owe no duty of care; and
(b)
Project Co bears the entire risk and will not make any Claim against the State for any Liability,
in connection with: (c)
the inclusion of the Agreed Exceptions in the PSR;
(d)
whether the Project Scope complies with the Project Requirements; or
(e)
whether carrying out the Project Activities (including preparation of the Design Documentation) or performing the Works in accordance with the PSR will ensure that Project Co can sufficiently discharge its obligations under the State Project Documents.
1.1.5
Notwithstanding that specific requirements in the Reference Design may have been incorporated by reference into the Project Requirements, the Reference Design does not form part of the Project Requirements or Project Scope.
1.1.6
Project Co must:
1.1.7
(a)
make its own determination of whether the requirements of the State Project Documents are satisfied by complying with the Reference Documents and whether any additional measures are required to enable Project Co to comply with the State Project Documents; and
(b)
incorporate all additional measures necessary to enable Project Co to comply with the State Project Documents.
A glossary of terms is set out in section 6.
2.
Reference Documents
2.1
General
PART A
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 8 OF 294
2.1.1
PART A
Subject to the Agreed Exceptions, the Works and the Project Activities must comply with the requirements of the Reference Documents, unless the Project Requirements specify a different requirement, standard, quality, level of service, quantum or scope, in which case the Project Requirements will prevail. The hierarchy of Reference Documents will be in the following order: (a)
in relation to Returned Works (other than the CityLink Returned Works), the relevant published standards of the Facility Owner;
(b)
VicRoads publications;
(c)
any relevant published standards of other Victorian government Authorities;
(d)
in relation to tunnels, Tunnel Reference Documents;
(e)
AUSTROADS publications;
(f)
the relevant standards, codes and guides of Standards Australia and Standards New Zealand (or, where an Australian Standard or a New Zealand Standard does not exist, the relevant British standard or international standard);
(g)
the standards, codes and guides published by the National Occupational Health and Safety Commission;
(h)
Australian and New Zealand Guidelines for the Assessment and Management of Contaminated Sites, ANZECC/MHNRC; and
(i)
all other publications, codes, references, guidelines, manuals and other technical documents which are relevant to the performance of the Project Activities.
2.1.2
Where an item, approach or option is referred to in a Reference Document and it is expressed in terms such as 'should', 'may be', 'recommended', 'suggested', 'desirable', 'advisable', the item, approach or option referred to is deemed to be a requirement and must not be varied unless otherwise agreed by the State.
2.1.3
Where a Reference Document provides for: (a)
a 'desirable' and an 'absolute' design limit, the desirable design limit is to apply unless other design limits are approved by the State;
(b)
the specification of material properties or mix designs for materials, such material properties or mix designs must be specified in the Design Report and on the drawings in the Certified Design Documentation;
(c)
the approval of construction procedures by a superintendent, such procedures must be included in the Construction Documentation submitted in accordance with Part F6;
(d)
the release of Hold Points by a superintendent, this responsibility must be exercised by the relevant Nominated Authority identified in the Quality Management Plan;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 9 OF 294
(e)
the acceptance of non-conforming works or materials by a superintendent, such non-conforming works must be notified as Defects in accordance with clause 21.1(b) of the Agreement;
(f)
the approval of alternative construction methods or materials by a superintendent, any such methods or materials must be notified to the State and the Independent Reviewer in the Preliminary Design Documentation, Certified Design Documentation, or as proposed changes to IFC Design Documentation in accordance with the Part F5;
(g)
the determination of classification of earthworks materials or approval to reduce the frequency of testing of materials, such determinations and approvals must be authorised by a Nominated Authority with the necessary knowledge and experience to verify compliance with relevant standards and specification requirements; and
(h)
any other determination, direction, or agreement by a superintendent, such determinations, directions, or agreements must be notified to the State and the Independent Reviewer in the Preliminary Design Documentation, Certified Design Documentation, or as changes to IFC Design Documentation in accordance with Part F5.
2.1.4
Where a VicRoads publication requires that the approval of a VicRoads officer be obtained in order to adopt or vary a particular standard, that standard shall not be adopted or varied without the prior written approval of the State.
2.1.5
Project Co must not apply the principles of Extended Design Domain (EDD) as detailed in the VicRoads Supplement to the Austroads Guide to Road Design (Part 2 – Design Considerations) in the development of its design.
2.1.6
If a requirement in a Reference Document: (a)
does not impose an obligation on any particular party, then it will be deemed to impose an obligation on Project Co; and
(b)
would or seeks to impose an obligation on the State or the Independent Reviewer, then that obligation will be deemed to be imposed on Project Co unless: (i)
expressly stated otherwise in the Agreement; or
(ii)
only the State or the Independent Reviewer (as applicable) can perform the obligation.
3.
Not Used
4.
General requirements
As a minimum, the Works and Project Activities must be undertaken to cater for:
PART A
4.1.1
the lane configurations, cross sections and clearances specified in Part H1;
4.1.2
the speeds specified in Part H2;
4.1.3
the design traffic volumes and vehicle mixes in Part H3;
4.1.4
the requirements for interchanges and intersections specified in Part H4;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 10 OF 294
4.1.5
the requirements for public transport specified in Part H6;
4.1.6
the urban design requirements in section 13 of Part B; and
4.1.7
the requirements for tolling hardware specified in Part H12; and
4.1.8
the Future Infrastructure in Part H13.
5.
Project outline
5.1
The Works include: 5.1.1
5.1.2
5.1.3
5.1.4
PART A
Freeway carriageways, including: (a)
traffic lanes and shoulders to the extent specified in Part H1;
(b)
all adjustments, reinstatement and improvements necessary to connect the Eastern Freeway and CityLink to the Freeway;
(c)
tunnels, approximately 4.4km in length linking the Eastern Freeway near Hoddle Street to CityLink at Parkville, consisting of three through lanes in both directions, including all additional infrastructure, plant and equipment necessary to operate the tunnels safely and efficiently; and
(d)
a grade separated freeway to freeway interchange at CityLink;
grade separated interchanges at: (a)
Ormond Road / Brunswick Road;
(b)
Mount Alexander Road; Hoddle Street; and
(c)
connections to the Freeway;
grade separation of Roads and the Freeway carriageways at: (a)
Manningham Street;
(b)
Wellington Street;
(c)
Alexandra Parade; and
(d)
Trenerry Crescent;
all adjustments, truncations, reinstatement and improvements necessary to existing Roads including: (a)
CityLink;
(b)
Brunswick Road;
(c)
Ormond Road;
(d)
Racecourse Road;
(e)
Manningham Street;
(f)
Elliott Avenue;
(g)
Macarthur Road;
(h)
Flemington Road;
(i)
Mount Alexander Road;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 11 OF 294
(j)
Smith Street;
(k)
Wellington Street;
(l)
Alexandra Parade;
(m)
Reeves Street;
(n)
Hilton Street;
(o)
Gold Street;
(p)
Hoddle Street;
(q)
Eastern Freeway; and
(r)
Trenerry Crescent;
5.1.5
making provision for the Future Infrastructure;
5.1.6
ensuring the functionality and level of service of the existing bicycle and pedestrian facilities impacted by the Works is maintained;
5.1.7
providing the bicycle and pedestrian enhancements in the Project Scope;
5.1.8
all structures over drains, creeks and other water courses within the Leased Area necessary for, or required as a result of, the performance of the D&C activities, including: (a)
all adjustments, reinstatement and improvements to creeks, drainage and other water courses; and
(b)
all drainage and flood mitigation and control works;
5.1.9
provision of the Freeway Control Centre;
5.1.10
Returned Works (being works which are necessary as a consequence of, or otherwise arising out of or in connection with, the D&C Activities) including where applicable: (a)
PART A
all adjustments, truncations, reinstatement and improvements necessary to existing Roads, to the extent they are outside the Leased Area including; (i)
CityLink;
(ii)
Brunswick Road;
(iii)
Ormond Road;
(iv)
Racecourse Road;
(v)
Manningham Street;
(vi)
Elliott Avenue;
(vii)
Macarthur Road;
(viii)
Flemington Road;
(ix)
Mount Alexander Road;
(x)
Smith Street;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 12 OF 294
(xi)
Wellington Street;
(xii)
Alexandra Parade;
(xiii)
Reeves Street;
(xiv)
Hilton Street;
(xv)
Gold Street;
(xvi)
Hoddle Street;
(xvii)
Eastern Freeway, east of the eastern abutment of the bridge over Merri Creek; and
(xviii) Trenerry Crescent; (b)
PART A
public transport interfaces which may include: (i)
modifications to the Clifton Hill rail line;
(ii)
modifications to the Upfield rail line;
(iii)
modification to the Route 55, 57 and 59 tram lines; and
(iv)
all other works required to comply with the public transport requirements contained in Part H6;
(c)
the protection, repair, replacement, reinstatement, alteration and relocation of Utility Infrastructure necessary for, or required as a result of, the performance of the D&C Activities;
(d)
all other Works not in the Leased Area;
(e)
the Accommodation Works including; (i)
all adjustments to existing infrastructure or property, excluding the Works referred to in section 5.1.10(c);
(ii)
all changes in access arrangements to existing infrastructure and property;
(iii)
demolition, clearing and decontamination and adjustment of built features;
(iv)
adjustment, re-establishment or making good of all existing buildings whether inside or outside the Construction Areas which are affected in any way by the D&C Activities;
(v)
adjustments to property drainage;
(vi)
modifications and reinstatement of Utility Infrastructure to properties; and
(vii)
all other property adjustment works necessary to ensure that the access to and egress from or the use of any property (including any building, structure, infrastructure or amenity which is affected by the D&C Activities) is reinstated in accordance with the relevant local council requirements or to at least the same standard and quality that it was prior to Financial Close;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 13 OF 294
5.1.11
5.1.12
PART A
(f)
all intersecting Roads;
(g)
footpaths and shared use paths on Roads;
(h)
any creek, water course or other drainage facility forming part of Melbourne Water’s main drainage network;
(i)
rail structures;
(j)
creek embankment works;
(k)
parks and wetlands areas occupied temporarily for construction purposes;
(l)
CityLink Returned Works;
(m)
modifications to sewers, drains and other utilities;
(n)
car parking areas occupied temporarily for construction workforce;
(o)
subject to clause 6.3A of the Agreement, the Community Enhancements, all structures over drains, creeks and other water courses outside of the Leased Area affected by the Works including: (i)
all adjustments, reinstatement and improvements to creeks, drainage and other water courses; and
(ii)
all drainage and flood mitigation and control works;
all associated Temporary Works associated with the above, including: (a)
temporary measures necessary to meet the needs of all road, public transport, public area and pathway users during all stages of undertaking the Works;
(b)
temporary arrangements to divert and control traffic and to provide public amenity, security and safety during performance of the D&C Activities;
(c)
temporary arrangements for people and vehicles to access all property affected by the D&C Activities;
(d)
all environmental safeguards and measures necessary to monitor and mitigate environmental effects during performance of the D&C Activities;
(e)
cleaning, maintenance, repair, replacement and reinstatement, as required, of all areas occupied by Project Co during performance of the D&C Activities;
(f)
the maintenance of roads within the Construction Areas;
(g)
site facilities required for performance of the D&C Activities;
(h)
temporary infrastructure installed or erected to undertake the Works; and
(i)
all temporary measures necessary to open the Freeway;
all other physical things and works necessary, or otherwise arising in connection with the matters described above, including:
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 14 OF 294
PART A
(a)
drainage, earthworks, structures, pavements, noise attenuation and road furniture;
(b)
urban design and landscaping features and finishes;
(c)
all infrastructure and equipment necessary to operate and maintain the O&M Area and any buildings, maintenance facilities and the Operations Management and Control Systems;
(d)
demolition, clearing and associated decontamination;
(e)
all fencing and security measures designed and constructed to prevent either unlawful or accidental access including as a result of legal possession of any land acquired or to be acquired;
(f)
pavement markings, signs and lighting;
(g)
traffic control signals and freeway ramp signals;
(h)
items of infrastructure or such items which are otherwise necessary to provide safety;
(i)
all environmental safeguards and measures necessary to mitigate environmental impacts of the Project Activities, including those identified in Part H21;
(j)
all equipment necessary to monitor the operational and environmental performance, and assess the durability of key elements of Stage One such as; (i)
vibration and temperature sensors for fans with motor power greater than 30kW;
(ii)
temperature sensors for motors over 30kW; and
(iii)
monitoring of cathodic protection if it is required as determined during the detailed design development phase.
(k)
all measures required in accordance with the Agreement in respect of community consultation, including those identified in Part G;
(l)
the provision of facilities for Emergency Services;
(m)
all adjustments to any existing road, footpath, shared use path, open space, landscaped area or street which is affected by the performance of the D&C Activities within the Leased Area;
(n)
all infrastructure required to connect the Freeway to the surrounding road network to ensure the continuing performance of the surrounding road network during construction and after Stage One Completion;
(o)
all infrastructure required to ensure the continuing performance of the pedestrian and bicycle facilities during construction and after Stage One Completion;
(p)
all necessary kerb and channel, connections of footpaths, driveways, removal of existing assets, including redundant driveways and pavement works;
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 15 OF 294
6.
(q)
all fixtures, fittings and other improvements, on, under, above or adjacent to Stage One; and
(r)
any other physical assets, plant, machinery, equipment, improvements, systems, hardware and software necessary to operate, repair and maintain the Relevant Infrastructure.
Glossary of Terms
Unless otherwise expressly defined, expressions used in this PSR have the meaning given to them in the Agreement. In this PSR, unless the context otherwise requires, the terms and phrases set out in Table A.1 have the meaning given in Table A.1. Table A.1 - Glossary of Terms
PART A
Phrase
Meaning
Adjusted CityLink Leased Area
means the CityLink Leased Area as adjusted in accordance with the Lease Principles.
Agreed Exception
means an agreed exception as set out in Part L.
Applicable Roads
means the roads as identified in Table B.7 generating traffic noise to be used in design of the required noise attenuation treatments.
Asset
means a physical component of the Works and includes each part of that physical component (which includes the items identified in the “Assets” column in Attachment 3 of Table K5.1 in Part K5).
Asset Component
means the items identified in the “Component” column in Attachment 3 of Table K5.1 in Part K5
Asset Inventory
has the meaning given in section 5.1.2 of Part D.
Asset Management Manual
means the manual described in section 2.3.1 of Part F1.
Asset Management System
means a system for Asset management that complies with section 5 of Part D.
Asset Sub Component
means the items identified in the “Sub Component” column in Attachment xx of Part K5
Automatic Incident Detection System
means the system described in section 2.8 of Part D.
Biodiversity Assessment Guidelines
means Victoria’s Permitted clearing of native vegetation – Biodiversity Assessment Guidelines incorporated into the Victoria Planning Provisions on 20 December 2013
Building(s)
means all Category A or B buildings as defined in VicRoads Traffic Noise Reduction Policy
CAG
means the East West Link community advisory group.
CIS
means the comprehensive impact statement, to the
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 16 OF 294
Phrase
Meaning extent it has been prepared for Stage One, under the Relevant Legislation.
PART A
CityLink Control Centre
means the centre used by CML to manage traffic operations on CityLink.
CityLink Returned Works
as described in Part H20
CityLink Returned Works Requirements
as described in Exhibit G of the Agreement
CityLink Project Information
means the Project Information in relation to CityLink provided by the State to Project Co prior to the date of this Agreement.
Closed Circuit Television System
means the system described in section 2.10 of Part D.
CML
means CityLink Melbourne Limited.
Code of Maintenance Standards
means the standards described in section 9 of Part F7.
Commercial Vehicle
means a vehicle classified as AUSTROADS Class 3 to 12 inclusive.
Communication System (CS)
has the meaning given in section 4 of Part D.
Communications and Community Engagement Strategy
means the strategy relating to communications and community engagement during the Term prepared by Project Co in accordance with Part F1.
Completion and Commissioning Plan
means the plan described in section 2.1.12 of Part F1.
Connector Road
means the new road connecting Mount Alexander Road with Racecourse Road generally located directly west of the Moonee Ponds Creek.
Concept Design
means the design contained in Part K5 and Part K6.
Construction Communications and Community Engagement Plan
means the plan described in section 2.1.10 of Part F1.
Construction Environmental Management Plan or CEMP
means the plan described in section 2.1.8 of Part F1.
Construction Management Plan
means the plan described in section 2.1.3 of Part F1.
Construction Package
means each construction package as contemplated by the relevant Construction Management Plan and includes the documents as described in section 2.1.1 of Part F6.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 17 OF 294
PART A
Phrase
Meaning
Construction Procedure
means a procedure required to be submitted by a Reference Document and as described in section Part F62.1.5 of Part F6.
Construction Quality Management Plan
means the plan described in section 2.1.4 of Part F1.
Construction Traffic Management Plan
means the plan described in section 2.1.7 of Part F1.
Consumables
means those Asset Sub Components which are not durable and are capable of being consumed, destroyed, dissipated, wasted, or spent including; grease, lubricants, oils, indicator lamps, disposable filters, battery electrolytes, gaskets, cooling water, chemicals, belts, static fuses, landscaping composts
Cooperative ITS Data
means a form of intelligent transport system that enables communication and real time information sharing between vehicles and roadside infrastructure as well as wireless consumer devices, in order to improve safety, productivity, efficiency and environmental outcomes of the road system, and to provide services to all road users and operators through giving advice or facilitating actions.
Co-ordinating Road Authority
has the meaning given to that term in s 3 of the Road Management Act 2004 (Vic).
Design Life
means, in respect of an Asset, the period commencing on the Date of Stage One Completion, or such later date as the Asset is replaced, over which the Asset performs its intended function without replacement, refurbishment or significant maintenance.
DCN
has the meaning given in section 2.4.3 of Part F5.
Design Management Plan
means the plan described in section 2.1.2 of Part F1.
Device
has the meaning given in the Payment Schedule.
DTMP
means a diversion traffic management plan.
Drained
Means that the underground structure permanent works are designed such that any groundwater pressure that would act on the underground structure is relieved, and ingress of any groundwater into the underground structure’s drainage system is provided for, throughout the required Design Life of the structure.
Double Incident
means; (a) a single fire incident, up to 50MW, with traffic stopped downstream, by a second, non-fire incident (or congestion) located downstream, anywhere from 100m from the first incident to the
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 18 OF 294
Phrase
Meaning tunnel exit; or (a)
PART A
a fire incident, up to 20MW, with traffic stopped downstream by a second fire incident, up to 5MW, located downstream, anywhere from 100m from the first incident to the tunnel exit.
Emergency Services
means any one or more of Victoria Police, MFB or Ambulance Victoria as the context requires.
Environmental Auditor
means the person described in section 8.1.5 of Part F6
Environmental Management and Sustainability Strategy
means the strategy relating to environmental management and sustainability during the Term prepared by Project Co in accordance with Part F1.
Environmental Management Framework
means the Environmental Management Framework in the CIS as modified by clause 5 of the Incorporated Document
Environmental Management System
means a system as described in AS/NZS/ISO 14001.
Environmental Representative
means the person described in section 8.1.4 of Part F6.
Environmental Performance Requirements
means the performance requirements allocated to Project Co contained in section 1 of Part H21
External Criteria
means the performance criteria that must not be exceeded, expressed as a noise level from all Applicable Roads, based on the design traffic volumes identified in Part H3.
Fire Engineer (FE)
has the meaning given in AS4805:11.
Fire Engineering Brief (FEB)
has the meaning given in AS4805:11.
Fire Engineering Report (FER)
has the meaning given in AS4805:11.
Forecast Maintenance and Refurbishment Program
means the document described as such in Part K.
Forecast Maintenance and Refurbishment Plan
means the plan described in section 2.2.10 of Part F1.
Forecast Operations Cost Estimate
means the document described as such in Part K.
Freeway Control Centre or FCC
means the building to be used by Project Co for controlling traffic on the Freeway.
Freeway Operations Manual
means the manual described in section 2.3.2 of Part F1.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 19 OF 294
PART A
Phrase
Meaning
Future Infrastructure
means the infrastructure specified in Part H13.
Handover Plan
means the plan described in section 2.2.12 of Part F1.
Health and Safety Management Plan
means the plan described in section 2.1.9 of Part F1.
Hold Point
means those points beyond which the stated construction activity must not proceed without the Nominated Authority’s approval to proceed.
Incorporated Document
Means the East West Link (Eastern Section) Project Incorporated Document forming part of the Planning Scheme Amendment, as amended.
ITMP
means an incident traffic management plan.
Inspection and Test Plans (ITPs)
means the plans related to inspections and tests that must be conducted at key points in the construction process.
Interface Management Strategy
means the strategy relating to interface management during the D&C Phase prepared by Project Co in accordance with Part F1.
Lane Use Management System
means the system described in section 2.4 of Part D.
Lead Verifier
means the suitably qualified and experienced persons independent of those having direct responsibility for the design identified as ‘Lead Verifiers’ in the Design Management Plan.
Maintenance Manual
means the manual described in section 2.3.2 of Part F1.
MTMP
means a maintenance traffic management plan.
MFB
Metropolitan Fire Brigade.
NCC
means the National Construction Code of Australia.
Nominated Authority
means the nominated person with the authorisation to release each Hold Point.
Non-Permitted Closures
has the meaning given in the Payment Schedule.
O&M Area
means and includes; (a) the Maintenance Site; and (b) the Operational Area; or anyone or more of them as the context requires.
O&M Phase Management Plan
means the plan described in section 2.2.1 of Part F1.
O&M Safety Audit Report
has the meaning given to it in the Australian Standards.
Operational Area
means the area described in Part H18
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 20 OF 294
PART A
Phrase
Meaning
Operations Environmental Management Plan (OEMP)
means the plan described in section 2.2.6 of Part F1.
Operations Management and Control System(OMCS)
has the meaning given in section 1 of Part D.
Operations Health and Safety Management Plan
means the plan described in section 2.2.7 of Part F1.
Operations Quality Management Plan
means the plan described in section 2.2.9 of Part F1.
Operations Traffic Management Plan
means the plan described in section 2.2.5 of Part F1.
Operations Workplace Relations Management Plan
means the plan described in section 2.2.3 of Part F1.
Over-height Vehicle System
means the system described in section 2.7 of Part D.
Performance Management Plan
means the plan described in section 2.2.2 of Part F1.
PIARC
means the World Road Association (PIARC).
Plant Management and Control System (PMCS)
has the meaning given in section 3 of Part D.
Point Z
is located 5m upstream of the connection between the Ramp A structure and the main carriageway structure.
Preparatory Works
means any works identified in section 2.7.2 of Part F5 which are scheduled to commence before Certified Design Documentation is available.
Project Delivery Management Plan
means the plan described in section 2.1.1 of Part F1.
Project Requirements
means all of the requirements for the performance of the Project Activities as set out in this Exhibit A other than the Project Scope.
Project Scope
means the project scope incorporated in Part K.
Project Strategy
means each of the strategies to be prepared by Project Co as described in Part F1.
Proposed Leased Area Plans
means the plans identified in section 2 of Part J
Quality Management Strategy
means the strategy relating to quality management during the Term prepared by Project Co in accordance with Part F1.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 21 OF 294
PART A
Phrase
Meaning
Ramp A to Ramp X
means a ramp described in Figure A.1.
Readily Accessible
means an Asset is able to be accessed for inspection and refurbishment or replacement without having to undertake significant civil or structural works that could not be performed during an Overnight Closure Window or could be safely undertaken without Closure of a full ramp or carriageway in either direction of the Freeway.
Reference Design
means the reference design prepared for Stage One by the State as published.
Reference Documents
means those documents described in paragraphs (a) to (i) of section 2.1.1 of Part A.
Relevant D&C Requirements
means the following requirements: (a) any standard, level of service or scope set out in the Concept Design; (b) capacity; (c) durability; (d) aesthetics of visible features; (e) whole of life performance; (f) functional performance; (g) safety; (h) security; (i) community amenity; (j) community benefits; and (k) user benefits, as required by this PSR.
Residual Design Life
means, in respect of an Asset, the remaining Design Life of that Asset at the Expiry Date.
Responsible Road Authority
has the meaning given to that term in section 3 of the Road Management Act 2004 (Vic).
Road Management Plan
means the plan described in section 2.2.4 of Part F1.
Roadside
means any area within a road reserve other than the pavement.
Safety Management Strategy
means the strategy relating to safety management during the Term prepared by Project Co in accordance with described in Part F1.
Terrorism Plan
means the plan described in section 2.1.11of Part F1.
Traffic Data System
means the system described in section 2.6 of Part D.
Traffic Management and Control System or TMCS
has the meaning given in section 2 of Part D.
Traffic Management Centre
means the centre used by VicRoads to manage traffic operations on VicRoads network.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 22 OF 294
PART A
Phrase
Meaning
Traffic Management Strategy
means the strategy relating to traffic management during the Term prepared by Project Co in accordance with Project Strategies, Project Plans and O&M Manuals described in Part F.
Tunnel Information Signing System
means the system described in section 2.3 of Part D.
Tunnel Portal Barrier System
means the system described in section 2.9 of Part D.
Tunnel Reference Documents
means: AFAC, Fire Safety Guidelines for Road Tunnels, 2001 AS 1530 Methods for fire tests on building materials, components and structures AS 2118 Automatic fire sprinkler systems AS 2149.1 Fire hydrant installations AS 4825 Tunnel fire safety AS/NZS 1158.5 Lighting for roads and public spaces – tunnels and underpasses AS4825, Tunnel fire safety Austroads, Guide to Road Tunnels, 2010 British Tunnelling Society and The Institution of Civil Engineers, Specification for tunnelling, third edition, 2010 CIE No. 31 - International Commission of Illumination Publication CIE No. 61 - International Commission of Illumination Publication. Tunnel entrance lighting CIE No. 88 - International Commission of Illumination Publication. Guide for the lighting of road tunnels and underpasses,2004 ISO 1996 Acoustics – Descriptions, measurement and assessment of environmental noise PIARC Fire and Smoke Control in Road Tunnels 1999 PIARC, Current practice for risk evaluation for road tunnels, 2012 PIARC, Road Tunnels: Vehicle emissions and air demand for ventilation, 2012R05EN PIARC, Systems and equipment for fire and smoke control in road tunnels, 2007 RMS R84 Continuous Reinforced Concrete Base
Undrained
means that the underground structure permanent works are designed as watertight, such that there will be no discernible ingress of groundwater into the permanent works or any effect on the groundwater table in the long term.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 23 OF 294
PART A
Phrase
Meaning
Urban Design Framework
the urban design framework set out in the CIS except that the urban design principles are those set out in section 2 of Part H21
Urban Design Principles
means the urban design principles contained in section 2 of Part H21
Variable Lane Configuration Management System
means the system described in section 2.11 of Part D.
Variable Message Signing System
means the system described in section 2.5 of Part D.
Work Breakdown Structure (WBS)
means the subdivision of a project into discrete work elements that can be used for project planning and delivery.
WEMP
means a worksite environmental management plan.
Work Lot
means any part of the work constructed or manufactured under essentially uniform conditions in a continuous operation and which is essentially homogeneous with respect to material properties, general appearance and construction or manufacturing process.
Workplace Relations Management Plan
means the plan described in section 2.1.6 of Part F1.
WTMP
means a worksite traffic management plan.
2015 Level
means the measured external noise level (dB LA10(18h)) in 2015.
2031 Level
means the external noise level (dB LA10(18h)) from all roads (including CityLink carriageways and associated existing ramps but excluding East West Link carriageways and associated ramps) based on 2031 traffic volumes.
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 24 OF 294
Phrase
Meaning
Figure A.1 - ramp and sectional definitions
1
PART A
PROJECT SCOPE & REQUIREMENTS – VOLUME 1 OF 3
PAGE 25 OF 294
Part B
PART B
ROAD AND BRIDGE REQUIREMENTS
Project Scope & Requirements – Volume 1 of 3
Page 26 of 294
1.
Design life and residual design life
1.1
Design life 1.1.1
Subject to section 1.1.2, each Asset must have a minimum Design Life that meets the requirements specified in Table B.1 .
1.1.2
Each Asset Component and Asset Sub Component must have a Design Life no less than the Design Life of the Asset unless that Asset Component and Asset Sub Component is identified in Attachment 3 in Table K5.1 of Part K5.
1.1.3
Each Asset Component and Asset Sub Component must have a minimum Design Life that meets the requirements of Attachment 3 in Table K5.1 of Part K5
1.1.4
When an Asset, Asset Component or Asset Sub Component is replaced, the replacement Asset, Asset Component or Asset Sub Component must meet the Design Life requirement of the Asset, Asset Component or Asset Sub Component it has replaced.
1.1.5
If an Asset can be classified in more than one Asset description in Table B.1 then the higher Design Life must apply to that Asset.
Table B.1 – Asset Design Life Requirements
Asset Description
PART B
Design Life Requirement
Tunnel and underpass structures, supports and structural linings
100 years
Bridges and roadway support structures including underpasses
100 years
Reinforced embankments, retaining walls, including reinforced soil walls
100 years
Elements of the drainage, fire protection, lighting, mechanical, electrical, traffic management, and control systems that are not Readily Accessible
100 years
Other major structures including above ground structures of the vent outlets
100 years
Buildings, including ventilation buildings
50 years
Sign support structures and other roadside furniture
50 years
Noise barriers and other noise attenuation devices
40 years
Architectural claddings
40 years
Drainage elements that are Readily Accessible for refurbishment including building drainage and sedimentation and detention ponds
20 years
Project Scope & Requirements – Volume 1 of 3
Page 27 of 294
Asset Description
1.2
Lighting
20 years
Pavement tunnels (excluding surface course)
100 years
Pavement freeways including ramps (excluding surface course)
30 years
Pavement other roads (excluding surface course)
20 years
Pavement surface course – dense graded asphalt
15 years
Pavement surface course – open graded asphalt
8 years
Shared use path and footpath pavements
20 years
Minor structures for shared use paths and footpaths
30 years
Mechanical and electrical equipment
20 years
Traffic management and control systems
20 years
Fire protection systems
20 years
Fencing
15 years
Residual Design Life 1.2.1
Each Asset must have a Residual Design Life as follows: (a)
subject to subparagraph (b), for an Asset with a required Design Life greater than 25 years, the required Design Life for that Asset less the O&M Phase;
(b)
for pavements, the period specified in subparagraph (a) or 10 years, whichever is longer;
(c)
for pavement surface courses, the greater of:
(d)
(e)
(i)
the required Design Life less the O&M Phase; and
(ii)
5 years;
for boundary fencing, the greater of: (i)
the required Design Life less the O&M Phase; and
(ii)
10 years; and
for any other Assets, the greater of: (i)
PART B
Design Life Requirement
the required Design Life less the O&M Phase; and
Project Scope & Requirements – Volume 1 of 3
Page 28 of 294
(ii) 1.3
50 percent of the Design Life requirement.
Design Life of Assets not readily accessible
Where part of an Asset is not Readily Accessible, it must satisfy the Design Life requirements of the Asset of which it forms a part. 1.4
Durability assessment
A durability risk assessment must be undertaken during the design of all buried structures, including foundations, based on the measured soil and groundwater aggressiveness at the relevant part of the Site and submitted as part of the Design Documentation. 2.
Structures
Project Co must ensure that:
PART B
2.1.1
vertical clearances under structures comply with section 3.8;
2.1.2
the traffic design loading for all new structures carrying road traffic is SM1600;
2.1.3
except for CityLink Returned Works, the traffic design loading for widened structures carrying road traffic is: (a)
SM1600 for the new widened part of the structure, including the interface; and
(b)
75% of SM1600 for the existing part of the structure;
2.1.4
appropriate design solutions are developed for critical and non-standard bridge elements that may be susceptible to failure from fire, including the justification of fire protection measures for critical bridge elements through an engineering analysis of risks and collapse scenarios due to fire events;
2.1.5
new bridge elements are designed for earthquakes in accordance with Austroads Technical Report AP-T200-12;
2.1.6
the design loading for shared user path bridges provides for maintenance vehicles;
2.1.7
structures carrying road traffic have approach slabs;
2.1.8
the use of bearings and transverse expansion joints is minimised;
2.1.9
there are no longitudinal expansion joints;
2.1.10
all conduits are concealed;
2.1.11
expansion joints on bridges within 300m of residential properties have a surface flush with the pavement and with a finger or overlapping joint type to minimise traffic noise effects;
2.1.12
in addition to the requirements of AS5100, any piers within the clear zone must be designed and / or protected to prevent collapse of the bridge from a maximum permissible loaded heavy vehicle travelling at the road operating speed which collides with the pier or pier protection system at any and all possible angles;
Project Scope & Requirements – Volume 1 of 3
Page 29 of 294
2.1.13
all structures must meet the requirements of section 13;
2.1.14
all new structures that have designated pedestrian access must include measures designed to prevent pedestrians:
2.1.15
2.1.16
(a)
causing self-harm from the bridge; and
(b)
throwing objects onto the roads below;
design drawings for each structure include full details of: (a)
fixtures, fittings, railings and access provisions to enable safe inspection and maintenance; and
(b)
fixtures, fittings, bracing or Temporary Works required to ensure safe transport and erection of structural components;
Certified Design Documentation for bridges include details that demonstrate integration of and compliance with the following requirements at bridge abutments: (a)
access for future maintenance of abutments and bearings;
(b)
connection to off-structure storm water drainage provisions;
(c)
drainage provisions for the abutment sill beam and for the subsurface drainage behind the abutment;
(d)
connection to off-structure service conduits;
(e)
treatments to ensure the stability and maintainability of batters adjacent to abutment wingwalls and fenderwalls; and
(f)
driven or bored piles must not be used as visible elements of bridge piers and abutments;
2.1.17
any fixtures, fittings, bracing or temporary works required for safe transport, erection or maintaining of structural components must be fully specified in certified Design Documentation.
2.1.18
hydrant points on structures are provided at locations agreed with Emergency Services; and.
2.1.19
despite the provisions of VicRoads BTN1999/018; (a)
chamfers be provided on precast square piles in accordance with VicRoads standard section 614 and clause 11.4.2.1 of AS 5100.3;
(b)
chamfers and fillets must be formed and cast integrally with the concrete member; and
(c)
there must be no cutting or grinding of chamfers.
3.
Road Geometric Design
3.1
Grades
PART B
3.1.1
Grades must be minimised to maximise the traffic throughput of the Freeway;
3.1.2
The upgrade in the tunnels must not exceed 4.0%; and
Project Scope & Requirements – Volume 1 of 3
Page 30 of 294
3.1.3 3.2
The maximum continuous length of carriageway within the tunnels with an upgrade greater than 3% must be less than 600m.
Interchanges and Intersections 3.2.1
3.2.2
Intersections and interchanges, including connections to the Freeway and other freeways, must allow for: (a)
the safe passage of vehicles at the speeds identified in Part H2 and the volumes identified in Part H3;
(b)
the interchange and intersection control identified in Part H4;
(c)
the safe passage of cyclists and pedestrians including people with disabilities; and
(d)
safe access to public transport stops.
The Works must be designed to cater for the design vehicles identified in Table B.2.
Table B.2 - Design vehicles
Element
Single Lane Turns
Multiple Lane Turns
Basic Intersection Layout
AUSTROADS 19m semitrailer (1)
AUSTROADS 19m semitrailer in one turn lane turning concurrently with cars in the other turn lanes(s) (1)
Swept path clearance to obstructions around intersections
AUSTROADS 25m semitrailer (1)
AUSTROADS 25m semitrailer (1)
Eastern Freeway and Hoddle Street bus lane
Single unit truck-bus 12.5m long and Long rigid bus 14.5m long and bi-articulated bus 18.5m long (2)
n/a
Lane widening on curves
AUSTROADS 25.0m semi-trailer
Table Notes: (1) intersection turning speed 5km/h to 15km/h (2) intersection turning speed 0 to 5km/h 3.2.3
3.3
Roadside furniture must be located 500mm clear of the swept path of the design vehicles and must not be within 500mm behind the face of kerb and channel.
Provision for Future Infrastructure
The design of the Works must allow for the future construction of the Future Infrastructure. 3.4
PART B
Sight distance
Project Scope & Requirements – Volume 1 of 3
Page 31 of 294
The design of the Works must incorporate the sight distance parameters identified in Table B.3. Table B.3 - Sight distance requirements
Location
3.5
Reaction Time
Coefficient of Deceleration Cars
Trucks
Tunnels
2.0
0.46
0.29
Surface roads
2.0
0.36
0.29
Sun glare
The design of the Works must minimise the impact of the sun on drivers exiting the tunnels. 3.6
3.7
Lane requirements 3.6.1
The design of the traffic lanes must be in accordance with Part H1.
3.6.2
Ramp lane widths must be 3.5 metres and, where required, include appropriate widening for vehicle tracking.
Cross sectional requirements
Footpath, shoulder, emergency stopping lane, clearances and median widths, must be as identified in Table H1.1. 3.8
Vertical clearances
The minimum vertical clearances must be as identified in Table B.4 or, for locations not listed below, in accordance with VicRoads usual requirements. Table B.4 - Vertical clearances
Location
Minimum vertical clearance (m)
Tunnels
4.9 (1)
Rail lines
5.75
OD Route 3
Refer Part H14
Tram lines
Public Transport Victoria requirements
Note: 1
An additional 200mm above the minimum vertical clearance must be provided for the protection of soft infrastructure including lighting and electronic signage from flapping tarpaulins, ropes, loose loads. 3.9
PART B
Over-dimensional vehicle route
Project Scope & Requirements – Volume 1 of 3
Page 32 of 294
The Works must be designed to allow for over-dimensional vehicles along the route described in Part H14 where they fall within the Project Area. 3.10
Single lane freeway merge entry ramp with 80km/h design speed
For freeway entry ramps entering freeways with a design speed of 80km/h, the merge distance identified in Figure V11.6 of the VicRoads Supplement to AUSTROADS Guide to Road Design – Part 4C may be modified from the stated arrangement of 140m / 80m / 100m to a 100m / 70m / 80m arrangement. 4.
Drainage and flood control
4.1
General 4.1.1
4.2
Drainage and flood control systems must: (a)
comply with the requirements of 0;
(b)
prevent scour and siltation;
(c)
prevent the stormwater generated by a 200 year Average Recurrence Interval (ARI) event, from entering into the tunnels;
(d)
separate cross drainage from road network drainage systems;
(e)
cater for existing drainage systems and flow paths with no additional impact on properties or infrastructure; and
(f)
allow for the Future Infrastructure.
Road network drainage
All road network drainage, except in the tunnels, must be designed for a 10 year ARI event or, where there is no gravity outlet, for a 100 year ARI event. 4.3
Cross drainage
Freeway cross drainage, except in the tunnels, must be designed such that flooding in a 50 year ARI event is confined to the outer shoulder. 4.4
Subsurface drainage
A subsurface drainage system must be provided for all road pavements and behind all bridge abutments and retaining walls. 4.5
Drainage pipes and pits 4.5.1
4.5.2
PART B
Drainage pipes must be: (a)
reinforced concrete and rubber-ring jointed, or other equivalent products approved by the State; and
(b)
visually inspected using CCTV for the full length between pits after completion of earthworks to subgrade level and before commencement of pavement construction.
Any Defects identified by the visual inspection of drainage pipes must be rectified by a method agreed by the State, acting reasonably, before pavement construction commences.
Project Scope & Requirements – Volume 1 of 3
Page 33 of 294
4.5.3 4.6
Realignment of the Alexandra Parade main drain and relief drain 4.6.1
4.7
Drainage pits installed in Returned Works must comply with the usual requirements of the Facility Owner.
Alexandra Parade main drain and relief drain must: (a)
be designed to meet the requirements of Melbourne Water and the requirements described in section 1 of Part H21; and
(b)
connect into the existing pipes just west of the Trenerry Crescent Merri Creek outlet structure so as not to undertake drainage Works in the Merri Creek.
Ross Straw Field water storage tanks and adjacent wetland 4.7.1
Project Co must ensure that the: (a)
(b)
4.7.2
4.8
PART B
(i)
is not significantly diminished by the D&C Activities; and
(ii)
is reinstated to the existing capacity as a condition precedent to Stage One Completion;
the function of the reticulation system from the Ross Straw Field water storage tanks and adjacent wetlands, as currently used by Melbourne City Council: (i)
is not diminished by the D&C Activities or the O&M Activities; and
(ii)
is reinstated to the existing function as a condition precedent to Stage One Completion.
If the net water storage capacity of the Ross Straw Field water storage tanks and adjacent wetlands is proposed to be diminished during the D&C Activities then Project Co must agree with Melbourne City Council an alternative arrangement prior to diminishing the capacity of the storage tanks and wetlands.
Drainage pits in shoulder 4.8.1
5.
net water storage capacity of the Ross Straw Field water storage tanks and adjacent wetlands, as currently used by Melbourne City Council:
Drainage pits within the shoulder or emergency stopping lane must: (a)
be provided with a grate meeting Load Class D in accordance with AS3996-2006 Access Covers and Grates;
(b)
avoid the intrusion of pits and grates into any traffic lane.; and
(c)
be trafficable for cyclists.
Shared use paths and footpaths 5.1.1
The clear path width (handrail to handrail) of new pedestrian and shared use path structures must be at least 3 metres.
5.1.2
A shared use path must be provided along Ramp G and on its approaches to provide a continuous shared use path between Hotham Street and Groom Street.
Project Scope & Requirements – Volume 1 of 3
Page 34 of 294
5.1.3 6.
Unless otherwise agreed by the State or the relevant Facility Owner, shared use path pavements must be saw cut overlapping reinforced concrete.
Traffic barriers 6.1.1
Subject to section 6.1.2 barriers must: (a)
provide continuous cross median protection along the Freeway;
(b)
provide for ease of maintenance of the barrier system and the area surrounding the barrier system;
(c)
provide a traffic barrier performance level as determined by a site specific risk assessment in accordance with the Reference Documents and achieve at least the minimum performance levels provided in Table B.5; and
(d)
protect against significant hazards including retaining walls, noise walls, gantries, vertical abutments, watercourses, buildings, drop offs and cross median protection.
6.1.2
Section 6.1.1 does not apply barriers which are existing at Financial Close unless a traffic running lane and barrier are in closer proximity than existed at Financial Close.
6.1.3
Ramp G pedestrian barrier (a)
The barrier on the outside of the shared use path on Ramp G must: (i)
have maximum through visibility where there is not a residential overlooking issue; and
(ii)
be in accordance with Part B section 2.1.14
Table B.5 - Traffic Barriers
Location (3)
Minimum Barrier Performance Level (1) 2
Structures including approaches over or adjacent to railways.
High
45
2
Structures including approaches , over or adjacent to roads where one of the roads has traffic volumes greater than 40,000 vehicles per day (as specified in Part H3 ). 2
PART B
Structures including approaches over or adjacent to other roads, watercourses, buildings, drop offs, or other significant hazard.
Medium
4
Any modifications to the barriers to the existing Hoddle Street bridge.
Medium
4
Within tunnels.
Regular
Cross median protection.
Regular
Project Scope & Requirements – Volume 1 of 3
Page 35 of 294
Location (3)
Minimum Barrier Performance Level (1)
Existing CityLink elevated structure from Dynon Road to approximately 300m north of Mount Alexander Road
Existing
1. As defined by VicRoads. 2. Bridge approach barriers may be divided into sections of differing performance level. Some sections
may have a performance level less than that identified. Any such reduction must be supported by a site specific risk analysis. The section abutting the bridge must be of the performance level identified and must not be less than 50% of total length of the bridge approach barrier. Sections must only abut another section with a barrier performance level one level lower or higher. Sections must be no less than 5m long. 3. Where a footpath or shared use path is within 2m of a traffic running lane, the barrier must be
between the path and the traffic running lane, where practical. 4. To be barrier and railing type with maximum through visibility. 5. For Ramp G the barrier between the shared use path and the adjacent traffic lanes, and the barrier
on the other side of the traffic lanes must, unless where over or adjacent to railways, be of Medium performance level.
7.
PART B
Pavement, surfacing and linemarking 7.1.1
New shoulder and emergency stopping lane pavements must be designed to meet the traffic volumes of the adjacent traffic lanes.
7.1.2
Dense graded asphalt must be used as the surface course across the full pavement width at ramp terminal intersections, freeway ramp signal sites, on Roads, and in tunnels.
7.1.3
Open graded asphalt must be used as the surface course across the full pavement width at all other locations.
7.1.4
Design of road pavements must be in accordance with the usual requirements of the relevant Facility Owner, subject also to meeting the Design Life requirements.
7.1.5
For all locations where open graded asphalt is required, the lip of kerb abutting the low side of pavements must be flush with the underside of the open graded asphalt. The lip of kerb abutting the high side of pavements must be flush with the top of the open graded asphalt.
7.1.6
The pavement and surface of new or upgraded footpaths, shared use paths and shared use bridges must comply with the usual requirements of the Facility Owner.
7.1.7
Where existing pavement is affected by pavement marking alterations that require removal and reinstatement on an alternative pavement marking arrangement, resurfacing will be required over the extent of the affected area to ensure a blemish-free surface for final pavement marking. Any such
Project Scope & Requirements – Volume 1 of 3
Page 36 of 294
resurfacing must be of the same type as the existing surfacing, unless otherwise agreed with the relevant Facility Owner. 7.1.8
The Freeway carriageway, ramps and Road pavements must be designed to meet the Design Life requirements, using the traffic volumes and vehicle mixes set out in Part H3.
7.1.9
The ride quality of all finished roadways, including bridges, must not exceed the maximum roughness limits as specified in Table B.6.
Table B.6 – Maximum Roughness Limits
Road
Maximum Individual IRIqc (m/km/lane) for any 100 m segment
Maximum Mean IRIqc (m/km/lane) per Work Lot
2.00
1.40
2.30
1.60
2.70
2.00
Freeway carriageways and the following Roads: (a) Eastern Freeway (b) CityLink Freeway ramps and the following Roads: (a) Hoddle Street (c) Alexandra Parade (d) Elliott Avenue (e) Flemington Road (f) Mount Alexander Road (g) Brunswick Road / Ormond Road (h) Racecourse Road All other Roads 8.
Settlement 8.1.1
Settlement must not exceed the following limits in comparison with the design gradeline/profile: (a)
(b)
PART B
structures: (i)
for all minor structures (including waterway crossings, sign gantry structures and pedestrian bridges), total settlement must be no more than 20mm;
(ii)
for all major structures, bridge piers and abutments, total settlement must be no more than 15mm; and
(iii)
maximum differential settlement must be no more than 10mm at all structures; and
other:
Project Scope & Requirements – Volume 1 of 3
Page 37 of 294
8.1.2
8.1.3
9.
the estimated gross settlement including creep (extrapolated on a logarithmic time scale from measured settlements) at any point in earthworks and pavement must not exceed 50mm over the period of 10 years following the Date of Stage One Completion; and
(ii)
within 25 metres of any structure, the maximum grade change must not exceed 0.4%, measured over a distance of 5 metres or less. Estimated settlement creep (extrapolated on a logarithmic time scale) at any point over this length must not exceed 50mm over the period of 10 years following the Date of Stage One Completion.
If anywhere settlement is identified, the settlement must be monitored at a frequency acceptable to the State and reported to the State and to the Independent Reviewer. The settlement monitoring program and reporting must: (a)
clearly indicate the locations of the monitoring points;
(b)
clearly indicate the type of measuring instruments;
(c)
clearly indicate monitoring intervals and length;
(d)
be carried out by a suitably qualified and experienced geotechnical engineer;
(e)
be presented in a form acceptable to the State; and
(f)
be presented in intervals acceptable to the State and include in each monitoring report a prediction of settlement for the next 15 years.
Where a report indicates that settlement exceeds the parameters or is predicted to exceed the parameters identified in section 8.1.1: (a)
a rectification plan must be agreed with the State; and
(b)
the agreed rectification works must be undertaken within the time frame identified in the rectification plan.
Road signing 9.1.1
9.1.2
PART B
(i)
The following signage must be provided: (a)
directional signage within the areas identified in section 1 of Part H9;
(b)
signage in accordance with Part D and section 16 of Part C;
(c)
operational signage in accordance with VicRoads usual requirements; and
(d)
project identification signage reasonably required by the State.
A directional signage scheme must be prepared which: (a)
is consistent with and includes all directional signs identified in section 2 of Part H9;
(b)
supports the integration of the Freeway with the existing arterial road system and the efficient operation of the road network;
Project Scope & Requirements – Volume 1 of 3
Page 38 of 294
(c)
promotes the safe operation of the Freeway and the overall road network;
(d)
informs and directs the movement of motorists in the directional signage area identified in section 1 of Part H9;
(e)
facilitates navigation on the road network, including access to, travel along, and egress from the Freeway;
(f)
ensures consistency with the existing directional signage system on Melbourne's arterial roads, freeways and tollways;
(g)
makes allowance: (i)
in sign face areas; and
(ii)
in gantry placements,
for changes necessary to accommodate Future EWL Stages. 9.1.3
9.1.4
10.
As part of the design of the directional signage scheme: (a)
an inventory of the existing directional signage must be conducted within the extent of the directional signage area as shown in Part H9 ;
(b)
the State’s approval to the scheme must be obtained; and
(c)
a sign face design of the directional signs must be prepared and approved by the State.
As part of the installation of the directional signage scheme: (a)
new signs and supports must be supplied and erected within the directional signage area as shown in Part H9;
(b)
all redundant directional signs and supports must be removed from the directional signage area as shown in Part H9;
(c)
any signs that would be misleading or unnecessary at the time of erection must be effectively secured and masked; and
(d)
redundant existing directional signage must be removed.
Intersection traffic signals 10.1.1
10.1.2
Project Co must: (a)
provide all temporary traffic signals required by WTMP’s and the permanent traffic signals identified in Part H4;
(b)
maintain all traffic signals within the Construction Areas;
(c)
program traffic signal controllers using VicRoads or a VicRoads prequalified contractor; and
(d)
comply with VicRoads usual requirements with respect to intersection traffic signals.
Permanent traffic signals must: (a)
PART B
meet the functional requirements of Part H4;
Project Scope & Requirements – Volume 1 of 3
Page 39 of 294
10.1.3 11.
provide all pedestrian movements (except those across un-signalised left turn lanes);
(c)
provide all bicycle movements associated with a shared use path, including bicycle aspect signal lanterns and detectors;
(d)
provide traffic detectors on all lanes to and from the Freeway;
(e)
incorporate bus priority phasing as identified in Part H6; and
(f)
be connected to VicRoads signal linking system in accordance with VicRoads usual requirements.
Temporary traffic signals must meet the requirements of the relevant WTMP.
Freeway ramp signals 11.1.1
12.
(b)
A freeway ramp signal system must be provided on the ramps identified in Part H7 which: (a)
has the number of lanes at the stop line identified in Part H7;
(b)
has a vehicle storage area to meet VicRoads usual requirements;
(c)
provides bypass lanes as identified in Table H7.2;
(d)
includes VicRoads RC1, RC2 and RC3 signs; and
(e)
is connected to the VicRoads Freeway Management System and either the CityLink traffic management system or the FCC as identified in Table H7.1
Street lighting 12.1.1
Street lighting must comply with the following requirements: (a)
(b)
General (i)
All wiring, except that internal to poles, must be underground.
(ii)
New street lighting for Returned Facilities must have a separate power supply for each Facility Owner.
(iii)
Power supply within the Leased Area must be separate to that of outside the Leased Area.
(iv)
Where lighting is provided or where provisions are required for future lighting, it must meet the requirements of Category V3 in the Australian Standard AS/NZS 1158.
Lighting (i)
Continuous lighting must be provided along: (A)freeways; (B)freeway to freeway ramps; (C)entry and exit ramps;
PART B
Project Scope & Requirements – Volume 1 of 3
Page 40 of 294
(D)other Roads, where lighting exists at date of Financial Close; and (E)shared use paths within underpasses.
13.
(ii)
Tunnels must be lit in accordance with section 12 of Part C.
(iii)
The lighting for the Freeway and Roads must satisfy the requirements of section 1 and 2 of Part H21.
Urban Design and Landscaping 13.1.1
13.1.2
The urban and landscaping design must be developed and implemented to be consistent with the: (a)
Urban Design Framework;
(b)
Part H21 (comprising the Environmental Performance Requirements and the Urban Design Principles)
(c)
requirements of the Approval Decision; and
(d)
section 13.1.2.
The urban and landscaping design must ensure: (a)
elements such as noise barriers, retaining walls and traffic barriers are integrated with one another;
(b)
all exposed concrete finishes on bridges and other structures achieve the requirements of VicRoads standard specifications for Road and Bridge Works - Section 610 – Structural Concrete;
(c)
colour and texture in concrete is achieved through the use of different aggregates, sands, cements and pigments, and through the use of surface textures and patterns. Applied finishes must be avoided, except for anti-graffiti coating;
(d)
drainage details and surface finishes avoid surface staining;
(e)
any rock used in creek works or beaching is consistent with the local geology, where feasible;
(f)
chain mesh fencing is black;
(g)
pedestrian bridges, underpasses and associated approaches are well lit with non-threatening spaces for pedestrians and good visual linkages to entry and exit points to and from surrounding areas;
(h)
bridge spans are open with retained abutments outside the clear zone;
(i)
rock beaching is of a high standard and is consistent with the local geology where feasible;
(j)
bridges over creeks maximise penetration of natural light to protect creek habitat;
(k)
colours of transparent noise walls do not: (i)
PART B
detract from road and public transport safety objectives; or
Project Scope & Requirements – Volume 1 of 3
Page 41 of 294
(ii)
14.
(l)
changes in noise wall height are resolved as a fundamental design consideration;
(m)
timber noise walls are not used unless specifically approved by the State;
(n)
planting densities and the structure and composition of plant communities: (i)
maximise potential for natural regeneration and habitat value; and
(ii)
minimise competition from weeds;
(o)
plantings have a functional lifespan of at least 20 years;
(p)
plantings when matured do not impede design sight distance requirements along roads and paths;
(q)
species that are, or have the potential to become, environmental weeds are not used;
(r)
existing vegetation and other environmentally sensitive areas are fenced, maintained and protected during construction;
(s)
fencing siting, materials and colours are well considered elements consistent with the design concept;
(t)
planting achieves full cover within 2 years of planting; and
(u)
the bridge widening over the Merri Creek may be constructed using a cable stay structure .
Conduit Systems 14.1.1
15.
result in shadow tones cast on private property which are considered unacceptable to abutting property owners;
The following conduit systems must be provided, including: (a)
those required for the operation of the Freeway;
(b)
those required for the operation of the tolling system identified in Part H12;
(c)
those required for the operation of the Department of Justice road safety cameras identified in Part H10;
(d)
those required by VicRoads identified in Part H11;
(e)
those required for the operation of CityLink ITS systems; and
(f)
those required for the State to use as identified in section 17 of Part C.
Emergency services facilities
Facilities must be provided for Emergency Services as required by this PSR. 16.
Tolling hardware
Tolling hardware must be provided in accordance with Part H12.
PART B
Project Scope & Requirements – Volume 1 of 3
Page 42 of 294
17.
Noise
17.1
General 17.1.1
17.2
17.3
PART B
The Works must be designed and constructed to meet the noise requirements of the Approval Decision.
Construction Noise 17.2.1
Permanent noise attenuation must where feasible be installed in advance of construction of adjacent Works.
17.2.2
Temporary noise attenuation must be provided at appropriate locations, to reduce construction noise impacts to sensitive receptors in accordance with the requirements of the Approval Decision.
17.2.3
As a minimum temporary structures must be constructed over the driven tunnel portals to attenuate noise impacts in the surrounding areas from D&C Activities.
Permanent Traffic Noise Attenuation 17.3.1
The Relevant Infrastructure must be designed, constructed and maintained to meet the External Criteria for the Buildings at the Building Location and Situations identified in Table B.7, using the traffic noise generated from the Applicable Roads identified in Table B.7.
17.3.2
If a Building is identified in more than one Building Location and Situation identified in Table B.7, then the lower External Criteria applies.
17.3.3
The External Criteria for Buildings applies to all levels of that Building.
17.3.4
Regardless of the noise attenuation treatment required, if Buildings are protected by existing noise walls, then any replacement noise attenuation treatment must include a noise wall with a height no less than existing.
17.3.5
Where the External Criteria cannot be complied with by practicable means, as defined in the VicRoads Design Note 6-1, and noise from the East West Link carriageways and ramps (based on the design traffic volumes identified in Part H3 ) is predicted to cause the 2031 Level to increase by 2 dB or more, then noise mitigation treatments must be implemented to meet the relevant recommended design sound level of Table 1 of AS2107-2000 at the mid-point between the Satisfactory and Maximum values, applied at all levels of that Building.
17.3.6
When assessing compliance with AS2107, noise must be measured during a typically noisy period relevant to the room occupancy. The measurement duration must be 10 - 60 minutes, or of sufficient duration to be within 1dB of the L Aeq(10min).
17.3.7
All noise levels must be rounded to the nearest decibel.
Project Scope & Requirements – Volume 1 of 3
Page 43 of 294
Table B.7
Building Location and Situation
External Criteria dB
Applicable Roads
LA10(18h)
Western End of EWL (1) (2) For Buildings that have an increase in noise levels as a result of the removal of a CityLink noise barrier.
≤ 63
East West Link carriageways and ramps. CityLink carriageways, inclusive of PAM#1, from Moreland Road to Macaulay Road including all ramps.
For Buildings that have a 2015 Level ≤ 61 dB LA10(18h)
≤ 63
East West Link carriageways and ramps.
For Buildings that have a 2015 Level ≥ 62 dB LA10(18h) and ≤ 66 dB LA10(18h)
2031 Level + 2 OR 68 whichever is the lower
East West Link carriageways and ramps. CityLink carriageways, inclusive of PAM#1, from Moreland Road to Macaulay Road including all ramps.
For Buildings that have a 2015 Level ≥ 66 dB LA10(18h)
≤ 68
East West Link carriageways and ramps. CityLink carriageways, inclusive of PAM#1, from Moreland Road to Macaulay Road including all ramps.
For Buildings that have an increase in noise levels as a result of the removal of an intervening building or structure
≤ 63
Hoddle Street between Roseneath Street and Johnston Street Alexandra Parade between Smith Street and Hoddle Street Eastern Freeway from Yarra Bend Road to East West Link East West Link carriageways Ramps connecting Hoddle Street, Eastern Freeway, Alexandra Parade or East West Link Roads connecting Alexandra Parade and Hoddle Street
For Buildings abutting existing roads within the areas bounded by: Keele Street, Gold Street, Alexandra Parade and Hoddle Street Smith Street, South Terrace/Council Street,
≤ 68
Hoddle Street between Roseneath Street and Johnston Street Alexandra Parade between Smith Street and Hoddle Street Eastern Freeway from Yarra Bend Road to East West Link East West Link carriageways Ramps connecting Hoddle Street, Eastern Freeway, Alexandra Parade
Eastern end of EWL (3) (4)
PART B
Project Scope & Requirements – Volume 1 of 3
Page 44 of 294
Building Location and Situation
External Criteria dB
Applicable Roads
LA10(18h)
Alexandra Parade and Hoddle Street Roseneath Street, Gray Street, Eastern Freeway and Hoddle Street Trenerry Crescent, Abbot Street, Eastern Freeway, and Hoddle Street
or East West Link Roads connecting Alexandra Parade and Hoddle Street
Table Notes: (1) For Ramp A, Project Co must design the Works to meet the noise requirements identified in the requirements of the Approval Decision for Ramp A traffic volumes only. (2) Noise attenuation is not required south of Racecourse Road, other than Ramp A. (3) Noise from traffic using Ramp G must be taken into account in determining noise attenuation requirements. (4) Noise attenuation must be provided to protect properties north of Alexandra Parade which have been exposed to traffic noise due to demolition of intervening buildings, prior to use of the land by Project Co, except where the use of the land is required to allow the installation of noise attenuation measures. 18.
Modifications to VicRoads Publications
18.1
General
18.2
18.1.1
VicRoads Standard Specification for Roadworks and Bridgeworks must be modified according to sections 18.2 to 18.5.
18.1.2
VicRoads Test Methods must be modified according to section 18.6.
Section 605 – Driven Piles 18.2.1
Add the following two paragraphs to clause 605.01 – General. “The procedure for handling piles, including lifting and pitching, shall be shown on the drawings and all cast in fittings and fixtures must be fully detailed.” “Piles shall not be lifted and slung using chains around the pile.”
18.2.2
Add the following sub-paragraph clause to 605.09. “(e) the fabrication of each mechanical splice assemblies being subject to the full inspection and test regime specified in Specification Section 630 – Fabrication of Steelwork, with traceability of each splice to a compliance Certificate and Inspection and Test Plan.”
18.2.3 18.3
PART B
Replace “AS/NZS 1554.1” in clause 605.09(d)(ii) with “AS/NZS 1554.3”
Section 606 – Bored Cast-in-place Piles (Without Permanent Casing)
Project Scope & Requirements – Volume 1 of 3
Page 45 of 294
18.3.1
Add the following to clause 606.06(b). “The use of concrete pump lines without a tremie is prohibited.”
18.4
Section 611 – Steel Reinforcement 18.4.1
Insert the following paragraph at the end of clause 611.10. “The Contractor must provide adequate support and/or bracing of reinforcement cages during construction to ensure stability. Bracing and support requirements for any reinforcement cages higher than 2.5 must be detailed on the certified design drawings.”
18.5
Section 612 – Post-tensioning of Concrete Units 18.5.1
Insert the following paragraph at the end of clause 612.13. “All strands of multi strand tendons with reverse curvature must be post‐tensioned simultaneously. Stressing with a mono strand jack is not permitted.”
18.6
Test Method RC 316.00 - Density Ratio and Moisture Ratio 18.6.1
Replace 2.5(a)(ii) with the following; “Determine the Hilf density ratio and moisture variation in accordance with AS 1289.5.7.1, provided that: if the Hilf Test is used for compaction control, Standard Density Tests must also be carried out to determine an Assigned Value for the material in accordance with AS1289.5.4.2; and the results of the Hilf Test shall not be used if the variation between the density ratio derived using the Hilf Test and the Assigned Value of density ratio from the Standard Compaction Test exceeds 1%.”
19.
PART B
Future EWL Stages 19.1.1
Prior to opening the EWL Future Stages, Project Co may deactivate all street lighting and the displays of the system devices identified in Part D, that are not required for the safe and efficient operation of Stage One, on the section of Stage One that is not open to traffic.
19.1.2
Immediately prior to the opening of EWL Future Stages, Project Co must; (a)
update all the directional signage within the Leased Area to that required for Scenario 2 as identified in Part H9;
(b)
reactivate all the street lighting and the displays referenced in section 19.1.1;
(c)
undertake pavement marking alterations within the Leased Area necessary for the safe and efficient operation of Stage One and EWL Future Stages; and
(d)
undertake linemarking and resurfacing over the extent of the affected area and within the Leased Area, required to ensure a blemish free surface.
Project Scope & Requirements – Volume 1 of 3
Page 46 of 294
Part C
PART C
TUNNELS
Project Scope & Requirements – Volume 1 of 3
Page 47 of 294
1.
General 1.1.1
1.1.2
The tunnels must provide for: (a)
the safe and efficient movement of traffic;
(b)
the support and preservation of existing infrastructure including roads, railways, Utility Infrastructure and buildings and the provision for future requirements including development above or adjacent to the tunnels as described in section 3.2.1;
(c)
the continuous control of internal air quality to meet the Tunnel Reference Documents PIARC Road Tunnels; Vehicle emission and air demand for ventilation 2012 R05EN;
(d)
the continuous management of emission air quality to meet the Environmental Requirements;
(e)
and emission air quality to meet the Environmental Requirements;
(f)
mechanical ventilation and smoke control systems capable of fully functional continuous operation for the range of fire events up to and including the 50MW scenario described in Appendix A of AS4825; 2011 ‘Tunnel fire safety’ for the incident modes prescribed in section 10;
(g)
emergency egress from all areas of the tunnels; and
(h)
effective incident management.
The design and construction of the tunnels must: (a)
minimise whole of life costs;
(b)
comply with the cross section and clearance requirements contained in Part H1 and Table B.4 respectively;
(c)
include detailed risk assessments of all aspects of the proposed tunnel design, construction, operation, repair and maintenance processes; and
(d)
comply with the Tunnel Reference Documents except where there is an Australian Standard equivalent to any British Standard specified in ‘Specification for tunnelling, British Tunnelling Society and Institution of Civil Engineers, Third Edition, 2010’, then the equivalent Australian Standard will prevail.
2.
Tunnel geometric design
2.1
Horizontal and vertical sight distances 2.1.1
PART C
The carriageways in the tunnels must be designed to provide sight distances as applicable to the posted speed shown in Part H2 and with the following design parameters: (a)
sight distance requirements in accordance with Table B.3; and
(b)
friction factors must be based on wet pavements.
Project Scope & Requirements – Volume 1 of 3
Page 48 of 294
3.
Tunnel excavation and support
3.1
Surface Limits
3.2
3.1.1
The tunnel must be constructed as a driven tunnel from Alexandra Parade at Reeves Street, Clifton Hill, to approximately 200 metres east of Elliott Avenue, Parkville, as indicated on the Land Availability Plans.
3.1.2
The cover of the eastern section of the cut and cover tunnel must extend to the eastern side of the Gold Street road reservation in Collingwood.
Future development 3.2.1
Future development of the land above and adjacent to the tunnels or other underground structures must be allowed for by designing and constructing for loading in addition to the design loads applicable to the support of the tunnel excavation. The additional loading requirements are as follows: (a)
Driven tunnels and adjoining underground structures must: (i)
allow for a building vertical load of: (A)50kPa working load acting on the ground at a level of 1m above the tunnel crown and in uniform and patterned (including symmetrical and unsymmetrical) arrangements which give the most unfavourable loading condition on the tunnel; and (B)20kPa equivalent to a build-up of the surface level with 1m of fill and design must allow for the loadings in section 3.2.1(a)(i)(A) and (B) to be applied together and separately; and
(ii)
3.3
PART C
retain a pillar of a minimum 7m width between the side wall of the tunnel and any adjacent building excavation.
(b)
Cut and cover tunnels and adjoining underground structures must allow for a surcharge of 25kPa with a load factor of 1.5 from future building or other development. This loading must be applied at the level of the top of the tunnel roof.
(c)
All tunnels and adjoining underground structures must: (i)
allow for additional loadings from developments which have been approved by the relevant Authority, current at the date of the Agreement; and
(ii)
also be assessed and the underground structures designed to avoid any impacts on these developments.
Permanent support 3.3.1
All underground structures including driven tunnels, cut and cover structures, cross-passages and trough structures must have permanent and durable structural linings.
3.3.2
Rockbolts must not be used as a permanent support in lieu of a structural lining or as a measure to partially relieve loads on a structural lining.
Project Scope & Requirements – Volume 1 of 3
Page 49 of 294
3.3.3
Permanent hold-down anchorages of the invert of the cut and cover and trough structures, where they are subject to uplift, are acceptable provided that construction methods and quality assurance systems ensure the anchorages meet the project durability and Design Life requirements.
4.
Groundwater control and seepage requirements
4.1
Groundwater control 4.1.1
All tunnels, cross passages and associated underground and trough structures must be Undrained from 200m west of The Avenue, Parkville, through to and including the connection with the Eastern Freeway at Hoddle Street.
4.1.2
All tunnels, cross passages and associated underground and trough structures from 200m west of The Avenue, Parkville, through to the western portal near the Upfield Rail Line must also be designed as Undrained, unless a detailed hydrogeological impact assessment and associated risk assessment is carried out to ensure that any water table drawdown and subsequent effects on the groundwater regime caused during the Project Activities or during the required Design Life of the tunnels, has no adverse impact on adjacent property or infrastructure.
4.1.3
The Project Activities must comply with the Environmental Requirements and in any event must minimise: (a)
groundwater contamination over and above any such contamination that may already be present within or adjacent to the Site. This includes contamination migration which covers the potential for drawing contaminated groundwater into existing uncontaminated groundwater within or adjacent to the Works;
(b)
hydrocarbon ingress into the tunnels due to the movement of contaminated groundwater;
(c)
adverse impact on available water for groundwater dependent ecosystems and existing groundwater users, including any adverse impact on the surface water flows of any existing watercourses, and deterioration of vegetation within or adjacent to the Site and
(d)
without limiting section 4.2 below, compliance with sections 4.1.3(a), (b) and (c) above will be achieved by the development and implementation of a comprehensive groundwater instrumentation and monitoring plan (Groundwater Plan) to be agreed by the Independent Reviewer (acting reasonably). The Groundwater Plan, must be developed using Best D&C Practices and must include the following: (i)
details of how Project Co will, prior to commencement of Project Activities with the potential to cause adverse impacts or groundwater movement: (A)identify the potential causes of adverse impacts or groundwater movement; (B)establish a 12 month baseline of relevant information (which takes into consideration historical and predicted natural
PART C
Project Scope & Requirements – Volume 1 of 3
Page 50 of 294
trends) from which continuous comparisons can be made during performance of relevant Project Activities; (ii)
details of the proposed instrumentation to be used and monitoring activities to be performed, including measures such as: (A)grout in place vibrating wire piezometers to obtain real time, precise water pressure data; (B)telemetered open stand pipes with petroleum probes for groundwater and gas monitoring to check for movement of contamination and water level; (C)automated total stations to monitor heritage structures; (D)reflector-less settlement monitoring; (E)INSAR satellite infrared imaging to monitor wider areas; and
(iii)
4.2
4.1.4
Lowering of groundwater levels using permanent dewatering systems by pumping is not permitted.
4.1.5
Any groundwater recharge program during the carrying out of the D&C Activities must be designed and implemented to the satisfaction of relevant Authorities and the State. Long-term recharge of the groundwater table using recharge wells is not permitted.
Groundwater seepage 4.2.1
Tunnel linings and retaining structures must not be visibly wet. Visible weepholes in tunnel linings and retaining structures are not permitted.
4.2.2
No water is to be permitted to drip or flow onto or over road pavements, walkways, egress passages and plant and equipment rooms.
4.2.3
There must be no adverse effects of groundwater chemistry on the overall tunnel structural integrity or the tunnel drainage system, including the potential for the precipitation of insoluble salts to reduce the effectiveness of the drainage system, over the required Design Life of the tunnels.
4.2.4
Without limiting the above requirements, water ingress during the O&M Phase must not exceed the following for Undrained tunnels: (a)
PART C
identification of appropriate triggers for remedial action to minimise adverse impact, and remedial action that will be performed when triggers are activated.
for each 110m length section of tunnel for segmental and insitu lining (excluding the 10m length at the intersection with a cross passage); (i)
0.1 litres per square metre of tunnel surface area per day for that total 110m section; and
(ii)
0.2 litres per square metre of tunnel surface area per day for any 10 metre length of tunnel within each 110m section;
Project Scope & Requirements – Volume 1 of 3
Page 51 of 294
4.2.5
4.2.6
5.
6.
for each 10m length of tunnel for segmental and insitu lining where a cross passage intersects with the main line tunnel, 0.6 litres per square meter of tunnel surface per day; and
(c)
groundwater seepage through the pavement and floors must be nil (zero litres per second).
Without limiting the above requirements, water ingress during the O&M Phase must not exceed the following for Drained tunnels: (a)
gross seepage rate must not exceed 2 litres per second over the full length of the Drained tunnels for the combined inflow from groundwater into both the internal and external drainage systems of the tunnels;
(b)
average seepage rate must not exceed 0.2 litres per second over any 100 metre length of Drained tunnel; and
(c)
groundwater seepage through the pavement and floors must be nil (zero litres per second).
The specified limits for water ingress must be evidenced as not being exceeded as a condition precedent to Stage One Completion and must be maintained thereafter and the specified limits must be satisfied by a measurement methodology agreed by the State.
Drainage system 5.1.1
The drainage system for the tunnels must comply with Part H21 and section 4 of Part B.
5.1.2
As a minimum, the tunnel drainage system must: (a)
accommodate a feasible range of stormwater, incident, groundwater, maintenance and other water ingress events;
(b)
only contain system elements that are flame proof and explosion resistant for areas classified as hazardous;
(c)
continuously monitor, control and record the system's operations as part of an integrated control system within the FCC;
(d)
provide appropriate pump system redundancy; and
(e)
identify, isolate, treat, store and dispose of contaminated water in accordance with the requirements of relevant Authorities.
Tunnel finishes 6.1.1
PART C
(b)
An architectural cladding, must be provided which: (a)
is continuous above the traffic barrier to a height of 4.0m above the roadway;
(b)
is durable, non-distorting and vitreous enamel coated; and
(c)
provides surface reflectance greater than 60 percent for the required Design Life.
Project Scope & Requirements – Volume 1 of 3
Page 52 of 294
7.
Fire and life safety requirements 7.1.1
7.1.2
The fire and life safety systems and facilities forming part of the Works must include: (a)
smoke control in the event of a fire incident;
(b)
emergency egress from vehicular tunnels at intervals to be determined in the FEB process referred to in sections 7.1.3 and 7.1.4;
(c)
fire suppression including hydrants, hose reels and a fixed water based-system;
(d)
linear thermal detection;
(e)
an Emergency Services communication system;
(f)
normal operation lighting and emergency and exit lighting;
(g)
emergency exit signage and low level parapet emergency exit lighting within the tunnel environment including signage indicating direction and distance to safe exits;
(h)
an uninterruptible power supply to: (i)
ensure that the parts of the critical safety systems and essential equipment that are necessary to close and evacuate the tunnel can operate for a minimum of 60 minutes;
(ii)
enable the deluge system to be operational; and
(iii)
enable FCC operators to operate the systems and equipment identified in section 7.1.1(h) (i) and (ii) for a minimum of 60 minutes;
(i)
a reliable water supply, including a valved ring main;
(j)
reliable control systems including redundancy provisions;
(k)
security systems and alarm switches on doors and service cabinets;
(l)
drainage with flame traps and hydrocarbon sensors in the pump wells;
(m)
illuminated and reflective signage and markers;
(n)
all fire protection functions which must be monitored and recorded at the FCC and integrated into the Traffic Management and Control System and Communication System; and
(o)
infrastructure for egress of people within the tunnels and underground structures to a point of safety, and access for Emergency Services.
As a minimum, the fire and life safety measures employed for the Works must achieve the following outcomes: (a)
a level of safety for tunnel occupants and Users that is consistent with Best Industry Practices and the FEB;
(b)
levels of safety and access for: (i)
PART C
operations and maintenance staff during routine activities in accordance with the Tunnel Reference Documents; and
Project Scope & Requirements – Volume 1 of 3
Page 53 of 294
(ii) (c)
7.1.3
Emergency Services personnel during an Incident to meet the requirements of the Emergency Services; and
minimise the impact of incidents on the Relevant Infrastructure, the O&M Activities, in-ground services, adjacent infrastructure and buildings and the surrounding road network including public transport operations.
Fire and life safety systems and facilities must be developed and designed in accordance with: (a)
the requirements of the Emergency Services; and
(b)
the process outlined in AS4825:2011 “Tunnel Fire Safety”.
7.1.4
The outcomes of this process must be documented in a FEB and FER.
7.1.5
An appropriately qualified Fire Engineer (FE) as described in AS4825:2011 must be appointed. The role of the FE must include: (a)
initiating and managing stakeholder consultation with the relevant Authorities in relation to fire and safety matters;
(b)
responsibility for planning, preparing and updating the FEB and FER; and
(c)
ensuring that the fire and life safety systems and facilities forming part of the Works comply with and are consistent with the FEB and the FER.
7.1.6
The Proof Engineer must fulfil the function of a third party reviewer as required by AS4825:2011.
7.1.7
The content of the FEB and FER are to be reviewed and agreed by Emergency Services in accordance with the process outlined in AS4825:2011.
8.
Fire suppression systems
8.1
Hydrants 8.1.1
8.1.2 8.2
8.3
PART C
Hydrants must be installed within: (a)
vehicular tunnels at a maximum of 60m spacing; and
(b)
emergency cabinets.
Two hydrant outlets must be provided in each emergency cabinet.
Hose reels 8.2.1
Hose reels with 36m long hoses must be provided in each emergency cabinet.
8.2.2
Each emergency cabinet must contain a 20-litre foam canister and the necessary equipment to enable either foam or water to be delivered from the hose reel or equivalent system and to the satisfaction of Emergency Services. This replaces the normal requirement of dry chemical extinguishers.
Automatic water based suppression
Project Scope & Requirements – Volume 1 of 3
Page 54 of 294
8.4
8.3.1
An automatic water based fire suppression ’deluge’ system must be provided in all tunnels subject to section 8.3.8.
8.3.2
The system must be zone-based with each zone covering a minimum length of 20 m of roadway in the mainline tunnels and ramps. The arrangement of zones in the merge and diverge areas including the appropriate length shall be in compliance with the area limitations in AS2118.3.
8.3.3
The system must be capable of operating up to 4 deluge zones and 2 hydrant lines simultaneously. The hydrant pressures/flows must comply with the requirements of AS 2419.1.
8.3.4
The system must be designed to operate so that fire fighters can safely approach, fight and control/extinguish a fire or fires.
8.3.5
The system must be designed to control a fire or fires (in accordance with the design fire scenarios) and limit it to the vehicle/s of origin.
8.3.6
The system must be designed for integrated operation with the other fire measures and shall be able to be operated in a timely manner by the tunnel operators.
8.3.7
The system must have a discharge density of a minimum of 10mm/min/m2 of measured road surface.
8.3.8
If a ‘water misting’ type system is proposed as an alternative to a ‘deluge’ system, it must be demonstrated, to the satisfaction of the MFB, that such a system will provide an operational performance equivalent to a ‘deluge’ type system.
8.3.9
Site acceptance testing of the automatic water based suppression system must include: (a)
operation under design conditions at the two most hydraulically onerous locations;
(b)
operation of the system for a minimum period of three minutes; and
(c)
use of suitable collection pans located throughout the operational zones to confirm the density of discharge.
Fire protection water supply 8.4.1
Dual water supplies must be provided in accordance with AS2118.1 "Automatic fire sprinkler systems”.
8.4.2
Suction and booster points for boosting the hydrant system must be provided within the vicinity of each portal of the tunnels at locations agreed with the MFB. Booster points must be fed from independent supplies, separated to avoid cross-contamination of supply.
9.
Fire resistance of tunnel infrastructure
9.1
Fire resistance and fire rating of tunnel structures: 9.1.1
For the purposes of complying with fire resistance and/or fire rating requirements, tunnel structures include: (a)
PART C
driven tunnels;
Project Scope & Requirements – Volume 1 of 3
Page 55 of 294
9.2
cut and cover tunnels;
(c)
escape passages, including cross-passages;
(d)
equipment rooms;
(e)
shafts;
(f)
bridging slabs between adjacent tunnels;
(g)
concrete filler walls;
(h)
vertical rock pillars between adjacent tunnels; and
(i)
horizontal rock pillars between adjacent tunnels.
9.1.2
As a minimum, a 2-hour Modified Hydrocarbon (as defined in the Tunnel Reference Documents) curve must be used as the governing design criteria in areas where the impact of a fire within the tunnel may result in operational failure of existing buildings or infrastructure.
9.1.3
The tunnel structures must be designed to limit spalling so that the outcomes specified in section 3.3 are met. The issue of spalling must be analysed and addressed in the FER.
Fire resistance of tunnel separation 9.2.1
9.3
(b)
As a minimum, the tunnels must be designed to comply with the following: (a)
tunnel carriageways must be separated by a minimum of 240/240/240 separation in accordance with AS1530 "Methods for fire tests on building materials, components and structures";
(b)
cross passage, longitudinal passage and egress doors including joints, openings, and sealants must have a fire rating of not less than /120/120 to AS1530. Two doors separated by a passage are considered to provide a -/240/240 rating; and
(c)
longitudinal passages must have a rating of not less than 120/120/120 to AS1530.
Fire rating of equipment 9.3.1
As a minimum, the tunnels must be designed to comply with the following: (a)
equipment, including associated supports, suspended from the roof of the tunnel, including the ventilation ducts, the jet fans, signage etc, must be maintained, in position, for a period not less than 2 hours when subjected to a temperature of 400oC; and
(b)
all mechanical ventilation system components including fans and dampers must have a fire rating of not less than 2 hours at 250oC.
10.
Smoke management
10.1
Smoke management system 10.1.1
PART C
A smoke management system must be installed in the tunnel comprising suitable ductwork and remotely operated dampers.
Project Scope & Requirements – Volume 1 of 3
Page 56 of 294
10.1.2
For a single incident fire up to and including a 50MW scenario, the smoke management system must be designed to: (a)
establish and maintain tenable conditions for evacuation and for intervention by MFB;
(b)
prevent back-layering of smoke to enable a tenable environment upstream of a fire;
(c)
enable the operation of longitudinal ventilation with smoke extraction to enable a tenable environment for contraflow access by Emergency Services personnel; and
(d)
ensure all cross passages, pedestrian egress tunnels and refuges are pressurised.
10.1.3
The design of the smoke management system, including the capacity of ductwork, must take into account the effect of the automatic water based suppression system.
10.1.4
For a Double Incident scenario the smoke management system must be operated as agreed by the FEB to provide tenability to the greatest extent possible utilising the systems installed capacity defined by the requirements of section 10.1.2.
10.1.5
Site acceptance testing of the smoke management system must be undertaken: (a)
by a series of commissioning, witnessing and integration testing to be carried out in accordance with section 10 of AS4825:2011; and
(b)
subsequently through a series of emergency smoke management tests (hot smoke tests) which must include: (i)
a minimum of two tests in three different locations within tunnels (at least six separate tests): (A)one test involving the simultaneous generation of 1.5MW of heat and 5.0MW of smoke; and (B)the second involving the simultaneous generation of 2.5MW of smoke heat and smoke;
PART C
(ii)
testing of the longitudinal smoke management system with counter flow by Emergency Services vehicles in the tunnels;
(iii)
testing of longitudinal smoke management in the vicinity of a portal in the tunnels;
(iv)
testing of the effect of the automatic water based suppression system and a range of longitudinal air velocities in the tunnel;
(v)
selection of test locations on the basis of simulating the most onerous conditions with at least one point where the downhill gradient is greatest;
(vi)
digital video recording of smoke tests; and
Project Scope & Requirements – Volume 1 of 3
Page 57 of 294
(vii)
tests which demonstrate the ability of all fire safety systems to operate in an integrated manner and provide operational preparedness for Emergency Services and the O&M Subcontractor.
11.
Tunnel power system
11.1
General 11.1.1
11.2
11.3
(a)
ensure continued and uninterrupted operations of essential services in the event of equipment or system failure irrespective of the cause; and
(b)
enable continued operations of the remaining (non-essential) tunnel services at a safe and acceptable functional level with minimum disruptions.
Supply failure 11.2.1
Secured no-break backup power supplies must be installed to ensure there is no adverse impact on the safe operation of the tunnels in the event of a total electricity supply failure.
11.2.2
Secured no-break backup power supplies must provide: (a)
subject to the specific provision for emergency lighting and exit signs in egress routes in paragraph (d), signs, communications, emergency power outlets, closed circuit television and ancillary areas for a minimum period of 1 hour;
(b)
a tunnel management control system and plant management control system for a minimum period of 4 hours;
(c)
all variable message signs (VMS) within the Maintenance Site, vehicle over-height detection devices and incident detection systems for a minimum period of 1 hour; and
(d)
emergency lighting, exit and directional signs in the tunnel and egress routes must be illuminated for a minimum of 90 minutes.
Electrical installation 11.3.1
PART C
The tunnel electrical systems must have a permanent power supply and alternative sources and equipment to:
The following requirements for electrical installation must be met: (a)
conduit, cubicles, trunking, cable tray boxes, metal work and cabling must be designed to withstand a tunnel environment, and must be fire resistant, non-flammable, low smoke, and halogen free and corrosion resistant. Conduit and other wireway materials within the tunnel envelope must meet the fire safety requirements for tunnels; and
(b)
all electrical equipment and cabling must be installed in accordance with the relevant Standards, and must address safety, segregation, adequate rating for maximum demands, voltage drop limitations, durability and operational safety.
Project Scope & Requirements – Volume 1 of 3
Page 58 of 294
12.
Tunnel lighting systems 12.1.1
Tunnel lighting, including emergency lighting, must be designed, installed and put into continuous service in accordance with the Reference Documents including AS / NZS 1158.5 Lighting for roads and public spaces – tunnels and underpasses and CIE No.88 – Guide for the lighting of road tunnels and underpasses, 2004.
12.1.2
The lighting design for the tunnel must be of the symmetrical system type and provide uniform light distribution.
12.1.3
The tunnel lighting sub-circuits must be arranged so that half of the tunnel lighting (each alternate luminaire group (maximum of 3 fittings) or alternate adjacent rows of luminaires) within any one electrical distribution zone remains unaffected by loss of power supply from any one substation main distribution board.
13.
Tunnel ventilation system
13.1
Performance requirements 13.1.1
The tunnel ventilation system must: (a)
(b)
13.1.2
13.2
meet all Environmental Requirements relating to air quality including the requirements of: (i)
EPA Worksafe Exposure Standards; and
(ii)
the Tunnel Reference Documents;
be able to be operated to meet specified in-tunnel and external air quality requirements under all credible atmospheric and traffic flow scenarios.
All necessary investigation, monitoring, modelling, design, works and other activities required to provide a tunnel ventilation system must be carried out in accordance with the Environmental Requirements, including: (a)
background air quality monitoring;
(b)
design, including emissions modelling, for the tunnel ventilation system;
(c)
obtaining any required EPA approval;
(d)
design, construction and installation in accordance with the EPA approval;
(e)
testing and commissioning as necessary to meet the requirements of Emergency Services and any other responsible Authority;
(f)
operating in accordance with any required EPA approval; and
(g)
designing, installing and operating a program of ambient air quality monitoring.
System design
The ventilation system must be designed in accordance with the recognised method described in the PIARC Technical Committee Report: Road Tunnels,
PART C
Project Scope & Requirements – Volume 1 of 3
Page 59 of 294
Vehicle emissions and air demand for ventilation 2012R05EN and any other relevant Tunnel Reference Documents. 13.3
13.4
13.5
Air flow 13.3.1
The ventilation system must be capable of introducing and removing air from the tunnels as required to meet the air quality requirements of this PSR.
13.3.2
All airways must be smooth and free from abrupt cross sectional area changes.
13.3.3
Longitudinal air velocity in the tunnels must be monitored continuously and automatically controlled to a level not exceeding 10 metres/second.
13.3.4
The ventilation system must be capable of being automatically controlled to maintain the specified air quality requirements based on real-time data from air quality, visibility and airflow monitoring. Suitable monitoring equipment must be provided and strategically placed to achieve this outcome.
13.3.5
Null points in the ventilation system must be minimised. In areas where low velocity can occur, an assessment must be undertaken to determine that the required ventilation criteria will be met under all credible atmospheric and traffic flow scenarios.
Management of incidents 13.4.1
The ventilation system must be capable of continuous operation for at least two hours under Double Incident fire mode condition.
13.4.2
In the event of an incident, noxious gases and by-products released into the tunnels must be effectively exhausted from the affected area by appropriate air flow enabling an orderly and safe evacuation of motorists along the emergency egress route.
13.4.3
The ventilation system must be capable of maintaining a minimum tunnel air velocity at any point along the tunnels as required, to prevent smoke back layering. The critical velocity must be achieved with the tunnels full of stationary vehicles.
System components
In addition to any other monitoring, air quality sampling ports and associated infrastructure must be provided at each exhaust outlet and at tunnel portals. 13.6
13.7
Acoustic requirements 13.6.1
With the ventilation system under full load, the octave band spectrum for the ventilation equipment flow must not exceed NR85 as determined in accordance with ISO 1996. Compliance must be demonstrated at any point measured along the centre line of any lane 1.5 m above road level for a situation with no traffic flow.
13.6.2
Maximum allowable external noise levels must comply with the Environmental Requirements.
Modelling of impact of tunnel ventilation emissions 13.7.1
PART C
Appropriate modelling must be undertaken in accordance with EPA requirements and designs refined to meet the Environmental Requirements
Project Scope & Requirements – Volume 1 of 3
Page 60 of 294
in order to substantiate the adequacy of air pollution dispersion to the Environment. The modelling must take into account all combinations of meteorological conditions and traffic flows.
13.8
14.
13.7.2
The modelling must demonstrate that, for the design adopted, air quality achieved at ground level and at receptors at nearby buildings complies with the specified air quality criteria. The modelling must also be used to demonstrate that designs minimise re-ingestion of pollutants into fresh air supplies of the tunnel ventilation system and of the surrounding buildings.
13.7.3
The impact of vehicular emissions must be assessed for both initial traffic flows, and for future traffic flows, to the satisfaction of the EPA. These scenarios investigated must include the assessment of varying flow conditions consistent with predicted traffic volumes.
Operating approval 13.8.1
All activities must be undertaken which are necessary to obtain approval for the operation of the tunnel ventilation system from the EPA.
13.8.2
In addition to the ventilation system design, and monitoring equipment and procedures, Project Co must provide details and calculations showing how contaminated water from spillages, deluge testing, wash down works and the like is to be collected and disposed.
Air quality monitoring 14.1.1
15.
(a)
be to the scope, methodology, standard and duration as reasonably determined by Project Co, and comply with all EPA requirements; and
(b)
comply with the requirements of the National Environment Protection Measures (NEPM) monitoring policy and any requirements of the EPA as expressed in Publication 440.1.
Emergency response facilities 15.1.1
PART C
All air quality monitoring must:
Emergency response facilities must be provided in accordance with the operational and quality standards required by Emergency Services and other relevant Authorities including: (a)
emergency response coordination at the FCC;
(b)
emergency services control points to provide immediate and direct access at the entry and exit zones at each end of the tunnels (either combined set of emergency control points at each end of the twin tunnels, or separate emergency services control points at the entry and exit zone of each tunnel);
(c)
emergency vehicle access from the surface road network, at Manningham Street to both carriageways at the western tunnel portal;
(d)
emergency telephone system for incident communications and management; and
(e)
emergency cabinets within the tunnels.
Project Scope & Requirements – Volume 1 of 3
Page 61 of 294
16.
Operational requirements
16.1
Over-height vehicles
Over-height vehicles must be detected and controlled as identified in section 2.7 of Part D. 16.2
17.
Dangerous goods 16.2.1
Vehicles carrying dangerous goods (as defined in the Dangerous Goods Act 1985, the Regulations made under that Act and the Australian Code for Transportation of Dangerous Goods by Road and Rail) must be prohibited from using the tunnels. All entry ramps must be monitored by CCTV and fixed warning signs must be provided.
16.2.2
Operators of vehicles carrying dangerous goods must be: (a)
warned of the need to divert and the alternative route definition by means of advanced fixed warning signs; and
(b)
if detected entering the tunnels, recorded and reported to relevant Authorities.
State conduit system 17.1.1
A State communication sub system must: (a)
be provided for the sole use of the State and its representatives;
(b)
consist of: (i)
a communication conduit 100mm in diameter which: (A)is continuous between the western and eastern portal communication pits; (B)is constructed in a straight line (where possible) or is a set distance from a continuous roadside element with a minimum radius of 800m;
(ii)
communication pits: (A)which are easily accessible from outside the eastern and western portals; and (B)along the conduit at a spacing to meet the requirements of paragraph (c);
PART C
(c)
be designed and constructed to allow easy installation of cabling by others; and
(d)
be fully self-integrated and not connected to any other power or communication sub system.
Project Scope & Requirements – Volume 1 of 3
Page 62 of 294
Part D
PART D
OPERATIONS MANAGEMENT AND CONTROL SYSTEM
Project Scope & Requirements – Volume 1 of 3
Page 63 of 294
1.
General
1.1
Purpose 1.1.1
1.2
An Operations Management and Control System (OMCS) must be implemented to safely and efficiently: (a)
operate the Freeway;
(b)
monitor and manage traffic and incidents; and
(c)
monitor and control plant and equipment.
Operations Management and Control System 1.2.1
The OMCS must: (a)
provide a high level of automation;
(b)
provide timely presentation of relevant information to operators at the Freeway Control Centre;
(c)
provide support to the operators via a real-time expert system;
(d)
interface with the Asset Management System (AMS); and
(e)
include and monitor:
(f)
1.3
the Traffic Management and Control System (TMCS);
(ii)
the Plant Management and Control System (PMCS);
(iii)
the Communication System (CS); and
(iv)
the periods during which each of the individual devices and systems identified in Annexure C of the Payment Schedule are deemed to be unavailable in accordance with Annexure C of the Payment Schedule; and
be modular, upgradeable and scalable to: (i)
minimise impacts during upgrades; and
(ii)
account for future developments in technology.
Operator interface 1.3.1
PART D
(i)
The OMCS must: (a)
provide a schematic map based graphical user interface;
(b)
provide all alarms in real time;
(c)
display the current status of all devices;
(d)
provide automatic operation together with manual over-ride facilities for each system and system element;
(e)
allow monitoring and control of a single system or multiple systems through operator selection;
Project Scope & Requirements – Volume 1 of 3
Page 64 of 294
1.4
1.5
PART D
(g)
include response procedures to assist operators with the management of all devices.
1.4.1
A comprehensive set of response procedures must be developed for the management of incidents and events and for user training.
1.4.2
The response procedures must be automatically displayed for the relevant alarm or warning.
Trainer system An OMCS trainer system must: (a)
be provided in the Freeway Control Centre;
(b)
provide a user interface identical to the OMCS;
(c)
provide for training functions;
(d)
be capable of simulating all incident and operations managed by the system;
(e)
provide an environment where modifications to the OMCS can be developed and tested; and
(f)
when operating in trainer mode, be easily distinguished from the online system.
Backup system 1.6.1
1.7
provide all alarms and warnings in a clearly visible pop-up window and in a consolidated log (all alarms must be visible and selected alarms audible); and
Response procedures
1.5.1
1.6
(f)
An OMCS backup system must: (a)
be provided at a location remote from the Freeway Control Centre;
(b)
provide a user interface identical to the primary OMCS;
(c)
act as a backup OMCS in the event of a failure of the primary OMCS; and
(d)
be maintained in an operational state at all times and able to function in OMCS back-up mode within three minutes of any failure of the primary OMCS.
Report and logging requirements 1.7.1
All incidents occurring within the Maintenance Site and the Operational Area must be logged in an OMCS event log database. The event log file must provide a record sufficient for audit purposes and the review of event sequences.
1.7.2
Event log files must be organised on a day boundary. Event logs for the previous day must be incorporated into an historic log area with access services available for the review of all historic log file data and retrieval for a minimum preceding period of 13 months.
Project Scope & Requirements – Volume 1 of 3
Page 65 of 294
1.8
1.9
1.7.3
The OMCS must provide comprehensive reporting facilities including full search functionality for the management review of all activity on the OMCS.
1.7.4
The OMCS must have the capability to generate reports on all stored data for any selectable time interval.
Reliability and Performance Requirements 1.8.1
All components of the OMCS computer system must be duplicated for redundancy unless specifically exempted in this section.
1.8.2
The OMCS software architecture must be designed to minimise the risk of cascading failures as the result of a fault in one software module or task.
1.8.3
The failure of any component or software module of the TMCS, PMCS or CS must not cause the failure of any other component or software module of the OMCS.
1.8.4
Individual roadside and other components of the OMCS that are not specified to have in-built redundancy are permitted to fail, provided such failure does not prejudice the overall integrity and availability requirement of the OMCS.
1.8.5
Project Co must demonstrate the availability and system redundancy requirements of this PSR through the conduct of a rigorous failure analysis using an internationally recognised failure analysis methodology.
1.8.6
The OMCS must satisfy the performance requirements included in Part H19.
Scalability 1.9.1
1.10
The OMCS design and configuration must be scalable to: (a)
meet future and short-term demand for additional functionality, scope and dimensions of OMCS functions;
(b)
support cooperative ITS functionality; and
(c)
support 200% more devices.
Freeway Control Centre 1.10.1
A Freeway Control Centre must be provided which is suitable for operational and incident management purposes.
1.10.2
The Freeway Control Centre must: (a)
be of a standard not less than that of existing control centres with similar usage in Australia;
(b)
include high standard facilities for at least 20 visitors to observe the operation of the control room from a separate room with full visibility of the control room. The separate room must be capable of acting as a command post in the event of an incident on the Freeway requiring the attendance of Emergency Services.
2.
Traffic Management and Control Systems
2.1
General
PART D
Project Scope & Requirements – Volume 1 of 3
Page 66 of 294
2.1.1
2.2
The OMCS must include a Traffic Management and Control System (TMCS) which: (a)
monitors traffic and automatically detects incidents within the Leased Area and Operational Area;
(b)
monitors traffic along: (i)
Brunswick Road / Ormond Road, between Pattison Street and Gibson Avenue;
(ii)
Mount Alexander Road / Flemington Road, between Mooltan Street and Boundary Road;
(iii)
Racecourse Road, between Stubbs Street and Ramp T;
(iv)
Alexandra Parade, between Wellington Street and the Eastern Freeway; and
(v)
Hoddle Street, between South Terrace and Johnston Street;
(c)
advises, controls and manages motorists in the Maintenance Site and Operational Area in accordance with the Traffic Management Strategy, the Diversion Traffic Management Plans, Incident Traffic Management Plans and Maintenance Traffic Management Plans;
(d)
integrates with the VicRoads freeway management system STREAMS to ensure seamless coordination of traffic management functions between the Freeway and the Road network;
(e)
integrates the signs and devices of the subsystems; and
(f)
enables electronic requests to signs and devices, from a range of inputs including from the VicRoads traffic management centre and CityLink control centre, to be prioritised so that multiple requests to the same device can be resolved to the highest priority level.
Traffic Management and Control System
The TMCS must incorporate the sub-systems described in sections 2.3 to 2.11 inclusive. 2.3
Tunnel Information Signing System 2.3.1
PART D
The tunnel information signing system must: (a)
display short messages to motorists advising of emergencies, on-road incidents, lane closures and other relevant information;
(b)
incorporate the ability to automatically default to a set message when a major system failure occurs;
(c)
consist of signs which: (i)
are mounted above the carriageway, centrally over each lane, such that the sign is clearly visible from the lane to which the sign applies;
(ii)
are positioned at approximately 200 metre intervals along the tunnel, generally midway between lane use management signs;
Project Scope & Requirements – Volume 1 of 3
Page 67 of 294
2.4
(iii)
are capable of being individually addressed;
(iv)
are capable of displaying operator formed or pre-programmed messages; and
(v)
display the message in white or amber;
(d)
are operated as identified in Table D.1; and
(e)
meet the performance requirements identified in Part H19.
Lane Use Management System (LUMS) 2.4.1
The lane use management system must: (a)
consist of lane control and variable speed limit signs: (i)
mounted above the carriageway, centrally over each lane, such that the sign is clearly visible from the lane to which the sign applies;
(ii)
mounted on gantries which are positioned: (A)in accordance with VicRoads usual requirements; (B)along both Eastern Freeway carriageways between Chandler Highway and the tunnel portals; (C)along both tunnels, no more than 400m apart, generally midway between every second tunnel information sign; (D)along the Freeway from Ramp A to the western tunnel portal and from the western tunnel portal to Point Z; and (E)along Ramp B and Ramp L;
2.5
PART D
(b)
consist of variable speed limit signs along Ramp A, Ramp C1, Ramp C2, Ramp E, Ramp F, Ramp G, Ramp J, Ramp M, Ramp O and the westbound Chandler Highway entry ramp to the Eastern Freeway;
(c)
be operated: (i)
as identified in Table D.1; and
(ii)
in accordance with the VicRoads operating principles;
(d)
meet VicRoads usual requirements;
(e)
meet the performance requirements identified in Part H19; and
(f)
transmit the operating displays of the lane use management signs on the gantry preceding each safety camera site to that road safety camera control box at that road safety camera site.
Variable Message Signing System 2.5.1
A variable message signing system must be provided which consists of variable message signs along freeways.
2.5.2
Variable message signs must:
Project Scope & Requirements – Volume 1 of 3
Page 68 of 294
(a)
2.6
(i)
above the carriageway; and
(ii)
to meet the requirements of the Traffic Management Strategy, Diversion Traffic Management Plans, Incident Traffic Management Plans and Maintenance Traffic Management Plans;
(b)
be operated in accordance with Table D.1;
(c)
meet VicRoads usual requirements;
(d)
include a colour pictogram and conspicuity devices;
(e)
display VicRoads and CML requested traffic information, including VicRoads travel time information, when the sign is not being used to display a message of higher priority; and
(f)
meet the performance requirements identified in Part H19.
Traffic Data System 2.6.1
A real time traffic data system and a daily traffic counting system must be provided.
2.6.2
The real time traffic data system must: (a)
(b)
PART D
be located:
have sites located: (i)
in accordance with VicRoads usual requirements;
(ii)
on the Eastern Freeway within the Operations Area; and
(iii)
on all freeway to freeway ramps at intervals not exceeding 500m;
measure and record in real time at each data station site the: (i)
average speed of the vehicles in each lane in km/h in each 20 second period;
(ii)
total number of vehicles in each lane in each 20 second period; and
(iii)
amount of time each lane is occupied at the data collection point during the 20 second period as a percentage of the total time;
(c)
transmit the data station data to VicRoads Traffic Management Centre as and when required by VicRoads, in accordance with VicRoads usual requirements;
(d)
receive travel time data from VicRoads;
(e)
display the VicRoads travel time data on variable message signs and real time information signs in accordance with the VicRoads usual requirements;
(f)
be operated as identified in Table D.1; and
(g)
meet the performance requirements identified in Part H19.
Project Scope & Requirements – Volume 1 of 3
Page 69 of 294
2.6.3
2.7
The daily traffic counting system must: (a)
identify individual vehicles on each lane of each carriageway of the tunnels between Ramps C/K and Ramps D/J;
(b)
count vehicles by the 12 AUSTROADS classifications;
(c)
record individual vehicles by time (year / month / day of week / hour / minute / second), lane, and AUSTROADS classification;
(d)
store individual vehicle data for easy retrieval for at least 7 years;
(e)
transmit the individual data to the State and VicRoads as and when required by the State, according to State protocols as identified by the State from time to time; and
(f)
meet the performance requirements identified Part H19.
Over-height Vehicle System 2.7.1
An automatic over-height vehicle system must be provided.
2.7.2
The over-height vehicle system must: (a)
detect over-height vehicles;
(b)
classify over-height vehicles into two categories being:
(c)
(d)
(e)
PART D
(i)
class 1 over-height, for vehicles from 4.6m to 4.9m in height (inclusive); and
(ii)
class 2 over-height, for vehicles greater than 4.9m in height;
warn drivers of over-height vehicles with sufficient time to: (i)
not exit CityLink via Ramp A or Ramp B;
(ii)
not use Ramp C1, Ramp C2 and Ramp J; and
(iii)
divert to Ramp H if travelling westbound on Eastern Freeway;
activate the associated portal barriers if class 2 over-height vehicles: (i)
use any of, Ramp A, Ramp B, Ramp C1, Ramp C2, Ramp J and the northbound lanes of the Future EWL Stages; and
(ii)
do not divert at Ramp H as required;
record and store images of over-height vehicles: (i)
passing the over-height detection points;
(ii)
approaching the tunnel (as appropriate); and
(iii)
using the tunnel (as appropriate);
(f)
record and store the class of the over-height vehicle;
(g)
provide areas for over-height vehicles to park safely prior to portal barriers; and
(h)
be operated as identified in Table D.1.
Project Scope & Requirements – Volume 1 of 3
Page 70 of 294
2.7.3
An Operations Traffic Management Plan must be developed and the Works must be designed and constructed to allow over-height vehicles to turn around onto the opposing carriageway.
2.7.4
Within 10 Business Days of any incident where a class 2 over-height vehicle (as described in section 2.7.2(b)(ii)) enters the tunnel:
2.7.5
2.8
an investigation into the cause of the incident to determine whether it was caused by the failure of the Over-height Vehicle System must be completed; and
(b)
a report detailing the outcomes of the investigation, and the rectification measures proposed, must be provided to the State, to the reasonable satisfaction of the State.
All rectification measures identified in the report described in section 2.7.4 must be undertaken within 30 Business Days of providing the report to the State, or such longer period agreed to by the State acting reasonably.
Automatic Incident Detection System 2.8.1
2.9
(a)
The automatic incident detection system must: (a)
alert the FCC operators to incidents within the Maintenance Site and Operational Area;
(b)
be operated as identified in Table D.1; and
(c)
meet the performance requirements identified in Part H19.
Tunnel Portal Barrier System 2.9.1
The portal barrier system must: (a)
be able to be controlled from the Freeway Control Centre and also through on-site control panels;
(b)
consist of tunnel portal barriers:
(c) 2.10
(i)
on the approach to each tunnel portal in order to safely stop vehicles entering the tunnels in the event of an Incident;
(ii)
be located on the approach side of emergency median crossings near each tunnel portal so that traffic access to these emergency median crossings is also controlled;
(iii)
be located at a sufficient distance from the portals to allow a suitable staging area for emergency services during Incidents;
(iv)
allow the passage of emergency and maintenance vehicles; and
be operated as identified in Table D.1.
Closed Circuit Television System 2.10.1
The closed circuit television system must: (a)
consist of cameras: (i)
PART D
located to provide continuous overlapping coverage of:
Project Scope & Requirements – Volume 1 of 3
Page 71 of 294
(A)traffic lanes and emergency stopping lanes within the Leased Area and Operational Area; (B)Brunswick Road / Ormond Road, between Pattison Street and Gibson Avenue; (C)Mount Alexander Road / Flemington Road, between Mooltan Street and Boundary Road; (D)Racecourse Road, between Stubbs Street and Ramp T; (E)Alexandra Parade, between Wellington Street and the Eastern Freeway; (F)Hoddle Street, between South Terrace and Johnson Street; (G)all tunnel cross passages and pedestrian egress routes; and (ii)
2.11
(b)
be operated as identified in Table D.1; and
(c)
meet the performance requirements identified in Part H19.
Variable Lane Configuration Management System 2.11.1
2.12
The variable lane configuration management system must: (a)
provide motorists with a comprehensive, integrated and easily understood linemarking and signage arrangement for each of the options identified in Part H8; and
(b)
be operated as identified in Table D.1.
Integration and Data Transmission 2.12.1
Project Co is responsible for the integration of the TMCS with VicRoads freeway management system – STREAMS to ensure that the Freeway operates seamlessly with the adjacent traffic management devices on the Eastern Freeway and adjacent roads.
2.12.2
Project Co is responsible for the integration of the TMCS with the CityLink freeway management system to ensure that the Freeway operates seamlessly with the adjacent traffic management devices on CityLink;
2.12.3
Integration of the TMCS data into the VicRoads freeway management system - STREAMS must be in accordance with VicRoads usual requirements.
2.12.4
Integration of the lane use management system with the CityLink lane use management system must be in accordance with CityLink Returned Works Requirements.
2.12.5
The TMCS must be able to transmit TMCS data to the VicRoads Traffic Management Centre and receive VicRoads traffic data from the VicRoads Traffic Management Centre which: (a)
PART D
which comply with VicRoads usual requirements;
is in real time;
Project Scope & Requirements – Volume 1 of 3
Page 72 of 294
(b)
complies with the requirements of NTCIP 2306;
(c)
includes agreed message sets as defined by the American Association of State Highway and Transportation Officials (AASHTO) Traffic Management Data;
(d)
complies with the VicRoads Information Security Policy and other relevant VicRoads security requirements and policies; and
(e)
allows the VicRoads Traffic Management Centre operators to seamlessly view the TMCS data on the VicRoads freeway management system - STREAMS.
2.12.6
The TMCS must be able to respond automatically to data transmitted from VicRoads to ensure integration of traffic management devices on the O&M Area with other traffic management devices on the road network.
2.12.7
The transmission of TMCS data to VicRoads must be capable of meeting the performance requirements identified in Part H19.
2.12.8
TMCS data must include: (a)
(b)
PART D
device and sign status of: (i)
the Tunnel Information Signing System;
(ii)
the Lane Use Management System;
(iii)
the Variable Message Signing System ;
(iv)
the Over-height Vehicle System;
(v)
Tunnel Portal Barrier System;
(vi)
the Closed Circuit Television System;
(vii)
the Variable Lane Configuration Management System;
sign content of: (i)
the Tunnel Information Signing System;
(ii)
the Lane Use Management System; and
(iii)
the Variable Message Signing System ;
(c)
real time traffic data from the Traffic Data System;
(d)
simultaneous video from at least 5 Closed Circuit Television System cameras with a transmission quality of at least: (i)
704 x 480 pixels;
(ii)
25 frames / sec; and
(iii)
Mpeg4;
(e)
identification of TMCS implemented Diversion Traffic Management Plans, Incident Traffic Management Plans and Maintenance Traffic Management Plans;
(f)
co-operative ITS data; and
Project Scope & Requirements – Volume 1 of 3
Page 73 of 294
(g) 2.12.9
alarms identifying incidents detected by the Automatic Incident Detection System.
For the purposes of this section 2.12, VicRoads traffic data will include: (a)
video from 5 VicRoads cameras (including from CityLink);
(b)
travel time data;
(c)
VicRoads lane use management sign data to enable Project Co to integrate the VicRoads lane use management system with the Lane Use Management System; and
(d)
other data agreed with VicRoads.
3.
Plant Management and Control System
3.1
General
The OMCS must include a plant management and control system which must monitor and control mechanical and electrical plant associated with the safe and efficient operation and maintenance of the tunnel and other relevant components of the Freeway. 3.2
Plant Management and Control System (PMCS) 3.2.1
The PMCS must: (a)
be designed so that no single point of failure causes: (i)
major performance degradation of one or more elements; or
(ii)
total unavailability of operational functions, which would necessitate the closure of a section of the Freeway;
(b)
be capable of showing the status, alarms and faults of all plant, equipment and other operating systems; and
(c)
be supported by secondary or manual systems to allow tunnels to be safely operated in a mode involving a higher level of operator control in the event of system failure.
4.
Communication System
4.1
General
The OMCS must include a Communication System (CS) which must allow FCC operators to communicate with Freeway Users. 4.2
Communication System Sub-systems 4.2.1
PART D
The CS system must incorporate the following sub-systems: (a)
tunnel radio re-broadcast system;
(b)
tunnel public address system;
(c)
tunnel mobile telephone system;
(d)
Emergency Services telephones; and
Project Scope & Requirements – Volume 1 of 3
Page 74 of 294
(e) 4.3
Tunnel radio re-broadcast system 4.3.1
4.4
(b)
include all Emergency Services radio bands;
(c)
provide sufficient signal strength on all stations to ensure that all users within the tunnel (including equipment rooms, emergency exit areas and cross passages) are capable of receiving re-broadcasts;
(d)
enable an operator in the FCC locally or remotely to temporarily interrupt all live radio channels in the tunnel to transmit live, or prerecorded messages;
(e)
be configured so that each tunnel can be separately interrupted; and
(f)
meet the performance requirements identified in Part H19.
The tunnel public address system, linked to the FCC, must: (a)
be audible in all areas throughout the tunnel environment under all traffic operating conditions;
(b)
be able to be operated automatically or manually; and
(c)
meet the performance requirements identified in Part H19.
The tunnel mobile telephone system must: (a)
provide continuity of service for all mobile phone carriers; and
(b)
meet the performance requirements identified in Part H19.
Emergency telephones and communication systems must; (a)
be provided in accordance with the usual requirements of Emergency Services; and
(b)
meet the performance requirements identified in Part H19.
Help Phone System 4.7.1
PART D
re-broadcast in seamless operation and at no cost to the top 20 government and commercial radio stations in Melbourne;
Emergency Services telephones 4.6.1
4.7
(a)
Tunnel Mobile Telephone System 4.5.1
4.6
The radio re-broadcast system for the tunnels must:
Tunnel Public Address System 4.4.1
4.5
help phone system.
The help phone system must: (a)
meet VicRoads usual requirements;
(b)
be designed to enable effective communication in the noise levels expected along the Freeway and to filter out traffic and other unwanted noise including having an internal adjustment to fine-tune the phones to their surrounding environment; and
(c)
have lighting provisions as per section 12 of Part B.
Project Scope & Requirements – Volume 1 of 3
Page 75 of 294
4.7.2
Help phones must: (a)
be answered as identified in Part H19;
(b)
be located: (i)
such that a person may access a telephone without the need to cross a freeway ramp;
(ii)
outside tunnels; (A)within indented paved breakdown bays when not on a structure; (B)at intervals not exceeding VicRoads usual requirements; (C)on the left and right side of the carriageway and directly opposite each other for carriageways with three traffic lanes or more; and (D)on the left hand side of the carriageway for carriageways that have two traffic lanes; and
(iii) (c) 5.
meet the performance requirements identified in Part H19.
Asset Management System 5.1.1
The Asset Management System must be in full use within 30 days of Stage One Completion.
5.1.2
The Asset Management System must: (a)
maintain a record of the current, historical and projected future condition of each Asset within the Maintenance Site (Asset Inventory) including detailed records of the repair or replacement of Assets, Asset Components and Asset Sub Components to assist in establishing the Residual Design Life of the Assets and Asset Components and Asset Sub Components;
(b)
maintain a record of the nature, extent, quantity, location, time and type of any maintenance activities performed by, or programmed to be performed by, Project Co under the Agreement;
(c)
initiate an appropriate maintenance response to ensure rectification within the response times defined in the Code of Maintenance Standards;
(d)
include a method of reporting to the State on the performance of any Asset by analysis of the specific condition and Defect information recorded for individual Assets, Asset Components and Asset Sub Components;
(e)
incorporate pavement performance models which: (i)
PART D
inside tunnels, at intervals not exceeding 120m; and
record and monitor key pavement performance parameters during the O&M Phase;
Project Scope & Requirements – Volume 1 of 3
Page 76 of 294
6.
(ii)
record and monitor implemented pavement maintenance activities and measured volumes of car traffic and commercial vehicles; and
(iii)
enable modelling of future performance and Residual Design Life for alternative maintenance programs and estimates of expected growth in the volume of car traffic and of commercial vehicles;
(f)
be provided to the State at Handover; and
(g)
retain an historical record of all of the data and information. Each data item must be referenced with the date of the record as appropriate to the type of data.
Lane Use Management and TMCS Integration 6.1.1
Integration and communications between the LUMS and the VicRoads LUMS must be in accordance with Figure D.1.
6.1.2
Integration and communications between Project Co’s LUMS and the CityLink LUMS will be as shown in Figure D.1.
Figure D.1
6.1.3 7.
Traffic Devices Operating Protocols 7.1.1
PART D
The TMCS must provide connection and integrated communications with the CityLink TMCS.
The traffic devices must be operated in accordance with the requirements of Table D.1.
Project Scope & Requirements – Volume 1 of 3
Page 77 of 294
Table D.1 - Traffic Devices Operating Requirements System
Primary Operator
Secondary Operator
Tunnel Information Signing System
Project Co
n/a
Lane Use Management System
Project Co
VicRoads
Variable Message Signing System
Project Co
VicRoads
n/a
n/a
Automatic Incident Detection System
Project Co
n/a
Tunnel Portal Barrier System
Project Co
VicRoads
Closed Circuit Television System
Project Co
VicRoads
Variable Lane Configuration Management System
Project Co
VicRoads
Freeway Ramp Signals
VicRoads
Project Co for EWL and CML for CityLink
Traffic Data System
Special Notes
VicRoads must be able, according to an agreed protocol, to select and control the Closed Circuit Television System.
Table Notes: The Secondary Operator may send an electronic request to the Primary Operator to implement an agreed operation. The Primary Operator then advises the Secondary Operator when the agreed operation has been implemented.
PART D
Project Scope & Requirements – Volume 1 of 3
Page 78 of 294
Part E
PART E
PROPERTY AND LAND
Project Scope & Requirements – Volume 1 of 3
Page 79 of 294
1.
Property Access 1.1.1
2.
(a)
subject to paragraphs (b) to (e), access, amenity and function is maintained to all properties at all times, including to those properties identified in Table H15.1;
(b)
reduction to the level of access to and egress from commercial properties during their normal trading hours is avoided to the greatest extent possible;
(c)
any reduction in the level of access to and egress from any property is limited to the absolute minimum duration necessary to carry out the relevant construction related D&C Activities and is subject to a WTMP;
(d)
all permanent access to any property affected by the D&C Activities must be restored, including associated landscaping and restoration works, and temporary access arrangements removed, within 7 days of completing the activity requiring the temporary access measures or within such other time as agreed with the relevant property owner. The restored permanent access must be to a condition at least equivalent to that existing prior to the commencement of the relevant D&C Activities; and
(e)
without limiting Project Co's obligations under the Agreement, notice must be given to the owner and occupier of a property in respect of which access may be affected by construction related D&C Activities at least 10 Business Days prior to the commencement of such activities. Such notice must include: (i)
a full description of the relevant activities;
(ii)
the impact such activities is likely to have on the property including access to the property; and
(iii)
the 24 hour contact phone numbers through which the owner or occupier of the property may obtain further information or register complaints regarding the carrying out of the activities or the effect of the activities on or near the property.
Fencing 2.1.1
PART E
All things necessary must be done to ensure that:
Subject to section 2.1.2: (a)
fences must be designed and constructed to prohibit pedestrians from accessing the Freeway;
(b)
appropriate boundary fencing must be provided between the Leased Area and abutting land; and
(c)
a security fence must be constructed between any shared use path and the Freeway traffic lanes or ramps.
Project Scope & Requirements – Volume 1 of 3
Page 80 of 294
2.1.2
A boundary fence or a security fence is not required where there is a noise wall which meets the requirements, other than fence type, for the boundary fence or the security fence, as the case may be, at that location.
2.1.3
A new boundary fence may be required when:
2.1.4
(a)
there is no existing boundary fence; or
(b)
the existing boundary fence does not perform the functions as described in section 2.1.5.
Each section of new boundary fencing must: (a)
be accurately located by cadastral survey on the Leased Area boundary defined on the relevant survey plans;
(b)
prevent access by vehicles, persons or animals to the Leased Area at locations other than authorised access points;
(c)
be constructed from materials and to standards that represent good workmanship;
(d)
be in a sound structural condition;
(e)
be of uniform appearance and be maintained free from graffiti when viewed from the Freeway or easily accessible public land;
(f)
provide an acceptable level of privacy to the property where the abutting land use is residential and be at least equivalent to the fence type specified in Table E.1; and
(g)
for private property fencing, be of no lesser standard than any removed fencing or the remainder of the property fencing.
Table E.1 – Boundary Fence Types Abutting Land Use
Fence Type
Residential
Treated pine paling fence. Minimum height 1.8m.
Other
Type K (refer to VicRoads standard drawings).
2.1.5
2.1.6
PART E
Each section of existing boundary fence proposed to be used as the permanent boundary fence must: (a)
be of a condition to prevent access by vehicles, persons or animals to the Leased Area at locations other than authorised access points;
(b)
be in a sound structural condition;
(c)
provide an acceptable level of privacy to the property where the abutting land use is residential; and
(d)
not vary from the Leased Area boundary by more than 100mm, unless otherwise agreed by the State.
Where a concrete safety barrier is required between a shared use path and Freeway traffic lanes, the security fence must be a welded mesh fence erected on top of the concrete safety barrier.
Project Scope & Requirements – Volume 1 of 3
Page 81 of 294
3.
4.
Demolition and Salvaged Materials 3.1.1
All residential buildings falling within the area subject of the Land Availability Plans must be demolished unless otherwise agreed by the State.
3.1.2
Demolition of those buildings must occur: (a)
no later than 5 Business Days after Project Co is to be provided with access to those buildings as contemplated by the Land Availability Plans; or
(b)
such earlier date as notified by the State (subject to the State's notice having been provided to Project Co at least 20 Business Days prior to the date for demolition).
3.1.3
Project Co. is to undertake condition surveys of land immediately after demolition and prior to commencement of any further D&C Activities for all areas of land that are included in the Licensed Construction Area but will not be included in the Leased Area.
3.1.4
The following salvaged materials which have been removed from their in-situ state within the Project Area remain the property of the relevant Facility Owner unless otherwise agreed by the Facility Owner: (a)
bluestone paving and kerbing;
(b)
train rails, sleepers and electrical infrastructure; and
(c)
all other salvaged materials, the retention of which constitutes a usual requirement of the Facility Owner.
3.1.5
Unless otherwise agreed with the Facility Owner, Project Co must make the salvaged material available for collection in a manner and location to facilitate easy loading and transport by the Facility Owner.
3.1.6
The existing pedestrian bridge over the Eastern Freeway, west of Merri Creek, must not be decommissioned until the new pedestrian bridge, east of the Clifton Hill rail line is commissioned.
Condition of Land 4.1.1
Subject to sections 4.1.2, 4.1.3 and Table E.2, any property affected by the D&C Activities, to the extent that such property does not comprise part of the Relevant Infrastructure or the Returned Works must, following the carrying out and completion of the relevant D&C Activities: (a)
be re-instated to at least the standard it was in; and
(b)
provide the same functionality that existed,
immediately prior to the commencement of the D&C Activities by Project Co on that property.
PART E
Project Scope & Requirements – Volume 1 of 3
Page 82 of 294
Table E.2 – Reinstatement of property not comprising Relevant Infrastructure or Returned Works Property
Scope of Reinstatement
Warehousing facilities
Subject to final selection of relevant premises/land including arrangements made with the respective land owner as to how the premises/land is to be left following completion of the works
TBM assembly yard
Subject to final selection of relevant premises/land including arrangements made with the respective land owner as to how the premises/land is to be left following completion of the works
PCC manufacturing facility
Subject to final selection of relevant premises/land including arrangements made with the respective land owner as to how the premises/land is to be left following completion of the works
Property developed within the areas from the Land Availability Plans
Refer section 4.1.3 for land on the north side of Alexandra Parade. For other areas refer to the Urban Design included in Part K
4.1.2
Nothing in section 4.1.1 restricts or affects Project Co's right or obligation to remove infrastructure on, or make improvements to, such land to the extent authorised or required by the Project Agreement.
4.1.3
Land, not comprising road reservation, on the north side of Alexandra Parade between Smith Street and Copper Lane must prior to the termination of the Construction Licence be; (a)
top soil and grassed; and
(b)
permanently fenced with a Type K fence (refer to VicRoads standard drawings) including a locked gate aligned with an existing crossover to enable a maintenance vehicle to access each site.
5.
Land Availability
5.1
Roads and CityLink 5.1.1
PART E
Before Project Co accesses any Roads or CityLink land identified in the Land Availability Plans, Project Co must use its best endeavours to agree a maintenance plan with the Responsible Road Authority for that land which identifies: (a)
the discrete area in respect of which access is required;
(b)
Project Co's maintenance obligations with respect to that discrete area and the assets located on that discrete area;
(c)
the condition of the assets within and, where appropriate, adjacent to, the discrete area;
(d)
the routine inspections to be undertaken;
Project Scope & Requirements – Volume 1 of 3
Page 83 of 294
5.1.2
5.1.3
5.2
5.3
the date from which Project Co will assume maintenance responsibility of the discrete area; and
(f)
the names and contact information of a representative from Project Co and the Responsible Road Authority.
Where Project Co is unable, despite using its best endeavours, to agree a maintenance plan with the Responsible Road Authority within 10 Business Days of first contacting that Responsible Road Authority, Project Co must submit a report to the State: (a)
demonstrating how it used its best endeavours to agree a maintenance plan;
(b)
detailing Project Co's proposed maintenance plan; and
(c)
detailing the reasons why agreement was not able to be reached.
Within 10 Business Days of receiving the report under section 5.1.2 the State will either, unless Project Co and the Responsible Road Authority subsequently agree a maintenance plan: (a)
procure the agreement of the Responsible Road Authority to Project Co's proposed maintenance plan; or
(b)
direct Project Co to comply with a maintenance plan (which may include such amendments to address issues raised by Project Co or the Responsible Road Authority as the State considers appropriate).
5.1.4
Prior to accessing that land, a maintenance plan must be in place (either agreed between Project Co and the Responsible Road Authority or as directed by the State).
5.1.5
Project Co must comply with any maintenance plan agreed or directed under this section 5.1.
5.1.6
Project Co must keep records of all maintenance activities undertaken on the Land and regularly submit them to the Responsible Road Authority and the State, including upon completion of the Works on that land.
Train and Tram 5.2.1
The train and tram interface points associated with the D&C Activities have been nominated as “State Projects” for the purposes of the Rail Projects Agreements.
5.2.2
Without limiting Project Co’s obligations under clause 10.12 of the Agreement, before Project Co accesses any “Rail” land identified in the Land Availability Plans, Project Co must comply with all relevant obligations in relation to “State Projects” under the relevant Rail Projects Agreements.
Land identified hatched blue in the Land Availability Plans 5.3.1
PART E
(e)
Access to the land identified hatched blue in the Land Availability Plans will be made available to Project Co at the date subject to the conditions identified in Table E.3. In the event that Project Co and Facility Owner are unable to agree arrangements with the Facility Owner, at least 20 Business Days before the date identified in Table E.3 , Project Co must notify the
Project Scope & Requirements – Volume 1 of 3
Page 84 of 294
State and, within 20 Business Days, the State will determine the conditions of access. Table E.3 – Hatched blue land conditions
5.4
Location
Date
Conditions
Debneys Park
1/6/15
Maintain public access to the community facilities on the land including, playgrounds, sporting areas, community centre and car parking until replacement facilities, or temporary arrangements as agreed with the Facility Owner, are commissioned.
Ormond Park
14/1/15
Maintain public access to the community facilities on the land including, sporting areas and car parking until replacement facilities, or temporary arrangements as agreed with the Facility Owner, facilities are commissioned.
Holbrook Reserve
14/1/15
Maintain public access to the community facilities on the land including, sporting areas and car parking until replacement facilities, or temporary arrangements as agreed with the Facility Owner, are commissioned.
Underground Strata Land 5.4.1
5.5
15m below the natural surface for all privately owned property; and
(b)
5m for all other land.
No part of Stage One (except works within the stratum Leased Area associated with the tunnels), the Utility Infrastructure or the Maintained OffFreeway Facilities may be located on those areas identified as "Temporary Works Areas" on the Land Availability Plans.
Gas and Fuel Site 5.6.1
6.
(a)
Temporary Works Areas 5.5.1
5.6
The upper limit of the land identified as “UGround Strata” in the Land Availability Plans is:
The Licensed Construction Area does not include: (a)
all the land in the Land Availability Plans identified as the “Gas and Fuel Site 1”; and
(b)
the land in the Land Availability Plans identified as the “Gas and Fuel Site 2” and which is above that land identified in section 5.4.1(b).
Leased Area Plans 6.1.1
Without limiting clause 6 of the Agreement, the Certified Lease Survey Plan and the Stage One Lease Plan must; (a)
PART E
be provided in Type 2, Type 4 and Type 5 formats as defined in Table E.4; and
Project Scope & Requirements – Volume 1 of 3
Page 85 of 294
(b) 6.1.2
7.
8.
identify segments and points for the whole of the boundary of the Leased Area which must be either: (a)
a boundary line within a Survey Plan; or
(b)
a defined point within a Survey Plan.
Maintenance Area Plans 7.1.1
Maintenance plans must be produced to identify the Maintenance Areas (Maintenance Area Plans).
7.1.2
The Maintenance Area Plans must: (a)
be in accordance with clause 6 of the Agreement;
(b)
be provided: (i)
to the State and any relevant Facility Owner as a condition precedent to Stage One Completion or Handback of the Returned Facility (as the case may be);
(ii)
on a photogrammetric base which identifies the completed Works; and
(iii)
in Type 2, Type 4 and Type 5 formats as defined in Table E.4;
(c)
be produced in consultation with the relevant road authority for each Road; and
(d)
identify segments and points for the whole of the boundary of the Maintenance Area which must be either: (i)
a boundary line within a Survey Plan;
(ii)
a defined point within a Survey Plan; or
(iii)
an easily determined and permanent on site location.
Survey Plans 8.1.1
PART E
be provided in an OP format acceptable to both the State and the Surveyor-General; and
Survey plans must be provided which must: (a)
be used by Project Co as the basis for preparation of the Lease Plans, the maintenance plans and road gazettal and authorised access point gazettal plans;
(b)
identify all boundaries (including new boundaries) of different land types;
(c)
be produced to comply with VicRoads standards;
(d)
be signed by VicRoads Property Officer (pursuant to the Survey Coordination Act 1958 (Vic)); and
(e)
identify any surplus land (e.g. land in the Project Area but not in the Leased Area),
Project Scope & Requirements – Volume 1 of 3
Page 86 of 294
(Survey Plans). 9.
Road and Authorised Access Points Gazettal Plans 9.1.1
Road and authorised access points gazettal plans must be provided to enable the Freeway and Roads to be declared.
9.1.2
The road and authorised access points gazettal plans must: (a)
10.
(i)
to the State as a condition precedent to Stage One Completion, at least two months prior to Stage One Completion unless otherwise agreed by the State;
(ii)
in a form agreed by VicRoads;
(b)
be produced in consultation with the relevant road authority for each Road (including CML in respect of CityLink) and with VicRoads for the Freeway;
(c)
be produced in Type 2, Type 4 and Type 5 formats as defined in Table E.4;
(d)
be agreed by the State; and
(e)
identify segments and points for the whole of the boundary of each road declaration which must be either: (i)
a boundary line within a Survey Plan; or
(ii)
a defined point within a Survey Plan.
CML Lease Plans 10.1.1
Lease plans must be provided for CityLink which incorporate the changes to the CityLink leased area that are necessary due to the establishment of the Leased Area (CML Lease Plans).
10.1.2
Without limiting clause 6 of the Agreement, the CML Lease Plans must: (a)
(b)
PART E
be provided:
be provided: (i)
in Type 2, Type 4 and Type 5 formats as defined in Table E.4; and
(ii)
in an OP format acceptable to both the State and the SurveyorGeneral;
(iii)
to the State as a condition precedent to Stage One Completion, at least two months prior to Stage One Completion unless otherwise agreed by the State; and
(iv)
in a form agreed by VicRoads;
identify segments and points for the whole of the boundary of the CML leased area which must be either: (i)
a boundary line within a Survey Plan; or
(ii)
a defined point within a Survey Plan.
Project Scope & Requirements – Volume 1 of 3
Page 87 of 294
11.
Plan Types Table E.4 – Plan Formats Format Type
12.
Definition
1
Electronic .pdf format fully text searchable and selectable
2
Electronic .pdf format with image selectable
3
Electronic CAD as described in section 14.2 of Part F6
4
Electronic GIS as described in section 14.3 of Part F6
5
Printed
Progressive Development
The plans identified in sections 5 to 11 must be prepared and progressively developed. 13.
GIS Data 13.1.1
The latest version of the data identified in Table E.4 must be provided to the State at the times identified so as to present an overall consolidated view of the design.
13.1.2
The GIS data must consist of: (a)
a file for each of the elements;
(b)
a consolidated merged GIS file for all elements with attributes that ensure display, colours, symbolisation and printing of elements is consistent with the digital CAD and PDF files provided.
Table E.5 - GIS Data Element
When required
Field(s) 1
Design Data Lip of Kerb
Status of design
Lane Lines
Status of design
Top of batter
Status of design
Bottom of batter Edge of shared use paths and footpaths Noise walls, fencing and barriers
Within 3 months of Financial Close then every 6 months up to Stage One Completion and as a condition precedent to Close Out
Status of design Status of design Status of design Type (2) Height (m)
Retaining walls
PART E
Status of design
Project Scope & Requirements – Volume 1 of 3
Page 88 of 294
Element
When required
Field(s) 1
New buildings
Status of design
All other civil design elements
Status of design
Leased Area
See sections and 6 and 10
n/a
Maintenance Area
See section 7
n/a
Road and Authorised Access Points Gazettal Plans
See section 9
Emergency Services Telecommunications Authority (ESTA) Data As-Designed Highway Configuration
6 months prior to Stage One Completion
To ESTA requirements
After Construction Actual Road Geometry
Prior to Stage One Completion and when changed thereafter
To ESTA requirements
Shared User Pathway(s)
6 months prior to Stage One Completion and when changed thereafter
To ESTA requirements
(1)
“Status of design” must be a number representing a specific stage of design. Type must be a number representing a specific form (eg 1=concrete noise wall, 2=chain mesh fence, etc). (2)
PART E
13.1.3
The Design Data in Table E.5 must be delivered to the State on CD or other agreed method.
13.1.4
The ESTA data in Table E.5 must be: (a)
delivered to the State and ESTA; and
(b)
delivered on CD or other method agreed by ESTA and Project Co.
Project Scope & Requirements – Volume 1 of 3
Page 89 of 294
Part F
PART F
PROCESS REQUIREMENTS
Project Scope & Requirements – Volume 1 of 3
Page 90 of 294
Part F1
Project Strategies, Project Plans and O&M Manuals
1.
Introduction
1.1
Project Strategies 1.1.1
1.1.2
The intended purpose of the Project Strategies is to describe Project Co's strategies and policies to carry out the Project, including to: (a)
ensure that the Relevant Infrastructure and the Project Activities comply with the requirements of the State Project Documents; and
(b)
demonstrate that Project Co has the understanding, capacity and capability at all times to carry out the Project Activities in accordance with the State Project Documents.
The Project Strategies must not be amended unless: (a)
it is necessary to do so to comply with the State Project Documents, including as a result of a Modification; or
(b)
it is otherwise appropriate to do so,
and the State agrees to the amendment. 1.1.3 1.2
The Project Strategies are attached in Part K.
Project Plans and O&M Manuals 1.2.1
The intended purposes of the Project Plans and O&M Manuals include to: (a)
demonstrate to the State and the Independent Reviewer how Project Co will meet its obligations under the State Project Documents in relation to the Project Activities; and
(b)
document: (i)
the processes and procedures that Project Co, the D&C Subcontractor and the O&M Subcontractor will adopt for the management of the D&C Activities and O&M Activities respectively; and
(ii)
the management accountabilities for ensuring effective implementation of such processes and procedures.
1.2.2
The Project Plans and O&M Manuals must be updated by Project Co in accordance with the timeframes set out in this Part F1.
1.2.3
The preliminary Project Plans are attached in Part K.
1.2.4
Obligation to prepare, update and submit (a)
PART F1
The Project Plans must be: (i)
prepared and updated in accordance with this Part F1;
(ii)
submitted to the State and the Independent Reviewer for review in accordance with the Review Procedures;
Project Scope & Requirements – Volume 1 of 3
Page 91 of 294
1.2.5
(iii)
must be prepared in accordance with all Environmental Requirements, relevant Approvals and conditions on those Approvals prior to being submitted pursuant to this section 1.2.4;
(iv)
as required by any Approval or Approval condition, submitted to the Victorian Minister for Planning or any other Minister of State and the Independent Reviewer in accordance with the Review Procedures.
Minimum Requirements (a)
The Project Plans and O&M Manuals must, as a minimum: (i)
be consistent with the Project Strategies; and
(ii)
where there is a relevant preliminary Project Plan be consistent with, and not limit or reduce the requirements or obligations of Project Co under, the relevant preliminary Project Plan,
except where it is otherwise necessary to comply with the State Project Documents or as otherwise agreed by the State. (b)
1.2.6
Compliance by Project Co with its obligations under this section 1.2 is not evidence of compliance by Project Co with its other obligations under the State Project Documents and does not ensure that Project Co will fulfil all of the requirements of the State Project Documents.
Updating of Project Plans and O&M Manuals (a)
Periodic Updates Each Project Plan and O&M Manual must be reviewed and updated:
(b)
(i)
throughout the period identified in Column 3 of Table F1.1; and
(ii)
subject to the following paragraphs of this section 1.2, at a frequency no less than the frequency specified for each Project Plan and O&M Manual in Column 4 of Table F1.1.
Event Updates Without limiting paragraph (a) above, the Project Plans and O&M Manuals must be further reviewed and, where necessary, updated to take into account events or circumstances which will, or may reasonably be expected to, affect the manner in which Project Co carries out the Project Activities including where:
PART F1
(iii)
any Modification has been implemented;
(iv)
any Change in Mandatory Requirements with which Project Co must comply has occurred;
(v)
any relevant change in Best Industry Practice has occurred;
(vi)
any additional Approvals have been obtained or existing Approvals varied (including to take into account the conditions of any additional Approvals);
(vii)
new phases or stages of design or construction as shown in the D&C Program have commenced;
Project Scope & Requirements – Volume 1 of 3
Page 92 of 294
(viii)
the current Project Plan or O&M Manual: (A)does not adequately address the matters it is intended to address; (B)does not allow Availability and KPI performance to be accurately measured under the Payment Schedule; or (C)has to be changed because of an audit finding; or
(b)
(ix)
any correction of a Defect occurs which will, or may reasonably be expected to, affect the manner in which the Project Activities are carried out; or
(x)
where otherwise required by the Agreement or where the Project Plans and O&M Manuals do not comply with the State Project Documents.
Continuous improvement (i)
The Project Plans and O&M Manuals must be further reviewed and updated to take into account and reflect: (A)relevant changes in technology and work methods for opportunities to improve its processes, particularly processes which affect the safety of and the efficiency of the Freeway; and (B)continuous improvement of the performance of the Project Activities.
(c)
Update at State request (i)
If at any time, Project Co has not updated any Project Plan or O&M Manual in accordance with the requirements of this section, the State may by notice request that the relevant Project Plan or O&M Manual is amended or updated specifying: (A)the reasons why the Project Plan or O&M Manual is required to be updated; and (B)the time within which such amendment or updating must occur (which must be reasonable, having regard to the amount of work required).
(ii)
Upon receipt of such notice, Project Co must: (A)amend or update the Project Plan or O&M Manual as requested by the State; (B)submit the amended or updated Project Plan or O&M Manual to the State and the Independent Reviewer for review in accordance with the Review Procedures within the time specified in the State's notice;
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 93 of 294
(C)as required by any Approval or Approval condition, submitted to the Victorian Minister for Planning or any other Minister of the State, after review by the State and the Independent Reviewer in accordance with the Review Procedures. 1.2.7
Notification
Without limiting section 1.2.5, Project Co must immediately notify the State and the Independent Reviewer of any proposed change to a Project Plan or O&M Manual and the amended Project Plan or O&M Manual must be submitted to the State and the Independent Reviewer within 5 Business Days of such notice for review in accordance with the Review Procedures. 1.2.8
Audit and Monitoring
Project Co must:
1.3
(a)
regularly audit its compliance with each Project Plan and O&M Manual;
(b)
invite representatives of the State and the Independent Reviewer to be present during such audits;
(c)
engage the Environmental Auditor to conduct regular audits of compliance with the CEMP (during the D&C Phase) and the OEMP (during the O&M Phase after the last DLP);
(d)
deliver copies of each audit report to the State and the Independent Reviewer (during the D&C Phase) and to the State (during the O&M Phase after the Last DLP) within 5 Business Days of its completion; and
(e)
permit the Independent Reviewer and the State to conduct monitoring and testing of any aspect of the Project Activities at any time.
Obligation to comply 1.3.1
The Project Activities must be carried out in accordance with: (a)
the Project Strategies; and
(b)
the Project Plans and O&M Manuals.
unless it is necessary to depart from a Project Strategy, Project Plan or O&M Manual in order to comply with the State Project Documents and the departure has been agreed by the State. 1.4
The Project Strategies are as follows: 1.4.1
PART F1
The Business Management Strategy sets out the manner in which Project Co will ensure delivery of the Project Activities in accordance with the Agreement including in relation to: (a)
providing a strategic business framework for the control, coordination and integration of all other strategies and plans;
(b)
Project Co's obligations at Law (including under the Road Management Act);
(c)
internal management and operation of Project Co;
Project Scope & Requirements – Volume 1 of 3
Page 94 of 294
(d)
an outline of strategic business objectives and key success indicators;
(e)
how Project Co will contractually commit to a partnership approach with the State;
(f)
the approach proposed to ensure that a single point of accountability is maintained throughout the life of the Project between: (i)
the State; and
(ii)
Project Co (on behalf of Project Co and its Subcontractors),
including the proposed strategy for managing Subcontractor issues prior to the presentation of those issues to the State;
1.4.2
PART F1
(g)
management of the D&C Subcontractor;
(h)
management of the O&M Subcontractor;
(i)
management of any other major contractors or subcontractors;
(j)
co-ordination of the D&C Subcontractor and the O&M Subcontractor during the D&C Phase, including: (i)
to ensure that the O&M Subcontractor is involved in relevant design issues affecting whole of life considerations and the ongoing operation and maintenance of the Project; and
(ii)
managing the interface between the D&C Subcontractor and the O&M Subcontractor including in relation to Stage One Completion;
(k)
management of Completion activities generally; and
(l)
include Project Co’s construction performance regime during the D&C Phase.
The Traffic Management Strategy sets out the manner in which Project Co will ensure the safe and effective management of traffic for both the D&C Phase and the O&M Phase in accordance with the Agreement, including in relation to: (a)
overall lane use strategy;
(b)
management of the interface with relevant road authorities;
(c)
maximising the efficiency of the surrounding road network; and
(d)
minimising construction and operations impacts associated with: (i)
traffic movements in peak periods;
(ii)
traffic movements in off-peak periods;
(iii)
public transport interfaces;
(iv)
pedestrian and bicycle movements;
(v)
access to local road network;
(vi)
access to properties and facilities; and
(vii)
parking management for local community and construction workforce.
Project Scope & Requirements – Volume 1 of 3
Page 95 of 294
1.4.3
The Environmental Management and Sustainability Strategy sets out the manner in which Project Co will ensure that the Project Activities have minimal impact on the local environment and which addresses all Environmental Requirements, relevant Approvals, any conditions of those Approvals and the PSR. The Environmental Management and Sustainability Strategy must meet the requirements of the Environmental Management Framework and incorporate an Environmental Management System.
1.4.4
The Quality Management Strategy sets out the manner in which Project Co will ensure delivery and operation of the Project in accordance with the Standards and the Agreement.
1.4.5
The Safety Management Strategy sets out the manner in which Project Co will ensure the safe delivery and operation of the Project in accordance with the Agreement.
1.4.6
The Communications and Community Engagement Strategy sets out the manner in which Project Co will ensure the community is properly informed in relation to the Project and the Project Activities.
1.4.7
The Interface Management Strategy must: (a)
identify interfaces and affected stakeholders;
(b)
outline how Project Co proposes to:
(c)
(i)
engage with affected stakeholders; and
(ii)
actively manage these interfaces in partnership with the State;
address, at a minimum, the following interfaces: (i)
during the D&C Phase: (A)working within an urbanised corridor; (B)Eastern Freeway; (C)urban road management and local traffic (VicRoads and council operated roads); (D)construction works (to be undertaken by the Shared Use Path Contractor) on a new shared use bridge over the Eastern Freeway west of Merri Creek; (E)rail interface works and other potential impacts on public transport; (F)construction and commissioning of the toll collection system; (G)Utility Infrastructure and Utilities; and (H)allowance for Future EWL Stages; and
(ii)
during the O&M Phase: (A)coordination with VicRoads (Eastern Freeway, Hoddle Street, broader arterial road network);
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 96 of 294
(B)working with local councils; (C)working with the Tolling Collection Contractor; (D)Utility infrastructure and utility providers; (E)working with potential contractors for construction of Future EWL Stages; and (F)working with operators, and potential operators, of Future EWL Stages; and (iii)
have a separate detailed section in relation to the interface with CML.
2.
Project Plans and O&M Manuals
2.1
D&C Phase Project Plans 2.1.1
Project Delivery Management Plan (a)
The Project Delivery Management Plan must identify the procedures, processes and management systems that will apply in relation to the D&C Activities. As a minimum, the Project Delivery Management Plan must: (i)
define an organisational structure for the D&C Subcontractor that identifies the key positions, roles, and the minimum skills and experience required for each position;
(ii)
provide a framework for how the Works will be divided and delivered in separate construction zones;
(iii)
outline the classification system of Asset Types and Component Types to be used in the Asset Inventory required by section 5.1.2 of Part D, and numbering protocol to be used to uniquely identify each Asset, Asset Component and Asset Sub-Component;
(iv)
describe policies and processes that will ensure: (A)effective input of the O&M Subcontractor into design and construction so as to optimise implementation of whole of life considerations; (B)effective consultation with Facility Owners to facilitate efficient commencement of construction, progressive completion of Returned Works and Handback of Returned Facilities; and (C)compliance with the requirements of Part F5;
(v)
describe strategies and procedures for: (A)managing risk; (B)managing industrial relations; (C)maximising local industry participation;
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 97 of 294
(D)obtaining all necessary Approvals; and (E)schedule management and cost control. 2.1.2
Design Management Plan
The Design Management Plan must;
2.1.3
(a)
identify how Project Co will ensure that the D&C Subcontractor will comply with the design requirements of the Agreement;
(b)
provide within the organisational structure of the D&C Subcontractor the key position roles and the minimum skills and experience required for each position in the D&C Subcontractor’s design team, including its subcontractors, its design verifiers and the position of Proof Engineer;
(c)
include a design program to ensure that Design Documentation is submitted in package sizes and timings that are reasonable and manageable to enable the State, Independent Reviewer and/or Facility Owner to carry out their obligations and respond within required timeframes;
(d)
include processes and allocation of responsibilities that will ensure that: (i)
the Preliminary Design Documentation complies with section 2.2 of Part F5;
(ii)
the Certified Design Documentation complies with section 2.3 of Part F5; and
(iii)
the documentation, certification and notification of proposed changes to IFC Design Documentation comply with section 2.4 of Part F5.
Construction Management Plans
The Construction Management Plans must: (a)
provide: (i)
a framework for delivery of components of the Works within each construction zone including an outline of the Construction Packages required within the zone;
(ii)
construction methodologies for each major construction stage and or key activity;
(iii)
proposed contracting arrangements for key subcontractors and suppliers; and
(iv)
forecast construction risks and impacts including noise, vibration and other community impacts and proposed mitigation measures;
for each of the construction zones outlined in the Project Delivery Management Plan. (b)
include procedures for: (i)
PART F1
the monthly updating of the D&C Program and the monthly progress summary required by Part F2; and
Project Scope & Requirements – Volume 1 of 3
Page 98 of 294
(ii)
2.1.4
the development and approval of Construction Documentation complying with section 2 of Part F6;
(c)
include procedures in relation to survey and condition monitoring;
(d)
include procedures to ensure progressive closure of As-Built Records in accordance with section 11 of Part F6;
(e)
include: (i)
records management indexing protocols that will enable referencing of all design and construction records back to Construction Packages, and Construction Packages to Asset, work type and location;
(ii)
a schedule of Construction Packages which complies with section 1.1 of Part F2; and
(iii)
a protocol (which must be agreed with the State) for notification of all Incidents.
Construction Quality Management Plan
The Construction Quality Management Plan must: (a)
comply with AS/NZS ISO 9001:2000 Quality Management Systems – Requirements;
(b)
nominate and define the responsibility and authority of a management representative (Quality Representative) who has responsibility for ensuring that the requirements of the Construction Quality Management Plan are implemented and maintained;
(c)
define the responsibility, authority and reporting function of personnel primarily responsible for quality assurance, including the name, qualification and scope of each Nominated Authority for the release of Hold Points;
(d)
describe procedures: (i)
to coordinate and implement quality assurance functions across all Project Plans including: (A)audit and surveillance; (B)notification of Hold Points and witness points and release of Hold Points; (C)notification and control of non-conformances; (D)corrective action and process improvement; and
(ii) (e)
in addition to 2.1.4(d), describe procedures that provide: (i)
PART F1
which define the scope, format and indexing of final As-Built Records and of Design Documentation.
the Independent Reviewer with reasonable notice of
Project Scope & Requirements – Volume 1 of 3
Page 99 of 294
(A)Hold Points prior to their release; and (B)witness points;
2.1.5
2.1.6
(ii)
a mechanism for the Independent Reviewer to nominate additional Hold Points and witness points for inclusion in the ITPs and Construction Procedures at any time during the D&C Activities; and
(iii)
access for the Independent Reviewer to attend the release of any Hold Point or witness point.
The Nominated Authority must: (a)
have knowledge of the Design Documentation relevant to the release of a Hold Point;
(b)
not be involved in the day-to-day supervision of the D&C Activities; and
(c)
physically inspect the works and the completed quality assurance documents to verify compliance with the Design Documentation before releasing the Hold Point.
Workplace Relations Management Plan
The Workplace Relations Management Plan must comply with the Victorian Code and Guidelines. 2.1.7
Construction Traffic Management Plan
The Construction Traffic Management Plan must: (a)
PART F1
demonstrate how traffic will be managed throughout the D&C Phase to ensure: (i)
traffic flow is optimised whilst providing a safe environment for all vehicles, cyclists, pedestrians, public transport users and construction personnel, with clear and accurate information for all users; and
(ii)
compliance with the Road Management Act, the Worksite Safety Traffic Management Code of Practice under the Road Management Act and the Agreement;
(b)
include area strategies, including for CityLink, for proposed traffic management arrangements for each interchange or other location where vehicles, cyclists, pedestrians and public transport may be affected;
(c)
be supported by traffic data and analysis to demonstrate that traffic impacts will be minimised and showing the proposed staging provisions for: (i)
temporary traffic and pedestrian routes;
(ii)
managing restricted lane widths;
(iii)
construction clear zones; and
(iv)
property access arrangements;
Project Scope & Requirements – Volume 1 of 3
Page 100 of 294
(d)
address the Environmental Requirements and the requirements of any relevant Approval;
(e)
include procedures and responsibilities for managing and reporting traffic accidents and incidents;
(f)
include procedures and responsibilities for:
(g) 2.1.8
(i)
preparing, reviewing and updating the WTMPs in accordance with section 7 of Part F6;
(ii)
traffic analysis to verify the adequacy of any WTMP;
(iii)
meeting all relevant timing and submission requirements for WTMPs;
(iv)
development and implementation of communications requirements;
(v)
training and induction to ensure that relevant personnel, including subcontractors, are aware of the requirements of the WTMPs; and
(vi)
implementing, auditing and adjusting the WTMPs; and
show any changes to the proposed arrangements for staging the Works, including Temporary Works, and for managing traffic.
Construction Environmental Management Plan
The CEMP must:
PART F1
(a)
be consistent with and meet, as a minimum, all the requirements of the Approval Decision and the Environmental Requirements;
(b)
include procedures and allocation of responsibilities for: (i)
the preparation and distribution of audit reports prepared in accordance with the Incorporated Document and EM3 of section 1 of Part H21, including audit reports assessing compliance with the CEMP;
(ii)
the development, implementation, reviewing, updating and monitoring of site or activity specific WEMPs; and the management of non-conformances, including correction and prevention of such non-conformances;
(c)
detail noise and vibration mitigation measures to be taken during construction;
(d)
outline air and water quality measures to be taken during construction;
(e)
include procedures for managing environmental incidents including: (i)
notifications to Project Co management, site staff, Subcontractors, EPA, Emergency Services and the State;
(ii)
location of on-site information on hazardous materials and dangerous substances; and
(iii)
procedures for spill containment;
Project Scope & Requirements – Volume 1 of 3
Page 101 of 294
2.1.9
(f)
address the Environmental Requirements and the requirements of any relevant Approval; and
(g)
include a site induction and training plan which: (i)
ensures that all personnel, including subcontractors, are familiar with relevant plans and emergency/incident response procedures;
(ii)
ensures systematic recording of required training and training undertaken;
(h)
be developed and updated to ensure that the role of the Environmental Representative remains the responsibility of Project Co;
(i)
define the activity to be managed and the potential environmental impacts to be controlled;
(j)
define responsibilities for developing and implementing the CEMP, verifying compliance with the CEMP before construction commences and monitoring the effectiveness of the CEMP during construction;
(k)
incorporate any additional reasonable requirements of any relevant Authorities; and
(l)
be developed, implemented and maintained in accordance with AS/NZS ISO 14001.
Health and Safety Management Plan
The Health and Safety Management Plan must identify how compliance with all legislative and Project specific occupational health and safety requirements will be achieved during the execution of the Project Activities. The Health and Safety Management Plan must comply with the Victorian Code and the Victorian Guidelines and must address:
2.1.10
(a)
hazard identification and risk analysis;
(b)
induction of all workers before they commence on Site;
(c)
work processes for safe systems of work;
(d)
accident and incident reporting including corrective actions;
(e)
risk assessment; and
(f)
the requirement for a safety culture program.
Construction Communications and Community Engagement Plan
The Construction Communications and Community Engagement Plan must identify how motorists, local communities and other stakeholders will be kept informed of planned D&C Activities (including road closures and changes in traffic conditions) and of progress of the D&C Activities. The Construction Communications and Community Engagement Plan must:
PART F1
(a)
comply with all requirements in Part G;
(b)
provide for the appointment of a communications and community relations representative; and
Project Scope & Requirements – Volume 1 of 3
Page 102 of 294
(c)
include procedures to: (i)
record, monitor and report on enquiries concerning D&C Activities;
(ii)
build and maintain effective relationships with local communities;
(iii)
record, monitor and report on public enquiries;
(iv)
respond in a timely and sensitive manner to matters which are of interest or concern to the community including: (A)project design; (B)significant milestones; (C)changed traffic conditions; and (D)construction activities; and
(v)
use both written and online communications: (A)to develop protocols for media management and liaise with the State on key milestones and opportunities for Project promotion related to the D&C Activities; (B)to address instances where the D&C Activities result in material impacts on the transport network; (C)to address incidents occurring in the Construction Areas which impact on the transport network operations; (D)to deal with complaint resolution including escalation beyond Project Co; (E)for the organisation of Site visits and opening events; and (F)to promote the Project and its benefits.
2.1.11
2.1.12
Terrorism Plan (a)
A Terrorism Plan must be prepared on the basis that the Freeway (or Stage One or EWL as the case may be) is to be declared as an ‘essential service’ under the Terrorism (Community Protection) Act 2003, as amended from time to time (Terrorism Act).
(b)
The Terrorism Plan must provide for the strategies, processes, procedures and responses to be implemented in accordance with the requirements of the Terrorism Act.
Completion and Commissioning Plan
The Completion and Commissioning Plan must define:
PART F1
(a)
planned dates for progressive completion and Handback of Returned Works;
(b)
processes and systems that will be used to monitor all completion and commissioning activities, including closure of Defects;
Project Scope & Requirements – Volume 1 of 3
Page 103 of 294
2.2
(c)
a detailed scope of commissioning tests which must be carried out prior to Stage One Completion and, where applicable, the sequence of such tests;
(d)
any Approvals or acceptances required from relevant Authorities, including Emergency Services;
(e)
the requirements for safety audits; and
(f)
access arrangements for the Tolling Services Contractor.
O&M Phase Project Plans: 2.2.1
O&M Phase Management Plan
The O&M Phase Management Plan must: (a)
identify the procedures, processes and management systems that Project Co will apply in relation to the delivery of the O&M Activities;
(b)
define an organisational structure within the O&M Subcontractor that identifies the key positions, roles and the minimum skills and experience required for each position;
(c)
identify all Subcontractors and suppliers;
(d)
include allocation of responsibilities and procedures for reviewing and updating:
(e) 2.2.2
(i)
operating and maintenance procedures;
(ii)
O&M Manuals;
(iii)
Asset Management System;
(iv)
Code of Maintenance Standards;
(v)
Forecast Maintenance and Refurbishment Plan;
(vi)
Forecast Maintenance and Refurbishment Program; and
(vii)
Forecast Operations Cost Estimate.
include a protocol agreed with the State for notification of all Incidents.
Performance Management Plan
The Performance Management Plan must include the following:
2.2.3
PART F1
(a)
detailed descriptions of the KPIs, the source of data for each KPI, and responsibilities for ensuring the accuracy and currency of such data;
(b)
the KPI measurement and reporting procedures including the methodology and frequency of measurement, the detail to be included in KPI reports, and the detail to be included in KPI summary reports;
(c)
the lane Availability recording and reporting framework, including methodology , the frequency of measurement and detail to be included in the reports; and
(d)
KPI auditing methodology and requirements.
Operations Workplace Relations Management Plan
Project Scope & Requirements – Volume 1 of 3
Page 104 of 294
The Operations Workplace Relations Management Plan must reflect the proposed workplace relations agreements to be entered into in relation to the O&M Activities and must comply with relevant requirements of the Victorian Code and Victorian Guidelines. 2.2.4
Road Management Plan
The Road Management Plan must:
2.2.5
(a)
identify the Standards and procedures to be applied in relation to the maintenance of the Freeway, Roads (to the extent relevant), roadside furniture, existing and new vegetation and other landscape features;
(b)
identify intervention levels for repair and maintenance activities;
(c)
be developed in accordance with the Road Management Act 2004 and the Code of Practice for Road Management Plans;
(d)
be based on standards at least equivalent to the standards for freeways at road maintenance category 1 in VicRoads Road Management Plan; and
(e)
be readily accessible and freely available to the public.
Operations Traffic Management Plan
The Operations Traffic Management Plan must demonstrate:
2.2.6
(a)
how traffic will be managed to ensure traffic flow is optimised whilst providing a safe environment for all vehicles, cyclists, pedestrians and public transport users, with clear and accurate information for all users;
(b)
compliance with the Road Management Act and the Regulations made under that Act, the Worksite Safety Traffic Management Code of Practice and the Agreement;
(c)
procedures to facilitate the effective operational interfaces with VicRoads, CML and other relevant road authorities; and
(d)
how standing DTMPs, MTMPs and ITMPs will be developed for managing and reporting traffic accidents, events, incidents and other emergencies and such plans should include: (i)
procedures for review and update;
(ii)
traffic analysis to verify adequacy;
(iii)
appropriate communications procedures;
(iv)
procedures to ensure training and induction of relevant personnel, including Subcontractors;
(v)
procedures for audit and adjustment; and
(vi)
separate plans to accommodate specific events or scenarios.
Operations Environmental Management Plan
The OEMP must address the potential environmental impacts of the O&M Area and must:
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 105 of 294
(a)
be consistent with and meet, as a minimum, all Environmental Requirements, relevant Approvals and conditions on those Approvals;
(b)
outline the regulatory framework under which the O&M Activities will be undertaken, including a list of any required Approvals;
(c)
identify and assess the potential impacts and risks of environmental damage in relation to sensitive areas described in the Environmental Requirements and any relevant Approval;
(d)
include procedures and responsibilities consistent with all Environmental Requirements for: the development, implementation and monitoring of site or activity specific OEMPs;
(ii)
managing environmental incidents;
(iii)
monitoring and managing air quality;
(iv)
spill containment;
(v)
the preparation and distribution of audit reports prepared in accordance with the Incorporated Document and EM3 of section 1 of Part H21, including audit reports assessing compliance with the OEMP;
(e)
include procedures for notifications to Project Co management, site staff, Subcontractors, the EPA, Emergency Services and the State;
(f)
include a site induction and training plan which ensures:
(c) 2.2.7
(i)
(i)
that all personnel, including Subcontractors, are familiar with relevant plans and emergency/incident response procedures; and
(ii)
systematic recording of required training and training undertaken; and
be developed, implemented and maintained in accordance with AS/NZS ISO 14001.
Operations Health and Safety Management Plan
The Operations Health and Safety Management Plan must identify how Project Co will comply with all legislative and project specific OH&S requirements during the O&M Phase and must:
2.2.8
(a)
address hazard identification and risk analysis;
(b)
address work processes for safe systems of work;
(c)
address accident and Incident reporting including corrective actions; and
(d)
comply with the Victorian Code and Victorian Guidelines.
Operations Communications and Community Engagement Plan
The Operations Communications and Community Engagement Plan must identify how consultation with local communities and other
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 106 of 294
stakeholders in relation to the O&M Activities will be undertaken and must:
2.2.9
(a)
comply with the requirements of Part G;
(b)
deal with the manner in which User calls are responded to so as to meet the performance requirements; and
(c)
include procedures to: (i)
record, monitor and report on public enquiries;
(ii)
build and maintain effective relationships with local communities;
(iii)
manage media communications including liaison with the State;
(iv)
respond to community issues in a timely and sensitive manner;
(v)
resolve complaints including escalation procedures; and
(vi)
promote the Project and its benefits.
Operations Quality Management Plan
The Operations Quality Management Plan must:
2.2.10
(a)
comply with AS/NZS ISO 9001:2000 Quality Management Systems – Requirements;
(b)
nominate and define the responsibility and authority of a management representative (Quality Representative) who has responsibility for ensuring that the requirements of the Operations Quality Management Plan are implemented and maintained; and
(c)
identify procedures which coordinate and implement quality assurance functions across all Project Plans including: (i)
audit and surveillance; and
(ii)
corrective action and process improvement.
Forecast Maintenance and Refurbishment Plan
The Forecast Maintenance and Refurbishment Plan must:
2.2.11
PART F1
(a)
maximise the extent to which the Freeway is open to the general public at all times during the O&M Phase for the safe, efficient and continuous passage of vehicles;
(b)
identify planned expenditure on periodic capital works, asset refurbishment and asset replacement for the Freeway and the Maintained Off-Freeway Facilities (and any revisions to it) in such detail as the State may reasonably require; and
(c)
be reconciled with the Forecast Maintenance and Refurbishment Program and provide details explaining any discrepancy as the State may reasonably require.
Terrorism Plan
Project Scope & Requirements – Volume 1 of 3
Page 107 of 294
The Terrorism Plan (as required by section 2.1.11 must be updated when the Freeway (or Stage One or EWL as the case may be) is declared as an ‘essential service’ under the Terrorism Act and must otherwise be amended at the times and in the manner described in columns 3 and 4 of Table F1.1. 2.2.12
Handover Plan
The Handover Plan must provide the overall strategy for Handover of the Relevant Infrastructure on the Expiry Date and must include details of how the following issues are to be dealt with:
2.3
(a)
operator training;
(b)
demonstration and documentation of the Residual Design Life of the Assets;
(c)
the transfer of all required intellectual property, records and documentation; and
(d)
the disclosure of any liabilities or potential liabilities remaining at Handover.
O&M Manuals
The O&M Manuals must include: 2.3.1
2.3.2
an Asset Management Manual including: (a)
procedures for condition monitoring of Assets;
(b)
an Asset Management System operating manual;
(c)
an index of As-Built Records; and
(d)
procedures for accessing and updating As-Built Records.
a Maintenance Manual which meets the performance requirements in Part H19 and includes: (a)
details of the O&M Subcontractor;
(b)
maintenance procedures, including maintenance recording procedures and safe operating procedures for plant and equipment;
(c)
a schedule of plant and equipment;
(d)
a Freeway Operations Manual, including: (i)
standard operating procedures and protocols to ensure the satisfactory, safe and secure operation of the Freeway and the Maintained Off-Freeway Facilities and the Operational Area including: (A)communication protocols with VicRoads, the State, CML and Emergency Services; (B)operating details for all systems and equipment; and (C)procedures for environmental monitoring;
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 108 of 294
(ii)
(e)
incident management procedures for all types of incidents including vehicle breakdowns, plant failures, electrical supply failures, traffic accidents, fires, spillages, vehicles out of fuel, damage to the Freeway or any part of the Maintained Off Freeway Facilities, injury to persons and other reports received; and
the Code of Maintenance Standards.
2.3.3
Project Co must prepare operation and maintenance manuals with respect to the CityLink Returned Works which comply with sections 2.3.1, 2.3.2 and the CityLink Returned Works Requirements.
2.3.4
Project Co must provide: (a)
the operation and maintenance manuals described in section 2.3.3 to the State, the Independent Reviewer and CML; and
(b)
any training reasonably required in order for CML to be able to take over the CityLink Returned Works,
as a condition precedent to achieving Handback of the CityLink Returned Works. Table F1.1 - Submission and updating requirements for Project Plans and O&M Manuals Name of Project Plan or O&M Manual
Time for Submission
Period during which Project Co must provide updates
Update or Revision Interval
Project Delivery Management Plan
Within 20 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly
Design Management Plan
Within 20 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly
Construction Management Plans
Within 30 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly
Construction Quality Management Plan
Within 20 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly
D&C PHASE PLANS
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 109 of 294
PART F1
Name of Project Plan or O&M Manual
Time for Submission
Period during which Project Co must provide updates
Update or Revision Interval
Workplace Relations Management Plan
On or before Financial Close
From time of initial submission until the Last DLP
6 monthly or as otherwise required by the Construction Code Compliance Unit
Construction Traffic Management Plan
Within 40 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly
Construction Environmental Management Plan
Within 40 A. Business Days after Financial Close
Health and Safety Management Plan
Within 40 Business Days after Financial Close
From time of initial submission until the Last DLP
6 monthly or more frequently if required by the CCCU
Terrorism Plan
Within 40 Business Days after Financial Close
From time of initial submission and thereafter in accordance with the Terrorism Act
in accordance with the Terrorism Act
Construction Communications and Community Engagement Plan
Prior to commencement of construction
From time of initial submission until completion of the Last DLP
6 monthly
Completion and Commissioning Plan
At least 12 months prior to the Date for Stage One Completion
From time of initial submission until the Last DLP
6 monthly
F 6 monthly rom time of initial submission until the Last DLP
Project Scope & Requirements – Volume 1 of 3
Page 110 of 294
Name of Project Plan or O&M Manual
Time for Submission
Period during which Project Co must provide updates
Update or Revision Interval
O&M Phase Management Plan
At least 120 Business Days prior to, and as a condition precedent to, Stage One Completion
From time of initial submission until completion of the O&M Phase
6 monthly
Performance Management Plan
At least 120 Business Days prior to, and as a condition precedent to, Stage One Completion
From time of initial submission until completion of the O&M Phase
6 monthly
Operations Workplace Relations Management Plan
At least 120 Business Days prior to, and as a condition precedent to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
Road Management Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
6 monthly
Operations Traffic Management Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
6 monthly
Operations Environmental Management Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
O&M PHASE PLANS
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 111 of 294
Name of Project Plan or O&M Manual
Time for Submission
Period during which Project Co must provide updates
Update or Revision Interval
Operations Health and Safety Management Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
Operations Communications and Community Engagement Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
Operations Quality Management Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
Forecast Maintenance and Refurbishment Plan
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
Terrorism Plan
In accordance with the Terrorism Act
In accordance with the Terrorism Act
In accordance with the Terrorism Act
Handover Plan
At least 3 years prior to Handover
Until completion of the O&M Phase
Annually
At least 120 Business Days prior to, and as a precondition to, Stage One Completion
From time of initial submission until completion of the O&M Phase
Annually
O&M MANUALS O&M Manuals
PART F1
Project Scope & Requirements – Volume 1 of 3
Page 112 of 294
Part F2
D&C Program
1.
D&C Program
1.1
Construction Packages 1.1.1
1.2
The Works must be subdivided into construction zones and Construction Packages that will be used as a basis for: (a)
the D&C Program;
(b)
packaging of Construction Documentation and construction records; and
(c)
progressive closure of As-Built Records.
1.1.2
The Project Delivery Management Plan must define a standard set of work types and a consistent method for describing location that will be used to identify each Construction Package.
1.1.3
There must be separate Construction Packages for each construction zone for the following: (a)
Preparatory Works;
(b)
Returned Works;
(c)
manufactured precast components or fabricated components;
(d)
Temporary Works;
(e)
significant items of plant or equipment;
(f)
tolling civil works or components thereof; and
(g)
Pre-Agreed Modifications or components thereof (if applicable).
D&C Program Requirements 1.2.1
PART F2
The D&C Program must: (a)
be in the form of a critical path network set out to a time scale of calendar weeks and showing key dates, float, logic links and constraints;
(b)
contain in the order of 2,000 to 3,000 activities unless otherwise agreed by the Independent Reviewer;
(c)
be underpinned by a suite of sub-programs (as sections of the main program) including a sub-program for CityLink on, above or affecting CityLink Works and Rail Interface Works, which provide a greater level of detail of the D&C Activities;
(d)
not include activities, constraints or programming methodologies which have the effect of constraining the program from reacting dynamically to change;
(e)
identify the date of commencement of construction of the Works;
(f)
be in the form of, and consistent with, the Bid D&C Program;
(g)
identify all Key Approvals, Applicable Approvals, and other Approvals that are on the critical path and the dates by which such approvals are
Project Scope & Requirements – Volume 1 of 3
Page 113 of 294
required, and make due allowance for the State or any other Authority responsible for providing the approvals to review Project Co's application and conduct any review or process necessary to determine the application (including any amendment and resubmission of the application which may be undertaken or requested by Project Co); (h)
PART F2
identify each Construction Package and, for each major activity required to complete each Construction Package, show: (i)
activity dependencies;
(ii)
the activity duration;
(iii)
the earliest start and finish dates; and
(iv)
the latest start and finish dates required to avoid a delay to Completion;
(i)
identify significant items of plant and equipment and the labour resources required for each activity and any constraints imposed on the scheduling of activities by the availability of such resources;
(j)
set out the sequence in which, and the times by which, the Preliminary Design Documentation and Certified Design Documentation for each Construction Package is to be submitted to the State and the Independent Reviewer;
(k)
make due allowance for the Design Documentation to be given to the Independent Reviewer within the time: (i)
which will enable the Independent Reviewer to conduct a general overview and reasonable checking of the Design Documentation; and
(ii)
required by the Agreement, and for any amendment and resubmission of the Design Documentation and any other activities or matters which are required to be accommodated by the Agreement;
(l)
identify the dates or periods for the review or comment on the Design Documentation by the State, the Facility Owners and the Independent Reviewer consistent with the Agreement;
(m)
clearly demonstrate the actual and then current critical path to achieve Completion;
(n)
allow adequate time for the preparation, and review in accordance with the Review Procedures, of all Project Plans and O&M Manuals;
(o)
accommodate the impact of the proposed construction on the surrounding environment and community including local traffic implications and an outline of the proposals to deal with those implications, including compliance with the Construction Traffic Management Plan and the Construction Environmental Management Plan;
(p)
identify the proposed commissioning tests for the Works and a program for the timing of those commissioning tests;
Project Scope & Requirements – Volume 1 of 3
Page 114 of 294
PART F2
(q)
identify the time allowed for the Tolling Services Contractor to carry out the Tolling Services Works;
(r)
identify the anticipated Dates of Handback of Returned Works to the relevant Facility Owners;
(s)
identify any other matters which may have a bearing on the time required to complete the D&C Activities in accordance with the Agreement;
(t)
identify the award of any Material Subcontract or other agreement which is significant to the performance of the D&C Activities;
(u)
include such other information as the State and the Independent Reviewer may reasonably require; and
(v)
be provided in Microsoft Project or Primavera P6 format or other format agreed by the State and the Independent Reviewer.
Project Scope & Requirements – Volume 1 of 3
Page 115 of 294
Part F3 1.
Road Safety Audits 1.1.1
2.
Safety Audits Road safety audits must be conducted by a suitably qualified road safety auditor who is independent of Project Co, the D&C Subcontractor and the O&M Subcontractor: (a)
during the design of the Works;
(b)
as required for traffic management activities;
(c)
prior to opening any part of the Relevant Infrastructure to traffic; and
(d)
immediately following the opening of any parts of the Relevant Infrastructure to traffic.
Safety Audit Reports 2.1.1
All corrective actions identified in a safety audit report must be promptly addressed.
2.1.2
The Traffic Representative must be responsible for addressing the recommendations of road safety audits.
2.1.3
All corrective actions which are contrary to any safety auditor’s recommendations must be approved by the Traffic Representative.
2.1.4
Copies of records of all corrective actions implemented, and identifying the Traffic Representative who approved the corrective action, must be promptly provided to the State and the Independent Reviewer after each road safety audit.
PART F3
Project Scope & Requirements – Volume 1 of 3
Page 116 of 294
Part F4 1.
Site and Survey
Investigation, Condition Survey and Monitoring
All site investigations, property, land and condition surveys and ground and infrastructure condition surveys must be undertaken as required for the performance of the D&C Activities. 2.
Condition surveys 2.1.1
Subject to 2.1.2: (a)
(b) 2.1.2 3.
4.
condition surveys must be: (i)
undertaken to accurately record the condition of existing ground and infrastructure prior to the commencement of the D&C Activities.
(ii)
undertaken with the prior approval of the relevant property owner and/or occupier, for all assets that are reasonably accessible and within 50m of the Project Activities, or other assets that may be affected by the Project Activities unless otherwise agreed by the State; and
(iii)
forwarded to the owner of the asset, the State and the Independent Reviewer within 4 weeks of the condition survey being undertaken; and
all condition surveys must be carried out by independent qualified assessors.
In relation to CityLink, Project Co must undertake condition surveys in accordance with the CityLink Access Deed.
Monitoring 3.1.1
Prior to commencing any part of the Project Activities, a monitoring strategy must be developed and implemented.
3.1.2
The monitoring strategy must include: (a)
any monitoring requirements identified in the Environmental Requirements;
(b)
any usual requirements of relevant Authorities and Facility Owners;
(c)
all necessary monitoring devices to monitor the actual effects of performance of the Project Activities where the ground conditions or infrastructure are expected to be affected by the performance of the Project Activities; and
(d)
the establishment of the baseline conditions.
Site Reinstatement 4.1.1
PART F4
Construction Areas, and any other land accessed for the purposes of carrying out any part of the Works, must be progressively reinstated (subject to the
Project Scope & Requirements – Volume 1 of 3
Page 117 of 294
carrying out of the Works) as each part of the Works is completed, as a condition precedent to Handback or Stage One Completion (as applicable). 4.1.2
PART F4
Subject to section 4.1.1 of Part E, all temporary areas and other land accessed or used for the purpose of the D&C Activities, including storage and site facilities, must be reinstated to a condition at least equivalent to that existing prior to their occupation or use after Project Co has departed the land.
Project Scope & Requirements – Volume 1 of 3
Page 118 of 294
Part F5
Design
1.
General
1.1
Preparation and submission of Design Documentation 1.1.1
1.2
The design of the Works must be: (a)
consistent with the Concept Design;
(b)
developed and completed in accordance with this Design Review Section and the State Project Documents; and
(c)
Fit For Purpose.
Changes to the Concept Design 1.2.1
The process of developing the design from the Concept Design to the IFC Design Documentation may result in changes to the Concept Design.
1.2.2
Subject to section 1.2.3, changes to the Concept Design must not be made unless: (a)
(b)
1.2.3
the change: (i)
is notified to the Independent Reviewer; and
(ii)
is necessary to comply with the State Project Documents; or
it is demonstrated to the satisfaction of the Independent Reviewer that the change: (i)
is minor; and
(ii)
is consistent with the design intent in the Concept Design, otherwise complies with the State Project Documents and does not result in a reduction of any Relevant D&C Requirement of any part of the Works.
Any change to the Concept Design which is not a change of the kind described in paragraph (b) may only be made if the change is agreed by the State.
2.
General Requirements for Design Documentation
2.1
Submission of Design Documentation
2.2
2.1.1
Preliminary Design Documentation must be submitted to the State and the Independent Reviewer in accordance with section 2.2.
2.1.2
Certified Design Documentation must be submitted to the State and the Independent Reviewer in accordance with section 2.3.
Preliminary Design 2.2.1
Preliminary Design Documentation must include: (a)
a preliminary design report which: (i)
PART F5
identifies the Construction Package(s) to which the Preliminary Design Documentation relates;
Project Scope & Requirements – Volume 1 of 3
Page 119 of 294
(ii)
identifies the aspects of the Design Management Plan to which the Preliminary Design Documentation relates;
(iii)
identifies all Reference Documents used in the preparation of the Preliminary Design Documentation;
(iv)
demonstrates that all relevant performance requirements including constructability, maintenance and operations requirements have been met and integrated into the Preliminary Design Documentation;
(v)
demonstrates that: (A)the Preliminary Design Documentation is consistent with the urban and landscape design elements of the Concept Design and the requirements of section 2 of Part H21. (B)where appropriate, advice has been sought from suitably qualified zoologists, marine biologists/aquatic specialists, ecologists and flora and fauna experts to ensure that potential environmental issues have been addressed; and (C)the Future Infrastructure has been considered and any future modifications required to construct the Future Infrastructure have been minimised to the fullest extent practicable;
(vi)
documents the outcomes of a formal safety-in-design assessment including, where applicable, the performance level for safety barriers and the personal security of users of pathways;
(vii)
includes a flood impact assessment for any Construction Package involving major drainage structures, stream crossings, or changes to road geometry that could affect patterns of stormwater drainage;
(viii)
includes all relevant geotechnical information and the results of any geotechnical analysis required for the design, including: (A)any durability assessment required by section 1 of Part B; (B)any assessment of tunnel, embankment or excavation stability; (C)likely settlement and any treatments required to achieve the requirements of section 8 of Part B; and (D)any assessment of the capacity of recommended foundations for structures;
(b)
PART F5
(ix)
identifies any changes to the Concept Design and the justification for such changes in accordance with section 1.2; and
(x)
contains any other information required by the State Project Documents;
all design drawings necessary to adequately define the preliminary design and demonstrate that the relevant elements of Stage One are wholly contained within the Leased Area; and
Project Scope & Requirements – Volume 1 of 3
Page 120 of 294
(c)
2.3
a schedule of the Assets, Asset Components and Asset Sub Components to which the report and layout drawings showing the location of each Asset.
2.2.2
The Preliminary Design Documentation must be submitted to the Independent Reviewer, the State and any relevant Facility Owner and those parties must be allowed 10 Business Days (or such longer period as contemplated by a Direct Interface Agreement or Requirement) to provide comments.
2.2.3
Any comments received from the Independent Reviewer, the State or any relevant Facility Owner must be considered by Project Co when developing the Certified Design Documentation.
Certified Design 2.3.1
Certified Design Documentation must include: (a)
PART F5
a design report which: (i)
identifies the Construction Packages to which the Certified Design Documentation relates, including any Construction Packages that have been issued for Preparatory Works;
(ii)
identifies the aspects of the Design Management Plan to which the Certified Design Documentation relates;
(iii)
identifies all Reference Documents used in the preparation of the Certified Design Documentation;
(iv)
documents any changes to the design since the preliminary design report was issued;
(v)
confirms that any changes to the Concept Design have been dealt with in accordance with section 1.2;
(vi)
provides results of any additional modelling, investigations or testing;
(vii)
provides evidence of any required Approvals that have been obtained;
(viii)
provides evidence of compliance with the requirements of clause 10.12 of the Agreement in relation to Rail Interface Works;
(ix)
provides evidence that comments on the Preliminary Design Documentation were sought from Facility Owners and the O&M Subcontractor;
(x)
provides written confirmation from the urban and landscape designer that the Certified Design Documentation meets the intent of the urban and landscape design;
(xi)
provides dispositions to all comments provided on the Preliminary Design Documentation;
(xii)
identifies any relevant Certified Design Documentation for Preparatory Works; and
(xiii)
contains any other information required by the State Project Documents;
Project Scope & Requirements – Volume 1 of 3
Page 121 of 294
(b)
if relevant, a road safety audit report and an O&M safety audit report including all dispositions to the audit recommendations and, if relevant, an explanation as to the manner in which those dispositions have been addressed;
(c)
all necessary drawings, reports and specifications bound separately for each Construction Package covered by the Certified Design Documentation;
(d)
all necessary drawings, reports and specifications for each Construction Package to which the Certified Design Documentation relates, including: (i)
defining the land boundaries of each Returned Facility to which the Certified Design Documentation relates;
(ii)
a schedule of Assets, Asset Components and Asset Sub Components to which the report and layout drawings showing the location of each Asset;
(iii)
Assets; and
(iv)
a list of the applicable Reference Documents and any Agreed Exceptions or additions to the requirements in the Reference Documents.
2.3.2
The Certified Design Documentation must be submitted to the State, the Independent Reviewer and, in respect of the CityLink Returned Works, CML.
2.3.3
The following documents must be submitted to the State and the Independent Reviewer with the Certified Design Documentation for each Construction Package:
2.3.4
2.3.5
(a)
a certificate from Project Co confirming that the Certified Design Documentation complies with the requirements of the State Project Documents;
(b)
a certificate from the D&C Subcontractor confirming that the Certified Design Documentation complies with the requirements of the State Project Documents;
(c)
a relevant certificate from the Proof Engineer where required by section 2.6; and
(d)
any other certificates or reports required under the State Project Documents (including the Schedule of Certificates and Notices).
If required by the State or the Independent Reviewer, the appropriate design personnel (including the Proof Engineer), must be made available to: (a)
explain any Certified Design Documentation; and
(b)
provide such information regarding any Certified Design Documentation as the Independent Reviewer or the State reasonably requests.
The Independent Reviewer will: (a)
PART F5
review the proposed Certified Design Documentation submitted or resubmitted by Project Co (by general overview and reasonable checking)
Project Scope & Requirements – Volume 1 of 3
Page 122 of 294
to form an opinion as to whether or not it complies with the State Project Documents; and (b)
give notice to the State and Project Co (and CML if the Certified Design Documentation relates to the CityLink Returned Works), within 7 Business Days of the later of: (i)
receipt of the proposed Certified Design Documentation; and
(ii)
compliance by Project Co with any requirement of the Independent Reviewer under section 2.3.4
as to whether or not, in the Independent Reviewer's opinion, the proposed Certified Design Documentation complies with the State Project Documents and the Independent Reviewer's reasons for the opinion. 2.3.6
If the Independent Reviewer notifies Project Co that it considers the Certified Design Documentation does not comply with the State Project Documents, Project Co, must within 5 Business Days of such notification: (a)
proceed to amend the Certified Design Documentation expeditiously and diligently to address the matters raised by the Independent Reviewer and resubmit the Certified Design Documentation in accordance with section 2.3.2 and sections 2.3.3 to 2.3.4 will re-apply;
(b)
seek the State's agreement to a proposed amendment to the Concept Design as contemplated by section 1.2 to enable the Certified Design Documentation to comply with the State Project Documents; or
(c)
notify the State and the Independent Reviewer of any matters in connection with which it disagrees with the Independent Reviewer's opinion together with its reasons for doing so (Design Explanation);
2.3.7
If Project Co provides a Design Explanation in accordance with paragraph 2.3.6(c), the Independent Reviewer will give notice to the State and Project Co, within 7 Business Days of receipt of any Design Explanation, of its opinion as to whether or not the Design Explanation satisfactorily addresses the Independent Reviewer's concerns together with its reasons for forming that opinion.
2.3.8
Despite any opinion of the Independent Reviewer that: (a)
the proposed Certified Design Documentation does not comply with the State Project Documents; or
(b)
the Design Explanation does not satisfactorily address the Independent Reviewer's concerns,
and subject to the State’s right of suspension under clause 13.7 of the Agreement, construction of the relevant Construction Package may commence on the basis of that Certified Design Documentation, subject to the State and the Independent Reviewer being given 2 Business Days’ notice of Project Co’s intention to proceed with construction of the relevant Construction Package at its own cost and risk, including the risk that a Certificate of Stage One Completion may not be issued (Notice of Intention to Proceed).
PART F5
Project Scope & Requirements – Volume 1 of 3
Page 123 of 294
2.3.9
A Notice of Intention to Proceed must include details of the reasons why Project Co intends to proceed with construction of the relevant Construction Package despite the opinion of the Independent Reviewer.
2.3.10
Within 5 Business Days of the receipt of the Notice of Intention to Proceed, the State may refer the matter to dispute resolution in accordance with clauses 41 and 42 of the Agreement.
2.3.11
To the extent that the dispute is resolved in favour of:
2.3.12
2.4
(a)
the State, Project Co must amend the Certified Design Documentation expeditiously and diligently to address the matters raised by the Independent Reviewer, resubmit the Certified Design Documentation in accordance with section 2.3.3, and carry out the Works in accordance with the Agreement, including correcting any Defect in the Works as a result of the failure of the Certified Design Documentation to comply with the State Project Documents; and
(b)
Project Co, where the State has exercised its rights of suspension in accordance with clause 13.7 of the Agreement, the suspension will be treated as an act or omission of the State for the purposes of the definition of Compensable Extension Event.
The provision by Project Co or receipt by the State of the Notice of Intention to Proceed or the referral by the State to dispute resolution under section 2.3.10 does not in any way limit or otherwise affect: (a)
the obligations of Project Co under the Agreement; or
(b)
the State's rights under the Agreement, including clauses 36, 39 and 40 of the Agreement.
IFC Design Documentation 2.4.1
2.4.2
PART F5
IFC Design Documentation for any Construction Package must not be issued, and construction of any Construction Package must not commence, unless: (a)
the Certified Design Documentation relating to that Construction Package and all required certifications have been provided to the State and the Independent Reviewer;
(b)
the Independent Reviewer has been given the required number of days to review and comment on the Certified Design Documentation; and
(c)
either: (i)
the Independent Reviewer has issued a notice under section 2.3.5 stating that, in the Independent Reviewer's opinion, the Certified Design Documentation complies with the State Project Documents; or
(ii)
if the Independent Reviewer has issued a notice under section 2.3.5 stating that, in the Independent Reviewer's opinion, the Certified Design Documentation does not comply with the State Project Documents, Project Co has issued a Notice of Intention to Proceed in accordance with section 2.3.8.
The IFC Design Documentation for each Construction Package must be prepared and submitted to the State and the Independent Reviewer together
Project Scope & Requirements – Volume 1 of 3
Page 124 of 294
with all necessary drawings, reports and specifications for that Construction Package and each drawing issued as part of IFC Design Documentation must be clearly marked as “Issued for Construction”. 2.4.3
If any changes to the IFC Design Documentation are proposed then, unless in the opinion of the Independent Reviewer the changes are minor or have no adverse effect on any Relevant D&C Requirement or the ability of Project Co to perform the Project Activities in accordance with the State Project Documents: (a)
the following must be submitted to the State and the Independent Reviewer: (i)
a design change notice which clearly describes the design change and the reasons for the design change (DCN);
(ii)
information which: (A)identifies the Construction Package, and the drawings within the IFC Design Documentation, to which the design change applies; and (B)confirms that the design change complies with all the requirements of the State Project Documents; and
(iii)
(b) 2.5
2.6
copies of all drawings affected by the design change with the design change marked up to scale and annotated to specify any requirements relating to the design change; and
the requirements of section 2.3.1 to 2.3.4 will apply again.
Design Verification 2.5.1
Design Documentation for each Construction Package must be subject to a process of design verification that covers all aspects of the design before submission of Certified Design Documentation and must be carried out by the Lead Verifier.
2.5.2
The Lead Verifier must verify that the Design Documentation complies with all requirements of the State Project Documents and that detail in drawings, reports and specifications accurately and adequately conveys the design.
2.5.3
Complete records of the scope and outcomes of design verification must be retained and signed by the designated Lead Verifier.
Proof Engineering 2.6.1
Project Co must ensure that, in the performance of the D&C Activities, the Proof Engineer: (a)
PART F5
undertakes an independent detailed check and certifies (in the form set out in the Schedule of Certificates and Notices) the adequacy of the Design Documentation for all: (i)
tunnel structures including all tunnel support and primary and secondary linings and all relevant fire and life safety considerations;
(ii)
bridges and underpasses;
Project Scope & Requirements – Volume 1 of 3
Page 125 of 294
(b)
2.7
earth retaining structures;
(iv)
sign gantries and other load bearing structures, including all foundations;
(v)
load bearing falsework;
(vi)
Temporary Works; and
(vii)
formwork required for concrete pours higher than 2 metres; and
prior to any load being applied to load bearing falsework: (i)
inspects all such load bearing falsework and formwork required for concrete pours higher than 2 metres prior to the application of loading; and
(ii)
certifies (in the form set out in the Schedule of Certificates and Notices) that the falsework or formwork (as applicable) has been erected in accordance with the IFC Design Documentation.
Preparatory Works 2.7.1
Certified Design Documentation for Preparatory Works must include: (a)
2.7.2
2.8
(iii)
a Preparatory Works design report which: (i)
clearly defines the scope of the proposed Preparatory Works;
(ii)
confirms that Preliminary Design Documentation has been submitted for any Works to which the Preparatory Works relate; and
(iii)
provides evidence that any required Approvals have been obtained;
(b)
marked up preliminary design drawings clearly defining the scope of the Preparatory Works;
(c)
relevant reports and specifications for the Preparatory Works; and
(d)
any certificates required by the Schedule of Certificates and Notices.
Unless otherwise approved in writing by the State, Preparatory Works must be limited to: (a)
survey and site investigations;
(b)
site clearing and grubbing;
(c)
site establishment;
(d)
fencing;
(e)
preliminary earthworks and drainage; and
(f)
relocation of, or modifications to, Utility Infrastructure.
Design Review Meetings 2.8.1
PART F5
Design review meetings must be held at least fortnightly, or as otherwise agreed by the State, throughout the D&C Phase to review:
Project Scope & Requirements – Volume 1 of 3
Page 126 of 294
2.8.2
PART F5
(a)
progress in submitting Design Documentation against the D&C Program;
(b)
an updated four week forecast for Design Documentation submission to assist in scheduling design reviews;
(c)
a register of issues affecting design progress and actions to resolve such issues; and
(d)
any other issues arising out of the design of the Works.
Design review meetings must involve representatives from the State, Project Co, the Independent Reviewer, the D&C Subcontractor and its designers, including urban and landscape designers where required, the O&M Subcontractor and, where relevant, the Proof Engineer.
Project Scope & Requirements – Volume 1 of 3
Page 127 of 294
Part F6 1.
Construction
Working hours
The construction of the Works must be carried out to minimise impact on the local community and in accordance with the Environmental Requirements. 2.
Construction Documentation 2.1.1
Construction Documentation for each Construction Package must include: (a)
site management and supervisory responsibilities;
(b)
the planned sequence of work, for the Construction Package.
(c)
the relevant IFC Design Documentation:
(d)
Inspection and Test Plans (ITPs) and Construction Procedures;
(e)
relevant WTMPs;
(f)
the Worksite Environmental Management Plan, including a specific risk assessment for the Construction Package;
(g)
a schedule of Assets, Asset Components and Asset Sub Components contained within that package;
(h)
safety plans, including safety procedures required for any construction operations such as lifting or trenching; and
(i)
forecast construction impacts including noise, vibration and other community impacts and proposed mitigation measures.
2.1.2
A standard set of the ITPs and Construction Procedures required by the Reference Documents must be established and used for relevant construction activities.
2.1.3
The ITPs and Construction Procedures must include all Hold Points required by the relevant Reference Document.
2.1.4
The ITPs must describe the process pursuant to which the Nominated Authority releases each Hold Point;
2.1.5
Each Construction Procedure must describe:
PART F6
(a)
the scope of activities covered;
(b)
the materials, plant and equipment to be used;
(c)
the personnel required and their roles, responsibilities and required competencies;
(d)
all induction requirements;
(e)
the ITPs to be used and quality assurance documentation to be completed; and
(f)
the detailed construction procedures to be followed.
Project Scope & Requirements – Volume 1 of 3
Page 128 of 294
2.1.6
Project Co must submit to the State and the Independent Reviewer, for each Construction Package, Construction Documentation which complies with section 2.1.1 to 2.1.5.
2.1.7
If required by the Independent Reviewer, Project Co must make available appropriate personnel to:
2.1.8
3.
(i)
explain the Construction Documentation; and
(ii)
provide such information regarding the Construction Documentation as the Independent Reviewer reasonably requests.
Project Co must ensure that construction of any Construction Package does not commence until at least 5 Business Days have elapsed after: (i)
the Construction Documentation has been submitted to the Independent Reviewer in accordance with paragraph 2.1.6; and
(ii)
Project Co has complied with any requirements by the Independent Reviewer under paragraph 2.1.7.
Construction Review Meetings 3.1.1
3.1.2
Construction review meetings must be held at least monthly, or as otherwise agreed by the State, throughout the D&C Phase to review: (a)
progress in submitting ITPs and Construction Procedures;
(b)
progress in submitting Construction Documentation for each Construction Package;
(c)
progress in closure of As-Built Records;
(d)
progress in dealing with non-conformances and in rectification of Defects;
(e)
progress in completion and Handback of Returned Works; and
(f)
a register of issues affecting construction progress and actions to resolve such issues.
Construction review meetings must involve representatives from the State, Project Co, the D&C Subcontractor and the Independent Reviewer.
4.
Notification of Incidents
4.1
Immediate Notification 4.1.1
PART F6
The State must be immediately notified of any incidents associated with or affecting the D&C Activities including: (a)
any fatality or injury to construction personnel;
(b)
any fatality or injury to a member of the public that could be attributed to the D&C Activities;
(c)
any traffic accident on roads affected by the D&C Activities;
(d)
any incident requiring closure of a road;
(e)
any material property damage;
Project Scope & Requirements – Volume 1 of 3
Page 129 of 294
4.2
(f)
any environmental incident involving issue of a Clean-Up Notice, Infringement Notice or other notice under the Environment Protection Act 1970 (Vic); and
(g)
any notice issued by WorkSafe.
Incident Details
All relevant details of any incident must be recorded (supported by photographs of the incident site including the location of all safety devices) as soon as possible after the incident. A report with this information must be forwarded to the State and the Independent Reviewer within 2 Business Days of the incident. 5.
Maintenance during Construction
5.1
Construction Area
The Construction Areas must be kept in a safe and tidy condition. 5.2
Roads 5.2.1
5.3
Subject to any maintenance plan agreed or directed under section 5 of Part E, all Roads within the Construction Areas must be: (a)
maintained and repaired until Handback to the relevant Facility Owner; and
(b)
maintained in accordance with the relevant Facility Owner’s road management plans (if any) and usual requirements.
Maintenance Records 5.3.1
Maintenance records must be maintained on site and must be available for review by the Independent Reviewer, any relevant Facility Owner and the State.
5.3.2
All maintenance and inspection records for the inspection and maintenance activities undertaken during the D&C Phase must be provided to the relevant Facility Owner upon Handback of the Returned Works.
6.
Construction staging
7.
Traffic Management during Construction
7.1
General
7.2
7.1.1
WTMPs must be prepared for the management of the performance of discrete stages or components of the Works and Temporary Works that have an impact on (or on users of) Roads, shared use paths, footpaths and public transport infrastructure.
7.1.2
A management representative (Traffic Representative) must be appointed and have authority and responsibility for issues relating to traffic management throughout the performance of the D&C Activities, and this role must not be delegated to a third party without the State’s prior consent.
WTMPs 7.2.1
Each WTMP must address: (a)
PART F6
vehicle, bicycle and pedestrian movements;
Project Scope & Requirements – Volume 1 of 3
Page 130 of 294
(b)
public transport movements;
(c)
lane, road and public transport route closures;
(d)
major traffic control devices;
(e)
traffic signal operation;
(f)
vertical and horizontal alignment;
(g)
drainage;
(h)
barrier placement;
(i)
operating conditions including speed limits;
(j)
safety of the public and workers;
(k)
peak flows and road traffic capacity, including catering for special events;
(l)
signing and linemarking;
(m)
lighting;
(n)
property access;
(o)
stakeholder communication and media advertising;
(p)
timing;
(q)
replacement public transport services;
(r)
Utility Infrastructure access;
(s)
any interface between the responsibilities and requirements of Project Co, its Subcontractors and any other Authority;
(t)
incident management; and
(u)
the freeway operational requirements of CML for CityLink and VicRoads for the Eastern Freeway.
7.2.2
WTMPs must include detailed drawings identifying the nature and location of all temporary measures contemplated including linemarking, traffic barriers and signs.
7.2.3
Where the proposed Works impact on CityLink (or users of CityLink), the WTMP must also comply with the requirements of the CityLink Access Deed.
7.2.4
Each WTMP must be distributed, agreed and approved in accordance with the following process:
PART F6
(a)
a draft WTMP must be distributed to the State, VicRoads, the road safety auditor, any other relevant road authority for any affected Roads (including, in respect of CityLink, CML) and, where the Works affect public transport infrastructure, Public Transport Interface Parties;
(b)
recipients of the draft WTMP must be allowed 10 Business Days to provide comments; and
(c)
a final WTMP, including:
Project Scope & Requirements – Volume 1 of 3
Page 131 of 294
(i)
any adjustments required to meet the requirements of the State, the road safety auditor, VicRoads and relevant public transport operators and the reasonable requirements (as determined by the State) of any other relevant road authority (including, in respect of CityLink, CML) and where the Works affect public transport infrastructure, any relevant Public Transport Interface Parties;
(ii)
the written agreement of the Traffic Representative to the measures proposed; and
(iii)
the written agreement of VicRoads and, where applicable, relevant Public Transport Interface Parties,
must be submitted to the State for approval and be provided to the Independent Reviewer for information purposes. 7.2.5
7.3
Within 10 Business Days of receipt of a final WTMP which satisfies sections 7.2.1 to 7.2.4 the State must either: (a)
approve the WTMP; or
(b)
acting reasonably, provide reasons why the State has not approved the WTMP, in which case a final WTMP must be updated and resubmitted in a manner which satisfies the matters raised by the State, in which case this section 7.2.5 will re-apply.
7.2.6
Advertising of the proposed Works included in a WTMP must not proceed until the WTMP has been approved by the State.
7.2.7
The Works included in a WTMP must not be undertaken until the WTMP has been approved by the State and all advertising requirements have been met.
Implementation of WTMPs 7.3.1
PART F6
Unless otherwise agreed by the State: (a)
a road safety audit of that part of the Works covered by a WTMP must be undertaken during the first day and night after the initial implementation of the WTMP;
(b)
within 48 hours of the initial implementation of the WTMP, a written report must be submitted to the State and the Independent Reviewer (and, where applicable, any relevant road authority (including, in respect of CityLink, CML)) which includes the results of the road safety audit and describes the actions that have been taken in response to the issues identified during the road safety audit;
(c)
the requirements of the "Road Management Act Worksite Safety Traffic Management Code of Practice" must be complied with, including the audit and surveillance obligations;
(d)
all deficiencies affecting the safety of the public or workers identified in a road safety audit must be rectified immediately; and
(e)
all other deficiencies identified in a road safety audit must be rectified within 48 hours.
Project Scope & Requirements – Volume 1 of 3
Page 132 of 294
7.4
7.5
Traffic Management Liaison Group 7.4.1
A Traffic Management Liaison Group (TMLG) must be formed prior to the implementation of any part of the Works that may impact upon (or upon the users of) roads, footpaths, shared use paths or public transport infrastructure.
7.4.2
The TMLG must comprise representatives from the State, VicRoads, Project Co including the Traffic Representative, the D&C Subcontractor, and other groups nominated by the State.
7.4.3
The TMLG is to be a forum for the exchange of information and the discussion of issues associated with WTMPs.
7.4.4
The TMLG will have no legal responsibilities and will not have any power to require any of the parties or their Associates to act or refrain from acting in any way, and Project Co's responsibility for traffic management will not be limited or affected by the existence of, or determinations or decision of, the TMLG.
7.4.5
The TMLG must meet fortnightly from its inception until Stage One Completion, unless otherwise agreed by the State.
7.4.6
The TMLG must be provided with: (a)
the Traffic Management Strategy, the Construction Traffic Management Plan and all WTMPs;
(b)
details as to timing of implementation of WTMPs;
(c)
a schedule of WTMPs submitted and those proposed to be submitted within the next two months; and
(d)
all relevant reports as required by the TMLG.
Traffic controllers
All persons required to perform the duties of a traffic controller must undertake the relevant training and must be examined and certified as competent to perform their respective traffic controller duties. 7.6
7.7
Access for Works 7.6.1
Entry and exit to and from the Construction Areas will be via roads operated by VicRoads or other parts of the road network, subject to obtaining any necessary prior approval of the relevant road authority.
7.6.2
Haulage of bulk material to and from the Construction Areas to within a 2 km range of the Project Area must be via roads operated by VicRoads or CML or, subject to obtaining prior agreement by the Responsible Road Authority other parts of the road network.
VicRoads Traffic Bulletin 7.7.1
7.8
A weekly report, to be included on the VicRoads web site, must be provided to VicRoads detailing to the extent required by VicRoads: (a)
all current Works affecting traffic; and
(b)
all Works proposed to be carried out within the next 3 weeks.
Incidents and Accidents
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 133 of 294
All incidents and accidents within the Construction Areas must be managed by Project Co. 8.
Environmental Management during construction
8.1
General 8.1.1
The D&C Activities must be carried out in accordance with: (a)
the Environmental Management and Sustainability Strategy;
(b)
the Construction Environmental Management Plan; and
(c)
the Environmental Requirements.
8.1.2
Separate Worksite Environmental Management Plans (WEMPs) must be prepared for the management of discrete stages or components of the Works that may have an impact on the Environment.
8.1.3
WEMP’s must: (a)
identify specific measures included in the relevant Construction Procedure to prevent adverse environmental impacts; and
(b)
include relevant drawings showing: (i)
location and scope of works to be managed;
(ii)
location and nature of physical controls required by the plan;
(iii)
nature and frequency of monitoring to be undertaken for each of the identified potential impacts; and
(iv)
procedures for notification of any incident or potential hazard;
8.1.4
A suitably qualified management representative (Environmental Representative) must be appointed by Project Co and this role must not be delegated to another party without the State's consent. The Environmental Representative will have authority and responsibility for issues relating to environmental management throughout the performance of the D&C Activities and must review the outcomes of all environmental audits and ensure that the issues identified in the environmental audits are addressed.
8.1.5
A suitably qualified environmental auditor who is independent of Project Co, the D&C Subcontractor and the O&M Subcontractor (Environmental Auditor) must be engaged to: (a)
review and comment on the proposed CEMP and OEMP in accordance with EM1 and EM2 and section 1 of Part H21;
(b)
review and where appropriate, endorse amendments to the CEMP in accordance with clauses 5.5 and 5.6 of the Incorporated Document;
(c)
review and comment on each proposed WEMP before distributed and reviewed under section 9.2;
(d)
carry out the following audits: (i)
PART F6
6 monthly audits of compliance with the Environmental Management and Sustainability Strategy;
Project Scope & Requirements – Volume 1 of 3
Page 134 of 294
8.1.6 8.2
(ii)
quarterly audits of compliance with the CEMP (during the D&C Phase) and the OEMP (during the O&M Phase);
(iii)
monthly environmental audits of implemented WEMPs including auditing the effectiveness of WEMPs.
Results of all environmental audits must be promptly provided to the State and the Independent Reviewer.
Worksite Environmental Management Plans (WEMPs) 8.2.1
Each WEMP must be distributed, agreed and approved in accordance with the following process: (a)
a draft WEMP must be distributed to the State and the Independent Reviewer;
(b)
recipients of the WEMP must be allowed 5 Business Days to provide comments; and
(c)
the final WEMP must: (i)
respond to any items raised by the State and the Independent Reviewer;
(ii)
be approved by the Environmental Representative; and
(iii)
must be submitted to the State and the Independent Reviewer for information purposes prior to the Works covered by the WEMP being commenced.
9.
Testing and Commissioning
9.1
General requirement
9.2
9.1.1
Testing and commissioning must be carried out and comply, as a minimum, with the requirements of this section 9 and the Construction Management Plan.
9.1.2
All testing and commissioning must be documented with the performance results clearly recorded against the design requirements.
Progressive testing
The testing and commissioning must be undertaken progressively and must be completed before Stage One Completion except for any commissioning tests which must be undertaken under traffic and which must be completed before Close-Out. 9.3
Testing and commissioning records 9.3.1
Testing and commissioning records must be made available to the State and the Independent Reviewer in accordance with section 14 and must include: (a)
Work Lot registers which must: (i)
PART F6
provide access to all checklists, test reports, test certificates, asbuilt survey certificates or other quality assurance documentation required by the Construction Quality Management Plan and Inspection and Test Plans; and
Project Scope & Requirements – Volume 1 of 3
Page 135 of 294
(ii)
identify for each Work Lot: (A)location and Asset (including Asset Components and Asset Sub Components); (B)quantities and sources of materials; (C)details to enable tracing of test samples; and (D)sampling frequency compared to specified testing frequency;
(b)
registers of sampling and testing which enable identification of all test requisitions for each Work Lot and the date and reference number of corresponding test reports;
(c)
road safety audit reports;
(d)
O&M safety audit reports;
(e)
commissioning reports verifying compliance with:
(f)
9.4
9.5
(i)
pavement performance parameters;
(ii)
ride quality;
(iii)
traffic noise amelioration;
(iv)
traffic management systems; and
(v)
any mechanical and electrical systems; and
as-built survey certificates, which must be certified by a qualified surveyor and which must compare the as-built survey with the design geometry and identify any non-conformances.
Measurement of noise 9.4.1
As a condition precedent to Close Out, commissioning tests to measure traffic noise must be carried out under conditions that are representative of normal traffic flow. The results of the commissioning tests must be used to validate the models used for traffic noise predictions and verify compliance with the Agreement requirements under the design traffic volumes identified in Part H3.
9.4.2
During the D&C Phase construction noise at sensitive receptors must be regularly measured to verify compliance with the Agreement.
Testing of off-site equipment
Off-site manufactured equipment must be tested at the point of manufacture prior to delivery (wherever this is practical) and further on site tests carried out during commissioning. 9.6
Non-conformance and Defects
The State and the Independent Reviewer must be promptly notified of any nonconformance or Defect identified by testing and commissioning. 10.
Construction records
10.1
General
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 136 of 294
Accurate and complete construction records must be maintained at all times during D&C Phase for every Asset, Asset Component and Asset Sub-Component identified in the Asset Inventory in a form that is readily accessible to the State and the Independent Reviewer. 10.2
Construction records system 10.2.1
10.3
(a)
ensure that all construction records are compiled in Work Lots and that each Work Lot is clearly referenced to the relevant Asset, Asset Component or Asset Sub-component; and
(b)
ensure that each certificate issued by the Quality Representative clearly identifies the relevant Asset, Asset Components and Asset Sub Components to which it relates and their constituent Work Lots.
Contents of construction records 10.3.1
10.3.2
10.4
The system used to maintain construction records must:
Construction records for each Construction Package must include: (a)
all quality assurance records required by the ITPs;
(b)
site instructions and any DCNs;
(c)
non-conformance reports; and
(d)
current versions of the IFC Design Documentation with as-built changes (including repaired Defects) marked up to scale and referenced to the applicable DCN.
If a drawing is amended and issued as a new revision before completion of the Construction Package, any changes recorded as mark-ups prior to that amendment must be incorporated in the new revision and the traceability to the relevant DCN must be preserved.
Control of non conformance 10.4.1
Project Co must notify the State and the Independent Reviewer of any nonconformance with respect to the Works within 1 Business Day of the nonconformance being identified.
10.4.2
Project Co must record all non-conformances and the status of all nonconformances in a register.
10.4.3
A Work Lot non-conformance must be treated as a Hold Point which must not be released until a disposition acceptable to the State, acting reasonably, is submitted to the State and the Independent Reviewer.
10.4.4
Project Co must review and analyse the cause of all non-conformances and develop a plan of corrective action to minimise the likelihood of recurrence.
10.4.5
If the Independent Reviewer notifies Project Co of a non-conformance, Project Co must deal with the non-conformance in accordance with this section 10.4.
11.
As-Built Records
11.1
General
As-Built Records must include the final versions of the construction records.
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 137 of 294
11.2
Closure of As-Built Records 11.2.1
Procedures for expeditious closure
11.2.2
The As-Built Records for a Construction Package or part of a Construction Package must be completed and closed as soon as practicable, in accordance with the Construction Quality Management Plan, so as to ensure that after Stage One Completion, the As-Built Records represent the Works as completed.
11.2.3
Closure of As-Built Records cannot occur until:
11.2.4
11.2.5
11.3
(a)
all inspections and tests required for the Work Lots represented by AsBuilt Records have been completed and the results recorded;
(b)
any non-conformances and Defects that cannot be corrected promptly have been notified and recorded on the Defects List in accordance with section 13, and the non-conformance report marked accordingly;
(c)
the final marked-up copy of every drawing relevant to the Construction Package or the part of the Construction Package, including drawings without change, have been checked for completeness and signed by a person with responsibility for supervision of the work;
(d)
the complete set of As-Built Records for the Construction Package or the part of the Construction Package has been made available to the State and the Independent Reviewer; and
(e)
the Quality Representative has certified (in the form required by the Schedule of Certificates and Notices) compliance with the requirements of this section 11.2.
As-Built Records must be closed before: (a)
the Works represented by the As-Built Records are covered up or subsequent Works are undertaken which would, in the opinion of the Independent Reviewer, prevent inspection or repairs;
(b)
manufactured components, including precast and fabricated components, are erected or incorporated into the Works; and
(c)
in the case of Returned Works, the notice required by clause 19.3(c)(ii) of the Agreement has been issued for the Returned Works represented by the As-Built Records.
The requirements in section 11.2.4 will not apply where it is either not practicable to undertake testing required for closure of As-Built Records before Works are covered up (e.g. flushing of subsoil drains) or in particular situations where test results are available. Where these circumstances apply, any additional inspection or testing arrangements required by the Independent Reviewer must be included in the applicable Inspection and Test Plan, and the As-Built Records must be closed as soon as practicable after the test results are available.
Revisions of As-Built Records
The electronic CAD files for the As-Built Records must be revised after the relevant Work Lots have been closed to incorporate all changes to enable production of the final electronic CAD files for the As-Built Records.
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 138 of 294
12.
Asset Inventory 12.1.1
12.1.2
12.1.3
13.
The Asset Inventory compiled in accordance with this section must be used as the basis for: (a)
the Work Breakdown Structure throughout the D&C Phase; and
(b)
the Asset Management System during the O&M Phase.
The Asset Inventory must be structured in layers comprising Assets, classified by type, Asset Components and Asset Sub Components where: (a)
Asset Components and Asset Sub Components are the constituent parts of an Asset which need to be separately identified in the design; and
(b)
Asset Component types are identifiable elements of an Asset type which have differing characteristics and inventory data requirements.
Linear Assets including road carriageways, roadsides and paths must be included in the Asset Inventory as discrete sections between readily identified points such as intersections, interchanges, cross roads or creek crossings.
Defects List 13.1.1
A system for monitoring the rectification of any Defects, including the maintenance of a Defects list, must be established.
13.1.2
Where Defects are notified by the State or the Independent Reviewer, the Defects list must record the party that notified the Defect and a reference to the notification.
13.1.3
The Defects list must identify any Defects proposed to be accepted by the State in accordance with clause 21.1 of the Agreement and must include references to any correspondence between the State and Project Co in respect of such Defects.
13.1.4
Records of Defects must not be deleted from the Defects list.
13.1.5
The Defects list must be maintained during the Term.
13.1.6
Every Defect must be identified against the relevant Asset Component or SubComponent and the location and nature of each Defect must be described in sufficient detail to enable subsequent inspection, repair and monitoring.
14.
Records and Reporting
14.1
Format of manuals, plans, drawings and reports 14.1.1
14.2
Any manuals, plans, drawings, programs, reports or associated information, or any updates or revisions of such manuals, plans, drawings, programs, reports or information required to be submitted must be submitted as a hard copy and as an electronic copy in the form agreed between Project Co and the State (or failing such agreement, in such form as the State or the Independent Reviewer, as the case may be, requires).
Format of CAD drawings 14.2.1
PART F6
CAD drawings must:
Project Scope & Requirements – Volume 1 of 3
Page 139 of 294
(a)
have a layer naming convention and all associated attributes in accordance with VicRoads Final Drawing Presentation Guidelines;
(b)
use the real world reference defined in the User Coordinate System (UCS) as follows: (i)
UCS: World;
(ii)
Units: metres;
(iii)
insertion base point: 0,0,0; and
(iv)
be accompanied by relevant Metadata,
and must be submitted to the State in Microstation V8i (or later). 14.2.2
14.3
(a)
reference models or Xrefs for each individual discipline including separate 2D concept and 3D design models as per Section 2 of VicRoads Final Drawing Presentation Guidelines;
(b)
all aspects of civil or structural works;
(c)
all aspects of drainage works and drainage modelling works;
(d)
all sight lines, vehicle turning movements and clearance envelopes as separate reference or Xref files; and
(e)
all design contour files at appropriate contour intervals for each work stage.
14.2.3
Digital CAD reference or Xref files must be saved in correct global orientation and in correlation with controlled survey.
14.2.4
Digital CAD reference or Xref files units to be in metres.
14.2.5
Final drawing productions must be presented in accordance with VicRoads Final Drawing Presentation Guidelines.
Format of GIS Data 14.3.1
14.3.2 14.4
The following design information must be provided in Digital CAD format:
GIS Data must be supplied: (a)
in a standard GIS (TAB) or CAD interchange format (.mid, .shp, .dwg or .dxf); and
(b)
as Horizontal Datum: GDA 94 (i)
Projection: UTM
(ii)
Grid: MGA
(iii)
Vertical datum: AHD
Layers are to be separated into feature classes in a structure that is clearly documented and supplied with the data.
Drawings
All drawings must be provided in PDF format.
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 140 of 294
14.5
Survey information
The format of all survey information must be in accordance with VicRoads Standards. 14.6
Access to design and construction records 14.6.1
14.6.2
14.7
During the D&C Phase, the State and the Independent Reviewer must be provided with electronic access to the following design and construction records indexed by Construction Package: (a)
Preliminary Design Documentation and Certified Design Documentation;
(b)
Construction Documentation;
(c)
site instructions and DCNs;
(d)
sampling and testing registers required by section 9.3.1(b);
(e)
monthly progress report required by section 14.7.1;
(f)
non-conformance reports;
(g)
the Defects list; and
(h)
closed As-Built Records.
Electronic access to design and construction records must: (a)
be available at all times during the Term;
(b)
be accessible by web browser;
(c)
present records in a format acceptable to the State and the Independent Reviewer;
(d)
have a response time less than 30 seconds;
(e)
enable convenient searching and selection of records; and
(f)
allow reports to be generated by the State and the Independent Reviewer on an as needs basis.
D&C Phase Progress Reports 14.7.1
During the D&C Phase, the State and the Independent Reviewer must be provided with monthly reports on the progress of the D&C Activities.
14.7.2
The monthly progress report must include (to the extent applicable) the following: (a)
a management overview which addresses overall progress and key D&C Phase issues;
(b)
photographs and video records of the progress of the D&C Activities;
(c)
a report on the D&C Activities which addresses: (i)
for each Construction Package, progress towards: (A)completion of Preliminary Design Documentation;
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 141 of 294
(B)completion of Certified Design Documentation; (C)Completion; and (D)closure of As-Built Records; (ii)
the D&C Program and progress relative to the D&C Program and the original Project milestones;
(iii)
key issues and actions arising from the D&C Activities including contractual and financial issues (including any Claims lodged under clause 56.3 of the Agreement), delays to progress, significant safety, environmental or quality issues, and Project Co’s response to these issues including; (A)progress claims paid under the D&C Subcontract; (B)commissioning and completion progress of the Works including procurement and performance; (C)stakeholder issues covering property and authorities/utilities; (D)traffic management issues;
14.7.3
14.8
(iv)
any issues associated with maintenance of Roads during construction, including public or Facility Owner complaints and safety issues;
(v)
occupational health and safety, environment, quality, project organisation structure and staffing, industrial relations, contractor and subcontractor issues;
(vi)
incidents notified to the State or the Independent Reviewer and outcomes of investigations or responsive actions; and
(vii)
identification and progress on rectification work and implemented Pre-Agreed Modifications;
(d)
planning and implementation of O&M Activities prior to Stage One Completion;
(e)
a corporate relations report (including government, media and community relations) which includes Project Co’s actions to address identified issues; and
(f)
other reasonable requirements of the State or the Independent Reviewer.
During the D&C Phase, CML must be provided with a monthly progress report in respect of the Works on, adjacent to or above CityLink which meets the requirements of sections 14.7.2(a), (b), (c)(i), (c)(ii), (c)(iv), (c)(vi) and (c)(vii) to the extent applicable to such Works. At the same time as it is provided to CML, a copy of the report must be provided to the State and the Independent Reviewer.
Submission of Records
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 142 of 294
14.8.1
Design and construction records must be provided to the State as a complete electronic record as a condition precedent to each of Stage One Completion and Close-Out.
14.8.2
A complete electronic copy of the As-Built Records for each Construction Package (including the final revised electronic versions of IFC Design Documentation) must be supplied to the State and Independent Reviewer prior, and as a condition precedent, to Close-Out.
14.8.3
For the purposes of section 14.8.2, a complete electronic copy of the As-Built Records for each Returned Works Construction Package (including the final revised electronic versions of the IFC Design Documentation) must be supplied to the State, the Independent Reviewer and the relevant Facility Owner no later than 60 days after the date of completion of the Returned Works and as a condition precedent to Handback of Returned Works. As-Built Records for Returned Works must also include the relevant inspection and maintenance records for the Returned Works during construction.
14.8.4
Complete electronic copy includes all the final CAD drawings for the Works in the format identified in section 14.2 and the final GIS data in the format identified in section 14.3.
PART F6
Project Scope & Requirements – Volume 1 of 3
Page 143 of 294
Part F7 1.
Operation and Maintenance
General 1.1.1
Project Co must: (a)
maintain and operate all facilities in the Leased Area, including the Freeway and the Freeway Control Centre:
(b)
maintain (and where appropriate, operate) the Maintained Off Freeway Facilities; and
(c)
operate the Operational Area,
in accordance with this Part F7, the O&M Phase Management Plan and the O&M Manuals.
2.
1.1.2
The O&M Phase Management Plan and the O&M Manuals must comply with the requirements in Part F1.
1.1.3
Vehicles undertaking Project Activities during the O&M Phase will be exempt from tolls on Stage One.
Operation 2.1.1
PART F7
In carrying out its obligations under paragraph 1.1.1, Project Co must: (a)
deal with all incidents in accordance with section 3 within the Leased Area and the Operational Area;
(b)
develop, maintain and comply with operating protocols with VicRoads and CML to ensure effective management and operation of the road network, including at Freeway interfaces;
(c)
communicate, coordinate and cooperate with VicRoads personnel at the VicRoads Traffic Management Centre and with CML personnel at the CityLink Control Centre in relation to the operation of the Freeway and the Operational Area;
(d)
communicate, co-ordinate and co-operate with VicRoads at all times;
(e)
communicate, co-ordinate and co-operate with other relevant road authorities for Roads;
(f)
ensure the Freeway and the Operational Area are safe for all Users under all conditions, including traffic congestion and during the management of any incident;
(g)
continually monitor, investigate and report on safety and traffic hazards and incidents on the Freeway and the Operational Area and undertake any required corrective actions;
(h)
liaise with relevant Authorities, including Emergency Services, on issues affecting the Freeway and the Operational Area;
(i)
provide security to prevent unlawful or unauthorised access to any part of the Relevant Infrastructure to which access is prohibited or is unsafe;
(j)
remove abandoned vehicles from the Freeway and the Operational Area;
Project Scope & Requirements – Volume 1 of 3
Page 144 of 294
3.
establish and maintain a system for receiving and addressing complaints and enquiries;
(l)
maintain records of all operations; and
(m)
ensure its operations systems and procedures are and remain compatible with the systems and procedures applied by VicRoads for the Melbourne transport network where they have a technical, operational or procedural interface.
Incident management 3.1.1
4.
(k)
Project Co must: (a)
provide a 24 hour incident response capability at all times to ensure safety of the public in the event of incidents;
(b)
include in the Code of Maintenance Standards all incident response requirements, including response time, rectification measures etc.
(c)
include in the Freeway Operations Manual a protocol developed with VicRoads, CML and relevant Emergency Services setting out contact details and arrangements to respond to any request for assistance from VicRoads, CML or Emergency Services, including under the provisions of the Emergency Management Act 1986 (Vic) and the State Emergency Response Plan (as defined in that Act);
(d)
respond promptly to any incident notification:
(e)
ensure disabled vehicles are removed to prevent obstruction to traffic or a road safety hazard;
(f)
ensure the restoration of damage to the Relevant Infrastructure arising from any incident and to assist Emergency Services personnel in the management of any Incident;
(g)
establish and maintain a system to monitor and report response times and rectification times for all incidents;
(h)
provide detailed reports to the State in respect of all Incidents; and
(i)
meet the performance requirements identified in Part H19.
Environmental Management during operations 4.1.1
The O&M Activities must be carried out in accordance with: (a)
the Environmental Management and Sustainability Strategy;
(b)
the Operations Environmental Management Plan; and
(c)
the Environmental Requirements.
4.1.2
The Environmental Representative will have authority and responsibility for issues relating to environmental management throughout the performance of the O&M Activities and must review the outcomes of all environmental audits and ensure that the issues identified in the environmental audits are addressed.
4.1.3
An independent, qualified environmental auditor (Environmental Auditor) must be engaged to carry out quarterly environmental audits of the Operations
PART F7
Project Scope & Requirements – Volume 1 of 3
Page 145 of 294
Environmental Management Plan, including auditing the effectiveness of the Operations Environmental Management Plan and the operation of the Environmental Management System. 4.1.4 4.2
Results of all environmental audits must be promptly provided to the State.
Notification to the State 4.2.1
4.2.2
The State must be immediately notified of either of the following associated with or affecting the O&M Activities: (a)
any Incidents; and
(b)
any notice issued by WorkSafe.
All relevant details of any Incident must be recorded (supported by photographs of the site including the location of all safety devices) as soon as possible after the Incident. A report with this information must be forwarded to the State and the Independent Reviewer within 2 Business Days of the Incident.
5.
Traffic management
5.1
Traffic Plans 5.1.1
5.2
(a)
Diversion Traffic Management Plans;
(b)
Incident Traffic Management Plans; and
(c)
Maintenance Traffic Management Plans.
Content of traffic plans 5.2.1
5.3
The following traffic plans must be developed, regularly updated and complied with:
Each traffic plan referred to in section 5.1 must address, as a minimum: (a)
traffic signal operations;
(b)
on site location of traffic control devices;
(c)
on site location of Victoria Police and incident management personnel;
(d)
on site location and content of DISPLAN boxes;
(e)
the content of TMCS signs and displays;
(f)
the content of signs and displays along CityLink and the Eastern Freeway; and
(g)
notification requirements before the traffic plan implemented.
Submission of Traffic Plans
Notwithstanding section 1.1.1 the traffic plans referred to in section 5.1 must be submitted to the State and the Independent Reviewer in accordance with the Review Procedures at least 6 months prior to Stage One Completion.
PART F7
Project Scope & Requirements – Volume 1 of 3
Page 146 of 294
5.4
5.5
5.6
5.7
Diversion Traffic Management Plans 5.4.1
DTMPs must be prepared for the management of traffic in the event of an incident on the Freeway and the Operational Area, or for other operational reasons.
5.4.2
Potential diversions requiring DTMPs, and the details within each DTMP, must be developed in consultation with, and agreed by, Emergency Services, VicRoads and, where relevant, CML, the operator of EastLink and local Councils.
Incident Traffic Management Plans 5.5.1
ITMPs must be prepared for the management of traffic around incidents that may occur within the Leased Area and Operational Area.
5.5.2
Each ITMP must include a series of standard drawings identifying the location of traffic devices.
5.5.3
Incident management personnel must be appropriately qualified and incident management vehicles must be appropriately equipped for each type of incident.
Maintenance Traffic Management Plans 5.6.1
Any O&M Activities that may involve working in close proximity to traffic must be undertaken in accordance with a MTMP.
5.6.2
Where maintenance activities impact on traffic outside the Leased Area, the agreement of the relevant road authority (including, in respect of CityLink, CML) must be obtained prior to the relevant maintenance activities commencing.
5.6.3
The O&M Traffic Representative must approve any MTMP prior to it being implemented.
O&M Traffic Representative
A management representative (O&M Traffic Representative) who has authority and responsibility for issues relating to traffic management for the O&M Activities must be appointed prior to Stage One Completion and the position of O&M Traffic Representative must be filled at all times during the O&M Phase. This role must not be delegated to a third party without the State's prior consent. 5.8
Traffic controllers
All persons who are required to perform the duties of a traffic controller must undertake the relevant training and be examined and certified as competent to perform their respective traffic controller duties. 5.9
Operations Traffic Management Liaison Group 5.9.1
An Operations Traffic Management Liaison Group (OTMLG) must be established at least 2 months prior to the anticipated Date of Stage One Completion.
5.9.2
The OTMLG must comprise representatives from the State, VicRoads, Project Co, the O&M Subcontractor and CML (as required) and other groups nominated by the State as required.
PART F7
Project Scope & Requirements – Volume 1 of 3
Page 147 of 294
5.10
5.9.3
The OTMLG is to be a forum for the exchange of information and the discussion of issues associated with operational traffic management, including liaison with VicRoads and (where applicable) CML, data sharing, operational interfaces, coordination of systems between the State's road network (and, where applicable, the CityLink network) and the Freeway, new traffic management developments and other issues.
5.9.4
The OTMLG will have no legal responsibilities and will not have any power to require any of the parties or their Associates to act or refrain from acting in any way, and Project Co’s responsibility for traffic management will not be limited or affected by the existence of, or determinations or decision of, the OTMLG.
5.9.5
The OTMLG must meet at least once every six months or at such other frequency as agreed by the State.
5.9.6
All relevant traffic management reports must be made available to the OTMLG.
VicRoads Traffic Bulletin 5.10.1
A weekly report, to be included on the VicRoads web site, must be provided to VicRoads detailing, to the extent required by VicRoads: (a)
all current O&M Activities; and
(b)
all O&M Activities proposed within the following three weeks,
that will involve the closure of any traffic lanes, including on Roads. 5.11
Traffic information 5.11.1
The State and VicRoads must be provided with monthly summaries of traffic data in a form acceptable to the State.
5.11.2
The State and VicRoads Traffic Management Centre must be immediately advised of any Incident or any unusual traffic congestion.
6.
Maintenance
6.1
General 6.1.1
PART F7
Project Co must: (a)
ensure that only trained personnel are engaged in respect of the O&M Activities;
(b)
plan and implement maintenance activities that will ensure compliance with the Code of Maintenance Standards;
(c)
coordinate all maintenance activities with the CityLink Control Centre and VicRoads Traffic Management Centre where there may be an operational impact on the road network;
(d)
keep the Relevant Infrastructure in a clean and tidy condition and remove all graffiti, litter and debris, including incident debris;
(e)
maintain the Asset Management System for the Relevant Infrastructure;
(f)
undertake regular inspections of the Assets, Asset Components and Asset Sub Components of the Relevant Infrastructure in accordance with the O&M Manuals;
Project Scope & Requirements – Volume 1 of 3
Page 148 of 294
6.2
(g)
include manufacturers' requirements in technical specifications and performance standards in the Code of Maintenance Standards; and
(h)
maintain records of all maintenance carried out.
General replacement and refurbishment
The replacement and refurbishment of Assets must be undertaken at such times as required to ensure that the Relevant Infrastructure at all times meets the requirements of the Agreement. 7.
O&M Manuals 7.1.1
The O&M Manuals must be developed in accordance with this section and be consistent with section 1.2 of Part F1.
7.1.2
The Code of Maintenance Standards to be included in the O&M Manuals must be developed in accordance with section 9.
7.1.3
The O&M Manuals must be submitted to the State and the Independent Reviewer in accordance with the Review Procedures.
8.
Asset Management System
8.1
General
An Asset Inventory must be maintained in the Asset Management System which lists all Assets to be managed under the Agreement, including all roadside Assets, roadside features, plantings and areas that may require specific maintenance or protective treatments to achieve the requirements in Part H19. 8.2
Inspection
The Asset Management System must be used to document the regular inspection of the Assets and Asset Components and Asset Sub Components and to record any failure, or imminent failure, to meet performance standards and/or condition requirements in the Code of Maintenance Standards. 8.3
Provision of Information to State
The Asset Management System must retain all data and information as an historical record. This Asset Management System must include the recording of all serial numbers of manufactured Assets in the Asset Inventory. This data and information is to be made available to the State on request. 9.
Code of Maintenance Standards
9.1
Maintenance Standards 9.1.1
PART F7
A Code of Maintenance Standards must be developed and achieved which: (a)
is consistent with the preliminary Code of Maintenance Standards;
(b)
ensures that all the requirements of the Agreement are met at all times for the duration of the O&M Phase;
(c)
clearly defines requirements for inspections, conditions requiring maintenance action, and maximum acceptable maintenance response times; and
Project Scope & Requirements – Volume 1 of 3
Page 149 of 294
(d) 9.1.2
clearly defines the system of asset condition rating to meet the requirements of section 10.2.
Maintenance standards must be defined in the Code of Maintenance Standards for each Asset, Asset Component and Asset Sub-Component, including roadside Assets, and must include: (a)
the specific performance characteristics that must be maintained (including safety for different user groups, durability, rideability, amenity and water quality);
(b)
potential defects or hazards which could affect each performance characteristic;
(c)
clearly defined severity ratings for each potential defect or hazard;
(d)
the severity rating at which the defect must be rectified or the hazard removed;
(e)
the period within which the defect must be rectified or hazard removed;
(f)
condition indicators and condition ratings for each specific performance characteristic that will be used to record an objective assessment of the condition of each Asset, Asset Component and Asset Sub-Component in the Asset Inventory;
(g)
an inspection schedule showing the required minimum frequency for: (i)
daytime and, as required, night time hazard and defect inspections;
(ii)
condition rating inspections for the Asset Inventory;
(iii)
the maintenance activities contemplated by the Payment Schedule. As a minimum, these activities include: (A)lighting; (B)tunnel ventilation; (C)tunnel safety systems; (D)pavement maintenance; (E)safety barrier realignment, repair or replacement; (F)hazard rectification; (G)cleanliness of tunnel linings; (H)litter control; and (I)grass and weed control.
9.1.3 9.2
The maintenance standards must be at least equivalent to VicRoads maintenance standards for comparable facilities.
Review of Maintenance Standards
PART F7
Project Scope & Requirements – Volume 1 of 3
Page 150 of 294
9.2.1
The Code of Maintenance Standards must be: (a)
without limiting paragraph (b), reviewed at the first anniversary of Stage One Completion and then at two yearly intervals for the duration of the O&M Phase; and
(b)
updated on an ongoing basis through the O&M Phase to ensure that the maintenance standards will enable Project Co to comply with its obligations under the Agreement.
10.
Condition monitoring of Assets
10.1
General
The condition indicators and ratings that will be used for recording the condition of Assets, Asset Components and Asset Sub Components and the minimum frequency of condition rating inspections, must be defined in the Code of Maintenance Standards. 10.2
Asset Condition 10.2.1
10.3
The Asset condition indicators, ratings and inspection frequencies must be: (a)
sufficient to allow objective determination of the condition and likely Residual Design Life of each Asset, Asset Component and Asset SubComponent; and
(b)
used to identify the time at which refurbishment or replacement of the Asset, Asset Components and Asset Sub Components should be undertaken.
Required Standards
The condition rating of Assets may be used to determine the extent to which the Relevant Infrastructure meets the Standards required by the Agreement at the Expiry Date. 11.
Scheduling and Performance of O&M Activities
11.1
State Consent 11.1.1
O&M Activities requiring Non-Permitted Closures may be scheduled or performed by Project Co if approved by the State in accordance with this section 11.
11.1.2
Where it is intended to implement a Non-Permitted Closure, Project Co must make a request to the State, together with the reasons for the proposed closure, at least 10 Business Days prior to the proposed date for the closure.
11.1.3
In considering a request from Project Co under section 11.1.2, the State may have regard to whether:
PART F7
(a)
the performance of the required O&M Activities during the requested closure will have less overall impact on the convenient and efficient flow of traffic;
(b)
the requested closure would be inconsistent with any duty or function of the State or Project Co as a road authority under the Road Management Act;
Project Scope & Requirements – Volume 1 of 3
Page 151 of 294
(c)
the duration of the requested closure exceeds the period reasonably required for the relevant O&M Activities to be performed;
(d)
it is practical to complete the O&M Activities the subject of the requested closure, within the requested period;
(e)
the requested closure is consistent with Project Co's obligations under the State Project Documents;
(f)
Project Co has provided all information reasonably required by the State for the purpose of being able to undertake a fully informed consideration of the request; and
(g)
there are any other relevant considerations in relation to the requested closure.
11.1.4
Any State consent given under this section 11 must be in writing for it to be effective.
11.1.5
Nothing in this section 11 (including any failure by the State to provide its consent): (a)
(b) 11.1.6
derogates from Project Co's obligations to: (i)
respond to and rectify any incidents or hazards in accordance with the Code of Maintenance Standards; or
(ii)
perform the O&M Activities as required by the State Project Documents; or
impacts the Abatement Regime.
Notwithstanding the provisions of this section 11, the State may, from time to time, and for any reason (including in order to cater for traffic movements related to special events or to restrict works at times that may affect the local community), by written notice to Project Co: (a)
direct Project Co not to undertake a lane closure which is otherwise scheduled in accordance with the Agreement; and
(b)
advise Project Co of an alternative time when Project Co may schedule the relevant lane closure.
12.
O&M Phase Reports
12.1
Monthly reports 12.1.1
During the O&M Phase, Project Co must provide the State with monthly reports on the progress of the O&M Activities.
12.1.2
The monthly progress report must include (to the extent applicable) the following: (a)
a management overview which addresses key issues relating to the O&M Activities;
(b)
a report on the O&M Activities which addresses or includes: (i)
PART F7
performance relative to the Performance Requirements identified in Part H19;
Project Scope & Requirements – Volume 1 of 3
Page 152 of 294
12.2
(ii)
roadway operations, including performance of the road data systems and traffic management;
(iii)
roadside services including incident reports, response times relative to targets and analysis of incidents;
(iv)
environmental and road safety performance, including results of analysis of breaches of environmental requirements or traffic related incidents;
(v)
road maintenance performance including progress, landscaping works, routine repairs and replacement activities for all infrastructure;
(vi)
Lane Availability, including the dates and times of actual lane closures within each section of the Freeway and the activities requiring the lane closures;
(vii)
progress against the Forecast Maintenance and Refurbishment Plan including an outline of any departures and reasons for these, including actions required to ensure delivery in accordance with the Forecast Maintenance and Refurbishment Plan;
(viii)
measurement and monitoring of KPIs and performance against required criteria;
(ix)
forecast and actual expenditure against budget;
(x)
other reasonable requirements of the State; and
(xi)
a corporate relations report (including government, media and community relations) which includes Project Co’s actions to address identified issues.
Incident Reports 12.2.1
Project Co must promptly provide the State with a detailed report of: (a)
any Defect in, or Incident occurring on, the Relevant Infrastructure of which it becomes aware;
(b)
the action which is proposed to be taken to: (i)
rectify the Defect; or
(ii)
respond to and rectify the Incident,
and the estimated time that this will require; and (c) 12.2.2
PART F7
where the Incident required an urgent response, the action already taken to respond to it.
If a report is provided or required to be provided to the State under paragraph (a), Project Co must thereafter provide to the State any additional information reasonably requested by the State in connection with the subject matter of such report. Project Co must take all steps in relation to the correction of the Defect or the response to and rectification of the Incident as the State may require for the purposes of ensuring that:
Project Scope & Requirements – Volume 1 of 3
Page 153 of 294
PART F7
(a)
Project Co’s obligations under the State Project Documents have been complied with; and
(b)
the Relevant Infrastructure is in the condition required by the State Project Documents.
Project Scope & Requirements – Volume 1 of 3
Page 154 of 294
Part G
PART G
COMMUNICATIONS AND COMMUNITY ENGAGEMENT
Project Scope & Requirements – Volume 1 of 3
Page 155 of 294
1.
Community information
1.1
General requirements
As part of the Construction Communications and Community Engagement Plan the following issues and activities must be addressed:
PART G
1.1.1
The establishment, resourcing and publicising of a 24-hour response phone number to be targeted to the local community to address specific aspects of project construction information on the Project. This arrangement should be available at all times during the performance of the D&C Activities.
1.1.2
The establishment of a register or database which records all enquiries from the public regarding the Project, including names, nature of inquiry, response provided and date of response provided. All enquiries must be promptly responded to. Weekly reports must be provided to the State outlining details of any public enquiries received and the response provided.
1.1.3
A digital communications system (DCS) must be established incorporating a project construction website, social media and SMS notifications. The DCS must: (a)
be developed in consultation with the State;
(b)
include video footage, aerial photography and time lapse production which will be used to promote the D&C Activities, inform communities of construction progress and obtain community feedback. Project Co must use a photographer approved by the State and the State will contribute 50 per cent of the agreed cost of photography and footage; (i)
be provided promptly to the State in an agreed format;
(ii)
include an accurate 3D interactive animation of the Project design that must be maintained to be used for community information and engagement purposes throughout the D&C Phase.; and
(iii)
include within the project construction website a sub domain of the www.linkingmelbourne.vic.gov.au website as provided by the State.
1.1.4
A minimum of four information bulletins per year must be prepared in conjunction with the State and distributed to households and businesses in the local community. The bulletins must provide information on construction progress, planned activities and impacts, as well as opportunities for community involvement. This information must also be accessible on the internet.
1.1.5
A minimum of two community events must be funded and conducted in respect of the Works. The first event must be held during construction to showcase progress of construction, including tunnel construction. The second must be an ‘open day’ shortly prior to Stage One opening. The event activities, management, dates, and location must be agreed with the State and must cater for public attendance numbers equivalent to similar previous events.
1.1.6
Households and businesses likely to be affected by the D&C Activities, including by noise, dust and changed conditions, must be notified before those
Project Scope & Requirements – Volume 1 of 3
Page 156 of 294
D&C Activities occur. Maximum possible notification must be given, including an explanation of the Works, timing and possible impact. Contact details must be provided to facilitate community questions and responses. Notification should occur no later than 10 Business Days prior to commencement of the relevant D&C Activities in any local area affected. Letters should be sent to the State for approval at least two Business Days prior to the intended date of delivery.
1.2
1.1.7
Branding guidelines for written and digital publications, including appropriate use of logos and branding as advised by the State, must be adhered to.
1.1.8
All community information and media materials prepared by Project Co must be approved by the State.
1.1.9
Project Co must immediately inform and provide details to the State of any enquiries from Members of Parliament, councillors and council officers.
1.1.10
An appropriate languages other than English (LOTE) strategy, which has been approved by the State, must be used to communicate with culturally and linguistically diverse (CALD) communities.
1.1.11
Project Co must organise and manage site visits for media and stakeholders as requested by the State.
1.1.12
Market research must be conducted on a six-monthly cycle to evaluate the effectiveness of communications, and make necessary adjustments based on research outcomes.
Community issues 1.2.1
1.3
Project Co must do all things reasonably necessary and in good faith to enable community issues to be resolved including: (a)
meeting with affected householders and/or businesses;
(b)
exchanging information;
(c)
considering all reasonably available alternatives; and
(d)
if necessary, changes to the design/construction methodology in consultation with the State and subject to complying with the requirements of the Agreement.
1.2.2
Protocols in relation to how community impacts associated with construction will be managed must be developed in consultation with the State and published, and made freely available to the public including a suite of standard measures to mitigate issues including noise and vibration on surrounding communities and consistent triggers for when such mitigation measures will be applied including mitigation measures such as alternative accommodation.
1.2.3
Protocols must include measures to evaluate the effectiveness of the noise and vibration mitigation, including field monitoring and regular market research conducted with surrounding communities.
Visitor Information Centre 1.3.1
A Visitor Information Centre must be established and must: (a)
PART G
enable stakeholders to raise concerns or provide feedback in relation to the Project;
Project Scope & Requirements – Volume 1 of 3
Page 157 of 294
(b)
be easily accessible to the public via all modes of transport;
(c)
be located within 500m of the Project Area;
(d)
be able to accommodate parking for 5 visitors’ cars and one bus;
(e)
have a dedicated room for presentations which: (i)
accommodates up to 50 people; and
(ii)
contains PC and audio visual equipment to enable presentations to be displayed using USBs and DVDs;
(f)
operate from five months after Financial Close until Close Out;
(g)
be staffed from 10.00am – 5.00pm Monday to Friday, and 10.00am – 4.00pm on Saturdays (excluding public holidays);
(h)
include: (i)
up-to-date information on the Project using photographs and videos updated quarterly;
(ii)
high quality Project information and visual displays which detail matters of interest including: (A)Project benefits; (B)tunnel ventilation systems; (C)tunnel fire and life safety systems; (D)traffic management strategies; (E)urban design concept and integration in built and landscape outcomes including urban design features; (F)noise attenuation; (G)environmental and cultural heritage; (H)tunnel and bridge construction; (I)progress of the works; and (J)geotechnical information;
(iii)
samples of finishes and urban design materials;
(iv)
a 3D interactive model(s) of the Project including: (A)tunnel portals; (B)ventilation outlets; (C)the Freeway Control Centre; and (D)other relevant project features;
PART G
Project Scope & Requirements – Volume 1 of 3
Page 158 of 294
1.4
(v)
model of the tunnelling system(s) used;
(vi)
drive-through presentations; and
(vii)
other display material provided by the State.
Accommodation for major community events
Project Co must plan and implement appropriate traffic and transport management measures for any major community events that occur during the Term. 1.5
Community Advisory Group 1.5.1
The State proposes to establish a community advisory group (CAG) to facilitate community and stakeholder involvement in the development of the Project in an advisory capacity and to create opportunities to address community concerns in relation to the Project.
1.5.2
Senior representatives of Project Co and the D&C Subcontractor will be required to participate in the CAG by:
1.5.3 1.6
(a)
attending all meetings as convened by the chair;
(b)
providing the CAG with a regular report of the D&C Activities; and
(c)
participating in other CAG stakeholder groups as required by the State from time to time.
The CAG will operate until a time determined by the State.
Sporting facilities at Holbrook Reserve and Ormond Park.
Project Co must ensure, to the reasonable satisfaction of the City of Moreland and the City of Moonee Valley, the ongoing operation of the sporting facilities at Holbrook Reserve and Ormond Park during the D&C Activities.
PART G
Project Scope & Requirements – Volume 1 of 3
Page 159 of 294
Part H
PART H
SPECIFIC APPENDICES
Project Scope & Requirements – Volume 1 of 3
Page 160 of 294
Part H1 1.1
Lane Requirements
General 1.1.1
1.1.2
As a minimum: (a)
the number of through and turning traffic lanes must be in accordance with sections 1.2 and 1.3;
(b)
the length of through and turning lanes must be in accordance with sections 1.2 and 1.3; and
(c)
the width of through and turning traffic lanes must be in accordance with section 1.4.
Number of traffic lanes (a)
Freeways (i)
The number of traffic lanes: (A)along the Freeway; (B)along CityLink and Eastern Freeway; and (C)along ramps, subject to section 1.3, must: (A)
be as shown in Table H1.1; and
(D)meet the requirements of Part H5. (b)
Other Roads (i)
The number of through and turning traffic lanes must not be less than: (A)those identified in section 1.3; (B)the requirements of Part H5; and (C)those existing prior to Financial Close.
1.1.3
Length of Lanes The lengths of traffic lanes for through and turning movements at intersections and interchanges must, as a minimum, be as identified in Table H1.2.
1.2
PART H
Freeway lanes
1Project Scope & Requirements – Volume 1 of 3
Page 161 of 294
Table H1.1 – Number of Freeway Lanes CityLink
Two traffic lanes Moreland Road
Moreland Road
Ramp P
Ramp Q 5 4 3 2 1
1 2 3 4 5
Brunswick Road
Hoddle Street North
Ramp L
Ramp D Ramp R
Ramp F
Hoddle Street South
Mt Alexander Road Hoddle Street
Ramp G
Ramp C2 Brunswick Road
Single lane entry ramp
Ramp C1
Ramp O
Alexandra Parade L Ramp B
Ramp E
Bus Lane
Ramp N
7 6 5 4 3 2 1
Eastern Freeway 1 2
Single lane exit ramp
3
Flemington Road
4
Ramp K
Ramp I
Flemington Road
5 6
Alexandra Parade
Ramp X
7
Transit Lane Yarra Bend Road
Ramp J
Bus Lane
Racecourse Road Point Z
Hoddle Street Ramp W
Two existing traffic lanes
Future Port Connection
Ramp M Racecourse Road
Bus Lane
Ramp A Ramp T
Dynon Road
Dynon Road
Transit Lane Hoddle Street Ramp V
Ramp U
Future Port Connection
Ramp H
L Limit of abutting works by others
CityLink
PART H
1Project Scope & Requirements – Volume 1 of 3
Page 162 of 294
1.3
Intersections and Interchange lanes Table H1.2 – Number and length of lanes
Location Brunswick Road / Ormond Road
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 163 of 294
Location Mount Alexander Road / Flemington Road
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 164 of 294
Location Flemington Road / Elliott Avenue
Hoddle Street
Table Notes: L = Left turning lane R = Right turning lane All lengths exclude taper lengths and are measured from the stop line.
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 165 of 294
1.4
Lane cross sectional dimensions Table H1.3 – Lane cross sectional dimensions
footpath
bicycle lane
Left emergency stopping lane / shoulder
Number / width of traffic lanes
Right emergency stopping lane / shoulder
(9)
off road shared use path
(9)
Yarra Bend Road to Ramp H
-
-
-
3.5 (1)
6 @ 3.5
3.0
Ramp H to tunnel portal
-
-
-
3.0 (2)
3 @ 3.5
1.0 (2)
Tunnel portal to Ramp E
-
-
-
1.0
3 @ 3.5
0.6
Ramp E to Ramp G
-
-
-
3.0
5 @ 3.5
1.0 (2) (6)
Ramp G to Yarra Bend Road
-
-
-
3.5 (1)
6 @ 3.5
3.0 (6)
-
-
-
1.0
3 @ 3.5
0.5
Eastbound west of Ramp B
-
-
-
4.1
2 @ 3.5
1.0
Westbound west of Ramp L
-
-
-
4.1
2 @ 3.5
1.0
South of Ramp V
-
-
-
E
E
E
Ramp V to Ramp A
-
-
-
0.5
4@ 3.35 (8)
0.5
Ramp A to Ramp L
-
-
-
E
E
E
-
-
2.5
5@ 3.35 (8)
0.5
(2)
Location
Eastern Freeway - Westbound
Eastern Freeway - Eastbound
Tunnels
East West Link – Eastern Section
CityLink - Northbound
Ramp L entry to Ramp P
North of Ramp P
-
-
-
E
E
E
North of Ramp Q
-
-
-
E
E
E
Ramp Q to Ramp B
-
-
-
2.5
5@ 3.35(8)
0.5
CityLink - Southbound
(2)
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 166 of 294
footpath
bicycle lane
Left emergency stopping lane / shoulder
Number / width of traffic lanes
Right emergency stopping lane / shoulder
(9)
off road shared use path
(9)
Ramp B to Ramp S
-
-
-
3.0 (7)
4 @ 3.5
0.6
Ramp S to Ramp M
-
-
-
E
E
E
Ramp M to Ramp U
-
-
-
0.5
4@ 3.35 (8)
0.5
South of Ramp U
-
-
-
E
E
E
Eastbound
-
2.1
-
-
no. varies / 3.5
-
Westbound
-
2.1
-
-
no. varies / 3.5
-
Location
Ormond Road / Brunswick Road
Flemington Road / Mount Alexander Road ≥3.2m
Both directions Connector Road Northbound
-
-
-
0.6
2 @ 3.5
Southbound
-
-
-
0.6
2 @ 3.5
Others Existing
Hoddle Street - northbound Johnston Street to Ramp G
-
-
-
-
4 @ 3.0
-
through plus bus lane
1 @ 3.0 Ramp G to Ramp J
-
2.5
-
-
3 @ 3.3
-
through
2 @ 3.3 left
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 167 of 294
Location
footpath
bicycle lane
Left emergency stopping lane / shoulder
Number / width of traffic lanes
Right emergency stopping lane / shoulder
(9)
off road shared use path
(9)
Ramp J to Ramp D
2.5
-
-
-
3 @ 3.3
-
through
Ramp D to Roseneath Street
-
-
-
-
3 @ 3.0
-
reducing to 2 lanes
Hoddle Street – southbound Roseneath Street to Ramp F
-
E
1.5
-
6 @ 3.0
-
(5)
Ramp F to Ramp H
3.0
-
-
-
4 @ 3.3
-
through
2 @ 3.0 right
South of Ramp H
E
Alexandra Parade E Alexandra Parade Ramp Westbound Ramp nose to Hoddle Street Bridge
Hoddle St Bridge to Gold Street
-
-
-
3.0
3 @ 3.5
3.0
(2)
(3)
(2)
-
-
-
1.0
3 @ 3.5
1.0
-
-
-
3.0
3 @ 3.5
1.0
(2)
(4)
Alexandra Parade Ramp Eastbound West of Gold Street
Ramps Through Lanes
3.5 (10)
Ramp G
-
-
3.0
0.6
2 @ 3.5
1.0
plus
1 @ 3.5 bus lane
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 168 of 294
Right emergency stopping lane / shoulder
(9)
Number / width of traffic lanes
Left emergency stopping lane / shoulder
bicycle lane
Location
footpath
off road shared use path
(9)
Table Notes: (1)
Also used as bus lane May be reduced to 0.6m at local constraints and from Ramp H to 200m west of Merri Creek Bridge (3) Includes the transit lane identified in Table H1.1 (4) May be reduced to 2 lanes under Hoddle Street (5) Number of lanes reduce from 6 at the stop line to 2 at Roseneath Street (6) May be reduced to 0.6m at the Merri Creek bridge (7) May be narrowed to 1m at Ramp B exit nose (8) 3.5m where practicable (9) “shoulder" when width <2m, “emergency stopping lane” when width >=2m (10) May be reduced to 3.3m along Ramp H/Ramp I from the start of the transit Lane to Ramp I “E” Existing width “-“ Not applicable (2)
General (a) all roadside hardware must be located clear of nominated footpath and shared use path widths. (b) parking to be reinstated as per existing. (c) all dimensions are in metres (d) minimum clearances to barriers in accordance with Table H1.4.
Table H1.4 – Clearance to barriers
PART H1
Location
Clearance to Barriers (from outer edge of emergency stopping lane / shoulder)
Tunnels
0.0m
Existing CityLink Elevated Roadway and approach ramps
0.0m
New Structures
0.0m or sight distance requirements whichever is the greatest
Project Scope & Requirements – Volume 1 of 3
Page 169 of 294
Location
Clearance to Barriers (from outer edge of emergency stopping lane / shoulder)
Eastern Freeway bridge over Merri Creek
0.0m or sight distance requirements whichever is the greatest
CityLink over Moonee Ponds Creek
0.0m or sight distance requirements whichever is the greatest
Eastern Freeway left emergency stopping lane - eastbound east of Ramp G and westbound east of Ramp H
0.6m to allow for bus use
Connector Road
0.0m or sight distance requirements whichever is the greatest
Elsewhere width must be widened to account for sight distance and pavement widening requirements on horizontal curves
PART H1
Project Scope & Requirements – Volume 1 of 3
Page 170 of 294
Part H2 1.
Posted Speeds and Design Speeds
Posted speeds and design speeds 1.1.1
The posted speeds must be in accordance with Table H2.1
1.1.2
The design speeds used for road design must be calculated in accordance with the VicRoads Supplement to AUSTROADS Road Design - Part 3 and must not be less than the minimum design speeds shown in Table H2.1.
1.1.3
Curves must be signed with an advisory speed when the design speed is less than the posted speed.
Table H2.1 – Posted, design and advisory speeds Posted (1) Speed Limit km/h
Minimum Design Speed km/h
Curve Advisory Speed km/h
Eastern Freeway (east of Hoddle easterly ramps)
100
110
n/a
East West Link - Eastern Section
80
80 (4)
n/a
CityLink
80
80
n/a
Ramp A
80
80
n/a
Ramp B
80
80
n/a
Ramp L
80
80
n/a
Ramp M
80
80
n/a
The Road being approached posted speed
80
n/a
The freeway being entered posted speed.
Appropriate to the posted speed of the freeway being entered.
n/a
Hoddle Street
Existing
80
n/a
Alexandra Parade
Existing
70
n/a
Wellington Street
Existing
60
n/a
Location
Freeway Carriageways
Freeway to Freeway Ramps
Freeway Exit Ramps All except freeway to freeway ramps
Freeway Entry Ramps (3) All except freeway to freeway ramps
Other Roads (2)
PART H2
Project Scope & Requirements – Volume 1 of 3
Page 171 of 294
Location
Posted (1) Speed Limit km/h
Minimum Design Speed km/h
Curve Advisory Speed km/h
Smith Street
Existing
60
n/a
Flemington Road
Existing
60
n/a
Boundary Road
Existing
60
n/a
Racecourse Road
Existing
60
n/a
Manningham Street
Existing
60
n/a
Mount Alexander Road
Existing
60
n/a
Connector Road
60
60
n/a
All Others
Existing
60
n/a
Table Notes 1 LUMS may operate some roads at a lower level 2 Where achievement of Minimum Design Speed is not practicable due to effects on adjacent land or adverse environmental effects, the higher of: the design speed calculated in accordance with VicRoads Supplement to AUSTROADS Road Design – Part 3; and the design speed formally agreed with the relevant Facility Owner, may be used. 3 Alexandra Parade ramps connect to Alexandra Parade at Gold Street. 4 When traffic is relocated to a shoulder or emergency stopping lane under a traffic arrangement identified in Part H8, then the minimum design speed for that arrangement must be 60km/h with a minimum reaction time of 1.5 seconds.
PART H2
Project Scope & Requirements – Volume 1 of 3
Page 172 of 294
Part H3 1.
Design Traffic Volumes 1.1.1
1.2
Design Traffic Volumes The tables in this Part H3 identify the: (a)
design traffic volumes and vehicle mixes for design year 2031; and
(b)
annual growth rates throughout the O&M Phase.
Annual Average Weekday Traffic Volumes Table H3.1 – Sectional average annual weekday traffic volumes
Location
(1)
Two way daily design traffic volumes AAWDT 2031
Freeway Sections CityLink south of Moreland Road
230,000
CityLink south of Flemington Road
115,000
CityLink south of Racecourse Road
145,000
Freeway (to/from Future EWL Stages) west of western tunnel portal
60,000
Freeway under Melbourne cemetery
125,000
Freeway under Hoddle Street
100,000
Eastern Freeway east of Hoddle Street ramps
210,000
Freeway Ramps
PART H4
Ramp A
10,000
Ramp B
30,000
Ramp C1
15,000
Ramp C2
15,000
Ramp D
15,000
Ramp E
40,000
Ramp F
5,000
Ramp G
15,000
Ramp H
50,000
Ramp I
40,000
Ramp J
15,000
Ramp K
20,000
Project Scope & Requirements – Volume 1 of 3
Page 173 of 294
(1)
Location
Two way daily design traffic volumes AAWDT 2031
Ramp L
40,000
Ramp M
10,000
Ramp N
15,000
Ramp O
15,000
Ramp P
15,000
Ramp Q
15,000
Roads Hoddle Street (north)
50,000
Hoddle Street (south)
80,000
Alexandra Parade east of Wellington Street
80,000
Wellington Street North
10,000
Wellington Street South
15,000
Flemington Road
70,000
Boundary Road
15,000
Racecourse Road
40,000
Manningham Street
10,000
Mount Alexander Road (west of Ramp X)
40,000
Connector Road
20,000
All Others
10,000
Table Notes: 1 2
PART H4
Ramp Volumes are one way AAWDT Average Annual Weekday Traffic
Project Scope & Requirements – Volume 1 of 3
Page 174 of 294
1.3
Design Hour Traffic Volumes Figure H3.1 – Location Plan
Area E
Area F
PART H4
Project Scope & Requirements – Volume 1 of 3
Page 175 of 294
Table H3.2 - Area A (Scenario 1) From
Eastern Freeway, under Chandler Hwy
Hoddle Street South
Alexandra Parade Total
East West Link Tunnels
Hoddle Street, north of Eastern Freeway
Chandler Highway westbound entry ramp
PART H4
To
AM Peak vehicles / hour
PM Peak vehicles / hour
Hoddle Street South
1,550
750
Alexandra Parade - total
1,980
1,760
East West Link - tunnels
3,960
3,180
Hoddle Street, north of Eastern Freeway
100
140
Eastern Freeway, under Chandler Hwy
570
2,100
Alexandra Parade
50
50
East West Link - tunnels
200
600
Hoddle Street, north of Eastern Freeway
830
1,470
Chandler Hwy eastbound exit ramp
80
60
Eastern Freeway, under Chandler Hwy
1,780
2,250
Hoddle Street South
150
150
East West Link - tunnels
30
40
Hoddle Street, north of Eastern Freeway
50
50
Chandler Hwy eastbound exit ramp
170
100
Eastern Freeway, under Chandler Hwy
2,820
3,890
Hoddle Street South
780
270
Chandler Hwy eastbound exit ramp
520
820
Hoddle Street, north of Eastern Freeway
130
140
Eastern Freeway, under Chandler Hwy
330
240
Hoddle Street South
1,290
1,100
East West Link - tunnels
110
190
Chandler Hwy eastbound exit ramp
20
10
Hoddle Street South
20
10
Hoddle Street, north of Eastern Freeway
10
20
Alexandra Parade - total
140
260
East West Link - tunnels
860
920
Project Scope & Requirements – Volume 1 of 3
Page 176 of 294
Table H3.3 - Area B (Scenario 1) From
To
Brunswick Road / Ormond Road CityLink, north of Moreland Road
370
410
East West Link - Tunnels
1,660
1,650
Mount Alexander Road / Flemington Road
1,540
1,010
310
250
3,540
2,420
10
10
East West Link - Tunnels
110
160
Mount Alexander Road / Flemington Road
110
120
80
70
CityLink, south of Dynon Road
750
460
CityLink, north of Moreland Road
330
300
20
10
East West Link - Tunnels
1,180
910
CityLink north of Moreland Road
1,550
1,900
Moreland Road - Offramp
170
110
Brunswick Road
200
200
Ormond Road
690
960
Dynon Road
200
120
1,300
1,170
CityLink, south of Dynon Road
870
510
CityLink, north of Moreland Road
740
1,320
East West Link - Tunnels
950
1,170
Moreland Road - Offramp
80
90
Dynon Road
20
20
CityLink, south of Dynon Road
580
510
CityLink, north of Moreland Road
150
370
Moreland Road - Offramp
20
60
East West Link - Tunnels
30
150
Racecourse Road
20
20
2,430
3,690
390
810
Dynon Road CityLink, south of Dynon Road Brunswick Road / Ormond Road Moreland Road Onramp
Dynon Road
Brunswick Road / Ormond Road
Moreland Road
East West Link Tunnels
Mount Alexander Road / Flemington Road
Mount Alexander Road / Flemington Road Racecourse Road
Dynon Road
CityLink, south of Dynon Road
PART H4
AM Peak PM Peak vehicles / vehicles / hour hour
CityLink, north of Moreland Road Moreland Road - Offramp
Project Scope & Requirements – Volume 1 of 3
Page 177 of 294
PART H4
East West Link - Tunnels
490
970
Racecourse Road
480
570
Project Scope & Requirements – Volume 1 of 3
Page 178 of 294
Table H3.4 - Area C (Scenario 1) From
AM Peak vehicles / hour 0
PM Peak vehicles / hour 10
20
20
Boundary Road, south of Racecourse Road
140
70
CityLink,south of Racecourse Road
100
100
Racecourse Road, west of CityLink
300
780
Mount Alexander Road, west of CityLink
160
130
CityLink, south of Brunswick Road
120
230
Boundary Road, south of Racecourse Road
20
30
CityLink,south of Racecourse Road
10
20
Racecourse Road, west of CityLink
30
400
Mount Alexander Road, west of CityLink
580
1,050
CityLink, north of Mount Alexander Road
600
980
30
150
Church Street
100
270
Elliot Avenue
20
20
CityLink,south of Racecourse Road
20
40
Racecourse Road, west of CityLink
20
70
Mount Alexander Road, west of CityLink
50
50
CityLink, north of Mount Alexander Road
60
160
East West Link - Tunnels
30
60
Church Street
30
110
Elliot Avenue
40
50
Flemington Road, south of Elliott Avenue
20
10
360
410
Mount Alexander Road, west of CityLink
0
0
CityLink, north of Mount Alexander Road
3,000
4,930
520
1,120
Church Street
60
100
Elliot Avenue
40
40
Flemington Road, south of Elliott Avenue
10
10
0
10
To East West Link - Tunnels Flemington Road, south of Elliott Avenue
Elliot Avenue
Flemington Road, south of Elliott Avenue
East West Link - Tunnels
Boundary Road, south of Racecourse Road
Racecourse Road, west of CityLink
CityLink,south of Racecourse Road
East West Link - Tunnels
Boundary Road, south of Racecourse
PART H4
Project Scope & Requirements – Volume 1 of 3
Page 179 of 294
From
AM Peak vehicles / hour
PM Peak vehicles / hour
Mount Alexander Road, west of CityLink
0
10
CityLink, north of Mount Alexander Road
100
210
East West Link - Tunnels
470
760
Church Street
60
40
Elliot Avenue
710
340
Flemington Road, south of Elliott Avenue
220
60
0
0
450
350
40
40
420
190
Church Street
50
50
Elliot Avenue
220
220
1,200
690
Boundary Road, south of Racecourse Road
0
0
CityLink,south of Racecourse Road
0
0
Racecourse Road, west of CityLink
0
0
1,770
1,820
0
0
Elliot Avenue
260
210
Flemington Road, south of Elliott Avenue
930
630
Boundary Road, south of Racecourse Road
450
220
CityLink,south of Racecourse Road
4,690
3,200
Racecourse Road, west of CityLink
10
70
0
0
1,180
910
Church Street
50
10
Elliot Avenue
20
0
230
50
20
10
CityLink,south of Racecourse Road
1,070
630
Racecourse Road, west of CityLink
830
450
To Road
Racecourse Road, west of CityLink
Boundary Road, south of Racecourse Road CityLink,south of Racecourse Road CityLink, north of Mount Alexander Road East West Link - Tunnels
Mount Alexander Road, west of CityLink
Flemington Road, south of Elliott Avenue
East West Link - Tunnels Church Street
CityLink, south of Brunswick Road
Mount Alexander Road, west of CityLink Brunswick Road / Ormond Road
East West Link Tunnels
PART H4
East West Link - Tunnels
Flemington Road, south of Elliott Avenue Boundary Road, south of Racecourse Road
Project Scope & Requirements – Volume 1 of 3
Page 180 of 294
AM Peak vehicles / hour 150
PM Peak vehicles / hour 650
1,720
2,010
890
1,160
0
0
330
190
Boundary Road, south of Racecourse Road
0
0
CityLink,south of Racecourse Road
0
0
Racecourse Road, west of CityLink
0
0
Mount Alexander Road, west of CityLink
0
0
CityLink, south of Brunswick Road
0
0
East West Link - Tunnels
0
0
AM Peak vehicles / hour 1,070
PM Peak vehicles / hour 630
1,300
1,170
0
0
1,720
2,010
Brunswick Road / Ormond Road
890
1,160
Mount Alexander Road / Flemington Road Interchange
East West Link - Tunnels
940
1,150
CityLink, south
East West Link - Tunnels
520
1120
Future EWL Stages
East West Link - Tunnels
0
0
CityLink, north of Brunswick Road
East West Link - Tunnels
1,770
1,820
Brunswick Road / Ormond Road
East West Link - Tunnels
1,180
910
From
To Mount Alexander Road, west of CityLink CityLink, south of Brunswick Road Brunswick Road / Ormond Road Elliot Avenue Flemington Road, south of Elliott Avenue
Church Street
Table H3.5 - Area D (Scenario 1) From
To CityLink, south Mount Alexander Road / Flemington Road Interchange
East West Link Tunnels
Future EWL Stages CityLink, north of Brunswick Road
PART H4
Project Scope & Requirements – Volume 1 of 3
Page 181 of 294
Table H3.6 - Area D (Scenario 2) AM Peak vehicles / hour 530
PM Peak vehicles / hour 170
770
490
Future EWL Stages
1,230
2,240
CityLink, north of Brunswick Road
1,470
1,610
Brunswick Road / Ormond Road
790
1,060
Mount Alexander Road / Flemington Road Interchange
East West Link - Tunnels
340
610
CityLink, south
East West Link - Tunnels
150
580
Future EWL Stages
East West Link - Tunnels
2,360
1,330
CityLink, north of Brunswick Road
East West Link - Tunnels
1,330
1,540
Brunswick Road / Ormond Road
East West Link - Tunnels
1,020
800
AM Peak vehicles / hour 100
PM Peak vehicles / hour 100
70
80
Brunswick Road
600
410
East West Link Tunnels
440
650
Myrnong Crescent
0
0
CityLink, northbound entry ramp
0
20
Brunswick Road
200
110
East West Link Tunnels
300
150
Ormond Road
110
100
Brunswick Road
190
210
10
30
Ormond Road
150
160
Pattison Street
20
20
From
To CityLink, south Mount Alexander Road / Flemington Road Interchange
East West Link Tunnels
Table H3.8 - Area E (Scenario 1) From
To Pattison Street CityLink, northbound entry ramp
Ormond Road
Pattison Street
CityLink, southbound exit ramp
PART H4
Myrnong Crescent
Project Scope & Requirements – Volume 1 of 3
Page 182 of 294
From
AM Peak vehicles / hour 240
PM Peak vehicles / hour 310
0
30
Ormond Road
420
450
Pattison Street
20
150
250
200
0
40
Ormond Road
490
420
Pattison Street
180
300
Brunswick Road
200
300
Ormond Road
20
20
Pattison Street
50
120
CityLink, northbound entry ramp
10
0
Brunswick Road
20
0
East West Link Tunnels
50
0
To East West Link Tunnels Myrnong Crescent
Brunswick Road
CityLink, northbound entry ramp Myrnong Crescent EWL Tunnels
Myrnong Crescent
Table H3.7 - Area F (Scenario 1)
To
Stubbs Street
Racecourse Road west of Stubbs
150
200
East West Link Tunnels
150
200
Racecourse Road east of CityLink exit ramp
160
250
10
10
410
780
1,250
500
Stubbs Street
50
50
Housing Estate
10
10
250
1070
Stubbs Street
50
150
Housing Estate
30
30
Racecourse Road west of Stubbs Street
700
400
Stubbs Street
140
120
Housing Estate Racecourse Road west of Stubbs
Racecourse Road east of CityLink exit ramp East West Link Tunnels
PART H4
AM Peak PM Peak vehicles / vehicles / hour hour
From
East West Link Tunnels Racecourse Road east of CityLink exit ramp
Racecourse Road west of Stubbs Street
Project Scope & Requirements – Volume 1 of 3
Page 183 of 294
To
CityLink Exit Ramp
Racecourse Road west of Stubbs Street
Housing Estate
1.4
AM Peak PM Peak vehicles / vehicles / hour hour
From
300
350
Stubbs Street
60
60
Racecourse Road west of Stubbs Street
20
20
Stubbs Street
20
20
Racecourse Road east of CityLink exit ramp
30
30
East West Link Tunnels
10
10
Commercial Vehicles Table H3.9 - Commercial Vehicle Percentages
Location
1.5
Percentage of Commercial Vehicles Daily Average
AM Peak Hour
PM Peak Hour
East West Link
10%
7%
7%
Eastern Freeway main carriageways
10%
5%
5%
City Link main carriageways
15%
7%
7%
Freeway Ramps between CityLink and EWL
10%
5%
5%
Other Freeway Ramps
10%
5%
5%
Growth Rate Table H3.10 - Annual Growth Rates Time Scale
Prior to and including 2031
2%
Post 2031
1%
Part H4 1.
Rate per annum
Intersections and Interchanges
Intersections and Interchanges 1.1.1
PART H4
Project Co must provide interchange ramp control with the Roads as defined in Table H4.1.
Project Scope & Requirements – Volume 1 of 3
Page 184 of 294
Table H4.1 - Interchange traffic control Interchanges
Control
Hoddle Street / Alexandra Parade
Traffic Signals
Mount Alexander Road
Traffic Signals
Brunswick Road / Ormond Road
Traffic Signals
1.1.2
Project Co must provide intersection control with the Roads as defined in Table H4.2.
Table H4.2 - Intersection traffic control Intersections
Control
Mount Alexander Road / CityLink
Traffic Signals
Mount Alexander Road / Connector Road
Traffic Signals
Flemington Road / CityLink / Boundary Road
Traffic Signals
Flemington Road / Church Street
Traffic Signals
Racecourse Road / Connector Road
Traffic Signals
Alexandra Parade / Wellington Street
Traffic Signals
1.1.3
Project Co must provide pedestrian control across Alexandra Parade as defined in Table H4.3.
Table H4.3 - Pedestrian control
PART H4
Location
Control
Across Alexandra Parade at Gold Street
Traffic Signals
Project Scope & Requirements – Volume 1 of 3
Page 185 of 294
Part H5 1.
Performance Criteria
Performance Criteria 1.1.1
Freeways and ramps must accommodate the peak hour design volumes and vehicle mixes in Part H3 with at least an operating Level of Service of D.
1.1.2
Intersections and interchanges forming the Works must accommodate the design hour traffic volumes in Part H3 with: (a)
a degree of saturation of no more than 0.9 except as identified in Table H5.1; and
(b)
all turning lanes accommodating 95 percentile traffic queue lengths.
Table H5.1 - Intersection Performance Criteria
PART H5
Location / Time
Performance Criteria / Constraint
Hoddle Street interchange, Ramp H and Ramp I AM peak
The queue of traffic on Ramp H and Ramp I must be accommodated within the dedicated off ramp. The traffic queue must be calculated by assuming there is a: 1. westbound capacity constraint along Alexandra Parade at Gold Street of 2,300 vehicle/h; and. 2. southbound capacity constraint along Hoddle Street at Truro Street of 4,000 vehicles/h.
Project Scope & Requirements – Volume 1 of 3
Page 186 of 294
Part H6 1.
Public Transport Facilities and Off Road Paths
Eastern Freeway westbound Bus Lane at Hoddle Street 1.1.1
Project Co must modify the signalised intersection of the Eastern Freeway exit to Hoddle Street to allow free flow for buses passing from the bus lane along Ramp H to the Hoddle Street bus lane.
1.1.2
This free flow bus movement shall only be stopped by a signalised pedestrian movement which crosses the bus lane only (separate from the traffic lanes), generally in accordance with the Figure H6.1.
1.1.3
The traffic island between the bus lane and the traffic lanes must be sized to accommodate expected pedestrian usage.
Figure H6.1 – Bus lane at Eastern Freeway / Hoddle Street
2.
Hoddle Street north bound Bus Lane 2.1.1
3.
A dedicated bus lane must be designed and constructed along Hoddle Street from the departure side of Johnston Street to the Eastern Freeway via Ramp G which: (a)
ensures that the average travel time during peak periods for north bound buses, from the departure side of the Johnston Street / Hoddle Street intersection to the Merri Creek bridge on the Eastern Freeway, is no greater than that which exists prior to the commencement of the D&C Activities; and
(b)
includes all hardware at bus stops as agreed with Public Transport Victoria.
Transit Lane 3.1.1
The existing transit lane along the Eastern Freeway will cease operation following opening of Stage One.
3.1.2
Project Co must: (a)
PART H7
provide a transit lane along Ramp H and Ramp I generally as identified in Table H1.1; and
East West Link Stage One – Outline Scope & Requirements
Page 187 of 294
(b) 4.
add new transit lane signs and remove and modify existing transit lane signs within the Project Area as agreed with VicRoads.
Existing Bus, Tram and Train Services 4.1.1
PART H7
Project Co must retain all existing bus, tram and train services and make allowance for the Future Public Transport Infrastructure identified in Part H13.
East West Link Stage One – Outline Scope & Requirements
Page 188 of 294
Part H7 1.
Freeway Ramp Signals
Freeway ramp signals 1.1.1
Freeway ramp signals must: (a)
consist of the number of lanes at the stop line identified in Table H7.1;
(b)
provide bypass lanes as identified in Table H7.2; and
(c)
have lane storage lengths calculated to VicRoads Freeway Ramp Signals Handbook, except where adopting the desirable standard for total length of storage, based on a 4 minute wait time, is not achievable within design and land constraints. In those circumstances, appropriate cycle time variations must be adopted in accordance with the handbook.
Table H7.1 – Freeway ramp signal lanes Ramp
Lanes at Stop Line
Communications connections to
Ramp A
2
VicRoads and FCC
Ramp B
3
VicRoads and FCC
Ramp C1
2
VicRoads and FCC
Ramp C2
2
VicRoads and FCC
Ramp E
3
VicRoads and FCC
Ramp F
2
VicRoads and FCC
Ramp G
2
VicRoads and FCC
Ramp J
2
VicRoads and FCC
Ramp L (prior to Ramp O merge)
3
VicRoads and CityLink
Ramp O
2
VicRoads and CityLink
Ramp M
2
VicRoads and CityLink
Freeway between Ramp A merge and Ramp B merge
2
VicRoads and FCC
Table Note: For freeway ramp signal sites located on structure, the emergency stopping lane may be used for one of the lanes subject to a VicRoads approved signing and linemarking arrangement. Table H7.2 - Freeway Ramp Signal Bypass Lanes Ramp
PART H7
Type
East West Link Stage One – Outline Scope & Requirements
Page 189 of 294
Ramp G
PART H7
Bus Lane
East West Link Stage One – Outline Scope & Requirements
Page 190 of 294
Part H8
Variable Lane Configuration Management System
Project Co must design, install and operate traffic devices to enable each of the traffic configurations identified in Table H8.1 along the Freeway to be automatically, quickly, safely and efficiently operated. Table H8.1 - Variable lane configurations
Location Western Portal - Eastbound Option A Mt Alexander Ramp C City Link north Ramp B CityLink south Ramp A
Future EWL Stages
Eastern Freeway
Option B Mt Alexander Ramp C City Link north Ramp B CityLink south Ramp A
Future EWL Stages
Eastern Freeway
Option C Mt Alexander Ramp C City Link north Ramp B CityLink south Ramp A
Future EWL Stages
PART H9 Project Scope & Requirements – Volume 1 of 3
Eastern Freeway
Page 191 of 294
Western Portal – Westbound Option D City Link north Ramp L
Eastern Freeway
Future EWL Stages
Mt Alexander Ramp K CityLink south Ramp A
Option E City Link north Ramp L
Eastern Freeway
Future EWL Stages Mt Alexander Ramp K CityLink south Ramp A
Option F City Link north Ramp L
Eastern Freeway
Future EWL Stages
Mt Alexander Ramp K CityLink south Ramp A
PART H9 Project Scope & Requirements – Volume 1 of 3
Page 192 of 294
Part H9 1.
Directional Signage
Directional Signage Area Figure H9.1 – Directional signage area
2.
Directional Signage Destinations
2.1
Freeway Sections Table H9.1 – Freeway Sections Location
Sign Destination Scenario 1 is operational Scenario 2 commences during the period from upon the opening of opening of Stage One Future EWL Stages#. until immediately prior to opening Future EWL Stages.
CityLink Southbound to Ramp B
Southbound Ramp B to Ramp S Southbound Ramp S to M Southbound South of ramp M
To M3 Ringwood
City
City
To M1 SE Suburbs
To M1 SE Suburbs
City
City
To M1 SE Suburbs
To M1 SE Suburbs
To M1 SE Suburbs
To M1 SE Suburbs
To M1 West Gate Bridge To M1 West Gate Bridge SE Suburbs SE Suburbs
Northbound M1 to Footscray Road
PART H10
To M3 Ringwood
To M3 Ringwood (1)
To M8 Ballarat
Melbourne Airport
To M3 Ringwood (1)
Project Scope & Requirements – Volume 1 of 3
Page 193 of 294
Location
Sign Destination Scenario 1 is operational Scenario 2 commences during the period from upon the opening of opening of Stage One Future EWL Stages#. until immediately prior to opening Future EWL Stages. Melbourne Airport
Northbound Footscray Road to Ramp A
To M3 Ringwood
To M3 Ringwood
Melbourne Airport
Melbourne Airport
Melbourne Airport
Melbourne Airport
City
City
West Gate Bridge
To M8 Ballarat
Eastbound
Doncaster
Doncaster
Hoddle Street to Doncaster Road
Ringwood
Ringwood
Northbound Ramp A to Bulla Road
Eastern Freeway Westbound Doncaster Road to Hoddle Street
Table Notes: (1) Not required on West Gate Freeway east of M1 / M2 interchange
PART H10
Project Scope & Requirements – Volume 1 of 3
Page 194 of 294
2.2
Freeway Interchange Table H9.1 – East West Link / CityLink Freeway Interchange Road Destination
Sign Destination Scenario 1 is operational Scenario 2 commences during the period from upon the opening of Future opening of Stage One EWL Stages#. until immediately prior to opening Future EWL Stages.
CityLink north
Melbourne Airport
Melbourne Airport
East West Link - tunnels
Doncaster Ringwood
Doncaster Ringwood
Mount Alexander Road / Flemington Road
Flemington Road (2) City Nth (3)
Flemington Road (2) City Nth (3)
CityLink south
To M1 West Gate Bridge To M1 West Gate Bridge SE Suburbs (1)
SE Suburbs (1)
n/a
To M8 Ballarat
East West Link – Future Stages
Table Notes: (1)
Not required coming out of EWL tunnels
(2)
Only from EWL tunnels
(3)
Only from CityLink north
(#)
Refer to section 6 of Part H13
PART H10
Project Scope & Requirements – Volume 1 of 3
Page 195 of 294
2.3
Arterial Road Interchanges Table H9.3 – Arterial Road Interchanges Road Destination
Sign Destination Scenario 1 is operational during the period from opening of Stage One until immediately prior to opening Future EWL Stages.
Scenario 2 commences upon the opening of Future EWL Stages
Brunswick Road / Ormond Road Interchange Ormond Road
Moonee Ponds
Moonee Ponds
Melbourne Airport
Melbourne Airport
Brunswick Road
Brunswick
Brunswick
East West Link southbound entry ramp
Doncaster Ringwood
Doncaster Ringwood
CityLink, northbound entry ramp
Mount Alexander Road / Flemington Road Interchange Mount Alexander Road
Moonee Ponds
Moonee Ponds
CityLink, northbound entry ramp
Melbourne Airport
Melbourne Airport
East West Link north-eastbound entry ramp
Doncaster Ringwood
Doncaster Ringwood
City
City
(2)
(2)
West Gate Bridge
West Gate Bridge
Footscray
Ballarat
Flemington Road Mt Alexander Road / Racecourse Road new connector Road Hoddle Street Interchange East West Link
PART H10
Project Scope & Requirements – Volume 1 of 3
Page 196 of 294
Road Destination
Sign Destination Scenario 1 is operational during the period from opening of Stage One until immediately prior to opening Future EWL Stages.
Scenario 2 commences upon the opening of Future EWL Stages
Hoddle Street North
Clifton Hill
Clifton Hill
Eastern Freeway
Doncaster
Doncaster
Ringwood
Ringwood
City
City
Hoddle Street South
St Kilda Alexandra Parade
(1)
Parkville
St Kilda (1) Parkville
Table Notes: from Alexandra Parade only
(1) (2) (#)
VicRoads usual requirements Refer to section 6 of Part H13
Part H10 Road Safety Camera Hardware 1.
General 1.1.1
2.
Project Co must design, construct and maintain: (a)
eight road safety camera sites;
(b)
a centralised equipment room;
(c)
a communication conduit and pit sub system; and
(d)
power supply at the camera sites and the centralised equipment room.
Road safety camera sites 2.1.1
Road safety camera sites: (a)
are to be generally located in accordance with Table H10.1;
Table H10.1 - Road safety camera sites Indicative Location
Direction
Below Elliott Ave
Both tunnels
1&2
Below West side of Melbourne General Cemetery
Both tunnels
3&4
Below Nicholson Street
Westbound tunnel only
PART H10
Project Scope & Requirements – Volume 1 of 3
Site No.
5
Page 197 of 294
Indicative Location
Direction
Below George Street
Eastbound tunnel only
Hoddle Street bridge
Both directions
Site No. 6 7&8
(b)
are to be configured to meet Department of Justice usual requirements;
(c)
must allow for the following devices to be supplied and installed by the Department of Justice or its contractors:
(d)
(i)
image cameras;
(ii)
lane use management video monitoring cameras;
(iii)
vehicle detectors;
(iv)
control box; and
(v)
connecting cables;
must consist of the following items designed, constructed and maintained by Project Co: (i)
supporting beams in the tunnels to support image cameras that are: (A)located centrally above each lane; and (B)weighing 250kg each;
(ii)
brackets or poles to support lane use management video monitoring cameras;
(iii)
space for a control box which: (A)enables a road safety camera technician to safely access and maintain the control box contents; and (B)is located within 50m of conduit from the detectors, image cameras and video cameras;
(iv)
240V, 30A isolated power supply to the control box;
(v)
communication conduits and pits between: (A)the control box and the supporting beam inside the tunnel; (B)the control box and the underside of the Hoddle Street bridge; (C)the control box and the video cameras; and (D)the control box and the detectors;
(vi)
power conduit and pits between: (A)the control box and the supporting beam inside the tunnel;
PART H10
Project Scope & Requirements – Volume 1 of 3
Page 198 of 294
(B)the control box and the underside of the Hoddle Street bridge; (C)the control box and the video cameras; and (D)the control box and the detectors. 3.
Centralised equipment room 3.1.1
4.
A centralised equipment room must be provided which must: (a)
be secure and easily accessible to road safety camera technicians from the Department of Justice;
(b)
be able to house ten full height 19 inch rack cabinets; and
(c)
240V single phase, 30A isolated power supply (3 phase).
Road safety camera communication sub system. 4.1.1
A road safety camera communication sub system must: (a)
be provided for the sole use of the Department of Justice;
(b)
consist of: (i)
communication conduit 100mm in diameter which: (A)connects together the control boxes at each road safety camera site and the centralised equipment room; (B)connects the centralised equipment room to a pit abutting the Leased Area and at a location agreed by Department of Justice; and (C)is constructed in a straight line (where possible) or is a set distance from a continuous roadside element with a minimum radius of 800m;
(ii) (c) 5.
communication pits which are lockable; and
be fully self-integrated and not connected to any other power or communication sub system.
Performance Requirements
The power supply for the safety camera sites and the centralised equipment room must meet the performance requirements identified in Part H19.
PART H10
Project Scope & Requirements – Volume 1 of 3
Page 199 of 294
Part H11 VicRoads Communication Hardware 1.1.1
Project Co must provide a communication sub system for the sole use of VicRoads. The VicRoads communication sub system must: (a)
PART H11
consist of a communication conduit: (i)
on either side of CityLink from Moreland Road to the western tunnel portal;
(ii)
within the tunnel; and
(iii)
on either side of the freeway from the eastern tunnel portal to the eastern abutment of the Merri Creek.
(b)
contain 2x96 core fibres in the conduit identified in section 1.1.1(a)(ii);
(c)
contain 1x96 core fibres in each conduit identified in section 1.1.1(a)(i) and section 1.1.1(a)(iii);
(d)
include communication pits at Moreland Road and on the eastern abutment of the Merri Creek; and
(e)
meet the usual requirements of VicRoads.
Project Scope & Requirements – Volume 1 of 3
Page 200 of 294
Part H12 Tolling Hardware 1.
2.
General 1.1.1
The State intends to implement an electronic Multi Lane Free Flow (MLFF) system along the Freeway which will be interoperable with all other tolling systems in Australia.
1.1.2
Project Co must design, construct and maintain: (a)
[not disclosed – could disadvantage parties in future projects] tolling point sites;
(b)
a centralised tolling room;
(c)
a communication conduit and pit sub system;
(d)
a power supply conduit and pit sub system; and
(e)
a power supply at the tolling points and the centralised tolling room.
Tolling point sites 2.1.1
2.1.2
Tolling point sites are to be generally located: (a)
in accordance with Table H12.1; and
(b)
on ramps, at least 25m downstream from the associated ramp meter site stop line.
The precise location of the tolling point sites and the gantries, pits and conduits at each site must be in accordance with the Tolling Services Contractor’s reasonable requirements.
Table H12.1 - Tolling Point Sites
Location
Tolling Point No
Eastern Freeway westbound between Ramp H diverge and Ramp J merge
1
eastbound between Ramp D diverge and Ramp E merge
2
Ramps Ramp A
3
Ramp B and Ramp C1 (prior to merge of Ramp C1)
4
Ramp C2
5
Ramp D
6
Ramp J
7
Ramp K
8
PART H12
Project Scope & Requirements – Volume 1 of 3
Page 201 of 294
Location
Tolling Point No
Ramp L and Ramp N (past diverge of Ramp N)
9
Ramp M
10
2.1.3
Tolling point sites must consist of the following: (a)
a main gantry and a secondary gantry foundations each located across the carriageway which must: (i)
be located: (A)at least 20m apart; (B)to ensure that the gantries are aligned at 90o +/- 1o to the centre of the road.
(b)
3.
(ii)
have a flat surface;
(iii)
have bolts extending from the surface to enable a tolling gantry to be connected; and
(iv)
be designed and constructed to enable the Tolling Services Contractor to easily connect the tolling gantry;
a toll point shelter which must: (i)
consist of a flat surface 10m2 suitable to place a secure building on; and
(ii)
be located within 50m of the nearest gantry;
(c)
a car park located within 50m of the tolling point shelter for a tolling technician to use to safely access the tolling point site and equipment;
(d)
access between: (i)
the car park and the tolling point shelter; and
(ii)
the tolling point shelter site and the main and secondary gantries;
(e)
power conduits and pits; and
(f)
communication conduits and pits.
2.1.4
Tolling points must allow for gantries, cabling, tolling and vehicle detection devices and lighting equipment to be supplied, installed and maintained by the Tolling Services Contractor.
2.1.5
Tolling points must be integrated into the design of the Works.
2.1.6
The pavement 10m either side of each toll point gantry must have a maximum water film depth of 1.5mm
Centralised Tolling Room 3.1.1
PART H12
A centralised tolling room must be provided which must:
Project Scope & Requirements – Volume 1 of 3
Page 202 of 294
(a)
be secure and easily accessible to tolling technicians from the Tolling Services Contractor;
(b)
have a floor space of 50m2;
(c)
have an associated car parking area:
(d)
4.
(i)
for 2 maintenance vehicles; and
(ii)
within 50m of the centralised tolling room; and
be supplied with power which: (i)
is separately metered; and
(ii)
is of a capacity that will enable the Tolling Services Contractor to operate the tolling system within the centralised tolling room including lighting, heating and cooling.
Tolling communication sub system 4.1.1
The tolling communication sub system must: (a)
consist of a communication conduit 100mm in diameter which: (i)
connects a communication pit at the base of the main gantry at the tolling points identified with a communication pit at the associated tolling point shelter;
(ii)
forms a redundant communication network connecting: (A)tolling point shelter pits; (B)the centralised tolling room communication pit; and (C)a pit adjacent to the Leased Area at Hoddle Street;
(b)
(iii)
connects a pit at the base of the main gantry with a pit at the base of the secondary gantry at each tolling point site; and
(iv)
is located in a straight line between pits or is a set distance from a continuous roadside element with a minimum radius of 800m:
consist of communication pits: (i)
located: (A)adjacent to each tolling point shelter; (B)at the base of the main gantry; (C)at the base of the secondary gantry; and (D)at no more than 200m centres along the communication conduit;
PART H12
(ii)
which are lockable; and
(iii)
which meet the reasonable requirements of the Tolling Services Contractor;
Project Scope & Requirements – Volume 1 of 3
Page 203 of 294
5.
(c)
be for the sole use of the Tolling Services Contractor;
(d)
meet the reasonable requirements of Tolling Services Contractor; and
(e)
be a fully self-integrated sub system not connected to any other power or communication sub system.
Tolling power sub system 5.1.1
The tolling power sub system must: (a)
(b)
PART H12
consist of power conduit 100mm in diameter which: (i)
connects a power pit at each tolling point shelter site with a power pit at the nearest local road power pole;
(ii)
connects a power pit at each tolling point shelter site with a power pit at the base of the corresponding main gantry;
(iii)
connects a power pit at the base of the main gantry with a pit at the base of the associated secondary gantry; and
(iv)
is located in a straight line between pits or is a set distance from a continuous roadside element with a minimum radius of 800m;
consist of power pits located: (i)
adjacent to each tolling point shelter;
(ii)
at the base of at the main gantry;
(iii)
at the base of the secondary gantry; and
(iv)
at no more than 200m centres along the communication conduit;
(c)
be for the sole use of the Tolling Services Contractor;
(d)
meet the reasonable requirements of Tolling Services Contractor; and
(e)
be a fully self-integrated sub system not connected to any other power or communication sub system.
Project Scope & Requirements – Volume 1 of 3
Page 204 of 294
Part H13 Allowances for Future Infrastructure 1.
2.
General 1.1.1
Provision must be made for, and the Works must not preclude, the design and construction of the Future Infrastructure (as identified in sections 2 to 9 below).
1.1.2
Preliminary Design Documentation and Certified Design Documentation must demonstrate that the Works have been designed and will be constructed to ensure any required future modifications to the Relevant Infrastructure and the Returned Facilities required to construct the Future Infrastructure are minimised to the fullest extent practicable.
Upfield Rail Line 2.1.1
3.
Two standard gauge tracks to the west of the existing tracks with: (a)
clearances in accordance with VRIOGS 001 – Envelope A (passenger and freight use but excluding double stacked freight container use); and
(b)
loading for freight trains, excluding double stacked freight container use.
Clifton Hill Rail Line
Four broad gauge stabling tracks to the east of the existing tracks with clearances in accordance with VRIOGS 001 – Envelope A (passenger use). 4.
Public Safety Barriers Public safety barriers on all structures which have a fall height greater than 10m and are over traffic lanes or emergency stopping lanes.
5.
CityLink Widening
Widening of CityLink as identified in section 1 of Part I . 6.
Future Port Connection
Extension of East West Link to the Port and beyond, including the signage identified in Part H9 as “Scenario 2”. 7.
Cooperative ITS functionality
See section 1.9 of Part D. 8.
Freeway Control Centre
Increase in size and capacity of the Freeway Control Centre to cater for potential Future EWL Stages and/or other relevant uses. 9.
PAM #1 CityLink additional north bound lane option
PART H13
Project Scope & Requirements – Volume 1 of 3
Page 205 of 294
Part H14 Over-Dimensional Route 3 1.
Over-dimensional route 3 1.1.1
1.1.2
PART H14
Where the Works overlap OD Route 3, OD Route 3 must: (a)
be maintained at all times unless agreed by VicRoads as part of a WTMP;
(b)
have a minimum vertical clearance of 5.9 m for new overhead constraints;
(c)
have a minimum vertical clearance of 6.1 m for overhead pedestrian structures; and
(d)
meet VicRoads usual requirements for over dimensional vehicle routes.
The requirement of paragraph (b) in section 1.1.1 does not apply to the Hoddle Street overpass bridge. At this location the vertical clearance at Financial Close must not be reduced.
Project Scope & Requirements – Volume 1 of 3
Page 206 of 294
Part H15 Property Access Table H15.1 - Special property access Location
Notes
1/159 Hotham Street, Collingwood 2/159 Hotham Street, Collingwood 3 Noone Street, Clifton Hill
Rear laneway access
5 Noone Street, Clifton Hill
Rear laneway access
7 Noone Street, Clifton Hill
Rear laneway access
9 Noone Street, Clifton Hill
Rear laneway access
Moonee Valley Racecourse Access Road from Pattison Street
Reconstruct access road including intersection with Pattison Street as required
Holbrook Reserve access road under CityLink adjacent to Moonee Ponds Creek
Maintain clearances
Ormond Park access road
PART H15
Realign access road if required
Project Scope & Requirements – Volume 1 of 3
Page 207 of 294
Part H16 Lease Principles Location
Lease Principle
General Upper Boundary The Upper boundary of the Leased Area is the higher of; the distance above the pavement necessary to operate the Freeway; the distance above and around all infrastructure that is required to operate and maintain the Freeway; and that identified in the Lease Principles within this Table. Lower Boundary The Lower boundary of the Leased Area is the lower of; 15 metres below the existing surface; and that identified in the Lease Principles within this Table H16. Legend
CityLink LP01 - Entry and Exit ramps Area Boundary Perpendicular across the ramp from the ramp concrete nose or the barrier attenuator, whichever gives the larger Leased Area. The barrier attenuator is within Project Co Leased Area.
plan view
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 208 of 294
Location
Lease Principle
LP02 – Elevated East West Link carriageways and ramps Lower Boundary Provide 100mm buffer around pier, pile cap, piles and under structure as shown by the dotted line.
longitudinal section
Area Boundary 1m outside all structural and architectural components of the bridge (as shown in plan view). plan view LP03 - Ramp L north of Ramp N diverge
cross section looking north
PART H16
Western Boundary Western extent of Leased Area boundary is located to which ever results in the greater Leased Area, where; A = 1m for aboveground infrastructure; and B = 100mm for below ground infrastructure. Eastern Boundary Western side of the barrier between Ramp L2 and CityLink northbound carriageway .
Project Scope & Requirements – Volume 1 of 3
Page 209 of 294
Location
Lease Principle
LP04 - Ramp B
Eastern Boundary CityLink Lease boundary at Financial Close Western Boundary As per LP03 (between CityLink)
LP05 - Ramp N
Lower Boundary As per LP02 Area Boundary As per LP02
LP06 – Ramp A and Ramp M
Lower Boundary As per LP02. Area Boundary As per LP01 and LP02.
LP07 – Shared use path bridge between Debney Park and Flemington Bridge
Lower Boundary As per LP02 Area Boundary As per LP02
LP08 – Connector Road
Area Boundary from 1m outside back of kerb to 1m outside back of kerb where at grade and as per LP02 otherwise. Lower Boundary (when on structure) As per LP02 Upper Boundary (under CityLink) As per LP02
Ross Straw Field / Upfield Rail Line / Royal Park LP 10 – Freeway over
Lower Boundary As per LP02 Area Boundary As per LP02.
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 210 of 294
Location
Lease Principle
LP 11 – Ross Straw Field
Boundary of strata land Generally the fence line as shown in drawings EWT-WCLUD100-DGR-LA-2056 EWT-WCLUD100-DGR-LA-2062 EWT-WCLUD100-DGR-LA-2063
as shown in Proposed Leased Area Plans LP 12 – Freeway under Upfield Rail Line Upper Boundary Top of tunnel structure but not including rail structure and the associated bearings. Lower Boundary As per LP20
LP13 – Shared Use Path Land Bridge
Area Boundary As per LP02 Lower Boundary As Per LP02 Note: Landscaping and all attachments on the bridge are included in the Leased Area.
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 211 of 294
Location
Lease Principle
LP14 – Portal buildings and structures (including, plant room access, access hatch and vent stack)
Side Boundary The distance X is 0.1m outside all structural components and architectural cladding, whichever is the greater.
tunnel longitudinal section Tunnels LP20 – Driven Tunnels. All Boundaries Where no tunnel infrastructure extends more than 4m out from the tunnel inner lining, X = 5m from the tunnel inner lining. Where tunnel infrastructure extends more than 4m out from the tunnel inner lining, the boundary is to be extended vertically and/or horizontally to cater for the protrusion with X = protrusion from the tunnel inner lining + 2m.
tunnel cross section
PART H16
Upper boundary The distance between the natural surface and the top of the Leased Area (Y) must be 15m for all privately owned property and 5m for all other land.
Project Scope & Requirements – Volume 1 of 3
Page 212 of 294
Location
Lease Principle
LP21 – Cut and Cover Tunnels.
Upper Boundary The higher of; The top most surface of the structural component. The top most surface of polystyrene fill above the structural component. The top most surface of protective layers related to the structural component or polystyrene fill. 5 metres below the natural surface. Side and Lower Boundary As per LP20.
tunnel cross section
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 213 of 294
Location
Lease Principle
LP22 – Transition from cut and cover tunnels and surface road.
Area Boundary For distance X (measured from the inside of the structural element and at least 1m below ground) Where no infrastructure extends more than 4m out from the inside of the structural element, X = 5m. Where infrastructure extends more than 4m out from the inside of the structural element X = protrusion from the structural element + 2m For distance Y (measured for the outside of the structural element) When abutting land is park land Y = 1m When abutting land is roadside Y=100mm When abutting land is road pavement Y=0m (ie the outside face of the structure and / or barrier) For distance Z (measured for the outside of the structural element) Where no infrastructure extends more than 4m out from the inside of the structural element, Z = 5m. Where infrastructure extends more than 4m out from the inside of the structural element Z = protrusion from the structural element + 2m.
cross section
Hoddle Street Interchange LP40 – Alexandra Parade / Eastern Freeway boundary.
PART H16
Ramp E westerly extent is the nose of the diverge for traffic going to Hoddle Street Ramp I westerly extent is the nose at the connection between the Ramp and the lane from Hoddle Street to Alexandra Parade.
Project Scope & Requirements – Volume 1 of 3
Page 214 of 294
Location
Lease Principle
LP41 – between LP40 and Hoddle Street.
cross section As shown LP42 – Ramp D and Ramp J.
Include in Leased Area.
LP42 – Under Hoddle Street.
Upper Boundary as per LP02
LP43 – between Hoddle Street and Merri Creek bridge.
Area Boundary As per the existing Eastern Freeway road declaration with eastern boundary being the eastern Merri Creek bridge abutment or expansion joint or edge of approach slab whichever results in the larger Leased Area, plus all areas required associated with the cable stays Upper Boundary As per LP02 under rail bridge
LP44 – Ramp G over both Hoddle Street and the Hoddle Street to Alexandra Parade connecting road.
Lower Boundary As per LP02 Area Boundary As per LP02
LP45 – Pedestran structure between Upfield Rail line and Merri Creek
All structural and architectual components of the bridge and ramps.
Tolling
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 215 of 294
Location
Lease Principle
LP50 – Toll point shelter and associated infrastructure
Area Boundary Include: toll point shelter site (plus a 2m buffer around the site); associated car parking; access road to associated car park; access paths and stairways (between toll point shelter and toll gantry and between gantries); and tolling conduits and pits.
Other LP90 – Any minor areas of land identified by the State which would otherwise result in that area being inaccessible or land locked.
Include in Leased Area.
LP91 – Any other area of land, agreed with the State, which would otherwise be included in the definition of Maintained Off-Freeway Facilities.
Include in Leased Area.
LP92 – Any other area of land for which there is not an appropriate Lease Principle
Appropriate Lease Principle to be determined by the State and advised to Project Co
PART H16
Project Scope & Requirements – Volume 1 of 3
Page 216 of 294
Part H17 Maintenance Principles Location
Guideline
MP01 – Freeway related signage
The following are Maintained Off Freeway Facilities: All signs and associated support structures, and direction signs attached to the same support structures, that incorporate electronic equipment operated by Project Co.
MP02 – Freeway abutments
The areas within the following boundaries are Maintained Off Freeway Facilities: Upper Boundary Strata Leased Area boundary.
longitudinal section
Boundary A When Road underneath then; outer edge of the footpath or shared use path; otherwise; the greater of 3m past the toe of batter as per A1; or the point at which H becomes greater than 2m as per A2. Boundary B Leased Area boundary.
plan MP03 – Freeway supported by retaining wall.
PART H17
3m past base of retaining wall.
Project Scope & Requirements – Volume 1 of 3
Page 217 of 294
Location
Guideline
MP04 – Entry and exit ramps connecting the Freeway to Roads that are not within the Leased Area and not within the area enclosed by the relevent green line identified in the Road Management Act 204 – Code of Practice – Operational Responsibility for Public Roads – Figure 1.
The areas within the following boundaries are Maintained Off Freeway Facilities: The boundary (across the ramp) nearest to the intersection, being as per the green line in Figure 1; The boundary (across the ramp) furthest from the intersection being the boundary of the Leased Area; and The boundary either side of the ramp being in accordance with the principles depicted in Figure 1
Table Notes :
PART H17
Project Scope & Requirements – Volume 1 of 3
Page 218 of 294
Part H18 Operational Area Operational Area
Description
OP01 – Eastern Freeway
The Eastern Freeway carriageways and ramps identified red.
PART H18
Project Scope & Requirements – Volume 1 of 3
Page 219 of 294
Part H19 Performance Requirements Table H19.1 – Performance Requirements KPI No identified in KPI table of Payment Schedule
Device
Description
Performance Requirement
7
n/a
Emergency notifications
The first emergency notification to the TMCS (including those from Emergency Services, VicRoads or help phones) in relation to a matter must be answered by a person within 30 seconds, 24 hours a day, 7 days a week, in accordance with the PSR ≥95% of the time.
8
Each individual automatic incident detector
Incident detection
Data from each individual automatic incident detection device must be received by the TMCS ≥98% of the time. Performance Points will not be incurred in respect of devices for which Performance Points are simultaneously incurred for the same devices under KPI’s 17,18 or 23
9
Each individual automatic incident detector
Incident detection
System Availability for the Automatic Incident Detection System must be ≥99.0%. Performance Points will not be incurred in respect of devices for which Performance Points are simultaneously incurred for the same devices under KPI’s 17,18 or 23
10
n/a
Incident detection
Incidents in the O&M Area must be detected within 20 seconds of the incident.
11
n/a
Incident response
Response crew must arrive on site no later than 10 minutes after the occurrence of an incident in the O&M Area ≥90% of the time.
PART H19
Project Scope & Requirements – Volume 1 of 3
Page 220 of 294
KPI No identified in KPI table of Payment Schedule
Device
Description
Performance Requirement
12
n/a
Incident clearance for Operational Area
85 % of Incidents in the Operational Area must be cleared and all lanes must be reopened no later than 45 minutes after each HCV Incident; and 20 minutes after each incident other than an HCV Incident.
13
Each individual lane use management sign
LUMS
Each individual lane use management sign must fully display the TMCS requested information ≥99% of the time.
14
Each individual lane use management sign
LUMS
System Availability for the Lane Use Management System must be ≥99.8%.
16
Each freeway variable message sign and each arterial variable message sign
VMS
Each freeway and arterial variable message sign must display the VicRoads traffic data (if properly transmitted by VicRoads) or relevant TMCS information ≥98% of the time.
17
Data from each traffic lane
Real time traffic data system
Traffic data for each individual Lane for the real time traffic data system must be received by the TMCS ≥98% of the time.
18
Data from each traffic lane
Real time traffic data system
System Availability for the real time traffic data system must be ≥99.5%.
19
Data from each traffic lane
Daily traffic data system
For each individual Lane, daily traffic data must be received by the State and VicRoads ≥95% of the time.
20
Data from each traffic lane
Daily traffic data system
System Availability for the daily traffic data system must be ≥98%.
21
Each tunnel information sign
Tunnel information signing system
Each individual sign for the tunnel information signing system must display the TMCS requested information ≥99% of the time.
PART H19
Project Scope & Requirements – Volume 1 of 3
Page 221 of 294
KPI No identified in KPI table of Payment Schedule
Device
Description
Performance Requirement
22
Each tunnel information sign
Tunnel information signing system
System Availability for the tunnel information signing system must be ≥99.5%.
23
Each individual CCTV camera
CCTV system
Images from each individual camera must be received by the FCC operators ≥98% of the time.
24
Each device that emits mobile phone communications to mobile phones
Tunnel mobile telephone system
System Availability for the tunnel mobile telephone system, in respect of which Project Co is responsible under the terms of the Project Agreement, must be ≥98%.
25
Each Emergency Services telephone
Emergency Services telephone system
Each individual Emergency Services telephone must be available for Emergency Services to communicate with the FCC operators ≥99% of the time.
26
Each device that emits radio communications to radio receivers
Tunnel radio rebroadcast system
System Availability for the tunnel radio re-broadcast system must be ≥99%.
27
Each device that emits audio communications to tunnel users
Tunnel public address system
System Availability for the tunnel public address system must be ≥99%.
28
n/a
Data transmission
Project Co must ensure that TMCS data is delivered to and integrated with VicRoads’ management system – STREAMS – to enable the continuous supply of all TMCS data for 99% of the time (except any Device data that is not transmitted to the TMCS due to events which are covered by other KPIs)
29
Each road safety camera site
Road safety camera electrical availability requirements
Individual road safety camera sites must be provided with power ≥99% of the time
PART H19
Project Scope & Requirements – Volume 1 of 3
Page 222 of 294
KPI No identified in KPI table of Payment Schedule
Device
Description
Performance Requirement
Table Notes: System Availability means the value calculated in accordance with the following formula: System Availability =
where: HP = number of hours in reporting period; ND = number of individual Devices; HL = total number of hours lost for all individual Devices in the reporting period (whether simultaneously or otherwise), rounded up to the nearest hour for each Device (e.g. if 1 Device has 20 minutes of unavailability in the reporting period, and a second Device has 1 hour and 15 minutes of unavailability in the reporting period, HL = 3). A Device will be deemed to be unavailable if it is not operating in accordance with the PSR; and GG = any period of time in respect of which Project Co can demonstrate to the State’s reasonable satisfaction that a Device did not need to be operational.
PART H19
Project Scope & Requirements – Volume 1 of 3
Page 223 of 294
Part H20 CityLink Returned Works 1.
2.
Introduction 1.1.1
This Part H20 applies only to the CityLink Returned Works.
1.1.2
Subject to sections 1.1.3 and 1.1.4, nothing in this Part H20 affects the application of the other Parts of the PSR to the CityLink Returned Works (and those other Parts will apply to the CityLink Returned Works).
1.1.3
Subject to section 1.1.4 but notwithstanding any other provision of the Agreement, if there is any inconsistency, ambiguity or discrepancy between this Part H20 and the other Parts of the PSR, this Part H20 will prevail to the extent of the inconsistency, ambiguity or discrepancy (and only in relation to the CityLink Returned Works).
1.1.4
Section 1.1.3 does not in any way limit Project Co’s obligations under this Agreement in relation to the Environmental Requirements.
CityLink Returned Works Requirements 2.1.1
CityLink Returned Works means the physical things and works which Project Co must design, supply, construct, install, produce, commission or complete in accordance with this Agreement within the Adjusted CityLink Leased Area, including (to the extent within the Adjusted CityLink Leased Area): (a)
(b)
2.1.2
PART H21
an additional lane on CityLink outbound between: (i)
Dynon Rd entry ramp and Racecourse Rd exit ramp; and
(ii)
Ramp L entry to Moreland Rd exit ramp;
an additional lane on CityLink inbound between: (i)
Moreland Rd entry ramp to Ramp B; and
(ii)
Ramp M to Dynon Rd exit ramp.
(c)
all adjustments, truncations, reinstatement and improvements to CityLink necessary as a result of the D&C Activities;
(d)
the protection, repair, replacement, reinstatement, alteration and relocation of Utility Infrastructure necessary for, or required as a result of, the performance of the D&C Activities;
(e)
all associated works described in section 5.1.10, 5.1.11, 5.1.12 of Part A as applicable to CityLink;
(f)
the ITS, traffic barriers, street lighting and noise attenuation works to be undertaken by Project Co as described in the CityLink Returned Works Requirements; and
(g)
if elected, Pre-Agreed Modification Number 1.;
(h)
any Modifications to, and rectification of Defects in, such physical things and works.
The CityLink Returned Works must comply with the CityLink Returned Works Requirements.
Project Scope & Requirements – Volume 1 of 3
Page 224 of 294
2.1.3
PART H21
The CityLink Returned Works Requirements are as described in Exhibit G of the Agreement and include a number of references to the CityLink Project Information. For the avoidance of doubt, the CityLink Project Information is Project Information for the purposes of the Agreement.
Project Scope & Requirements – Volume 1 of 3
Page 225 of 294
Part H21 Environment and Urban Design 1.
Environmental Performance Requirements
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 226 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 227 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 228 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 229 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 230 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 231 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 232 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 233 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 234 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 235 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 236 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 237 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 238 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 239 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 240 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 241 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 242 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 243 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 244 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 245 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 246 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 247 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 248 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 249 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 250 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 251 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 252 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 253 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 254 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 255 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 256 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 257 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 258 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 259 of 294
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 260 of 294
2.
Urban Design Principles
No.
Urban Design Principle
1.
Design and integration
1.1
Provide a high quality, well-resolved design outcome; and a memorable, innovative urban design response which is enduring in expression and timeless in nature, for road users, surrounding land users and for Melbourne as a whole:
Project Co
1.1.1
The design is to make a positive contribution to locally affected environments, and to greater Melbourne's cultural identity and reputation for design innovation, liveability and excellence.
Project Co
1.1.2
The whole of the Project is to be well conceived, carefully resolved and finely executed in detail as a design which is innovative, responsive, engaging, environmentally sustainable, functional, and adaptable for future infrastructure needs.
Project Co
1.1.3
All structural, functional and service elements are to be resolved and integrated in a context sensitive manner as part of the urban design solution.
Project Co
1.1.4
Spaces associated with or created by the Project are to be optimised through careful siting of structural elements to facilitate spatial useability and access where appropriate.
Project Co
1.1.5
The design is to ensure particular attention to successful integration and responsiveness to the existing landscape(s), and urban environments, cultural heritage, land use, the character and integrity of key precincts along the alignment, and the overall coherence and identity of the Project.
Project Co
1.1.6
Design of new structures at the Melbourne Citylink Gateway is to enhance the urban design of the precinct and contribute to a redefined and heightened gateway and multi-modal interchange experience.
Project Co
1.1.7
Incorporate sustainable design approaches into the Project as a whole, and to its elements. Consider materials for the design that minimise embodied energy use, and consider whole-of-life energy and water costs for the Project.
Project Co
1.1.8
Protect and enhance public viewlines and vistas where appropriate.
Project Co
1.2
Provide a high quality outcome for residents and adjacent private and public land users and land owners with respect to protection of views and privacy, noise amelioration, avoiding overshadowing, and maintaining access and security through design.
Project Co
1.2.1
A distinctive character and sense of journey for both the freeway and other integrated transport modes is to be created through a holistic landscape, architectural and urban design response to the whole Project including the development of a palette of forms, treatments and materials for all elements:
Project Co
PART H21
Project Scope & Requirements – Volume 1 of 3
Responsibility
Page 261 of 294
No.
Urban Design Principle
Responsibility
1.2.2
Roads, waterways, parklands and necessary bridges and elevated structures (vehicular, pedestrian, cycling, and public transport).
Project Co
1.2.3
Tunnels, tunnel portals and ventilation structures.
Project Co
1.2.4
Noise barriers, retaining walls, fencing and safety barriers.
Project Co
1.2.5
Pedestrian and cycle paths, including all crossings.
Project Co
1.2.6
Earth forming, planting and open space elements.
Project Co
1.2.7
Associated urban design elements including signage, lighting and any furniture.
Project Co
1.3
The form, finishes and siting principles for all road and street furniture, lighting, signage housings and other miscellaneous items are to be established at the concept stage of the design. These should be rationalised to minimise visual clutter, and designed as integral to the urban design concept.
Project Co
1.4
The siting and design of walls and other elements and the choice of materials, colours and surface finishes is to avoid them becoming a target for graffiti. A graffiti management strategy is to be prepared and implemented for the road and the open space network for the life of the Project.
Project Co
1.5
Any works within the Moonee Ponds Creek corridor are to enhance the creek environment for open space, amenity and habitat values, contribute to integration of water catchment management, and to be in accordance with Melbourne Water requirements for flood protection. These works are to be determined in conjunction with the Cities of Melbourne and Moonee Valley.
Project Co
1.6
The architectural, landscape and urban design works are to be designed to ensure an environment which is accessible, inclusive, supports safe behaviour, and is perceived as being safe.
Project Co
2.
Bridges and elevated road structures
2.1
Bridges or elevated road structures are to contribute to an experience of gateway or provide landmark thresholds where they are appropriately located to serve this purpose. They are to be respectful of context and wellresolved in response to existing landmark urban elements, and they include:
Project Co
2.1.1
Melbourne Gateway at Citylink - including existing sculptural, landscaping and sound attenuation elements.
Project Co
2.1.2
Eastern Gateway at Eastern Freeway - including proximate heritage elements such as the Shot Tower.
Project Co
2.1.3
Western Gateway at Footscray Road / Dockland Highway
State
2.1.4
Secondary thresholds and interchanges including the tunnel portals.
Project Co
2.2
Minimise the extent and impact of elevated road structures.
Project Co
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 262 of 294
No.
Urban Design Principle
Responsibility
2.3
All elements of elevated structures, including associated services and lighting, are to be designed to minimise their visual and spatial impact, while achieving high levels of visual, acoustic and spatial amenity for the character of the streets and open spaces they intersect, and to the identity of the Project as a whole.
Project Co
2.4
All bridges and elevated road structures are to be integrated design solutions in terms of their form, elements, proportions and details, having regard to their location and urban context. Structural solutions must integrate visual and spatial architectural and urban design considerations to ensure visually elegant and contextually-appropriate structural outcomes.
Project Co
2.5
The design of areas under elevated structures is to be carefully designed and fully resolved to maximise their usefulness and amenity, particularly for public open space and access to natural light. Ensure uses or activities to be located under or near elevated structures are suitable for such locations having regard to environmental considerations. Carefully site or align piers or support structures to optimise the useability and positive urban qualities of undercroft spaces.
Project Co
2.6
The designs of new road structures in Royal Park or other public open space locations are to ensure that the landscape character of the place is dominant and that visual and physical severance is minimised. The form, scaling, expression, materials, connections, details and finishes of structures must be developed as innovative, sensitive and responsive elements that contribute to the character, identity and positive experience of the parkland, and prepared in conjunction with the managers of that open space.
Project Co
2.7
Ensure there is no additional overlooking of private open space and habitable room windows of residents potentially affected by the Project.
Project Co
2.8
Any new road structures connecting with the Arden-Macaulay urban renewal area are to integrated with the local movement system and be consistent with the Structure Plan and designed in consultation with the City of Melbourne.
Project Co
3.
Tunnels
3.1
The design and visual presence of tunnel portals and structures are to be sensitive to their urban context while making a positive contribution to the road's identity as a whole and to the local environments, through high quality form, expression, scaling, detail and materials.
Project Co
3.2
Tunnel interiors, lighting and surface finishes are to contribute to the urban design quality and memorable experience for users of the East West Link. Tunnel interiors should optimise road safety, driver experience and be easy to maintain and designed to avoid surface staining.
Project Co
4.
Ventilation structures
4.1
Ventilation structures are to be designed to be sensitive responses to their urban context and deliver high quality architecture including form, expression, finishes and detailing.
PART H21
Project Scope & Requirements – Volume 1 of 3
Project Co
Page 263 of 294
No.
Urban Design Principle
Responsibility
4.2
Ventilation structures are to be sensitively sited with due consideration given to the environment and amenity impacts within their immediate and surrounding urban context.
Project Co
4.3
Ventilation structures are to be designed to make a positive contribution through their form, scaling and detail, as innovative responses to the local environment and to the road's identity as a whole.
Project Co
5.
Noise attenuation
5.1
Noise barriers and noise mounds are to be designed as compatible elements with the structures, landform and urban interfaces of their location and urban design concept for Project as a whole.
Project Co
5.2
Overshadowing of residential properties and open spate, waterways and valuable habitat by noise barriers or other noise attenuation structures is to be minimised.
Project Co
5.3
Transparent panels are to be considered in locations near to residential property where noise walls substantially interfere with the aspect or view, or access to daylight.
Project Co
5.4
Design noise barriers to positively address both the road side and community side of barriers.
Project Co
5.5
Design to minimise potential for vandalism to noise attenuation treatments, through materials selection, detail and positioning.
Project Co
6.
Pedestrian and bicycle connections
6.1
New pedestrian and bicycle paths are to maintain and extend current local connectivity, including linking to relocated and new community facilities, open spaces and urban renewal areas.
Project Co
6.2
Maximise opportunities to create and enhance pedestrian and bike paths that provide for local connections and linkages to co-ordinate with the wider Principal Bicycle Network.
Project Co
6.3
Extend and enhance existing at grade pedestrian and bike connections, including along and across Hoddle Street, Alexandra Parade and Moonee Ponds Creek, and identify locations where new connections would be advantageous.
Project Co
6.4
Maximise opportunities to enhance connectivity of the Yarra Bend Trail, Capital City Trail and Moonee Ponds Creek Trail with other existing trails to improve and extend the network.
Project Co
6.5
Improve way finding convenience and legibility of access between and along streets and to key destinations where new road infrastructure will impact on existing connections and at new connections.
Project Co
7.
Public realm, parkland and recreation
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 264 of 294
No.
Urban Design Principle
Responsibility
7.1
Design is to minimise permanent loss of public open space, and offset where feasible.
Project Co
7.2
Design is to minimise the removal of mature trees and remnant vegetation and protect parkland character. At Royal Park, this includes, where practicable, screening of excavated works and structural elements by subtle 'layering' of vegetation, with replanting programmes to conform to the 1984 Royal Park Master Plan. All such works to be designed in collaboration with the City of Melbourne.
Project Co
7.3
Maximise opportunities to create or enhance open space, community and recreation facilities, and to improve accessibility, inclusiveness and general amenity for the community, including:
Project Co
7.3.1
Merri Creek open space link in the vicinity of the new road structures.
Project Co
7.3.2
The connection from Yarra Bend Park to Alexandra Parade by the proposed relocation of Groom Street/Trenerry Crescent Overpass.
Project Co
7.3.3
Reinstatement and enhancement of the landscape character of Royal Park and Moonee Ponds Creek Linear Park.
Project Co
7.3.4
Playing fields, recreation spaces, wetlands and associated areas of Ross Straw Field and Moonee Ponds Creek Linear Park facilities.
Project Co
7.3.5
The recreation facilities, community centre, community gardens and associated areas of Debney's Park.
State
7.3.6
The edges of Ormond Park, Holbrook Reserve and Moonee Valley Racecourse.
Project Co
7.3.7
Moonee Ponds Creek as an urban parkland, waterway and walking/cycling and habitat corridor between Royal Park and Docklands, through the ArdenMacaulay and E-Gate urban renewal precincts and north between Racecourse Road and Ormond Road within the East West Link alignment.
Project Co (except where not relevant to Stage One)
8.
Planting and vegetation
8.1
The design is to ensure a net enhancement of the landscape amenity and biodiversity of areas along the corridor and nearby parklands affected by the Project.
Project Co
8.2
Design is to achieve a substantial net increase in tree canopy and contribution to the urban landscape across the corridor. Plant selection, design and layout are to:
Project Co
8.2.1
Present a coordinated colour, form and texture palette which is integral to the urban design concept.
Project Co
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 265 of 294
No.
Urban Design Principle
Responsibility
8.2.2
Be well-implemented with appropriately selected species that ensure a low maintenance, thriving and enduring outcome. Replacement trees for avenue trees removed to accommodate new road alignments including along Flemington Road must, where practicable, be of the same taxon and on an alignment and at a spacing as close as possible to the trees removed.
Project Co
8.2.3
Maximise performance, long term viability and contribution to the landscape character, amenity and design concept as a whole by considering local conditions and existing character, microclimates and uses.
Project Co
8.2.4
Maximise use of locally indigenous and native species, where viable in the context of microclimate and character.
Project Co
8.2.5
Where planting is proposed, employ a process for maintenance to ensure net increase in tree canopy is met.
Project Co
9.
Materials and finishes
9.1
The detailed design of buildings and road structures is to integrate:
Project Co
9.2
Materials and details that will allow reasonable ease in repair, replacement or recoating and maintain design character, expression and features to age gracefully.
Project Co
9.3
Colour and texture which is integral to any materials, not the result of applied finishes, or, if applied, is demonstrably highly durable and able to be repaired with ease, and appropriate to maintaining the longevity of urban design concept.
Project Co
9.3.1
Provide accessibility and functionality for ease of maintenance.
Project Co
10.
Lighting
10.1
Lighting and lighting structures, poles and masts are to be designed as an integral element of the urban design concept for the whole Project to ensure functionality and efficiency are achieved.
Project Co
10.2
Consider special lighting for major infrastructure, interchanges, gateways, movement corridors and 'moments', to contribute to way-finding and legibility, and the creation of memorable experiences for all users.
Project Co
10.3
Design is to provide lighting for pedestrians and cyclists to the parkland, places and paths created around and under the new road infrastructure, where appropriate.
Project Co
10.4
Design is to use highly directional lighting wherever possible to avoid lighting spill into surrounding neighbourhoods, parks and urban environments.
Project Co
10.5
Use energy efficient, vandal proof light fixtures that offer ease of access for maintenance.
Project Co
11.
Water Sensitive Road Design
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 266 of 294
No.
Urban Design Principle
Responsibility
11.1
Integrate Water Sensitive Road Design into urban design solutions to achieve sustainable water and resource management.
Project Co
11.2
Employ best practice treatment of water run-off through swales and biofiltrations systems as appropriate.
Project Co
11.3
Include water harvesting for roadside landscape and •open space irrigation, wherever possible.
Project Co
11.4
Consider measures to mitigate the urban heat island effect through effective urban design.
Project Co
11.5
Maximise permeability opportunities within road and associated hard landscape areas.
Project Co
12.
Integrated public artworks
12.1
Undertake a programme to incorporate public artworks at suitable locations across the Project that are responsive to the character of the urban setting, and which, where appropriate, are integrated into the wider design as functional elements of the overall design philosophy.
State
12.2
Institute a public art programme to ensure that the public artworks are considered at an early stage of the design process with adequate funding. Opportunities for artistic expression should be an integrated element of the overall design and the Project's infrastructure. The sequencing of 'landmark' artworks should be carefully considered to relate to 'choice points' where the freeway is exited.
State
12.3
Consider the incorporation of a series of smaller public artworks associated with the shared user paths and other movement routes.
State
12.4
Where public artworks are proposed, employ a process for selection, commissioning, implementation and maintenance that ensures the works are of a high quality, appropriate to location, and will endure.
State
12.5
Involve the local communities to contribute to the design and selection of appropriate local art through one or more 'artists in residence' or similar programs.
State
PART H21
Project Scope & Requirements – Volume 1 of 3
Page 267 of 294
Part I
PART I1
PRE AGREED MODIFICATIONS AND COMMUNITY ENHANCEMENTS
Project Scope & Requirements – Volume 1 of 3
Page 268 of 294
Part I1 1.
Pre-Agreed Modifications (PAM’s)
PAM #1: CityLink additional north bound lane option 1.1.1
PAM #1 involves: (a)
an extra lane northbound on CityLink from the Ramp A / Ramp W diverge to the Moreland Road exit ramp as identified in Table I1.1;
(b)
modifications to: (i)
the Moreland Road entry ramp to cater for: (A)additional lane southbound, north of Moreland Road; and (B)freeway ramp signals;
(ii)
the Moreland Road exit ramp to cater for the additional lane to the south and two lanes to the north;
(iii)
the Flemington Road entry ramp: (A)to cater for the additional northbound lane; and (B)to incorporate freeway ramp signals;
(iv)
the Dynon Road entry ramp to cater for: (A)an additional northbound lane south of Dynon Road; and (B)freeway ramp signals;
(v)
PART I1
lane widths as identified in Table I1.2.
(c)
freeway ramp metering signals as identified in Table I1.3.
(d)
includes VicRoads RC1, RC2 and RC3 signs;
(e)
design volumes as identified in Table I1.4; and
(f)
variable speed limit signs for traffic entering CityLink from Ramp Q, Ramp X, Ramp V and Ramp T.
Project Scope & Requirements – Volume 1 of 3
Page 269 of 294
Table I1.1 – Extra lane along CityLink Location
PART I1
Project Scope & Requirements – Volume 1 of 3
Page 270 of 294
Table I1.2 - Lane cross sectional dimensions
Number / width of traffic lanes
Right emergency stopping lane / shoulder
(9)
Left emergency stopping lane / shoulder
(9)
E
E
E
Dynon Road entry ramp to Racecourse Road exit ramp
0.5
4@ 3.35
0.5
Racecourse Road exit ramp to Flemington Road entry ramp nose
0.5
4@ 3.35
0.5
Flemington Road entry ramp to Ramp L entry ramp
1.0
5@ 3.35
1.0
6@ 3.35
1.0
(1)
E
E
E
Location
CityLink - Northbound South of Dynon Road entry ramp
(1)
Ramp L entry to Moreland Road exit ramp
1.0
North of Moreland Road exit ramp
(1)
(1)
Table Notes: E - Existing (1)
may be reduced to 0.5m under existing bridges to cater for the structural element of the bridge or for barrier protection for the bridge. Table I1.3 – Additional ramp metering signals and design hour volumes Rampr (a) e v i Ramp Q s e Ramp X d Ramp V Ramp T
PART I1
Design Volumes
Lanes at Stop Line
Communications connected to
1,200
2
VicRoads and CityLink
1,500
4
VicRoads and CityLink
600
2
VicRoads and CityLink
1,200
2
VicRoads and CityLink
Project Scope & Requirements – Volume 1 of 3
Page 271 of 294
Table I1.4 - Revised design volumes
Location
PART I1
(1)
Two way daily design traffic volumes AAWDT 2031
CityLink south of Moreland Road
250,000
CityLink south of Flemington Road
130,000
CityLink south of Racecourse Road
160,000
Project Scope & Requirements – Volume 1 of 3
Page 272 of 294
2.
PAM #2: VicTrack Communication Conduits 2.1.1
A communication sub system must be designed, constructed and maintained for the sole use of the VicTrack. The VicTrack communication sub-system must: (a)
meet the reasonable requirements of VicTrack;
(b)
consist of: (i)
a communication conduit 100mm in diameter which: (A)connects the access points together; (B)is located in a straight line between access points or is a set distance from a continuous roadside element with a minimum radius of 800m; and (C)is a fully self-integrated sub system not connected to any other power or communication sub system;
(ii)
access points: (A)located: on the Upfield rail reservation; on the Clifton Hill rail reservation; adjacent to the Freeway Control Centre; and at no more than 380m centres; (B)constructed using: P8 pits with concrete locking lids and marker posts outside the tunnel; and pits and markers agreed with the State inside the tunnel; and
(c)
PART I1
be a fully self-integrated sub system not connected to any other power or communication sub system.
Project Scope & Requirements – Volume 1 of 3
Page 273 of 294
3.
PAM #3: Reinstatement and Enhancements of “Old Grass Hockey Fields” Royal Park 3.1.1
General (a)
Project Co is required to reinstate and enhance this area with the provision of a purpose designed and built multi purpose sports and recreational area. The area is required to provide sporting facilities for Baseball, Soccer, Touch Sports and Cricket and be available for use in both the summer and winter seasons.
(b)
The area will generally provide two baseball diamonds, two synthetic wicket cricket ovals, two full size soccer pitches and approximately three additional half size soccer pitches. A pavilion is to be constructed to support and provide toilet/change facilities for all participants.
(c)
The design and construction of this area is to be co-ordinated in consultation with the City of Melbourne as Returned Works.
(d)
Without limiting the obligations of the State Project Documents, it will be Project Co's responsibility at its cost:
(e)
3.1.2
PART I1
(i)
in consultation with City of Melbourne and the service authorities, to locate all existing services to this area and agree to discharge/connection points or source points for all services including electricity, gas, water and sewer; and
(ii)
all necessary Approvals for the carrying out of the works, not including planning approval.
All materials supplied and all work performed must be to the usual requirements of City of Melbourne and comply with the requirements of any authority having jurisdiction over any aspects of the work. The relevant Australian Standards must be complied with.
Requirements (a)
The construction zone to facilitate this work will need to be expanded to include the necessary areas to the East and West of the existing designated construction zone.
(b)
The work area within the current construction zone will need to be backfilled and compacted to an appropriate level to suit the future proposed work.
(c)
The new areas (East & West) to be expanded into for the enhancement works will require initial preparation including; (i)
kill the existing grass cover;
(ii)
remove existing turf and dispose of all material off site if appropriate. Consideration will need to be given to the potential contamination of soil and the requirement for managing the disposal or retention on site. Contamination reports are not available for this area;
Project Scope & Requirements – Volume 1 of 3
Page 274 of 294
(d)
PART I1
(iii)
removal of any items that currently exist in the site that may impact works;
(iv)
locate all existing underground services in and near the site. Maintain or remove ensuring all existing current/live services are retained;
(v)
secure the safety of the entire site during the carrying out of the works; and
(vi)
spray the whole site and immediate surrounds with Glyphosate herbicide (or equivalent).
The reconstruction/enhancement work will include; (i)
reshaping the site according to the concept drawing involving cutting and filling of the designated areas to produce a ridge shape of 1 in 200 and match into the surrounds to the new design;
(ii)
laser grading until surface is smooth and consolidated;
(iii)
shaping surrounds to match the new surface;
(iv)
installing a network of subsurface drainage;
(v)
installing field lighting;
(vi)
installing automatic irrigation system;
(vii)
installing two concrete cricket pitches and synthetic pitch covers;
(viii)
installing 300mm (solid) layer of suitable sand to the surface;
(ix)
grassing the surface of the sportsfield surface using Kikuyu grass sod;
(x)
provision of two baseball diamonds and associated fencing;
(xi)
provision of a sports pavilion and associated fit-out/infrastructure and services;
(xii)
maintenance of the sportsfields for a minimum of 13 weeks from grassing prior to Handback;
(xiii)
expansion of the adjacent car park by up to 30 bays;
(xiv)
no fencing, other than sports netting to reduce the risk of sports balls reaching the adjacent tram tracks and roads;
(xv)
provisions to discourage unauthorised vehicles from accessing the playing fields; and
(xvi)
authorised and secured vehicle access points.
Project Scope & Requirements – Volume 1 of 3
Page 275 of 294
4.
5.
PAM #4: Eastern Freeway shared use path, Merri Creek to Chandler Highway 4.1.1
The scope of these works are described in section 11 of Part I2.
4.1.2
The bridge across the Yarra River will be one of the Maintained Off-Freeway Facilities
PAM #5: Melbourne Zoo and SNHC Carpark 5.1.1
6.
PAM #6: Truro Street path upgrade 6.1.1
PART I1
The scope of these works are described in section 13 of Part I2
The scope of these works are described in section 12 of Part I2
Project Scope & Requirements – Volume 1 of 3
Page 276 of 294
7.
PAM #7: Eastern Freeway shared use overpass, east of Clifton Hill rail line 7.1.1
PAM #7 includes the design, construction and maintenance of a shared use bridge over the Eastern Freeway / East West Link generally in accordance with the drawings identified in TableI1.4 and as clarified in EWC-145 in Part K5, Table K5.3.
7.1.2
The bridge must; (a)
be a two span steel structure with a pier in the median of the East West Link; and
(b)
link, via shared use paths, to adjacent roads and/or paths.
Table I1.4 Drawings
Drawings EWT-ECS2-SKT-RG-2301_S3
EWT-EGSMS-DRG-BR-4022_B
EWT-ECS2-SKT-RG-3001_S2
EWT-EGSMS-DRG-BR-4046_A
EWT-EGSMS-DRG-BR-4001_B
EWT-EGSMS-DRG-BR-4041_A
EWT-EGSMS-DRG-BR-4011_A
EWT-EGSMS-DRG-BR-4051_B
EWT-EGSMS-DRG-BR-4021_A
EWT-EGSMS-DRG-BR-4052_A Shared Used Overpass – Main Span Member Sizes
EWT-ECS2-SKT-RG-3001_S1
PART I1
Project Scope & Requirements – Volume 1 of 3
Page 277 of 294
(i)
PART I1
Project Scope & Requirements – Volume 1 of 3
Page 278 of 294
8.
9.
PAM #8: Eastern Freeway shared use path, Ramp G to connect with PAM #4 8.1.1
The scope of these works are described in section 14 of Part I2
8.1.2
The bridge across Merri Creek will be one of the Maintained Off-Freeway Facilities
PAM #9: Shared use path, Moonee Ponds Creek trail to Capital City Trail through Ross Straw fields. 9.1.1
PAM#9 includes the design and constructions of a new stand-alone elevated shared use path connection from the Moonee Ponds Creek trail near Travancore Park across CityLink to the north of Ross Straw Field generally in accordance with Table I1.5 and as clarified in EWC-143 in Table K5.3 of Part K5.
9.1.2
The bridge across CityLink will be one of the Maintained Off-Freeway Facilities.
9.1.3
Table I1.5 Drawings
Drawings EWT-WCRAL100-DRG-SP-2001_P1 EWT-WCRAL100-DRG-SP-3001_P1 EWT-WC-A-BR-900-DRG-UD-2901-P1 EWT-WC-A-BR-900-DRG-UD-2902-P1 EWT-WC-A-BR-900-DRG-UD-2903-P1 EWT-WC-A-BR-900-DRG-UD-2904-P1 EWT-WC-A-BR-900-DRG-UD-2905-P1 EWT-WC-A-BR-900-DRG-UD-2906-P1 EWT-WCLUD300-DRG-LA-2005 [P1] EWT-EGSMS-DRG-BR-6001_P1 EWT-EGSMS-DRG-BR-6002_P1 EWT-EGSMS-DRG-BR-6003_P1 EWT-EGSMS-DRG-BR-6021_P1 EWT-EGSMS-DRG-BR-6022_P1 EWT-EGSMS-DRG-BR-6023_P1
PART I1
Project Scope & Requirements – Volume 1 of 3
Page 279 of 294
Part I2 0.
Community Enhancements
General
0.0.0 The Community Enhancements includes: 0.0.1 the works set out in sections 1 to 14 below; and 0.0.2 where relevant, the works required by the Project Requirements and Project Scope including as described in the Urban Design Report (Attachment 4 of Table K5.1 of Part K5) and the Communications and Community Engagement Strategy (Attachment 1 of Table K12.1 of Part K12).
PART I2
Project Scope & Requirements – Volume 1 of 3
Page 280 of 294
1.
Community Enhancement #1 – Trenerry Crescent 1.1.1
Community Enhancement #1 includes: (a)
(b) 1.1.2
PART I2
(i)
providing 1.5m wide cycle lanes in each direction;
(ii)
providing one 3.5m traffic lane in each direction; and
(iii)
maintaining the existing footpath width.
the design and installation of associated urban design and landscaping elements.
Reference Drawings: (a)
1.1.3
upgrading, and where necessary widening, Trenerry Crescent between Gray Street and the south of the Eastern Freeway by:
EWT-ECLUD200-DRG-LA-2023
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 281 of 294
2.
Community Enhancement #2 – Royal Park shared use path connectivity 2.1.1
2.1.2
2.1.3
PART I2
Community Enhancement #2 includes: (a)
upgrade of the existing path parallel to Route 55 tram line between Elliott Avenue and Zoo car park to resurface to type PV03;
(b)
upgrade of the existing path parallel to and north of Elliott Avenue between Brens Drive and the Route 55 tram line where it intersects with Elliott Avenue to resurface to type PV03;
(c)
the design and installation of associated urban design and landscaping elements; and
(d)
designing and installing an integrated signing scheme for path users.
Reference Drawings (a)
EWT-WCLUD100-DRG-LA-2007 S2
(b)
EWT-WCLUD200-DRG-LA-2009 S3
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 282 of 294
3.
Community Enhancement #3 – Moonee Ponds Creek Trail enhancements 3.1.1
3.1.2
3.1.3
PART I2
Community Enhancement #3 includes: (a)
the design and construction of a duplicate pedestrian bridge across the Moonee Ponds creek east of Ramp R and the existing pedestrian bridge;
(b)
the design and construction of a new ramp connecting the new and existing bridge, identified in section 4.1.1, to Union Street;
(c)
the design and installation of associated urban design and landscaping elements; and
(d)
designing and installing an integrated signing scheme for path users.
Reference Drawings (a)
EWT- WCLUD300-DRG-LA-2024;
(b)
EWT- WCLUD300-DRG-LA-2004 S2
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 283 of 294
4.
Community Enhancement #4 – Reggio Calabria Club car park and field upgrades 4.1.1
Community Enhancement #4 includes: (a)
4.1.2
PART I2
(i)
flood lighting; and
(ii)
team shelters;
(b)
the design and construction of upgraded and expanded parking facilities including landscaping; and
(c)
relocation of chapel facilities.
Reference Drawings (a)
4.1.3
the design and construction of an upgraded turf soccer pitch including:
EWT- WCLUD300-DRG-LA-2024
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 284 of 294
5.
Community Enhancement #5 – Moonee Ponds Creek Trail enhanced connectivity and enhancements to Ormond Park and Holbrook Reserve 5.1.1
5.1.2
5.1.3
PART I2
Community Enhancement #5 includes: (a)
the design and construction of a new shared use path bridge over the Moonee Ponds Creek and Moonee Ponds Creek Trail to connect Holbrook Reserve and Ormond Park west of CityLink;
(b)
the design and construction of a new shared use path bridge over the Moonee Ponds Creek to the south west of Holebrook Reserve to connect Holbrook Reserve with the Moonee Ponds Creek Trail;
(c)
the design and construction of paths through and around HolebrookReserve, 2m wide;
(d)
upgrading the shared use path around Holbrook Reserve under CityLink, at the northern and southern ends of Holbrook Reserve;
(e)
the design and installation of associated urban design and landscaping elements.
(f)
designing and installing an integrated signing scheme for path users;
(g)
reconfiguration and upgrade the sports field in Holbrook Reserve to a standard for seniors cricket; and
(h)
upgrading the Ormond Park playground.
Reference Drawings (a)
EWT- EWT-WCLUD300-DRG-LA-2023 S3; and
(b)
EWT- EWT-WCLUD300-DRG-LA-2024
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 285 of 294
6.
Community Enhancement #6 – Moonee Ponds Creek Trail enhanced connectivity and enhancements – Travencore Area. 6.1.1
6.1.2
6.1.3
PART I2
Community Enhancement #6 includes: (a)
the design and construction of paths on the western side of the Moonee Ponds Creek between Ormond Road and Delhi Court;
(b)
the design and construction of a children’s play area;
(c)
the design and construction of a community garden;
(d)
the design and installation of associated urban design and landscaping elements;
(e)
construction to the existing paths on the western side of the Moonee Ponds Creek between Ormond Road and Delhi Court.
Reference Drawings (a)
EWT-WCLUD300-DRG-LA-2024;
(b)
EWT-WCLUD300-DRG-LA-2025;
(c)
EWT-WCLUD-300-DRG-LA-2004 S2; and
(d)
EWT-WCLUD-300-DRG-LA-2005 S2
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 286 of 294
7.
Community Enhancement #7 – Flemington Bridge Station access and landscaping enhancements 7.1.1
Community Enhancement #7 includes: (a)
(b)
7.1.2
7.1.3
PART I2
the design and installation or upgrade of paths connecting: (i)
Mount Alexander Road path with the Flemington Bridge rail station;
(ii)
the “circular bridge” to the path in section 8.1.1;
(iii)
Mount Alexander Road path with the Moonee Ponds Creek Trail;
(iv)
the Capital City Trail to Flemington Bridge rail station; and
(v)
the Moonne Ponds Creek Trail with Flemington Bridge rail station, south of the rail station.
the design and installation of bridges connecting; (i)
Debney Park with the Capital City Trail; and
(ii)
the Moonee Ponds Creek trail north of Mount Alexander Road to Flemington Bridge rail station
(c)
the design and installation of an integrated signing scheme for path users; and
(d)
the design and installation of associated urban design and landscaping elements.
Reference Drawings (a)
EWT-WCLUD200-DRG-LA-4001
(b)
EWT-WCLUD200-DRG-LA-2084;
(c)
EWT-WCLUD200-DRG-LA-2085;
(d)
EWT-WCLUD200-DRG-LA-2086;
(e)
EWT-WCLUD200-DRG-LA-2087;
(f)
EWT-WCLUD200-DRG-LA-2008 S2.
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 287 of 294
8.
Community Enhancement #8 – Debney’s Park Redevelopment 8.1.1
Community Enhancement #8 includes: (a)
8.1.2
8.1.3
PART I2
the design and construction of a new community facilities including; (i)
Community Centre;
(ii)
reinstatement of parking;
(iii)
multipurpose courts;
(iv)
sporting fields;
(v)
paths;
(vi)
play areas;
(vii)
community gardens; and
(viii)
the design and installation of associated urban design and landscaping elements.
Reference drawings: (a)
EWT-WCLUD200-DRG-LA-2008
(b)
EWT-WCLUD200-DRG-LA-2084
(c)
EWT-WCLUD500-SKT-LA-2210
(d)
EWT-WCLUD200-SKT-LA-2211
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 288 of 294
9.
Community Enhancement #9 – Indigenous Meeting Place 9.1.1
9.1.2
PART I2
Community Enhancement #9 includes: (a)
community consultation required to design and construct an indigenous meeting place near the confluence of the Merri Creek and the Yarra Rivers; and
(b)
the design and construction of the indigenous meeting place including interpretative signing, and associated landscaping.
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 289 of 294
10.
Community Enhancement #10 – Urban Camp Sustainability Initiatives 10.1.1
10.1.2
PART I2
Community Enhancement #10 includes the upgrading of the Urban Camp located on Brens Drive by; (a)
designing and installing double glazing to all windows;
(b)
design and install air conditioning;
(c)
design and install security shutters to all windows;
(d)
designing and installing a 10kW grid connected solar panel system;
(e)
installing rainwater tanks, totally 20,000 litre capacity with associated pipes and taps to allow easy watering of adjacent gardens;
(f)
installing recycled plastic seating; and
(g)
installing a food waste compactor.
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 290 of 294
11.
Community Enhancement #11 – Eastern Freeway shared use path, Merri Creek to Chandler Highway 11.1.1
If directed by the State pursuant to clause 33.12 of the Project Agreement, Community Enhancement #11 includes: (a)
11.1.2
11.1.3
PART I2
the design and construction of a new shared use path, type PV02a (modified), with saw cut joints and overlapping reinforced, between the Main Yarra Trail, north of Chandler Highway, and the Main Yarra Trail at the Eastern Freeway bridge over the Merri Creek including; (i)
a new shared use path bridge across the Yarra River adjacent to the Eastern Freeway; and
(ii)
signing along and at the intersecting paths.
Reference Drawings (a)
EWT-EC200-SKT-SP-0106_B
(b)
EWT-EC200-SKT-SP-2006_A
(c)
EWT-EC200-SKT-SP-2007_A
(d)
EWT-EC200-SKT-SP-3006_A
(e)
EWT-EC200-SKT-SP-3007 A_
(f)
EWT-EGSMS-DRG-BR-3001_S1
(g)
EWT-EGSMS-DRG-BR-3021_S1
(h)
EWT-EGSMS-DRG-BR-3081_S1
(i)
EWT-EGSMS-DRG-BR-3082_S1
(j)
EWT-EGSMS-DRG-BR-3083_S1
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 291 of 294
12.
Community Enhancement #12 – Truro Street path upgrade 12.1.1
12.1.2
12.1.3
PART I2
If directed by the State pursuant to clause 33.12 of the Project Agreement, Community Enhancement #12 includes: (a)
the design and construction of a new path connecting across Hoddle Street, along Truro Street, under the Upfield rail line and then to Lulies Street;
(b)
the design and installation of associated urban design and landscaping elements.
Reference Drawings (a)
EWT-ECLUD200-DRG-LA-2054-S2
(b)
EWT-ECLUD200-DRG-LA-4005-S2
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 292 of 294
13.
Community Enhancement #13 – Melbourne Zoo & SNHC car park 13.1.1
13.1.2
13.1.3
PART I2
If directed by the State pursuant to clause 33.12 of the Project Agreement, Community Enhancement #13 includes: (a)
the upgrading of the Project Co staff construction car park in the triangle of land between the SHNC, tram route 55 and the Upfield rail line to a permanent car park, including associated landscaping;
(b)
limiting the use of the carpark during the D&C Phase to vehicles with the GMV of 3 tonne;
(c)
the upgrading of the access road through the zoo car park to a permanent arrangement;
(d)
upgrading the tram crossing, over tram route 55, to a permanent arrangement to meet PTV usual requirements; and
(e)
upgrading the shared use path on the north side of the new car park to a permanent arrangement, including the crossing of the tram track.
Reference Drawings (a)
EWT-ECLUD100-SKT-LA-2213 S2
(b)
EWT-ECLUD100-SKT-LA-2214 S2
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 293 of 294
14.
Community Enhancement #14 – Eastern Freeway shared use path, Ramp G to connect with PAM#4/Community Enhancement#11 14.1.1
If directed by the State pursuant to clause 33.12 of the Project Agreement, Community Enhancement #14 includes: (a)
14.1.2
14.1.3
PART I2
the design and construction of a new shared use path connecting the Community Enhancement #11 shared use path with the Ramp G shared use path and PAM#7, including a new single span shared use path bridge over the Merri Creek and Trenerry Crescent.
Reference Drawings (a)
EWT-EC200-SKT-SP-0106 Rev B;
(b)
EWT-EC200-SKT-SP-2006 Rev A;
(c)
EWT-EC200-SKT-SP-3006 Rev A;
(d)
EWT-EC-A-BR-900-DRG-UD-2951 Rev P1;
(e)
EWT-ECLUD200-DRG-LA-2019;
(f)
EWT-EGSMS-DRG-BR-5001 Rev A; and
(g)
EWT-EGSMS-DRG-BR-5081 Rev A.
The D&C Cost for this Community Enhancement is $[not disclosed – could disadvantage parties in future projects].
Project Scope & Requirements – Volume 1 of 3
Page 294 of 294
