Metro programmes underway in Sydney, Melbourne and Brisbane carry some of the densest ELV scopes in Australian infrastructure — station CCTV, PA and passenger information, emergency phones, and tunnel radio, repeated across dozens of stations and kilometres of tunnel. The sheer scale, and the multi-contract-package structure these programmes are typically delivered under, make interface management as much a part of the ELV design discipline as the systems themselves.
Tunnel Radio: A Fundamentally Different Coverage Problem
Tunnels attenuate RF signal severely, and public mobile coverage plus emergency services radio continuity through a tunnel section needs dedicated infrastructure — leaky feeder radiating cable or a distributed antenna system running the tunnel's length, fed from surface base stations or dedicated in-tunnel equipment rooms. This is a genuinely different design problem from surface station coverage, which can often be achieved through comparatively simple external antenna coverage from nearby carrier infrastructure. Tunnel radio design needs to account for train movement, multiple carrier requirements, and emergency services radio bands that surface coverage design rarely has to consider with the same rigour.
The Systems Stack Repeated Across Every Station
- Station CCTV — covering platforms, concourses and station entrances, with analytics increasingly specified for crowd density and platform-edge monitoring.
- Public address and passenger information display systems — coordinated across the network for consistent, synchronised messaging during service disruptions.
- Emergency help points and duress systems — positioned to Australian rail safety standards, with communications routing back to a central operations centre.
- Fire and life-safety systems — station and tunnel fire detection, often with specific tunnel ventilation and smoke management integration beyond a standard building's fire system scope.
Design takeaway: Treat tunnel radio as a dedicated design discipline with its own coverage modelling, distinct from surface station coverage — the propagation physics, emergency services band requirements and multi-carrier coordination needs are genuinely different problems, not a scaled-up version of surface RF design.
Interface Management Across Contract Packages
Large Australian metro programmes are typically delivered through multiple contract packages — tunnelling, stations, systems, rolling stock — awarded to different contractors, often with different design and delivery timelines. ELV systems that span multiple packages, such as station-to-tunnel communications continuity or a network backbone connecting station systems to a central control room, need explicit interface control documents defining exactly which package delivers what and where responsibility boundaries sit. Without this discipline, cross-package ELV interfaces are a consistent and costly source of late-stage coordination disputes on Australian rail programmes, often surfacing during commissioning when it's most expensive to resolve.
Frequently Asked Questions
Why does tunnel radio need different design treatment than surface station communications?
Tunnels attenuate RF signal severely and need dedicated infrastructure — leaky feeder or distributed antenna systems running the tunnel's length — to maintain both public mobile coverage and emergency services radio continuity, which surface stations achieve through comparatively simple external antenna coverage from nearby base stations.
What ELV systems typically make up the densest scope on an Australian metro project?
Station CCTV, public address and passenger information display systems, emergency help points, tunnel and station radio infrastructure, and fire/life-safety systems each run through every station and much of the tunnel length — the sheer repetition across dozens of stations and kilometres of tunnel is what makes metro ELV scope so much denser than a typical single-building project.
How do designers manage interfaces across the many contract packages on a metro project?
Large Australian metro programmes typically split work into multiple contract packages (tunnelling, stations, systems, rolling stock) awarded to different contractors, and ELV interface management requires explicit interface control documents defining exactly which package delivers what, and where responsibility boundaries sit — without this, ELV systems spanning multiple packages (station-to-tunnel communications, for instance) are a common source of costly late-stage coordination disputes.