Chaos in Melbourne as Two Traffic Tunnels Close Due to Comm Switch Failure

Tunnels closed for 12 hours as switch back-up fails to kick in

1 min read
Chaos in Melbourne as Two Traffic Tunnels Close Due to Comm Switch Failure

Drivers were no doubt spitting out uniquely colorful Australian epithets as they sat for hours in the mayhem caused today by the closing of Melbourne’s two busiest traffic tunnels.The Burnley and Domain tunnels carry about 120 000 vehicles per day into and out of the city’s central business district.  

According to The Australian, at about 4:10 AM local time, a system error was detected that indicated the tunnels’ “neon speed and lane-changing signs had stopped working.”  Technicians tried to correct the problem, but were unsuccessful.  At 4:30 AM, Transurban the owner/ operator of the tunnels – decided to close them because it wasn’t clear in the tunnels’ control room whether the incident detection and safety systems, such as the sprinkler and ventilation systems, would work in case of an accident.

Their fears were not without cause. In 2007, a horrific multiple vehicle crash and fire in the Burnley tunnel killed three people and required that the tunnel be evacuated.

Today, the tunnels were finally partially reopened at 4:45 PM, more than 12 hours after their closing. By then gridlock had encompassed most of the Melbourne region.  Luckily, it was a school holiday or traffic could have been much worse.

The system error was attributed to a failure of a “core communication switch.” A Transurban press release stated that, “In the usual course of events, the backup system would take over, however the back up system … also failed.” It went on to say, “At this point we do not know the reason for the initial failure or back up failure but will provide further updates once our investigation is complete."

Transurban apologized for the “inconvenience.”

I wonder what epithets followed that apology.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less