• Permanent structural components – 100 years
• Inaccessible drainage components – 100 years
• Accessible drainage that is replaceable – 50 years
• Jet fan/major overhead equipment – 100 years
• Temporary structural components for support – 5 years
• Fans – 25 years
Chapter 8: Tunnel design requirements
• Luminaries housing and supports – 25 years
• Cabling – 20 years
• ITS hardware – 15 years unless otherwise specified
• ITS software – 5 years
• Other electrics – 15 years
• Pumps – 10 years
• Wall panels, doors and architectural components – 40 years
• Asphalt surfacing (if provided) – 20 years
8.3 Review of drawings and scheme documents
The drawings and scheme documents are to be reviewed and accepted for safety, durability, future performance, constructability and maintenance by Transport and Main Roads officers in accordance with design management (generally reflecting a 15%, 85% and final design stages) and any
permission to use (PTU)) requirements of the contract. Handover Reports for Tunnels
a) The following reports shall be submitted:
• RPEQ certified “As constructed” drawings signed and dated by the Administrator
• Design Report
• Construction Handover Report
• Fire and Life Safety Report (minimum requirement is a copy of submission to Queensland Fire and Rescue Service (QFRS)
• Operation, Inspection and Maintenance Manual
• Incident Management and Recovery Manual
• Level 2 (and Level 3 if required) Tunnel Inspection Report
b) All reports and manuals shall be submitted and accepted by Transport and Main Roads in accordance with the contract prior to opening the facility to use. All procedures/trials/
simulations/tests/training are to be satisfactorily completed prior to opening the facility to use.
8.3.1 “As constructed” drawings
a) The Contractor or Alliance shall provide “As Constructed” drawings, stamped, certified and dated by an RPEQ engineer experienced in the relevant engineering discipline (geotechnical, structural, civil, electrical and so on). Where tunnel schemes are constructed in accordance with the original drawings and specifications issued for construction, the Contractor/Alliance shall provide the original documents, stamped, certified and dated by the RPEQ engineers as a conformance record:
• “As constructed” drawings shall certified by an RPEQ
• An RPEQ shall certify all design changes and include into “ As constructed” drawings
• The Administrator must have documentation to prove “As constructed” details are true and correct, and shall sign the plans accordingly.
Chapter 8: Tunnel design requirements
b) “As constructed” drawings shall contain, but not be limited to:
• Foundation details
• Variations/modifications during construction
• Works constructed outside tolerance
• Updated geotechnical reports, based on actual profile as determined during excavation
• Location of all rock anchors, including a statement if the anchors are short-term or long- term
• Service/Public Utility Plant (PUP) locations (and relocations).
8.3.2 Design report
a) A Design Report shall be prepared and provide details including, but not limited to:
• Transport and Main Roads publication design criteria/codes used, including date of publications and (any) amendments
• Date of referenced Transport and Main Roads Design Criteria for Bridges and Other Structures (Date of this document stated on the first page of this attachment)
• Other referenced documents
• Design criteria adopted, including those from other jurisdictions/regulatory authorities/ stakeholders
• The design methodology, durability, serviceability and ultimate loads, together with a statement of the design life for each structure and each component category (drainage, signs, metalwork, mechanical, ITS, asphalt, architectural components and so on)
• Controls/limits/restrictions/assumptions
• Construction methodology for the design developed
• Durability and Robustness
• “Safety in Design” considerations for construction, inspection, maintenance and operation.
• Achievement of functionality
• Achievement of Level Of Service (LOS)
• Assumptions, departures, Extended Design Domain (EDD).
b) The report shall demonstrate compliance with the Design Brief. Any proposed
departures/relaxations/ exemptions from the Design Brief shall be discussed in terms of safety, durability, future performance, constructability, operations, maintenance and whole-of- life cost considerations. Any proposed departures/relaxations/exemptions shall be submitted to Transport and Main Roads Deputy Chief Engineer (Structures) for consideration in accordance with the contract. The Design Report shall be certified by the RPEQ responsible for each component of the design.
c) The final Design Report shall be submitted as part of the final scheme submission for Transport and Main Roads acceptance. For Alliance/Early Contractor Involvement (ECI)/
Chapter 8: Tunnel design requirements
Design and Construct type projects, the Design Report shall be accepted by the department prior to construction commencing.
8.3.3 Construction handover report
A Construction Handover Report shall include:
• Safety in Design Report updated for construction
• Details of proprietary products
• Commissioning records - fire tests, ventilation validation, electrical supply validation, lighting validation, drainage validation and system integration
• Casting yard records
• Material test records
8.3.4 Fire and life safety report
Minimum requirement is a copy of submission to the QFRS. Operation, Inspection and Maintenance Manual
a) An Operation, Inspection and Maintenance Manual shall be prepared as a part of the designer's Safety in Design obligations under the relevant act and regulations. The Manual relates to in-service inspection, maintenance and operation of the bridge and/or structure. b) The Operation, Inspection and Maintenance Manual shall include but not be limited to:
• Operational information on all structures and equipment (mechanical, electrical, ITS, and so on)
• Inspection frequency (For typical bridges, this will be in accordance with the Transport and Main Roads Bridge Inspection Manual. For special/non-routine design, the frequency needs to be developed.)
• Operational requirements
• Inspection frequency (For tunnel structures special/non-routine design, the frequency will need to be developed.)
• Details of inspection access requirements (including any confined space access requirements)
• Design life of all components and sub-components. For any component or sub-component that has a design life less than the specified design life of the structure, details for
replacement of the (sub-) component shall be provided.
• Routine maintenance schedule, including cleaning, wash down, failed light replacement, incident response systems testing, and so on
• Scheduled maintenance program, incorporating procedures for maintenance including replacement schedules. For paint systems, the procedure shall be suitable for repainting by roller or brush without abrasive blasting to bare metal. The recoat system shall be suitable for over-coating the previously applied system.
Chapter 8: Tunnel design requirements
• Details of how routine and schedules maintenance will be undertaken
• Special maintenance.
8.3.5 Incident management and recovery manual
An Incident Management and Recovery Manual shall be prepared and shall include, but not be limited to: • Vehicle breakdown • Damage-only incident • Debris on road • Fire • Injury incident • Spills • Load shedding • Over-height vehicles
• External electrical supply failure
• Water on pavement
• Flooding
• Explosion and release of noxious liquid or gas
• Incident management training (including any in-tunnel incident trials/simulations/tests).
8.3.6 Level 2 (and Level 3) inspection of tunnel
a) A Level 2 (and Level 3 if required) inspection shall be carried out by a qualified inspector prior to opening of the facility to use in accordance with the Transport and Main Roads Bridge Inspection Manual and the results provided to the department for entering into Transport and Main Roads Bridge Information System.
b) Structure and Design inventory verification forms shall be completed.
8.3.7 Learnings
The projects shall identify in the documentation any learnings for possible application to future projects.