The document outlines the integration of an IP network for a new airport terminal designed to handle significant passenger traffic increases, from an initial 40,000 to 800,000 passengers annually with new international routes. It details the network design, various port configurations, and the technological requirements for systems including CCTV, access control, and a building management system. Additionally, it highlights challenges faced during the planning and implementation phases, emphasizing the need for effective collaboration and flexibility among stakeholders.

1. An Integrated IP network for a
new Airport Terminal
Barry Shambrook RCDD

2. The existing traffic
• 3 destinations
• 40,000 pax/year
• No border control or
customs

3. The new traffic
• Initially 8 new
routes, 14 by
2013
• International –
UKBA and
Customs
• Max 800,000
pax/year

4. The brief
• 200
passengers/
hour
• 5 stands
• Planning
approval 2007
• Turn key

5. Design proposal – IP network

6. Cable routes
• No raised floor
• Only location for distributors in centre
• Only route to perimeter is below roof, from
first floor

7. Distribution cupboards and MER

8. Outlet counts
ITS network connections
Network type IP Analogue Outlets
6 port fibre switch/media converter
IP surveillance camera FIXED IP
BMS outstation/server FIXED IP
Access controller FIXED IP
Baggage/scanner interface
Total outlet ports
Analogue/ISDN phone
2 port wall/floor outlets
Total other ports
TV screen/advertising
Panic alarm buttons
2 port ceiling outlets
Total IP ports
Baggage system
Total PoE ports
Analogue CCTV
Floor distributor
Printer/scanner
VoIP handset
Self check in
CUTE set
WI-FI A/P
TV signal
EPOS
FID
PC
DESCRIPTION
G2 Land side disabled toilet 0 0 0 1 2
G2 Air side disabled toilet 0 0 0 1 2
G2 Passport check 0 0 0 3 6
G2 Immigration office 0 0 0 1 2
G2 Baggage reclaim/customs 3 1 3 4 7 1 1 6 6 24
G2 Mechanical riser 1 0 1 0 1 2
G2 Interview room 1 1 1 2 1 1 2 1 6
G2 Interview room 1 1 1 2 1 1 2 1 6
G2 Interview/testing room 1 1 1 2 0 2 1 6
G2 Distribution cupboard G2 3 1 0 4 12 12 0
G2 Land side concourse 2 0 2 0 2 4
G2 Total 6 1 6 0 0 0 0 0 3 0 0 0 4 7 20 0 12 3 0 0 60
Grand Total 55 14 77 11 23 4 24 0 20 6 0 11 27 91 272 3 62 10 2 0 496

9. Floor distributor count
Floor distributors
Copper
backbone
of which 24 port Total inter- cables
PoE edge power Non-IP Horizontal connect u comms
Location IP ports ports PoE load switches Heat load load ports cables space room to FD
F1 100 39 390 W 5 500 W 890 W 15 156 21 36
F2 61 20 200 W 3 300 W 500 W 21 126 16.5 36
G1 63 20 200 W 3 300 W 500 W 26 106 15 36
G2 18 7 70 W 1 100 W 170 W 15 56 9 36
Totals 860 W 12 2060 W 444
Core switches 2

10. Physical network internal

11. Physical network external

12. Virtual IP networks

13. Issues and successes
• Specialist intransigence
• Client naivety
• Flexibility
• Design and build co‐operation

14. CCTV – Analogue on Cat5e

15. CCTV – additional cameras

16. Access control – dumb card readers
New technology –
intelligence on board
reader

17. Stand equipment

18. BMS – external plant interfaces
Fibre from terminal
Patch cord
Multicore
cable

19. FIDS, CUTE and CUSS
Also spot the cable
containment!

20. Backbone fibres

21. Construction/IT interface
VLAN SYSTEM IP RANGE DHCP Notes
Yes for WiFi connections? WiFi access to all VLANS, public access to
0 Internet / Wifi xx
Internet
DHCP/DNS provided by Riverbed device inline
between primary MPLS router and LAN,
1 SGL Backoffice xx DHCP provided by Riverbed
Backoffice VLAN needs to be available in ATC,
old terminal and firestation
Backoffice systems require access to Ultra
server in hosting centre over VPN on
10.230.5.0/24, access to web interface on
2 Ultra xx No, fixed IPs required for each device CCTV control server, access to web interface
on BMS management server, access to
Shoretel server. MPLS routers will need to be
connected to this VLAN
Access to SGL Backoffice VLAN to allow
Yes for handsets, assume fixed IPs also required for connection from SGL PCs to management
3 ShoreTel xx
servers and switches software and for local server to communicate
with central ShoreTel server in SCC
BMS server needs to be available to SGL
No, fixed IP addresses required for BMS
4 Building Management System xx backoffice VLAN. Possible requirement for
outstations/consoles
Internet connection for remote support
TBC – possible internet connection to time
5 Clocks xx TBC
source
Access to SGL backoffice VLAN and also to
6 Access Control/CCTV xx No, fixed IP addresses
UKBA for CCTV
Requires direct internet connection, perhaps
7 EasyJet HALO TBC TBC
guaranteed bandwidth as well
EasyJet plan to install dual diverse WAN
8 EasyJet Backoffice TBC TBC connections but use shared LAN to patch
those through to their locations
Isolated VLANs per concession. Must be
TBC depending on
secure to be able to handle EPOS transactions,
9 Retailer/Concession VLAN customer TBC
possibly defined bandwidth, also accessible
requirements
from Aruba WiFi network

22. TV signal distribution

23. A few more “dramas”
• Baggage system control link
• Telephony link to PA
• BMS remote access