Ms MacTiernan questions the Minister for Transport regarding the Narrows Bridge duplication project's completion date, contract variations, and final costs. The Minister provides updates on the project timeline, approved variations, and estimated total cost.

AnsweredQoN 124Legislative Assembly
Asked
9 August 2000
Portfolio
Transport

QuestionView source ↗

124. Ms MacTIERNAN to the Minister representing the Minister for Transport:
(1) Will the Minister advise the expected completion date for the Narrows Bridge duplication?
(2) Will the Minister advise whether the contractor has sought any variations to the contract, and if yes, will the Minister advise what variations have been approved by Main Roads?
(3) What is the estimated final cost of -
(a) the Leighton contract; and
(b) the total project?

AnswerView source ↗

Answered
14 November 2000
Response time
97 days
The Minister Replied:
(1) The project completion date is late April 2001, however the new bridge is expected to be open to traffic in February 2001.
(2) To date the current value of approved variations, including variations initiated by Main Roads, totals $152 606 and comprises:
- An unconditional undertaking for material stored off site ($10 914).
- Installation of additional settlement gauges ($18 240).
- Provision of two additional monitoring piles ($18 200).
- Supply and installation of additional granite pilasters ($12 142)
- Design of different lane allocations on Mounts Bay Road Ramp ($7 200).
- Design of extension of northern roadworks ($30 000).
- Design of southern roadworks tie in ($23 400).
- Provision of additional settlement monitoring points ($630).
- Revised details for shared path bridge balustrade ($10 032); and
- Emergency repairs to the expansion joint on the existing Bridge ($21 848).
(3) (a) The final cost of the Leighton contract is subject to negotiation with the contractor following completion of the project.
(b) $48.3 million.

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more