Attachment 4b - Data Center Report

AMAALA AIRPORT WORK PACKAGE 2
SCHEMATIC DESIGN REPORT (50 %)
10 COMMUNICATION SYSTEMS
10
10 | COMMUNICATION SYSTEMS
10 COMMUNICATION SYSTEMS
10.1 Local Area Network and Wide Area Network (LAN/WAN)
10.1.1 Introduction
The LAN/WAN system will provide a consolidated communications infrastructure comprised of
copper and fibre optic cables routed throughout the airport facilities and the active network
equipment needed. This system should provide transmission media for video, voice and data
signals.
The objective of the network is to provide universal access to voice, video and data services over
a common network infrastructure. It will be a scalable, reliable, highly available three-layer IP
network transport infrastructure to meet the performance and operational needs of the airport.
The LAN/WAN system will provide a base layer for communications between all systems and
users at the airport.
The design shall address issues as high availability, scalability, modularity, manageability, future
development potential and low operating and maintenance costs.
The LAN/WAN System will provide services at least to:
○ Operations;
○ Security;
○ Infrastructure;
○ Airport Staff and Administration;
○ Airlines;
○ Internet Access;
○ Telephony Access;
○ Etc…
AMAALA AIRPORT WORK PACKAGE 2 199/516

SCHEMATIC DESIGN REPORT (50%) | Ref: C3837-EGS-SDR INF-G0050 | Version: 0.1 | Egis | July 2020
10.1.2 Applicable Codes, Standards and Regulations

Code/standard identification Title
ANSI/TIA/EIA-526-7 and 14A Measurement of Optical Power Loss of Installed Single-Mode /
Multimode Fiber Cable Plant
ANSI/TIA/EIA-568-B Commercial Building Telecommunications Cabling Standard
ANSI/TIA/EIA-569-A Commercial Building Standard for Telecommunications

Pathways and Spaces
ANSI/TIA/EIA-569-B Commercial Building Standard for Telecommunications

Pathways and Spaces
ANSI/TIA/EIA-606-A Administration Standard for the Telecommunications

Infrastructure of Commercial Buildings
ANSI/TIA/EIA-607-A Commercial Building Grounding and Bonding Requirements

for Telecommunications
ANSI/TIA 942 Telecommunications Infrastructure for Data Centres
BICSI – TDMM Telecommunications Distribution Methods Manual
BICSI - COOPDM Customer-Owned Outside Plant Design Manual
BICSI - ITSIM Information Transport Systems Installation Manual
BICSI - NDRM Network Design Reference Manual
BICSI - WDRM Wireless Design Reference Manual
IEC 603-7 Current capacity for connectors
IEEE 802.1 LAN/MAN Bridging and Management
IEEE 802.3 CSMA/CD Access Methods (Ethernet)
IEEE 802.3ae 10 Gigabit specification
IEEE 802.3z 1000 Base-S specification
IEEE 802.3ab 1000 Base-T specification
IEEE 802.3af/at Power over Ethernet
IEEE 802.3u 100 Base-T specification
IEEE 802.1Q VLAN
IEEE 802.1P Prioritization
IEEE 802.11 a/b/g/n CSMA/CA Access Methods (Wireless LAN)
Class D, E, EA, F, FA ISO/IEC Information Technology – Generic Cabling for Customer

11801 Premises
TIA/EIA 606-A Administrative Standard for Commercial Telecommunications
IATA International Air Transport Organization
ICAO International Civil Aviation Organization
NIC National Information Centre
Table 55-LAN/WAN applicable References, Standards and Regulations

10.1.3 System Description and Concept of Operation

The LAN/WAN system is the main framework for all other systems, as all communication
between systems and users will be permitted by the Airport network.
In a new airport of these characteristics is important to give a thought to the network as the
main framework of the Airport, considering all buildings and phases. The system shall be design
considering the final capacity.
The fact of having a single system capable of guaranteeing network access to the entire airport,
allows systems and users to exchange information in a simple way and therefore a greater
number of processes can be automated.
All the considerations detailed above make the LAN/WAN System to be considered as essential.
The LAN/WAN System comprises the connection between buildings with a FO ring, the
structured cabling inside each building, the active network equipment and the necessary
equipment to give external access to the LAN/WAN system.
10.1.4 System Architecture

Datacentre 1
Access
Aggregation
Access
Distribution Core
Internet
...
Core
Access
PSTN
Aggregation
Access
Datacentre 1
Figure 57-LAN/WAN architecture
For the design of the Optical Fiber Ring, it is necessary to consider a double ring, what means
two Physical different rings connecting each building of the ring. Each building shall have two
separate manholes for each FO entrance.
The drawing shows how the ring need to be performed, but how the ducts will be deployed
depends on the constructor design.

26. Vip 42.Electrical 40.Power 30.Northern

37.ARFFS 41.Fuel Farm 38Chillers 36.ATC TWR
Hangars charging Plant Gate
46.Staff
25. Ops&Mto
Parking
29.Parking
38. Chillers
Area
26. Vip 33.Sec

Hangars Entrance
27. Airside 23. Mirage

Parking Terminal
42.Electrical 32.Entrance
Charging Drop
28.Gas
31.Vip Drop
Station
30.Northern 29. Parking

Access Gate Area
39.Water 35.Admin 46.Staff 29.Parking

49. Staff PTB 34.Cargo+BHS 38.Chillers
Tanks Building Parking Area
Figure 58-FO Ring Distribution
10.1.5 General System Requirements
Functional Requirements
development potential and low operating and maintenance costs.
The LAN/WAN network should provide connectivity and communications service for all
buildings and all infrastructure that should need any data or voice transmission at the airport.
As security and performance requirements are different depending on the final user (or
department) the LAN/WAN would be logically divided into subnets.
Communications should not be possible between elements located in different subnets. Only
predefined interface points, with firewall and routing capabilities, should be allowed to connect
to more than one subnet.

The areas which shall be supported by network connectivity include but are not limited to the
following:

23 Mirage Terminal
25 OPS&MTO
26 VIP Hangars
27 Airside Parking
28 Gas Station
29 Parking area
30 Northern Access Gate
31 VIP Drop
32 Entrance Drop
33 Sec. Entrance
34 Cargo + BHS
35 Admin Building
36 ATC TWR
37 ARFFS
38 Chillers
39 Water Tanks
40 Power Plant
41 Fuel Farm
42 Electrical Charging
46 Staff Parking
49 Staff PTB
41 Fuel Farm
42 Electrical Charging
46 Staff Parking
49 Staff PTB
Table 56-LAN/WAN areas to be connected
External communications interface should provide service to, but not limited to, the next
systems:
○ Redundant internet access;
○ ATM networks;
○ Fixed and Mobile Telephone Providers;
○ Airline systems.
Quality of service, congestion management and multicast control shall be implemented to

prioritize network data traffic and to manage real-time voice and video data traffic.
Network security shall be an inherent part of the design. Firewall and IPS functionality shall be
implemented at the perimeter of the network.

The network shall be able to transport both layer 3 and layer 2 Multi-Protocol Label Switching
(MPLS) VPNs (Virtual Private Networks).
The network background traffic (service traffic, routing updates and management traffic) shall
never exceed 10% of the total bandwidth of any link.
development potential and low operating and maintenance costs. As the operational hours of
an airport are 24x7x365, robustness, stability, scalability and ease of management and
maintenance are key design considerations.
All switches shall have a minimum slot and interface port spare capacity of 20% for future
expansion.
All endpoint outlets should be connected to its Access layer switch port.
10.1.5.1.1 Security of Information System (SSI)
The SSI Equipment shall guarantee the protection of systems and data against accidental acts
or deliberate attacks. This protection shall meet four objectives:
○ Availability;
○ Integrity;
○ Privacy;
○ Identification.
At this stage, the regulatory framework is not indicated yet. The only framework indicated at
this level is the ICAO 8973 chapter 18 10th edition 2017 or newer if available.
It is recommended to follow the ISO 27000, 27001, 27002 and 27005 standards, as well as the
ANSSI recommendations.
The Security Equipment/Firewalls to be provided to guarantee the security of the information
exchanged shall provide at least the following functionalities:
○ Filtering;
○ IDS/IPS;
○ Proxy;
○ Antivirus;
○ IPSec/SSL;
○ VPN Server.
The SSI solutions will be distributed in the different layers of the Information Systems. The
proposed solution should allow a correlation of events that occur at different levels and show
the alerts to the IT Department in the AOCC operational centre to be determined through rule
mechanisms.
The security equipment shall interact with:
○ All Active equipment and network management solution;
○ Wireless network (Wi-Fi) equipment;
○ All systems and equipment connected to the network shall be supervised;
○ AOCC: The operator shall have a monitoring interface that integrates different security
elements.

Design Criteria
All critical equipment shall be back up with an Uninterruptible Power Supply (UPS) that shall
maintain the system during at least 2h.
10.1.5.2.1 Cabling
Only Basic cabling requirements are included in this chapter for initial design purposes. Final
and more accurate requirements list shall be done in later design stages.
○ HORIZONTAL LAN CABLING:
F/UTP Category 6A rated for horizontal cabling, STP when critical systems are involved.
The horizontal cable length from the distribution room to the telecommunications
outlet/connector shall be no more than 90m long.
A 10m allowance is made for the combined length of patch cords and cables used to connect
equipment.
Sufficient space should be provided in the telecommunications outlet box or equivalent space
so that minimum bend radius requirements are not exceeded.
If an outlet is required outside of the 90m requirement for copper cabling and the requirement
is deemed to be too low density to design an additional communications room, fibre optic
cabling should be utilized.
○ VERTICAL LAN AND WAN CABLING:
Multi-mode or single mode (depending on bandwidth and distance) for vertical and WAN
backbone.
The multiple dual ring fibre optic backbone network consists of an A & B fibre optic cable. The
ring cables contained in the dual ring networks have an identical core count.
Buildings shall be provided with a dual ring backbone cable to support the two feeder cables.
A feeder cable is provided from each dual ring to each building entry from diverse splices. These
building entry points are then either located within or connected directly to the building
distribution rooms via a minimum of two twenty four (24) core fibre optic cables routed
separately from different manholes, within the same building in order to achieve maximum
pathway diversity.
The backbone optical fibre cable system shall consist of high capacity, loose tube,
nonconductive, multi-core, low loss, dry water blocking, rodent resistant, aramid yarn di-electric
armouring, loose tube, gel filled polyvinylidene fluoride (PVDF) or high density polyethylene
(HDPE) sheath, inside/outside plant cable.
10.1.5.2.2 Racks
Technical Rooms shall be equipped with 19" racks. Unless recommended by the manufacturer,
all active equipment will be installed in these racks.
○ Minimum Dimensions: 800mm x 800mm;
○ Other Dimensions: 800mm x 1000mm or 1200mm for active equipment in some cases;
○ Minimum Height: 42 U;
○ Optic drawers;
○ Cable-pass panels;
○ RJ-45 connector patch panels;
○ Two (2) Power Distribution Units (PDUs) connected in two (2) different circuits;
○ Access to the equipment shall be protected by a key lock.

10.1.5.2.3 Core Switches
All core switches shall be connected to each other in a fully redundant partial mesh. Each Core
switch shall be connected to at least two (2) other Core switches. All Core switch interfaces shall
be at least 10GBASE-X.
All connections between Core and between Core and Distribution/Aggregation switches shall
utilize load balancing.
The Core switches shall support VLAN (IEEE 802.1Q). A minimum of 4096 VLAN’s shall be
supported.
The core switches shall be mountable in 19-inch standard rack.
○ Minimum performance data:

● +400 mpps Layer 3 forwarding;
● +50.000 MAC entries;
● +128.000 routes.
○ A switch fabric capable of supporting a minimum of 250 Gbps bandwidth.
○ A non-blocking backplane with full load of all switching modules-between modules and in
case of inter-module trunking.
The Core switches shall be equipped with redundant hot-swappable power supplies to be
connected to two different power distribution circuits.
The Core switches shall have redundancy/failover support that includes Virtual Router
Redundancy Protocol (VRRP or similar) on routing modules, hot-swappable supervisor engines,
routing modules and line cards as well as replaceable fan-trays.
The Core switches shall be able to automatically shut down in case of overheating.
The Core switches shall be able to withstand a Denial of Service (DoS) attack without significant
performance degradation.
The Core switches shall support full routing functionality for both IPv4 and IPv6.
The supported routing protocols shall include Static, OSPF (Open Shortest Path First), LDP (Label
Distribution Protocol) and MP-BGPv4 (Multiprotocol – Border gateway protocol).
OSPF, LDP and MP-BGPv4 shall support MD5 authentication.
Multi-Protocol Label Switching (MPLS) shall be supported.
MPLS (LSP) Ping and TraceRoute shall be supported.
Access Lists shall be configurable for VLANs, Ports, Routers and MAC addresses.
RSVP (Resource reservation protocol) should still be enabled in the network though. It shall be
used for MPLS Traffic Engineering (TE). On one hand, the network should not be congestion
free, but on the other hand, there is always more than one link between any switches in the
network. TE shall be used to shape and steer the traffic along the best path in the network at
any given time. If for example there is congestion on a link between two Core switches, TE shall
automatically route additional traffic through another path to ensure that the traffic is treated
according to its SLA (Service Level Agreements) parameters. The Core switches shall therefore
support RSVP-TE.
Fast Re-Routing (FRR) of TE tunnels in case of a link failure is a requirement.

10.1.5.2.4 Aggregation/Distribution Switches
Aggregation/Distribution switches shall collect 1000BASE-X and 10GBASE-X uplinks from Access
switches and transmit 10GBASE-X Ethernet signals to two Core switches.
All connections between Core and Aggregation/Distribution switches shall utilize load
balancing.
All connections between Aggregation/Distribution switches and Access switches shall utilize
load balancing.
The connections from each Distribution switch to two physically separated Core switches
(located in each Data Centre) shall be 10 Gbit/s SR/LR/ER interfaces. If more than 10 Gbit/s are
needed, the interfaces shall be bundled as one logical channel using LACP.
Every Distribution switch shall be paired with another Distribution switch connecting the same
access switches.
Every Aggregation switch shall be paired with another Aggregation switch connected to the
same pair of Core Switches.
Access switches should connect to the Aggregation/Distribution switch pair through a
1000BASE-X or 10GBASE-X connection to each switch. Distribution switches shall support
modular interfaces (SFP or GBIC).
The Aggregation/Distribution switches shall support VLAN (IEEE 802.1Q). A minimum of 4096
VLANs shall be supported.
The Aggregation/Distribution switches shall support LACP (IEEE 802.3ad).
The Aggregation/Distribution switches shall be mountable in 19-inch standard rack.
○ Minimum performance data:
● +400 mpps Layer 3 forwarding;
● +50.000 MAC entries:
● +128.000 routes.
○ A switch fabric capable of supporting a minimum of 250Gbps bandwidth;
○ A non-blocking backplane with full load of all switching modules-between modules and in
case of inter-module trunking.
The Aggregation/Distribution switches shall be equipped with redundant hot-swappable power
supplies to be connected to two (2) different power distribution circuits.
The Aggregation/Distribution switches shall be able to automatically shut down in case of
overheating.
The Aggregation/Distribution switches shall be able to withstand a Denial of Service (DoS) attack
without significant performance degradation.
The Aggregation/Distribution switches shall support full routing functionality for both IPv4 and
IPv6.
The supported routing protocols shall include Static, OSPF, LDP and MPBGPv4.
OSPF, LDP and MP-BGPv4 shall support MD5 authentication.
Multi-Protocol Label Switching (MPLS) shall be supported.
MPLS (LSP) Ping and TraceRoute shall be supported.
Access Lists shall be configurable for VLANs, Ports, Routers and MAC addresses.
RSVP should still be enabled in the network though. It shall be used for MPLS Traffic Engineering
(TE).

On one hand, the network should not be congestion free, but on the other hand, there is always
more than one link between any switches in the network. TE shall be used to shape and steer
the traffic along the best path in the network at any given time. If for example there is
congestion on a link between an Aggregation switch and Core switch, TE shall automatically
route additional traffic through another path to ensure that the traffic is treated according to its
SLA parameters.
The Aggregation/Distribution switches shall therefore support RSVP-TE.
Fast Re-Routing (FRR) of TE tunnels in case of a link failure is a requirement.
The Aggregation/Distribution switches shall support Spanning Tree including IEEE 802.1w Rapid
Spanning Tree (RSTP) for loop-prevention and IEEE 802.1s Multiple Spanning Tree Protocol
(MSTP) or similar for layer 2 load balancing over redundant links.
10.1.5.2.5 Access Switches
Access Switches shall provide 10/100/1000BASE-T Ethernet ports to attached end user devices
or servers and redundant 1000BASE-X or 10GBASE-X (depending on load prevision) to the
Distribution/Aggregation layer.
All switches shall have a minimum of two (2) uplink ports to the Distribution/Aggregation layer.
Some end user equipment should need to be connected through fibre either because it is
located too far away for twisted pair cabling or because the equipment is located outside.
All Access switches shall be connected to two (2) Aggregation/Distribution switches with
1000BASE-X or 10GBASE-X Ethernet interfaces.
All end user devices or servers shall be connected to the Access switches with 10/100/1000BASE-
T or 10GBASE-X uplinks.
Some servers need more bandwidth than one 10/100/1000BASE-T uplink can provide and may
therefore be able to bundle two or more 10/100/1000BASE-T interfaces through IEEE 802.3ad
Link Aggregation. Access switch shall therefore support this functionality.
All Access switches shall support Power over Ethernet (IEEE 802.3af) or preferably PoE+ (IEEE
802.3at) for Wireless Access Points, IP-telephones, IP-based cameras or similar.
To minimize the risk of loops in the net, only one device (one MAC address) shall be connected
to end user switch ports unless the connected device is an IP phone with built in switch ports.
The switch configuration shall take this into account. If more than one device is connected to a
switch port, the port shall go in administrative shutdown for five (5) minutes, and a Simple
network Management Protocol (SNMP) trap shall be transmitted detailing the event.
The Access switches shall support VLAN (IEEE 802.1Q). A minimum of 4096 VLANs shall be
supported.
The Access switches shall support LACP (IEEE 802.3ad).
The Access switches shall be mountable in a 19-inch standard rack.
The Access switches shall include a non-blocking backplane.
The Access switches shall provide redundant power supplies to be connected to at least two (2)
different power Distribution circuits.
The Access switches shall be able to automatically shut down in case of overheating.
The Access switches shall employ broadcast-, multicast- and unicast storm control to prevent
faulty end stations from degrading the switch performance.

Similarly, the Access switches shall be able to withstand a Denial of Service (DoS) attack without
significant performance degradation.
Access Lists shall be configurable for VLANs, ports and MAC-addresses.
Access switches shall be able to classify and remark the data traffic to the Differentiated Services
Code Point (DSCP) values determined in the QoS schedule. DSCP markings shall not be
accepted at the ingress ports to the Access switches, with the only exception being where the
IP Phone has a built-in switch where DSCP marking can be done.
The Access switches shall support Spanning Tree including IEEE 802.1w Rapid Spanning Tree
(RSTP) for loop-prevention and IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) or similar
for layer two (2) load balancing over redundant links.
The Access switches shall support IEEE 802.1X for port-based security on end user ports. All end
user ports shall be assigned to VLANs dynamically based on the 802.1X authentication unless
the port is manually configured for a specific VLAN.
All Access switch end user ports shall support IEEE 802.1p. 802.1p shall be used to ensure that
IP telephones are put into the proper VLAN and gets the proper QoS treatment.
Protocol Independent Multicast shall be supported including Protocol Independent Multicast
(PIM) Sparse Mode.
Internet Group Management Protocol (IGMP) Snooping shall be supported for fast IP multicast
client joins and leaves.
Dynamic Host Configuration Protocol (DHCP) Snooping shall be supported to avoid spoofing of
DHCP servers.
The Access switches shall be able to mirror traffic on one port to another for monitoring and
fault handling.
10.1.6 Integration Requirements

This system should provide service to all IT systems existing in the airport.
OTHER SYSTEMS
ERP VoIP PAS

OPERATIONAL
SYSTEMS
SECURITY SYSTEMS AIRPORT NETWORK
CONTROL CENTERS
DAS WLAN BMS MCS
Figure 59-LAN/WAN Integration Diagram

10.1.7 IP Address Scheme

The LAN/WAN Supplier shall be responsible for providing and maintaining an IP addressing
scheme which shall require client approval in accordance to LAN policies of the Airport.
10.1.8 Software Requirements

Commercial software packages shall have registration and licensing documentation filed
indicating the Employer as the owner of the software.
Fully licensed software shall be provided for use in the live operational environment.
Software developed shall be licensed to the Employer. This license shall include all executable,
library, object, and source code required to maintain and modify the delivered product. This
information shall be delivered on CD-ROM. All compilers, case tools, utilities, etc. that are
needed to create the executable code shall be included.
Perpetual commercial off-the-shelf software licenses shall be provided.
Software support shall be granted within the terms of the warranty.
All software user interfaces shall use the English language as default.
Systems shall handle dates using Gregorian calendar.
Software support shall include upgrades to newer versions of software where appropriate.
A Software Development Kit shall be provided with each application
10.1.9 Hardware Requirements

It shall include the general requirements for hardware components of any system:
○ All components shall be current production products.
○ All components shall be UL listed or CE marked.
○ Manufacturers: Core, aggregation and distribution switches shall be supplied from
internationally recognized manufacturers including, but not limited to: Cisco, Aruba
Networks, Extreme Networks, etc.
○ All components within the system shall be of a high, professional quality from reputable
manufacturers.
○ All system components (where reasonable possible) shall be manufactured from the same
manufacturer.
○ The hardware shall be off-the-shelf, state-of-the-art and of proven commercial quality. To
assure local commercial availability of maintenance skills and spare parts, it is preferable if
the switches and cabling offered by the Supplier are of a make and type in common use in
Saudi Arabia.
○ Hardware shall be designed and built to interface with standard components, including
racking (as pre-installed within the Data Centres and comms rooms), shelving, support
hardware (screws, bolts, nuts, clips, etc.), cable interface, connectors, wiring assemblies, etc.
○ Hardware shall, where applicable, include indicators (lights, LEDs, etc.) to denote power-on,
systems activity, system failure and system trouble, as well as discrete indicators appropriate
for each device and device class.
○ Hardware that includes a processor such as a PC shall be capable of being remotely stopped,
started and rebooted.
○ Hardware shall be suitably and clearly labelled at minimum with the manufacturer´s name,
the product number, serial number, and date of manufacture and asset number.
○ In case of misplacement of interchangeable units, no damage shall be caused to the
equipment and the protection methods employed in that regard shall be detailed.

○ All hardware data shall be coordinated with the design drawings, bills of material and basis
of quantity documents.
○ Fully licensed hardware shall be provided for use in the live Operational environment.
○ The components, software and technologies to be employed in the design should be well
proven and conform to the international and industry defined open standards.
○ The provision of the equipment (hardware, software, middleware, firmware, etc.) and
materials should be of international and industry defined standards. The equipment and
materials to be installed and supplied should be of the latest models/standards prior to
delivery, and these provisions should be easily upgradeable to the new standards in use at
any time.
○ All systems should operate under Saudi Arabia´s environmental conditions.
10.1.10 Performance Requirements

The switches to be provided shall fulfil the following requirements:
○ All switches shall be identifiable to support maintenance technicians and make easier
administration from the control centre.
○ For the switches to be installed in an interior controlled environment, the LAN system shall
be operational in an ambient air temperature between 15 to 40 degrees Celsius. IT rooms
and Data Centres require this type of environment.
○ For the switches to be installed in an interior uncontrolled environment, the switches shall
support temperatures between 0 to 65 degrees Celsius.
Availability, Maintainability & Reliability

LAN system shall comply with the following redundancy, scalability and reliability requirements
○ Availability: The entire LAN system shall provide a high availability. All configurations and
data used by the software shall be backed up on a daily basis to prevent data loss.
○ System stability: The system provided shall be equipped with a UPS solution to maintain
the system stability. Any power variation should not affect the quality of the picture nor the
video features.
○ Usability: The organization of information on the screen shall be clear. The information
(Online Help, Documentation) provided with the system shall be clear and concise. The
Graphic User Interface shall be user friendly.
○ Reliability: The system provided shall work 24 hours a day. The LAN System shall have a
high MTBF, and a reduced MTTR shall be achievable.
○ Performance / Response time: The LAN system shall manage high speed bit rate in real
time. Response time shall be low.
○ The Supplier shall provide within the proposal detailed information regarding technical
specifications of each of the proposed equipment, materials, and accessories demonstrating
integration / interfacing amongst them.
○ The Mean Time Between Failures (MTBF), Mean Time To Repair (MTTR), Mean Time Between
Critical Failures (MTBCF) and Availability figures of all the equipment proposed should be
provided and the overall system, indicating the method used for the calculation, such as MIL-
HDBK-217. If sub-system MTBF, MTTR, MTBCF, and Availability numbers are submitted, these
shall be rolled up into an overall system MTBF, MTTR, MTBCF and Availability numbers. The
MTBF, MTTR, and the MTBCF numbers of other sites with similar types of equipment installed
should be provided so the quoted numbers may be verified.
○ A list of parts which are unique to the system (such as switches or FO transceivers) and which
in case of failure would be considered critical and cause a suspension of service should be
provided.
○ The MTBF, MTTR, MTBCF and Availability numbers for the communication equipment and
its subsystems should be provided separately.

○ The Availability of the entire system over a period of twelve (12) months shall be at least
99.99%.
Scalability & Expansion Capability
The LAN system shall be configurable depending assuming the future growth of Amaala
Airport. With the progressive development of the different stages of Amaala airport Master
Plan additional displays will have to be installed to cover the new environments to be built,
although the system will have capacity to assume this increase in the number of managed
devices without requiring any system upgrade or new investment. Infrastructure
Requirements.
Scalability: For future expansion it shall be possible to include additional switches. The
LAN environment will be able to support at least up to 15% switches more and will be able
to support a future growth in the next years of operation. System resources (core/switches
capacities, memory, and network bandwidth) will be dimensioned accordingly.
The Supplier shall provide expansion and reserve capacities for any equipment, if required.
Power supplies shall have a capacity of 1.5 times that required for the proposed design.
Sufficient input/output communications ports shall be physically provided to meet the
specified requirements plus 20% spare capability.
Redundancy
LAN Core/aggregation switches shall be installed in the Data Centre at the Airport.
The management software system to be finally deployed in the Data Centre should use the
virtual server technology.
Optimization of resources should be maintained and the environmental and physical
capabilities of the Data Centre respected. Reliability and cost shall be key decision features
together with the ability to use power efficiently with a view to keeping operating costs to
a minimum.
The System shall be deployed in such a way as to provide a redundant, hot failover ensuring
no single point of failure solution.
The System shall be fault-tolerant, with back-up or redundant capacity built-in and should
have the following service continuity considerations
○ High Availability: A high-level of system availability is required. The System shall be designed
to meet the availability requirements. This may be met through high reliability available in
each component, through redundant servers, or a combination of the two.
○ Hot Swappable: System shall be designed to allow for the replacement of failed or failing
components while the system is operating, up to and including replacement of cards,
components, and other discrete modules of the system.
10.1.11 Project Deliverables

The Supplier shall be responsible for the production as requested by the client for all necessary
project related documentation such as but not limited to: O&M, as-built drawings, Risk
assessments, commissioning plans, FAT/SAT procedures and test certificates, (including
maintaining an “As-Built” door schedule for the facility once constructed) and other handover
materials as required by the Design Consultant.

The following table sums up in a high-level overview the deliverables to be provided by the VoIP
supplier during the project:
ID Deliverable Phase
LAN-DES-1 System Detailed Design for installation (controllers’ Design Phase

location, type of controllers, sensors, cabling, fixation, etc.)
LAN -DES-2 Software Detailed Design (system architecture, Design Phase

functionalities, etc.)
LAN -DES-3 Testing & Commissioning Plans Design Phase
LAN -DES-4 FAT and SAT test Procedures Design Phase
LAN -DES-5 Maintenance Plan Design Phase
LAN -DES-6 Integration Plan and Interfaces Design Phase
LAN -DES-7 Training Plan Design Phase
LAN -DEL-1 Cable Management Document Delivery Phase
LAN -DEL-2 Configuration Control Document Delivery Phase
LAN -DEL-3 Test & Commissioning Reports Delivery Phase
LAN -DEL-4 Integration tests Reports Delivery Phase
LAN -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
LAN -DEL-6 Application user manuals Delivery Phase
LAN -DEL-7 As Built drawings Delivery Phase
Table 57-LAN/WAN Project Deliverables
10.1.12 Airport Organizational Units Involved

All the systems use the LAN/WAN infrastructure, from simple computer to the most complex
operational system, including telephones and video systems. Therefore, all the organizational
units present in the airport should be indirect users of this system.
The maintenance and management of the system shall be in charge of IT Support Unit within
the Maintenance and IT department.
Unit id Unit User type Description
XX.XX.XX All User Lan/WAN User System
06.04.00 IT Support Maintenance System Maintenance
Table 58-LAN/WAN Airport Organizational Units

10.2 Fixed telephony (Voice over internet Protocol – VoIP)
10.2.1 Introduction
The objective of the VoIP System is to enable the users in the airport to communicate internally
and externally, to the PSTN through the Voice Gateways. All the VoIP infrastructure should rely
on the usage of the local multiservice LAN/WAN backbone.
The system should be scalable, reliable, highly available IP Telephone System (VOIP) to meet the
performance and operational needs of the airport and the integration of the new system with
the other voice communication systems present at the Airport.
The VoIP System comprise all internal deployment for the internal telephony and also the
configuration of a gateway through the LAN/WAN PSTN to be able to generate outside calls
through the designated telecom operator.

IEEE 802.3X Ethernet physical interfaces specification
IEEE 802.11X CSMA/CA Access Methods (Wireless LAN)
IEEE 802.1q VLAN Ethernet
IEEE 802.1p Prioritization
IEEE 802.1d/s/w Spanning-Tree protocol specifications
IEEE 802.1x network security standards
All standards xDSL, BRI, PRI, E1/T1 and analogic interfaces
Table 59-VoIP applicable References, Standards and Regulations

A telephony system will always be required at the airport for both internal and external
communications. The choice of VoIP is due to the fact that it provides more functionalities than
traditional telephony. It can be easily integrated with legacy APBX and also the reuse of the
network infrastructure leads to a clear reduction of costs.
A billing tool within the VoIP management can be implemented as well. The implementation of
a VoIP telephony system is essential for the Airport.
The system shall cover all telephone needs for buildings in WP2.2.
The VoIP supplier shall provide a proposal for the design, procurement, installation, integration,
testing & commissioning for the Voice over IP/Telephony Communications System (VoIP/TCS)
at WP2 .2 Buildings of Amaala International Airport. Including the following components:
○ Call IP Telephony core processing: Value services such as unified messaging, presence,
instant messaging, collaborative work, IP fax servers, multi-conference, video calls, video
conference, wireless IP telephone, etc. should be able to integrate.
○ Voice gateways to allow the IP telephony system to be able to establish communication with
the public switched telephone network or with other telephone exchanges.
○ Voice messaging and fax services shall be integrated with the system.

○ IP terminals and client devices: Desk or wireless phones or even a software phone application
that runs on a PC must be provided. IP phones must have all the functions expected from a
telephone, as well as more advanced features such as the ability to access web sites.
○ Billing server: Management software application suite for call accounting, cost control and
phone network optimization must be provided.
○ Recording call system: The system should be able to record selected calls.
○ Management tool Telephones to configure all features. Web interface configuration shall be
available.
Although this document provides a conceptual and schematic design to enable the physical
elements of the terminal to be coordinated, the Supplier shall have complete responsibility for
the design and integration of the VoIP system. The VoIP procurement include the:
○ Detailed information of the telephone’s installation in workplaces, information, counter or
boarding desks, or any location required.
○ The design, deployment, installation and integration of all VoIP system.
Call processing unit 2

Call processing unit 1 Recorder
LAN/WAN
IP Terminal
Voice Gateway PSTN
Fax
Management consoles Voice Gateway
Figure 60-VoIP architecture
The VoIP is required to enable the users in the airport to communicate internally and also
externally for mobility services.
The VoIP architecture is composed of the following elements:
○ Call Processing Cores: The Call Processing equipment is the core processing equipment in
an IP telephony scenario. It can also integrate other added value services such as unified
messaging, presence, instant messaging, collaborative work, IP fax servers, multi-conference,
video calls, video conference, wireless IP telephone, etc.
○ Voice Gateways: The voice gateways allow the IP telephone systems to be able to establish
communication with the public switched telephone network or with other telephone
exchanges.

○ IP Terminals and Client Devices: Communication endpoint is a user instrument such as a

desk phone, wireless phone or even a software phone application that runs on a PC. In an
IP environment like this, each phone has an Ethernet connection. IP phones have all the
functions expected from a telephone, as well as more advanced features such as the ability
to access web sites.
○ Integrated Messaging and Fax Server: It provides a Voice messaging and fax services
integrated with the system.
○ Billing Tool: The Billing tool is the management software application suite for call accounting,
cost control and phone network optimization.
○ Recording System: The system should be able to record selected calls, such as: unidentified
calls, calls incoming or outgoing from/to a given number, or any call as per user command.
○ Management Tool: The telephone configuration shall be accessible to users via web browser
interface to make changes to the user set-up features such as call preference, divert, voice
mail, etc. All features that can be configured from the desk-phone shall be available from
the Web interface.
Call processing cores, voice gateways, fax and billing servers and billing system shall be installed
distributed within both data centres (included in Data Centre design).
Basic, standard and advanced phones are placed in workplaces.
Wireless phone is personal operational equipment.
Management Workstation should be placed in an Electronics & Communication department
workplace
The system shall be capable of supporting the total number of IP Telephones required plus 20%.
The overall system shall be capable of expanding to support a minimum of 200% more users.
Design Criteria
10.2.5.2.1 Call Processing Cores
The Call Processing equipment is the core processing equipment in an IP telephony scenario. It
can also integrate other added value services such as unified messaging, presence, instant
messaging, collaborative work, IP fax servers, multi-conference, video calls, video conference,
wireless IP telephone, etc.
Two (2) main call processing units should work together as a single IP PBX system, also known
as cluster. The cluster should be distributed across the IP network, one call processing unit in
each Data Centre, to allow for physical redundancy.
The cluster shall be operating as a Primary/Backup configuration. In normal operation, Primary
server should oversee all services, backup should only have the state of operation updated. Any
changes made on the primary shall be automatically replicated to the secondary such that
should one of the servers fail, the other should automatically control all call setups and tear
downs.
Primary and backup servers shall be installed physically separated, in different buildings, in
different Data Centres.

The call processing and management solution shall include voicemail and telephony
conferencing services.
It shall include Interactive Voice Response (IVR) functionality up to thirty (30) simultaneous
connections and multi-language support. IVR shall have text to speech functionality.
The call processing and management equipment shall include standard call centre
functionalities for up to twenty (20) agents (five (5) working simultaneously).
The system shall achieve an availability of 99.999% assuming a two (2) hour MTTR.
10.2.5.2.2 Voice Gateways
The Voice Gateways allow the IP telephone systems to be able to establish communication with
the public switched telephone network or with other telephone exchanges.
The main function is to convert the traditional voice to packets that are adequate for the
transmission of voice traffic over a TCP/IP network and vice versa. For this purpose, it uses
Digital Signal Processors (DSPs), which are in charge of doing this conversion using algorithms
that can digitalize, packetize and compress the voice.
 Dual tone multifrequency (DTMF) relay capabilities;

 Supplementary services such as hold, transfer and conferencing;
 Fax/modem support;
 Support at least the inbound and outbound traffic generated by five hundred (500)
users;
 It shall be modular and redundant and with redundant power supply modules;
 Voice gateways shall have a management port.
10.2.5.2.3 IP Terminals and Client Devices
Communication endpoint is a user instrument such as a desk phone, wireless phone or even a
software phone application that runs on a PC. In an IP environment like this, each phone has an
Ethernet connection. IP phones have all the functions expected from a telephone, as well as
more advanced features such as the ability to access web sites.
Base key telephone handset features to be supported should include:
 Multi-line and programmable feature keys;

 High-resolution displays to provide visual indication of equipment status;
 For wired terminals, integrated 10/100/1000 Base-T Ethernet Switch LAN and PC ports,
to enable single cable drop to support both the phone and collocated PC;
 Support 802.3af standard based Power-over-Ethernet;
 Support customized data and web-based applications via external application servers;
 Full duplex audio;
 Echo cancellation;
 Caller ID Generation;
 Speed dialling;
 Support for two (2) VLANs.
Handset types required shall be:
 Basic;
 Standard;
 Advanced;
 Wireless.
10.2.5.2.4 Integrated Messaging and Fax Server

Voice messaging and fax services shall be integrated with the system.
A voice messaging platform allows to manage voice messages in a variety of ways using email
inbox, web browser, phone and smartphone, etc.
Fax integration allows to send and receive faxes via standard fax devices or even using a desktop
software in a computer or smartphone.
The Base Station shall be capable of showing Voltage Standing Wave Ratio (VSWR)
measurements or return power on the Feeder Cable and measuring its own Output Power.
10.2.5.2.5 Billing Tool
The Billing tool is the management software application suite for call accounting, cost control
and phone network optimization. Among other features, it provides:
 Integral information on all traffic types;

 Real-time control of communication status;
 Flexible, programmable reports which can be distributed automatically;
 Awareness of unexpected or undesired usage of phone services or resources;
 Early detection of PBX operation alarms;
 Communicate telephone billing information to the airport billing system (ERP).
10.2.5.2.6 Recording System
The recording system shall be capable of recording at least fifty (50) simultaneous calls.
The system should be able to keep the recording data for at least thirty (30) consecutive days.
The system should be upgradable and scalable.
The system should be able to record selected calls, such as: unidentified calls, calls incoming or
outgoing from/to a given number, or any call as per user command.
The system should include remote management using web interface.
The system should include remote monitoring and management via SNMP.
10.2.5.2.7 Management Tool
The telephone configuration shall be accessible to users via web browser interface to make
changes to the user set-up features such as call preference, divert, voice mail, etc. All features
that can be configured from the desk-phone shall be available from the Web interface.
The web interface shall provide a manager to enable authorized users to manage multiple
devices profiles.
The whole VoIP system shall be able to be managed remotely through the network.
The equipment shall support network management through the latest version of Simple
Network Management Protocol (SNMP) and Management Information Base (MIB).

Their functionalities should include at least:
 The GUI shall display the operator on duty and status;

 The GUI shall display system alarms;
 Line number identification;
 The ability to view status and dial any extension;
 Split calls and stay on the line;
 Interrupt calls;
 Recall facility;
 Call monitor facility;
 Call mute;
 Hold calls in loop.

The VoIP system shall have interface with the following systems:
 LAN/WAN: VoIP uses the network infrastructure for all communications;

 WLAN: wireless IP phones link to the wireless network to communicate with the rest of
the system;
 ERP: for potential billing of communication services;
 Master Clock System;
 Fixed Telephone provider Access (National telephone provider to call outside).
Fixed Telephone Provider

Access
OTHER SYSTEMS
ERP VoIP WLAN

OPERATIONAL
SYSTEMS
CONTROL CENTERS
WLAN MCS
Figure 61-VoIP Integration Diagram

The VoIP Supplier shall be responsible for providing and maintaining an IP addressing scheme
which shall require client approval in accordance to LAN policies of the Airport.


A Software Development Kit shall be provided with each application.

It shall include the general requirements for hardware components of any system.
All components shall be current production products.
All components shall be UL listed or CE marked.
Call processing cores, voice gateways, phones, recording system and billing server shall be
supplied from internationally recognized manufacturers including, but not limited to Avaya,
Cisco, Mitel, Nokia, etc.
All components within the system shall be of a high, professional quality from reputable VoIP
manufacturers.
All system components (where reasonable possible) shall be manufactured from the same
manufacturer.
The hardware shall be off-the-shelf, state-of-the-art and of proven commercial quality. To
assure local commercial availability of maintenance skills and spare parts, it is preferable if the
telephone offered by the Supplier are of a make and type in common use in Saudi Arabia.
Hardware shall be designed and built to interface with standard components, including racking
(as pre-installed within the Data Centres and communication rooms), shelving, support hardware
(screws, bolts, nuts, clips, etc.), cable interface, connectors, wiring assemblies, etc.
Hardware shall, where applicable, include indicators (lights, LEDs, etc.) to denote power-on,
systems activity, system failure and system trouble, as well as discrete indicators appropriate for
each device and device class.
Hardware that includes a processor such as a PC shall be capable of being remotely stopped,
Hardware shall be suitably and clearly labelled at minimum with the manufacturer´s name, the
product number, serial number, and date of manufacture and asset number.
In case of misplacement of interchangeable units no damage shall be caused to the equipment
and the protection methods employed in that regard shall be detailed.
All hardware data shall be coordinated with the design drawings, bills of material and basis of
quantity documents.
Fully licensed hardware shall be provided for use in the live Operational environment.
The components, software and technologies to be employed in the design should be well
The provision of the equipment (hardware, software, middleware, firmware, etc.) and materials
should be of international and industry defined standards. The equipment and materials to be

installed and supplied should be of the latest models/standards prior to delivery, and these
provisions should be easily upgradeable to the new standards in use at any time.
All systems should operate under Saudi Arabia´s environmental conditions.
Telephone Specifications
Basic phone: Graphic display, phone address list (1000 contacts) and list of calls, media and
signal circulation, authentication by IEEE 802.1x. Updating by software.
Standard phone: Graphic colour display of 3.5", screen with adjustable tilt, variable function tabs
(soft-keys), quick mark buttons, phone address list (1000 contacts) and call list. Signal cyphering.
Authentication by IEEE 802.1x. Updating by software.
Advanced phone: Display colour graphic of 4.3”. Web navigation, touch screen, self-tightening
keys, menu with icons, two pages with quick marking keys, phone address list (1000 contacts)
and list of calls. Signal cyphering. Authentication by IEEE 802.1x. Updating by software.

All elements included in the VoIP system to be provided shall fulfil the following requirements:
 All telephones shall be identifiable to support maintenance technicians and make easier
 For the Telephones to be installed in an interior controlled environment, the VoIP
system shall be operational in an ambient air temperature between 15 to 40 degrees
Celsius. IT rooms and Data Centres require this type of environment.
 For the Telephones to be installed in an interior uncontrolled environment, the
telephones shall support temperatures between 0 to 65 degrees Celsius.
 For the Telephones to be installed at exterior environments, the devices shall support
temperatures between 0 and 65 degrees Celsius. Purpose-built to survive in the
harshest outdoor environments.

VoIP system shall comply with the following redundancy, scalability and reliability requirements:
 Availability: The entire VoIP system shall provide a high availability. All configurations
and data used by the software shall be backed up on a daily basis to prevent data loss.
 System stability: The system provided shall be equipped with a UPS solution to
maintain the system stability. Any power variation should not affect the quality of the
picture nor the video features.
 Usability: The organization of information on the screen shall be clear. The information
(Online Help, Documentation) provided with the system shall be clear and concise. The
Graphic User Interface shall be user friendly.
 Reliability: The system provided shall work 24 hours a day. The VoIP System shall have
a high MTBF, and a reduced MTTR shall be achievable:
 Performance / Response time: The VoIP system shall manage high speed bit rate in
real time. Response time shall be low.
The Supplier shall provide within the proposal detailed information regarding technical

The Mean Time Between failures (MTBF), Mean Time To Repair (MTTR), Mean Time Between
A list of parts which are unique to the system and which in case of failure would be considered
critical and cause a suspension of service should be provided.
The MTBF, MTTR, MTBCF and Availability numbers for the communication equipment and its
subsystems should be provided separately.
The Availability of the entire system over a period of twelve (12) months shall be at least 99.99%.

The VoIP system shall be configurable depending assuming the future growth of Amaala Airport.
With the progressive development of the different stages of Amaala airport Master Plan
additional displays will have to be installed to cover the new environments to be built, although
the system will have capacity to assume this increase in the number of managed devices without
requiring any system upgrade or new investment. Infrastructure Requirements.
Scalability: For future expansion it shall be possible to include additional telephones. The VoIP
environment will be able to support at least up to 30% telephones more and will be able to
support a future growth in the next years of operation. System resources will be dimensioned
accordingly.
Sufficient input/output communications ports shall be physically provided to meet the specified
requirements plus 20% spare capability.
Redundancy
Call processing cores, voice gateways, fax and billing servers and billing system shall be installed
distributed within both data centres.
Optimization of resources should be maintained and the environmental and physical capabilities
of the Data Centre respected. Reliability and cost shall be key decision features together with
the ability to use power efficiently with a view to keeping operating costs to a minimum.
The System shall be deployed in such a way as to provide a redundant, hot failover ensuring no
single point of failure solution.
The System shall be fault-tolerant, with back-up or redundant capacity built-in and should have
the following service continuity considerations
High Availability: A high-level of system availability is required. The System shall be designed
to meet the availability requirements. This may be met through high reliability available in each
component, through redundant servers, or a combination of the two.
Hot Swappable: System shall be designed to allow for the replacement of failed or failing
components while the system is operating, up to and including replacement of cards,
components, and other discrete modules of the system.


VoIP-DES-1 System Detailed Design for installation Design Phase

(controllers’ location, type of controllers, sensors,
cabling, fixation… etc)
VoIP -DES-2 Software Detailed Design (system architecture, Design Phase

functionalities… etc)
VoIP -DES-3 Testing & Commissioning Plans Design Phase
VoIP -DES-4 FAT and SAT test Procedures Design Phase
VoIP -DES-5 Maintenance Plan Design Phase
VoIP -DES-6 Integration Plan and Interfaces Design Phase
VoIP -DES-7 Training Plan Design Phase
VoIP -DEL-1 Cable Management Document Delivery Phase
VoIP -DEL-2 Configuration Control Document Delivery Phase
VoIP -DEL-3 Test & Commissioning Reports Delivery Phase
VoIP -DEL-4 Integration tests Reports Delivery Phase
VoIP -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
VoIP -DEL-6 Application user manuals Delivery Phase
VoIP -DEL-7 As Built drawings Delivery Phase
Table 60-VoIP Project Deliverables

This is an ‘universal’ system. All the staff in the airport should be user of the telephony system.
Maintenance staff, mainly IT Support, should be responsible for maintaining the system in the
correct operational state.
XX.XX.XX All User VoIP User system
Table 61-VoIP Airport Organizational Units

10.3 Public Address System (PAS)
10.3.1 Introduction
A Public Address System (PAS) shall be provided to enable the making of general
announcements and for the annunciation of instructions during evacuation of the buildings.
The PAS system is intended to deliver emergency voice messages, as a primary use, in line with
international requirements. As a secondary use, the system has been designed to deliver non-
emergency messages, such as paging and general public announcement messages.
The PAS system has not been designed for background music reproduction. However, it shall
have the facility to allow connection of a background music source, such as a music server.
The PAS system shall provide audio reproduction coverage for all public of the building, being
suitable for its use for both emergency and non-emergency voice announcements and using
either microphones or a digital message store as the source for such announcements. Staff and
other areas should be at least covered with Fire Alarm sounder/strobes, but the final PAS
coverage shall be defined with a site survey considering airport security and operational needs.
The PAS shall provide standard public address functionality while adding an expanded feature
set. Using the latest digital audio and network technologies end users shall be provided with
system control and monitoring. This provides a feature rich system that is easier to maintain
and administrate.
The system shall utilize standard network topology that allows a distributed architecture.
Traditional systems require all speaker and microphone cabling to converge at one room, the
PAS System shall allow cabling to be run to the nearest communications room with paging
hardware. The end result shall be less speaker and microphone cable. By leveraging the existing
Ethernet network as the system backbone new hardware can be added anywhere with a network
connection.
It is recommended to define operating areas that may facilitate the management of the
messages through the speakers.
The PAS System procurement will include all hardware, software, and infrastructure needed to
create an audio passenger communication system. Basic functions that shall be provided by the
PAS system will be the following ones:
 Selectively connect any zone to any available signal channel;

 Selectively control sound from microphone outlets and other inputs;
 "All-call" feature shall connect the all-call sound signal simultaneously to all zones
regardless of zone or channel switch settings;
 Telephone paging adapter shall allow paging by dialling an extension from any local
telephone instrument and speaking into the telephone;
 Produce a program-signal tone that is amplified and sounded over all speakers,
overriding signals currently being distributed;
 Reproduce high-quality sound that is free of noise and distortion at all loudspeakers at
all times during equipment operation including standby mode with inputs off;
 The PA system shall provide intelligible output coverage at a levels 15 dB to 20 dB over
measured ambient noise;
 The coverage shall be a uniform level of plus or minus 3 dB @ 1000 Hz Octave band;
 The speech intelligibility of the PA system announcements (measured in STIPA female
index) shall be minimum 0.6.


IEC 60849:1998 Sound systems for emergency purposes
UL 2572 Standard for Mass Notification Systems
UL 1711 Standard for Amplifiers for Fire Protective Signalling Systems
UL 864 Standard for Control Units and Accessories for Fire Alarm Systems
SBC 801 Saudi Fire Code
NFPA 101 Life Safety Code
NFPA 424 Guide for Airport Emergency Planning
NFPA 72 National Fire Alarm and Signalling Code
NIC National Information Center
Table 62-PAS applicable References, Standards and Regulations

The PAS System has the following uses that are necessary for the Airport Operation:
 Allows the mandatory announcement of emergency situations and evacuation requests;

 Keeps all passengers and staff informed of any event in the Airport or any useful
information;
 Allows staff to record messages (or generate them automatically) to be played by the
system in different zones whenever required, therefore reducing the workload of the
staff to make those announcements.
The PAS system shall be configurable to the size of Amaala Airport. The system shall give
coverage to the Mirage Passenger Terminal and the Staff Passenger Terminal.
PAS procurement is absolutely of the essence for airports, particularly due to its emergency and
evacuation support nature, therefore it is an essential system to be deployed.
In a final stage of the system design an acoustic study to ensure the PAS coverage within both
terminals. Also, a zone announcement classification shall be defined for the different type of
announcement and evacuation messages.
The Supplier shall provide a proposal for the design, procurement, installation, integration,
testing & commissioning for the PAS System at Amaala International Airport. Including the
following tasks:
 All activities which may be necessary to complete the design and installation of the
PAS devices;
 Installation, setup and configuration and associated activities necessary to deliver
an operationally ready PAS. The IP addressing scheme and VLAN requirements
shall be developed with the Common Network Supplier;
 Supply of hardware as specified for the system;
 PAS monitoring application in charge to interface with the Fire Alarm System and
all the other systems that may be required to make the system fully operational;
 Installation, configuration and testing of the system hardware and software.

elements to be coordinated, the Supplier shall have complete responsibility for the design,
location and integration of the PAS.
The PAS System to be provided by the Supplier shall correspond to the need of announcements
throughout the various classified zones. The System provided and installed shall be of proven
efficiency according to existing references in other recent International Airport installations.
The Supplier shall divide the terminal into functional zones corresponding to their utilization
and different announcement. These zones shall be split into categories and levels regarding the
emergency and evacuation plan.
The Supplier shall provide an electroacoustic study to optimize the zones and speakers, and the
audio quality of the speakers.
The PAS supplier shall accept any design change request (due to external conditions such as the
construction works or other systems design) which shall not have any justifiable extra-cost for
the Supplier.
The PASS software and system customization is part of the Supplier´s scope in order to support
all the functionalities requested in this document.
The PAS supplier will provide cooling, ventilation and power information to the MEP supplier to
ensure the proper working of all the PAS system components.
All the measures provided in the Specifications should be given using the International System
of units (SI).
10.3.4 System Architecture and Design Considerations

A physical representation of the PAS System architecture has been presented below, redundancy
and high availability are the main design criteria. Integration with other systems shall be
essential to obtain the necessary data to undertake its function. Further information about
integration in section System Integration.
DISTRIBUTION SPEAKERS AREA N
ROOM X
DATA CENTER 1
AMPLIFIER A1
CENTRAL PROCESSOR - A
SWITCH LAN A
TEXT TO SPEECH AIRPORT NETWORK

SERVER - A
AMPLIFIER B1
SWITCH LAN B
AODB/FIDS
AMPLIFIER AN
DATA CENTER 2
CENTRAL PROCESSOR - B
AMPLIFIER BN
TEXT TO SPEECH
SERVER - B TERMINAL AREA N
DIGITAL PAGING
STATION
TERMINAL AREA N+1
DIGITAL PAGING
STATION
Figure 62-PAS architecture

The system shall be based on redundant link architecture, such that no single failure in
connections between amplifiers or central processor will result in any loss of system
performance.
The system shall utilize fibre optic and copper cabling infrastructure for the backbone of the
announcement distribution, management and maintenance operation. Equipment shall provide
the appropriate interfaces to the copper and fibre optic cabling to implement all required paging
and associated functions.
The following elements will compose at least the scope of supply for the PAS system:
 Servers: The server coordinates all activities of the PAS System and provides storage
for databases and system logs. The PAS System shall utilize physical servers. A variety
of redundancy technologies can be implemented to facilitate maximum uptime. These
shall include Redundant Array of Independent Disks (RAID), failover, and clustering
configurations.
 DSPs: The Digital Signal Processor (DSP) controls audio routing for the system. The
device handles all analogue input and output connections, ambient noise
compensation, and telephone interfaces. The DSP also allows conversion between
analogue and networked audio.
 Amplifiers: The power amplifiers take the DSP line level output and boost it to the high
voltage (70V/100V) signal utilized by the system speakers. The amplifier should be
sized to meet the power requirements of each speaker circuit. Amplifiers should have
a variety of configurations with multiple channels and power ratings.
 Paging Station: The paging station is comprised of an intelligent touch screen device
and handheld microphone that provides full functionality for public address and flight
information system control.
o The DPS shall be compatible with PoE;
o Dual Ethernet connection to support redundancy.
 Microphones: Ambient Noise Sampling microphones.
o The microphones shall be compatible with PoE.
 Speakers: The PAS System shall be compatible with a variety of speaker types.
 End of Line Device: To aid verification of the distributed loudspeaker line’s integrity,
the impedance shall be detectable by the audio system.
Design Decisions
The vendor solution is to remain market competitive and as such the final architecture model
shall be left to Supplier to define the most commercially viable solution for their offered system.
The Airport shall be divided in zones. The audio output of the system shall be broadcast via the
loudspeakers, grouped in loudspeaker zones. The system will be capable of addressing any
combination of zones simultaneously, and the zone groups required during normal operations
and during emergencies shall be programmed into the system during commissioning.
System Procurement
PAS is an independent system that shall run from its own clustered servers and core equipment
placed in the Amaala Data Centres. For redundancy and availability, each set of PAS servers
shall be installed in separate Data Centres; the same shall apply for the digital processors.
The PAS is considered to contain the following equipment:

Item Id Item Amount
PAS01 PAS Application 1
PAS02 PAS servers 2
PAS03 PAS Digital Signal Processor 2
PAS04 PAS Ceiling Loudspeaker 200
PAS05 PAS Column Loudspeaker 50
PAS06 Acoustic survey 1
PAS07 Audio Amplifiers 20
PAS08 Microphones 45
PAS09 Paging Stations 5
PAS010 End Of Line Device 20
Table 63-PAS Infrastructure requirements
PAS servers and DSP should be redundant and located within each data centre.
Workstations/Paging Stations will be installed at the AOCC, Security Operations Centre (SOC)
and other areas.
Microphones will be installed along the terminal (gates, etc).
Speakers will be installed along the terminal in order to cover all operational zones.
End of lines devices will be installed at the end of each speaker line.
Spares Procurement
The following spares are recommended to be provided by the Supplier. This is just an estimate,
the Supplier is free to justify a different quantity or additional equipment. The PAS is considered
to contain the following spare equipment in order to be able to maintain the system without
interruptions.
Item Id Item Amount
PAS011 PAS server 1
PAS012 PAS Digital Signal Processor 1
PAS013 PAS Ceiling Loudspeaker 20
PAS014 PAS Column Loudspeaker 5
PAS015 Audio Amplifiers 2
PAS016 Microphones 5
PAS017 Paging Stations 1
PAS018 End Of Line Device 2
Table 64-PAS Spare requirements


The PAS shall provide standard public address functionality while adding an expanded feature
set. Using the latest digital audio and network technologies end users shall be provided with
system control and monitoring. This provides a feature rich system that is easier to maintain
and administrate.
The system shall utilize standard network topology that allows a distributed architecture.
Traditional systems require all speaker and microphone cabling to converge at one room, the
PAS System shall allow cabling to be run to the nearest communications room with paging
hardware. The end result shall be less speaker and microphone cable. By leveraging the existing
Ethernet network as the system backbone new hardware can be added anywhere with a network
connection.
The PAS System procurement will include all hardware, software, and infrastructure needed to
create an audio passenger communication system. Basic functions that shall be provided by the
PAS system will be the following ones:
 Selectively connect any zone to any available signal channel;
 Selectively control sound from microphone outlets and other inputs;
 "All-call" feature shall connect the all-call sound signal simultaneously to all zones
regardless of zone or channel switch settings;
 Telephone paging adapter shall allow paging by dialling an extension from any local
telephone instrument and speaking into the telephone;
 Produce a program-signal tone that is amplified and sounded over all speakers,
overriding signals currently being distributed;
 Reproduce high-quality sound that is free of noise and distortion at all loudspeakers at
all times during equipment operation including standby mode with inputs off.
The system shall operate as a fully integrated part of the building emergency system, alongside
the fire detection and alarms (fire alarm) system. The primary function of the system shall be to
provide secure, fail-safe and high intelligibility emergency speech broadcast to all areas.
The area of coverage shall include all public areas. Back of house areas are to be covered by
sounders directly from the fire alarm system.
10.3.5.1.1 Announcement Zones management
The PAS System shall not constrain the number of zones that may be created. Zones shall be
named and presented to users with descriptive alphanumeric names.
The audio output of the system shall be broadcast via the loudspeakers, grouped in loudspeaker
zones. The system will be capable of addressing any combination of zones simultaneously, and
the zone groups required during normal operations and during emergencies shall be
programmed into the system during commissioning.
The PAS System shall be capable of assigning any paging station to any paging zone(s) without
hardware changes, as well as grouping paging zones without hardware changes.

10.3.5.1.2 Emergency and evacuation management
For emergency purposes, the system shall be capable of broadcasting pre-recorded emergency
messages into combinations of pre-determined zone groups, as instructed by the Fire Alarm
System.
There shall also be a fireman’s microphone console with access to override all signals (including
the emergency pre-recorded messages) and broadcast to any combination of zone or zone
group as provided on a programmable console. There shall also be a number of microphone
consoles distributed in the terminal gates and lounges for local non-emergency broadcasts.
The method of evacuation will be provided via a horizontal / vertical evacuation system, similar
to the systems used within other large buildings such as hospitals where people are moved from
the area/ areas of danger to an adjacent (vertical or horizontal) safe zone.
Once the fire signal has been verified and dependent on the location of the fire source (the
particular zone) the safety management personnel shall instruct people via the PAS systems to
evacuate a particular zone and make their way to an adjacent zone or out of the building as
required.
Verification may be provided by a second fire alarm (e.g. a second automatic detector, in which
case the automatic annunciation systems will be activated, announcing the pre-programmed
evacuation procedures).
10.3.5.1.3 Sound modulation and ambient noise compensation
The system controller shall include frequency response equalization (to optimize sound quality
in relevant zones and system inputs), and electronic time delays (to align audio signals in large
zones with long-throw loudspeakers).
The loudspeaker outputs shall be commissioned to achieve the signal levels specified and the
system balanced (preamplifier gains, power amplifier gains, and individual loudspeaker tapings)
and adjusted(equalization) to give optimized evenness of coverage and speech intelligibility.
The PAS System shall provide for ambient noise compensation that shall allow users to adjust
playback volume up or down based upon the level of ambient noise. Ambient noise adjustment
is handled in one of three (3) ways:
 Hardware Based:
Automatic ambient noise analysis compensation via ambient noise sensing shall be
capable of sensing via single or multiple microphones. Multiple sensing microphones
in a space that has varying ceiling heights shall be adjustable and mixable as one zone.
Ambient noise sensing controls amplified SPL levels by independent zones based on a
time and frequency weighted averaging of ambient noise within any given zone area.
Time and frequency weighting shall be user selectable.
 Software Based:
Time based Ambient Noise Compensation shall allow for automatic adjustment of
volume levels within any zone based upon user defined schedule. For example, turn up
the volume in Concourse B at 6:30 a.m. and turn it back down at 12:30 p.m.
 Manual override:
It shall allow the user to manually set the volume in any zone from the Administration
Console. All volume adjustments are handled manually in this mode.

10.3.5.1.4 Messages management
The PAS System shall support and distribute digital audio for paging stations, message queuing,
emergency announcements, local announcements, background music, and scheduled
messages.
The PAS System shall support the management of passenger-intended messages (i.e. a Courtesy
Announcement) through a client application accessible or intelligent LAN based paging station.
The PAS System shall support the following message types:
 A Scheduled Message is typically professionally recorded, complete .wav file that can
be scheduled to play between begin and end dates (or never end) by day of the week
and/or time of day.
 A Dynamic Message is created by assembling complete messages from Message Assets
(also known as takes or message parts ). Which message assets are used is determined
by variable data in the flight information (or other) database (i.e. carrier, time, flight
number, flight status, etc) and voice inflection based upon where, in the sentence, the
asset is to be used (beginning, middle, or end). Software concatenates the message
into a single .wav with a unique index.
 A Courtesy Message is a predefined message with input controls for variable data (i.e.
passenger name) to be entered at the time of scheduling.
The PAS System shall support Text-To-Speech (TTS) generation of scheduled messages, dynamic
messages, and courtesy announcements. Text-to-speech messages will be generated for any
message type that does not have proper message assets in the system or all courtesy based
announcements.
The PAS system shall be capable of generating audio messages based upon real-time flight data.
Audio messages are generated from flight data using text-to-speech technologies or pre-
recorded phrases.
The PAS System shall support configurable pre-recorded messages. Pre-recorded messages
shall not be constrained in total number or length of messages.
The PAS System shall allow messages and announcements to be assigned to paging zones or
zone groups.
The PAS System shall allow user configuration of message types and priority levels. The number
of priorities is not restricted. The paging system allows messages with higher priorities to
interrupt messages of lower priority. In the case of an interruption, messages with higher
priorities will interrupt the current lower priority message.
The PAS System shall support full paging control via Voice Over IP (VOIP) or telephone interface
card technology including, live paging, record and playback paging. Telephone paging can be
based upon user PIN access.
All messages in the system shall be fully audited based on location and/or user. All messages
can be reviewed and played back in the system as recorded .wav files.

10.3.5.1.5 Administration
The PAS Administration Console shall allow the system administrator to manage all aspects of
Public Address System from one application including hardware management, audio
management, user and system administration, reporting, diagnostics, and flight information
interface.
The PAS Administration Console shall connect to the paging server and audio equipment via
Ethernet allowing users to administer the paging system remotely.
The PAS Administration Console shall be password protected requiring username and password
authentication. Once logged in users are restricted to what their permissions allow.
10.3.5.1.6 Diagnosis
The PAS System shall be capable of monitoring critical system information for hardware device
including servers, audio controllers, amplifiers, matrix mixers, paging stations, and powered
loudspeakers via the Administration Console.
The PAS System shall be capable of monitoring critical system software via a central
Administration PC console.
The PAS System shall be capable of providing configurable diagnostic information and
automatic notification via e-mail to any e-mail address.
10.3.5.1.7 Reports
The PAS System shall provide a comprehensive set of reports, including, but not limited to:
 Flight Lookups;
 Flight Changes;
 Priority Changes;
 Input Changes;
 Microphone History;
 Message History;
 Output Changes;
 Message Auditing.
Deployment/Performance Requirements
All critical equipment shall be backed up with a Uninterruptible Power Supply (UPS) that shall
The following parameters shall be considering when designing and deploying PAS system:
 Availability:
The whole of the automatic detection and alarm PAS systems will be backed up via a
separate emergency battery system that will be capable of operating for a specific
period.
The failover and monitoring system shall monitor both hardware and software
elements. The software monitor manages all active services related to the PAS System.
This includes the server-based applications, interfaces, database elements, web
services, and paging station applications.
The PAS System shall support amplifier monitoring, failover, and failback. During a
failover event, the PAS System monitors the secondary channel as it actively powers the
zone. Additionally, alerts for failure events can be sent via e-mail with details of the
event including device name, location, amplifier channel and the system conditions
which caused the system to fail over.

 Scalability:
The PAS central extension and the management application shall be scalable to support
100% more speakers, paging stations, microphones… etc., beyond the requested values
with constant response time when adding hardware.
 System stability:
It should be able to support concurrent use by multiple operators in non-stop 24 hours-
a-day operations.
The whole system shall be equipped with a UPS solution to maintain the system
stability.
 Usability:
PAS supplier will perform an electroacoustic study to optimize the audio
quality/speakers to be deployed through an informatics simulation according the
following context:
o Data
- Use the building architecture drawings to prepare the simulation space;
- Including the building materials.
o Acoustic parameters calculation

- Reverberation times, with different people attendance;
- Coverage. Speakers positioning (alternatives);
- Sound Pressure level (SPL), checking the possible shadows;
- Total efficiency (direct reflected);
- Intelligibility.
o Objectives
- Define the different zones/areas and cover all Amaala airport requirement
for the specific areas;
- Obtaining the correct average reverberation time. If necessary, some
absorbent building materials can be applied;
- Consistency coverages for the speaker systems whose fluctuation does not
exceed +/- 3 Db;
- SPL calculation. Total SPL >=85 DB.
10.3.6 Integration and Interface Requirements

The specified PAS system should be fully integrated and installed as a complete package,
covering airport control needs and including the staff accreditation platform.
The PAS System shall be fully integrated with the flight information on the AODB. Such
integration shall be performed through the Airport Network, and it will enable the automatic
announcement of flight information on specific stages.
The PAS System shall be integrated with the Fire alarm system for emergency detection
situations. Such connection shall be direct and without the intermediation of any software to
avoid failures on emergency situations. Find below the PAS system integration diagram.

AODB
AIRPORT NETWORK
FIRE MCS
PAS
ALARM
Figure 63-PAS integration
As previously described and not limited to, the system shall have some logical and physical
interfaces with other systems for which the PAS Supplier shall be responsible for:
System Interfaces, Fire Detection and Alarm System

The PAS System shall be integrated with the Fire alarm system for emergency detection
situations. Such connection shall be direct and without the intermediation of any software to
avoid failures on emergency situations.
System Interfaces. Airport Operational Data Base (AODB)

The PAS System shall be fully integrated with the flight information on the AODB. Such
integration shall be performed through the IB, and it will enable the automatic announcement
of flight information on specific stages.
System Interfaces. Master Clock System (MCS)

The System will be interfaced with the Master Clock System (MCS), as to ensure the proper Time
Synchronization. The clocking source shall be Network Time Protocol (NTP) delivered via the
Airport Common Network (ACN).

The PAS Supplier shall be responsible for providing and maintaining an IP addressing scheme


The PAS operating system must provide a seamless solution. The management software shall
be an industry standard, scalable, reliable, multi-user platform.
The PAS system shall be based solely on TCP/IP and capable of supporting this environment.
All components of the PAS system shall be redundant to ensure the continuation of service.
From multi-path wiring to redundant switches and servers to RAID disk arrays on servers and
interleaving workstations across switch devices, PAS installation shall be protected so that no
single component failure can ‘compromise’ the overall service. The Core PAS Equipment will be
installed at two separate Data Centres with independent Power Supply Circuits for the ensuring
of higher level of the redundancy of the system.
PAS system has to be designed and implemented based on a high-speed LAN architecture with
the fastest possible network performance using state-of-the-art LAN networking technologies.
It has to be designed to be fully redundant and resilient while providing flexibility and scalability.
Different segments of the switched Ethernet LAN must have the possibility to be configured for
different amounts of traffic in order to economically pair speed with need. The bandwidth
offered by switched Ethernet has to allow the integration of new PAS and non-PAS functions
and applications on the LAN.
The PAS software shall be 64-bit and based on an open system architecture.
The software shall be designed using a modular approach, in a commonly available
development environment. Software code and functionality shall be well documented in order
to facilitate maintenance by personnel other than the original programmer.
A single user license of the development system and any tools/utilities used during development
shall be included in the proposal as a deliverable item. Custom assembly language routines are
not allowed without specific permission of the Client Design Consultant.
The software selected shall meet the operational, functional, and performance requirements
specified herein. Additionally, due to the rapid advancement and antiquation of software
technology, the supplied software shall be the latest released version with all manufacturer
patches applied.
The Supplier shall deliver all required system and application software for a fully functional
system. Each application shall be identified by the generic, off-the-shelf name. Software
provided by the Supplier to operate the system shall be delivered in a ready-to-run form,
including all necessary utility programs and documentation.
Software shall use industry standard components. Software shall not contain any proprietary
interfaces or components. Software shall use industry standard application development
software such as Java, C++, CORBA, and XML. Supplier shall state what application development
software has been used, for Design Consultant’s review.

All supplied software running on servers or clients shall synchronize to a Network Time Protocol
(NTP) source. The Supplier shall coordinate with other entities the exact IP address of the NTP
source.
System updates: The system shall be based on a concept that all necessary software
components shall be downloaded by the workstations at the time of successful log-in. Any
modification to the software configuration shall therefore only be done at the server level. Such
modifications shall take effect by logging a workstation out and in again. Updates to the PAS
systems shall be distributed from the central platform servers and become active at the
individual workstations upon new login.
The PAS configuration as previously described shall be by proprietary software application
applicable to the selected PAS vendor which shall require approval by the Client Design
Consultant. This application software shall be installed to client and server computers provided
by the PAS Supplier, and accessible only with authorized levels of user privileges.

Software and hardware components such as systems operator workstations, application servers,
processors, DPS Microphones, amplifiers and Speakers to other systems are included in the
scope of the PAS.
All components within the system shall be of a high, professional quality from reputable
manufacturers.
manufacturer.
computers offered by the Supplier are of a make and type in common use in Saudi Arabia.
Hardware shall be modular, allowing easy replacement of cards, boards, and components
without hard connections (i.e. using quick-connects, plug-and-socket connections, etc.).
Hardware shall be commercially available, with multiple sources for replacement parts wherever
possible. One-off, custom hardware is not acceptable.
(as pre-installed within the Data Centres and communications rooms), shelving, support
In case of misplacement of interchangeable units, no damage shall be caused to the equipment
quantity documents.

Internet access shall not be allowed from PAS workstations.
All peripherals provided shall be certified for use on the PAS platform.
All applications running on the PAS platform shall be certified by the PAS provider.
The equipment shall be standardized and certified by the supplier. The documents shall be
delivered with them.
The PAS system must be based on standard components which have already been used in
comparable installations at other airports.
The service provider shall propose a configuration so that its upgrade throughout the Contract
term is not necessary. Moreover, a maintenance plan (in accordance with the manufacturers’
instructions) shall provide a number of spare equipment to be delivered with all the equipment.
Head End Equipment Capacities

The system shall be capable of supporting 100% growth with the addition of field hardware and
shall not require upgrading of the system software or servers.
The Supplier shall provide software licenses capable of supporting the quantity of microphones,
speakers, DPS, workstations, servers, etc. as designed and installed as part of this specifications.
Supply install and commissioning of software application and any other software that may be
required to make the system fully operational to meet client requirements.
Regarding communications, the PAS deployment will fulfil the following requirements:
 The PAS system should be an IP-based system, with an Ethernet network and TCP/IP
protocols.
 It is the responsibility of the network provider to dimension and guarantee the data
traffic required by the system.
Regarding Energy, the PAS deployment will fulfil the following requirements:
 For the Workstations and Servers, it will be necessary to have electrical connections of
safe power, coming from UPS.
 All equipment shall be fed locally via double pole-fused isolators provided by the
electrical service Supplier, according to plan of implantation to be executed by the
Supplier.
 It is the responsibility of the supplier of the power grid to dimension the same to
guarantee the permanent service.
The PAS shall be an IP-based system and all wiring from all controllers and monitoring stations
is expected to be as high as possible using the CAT-6 UTP cable, with Ethernet and TCP/IP
protocols.

System Capacity
The system shall be designed to support simultaneous operations.
The system shall be capable of supporting all interfaces as specified in this document (as a
minimum) within the performance requirements as outlined herein.
At peak demand, system utilization of resources shall not exceed Sixty percent (60%) of capacity.
The systems shall be capable of supporting priority orders data queuing and transmission to
ensure immediate delivery of higher priority and time sensitive messages.
10.3.10.2.1 Utilization
For any twenty (20) minute sampling period of normal peak hour operation, system utilization
of resources shall not exceed fifty percent (50%) of capacity. Utilization in this context refers to
CPU usage; CPU usage is obtained through the use of the operating system tool System Activity
Reports (SAR).
10.3.10.2.2 Scheduled Downtime
Downtime to update operating systems, applications or repair components shall be acceptable

reasons for downtime, however, where components are duplicated; there shall be no
interruption to system services. The following reasons shall be acceptable causes of downtime:
 If the operating systems of the servers require maintenance or updates, or if the

servers require system maintenance, each server shall be brought down individually
to be updated/maintained, such that at no time is more than one server down;
 If the operating system of the end devices requires maintenance or updates, or if
the end device requires system maintenance, the end device that requires the
maintenance shall be brought down during non-peak hours of operation;
 The Employer may authorize maintenance/updates on the end devices during
other than non-peak hours if the particular end device is non-functional without
having the maintenance or updates performed.
10.3.10.2.3 Response Time
Response time criteria shall be met under maximum loading conditions:

 The transmission delay for on-line critical business transactions shall not exceed 1.0
second total for 95% of all transactions. The remaining 5% of transactions shall not
exceed 2.0 seconds;
 The time required for servers to complete a full fail-over switching shall not exceed
one (1) minute;
 The time required to restart and resynchronize the servers after a complete system
failure shall not exceed fifteen (15) minutes (e.g. after an extended system outage
or failure of both main and standby servers);
 Start-up processing time at PAS workstations shall not exceed two (2) minutes.


The system shall be built and installed in accordance with the guidance given in in the following
standardization documentation:
 NFPA 72:2010;
 BS EN 54-2;
 BS EN 54-4;
 BS 5839-8:2008;
 IEC 60849:1998.
The following parameters shall be considering when designing and deploying PAS system:
 Availability:
o The whole of the automatic detection and alarm PAS systems will be backed up
via a separate emergency battery system that will be capable of operating for a
specific period;
o The failover and monitoring system shall monitor both hardware and software
elements. The software monitor manages all active services related to the PAS
System. This includes the server-based applications, interfaces, database
elements, web services, and paging station applications;
o The PAS System shall support amplifier monitoring, failover, and failback. During
a failover event, the PAS System monitors the secondary channel as it actively
powers the zone. Additionally, alerts for failure events can be sent via e-mail
with details of the event including device name, location, amplifier channel and
the system conditions which caused the system to fail over.
 Scalability:
o The PAS central extension and the management application must be scalable to
support 100% more speakers, paging stations, microphones, etc, beyond the
requested values with constant response time when adding hardware. Such
scalability shall support the extension of Amaala Airport according to the current
airport Master Plan.
 System Stability:
o It should be able to support concurrent use by multiple operators in non-stop
24 hours-a-day operations;
o The whole system shall be equipped with a UPS solution to maintain the system
stability.
 Usability:
o PAS supplier will perform an electroacoustic study to optimize the audio

quality/speakers to be deployed through an informatics simulation
according the following context:
 Data:
1. Use the building architecture drawings to prepare the
simulation space;
2. Including the building materials.

 Acoustic parameters calculation:

1. Reverberation times, with different people attendance;
2. Coverage. Speakers positioning (alternatives);
3. Sound Pressure level (SPL), checking the possible shadows;
4. Total efficiency (direct reflected);
5. Intelligibility.
Objectives:
1. Define the different zones/areas and cover all Amaala airport

requirement for the specific areas;
2. Obtaining the correct average reverberation time. If necessary,
some absorbent building materials can be applied;
3. Consistency coverages for the speaker systems whose
fluctuation does not exceed +/- 3 dB;
4. SPL calculation. Total SPL >=85 DB.
 Reliability:
o The system provided shall work 24 hours a day. The system shall have a high
MTBF, and a reduced MTTR shall be achievable:
 The Supplier shall provide within the proposal detailed information
regarding technical specifications of each of the proposed equipment,
materials, and accessories demonstrating integration / interfacing
amongst them.
 The Mean Time Between failures (MTBF), Mean Time To Repair
(MTTR), Mean Time Between Critical Failures (MTBCF) and Availability
figures of all the equipment proposed should be provided and the
overall system, indicating the method used for the calculation, such as
MIL-HDBK-217. If sub-system MTBF, MTTR, MTBCF, and Availability
numbers are submitted, these shall be rolled up into an overall system
MTBF, MTTR, MTBCF and Availability numbers. The MTBF, MTTR, and
the MTBCF numbers of other sites with similar types of equipment
installed should be provided so the quoted numbers may be verified.
 A list of parts which are unique to the system (such as sensors or locks)
and which in case of failure would be considered critical and cause a
suspension of service should be provided.
 The MTBF, MTTR, MTBCF and Availability numbers for the
communication equipment and its subsystems should be provided
separately.

With the progressive development of the different stages of Amaala Airport Master Plan and
with the increase in the number of passengers and boarding gates, additional Microphones,
DPSn and Speakers will have to be installed to cover the new environments to be built, although
the system will have capacity to assume this increase in the number of managed devices without
requiring any system upgrade or new investment.
The system and supporting tools and applications selected shall allow for future expansion, with
the ability to expand the total storage and number of users as needed without significant
upgrades or modifications to the system.

PAS servers and workstations shall have excess capacity to avoid an increase in processing time
in peak hour on a busy day.
The system and supporting tools and applications selected shall be appropriate for at least four
(4) times the expected initial load on the system to allow for future expansion, with the ability
to expand the total storage and number of users as needed without significant upgrades or
modifications to the system.
Scalability: The PAS to be procured shall cover the airport needs for all the phases regarded at
the airport Master Plan.
For future expansion it shall be possible to include additional resources. The PAS environment
will be able to support a future growth in the next years of operation. System resources
(processor speed, memory, disk space, network bandwidth) will be dimensioned accordingly.
Reserve spare capacity of the processing time shall be not less than 40% of the available
processing time for each processor, based on average use values.
Reserve spare capacity of the memory shall be not less than 40% of the available memory for
each processor, based on average use values.
Redundancy
System application head-end processors shall be installed in the Data Centres at the Airport.
The server technology to be finally deployed in the Data Centres should be chosen. The use of
blades should be encouraged as should be the use of virtual server technology.
Optimization of resources should be maintained, and the environmental and physical
capabilities of the Data Centres respected. Reliability and cost shall be key decision features
together with the ability to use power efficiently with a view to keeping operating costs to a
minimum.
the following service continuity considerations:
 High Availability: A high-level of system availability is required. The System shall be
designed to meet the availability requirements. This may be met through high reliability
available in each component and through redundant servers;
 Hot Swappable: System shall be designed to allow for the replacement of failed or
failing components while the system is operating, up to and including replacement of
cards, components, and other discrete modules of the system.
Load Balancing: The system shall run on fully load balanced server hardware. Load Balancing
shall be achieved by allocating messages and distributing load among interchangeable servers
and provide support for transaction queuing.

Additionally, all systems requiring server-based hardware to support their operation shall
provide as a minimum:
 Multiple hot-swappable redundant power supplies;

 Servers shall utilize a redundant server pair with automatic fail-over to ensure that
performance and high-availability objectives are met without manual intervention;
 Redundant servers shall be located in diverse locations;
 Servers shall be fault tolerant via mirroring or clustering or another vendor
technology;
 The design should allow a server to be powered down and replaced without
disruption to the network or applications;
 Multiple load sharing application servers or other configurations shall be
considered viable alternatives to redundant application server pairs if equivalent or
better system redundancy and resiliency can be demonstrated.
To this scope, continuous monitoring of the status of both internal services and servers is
required.
The processing capability of the server configuration shall be configured to consider both the
message throughput and any other factors such as the processing load required for each
message.
In the Event of Failure

System failures, including server or device failures, shall be viewable at a central control point
(i.e., the System Administrator's workstation). A failure shall initiate an alarm and add a failure
record. Additionally, the system administrator shall receive a warning message on the system
administrator workstation, notifying of the failure. The system shall also be capable of providing
pager and e-mail notification. Server failure shall include any hardware or software-based
failure.
In the event that a server or end device goes out of service, the central control log shall be
updated. Therefore, where practical, a positive relationship (e.g., system heartbeat) shall exist
between all components of the systems at all time.
All failures of the system shall be logged at a central control point (i.e. Application Server). The
failure shall initiate alarms and reports (e.g. time and date of failure event).
When a failure is detected, the system shall be able to automatically reconfigure onto the
surviving server and to restart processes, so that operation can continue without message loss
or the need for immediate operator intervention.


The following table sums up in a high-level overview the deliverables to be provided by the PAS
PAS-DES-1 System Detailed Design for installation Design Phase

cabling, fixation, etc.)
PAS-DES-2 Software Detailed Design (system architecture, Design Phase

PAS-DES-3 Testing & Commissioning Plans Design Phase
PAS-DES-4 FAT and SAT test Procedures Design Phase
PAS-DES-5 Maintenance Plan Design Phase
PAS-DES-6 Integration Plan and Interfaces Design Phase
PAS-DES-7 Training Plan Design Phase
PAS-DEL-1 Cable Management Document Delivery Phase
PAS-DEL-2 Configuration Control Document Delivery Phase
PAS-DEL-3 Test & Commissioning Reports Delivery Phase
PAS-DEL-4 Integration tests Reports Delivery Phase
PAS-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
PAS-DEL-6 Application user manuals Delivery Phase
PAS-DEL-7 As Built drawings Delivery Phase
PAS-DEL-8 Acoustic Survey Report Delivery Phase
Table 65-PAS Project Deliverables

Main organizational units to be involve in PAS use and maintenance are presented below.
01.01.00 Commercial and User User To include advertisement on

Advertising announcements
02.02.XX Airport Operations User For voices announcement about operation
02.03.XX Fire and Rescue User For voices announcement about

Services emergencies
13.01.00 Airline User User Flight announcement
13.04.00 Passenger User Receive information
Table 66-PAS Airport Organizational Units Involved

10.4 Distributed Antenna System (DAS)
10.4.1 Introduction
The DAS System is an antenna distributed system that allows to share mobile coverage within
the places that the telecom operator is not arriving, basically used inside big buildings where
the mobile phone signal is not arriving.

ANSI/TIA/EIA-526-7 and 14A Measurement of Optical Power Loss of Installed Single-Mode /
Multimode Fiber Cable Plant
ANSI/TIA/EIA-569-A Commercial Building Standard for Telecommunications Pathways

and Spaces
ANSI/TIA/EIA-569-B Commercial Building Standard for Telecommunications Pathways

and Spaces
ANSI/TIA/EIA-606-A Administration Standard for the Telecommunications Infrastructure

of Commercial Buildings
ANSI/TIA/EIA-607-A Commercial Building Grounding and Bonding Requirements for

Telecommunications
BICSI - COOPDM Customer-Owned Outside Plant Design Manual
IEEE 802.1 LAN/MAN Bridging and Management
IEEE 802.3 CSMA/CD Access Methods (Ethernet)
IEEE 802.3ae 10 Gigabit specification
IEEE 802.3z / IEEE 802.3ab 1000 Base-S specification / 1000 Base-T specification
IEEE 802.3af/at Power over Ethernet
IEEE 802.3u 100 Base-T specification
IEEE 802.1Q VLAN
IEEE 802.1P Prioritization
Class D,E,EA,F,FA ISO/IEC 11801 Information Technology – Generic Cabling for Customer Premises
IATA International Air Transport Organization
ICAO International Civil Aviation Organization

Table 67-DAS applicable References, Standards and Regulations


DAS is a network of spatially distributed antennas connected to a common source, thus
providing wireless service within a specific geographic area. The RF signals to and from the
mobile operator’s site base station are combined and piped through a system of multiple
antennas. The system can support a wide variety of technologies and frequencies, obviously
including GMS, 2G, 3G, 4G and 5G.
The DAS System will provide mobile coverage within the main buildings Mirage Terminal, Staff
Terminal, ATC Tower, Administration Building, Hangars and Cargo and BHS Handling Building.
The outside buildings zones and other airport area shall be cover with the telecom operator
base stations along the Amaala area.
In order to cover the desired areas, RF coaxial cable to deploy an antenna matrix shall be installed
along the areas.
In furthers stages of the System Design, the provider shall ensure the coverage performing a
Coverage study and proposing the best location for the antennas to be installed.

See below the basic antenna distribution for the DAS System:
Antenna
Distribution Airport
Aerea
RF Coupler Repeater/Amplifier
Signal
Source
Figure 64-DAS architecture
10.4.5 General Requirements
The radio equipment connected to the Distributed Antenna System shall operate in the 800/900
MHz bands (825 – 960 MHz), 1800 MHz band (1710 – 1880 MHz) and the 2100 MHz band (1910
– 2170 MHz) in accordance with the relevant ITU, ETSI and 3GPP specifications.
The design shall include Multiple Input/Multiple Output (MIMO).
All elements shall be with PIM less than -150dBc @ 20W.

The design shall generally specify the use of components which operate over the frequency
range 825 – 960 and 1710 - 2170 MHz. Antennas and radiating cable shall operate over the
frequency ranges 825 – 960 and 1710 –2690 MHz.
RF levels shall be sufficient to facilitate both-way handovers with the external network at
locations agreed on the target Coverage Area.
The antennas to be installed throughout the Airport as part of the proposed DAS shall be low-
profile, flush-mounted, multi-band. The antennas shall be resistant to vandalism, accidental
physical abuse or extreme weather conditions (wind, precipitation, etc.).
Handovers to/from external fast-moving mobiles need to be avoided (except in tunnels). The
design should ensure that RF levels specified at ground level outside the building are met.
The DAS shall satisfy the following signal coverage requirements:
 Signal coverage of 95% or better in public and non-public areas inside within Mirage
Terminal, Staff Terminal, ATC Tower, Administration Building, Hangars & Cargo and
BHS Handling Building, and within three hundred (300) feet outside of these facilities.
 Minimum signal penetration are as follows:
o 85 dBm indoors throughout 95% of the anticipated coverage area;
o -95 dBm outdoors throughout 90% of the anticipated coverage area.
The DAS shall satisfy the following reliability requirements:
 Fault tolerance mechanisms to mitigate and/or eliminate single points of failure for all
components of the system. The DAS shall have self-healing features so that none of
the applications is disrupted.
 Service level of 99.99 percent or better for all applications.
The DAS shall satisfy the following backup power requirements:
 Capability of connecting to a backup power generator to be provided by Amaala

Airport. This is necessary if electrical power is lost to the Airport.
 Battery and/or solar power backup for all network equipment. Such back up shall be
sufficient to ensure continuous operation at full power and functionality for a period of
not less than two (2) hours in the absence of utility power.
The proposed equipment shall operate from a power source of 220 V ± 10%, 60 Hz ± 5% and
from the Uninterruptible Power System (UPS) supplied by the Supplier.
All outdoor-mounted equipment shall be designed to support ambient temperatures ranging
between 0°F (-17°C) and +140°F (60°C).
All outdoor-mounted equipment shall be designed to withstand sustained winds up to 85mph
(137Km/h) and gusts to 105mph (169km/h).
All components shall be protected against electrical overstress (e.g. from lightning, overvoltage,
surges and sags, electrostatic discharge, etc.). Cables leaving the equipment shall be adequately
shielded.
The Supplier shall explain any physical changes that shall be made to the Airport facilities to
accommodate the installation of the system. This includes cutting into or through any part of
the building structures, such as girders, beams, concrete, floors, partitions or ceilings. The
Supplier shall obtain written permission from the Owner prior to making these types of physical
changes to the facilities.

Design Criteria
All critical equipment shall be back up with a Uninterruptible Power Supply (UPS) that shall
Indoor antennas will be installed suspended on ceilings whenever possible. Final location of the
antennas will be validated by the Supplier, coordinating with Electrical and IT Passive
Infrastructure for final location of these components.
The proposed solution shall specify the number of remote units and antenna arrays depending
on the coverage analysis and heat maps.
Expansion capacity shall be considered for currently not covered areas or possible load increase.
This capacity shall be apart from the spare capacity and should be at least a 20% of the total
capacity.
Power supplies shall have a capacity of two (2) times that required for the proposed design.
Local authorities shall provide DAS frequencies to be use. Channel loading and frequency bands
shall be proposed for full building coverage. Prior to installation, Suppliers shall confirm the
channel loading and frequency use in the serving area and shall guarantee coverage for these
channels.
The service life of the equipment shall be at least ten (10) years.
The DAS normally comprises at least the following components:
 Donor Antennas;
 Coverage Antennas;
 Coax Cable;
 Coax Connectors;
 Splitters;
 Combiners;
 Couplers;
 Fiber-Optic Cable;
 Fiber-Optic Connectors;
 Fiber-Optic Jumpers;
 Fiber-Optic Master Unit;
 Fiber-Optic Remote Units.
All the DAS equipment shall be mountable in a 19-inch rack.
10.4.5.2.1 Donor Antenna
Broadband Donor Antennas shall feature a multi-band design, accommodating Cellular, PCS,
LMR and AWS frequencies in a single small antenna.
The Donor antennas frequency bands will be between 700-806Mhz, 806-960Mhz and 1710-
2200 Mhz.
10.4.5.2.2 Omnidirectional coverage antennas
Omni-Directional Coverage antennas shall feature a multiband design, accommodating multiple

frequency bands in a single small antenna.
The Omnidirectional Coverage antennas frequency bands will be between 698-800Mhz and
1710-2200 Mhz.

10.4.5.2.3 Directional coverage antennas
Directional coverage antennas shall feature a multi-band design, accommodating multiple

frequency bands in a single small antenna.
The Directional Coverage antennas frequency bands will be between 698-800Mhz, 806-960Mhz
and 1710-2700 Mhz.
10.4.5.2.4 Cabling
The Supplier shall try to standardize cable types and lengths in the installation.
The cables shall be laid out, depending on the location, in cable troughs, elevated floors,
suspended ceilings, pipes, cable shafts or cable trays. Outside cables shall be protected in
conduits or in armoured jackets.
Cables shall be placed side by side and tied at regular intervals along their routing and grouped
by function. Addition of cables/wires in existing cable trays shall be reviewed by Amaala Airport
after the provision of the appropriate calculation of additional weight and heat gain by the
Supplier.
To avoid induction, low-level signal cables shall be separated from power cables by a minimum
of 0.25m and shall cross at perpendicular angles.
All interconnecting cables and harnesses used throughout the equipment shall be effectively
formed and loomed, paired out and terminated with crimp connectors or other mechanically
and electrically secure terminals to enable the ready re-assembly and re-connection of
equipment at site.
Cables shall be clearly identified at a prominent point and each wire of the cable shall be
individually identified at each end of the cable adjacent to the terminal with a slip-on tag or
other secure means of tagging.
10.4.5.2.5 Fibre optic cables and connectors
 Fibre Optic Cable:

Cables shall be six-strand or greater, designed for point-to-point applications as well
as mid-span access, and shall provide a high-level of protection for optical fibre
installed in interior building environments.
 Fiber Optic Pigtails:
To maintain channel integrity, optical fibre patch cords and pigtails shall be fabricated
to meet the performance parameters corresponding to the optical fibre cable approved
product type specified below. Patch cord and pigtail plug connectors shall be equipped
with boots and shall have same colours as related optical fibre backbone cables, unless
specified or indicated otherwise. Optical fibre patch cords and pigtails shall be available
with the following options as specified or indicated.
10.4.5.2.6 Distributed Control Unit (DCU)
The Fiber optic DCU shall convert Radio over Coax. (RoC) from the Donor antenna to Radio-
Over-Fiber (RoF) for distribution to Fiber-Optic Remote Units (DHR).
10.4.5.2.7 Optical Distribution Unit (ODU)
The ODU performs RF to optical conversion and transports these signals over long distances
while minimizing loss. The ODU is co-located with the BIU from which it receives power and RF
communication.

10.4.5.2.8 Distributed Remote Head (DRH)
DHR converts the Radio over Fiber (RoF) signal back to radio over coax, as well as provides
filtering so that multiple frequency bands can reside over the same passive cable and antenna
infrastructure. The proposed design shall include the necessary amount of DCU to cover the
operation of the project.
10.4.5.2.9 DAS Management System (MS)
A network management and monitoring platform for all the access points shall be provided with
at least the following specifications:
 The client-server architecture shall allow the monitoring of the status of at least all
devices supplied in the project;
 The MS shall have a graphic interface to monitor the status of the devices;
 There shall be no limit for new devices;
 The MS shall have a topology administration feature with auto discovery feature;
 The MS equipment visualization feature shall be able to supervise the devices´ status;
 The MS shall be accessed through Web client and SNMP client.
The MS shall monitor the entire DAS. Besides monitoring all the active network devices, the MS
will also be used as a tool for fault-resolution, device configuration and as central (backup)
repository for active network device configurations and software.
The MS shall be redundant and fault tolerant to the extent that if a breakdown occurs in either
soft- or hardware, normal operations can be resumed within a short time frame.
The MS shall be able to communicate with the DAS equipment using standard protocols.
Deployment/Performance Requirements
The solution shall have high availability of master equipment.
MTBF, MTTR, MTBCF and Availability figures of all the equipment proposed and the overall
system shall be provided, indicating the method used for the calculation, such as MIL-HDBK-
217.
The Availability of each provided equipment over a period of twelve (12) months shall be at least
99.99%, including boards, components and power supply.

DAS system should provide service to all the required areas and for this purpose it shall be
integrated to the Local Mobile Telephony Service.

Mobile Telephone
Provider Access
AIRPORT NETWORK
DAS MCS
Figure 65-DAS Integration Diagram

The DAS Supplier shall be responsible for providing and maintaining an IP addressing scheme

The Supplier shall provide a complete software package (including diagnostics and all software
licenses), which is free of all known errors. Off-the-shelf proven programs and packages should
be used as much as possible. The license prices shall be specified in the proposal.
The Supplier shall ensure the needed license(s), to provide a lifetime operation for all the
equipment and systems, with all the requested features and characteristics regarding DAS
functionalities.
If any additional license(S) is/are needed, that has an expiration time, it shall be clearly specified,
and explain which functionalities or features will be affected at the expiration time.
Programs shall be designed in a structured language and based on open architecture principles.
The Supplier shall specify the language(s) and version(s) used including all operating systems,
all database management software, program development and run time languages.
The Supplier shall include licenses for all software used in the solution. Also, the Supplier is
requested to provide the annual price of the software licenses, if any.
The Supplier shall ensure that enough licenses to the software are provided and that the
individual licensing schemes are the most favourable for Amaala Airport.
The licenses shall as a minimum include free upgrades within major releases.
A structured or object-oriented programming approach should be used to produce reliable and
maintainable software which can be easily changed and expanded. All the individual programs
used to implement functions shall be modular.
The Supplier is requested to provide the annual price of the software licenses, if any. Software
language shall be English.


It shall include the general requirements for hardware components of any system:
manufacturers.
manufacturer.
It is highly desirable that commonality of hardware is considered to simplify logistic support and
reduce training costs during the life of the equipment. This especially relates to similar
processors and ancillary functionality, e.g. hard disks, CD/DVDs, memory, video cards, etc. for
maintenance workstations, display processors, and data processing systems. The hardware
should have a high level of availability.
computers offered by the Supplier are of a make and type in common use in Saudi Arabia
Commercial off the Shelf (COTS) hardware shall be used as much as possible.
without hard connections (i.e., using quick-connects, plug-and-socket connections, etc.).
(as pre-installed within the Data Centres and comms rooms), shelving, support hardware (screws,
bolts, nuts, clips, etc.), cable interface, connectors, wiring assemblies, etc.
quantity documents.

The equipment shall be standardized and certified by the Supplier. The documents shall be
The systems and equipment shall be capable of automatic start-up at power on, a system crash
and/or a power failure. It shall also be able to initiate a system start-up in either a cold start or
a warm start mode.
A cold start mode shall consist of starting the system with default parameters, with configuration
and all active files cleared.
A warm start mode shall consist of starting the system with the latest parameters for the
configuration prior to the incident and active files.
The operating environment shall have a menu to allow the operators to modify the different
parameters, such as brightness, colours, etc.
Any human-machine interface (HMI) shall have a graphic environment and be user-friendly. The
information shall be displayed in different colours for easy interpretation.
All supplied equipment and materials shall be new.
The DAS system must be based on standard components which have already been used in

DAS system shall comply with the following redundancy, stability and reliability requirements.
Availability: The entire DAS system shall provide a high availability. All configurations and data
used by the software shall be backed up on a daily basis to prevent data loss.
System stability: The system provided shall be equipped with a UPS solution to maintain the
system stability. Any power variation should not affect the quality of the picture nor the video
features.
Usability: The organization of information on the screen shall be clear. The information (Online
Help, Documentation) provided with the system shall be clear and concise. The Graphic User
Interface shall be user friendly.
Reliability: The system provided shall work 24 hours a day. The DAS System shall have a high
Performance / Response time: The DAS system shall manage high speed bit rate in real time.
Response time shall be low.
The Mean Time Between failures (MTBF), MTTR (Mean Time To Repair), Mean Time Between
The Supplier shall provide a list of parts which are unique to the system and that in case of
failure would be considered critical and cause a suspension of service.

The Availability of the entire system over a period of twelve (12) months shall be at least 99.99%,
including boards, components and power supply.

The Supplier shall provide a Reserve expansion capacity for currently not covered areas or
possible load increase. This capacity shall be apart from the spare capacity and should be at
least a 30% of the total capacity.
Power supplies shall have a capacity of two (2) times that required for the proposed design.
The Supplier shall provide a full explanation about how this extra capacity or growing could be
achieved.
Redundancy
DAS controller shall be installed in the Data Center at the Airport.
of the Data Centres respected. Reliability and cost shall be key decision features together with
 High Availability: A high-level of system availability is required. The System shall

be designed to meet the availability requirements. This may be met through high
reliability available in each component and through redundant servers or a
combination of the two;
 Hot Swappable: System shall be designed to allow for the replacement of failed
or failing components while the system is operating, up to and including
replacement of cards, components, and other discrete modules of the system.


The following table sums up in a high-level overview the deliverables to be provided by the DAS
DAS-DES-1 System Detailed Design for installation Design Phase

DAS-DES-2 Software Detailed Design (system architecture, Design Phase

DAS-DES-3 Testing & Commissioning Plans Design Phase
DAS-DES-4 FAT and SAT test Procedures Design Phase
DAS-DES-5 Maintenance Plan Design Phase
DAS-DES-6 Integration Plan and Interfaces Design Phase
DAS-DES-7 Training Plan Design Phase
DAS-DEL-1 Cable Management Document Delivery Phase
DAS-DEL-2 Configuration Control Document Delivery Phase
DAS-DEL-3 Test & Commissioning Reports Delivery Phase
DAS-DEL-4 Integration tests Reports Delivery Phase
DAS-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
DAS-DEL-6 Application user manuals Delivery Phase
DAS-DEL-7 As Built drawings Delivery Phase
DAS-DEL-8 Coverage Survey Report Delivery Phase
Table 68-DAS Project Deliverables

Main organizational units to be involve in DAS use and maintenance are considered as general
for all passenger, airport staff and airlines.
XX.XX.XX All User DAS User system
Table 69-DAS Airport Organizational Units Involved

10.5 Wireless Local Area Network System (WLAN)
10.5.1 Introduction
The WLAN or Wi-Fi System shall be provided to enable the airport staff, operations, airlines,
ground handling services, retails tenants, security services and passengers to access a wide
range of services, e.g. high-speed internet access, voice and video applications throughout the
airport. The WLAN system should work as an extension of the LAN system. It should supplement
the connectivity provided by the Local Area Network (LAN). This service could clearly split in
three main services:
○ Public providing to the passengers the internet connection;

○ Public providing to the airlines and handlers the connection to their own systems;
○ Internal providing to the whole airport staff the access to the airport systems.

ANSI/TIA/EIA-569-B Commercial Building Standard for Telecommunications Pathways

and Spaces
FCC Federal Communications Commission regulations and Standards
ICAO International Civil Aviation Organization Security Requirements
IEEE 802.1Q VLAN
Class D,E,EA,F,FA ISO/IEC 11801 Information Technology – Generic Cabling for Customer
Premises
IATA Airport Development Reference Manual
Table 70-WLAN applicable References, Standards and Regulations

The WLAN System will allow to have network access in places where the cable is not arriving, as
for example the baggage load at the aircraft (for ground handlers’ use) and therefore facilitating
the work.
Devices with WLAN adaptors, such as laptops and smartphones, are everyday becoming more
common in modern airports for airport staff and for passengers that nowadays are more
dependent on the technologies and having network access.

Guaranteeing access to WLAN/WIFI for passengers is an indisputable service, which the airport
can take advantage of to obtain information on its passengers through the login required to
access the Wi-Fi. The WLAN shall provide a captive portal for public wireless users to
authenticate access to the system, or to accept an appropriate Acceptable Usage Policy prior to
guest access.
Facilitating access to data, video and voice services through the WLAN results in greater
efficiency in management and undoubtedly impacts on the benefits, therefore the installation
of a WLAN systems is considered essential.
The WLAN system will be essential to have coverage at the Mirage passenger terminal, Staff
Passenger Terminal, ATC Tower, Apron areas and Hangar Areas.
Another advantage of this system is that it can be procured as a concession. The awarded
company can design, install and manage the system, getting paid by a percentage of the income
generated by the WLAN use.
The WLAN supplier shall provide a proposal for the design, procurement, installation,
integration, testing & commissioning for the Wireless Local Area Network system at Amaala
International Airport. Including the following components:
 Full coverage study;
 Access Point installation requirements for civil Supplier;
 WLAN controller configuration proposal;
 Deployment proposal.
elements of the terminal to be coordinated, the Supplier shall have complete responsibility for
the design and integration of the WLAN system.
Access Point installation in the best location to maximize the antennas radiation, even whether
any mechanical adaptation has to be done.
The design, deployment, installation and integration of both access point and wireless controller.
The WLAN supplier shall provide the Detailed Design documentation and all documents needed
for the implementation of the WLAN once the contract is awarded. Such detailed design
documentation will include at least (but not limited to):
 Detailed coverage study;

 Design schemes, detailing technical and physical features;
 Specific details on the installation, to be requested by the customer on-demand
basis;
 As-built drawings with the final details of the Access Point installation.

Wifi AP Wifi AP Wifi AP Wifi AP Wifi AP
WLAN controller WLAN controller

WLAN management console
Figure 66-WLAN architecture
The WLAN is required for mobility services. Passengers Internet service Access could be offered.
Laptops, smartphones, tablets, etc. could connect to the WLAN.
The WLAN architecture is composed of the following elements:
 Access Point: It is a station that transmits and receives wireless data and connects
wireless users to other users across the fixed network (LAN). It serves as the point
of interconnection between the WLAN and the fixed wired network;
 Controllers: They provide the central intelligence of the WLAN system and are
responsible for managing de AP’s. They perform real-time RF management and
detection and avoidance of RF interference. They also provide a common platform
for their configuration and allow several AP’s to work together in a unified manner.
Location-based solution can be provided by using wireless infrastructure to deliver
personalized content to mobile devices and gather customers insights to make
smarter business decision;
 WLAN Management system: It provides a tools suit to manage the WLAN Network
in order to identify problems before there are disruptions to connectivity, app
quality, and RF coverage. Performances analysis, reports and real time operation
are provided.
WLAN Controllers should be located physically in the Data Centres with physical independent
connections.
The WLAN system highly depends on the availability and redundancy of the Network.

There shall be a secure logical airport operations WLAN covering the staff buildings, both
terminals and adjacent apron and stands.
The airport operations WLAN shall support voice, video and data so as to deliver client services
throughout the airport buildings and adjacent apron areas.
There shall be a logical public WLAN covering the publicly accessible areas of the airport (e.g.
terminal building or Hotel).
The WLAN system shall be completely integrated with the LAN/WAN infrastructure, including
any authentication and network security systems.
The system shall have the capability to add new logical WLANs as required to support other
functions.
The design of the WLAN should be optimized to provide high capacity in the areas where usage
is predicted to be the highest.
The WLAN shall provide a captive portal for public wireless users to authenticate access to the
system, or to accept an appropriate Acceptable Usage Policy prior to guest access.
The WLAN shall permit seamless roaming between permitted access points for all applications
without loss of connection.
The WLAN shall have Quality of Service and prioritization techniques to support IP telephony
and real-time data traffic including video.
The system shall be able to monitor the bandwidth consumed by individual Service Set Identifier
(SSID’s).
The System shall allow guests, vendors, and partners to access the Internet while keeping the
internal network secure and easy to manage. The guest username and password shall be saved
for seven (7) days for the transit passengers and one (1) day for the office visitors.
10.5.5.1.1 VoIP compatibility
Voice over IP (VoIP) shall be implemented. The handset devices are included in the VoIP general
system, but WLAN shall be completely compatible with them.
To deploy a voice over WLAN solution, it is recommended to maintain a minimum power
requirement of -67dBm at the cell boundary. This shall be considered to achieve packet errors
of one percent or less and to achieve desired Signal to Noise Ratio (SNR) levels (25dB or greater).
It is recommended to obtain -67dBm cell ratio, with 15%-20% overlap to have optimized
network.
The design shall a roaming capability for WLAN data and voice users. When the wireless data
and voice users identify that the signal quality is reaching the minimal threshold level, it takes a
decision to initiate a handoff in order to connect to other Wireless Access Points offering better
signal quality.

Message mobility exchange
WLAN
WLAN controller
controller 11 WLAN
WLAN controller
controller 22
AP 1 AP 2
Client roams from point A to B
Figure 67-Inter WIFI controller roaming
Non-Functional Requirements
The Wireless Network should be a single physical IEEE 802.11a/b/g/n WLAN which should
support multiple logical networks, each comprising several unique Service Set Identifiers (SSID).
The design shall include inherent spare capacity to allow for the quantity of applications to
increase by 25% without the need of major re-engineering of the WLAN.
The centralized WLAN controllers shall be duplicated and located in both main Data Centres.
Wireless Access Points shall be installed at agreed locations in the airport buildings.
The WLAN system shall be based upon a network topology of centralized fully meshed WLAN
controllers that shall be clustered to ensure mobility across an entire wireless network.
Later design phases shall include a radio prediction survey to establish the number of AP’s and
their locations and shall confirm the coverage provided by survey and measurement of signal
strength.
The WLAN end-to-end latency shall not exceed 150ms.
The WLAN shall provide a Received Signal Strength Indication (RSSI) no less than -85dBm.
The WLAN shall automatically augment itself in response to external Radio Frequency (RF) &
Electromagnetic Interference (EMI).
In the event of failure of the WLAN controller to which an AP is connected the AP shall
automatically failover to an alternative controller.
Network equipment shall allow radio frequency to be selected by the software rather than fixed
at a certain frequency.
WLAN system components shall be fully integrated with the LAN/WAN system, exactly with
Access layer and Distribution layer.

WLAN controllers shall be connected to the Distribution layer of the airport network and APs
shall be connected to the Access layer of the network.
The frequencies used for WLAN communications shall be in 2.4GHz spectrum and 5GHz
spectrum. Due to its nature of interference, the UNII-2 band should not be allowed, and the use
of the rest of bands in 5GHz spectrum should be coordinated with the local telecommunications
authority.
The WAPs shall be placed at a suitable location to provide the uniform and complete coverage
across all facilities. Cells provide the coverage area for the WAPs. It shall formulate a honeycomb
pattern aligning them, leaving a hexagonal formation so that there are no blind spots.
The next figure shows the ideal distribution of WAPs.
AP
AP 11 AP
AP 22 AP
AP 33
AP
AP 44 AP
AP 55 AP
AP 66 AP
AP 77
n-2
n-2 n-1
n-1 nn
Figure 68-Cell Structure
The coverage and ratio of overlap shall depend upon the usage of the system components and
applications. Each WAP has a spherical boundary of RF coverage around it. In order to provide
the consistent coverage and availability across the facility, each of the cells shall join with each
adjacent cell at a coverage boundary that is greater than our desired minimal signal threshold
level.
The application of cell overlap is intended for VoIP clients as they would quickly roam to an
adjacent cell as soon as they experience packet loss. Where applicable, the cells shall be
overlapped by 15%-20% for inter-cell traffic handover so that the user shall not face
disconnection while moving from one cell to another.
The WLAN system coverage is also dependent on the type of rooms and size of the room. As
an approach to the WLAN system design, areas that have high voice and video traffic over the
internet shall have complete blanket coverage with cell overlap of 15% - 20% while areas with
low usage such as workshops, hangers and equipment rooms are covered with variable overlap.
Performance
The WLAN system shall be designed to support the operational functional and performance
requirements for a minimum of five hundred (500) simultaneous 802.11a/b/g/n.
A maximum capacity of sixteen (16) users per access point and a throughput of a minimum of
24mbps shall be provided at any given time.
A minimum signal of -67dBm shall be provided.
The WLAN system shall continue to deliver coverage and function with minimal degradation of
service in the event of any single component failure.
The WLAN shall achieve an availability of 99.9% over a year (526 minutes maximum downtime
per year).

The 802.11n WAP should be plugged into the Gigabit Ethernet switch ports (LAN/WAN) to take
full advantage of the throughput improvement of 802.11n.
Access Points
A Wireless Access Point (AP or WAP) is a station that transmits and receives wireless data and
connects wireless users to other users across the fixed network (LAN/WAN). It serves as the
point of interconnection between the WLAN and the fixed wired network.
The WAP shall be compatible with IEEE 802.11a/b/g/n and shall support IEEE 802.11af and
802.11at for Power over Ethernet (PoE).
The WAPs shall be Light Weight Access Points and shall use the following:
 Dynamic Transmit Power Control (DTPC) mechanism to communicate with the wireless
users;
 Control and Provisioning of Wireless Access Points (CAPWAP) to communicate with the
WLAN controller.
The WAPs shall be allocated in a manner that supports anticipated utilization patterns. The
WLAN design involves the use of both indoor and outdoor WAPs. The selection of a WAP shall
be based on the coverage range and transmit power requirement for each individual facility.
WLAN Controllers
WLAN controllers provide the central intelligence of the WLAN system and are responsible for
managing de AP’s. They perform real-time RF management and detection and avoidance of RF
interference. They also provide a common platform for their configuration and allow several
AP’s to work together in a unified manner.
The controllers have embedded software that detects the changes and resolves any problem in
real time by supporting dynamic channel assignment, load balancing, coverage gap detection
and compensation and dynamic power control, thus creating a self-organizing and self-
correcting WLAN environment.
Using clustering, logical groups of wireless controllers shall be created, which pro-actively share
network and user information for consistent wireless services and transparent roaming.
Controllers should be duplicated, and each group installed at a Data Centre. It is recommended
to install them in the same room as the core and aggregation switches.
WLAN Management System

A wireless LAN Management System shall be provided and integrated with the LAN/WAN
management system. It shall have the following minimum functionalities:
 Support the IEEE 802.11 MIB standard:

o Operational Scheduling;
o Auto discovery;
o Rogue detection;
o Group configuration;
o Remote configuration;
o Remote upgrades to WLAN controllers and AP’s;
o Performance monitoring for individual devices and the whole network;
o Secured Access.
 Alarm Display and Remote Notification.


WLAN system shall interface with the following systems:
 LAN/WAN:
o The physical network should be used to communicate the WAP with the
WLAN Controllers;
o Users can access the airport systems, or the Internet, from the WLAN and
through the LAN/WAN.
 VoIP:
o Wi-Fi telephones should use the wireless network created by the WAP.
o The communication between phones and servers should as well be trough
the WLAN and LAN/WAN infrastructure.
VoIP
AIRPORT NETWORK
WLAN
Figure 69-WLAN Integration Diagram

The WLAN Supplier shall be responsible for providing and maintaining an IP addressing scheme



Manufacturers: Access points and controller shall be supplied from internationally recognized
manufacturers including, but not limited to: Cisco, Aruba Networks, Extreme Networks, etc.
manufacturers.
manufacturer.
access points offered by the Supplier are of a make and type in common use in Saudi Arabia.
(as pre-installed within the Data Centers and comms rooms), shelving, support hardware (screws,
quantity documents.
Access Points Supports. Design Specifications

 Mounting kit for the Access Points shall be provided.
 Ceiling fixation supports shall be provided
 All mounting kits, supports and fixations are under this system scope.


All access points shall be identifiable to support maintenance technicians and make easier
For the access points to be installed in an interior controlled environment, the WLAN system
shall be operational in an ambient air temperature between 15 to 40 degrees Celsius. IT rooms
and Data Centres require this type of environment.
For the access point to be installed in an interior uncontrolled environment, the access points
shall support temperatures between 0 to 65 degrees Celsius.
For the access point to be installed at exterior environments, the devices shall support
temperatures between 0 and 65 degrees Celsius. Purpose-built to survive in the harshest
outdoor environments.

WLAN system shall comply with the following redundancy, scalability and reliability
requirements
Availability: The entire WLAN system shall provide a high availability. All configurations and
data used by the software shall be backed up on a daily basis to prevent data loss.
System stability: The system provided shall be equipped with a UPS solution to maintain the
system stability. Any power variation should not affect the quality of the picture nor the video
features.
Usability: The organization of information on the screen shall be clear. The information (Online
Help, Documentation) provided with the system shall be clear and concise. The Graphic User
Interface shall be user friendly.
Reliability: The system provided shall work 24 hours a day. The WLAN System shall have a high
Performance / Response time: The WLAN system shall manage high speed bit rate in real time.
Response time shall be low.
A list of parts which are unique to the system (such as switches or FO transceivers) and which in
case of failure would be considered critical and cause a suspension of service should be
provided.
The Availability of the entire system over a period of twelve (12) months shall be at least 99.99%.


The WLAN system shall be configurable depending assuming the future growth of Amaala
Airport. With the progressive development of the different stages of Amaala airport Master Plan
additional AP will have to be installed to cover the new environments to be built, although the
system will have capacity to assume this increase in the number of managed devices without
requiring any system upgrade or new investment. Infrastructure Requirements.
Scalability: For future expansion it shall be possible to include additional access points. The
WLAN environment will be able to support at least up to 30% access points more and will be
able to support a future growth in the next years of operation. System resources (controller
capacities, memory, network bandwidth) will be dimensioned accordingly.
The Supplier shall provide expansion and reserve capacities for any equipment, if required
Redundancy
WLAN controller shall be installed in the Data Centre at the airport.
The management software system to be finally deployed in the Data Centre should use the
hardware platform or a virtual server technology.
of the Data Centre respected. Reliability and cost shall be key decision features together with
 High Availability: A high-level of system availability is required. The System shall be
designed to meet the availability requirements. This may be met through high reliability
available in each component, through redundant servers, or a combination of the two.
 Hot Swappable: System shall be designed to allow for the replacement of failed or
failing components while the system is operating, up to and including replacement of
cards, components, and other discrete modules of the system.


The following table sums up in a high-level overview the deliverables to be provided by the PAS
WLAN-DES-1 System Detailed Design for installation Design Phase

WLAN -DES-2 Software Detailed Design (system architecture, Design Phase

WLAN -DES-3 Testing & Commissioning Plans Design Phase
WLAN -DES-4 FAT and SAT test Procedures Design Phase
WLAN -DES-5 Maintenance Plan Design Phase
WLAN -DES-6 Integration Plan and Interfaces Design Phase
WLAN -DES-7 Training Plan Design Phase
WLAN -DEL-1 Cable Management Document Delivery Phase
WLAN -DEL-2 Configuration Control Document Delivery Phase
WLAN -DEL-3 Test & Commissioning Reports Delivery Phase
WLAN -DEL-4 Integration tests Reports Delivery Phase
WLAN -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
WLAN -DEL-6 Application user manuals Delivery Phase
WLAN -DEL-7 As Built drawings Delivery Phase
WLAN -DEL-8 Coverage Survey Report Delivery Phase
Table 71-Project Deliverables

As it happens with the LAN/WAN, all staff working at the airport is a potential user of the WLAN.
For example, using their Wireless phones or personal smartphones.
Passengers should also become users of this system.
The maintenance and management of the system shall be in charge of Electronics &
Communications unit within the Maintenance and IT department.
Any Any User Using this system
06.04.00 IT Support Maintenance Maintenance and

Support
13.03.00 Handling User User For BRS use
13.04.00 Passenger User Internet Access
Table 72-WLAN Airport Organizational Units Involved

10.6 Master Clock System (MCS)
10.6.1 Introduction
A Master Clock System typically either uses an external network-based timeserver such as a
timeserver available on the Internet, or a global positioning system (GPS) receiver that serves as
its own timeserver.
The Master Clock system to be procured for Amaala Airport will facilitate the time
synchronization of all systems and devices throughout the entire airport, as well as to provide
an accurate time for all stakeholders, such as passengers, staff (operators, security…) and airlines.
Such procurement shall comprise the following components:
 GPS Antenna;
 Master Clock and Time Server Units;
 Analogue or digital slave time displays in various locations.
Typical locations for Slave clocks include:
 Operational Centres:
Airport Operational Control Centre, Security Centre, Data Centre, etc.
 Passenger Area
Mirage Passenger Terminal, Staff Passenger Terminal, etc.
 Other Facilities
RFFS, Air Traffic Control Tower, Cargo.

IEEE 802.1q VLAN Ethernet
ANSI/T1.101 Synchronisation Interface Standards for Digital Networks
NTPv4 (RFC 1305) Network Time Protocol Specification, Implementation and Analysis
IEEE 802.1x network security standards
IEEE 802.3af Power over Ethernet standard
Table 73-MCS applicable References, Standards and Regulations

The objective of the Master Clock system is to provide the airport with a highly accurate central
time reference available to all users and to drive time displays for passengers.
Technically and operationally speaking, it is extremely required to keep all systems and
processes synchronized with the same master time, and this is the main function of the MCS.
The system shall cover the airport needs about new systems synchronization for all the phases
regarded at the airport Master Plan.
The Master Clock system allows to other systems to offer the airport accurate synchronization
and presentation of information which is currently one of the major objectives of airports
globally.

The Scope of Work shall include, but not be limited to:
 This scope of work shall include all design, planning and coordination support
relating to the final placement of field devices to include but not limited to;
drawings, specifications, project plans, equipment, materials, labour and services,
not specifically mentioned or shown, which may be necessary to complete the
design and installation of the MCS;
 The scope of work shall include the development of interfaces to other systems
using the Airport Common Network;
 The scope of works for the MCS supplier is for the design and provision of a
scalable, reliable and highly available MCS to meet the security, safety and
performance needs of the airport.

A physical representation of the MCS System architecture has been presented below,
redundancy, time accuracy and high availability are the main design criteria. Integration with
other systems shall be essential to obtain the necessary data to undertake its function. Further
information about integration in section System Integration.
GPS Antennas GPS Antennas
Global Positioning System Global Positioning System
NTP Server 1 NTP Server 2
CORE Switches CORE Switches

DATA CENTER 1 DATA CENTER 2
AIRPORT NETWORK
Figure 70-MCS Architecture
All primary system servers (AODB, CUPPS, FIDS, etc.) shall obtain clock signal references directly
from the Master Clock. Subsequently connected devices will obtain time information from their
dedicated system server. As for example:
 Stratum 1: The Network Timer Server shall be at Stratum 1 level;
 Stratum 2: The AODB server will obtain clock directly from the Network Time Server
(NTS). This means that the AODB server shall be at Stratum 2 level;
 Stratum 3: Any device attached to a stratum 2 device is classified as a stratum 3
device.
It is worth noting that, in some cases, although a device such as a computer terminal may be
attached to a Stratum 2 server it may still receive its time from a higher stratum server.

The Time servers shall be installed in both Data Centres and will establish a peer group (NTP
Peering) by communicating with each other over the Airport Network.
Other considerations regarding system architecture are:
1. All systems will be configured with the two IP addresses of the MCS;
2. The MCS shall be configured in the network in order that all systems can
reach it.
10.6.5 General Systems Requirements

The objective of the Master Clock system is to provide the airport with a highly accurate central
time reference available to all users and to drive time displays for passengers.
The Timeserver shall be mounted in industry standard 19-inch racking. For the purpose of
design dual servers shall be supplied to accommodate redundancy across the Data Centres that
will be established at the new airport.
The Time Server shall be 10/100 Ethernet compatible.
The time server shall contain an oven-stabilized crystal oscillator to maintain the time signal in
the event of loss of the GPS signal.
The server shall synchronize with GPS time signals and include a suitable interface for the GPS
antenna.
The Supplier shall provide and install weatherproof GPS antennas including all mountings and
fixings.
The GPS antenna shall be suitably mounted to withstand the meteorological hazards.
The GPS antenna shall operate over a temperature range of -20C to +40C.
The GPS antenna shall be allocated in a position coordinated with the Architect.
The GPS Antenna shall be provided with protections to prevent electromagnetic surge and/or
lightning causing shutdown or damage to the master clock time server.
Design Criteria
The Master clock shall have outputs in the following formats:
 NTP V2, V3, and V4;
 RS232;
 RS485;
 SNMP v3.
When synchronized to GPS, the server shall be accurate to within 50uS of the UTC.
When the server is in stand-alone operation (i.e. without GPS synchronizing to the UTC) the
server shall be accurate to less than 0.1seconds/day.
Switching between Daylight Saving Modes shall be automatic.
The provided system shall include the ability to remotely manage the Master Clock.
Clients shall be synchronized by the server within 10mS (discounting network time delay and
jitter).


The Master Clock System shall act as an NTP server for attached network devices. The Master
Clock System shall provide time signals to each Stratum two (2) server and they, in turn, shall
disseminate accurate time to their respective attached system devices.
The Master Clock shall utilize NTP communications across the Airport Common Network.
The Supplier of the MCS shall liaise with the Client and other trade Suppliers installing systems
which require a time signal to ensure successful interfacing between the relevant system and
the Master Clock.
OTHER SYSTEMS
ERP VoIP WLAN PAS

OPERATIONAL
SYSTEMS
BMS MCS
Figure 71-Airport systems to be integrated with the MCS

The MCS Supplier shall be responsible for providing and maintaining an IP addressing scheme
which shall require client approval in accordance to LAN policies of the airport.

The MCS system shall be based solely on TCP/IP and capable of supporting this environment.
All components of the MCS system shall be redundant to ensure the continuation of service.
The Core MCS Equipment will be installed at two separate Data Centres with independent Power
Supply Circuits for the ensuring of higher level of the redundancy of the system.

MCS system has to be designed and implemented based on a high-speed LAN architecture with
Different segments of the switched Ethernet LAN must have the possibility to be configured for
different amounts of traffic in order to economically pair speed with need.
The MCS software shall be 64-bit and based on an open system architecture.
development environment. Software code and functionality shall be well documented in order
to facilitate maintenance by personnel other than the original programmer.
patches applied.

Software and hardware components such as GPS antennas, time server units, analogues and
digital displays and interfaces to other systems are included in the scope of the MCS.
manufacturers.
manufacturer.


quantity documents.
All systems should operate under Saudi Arabia’s environmental conditions.
The MCS system must be based on standard components which have already been used in
GPS Antennas operating temperature shall be prepared for the Amaala high temperatures.
Head End Equipment Capacities

Supply, install and commissioning of software application and any other software that may be
required to make the system fully operational to meet client requirements.
Regarding communications, the MCS deployment will fulfil the following requirements:
 The MCS system should be an IP-based system, with an Ethernet network and TCP
/ IP protocols;
 The equipment shall be accessible by telnet sessions for:
o IP Configuration;
o Setting time zone offset from UTC if any;
o Status reporting.
Regarding Energy, the MCS deployment shall fulfil the following requirements:
 For the Servers it will be necessary to have electrical connections of safe power,
coming from the UPS;
Supplier;

The MCS shall be an IP-based system and all wiring from all servers and display stations are
expected to be as high as possible using the CAT-6 UTP cable, with Ethernet and TCP / IP
protocols.
System Capacity
10.6.10.2.1 Scheduled Downtime

reasons for downtime, however, where components are duplicated; there shall be no
interruption to system services. The following reasons shall be acceptable causes of downtime:
 If the operating systems of the servers require maintenance or updates, or if the

servers require system maintenance, each server shall be brought down individually
to be updated/maintained, such that at no time is more than one server down;
 If the operating system of the end devices requires maintenance or updates, or if
the end device requires system maintenance, the end device that requires the
maintenance shall be brought down during non-peak hours of operation;
 The Employer may authorize maintenance/updates on the end devices during
other than non-peak hours if the particular end device is non-functional without
having the maintenance or updates performed.

The MCS system shall comply with the following redundancy, stability and reliability
requirements:
Availability: The entire MCS system shall provide a high availability. All configurations and data
used by the software shall be backed up on a daily basis to prevent data loss. A device shall be
considered available only if all components are operating and fully functional. Besides
scheduled downtime, as identified below, individual device availability shall be at least 99.5 %.
All systems, subsystems, software, and interfaces shall execute, without degradation, at the
scheduled periods and response times for the systems to be considered available. The systems
shall operate as specified twenty-four (24) hours per day, seven (7) days per week. Availability
of the overall system shall be at least 99.99%.
System stability: The system provided shall be connected to a UPS solution to maintain the
system stability. Any power variation should not affect the system features.
Reliability: The system provided shall work 24 hours a day. The system shall have a high MTBF,
and a reduced MTTR shall be achievable.

A list of parts which are unique to the system (such as oscillators) and which in case of failure
would be considered critical and cause a suspension of service should be provided.

With the progressive development of the different stages of Amaala airport Master Plan and
with the increase in the number of passengers and boarding gates, additional time displays will
have to be installed to cover the new environments to be built, although the system shall have
capacity to assume this increase in the number of managed devices without requiring any
system upgrade or new investment.
Scalability: The MCS to be procured shall cover the airport needs for all the phases regarded at
the airport Master Plan.
Redundancy
System servers shall be installed in the Data Centres at the Airport.
minimum.

reliability available in each component and through redundant servers;

 Servers shall utilize a redundant server pair with automatic fail-over to ensure that
performance and high-availability objectives are met without manual intervention;
technology;
disruption to the network or applications.

record. Additionally, the Network Management System shall receive a warning message on the
system administrator workstation, notifying of the failure. Server failures shall include any
hardware or software-based failure.
All failures of the system shall be logged at a central control point. The failure shall initiate
alarms and reports (e.g. time and date of failure event).
The MCS Supplier shall in their tender submission outline their vision for mitigating single points
of failure in the overall system.

materials as required by the Employer.

The following table sums up in a high-level overview the deliverables to be provided by the MCS
MCS-DES-1 System Detailed Design for installation Design Phase

MCS-DES-2 Software Detailed Design (system architecture, Design Phase

MCS-DES-3 Testing & Commissioning Plans Design Phase
MCS-DES-4 FAT and SAT test Procedures Design Phase
MCS-DES-5 Maintenance Plan Design Phase
MCS-DES-6 Integration Plan and Interfaces Design Phase
MCS-DES-7 Training Plan Design Phase
MCS-DEL-1 Cable Management Document Delivery Phase
MCS-DEL-2 Configuration Control Document Delivery Phase
MCS-DEL-3 Test & Commissioning Reports Delivery Phase
MCS-DEL-4 Integration tests Reports Delivery Phase
MCS-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
MCS-DEL-6 Application user manuals Delivery Phase
MCS-DEL-7 As Built drawings Delivery Phase

Main organizational units to be involve in MCS use and maintenance are presented below.
Any Any User Using this system
02.01.00 Airport Duty Managers User Universal Time Reference
02.02.XX Airport Operations User Universal Time Reference
05.01.00 Airport Security User Universal Time Reference
13.04.00 Passengers User Universal Time Reference
Table 75-MCS Airport Organizational Units Involved

10.7 Services
10.7.1 Supplier Responsibilities & Requirements

The Supplier shall be solely responsible for the design, selection of components and
materials, construction, manufacturing and installation techniques; for ensuring overall
systems integrity and full compatibility between major elements and all ancillary units; and
providing adequate training for employees to ensure successful operation of all the
equipment supplied.
The Supplier shall obtain all required permissions for civil works, local power supply,
telecommunications and other regulatory agency approvals.
The Supplier shall be responsible for all shipping and insurance costs as well as on-site
storage costs, customs storage, and all the applicable taxes in Saudi Arabia.
All training on system operation and general day to day maintenance shall be the
responsibility of the System Supplier and it shall be his responsibility to liaise with the
various Stakeholders to agree content and timescales of training.
The Supplier shall be responsible for any damage against existing properties and/or third
parties.
The Supplier shall have a local branch facility. Emergency service shall be available on a 24-
hour, 7-day-a-week basis.
The Supplier should have relevant experience in similar projects at airports.
The Supplier is also to proceed on the basis that design information has been developed
based on the Master Plan information which will need to be verified on site in terms of
setting out, levels and condition.
The Supplier is responsible to get the approval from the Client or the Design Consultant of
all presented deliverables and arrange all required coordination in case of variations
resulting from any change in the original Master Plan or during the construction phase.
The Supplier shall provide proof of their ability to supply quality long term system
maintenance and customer care facilities locally.
The Supplier shall have a locally based dedicated systems service infrastructure capable of
providing technical support on and off site at all levels together with a corresponding parts
replacement service.
The Supplier shall guarantee local representation of the company as a minimum during the
life of the warranty of the contract.
10.7.2 Stakeholder Engagement

The Supplier shall generate the detailed design delivery in coordination with the client and
the design consultant following the established decision-making processes to be settled
down in the project.
The Supplier shall lead the coordination activities with all stakeholders involved in the
design, use and maintenance.
Site inspections, meetings and design coordination particularly in respect of architectural
and infrastructure issues.

The Supplier shall liaise with the Client, Architect, Design Consultant, Security Agencies and
other appropriate parties to define the infrastructure required for each of the necessary
speaker type to be used.
The Supplier shall liaise with the Client, Design Consultant and other appropriate parties to
obtain the information necessary to establish an estimate of the network traffic utilization
profile.
The Supplier shall liaise with the Client and other appropriate parties to determine the exact
location and fixing of the required field equipment.
The Supplier shall be responsible for working with the Airport and the stakeholders to
develop the proper configuration and format for the system.
10.7.3 Installation
The following points explain the general requirements in order to accomplish a complete
functional deployment of the system.
Cabling
Both the structured data cabling and power cabling for the system are expected to be
provided by third party Suppliers, nevertheless, the following points describe the complete
general cabling requirements in order to deliver a full system interconnection. The detailed
scope of the Supplier in these terms needs to be specified with the Client. Meantime it is
assumed that the Supplier will be responsible for the complete installation, labelling and
testing of the cabling up to the closed connection outlet.
The structured cabling shall be CAT 6 and Low Smoke Zero halogen.
All the cabling shall be certified and finished in patch panels and sockets.
The cabling should finish in a male RJ45 to be connected to the monitors/controller.
All the cabling, patch panels and intermediate boxes shall be labelled as per labelling
specifications detailed below.
The maximum distance between the displays and the network distribution rooms for the
Ethernet cable shall be less than 95m.
The Supplier shall provide the cable certification and validation to the Employer.
Power/Grounding Requirements
The equipment shall operate from a power source of: 230 V ± 10%, 50 Hz ± 5% and from
the Uninterruptible Power System (UPS) supplied by a third party Supplier.
The connection to the power outlet at the installation site shall be the responsibility of the
Supplier. Supplier shall coordinate all power requirements at the design stage in order to
arrange the location of the power points as close as possible to the equipment final
location.
The Supplier shall provide the estimated consumption of all equipment so the MEP Supplier
may size the power installation accordingly. The Supplier shall specify itemized the
electrical capacity in Watts needed for the system connection.
The system will be connected to the Airport UPS.

All the electrical boards and cables shall be labelled.

All the support mechanic parts will be connected to the building earth.
Labelling
Labelling both equipment and cables is not only a good practice but also a requirement in such
big facilities as airports where different types of systems hardware interface with each other.
All active and passive equipment shall be labelled. The label shall include the system information,
building (XX), floor (YY), room (ZZ), Equipment name (SW) and identification number (001).
All this information shall be included in a tool/system that will be able to link the equipment
installation place with the equipment information (Manufacturer, S/N, P/N, etc.).
Each cable shall be identified at its extremities, in junction boxes and at manholes by a
coloured label containing the following information, as a minimum:
 Cable function;
 Cable number: This number shall identify the nature of the cable and its source and
destination (indicating the connected equipment and its location at both ends of
the cable).
The Supplier shall provide the appropriate cable documentation which shall contain the
following information for each cable:
 Source. Equipment and location;
 Destination. Equipment and location;
 Cable type;
 Cable function/service;
 Cable number;
 Technical description.
10.7.4 Testing and Commissioning

The supplier shall provide Testing Plans and procedures for Factory Acceptance and Site
Acceptance Tests and will contribute for the generation of the integration and operation
testing plans and procedures wherever they may be involved.
The supplier shall detail the suggested procedure to follow during the commissioning
stage, including the schedule and the required participants for each of the steps.
The supplier will be responsible for the integration, testing and commissioning of the
system as a whole and with third party interfaces, making sure that the system is fully
operational and complies with all the requirements explained along this document.
The supplier shall participate in all the tests processes whether they are required, such as
the integration and the operation tests.
All tests reports should be delivered at the end of the testing as part of the commissioning
and acceptance process.
Factory Acceptance Tests
The Factory acceptance test shall ensure the proper operation of the system between the
supplier/manufacturer and the Supplier.
The Supplier shall ensure that all equipment and materials are in good working condition
prior to and after installation.

The Supplier shall invite authorized supplier representative(s) to confirm and accept that
proper installations, termination and another technical requirement are attained.
The Supplier shall ensure a Factory acceptance test sheet properly filled in by the
supplier/manufacturer before the actual testing and commissioning stages.
Site and System Acceptance Tests
After all work is completed, and prior to requesting the acceptance test, the Supplier shall
conduct a final inspection, and pre-test all equipment and system features.
During the acceptance test, the Supplier shall demonstrate all equipment and system
features to the Client/Consultant. The Supplier shall remove covers, operate equipment,
and perform other reasonable work as requested by the Client/Consultant.
Any portions of the work found to be deficient or not in compliance with the project
drawing, specifications and the Supplier Design shall be rejected. The Supplier shall correct
all deficiencies in accordance with the General Contract Requirements.
Upon completion of the installation activity, the Supplier shall test, start-up, commission
and handover the system to the Client/Consultant.
The Supplier shall perform the following tests as required for the system with the presence
of the Client/Consultant:
 Installation Check Report;
 Power "On" test;
 Integration test;
 Power "Off" test (test of back-up power sources and failover).
The Supplier shall provide a detailed test plan with all relevant functions of the above-
mentioned tests. The test plan shall be reviewed and/or approved by the Client/Consultant
prior to testing.
The Supplier shall ensure proper coordination in testing each relevant system. The Supplier
shall guarantee to the Client/Consultant that each system is ready for testing.
The Supplier shall incur all cost related functions of the acceptance test.
Upon reaching substantial completion, the Supplier shall perform a complete test and
inspection of the system (commissioning). If the system is found to be installed and
operating properly, the Supplier shall notify the Client/Consultant of the Supplier's
readiness to perform the formal test and inspection of the complete system.
Integrated System Tests
The Supplier shall undertake system-wide integrated testing to verify, test and commission
all interfacing systems & equipment.
The integrated system tests shall verify the functionality of the interfacing systems and
confirm that the respective systems and equipment perform and interact satisfactorily and
in accordance with the Requirements.
The Integration test shall not limit the warranty of the system.
The Supplier shall be responsible for inspecting and testing the complete system.
The Supplier shall start up and operate the system for a trial period to ensure that it
operates correctly.

The Supplier shall demonstrate the network resilience by creating a series of failures (i.e.
cutting power to equipment, pulling out cables, etc.) across the different components.
The Supplier shall supply a list of the 'failures' to be simulated including the functionality
that is to be tested as well as the anticipated outcome. The list shall be approved by the
Client/Consultant before the test commences.
The Supplier shall provide the system test strategy, including various test environments
through initial software customization to commissioning; resources; data; tools;
documentation and defect management.
The Supplier shall produce a detailed test plan covering initial software customization
through to commissioning, to include functional and non-functional requirements testing
and manage all systems test teams to complete test schedules specified therein, ensuring
defects are managed appropriately and in accordance with agreed entry / exit criteria, test
cases and schedules for acceptance of all systems individually and for all integrated systems
within the confines of the agreed detailed time program.
Tests after Completion shall be conducted following issue of a Taking-Over Certificate of a
section or the works, as applicable.
ORAT Activities
The organization and execution of all ORAT activities to take place after ICT commissioning
will be the responsibility of the Design Consultant. Nevertheless, the Supplier is expected
to assist those activities in each of the steps that may be related to the system provided.
Typical phases where the Supplier shall be involved:
 ORAT set-up;
 Operational Preparation;
 Training and Familiarization;
 Operational Trials;
 Terminal Transfer;
 Opening Support;
 Post Opening Support.
10.7.5 Training
The training program shall ensure that the staff is fully trained in handling the individual
units, subsystems and the full systems. The scope shall include, but not be limited to:
 Educational requirements;
 Operational procedures and measuring techniques;
 Maintenance procedures;
 System design including architecture, functionality, performance and non-
functional characteristics;
 Trouble shooting;
 Quality management;
 Health and safety issues;
 Environmental issues;
 Risk assessment and management;
 Content and familiarization with O&M (Operation & Maintenance) manuals;
 Business continuity strategy & disaster recovery.

Training shall be provided to trainers and selected operational and maintenance staff for
onward training. The staff shall include outsourced operational and maintenance entities.
Attendees shall include, but not be limited to:
 Trainers;
 The technical management;
 Engineers;
 Airlines Operators;
 Maintenance staff.
Factory Training
Technical Factory Training to be performed together (not at same time) with FAT within the
Factory Dependencies.
The training shall be based on system functions, configuration, trouble shooting and
maintenance
On Site Training
Technical and Operational training to be performed before the SAT.
During the system installation the Supplier shall offer On the Job Training (OJT) without any cost
to the system technicians.
On-site training shall be offered to System Administration, System Operation and Maintenance.
Training Duration will vary for each of the Systems.
10.7.6 Technical Documentation

Refer to each system section “Project Deliverables” for the technical documentation expected
for each of the systems.
All documentation should be in English unless otherwise stated.
Supporting documentation: Each tender shall be supported by adequate technical
documentation including system and data sheets, performance sheets, drawings, illustrations,
photographs, etc., in order to facilitate a complete and detailed evaluation of the tender.
The financial offer shall provide, as a minimum, prices itemized to the level agreed in the
instructions to Suppliers.
The proposal shall include documentation related to the operational commands, preventive and
corrective maintenance routines, fault analysis and other information which the Supplier deems
necessary.
Project Implementation: The Supplier shall submit with the tender a proposed schedule setting
out the anticipated program of major activities of the design, fabrication, supply, installation of
the systems, Site Acceptance Tests, training, integration and commissioning.
System Design Document (SDD)

The Supplier shall submit, within thirty (30) days after contract signature, a System Design
Document (SDD) in English.
The SDD shall be delivered in hard copy. The Supplier shall also provide a soft copy of the SDD.

The SDD shall include, amongst others:
 Detailed listing of the scope of supply: COTS, main installation material, such as
trays, pipes, etc.;
 All relevant technical descriptions of the equipment hardware/software based on
the personalization of the contractual configuration;
 System architecture;
 Scaled and detailed equipment floor plans and equipment location drawings;
 Cable routing and interconnections;
 Supports Designs;
 Civil works specifications / requirements (if any);
 A complete and detailed final work schedule.
The Supplier shall update the approved project plan on a bi-weekly basis until contract
completion.
Design Review Meeting: The Supplier shall arrange a Design Review Meeting within two
(2) weeks after submitting the revised SDD. The meeting shall be held between the Supplier
and the Employer´s appointed representatives, at a mutually agreed location.
The purpose of the meeting shall be to review the system design as outlined in the SDD.
The SDD shall be subject to the Client/Consultant´s review and approval.
In order to facilitate the review, the Supplier shall provide a spreadsheet indicating the
documents that are part of the SDD (including drawings, datasheets, etc.), version number
and submission date. This document will be utilized to keep track of the changes in the
SDD documentation, as well as the clarifications requested by the Employer. The Supplier
will update this spreadsheet with each SDD submission.
If the document(s) in question are rejected, the Supplier shall have fifteen (15) days to
correct the document(s) and revise them at no additional cost.
The Supplier should assume the responsibility of adapting the design in case of changes in
the civil works or the Master Plan and follow the previously agreed change management
process together with the Client/Consultant in order to manage any impact in the project.
10.7.7 Maintenance & Warranty

The supplier shall also consider in the proposal all the maintenance works (both preventive
and corrective) necessary for the system including the equipment warranties for two years
after the system commissioning, ensuring full time availability for local support to the Client.
An optional extension for two additional years of such System maintenance activities shall
be quoted.
The Supplier shall offer a commitment that all products supplied shall be supported for a
minimum of ten (10) years following range replacement or obsolescence.
The Supplier shall support the equipment 24/7, 365 days a year. Proposed SLA conditions
for such support shall be specified and quoted by the Supplier.

Sufficient spares shall be provided for the system such that the reliability, availability and
maintainability figures specified can be sustained following issuance of Taking-Over
Certificate and shall demonstrate, that the proposed spares are sufficient through the use
of appropriate techniques to provide evidence to this effect.

11 SECURITY SYSTEMS
11
12 | SAFETY SYSTEMS
11 SECURITY SYSTEMS
11.1 Security Concept Overview
11.1.1 Acts of unlawful interference

Criminal intervention in aviation is nearly as old as commercial flights. The first record of a
hijacked aircraft goes back to 1930, when a Pan American mail-plane was hijacked by Peruvian
revolutionaries seeking to drop leaflets over Lima. Security-related incidents tended to be
dominated by aircraft hijacking and bombings for several decades thereafter, usually by persons
seeking expeditious political asylum, rather than political leverage.
The situation changed dramatically in the 1980s with not only the appearance of terrorist
bombings of aircrafts, but also with direct attacks on Airport Passenger Terminal Buildings
(PTBs).
Beginning with Rome and Vienna airport attacks on 27th of December 1985 and the TWA Flight
840 bombing, radical organizations sought to create terror and call attention to their causes by
exploiting landsite security gaps and the destruction of aircrafts in flight.
The International Civil Aviation Organization (hereafter ICAO), as specialized agency of the
United Nations and vested with international authority (among signatory states including the
Kingdom of Saudi Arabia) defines Aviation Security as the protection of Civil Aviation against:
“Acts of Unlawful Interference”.
In accordance with ICAO document 8973, 11th edition, examples for acts or attempted acts of
unlawful interference include (for guidance purposes):
 Unlawful seizure of aircraft in flight;

 Unlawful seizure of aircraft on the ground;
 Hostage-taking on board aircraft or on aerodromes;
 Forcible intrusion on board an aircraft, at an airport or on the premises of an
aeronautical facility;
 Introduction on board an aircraft or at an airport of a weapon or hazardous device
or material intended for criminal purposes;
 Communication of false information such as to jeopardize the safety of an aircraft
in flight or on the ground, of passengers, crew, ground personnel or the general
public, at an airport or on the premises of a civil aviation facility.
11.1.2 Airport Security Concepts

Based on the different Standards and Recommended Practices (SARPS) of airports, there are
three basic concepts that must be considered during the design stage of security measures:
 The characteristics of the airport Security Zones, such as air, land, safe, unsafe,
sterile and non-sterile areas of the airport;
 The necessity of monitoring and control of the basic operation processes of the
airport;
 The characteristics of Internal Areas, due to the activity carried out in it, its assets
and users.

12 | SAFETY SYSTEMS
Security Zones
The first basic concept to consider in the protection of an airport is the Security Zones, for the
purposes of common understanding, based on ICAO and others SARPS documents, the
definition we have in this regard is as follows:
 Public parts: Areas of an airport, adjacent land and buildings or parts thereof that
are not aeronautical parts, identified as such by the State and the pertinent entities
in their security programs.
 Land side: The portion of the airport accessible to the public and employees which
have not passed through a Security Screening Check Point (hereafter SSCP).
Landside normally includes airline ticket sales offices, check-in areas, luggage drop-
offs, luggage claim, services areas, bars, and restaurants.
Security Screening Check Points or SSCPs situated in this area serve as border
between Landside and Airside.
 Air side: The portion of the airport accessible only to the public, Visitors, and
employees after they have been Screened Passing Successfully Security (SSCP) and
have been authorized to proceed to an aircraft or other restricted areas of the
terminal building or controlled parts of the airport in general.
These areas normally include airline service areas, arrival/departure gates, waiting
or holding areas, retail or mall establishments and restaurant areas.
 Secure area: The part of the airport that relates to the delimitation of the space
that has been secured or cleared by airport operations and security and all persons
who enter this area have successfully passed through a security checkpoint (located
in Airside or Landside).
 Sterile area (also known as a Restricted Security Zone): It is the portion of an airport
located between inspection points and aircraft, where access is only allowed to
passengers who have a valid boarding pass or staff with valid "ID" (identified and
equipped with a card identification). All of them will have been previously
inspected.
Basic processes
The second basic concept in the protection of airports is the operation processes, at Amaala
Airport security measures must monitor and control the following:
 Passengers;
 Employees;
 Pilots and cabin crew;
 Authorities;
 Visitors;
 Baggage;
 Supplies, including fuel;
 Vehicles;
 Waste.

12 | SAFETY SYSTEMS
Internal Security Area

The third concept to consider in the protection of an airport is the "internal security area", which
is any physical location on the scene differentiated from the others by the activity carried out
on it, its assets and users.
The main “internal security areas” existing at Amaala Airport are identified below, which may
correspond to one building by themselves or may exist in several in the same building.
 CPD;
 Operation / Control Centres;
 Boarding / disembarkation area;
 Inspection / control areas;
 Waiting room;
 Offices;
 Transformation centre;
 Energy distribution rooms;
 Network equipment rooms;
 Air conditioning rooms;
 BHS;
 Counter service for billing / information / dealers;
 Security forces dependencies;
 Authorities area;
 Prayer areas;
 Rent car facilities, resort transfers;
 Public parking / employees / VIPs.
11.1.3 Philosophy of Protection
Airport Facilities Classification

The previously defined concepts (security zones, processes and internal security areas)
determine the basic conditions of the scenario to be protected, in this case Amaala Airport, and
on which the catalogue is developed in the next sections of the design. of the protection
measures to be implemented.
According to the following basic classification:
 Facility Security Level 1:

All Airport facilities with no direct functional impact on the Airport operations
and/or Airport personal.
All Airport facilities where staff or systems are involved for Airport Security, Airport
Safety and Airport Operations.
This classification applied for Airport facilities with a Landside/airside Access

12 | SAFETY SYSTEMS
Protection Measures
The catalogue that will be developed, will be based on the different Standards And
Recommended Practices (SARPs) of airports, considering it necessary to give priority to a
philosophy of preventive actions over those of a corrective type, which schematically means:
Action Objective Mean of Protection

To hinder The presence of the risk-causing agent Passive technical means
To identify The presence of the risk-causing agent Active technical means
To reduce The effects of the risk-causing agent Organizational means
Table 76-Philosophy of protection
Based on the prevention criteria presented, the philosophy of protection in all airport areas is
proposed through the creation of different "security circles or sectors", which allows us to
escalate and progressively manage risk at different levels; each of which with certain objectives
and corresponding means of protection. Within the scope defined in this design document, we
identify:
 Passive technical means: Initially, they are not the object of design of this
document, but they are identified since in certain systems specific requirements
must be established in this regard.
 Active technical means: They are the basic design object of this document and its
development is carried out in the next sections.
 Organizational means: They are the set of human resources and procedures on
which the airport security operation is based. Identification is carried out in this
document, but not their development.
11.1.4 Security organization

Airports generally dispose of a single power, responsible for Airport Security, assigned by the
competent state authority and it is commonly recognized that the airports director shall act as
this “single power”. Airport Director will normally delegate his mandate in a Head of Airport
Security.
In the case of the Kingdom of Saudi Arabia, according to the information received (Master Plan),
the organization and distribution of functions in the security operations of the Amaala airport,
that is, the main users of the security systems to be designed, are:
RSAF Responsible for airside security systems, including AOCC Airport Operation
Control Centre for security matters, permanent command post and mobile
command post.
GID Responsible for airside security check and screening in Passenger Terminal
Buildings and airside main gates.
POLICE Responsible for airport security in the landside areas.
ROAD POLICE Responsible for road security in the landside roads within the airport, and
airport main gate.
CUSTOMS Responsible for screening and customs import/export within the PTB.
IMMIGRATION Responsible for border control in international passengers (inbound-
outbound),
Table 77-Organization and Distribution of functions in the Security Operations of the Amaala Airport

12 | SAFETY SYSTEMS
11.2 Security System Bottom/Top Classification
11.2.1 Structure of Systems

With general criteria, for airport security systems and the corresponding protective equipment
to be used, at the level of basic technical structure, three types of components shall be
considered:
Field Equipment
11.2.1.1.1 Passive measures
It should be noted that, initially, the design of the passive technical means used in security are
not the object of this document, aimed at delaying the materialization of a risk, by applying
elements that hinder the presence of the causal agents.
Below, their basic relationship is presented, as they have a direct impact on the operation and
performance of any of the different systems to be implemented and in certain systems specific
requirements must be established.
FIELD EQUIPMENT – PASSIVE MEASURES

 Doors  Trellises
 Barriers  Shields
 Fenced  Container elements
 Locks and closing mechanisms  Step regulating elements
Table 78-Field equipment – Passive media
11.2.1.1.2 Active measures
Active technical protection measures are those that complementing the existing physical ones,
must achieve an effective response to a previously evaluated risk.
This equipment is distributed throughout the different areas of the airport and within the
security control centres, in accordance with the coverage criteria assigned to each of the
systems.
The basic equipment identified as the first level of the systems structure is the one presented
below:
FIELD EQUIPMENT – ACTIVE MEASURES

BASIC EQUIPMENT PANEL EQUIPMENT
 Cameras  Monitors
 Alarm Controller  Videowall
 Intrusion detectors  Video Storage
 Alarm push buttons  Printer badging
 Access Controller  Workstation
 Keyboard
 Card readers
 Biometric readers
 Output trigger
 Intercom
 RX machines
 ETD
 WTMD
 HHMD
Table 79-Field equipment – Active media

12 | SAFETY SYSTEMS
Control System
The second level of the systems structure is the one that controls and monitors certain field
elements under specific configuration and functionality. Basically, they are software programs,
installed in the corresponding CPD, main and backup, in redundant configuration.
The identified control systems are those presented below:
CONTROL SYSTEMS
BASE APPLICATION AUXILIARY MODULES
 Closed Circuit Television (CCTV) System  Video Analytics System
 Security Access Control System (SACS)
Table 80-Control Systems
Management System
The third level are basically platforms that integrate various of the existing control systems and
some specific field element, facilitating integration between these and other airport applications.
They are also installed in the corresponding CPD, main and backup, in redundant configuration.
The identified management systems are those presented below:
CONTROL SYSTEMS
 Security Management System (SEMS)
Table 81-Management Systems
11.2.2 General architecture

An overview of the architecture of the different Security Systems to be implemented is identified
in the following scheme:
Figure 72-Architecture Security Systems

12 | SAFETY SYSTEMS
11.2.3 Integration scheme

As indicated in the systems description, the management applications are the elements that
make the interconnection between the different control systems and their equipment. Likewise,
they are the elements that are foreseen with the capacity to interrelate with other airport
systems.
Control systems, also the ability to integrate with each other and with external applications,
usually for updating their databases.
Information on the specific integration requirements of each one of them will be expanded in
the different chapters of the systems description, but an overview of the basic links of the
different Security Systems is identified in the following diagram:
Figure 73-Security systems integration scheme

12 | SAFETY SYSTEMS
11.3 Security Access Control System (SACS)
11.3.1 Introduction
The Security Access Control Systems (SACS) addresses the need to control the passage of staff
(not passengers) into secure and sterile areas in line with the regulatory requirements and the
Airports specific Security Program (ASP). These systems are not designed to control the access
of passengers and specifically not for the “Trusted” or “Registered” travel program.
Those responsible for airport security want to be able to control and monitor access to airport
facilities in real time. The result is that Security Access Control Systems are increasingly being
integrated with both airport’s IT network.
At a general level, access control is divided into three basic parts:
 Security Access Control:

System object of this section.
 Airport Personal Identity Card (APIC):
A common and standard element of personnel identification.
 Identity Management System (IDMS):
It provides services for the APIC request, identity proofing, verification, background
investigation and validation of an Applicant prior to APIC Card issuance
(*) APIC and IDMS will be treated in next section.
Also, the new market trends, complementing the basic functions of a SACS, introduce functional
improvement features through the following modules or subsystems:
 Intrusion Detection System (IDS);

 Security Intercom System (SIS).
Modules that will be addressed within the scope of the SACS.

ICAO Annex 17 Security - Safeguarding International Civil Aviation against Acts of
Unlawful Interference‖ and Annex 9 ―Facilitation
ICAO Doc. 8973 – Restricted ICAO The Aviation Security Manual 10th Edition 2017
EC No. 300/2008 Regulation (EC) No 300/2008 of the European Parliament and of the
council of 11 March 2008 on common rules in the field of civil
aviation security and repealing Regulation (EC) No 2320/2002.
EU No. 185/2010 Commission regulation (EU) No 185/2010 of 4 March 2010 laying

down detailed measures for the implementation of the common
basic standards on aviation security.
TSA - Title 49 – PART 1540 Civil aviation Security General Rules.
TSA - Title 49 – PART 1542 Airport Security.
TSA - Title 49 – PART 1544 Aircraft operator Security.
TSA - Title 49 – PART 1546 Foreign Air Carrier Security.
TSA - Title 49 – PART 1548 Indirect Air Carrier Security.
TSA - Title 49 – PART 1549 Certified Cargo Screening Program.
TSA - Title 49 – PART 1550 Aircraft Security Under General Operating and Flight Rules.

12 | SAFETY SYSTEMS

EN 50133-1 Alarm Systems – Access control systems for use in security
applications- System Requirements
EN 50133-7 Alarm Systems – Access control systems for use in security

applications-Part 7 Application Guidelines.
BS EN 50133-2-1 Alarm systems. Access control systems for use in security

applications. General requirements for components.
BS EN 60839-11-1:2013 Alarm and electronic security systems. Electronic access control

systems. System and components requirements.
BS 7799-1 Information Security Management – Part 1: Code of practice for

information security management.
BS 8220 – 2 Security of Buildings Against Crime Part 2 – Offices & Shops
BS 8220 – 3 Security of Buildings Against Crime Part 3 – Warehouse &

Distribution Units
BS EN 179 Building Hardware. Emergency Exit devices operated by a lever or

push pad
NFPA 80 Standard for Fire Doors and Other Opening Protective: 2010 Edition
NFPA 101 Life Safety Code, 2012 Edition
NACP 30 NSI Code of Practice for Planning, Installation and Maintenance of

Access Control Systems
DD 243:2004 Installation and configuration of intruder alarm systems designed to

generate confirmed alarm conditions. Code of practice
PD 6662: 2010 Scheme for the application of European Standards for intruder alarm
systems
BS 7858:2006 Security screening of individuals employed in a security environment
BS EN 1303:2005 Building hardware. Cylinders for locks. Requirements and test

methods
BS ISO/IEC 19785-1:2015 Information technology. Common Biometric Exchange Formats

Framework. Data element specification.
BS ISO/IEC 24708:2008 Information technology. Biometrics. BioAPI Interworking Protocol.
LPS 1175: Issue 5.1, 2004 Specification for testing and classifying the burglary resistance of
building components, strong-points and security enclosures. All
other relevant BS EN standards
Table 82-SACS applicable References, Standards and Regulations

12 | SAFETY SYSTEMS
Basic functions
SACS is based on a reading terminal of the APIC, linked to a control unit, which when verifying
the access privileges assigned to the user, allows or does not automatically allow entry to a
certain room, releasing the existing physical lock (door , barrier, etc.).
The SACS System will allow airport security responsible to straightforward transfer its protection
policy to the access control installation and manage as well as monitor the systems; profiles and
access routes to restricted areas with calendar and timetables, location of persons, capacity
control, real-time alerts, list of events, etc.
The SACS System main functions are:
 Deterrence:
The visible presence of control elements may deter the potential penetrator that is
seeking unauthorized access.
 Prevention:
The system will allow the access to be unlocked only for authorized persons.
 Detection:
The system will activate an alarm signal if the input is forced.
 Traceability:
The system can provide a traceability of the actions performed and thus identify a
person who does not act according to established standards.
Centralized control
The SACS is an IP-based system that uses "controllers" directly connected to the security
network, equipment that can verify the access privileges of the accredited person and thus
regulate entry to the different areas of the premises.
The field elements, through the "Access Controller" must transfer the information of all the
events occurred to the "Access to the server", as well as update the data in a bidirectional way
about the personnel and the assigned privileges.
All these processes are carried out automatically, but it is required that the information be
controlled centrally, due to the possible presence of certain incidents of use:
 The so-called “BUDDY” effect facilitated by an authorized person;

 The one known as "TAILGATING", where an unauthorized person follows an
authorized user;
 The incorrect closing of an access, due to obstacles or other circumstances, after
the passage of the authorized party;
 Force a door;
 The use of a lost or stolen card.
It is the function of the system operators to control the incidents that may occur, through the
Workstation of the different control centres, which provides them with real-time information on
the events that are occurring.
The operator also has the ability to centrally lock certain points in the facility or free others due
to emergency situations.

12 | SAFETY SYSTEMS
Identification Technologies
SACS can address the control of one or more of the three factors that identify an individual:
 "What you have": Personal ID card;

 It is currently in common use to utilize contactless card technologies, the credential
being a conventional proximity card or a high-frequency transmission smart card
(Mifare);
 "What you know": PIN codes: (Personal identification number);
 "What you are ". Biometric characteristics;
 As an additional factor to verify the identity of the person requesting access, it is
not a regulatory requirement, but there is a tendency to implement it at high-risk
points.
The current design envisages the use of accreditation reading terminals with the complementary
PIN option. The use of biometric terminals is not initially established, but the general
characteristics of the system will establish the requirement of a possible change to a biometric
terminal without having to carry out additional installations or incorporate complementary
licenses.
IDS Module
The SACS will have the capacity to manage the events / alarms that it generates in the
monitoring of the closing elements (doors, barriers ...) and other alarm signals of auxiliary
elements that are considered necessary.
The trend in the security of airport facilities is to incorporate signals such as:
 In doors destined to processes of emergency or logistic, not destined to habitual

flows of the personnel;
 In critical areas for exploitation, where the presence of personnel should not be
habitual;
 In risk areas whose activity is a single work shift, there are wide time margins
without personnel presence;
 In access to stays of a technical nature, of low use and that are not considered in
the program of control of the SACS;
 In support of internal personnel, especially of attention to the public, as an element
to alert to situations of coercion / panic.
The IDS module is fully integrated into the SACS control platform and at field equipment level
has the following elements:
 Detectors;
 Push-buttons;
 Alarm Controller.
SIS Module
The centralized management of the security facilities, with control and monitoring of the
different personnel flows, requires at certain times to have intercommunication at the control
points between the users and the Control Centre staff, in order to answer queries, resolve
incidents or activate alternative access procedures.
The trend in the security of airport facilities is to incorporate the SIS (Security
Intercommunication System) into the SACS itself, through the availability of "Access Controller"
that have Audio/Video over IP service and allow the integration of intercom equipment.

12 | SAFETY SYSTEMS

According to the exposed, the architecture of the system is the following:
Figure 74-SACS Architecture
As defined in the section on Airport security concepts, there are three (3) basic concepts that
shall be considered during the design stage of security measures:
 The characteristics of the Airport SECURITY ZONES, such as air, land, safe, unsafe,
sterile and non-sterile areas of the Airport;
 The necessity of monitoring and control of the basic operation processes of the
Airport;
 The characteristics of INTERNAL AREAS, due to the activity carried out in it, its assets
and users.

12 | SAFETY SYSTEMS
11.3.5.1.1 Boundaries
The rules of flows or transits that can occur in the airport environment and shall be controlled,
are summarized in the following scheme:
Figure 75-Airport Security Zoning
The definition of the security areas implies the notion of boundaries. In an airport terminal
building, one may define four (4) types of boundaries, among which two (2) are Security
boundaries:
 Security boundaries:
o Secured / Non-Secured;
o Sterile / Non-Sterile.
 Non-Security boundaries:
o Inbound / Outbound of immigration/emigration border;
o Inbound / Outbound of customs border.
To each boundary a special type of access and procedure is associated where for the limits of
security the basic criteria are:
 The change from secure to non-secure zone implies controlled access;
 Passing between two secure zones may also involve controlled access (for being
different access privileges);
 The passage from sterile to non-sterile zone involves a security check (inspection).
The determination of boundaries is therefore an important element for the design and
boundaries between the different areas should be made clear by the architectural design:
 Shall be materialized by a physical separation such as a wall.
 The number of communication points between controlled and non-controlled areas
shall be reduced to the minimum.
 Access points to Secured and Sterile areas should be fitted with closing devices and
with automatic or attended access control features. This is the purpose of the following
chapters.
This is the purpose of the following chapters.

12 | SAFETY SYSTEMS
11.3.5.1.2 Door Types
At a general level, the main application of access control is in the communication points that
can be identified in the exposed limits are:
Type Entrance Sort Temporary Emergency Monitored

01 FREE FREE NO NO / SI NO
02 FREE FREE NO NO / SI YES
03 CONTROLLED FREE NO NO YES
04 CONTROLLED FREE YES NO YES
05 CONTROLLED CONTROLLED NO NO YES
06 CONTROLLED CONTROLLED YES YES YES
07 CONTROLLED CONTROLLED/FREE NO YES YES
08 PROHIBITED Prohibited NO YES YES
09 PROHIBITED FREE NO NO YES
10 PROHIBITED CONTROLLED NO NO YES
Table 83-Doors Type
 Where, for security criteria, it is established:

o Entry (E). Flow of personnel from the exterior of a building to the interior. Inside
a building, the flow that occurs between different functional areas (considering
the lowest risk to the highest risk);
o Sortie (S). Traffic contrary to that defined in the previous section;
o Temporary (T). Controlled access with local release option, by authorized
agent;
o Controlled (C). Door where there is an access control mechanism with personal
identification and assigned privileges;
o Prohibited (P). There is no mechanism that allows the passage.
o Free (F). There is a mechanism that allows free movement.
o Emergency (Eg). Exit door of a space or area belonging to an evacuation route;
o Monitored (M). Door that has elements for centralized status monitoring.
11.3.5.1.3 Transition Criteria Secured / Non-Secured
The main airport services and corresponding transits to be covered at the Amaala airport
complex are:
 Parking’s;
 Passenger processing area;
 Boarding damper;
 Salons y waiting areas Landside;
 Awaiting gate pods;
 Circulation areas;
 Bathroom, Trash and staff facilities;
 Office installations;
 Customs Facilities;
 Storage Facilities and GSE;
 Immigration Service Facilities;
 Prayer rooms;
 Technical and Handling Installations;
 Intermodal Transport Interchange;

12 | SAFETY SYSTEMS
 Facilities for Ultra High Net Worth Individuals. (UHNWI);

 Baggage carrousel(s);
 Boarding gates.
For the assignment of one type of security to each of the doors or another in the transitions
between SECURITY USES, the following criteria are used:
Type Assignation Internal security Areas Considered

Public halls.
E=F; S=F; T=NO; E.g.=NO/SI; M=NO
Waiting rooms.
As a rule, it will be applied in:
Prayer rooms.
Facility Security Level 1.
Toilets.
All Airport facilities with no direct functional impact on
01 Cleaning rooms.
the Airport operations and/or Airport personal.
Internal offices.
Facility Level 2 internal enclosures, when their use or
Dealers / Rent a Car.
risk classification is not different from that of the
Ticket sales.
general area already covered.
Ground access to terminal

E=F; S=F; T=NO; E.g.=NO/SI; M=SI.
building.
It will be applied on the perimeter of buildings with
Perimeter accesses in land zone
public areas.
02 buildings.
Likewise, in premises considered as “Facility Security
Perimeter accesses in buildings
Level 1”, but with a low presence of personnel (as an
in the air zone.
intrusion detection system).
Airport offices.
E=C; S=F; T=NO; E.g.=NO; M=SI.
Security agency offices.
Generally, it will be applied in:
Technical rooms.
Facility Security Level 2
03 Wiring Centres
All Airport facilities where staff or systems are involved
SATE facilities and warehouses
for Airport Security, Airport Safety and Airport
Closed air conditioning rooms.
Operations.
Electrical substation.
E=C; S=F; T=SI; E.g.=NO; M=SI.

Temporary opening of control
As a rule, it will be applied in:
points (goods, customs, ...)
Facility Security Level 2 where prolonged opening and
04 VIPS rooms.
control by authorized agent is required.
Authorities areas.
Where there are periods of
opening hours with personalized attention of costumers.
CPD
CCO
E=C; S=C; T=NO; E.g.=NO; M=SI. COS
As a rule, it will be applied in connection with Facility CMC
Security Level 2, where: Control Room BHS
Presence or access control by lock is required. Screening Centre.
05
At all accesses from the airside of the terminal to the Most accesses to Exterior Air
platform area. except closed rooms.
In communications between controlled (secure) Boundaries between
premises. independent controlled
premises.
E=C; S=C; T=SI; E.g.=NO; M=SI.

Generally, it will be applied in accesses from the air side Boarding / disembarkation
06 of the terminal to the platform area. where: doors.
Prolonged opening controlled by an authorized agent is
required.

12 | SAFETY SYSTEMS
E=C; S=F/C; T=NO/SI; E.g.=SI; M=SI.

To be study through the
As a rule, it will be applied in any of the cases foreseen
Evacuation Plans when these are
07 in types 03, 04, 05 and 06, where the door is considered
approved and available
as an evacuation route and affected by the control
equipment.
To be study through the
E=P; S=P; T=NO; E.g.=SI; M=SI.
Evacuation Plans when these are
08 Doors, exclusively designed for emergency use only and
approved and available
effects upon the Security Zones.
Table 84-Doors Type Assignment
11.3.5.1.4 Sterile / Nonsterile Transition Criteria
Transitions between Landside and Airside in the control process defined as input-from the area
with the lowest to highest risk- (which would coincide with the departures of the passengers),
based on SECURITY CONTROLS, or inspection points that are not within the scope of the present
system.
The transitions between Airside and Landside in the process defined as output (which would
coincide with that of passenger arrivals) the following typologies of doors:
Type Assignation Internal security Areas Considered
E=P; S=F; T=NO; E.g.=NO; M=SI.

Generally, it will be
Communication between the landing
applied in
01 and baggage claim area.
passenger processes
of Airside / Landside
departure.
E=P; S=C; T=NO; E.g.=NO; M=SI.
In general rule, it will Exit doors in line with inspection filters (if
be applied in NO any)
02
passenger processes
on the Air Side /
Land Side exit.
Table 85-Sterile / Non-Sterile Transition Criteria

12 | SAFETY SYSTEMS
11.3.5.1.5 Other applications for Access control
Other applications to be foreseen in the design of access control, not assigned to a standard
door, are:
 Vehicle Barriers:
Access points where the concepts of controlled, free or prohibited are equally
applicable. (without identifying emergency criteria).
 Lifts:
Transit points where the concepts of controlled, free or prohibited are equally
applicable.
 Totem:
Personnel identification point in Security Checkpoint, supervised by security personnel
or it can be automated with a one-person access mechanism.
 BHS Blinds:
Luggage passage gates, whose activation requires identification of personnel and
assigned privileges.
 Alarm Devices:
Included in the IDS module, the need to incorporate manual alarm activation elements
with direct notice to COS is established, with two basic objectives:
o Panic button.
At points where the organization's personnel and concessionaires may be

subjected to coercion.
o Medical emergency push button.
In areas where a passenger or internal staff can be found alone and needs to
alert of a medical emergency.
The usual location of the mentioned elements is:
Location Panic Button Medical Emergency Push Button

Information desks Yes
Car rental counters Yes
Airline counters Yes
Immigration counters Yes
Customs Counters Yes
Ablution room Yes
Toilets Yes
Table 86-Alarm Push Button Location

12 | SAFETY SYSTEMS
Design Criteria
With general criteria, the SACS technology should be:
 The SACS solution must be implemented and configured to take advantage of the latest
technology available at the time of design;
 The architecture of the SACS system will be modular, allowing easy expansion and
adaptation to new needs;
 The solution must demonstrate innovation in delivery within the limits of acceptable
risk;
 The solution must support the delivery of an efficient operation in all aspects of the
airport.
maintain the system during at least 4 hours.
The SACS system to be supplied will comply with the following structure:
 The system will be made up of a base management module and different optional
control modules, which can be added and expanded depending on the needs of
the installation.
 The system is fully scalable.
 The initially planned modules are:
o System administration;
o User administration;
o Control of ID card holders;
o Vehicle control;
o Alarm / Synoptic Module;
o Interfaces.
The structure of each market application can determine the existence or not of certain modules
of the exposed relationship, but it is a mandatory requirement:
 That all the planned functionalities are fulfilled;

 That the different management / control modules will be integrated with each
other;
 That everyone uses the same database, SQL 2016, Exadata, or Oracle 12 +.
The system is compatible with different reader topologies or data collection elements:
Keyboards.
 Proximity readers;
 Biometric readers (option pending validation);
 Vehicle License Plate Readers (VLPR).
Airport operations require at certain times to have intercom at control points between users and
Control Centre staff, to answer queries, resolve incidents or activate alternative access
procedures. Therefore, the proposed solution must have one of the following work options:
 The availability of SACS equipment that itself incorporates communication

elements with Audio / Video over IP services.
 The possibility of a controller that allows integration with third-party intercom
systems, which has the corresponding Audio / Video elements.
In either case, audio management can be performed from the SACS workstations themselves or
through compatible SIP telephone exchanges.

12 | SAFETY SYSTEMS
The system will have a colour graphical user interface (GUI) with maps and dynamic icons:
 Showing the location and individual status of all elements of the SACS system
installed at the airport.
 The synoptic module allows monitoring of events and alarms on maps, in real time.
 Access to the configuration change of the elements must be possible from the
synoptic module maps themselves, per user with administrator level.

The Security Access Control System (SACS) shall be fully integrated and installed as a complete
package, covering the Airport's security needs and also including other platforms that may be
installed at the Airport for maintenance or operations to form a complete system complying
with the requirements and the appropriate standards.
The SACS System shall be integrated with:
 CCTV System:
The SACS system shall be integrated with the CCTV to such point that any alarm
generated by the system (Door Forced, Door Held etc.) shall cause the camera nearest
that door to display the relevant image on a monitor screen. If covered by a
Pan/Tilt/Zoom (PTZ) camera the camera shall pan/tilt and zoom appropriately to
present the operator with the best image available. Integration shall be at data level
and interfacing by dry contacts shall not be permitted.
 Fire Detection and Alarm System FDAS:
The SACS system shall be fully integrated with the FDAS in order to liberate al doors
and enable the correct evacuation of personnel in the event of a fire alarm.
 Master-Clock System (MCS):
The SACS system shall be time synchronized to the MCS; this synchronization shall
occur through the use of software that requests time from the Network Time Server at
intervals not exceeding 15 minutes. All recorded alarms shall incorporate the time and
date as well as the ACS field component ID.
 Building Management System (BMS):
The SACS system will be integrated with the BMS to report the operational status of its
elements. The connection is limited to energy data and communications for security
aspects.
 Airport Workers Identity Management System:
The SACS system shall be fully integrated with the Airport Workers Identity
Management System in order to be able to collate personal data of employees.
 Identity Management System (IDMS):

The SACS will be fully integrated with the IDMS for the validation and production of
identities.

12 | SAFETY SYSTEMS
Figure 76-SACS Integration

The SACS will use the airport LAN to provide services to the controller units (access and alarms),
servers and workstations.
When the controllers do not have copper connectivity, the network will communicate through
a fibre optic cable to a media converter located within the closest communications room or
cabinet where the signal will be converted and enter the local switch.
The primary and backup servers for the system will be in two different main communication
rooms and will be connected to the LAN switches via 1000-BaseT Ethernet NICs.
Clients must connect to the LAN via 1000-Base-T or 10/100 Mbps Ethernet NIC (auto-
negotiation).
The SACS Supplier shall be responsible for providing and maintaining an IP addressing scheme
11.3.8 Software Requirements.

The application shall be virtualizable.
The application will be able to work in Hot Backup.
The software to be supplied will have the following system access requirements:
 The system must be accessible from any Client Station, without the need to install
specific client software;
 The system may restrict access to system users, selected based on the assigned
profile and the Client Position from where the session starts;
 Users and system administrators can change their password at any time;
 The system will allow you to force system users to change their password after the
first login or after the system administrator has reset a system user password;
 All password information will be encrypted.

12 | SAFETY SYSTEMS
The software to be supplied will guarantee the following system administration benefits:
 The application will automate, as much as possible, the administrative procedures

that are required (time changes, cancellations, data deletion, backups);
 The system will offer a customizable graphical user interface, so that it can be
configured to only display the menu items relevant to the user's profile;
 The system will allow the user to switch quickly and easily between system tasks
without losing the entered information that has not been saved;
 The system will provide a unified search function, that is, a simultaneous search for
all the information of a specific cardholder;
 The application will have the possibility of making virtual partitions for the
management of certain operational areas, through this functionality the
administrator can assign operators what devices they can manage and in what time
periods;
 The software to be supplied will have tools for preparing reports, according to the
format and content that the client will determine;
 The system will determine who has access to make, view or manage reports;
 The application will allow the reports to be viewed on the screen, export to different
formats (Excel, Word, PDF, etc.) or to print them.
The system allows, for all control points, to configure and identify the devices that are considered
input and output, and thus be able to differentiate the actions they perform, which will allow us
to carry out the following actions:
 Counting:
Through the established input-output configuration, the system will provide the
possibility of counting personnel who have accessed a certain facility or area of it.
 Anti-Pass Back:
The system will provide the possibility of programming the Anti-Pass Back (APB),
in areas where there are exit readers, to prevent people from entering the zones
and access points selected by reusing an access card from a cardholder who has
not previously left the area or access point in question.
 Two-person rule:
The system will allow regulating access to certain areas only if two authorized
persons present their access card in the same card reader, within a definable period.
 Minimum occupancy rules:
The system will prevent individuals from being alone in selected areas with exit
readers, by applying certain restrictions.

12 | SAFETY SYSTEMS

 Access Controller - Two readers
Component Specification
Terminal inputs Two reading terminals

Configurable for one or two doors
Auxiliary inputs 2 for opening detector

2 for opening signal
2 for reader inhibition
2 supervised general-purpose entrances
Outputs 2 auxiliary outputs per relay, configurable

2 general purpose digital outputs
Internal alarms Alarm power failure, battery failure, door forced/open door
Network Communication to Ethernet network, with TCP / IP protocol
Processability Pass accreditation> 50,000

Vehicle registrations> 5,000
Events message> 2,000
Alarms message> 1,000
Electrical supply 220-240 VAC, 50 / 60Hz

12Vac Power Supply is included. / 1A with 5A / h battery (minimum)
Protection Box Ability to contain all the elements and with tamper detector
Table 87-Access Controller - Two readers
 Access Controller – Four readers
Four reading terminals

Terminal inputs
Configurable for one to four doors
4 for opening detector

4 for opening signal
Auxiliary inputs
4 for reader inhibition
4 supervised general-purpose entrances
4 auxiliary outputs per relay, configurable
Outputs
4 salidas digitales de propósito general
Internal alarms Alarm power failure, battery failure, door forced/open door
Pass accreditation> 50,000

Vehicle registrations> 5,000
Processability
Events message> 2,000
Alarms message> 1,000
220-240 VAC, 50 / 60Hz

Electrical supply
Table 88-Access Controller - Four readers

12 | SAFETY SYSTEMS
 Alarm Controller
Terminal inputs Does not apply
Auxiliary inputs 8 supervised general-purpose inputs (minimum)
Outputs 8 general purpose digital outputs
Internal alarms Alarm power failure, battery failure
Electrical supply 220-240 VAC, 50 / 60Hz

Table 89-Alarm Controller
 Proximity reader
Technology Proximity card reader unit operating in the 13.56 MHz frequency range.
Process Ability to read both the CSN (Chip Serial Number) of the card, and read-
write data in the memory of the card
Reading range Minimum 30 mm
Mounting Surface or embedded
Electrical supply 12Vdc (from the Access Controller)
Protection Box IP65
Table 90-Proximity reader
 Proximity reader + keyboard
Technology Proximity card reader unit operating in the 13.56 MHz frequency range.
12-key keyboard and display
Process Ability to read both the CSN (Chip Serial Number) of the card and read-
It establishes the identification by double factor, with card and code
Stable temporary openings
Reading range Minimum 30 mm
Protection IP65
Table 91-Proximity reader + keyboard

12 | SAFETY SYSTEMS
 Proximity + biometric reader (optional to decide in next design stages)
Technology Compact reader made up of optics, OCR analyser and IR lighting
Technology Proximity card reader unit operating in the 13.56 MHz frequency range
Biometric reader unit based on fingerprint reading
Process Ability to read both the CSN (Chip Serial Number) of the card, and read-
Reading through a certified optical sensor, with a resolution of 500 dpi
Operation in 1: N or 1: 1 identification mode
Reading range Minimum 30 mm. away (proximity)

Less than 1 second in fingerprint verification (biometric)
Protection IP65
Table 92-Proximity + biometric reader
 Opening detector
Technology Magnetic door control device
Process 2 NC contacts (alarm and tamper)
Working range Protected against sabotage by magnetic field

Suitable for mounting on ferromagnetic materials
Protection Environmental class III, IP67
Table 93-Opening detector
 PIR sensor
Technology Infrared detector to automate the output process
Working range Output by contact relay 30V / 1A, in "failsafe" mode or unlock in case of
interruption
Adjustable relay operating time
Network Connectable to Access Controllers
Mounting Wall or ceiling mount
Protection IP65
Table 94-PIR sensor

12 | SAFETY SYSTEMS
 Electromechanical strike lock

Element that is defined in this design but that must be supplied and machined in the workshop
by the supplier of the different doors.
Technology Electromagnetic lock
"Failsafe" typology
Working range Minimum holding force 3500 N
Close control contact
Horizontal or vertical
Mounting
Long front with latch housing provision
Table 95-Electromechanical strike lock
 Electromagnetic suction cup

Element that is defined in the present design as an alternative to the electromagnetic strike, for
situations where the previous one cannot be used.
Technology Electromagnetic suction cup for door retention
Minimum holding force 3500 N

Working range
Close control contact
Mounting Surface or recessed
Protection IP65
Table 96-Electromagnetic suction cup.
 Workstation
The workstations required by the system will be provided by the IT Supplier, for the
standardization of the elements of the different control rooms and will meet the requirements
identified in the "Hardware Workstation" section of the Security Operation Centre (SOC).
 Server
The SACS application must be implemented on a virtual server.
The Supplier shall provide a solution that allows system servers to run on blade server
technology running on VM containers. Suppliers that are unable to accommodate this request
shall state the reason why.

12 | SAFETY SYSTEMS
The Customer requests that the Supplier supplies an optional price for the above requirement.
 Variety of redundancy technologies can be implemented to facilitate maximum

uptime. These include RAID, failover, and clustering configurations.
 The server hardware platform shall be state of the art system with the following
capabilities:
o Multi-Core processors;
o Multi CPU servers;
o Capable of running 64-bit enterprise level OS.
 The Server hardware shall have the following as minimum specification:
Unit id Unit
1) 19” (483mm) Rack mount – 2RU Server Chassis (Standalone)

Device
2) 19” (483mm) Rack mount – 10RU Sever Chassis (Blade Server)
Processors Two Processors: Each Processor Intel Xeon 2.93 GHz 64-bit Quad-core
Memory 24GB RDIMM DDR3 SDRAM
1) Support for Hot plug, Serial Attached SCSI, 2.5” 15KRPM Hard drives
Internal Storage
2) DVDRW Optical Drive
Network 10/100/1000/10000 Ethernet Ports; 8Gbps Fibre Channel Ports

1) Minimum 4 USB ports
2) Fully Redundant hot plug fans

Additional
3) Redundant 750 Watt (standalone) or 2400 Watt (Blade Server

Chassis), 100-240 VAC, 50/60Hz Power Supplies
Table 97-Server specification.
11.3.10 Performance Requirements.

The software to be supplied will guarantee the following performance values:
 The number of devices to be controlled by the system is theoretically unlimited.

 The number of users to be controlled by the application is theoretically unlimited.
 The system will allow simple and unlimited expansion, at any time after commissioning,
without a decrease in performance and without the need to adjust the system hardware
and software.
 The system will not present any design limitation in relation to the theoretical number
of possible simultaneous users who can log in.
 The system will be able to host an unlimited number of geographic locations, from
those located on the airport campus.
 The Supplier must provide software licenses capable of supporting the number of
workstations, servers, etc. as designed and installed as part of these specifications, with
a service expansion margin of 50%.

12 | SAFETY SYSTEMS
Availability & reliability

The entire SACS system shall offer a high availability. All configurations and data used by the
software shall be backed up on a daily basis to prevent data loss.
The system provided shall work 24 hours a day. The CCTV System shall have a high MTBF, and
a reduced MTTR shall be achievable.
The supplier shall provide within the proposal detailed information regarding technical
HDBK-217.
The SACS system shall display the visual information in real time. The following values shall be
considered:
o System start time: 3 min. maximum;
o Switching time: 10’’ maximum;
o Fault detection time: 10’’ maximum.
Scalability & expansion capability

The systems shall manage security operations throughout the whole airport campus.
The SACS system shall be configurable to assume a future growth, without requiring any system
upgrade or new investment.
System resources (processor speed, memory, disk space, network bandwidth) shall be
dimensioned accordingly.
Reserve spare capacity of the processing time and memory shall be not less than 40% of the
available processing time and memory for each processor, based on average use values.
The design shall have the capacity to expand by 25% over the final configuration planned,
without having to adapt programs or licenses.
Maintainability
The SACS shall support centralized monitoring and fault reporting to minimize maintenance
overhead and operating expenses (OPEX).
The SACS shall allow technical administrator access that can perform incident diagnostics and
firmware updates remotely.
Data Integrity.
The system shall provide a complete logging system for all alarm and event data.
The solution shall support the integrity and confidentiality of data from source to point of use.
The solution shall support the capture of operational and commercial performance data for
analysis and reporting purposes.

12 | SAFETY SYSTEMS
RF interference compliance:
The SACS is to be installed in a major airport and is subject to background RF levels expected in
such an area, including but not limited to aircraft navigation aids and land based mobile radio
systems. All equipment shall comply with statutory radiation limits.
It is the Supplier's responsibility to protect the systems specified here from interference of other
systems and to prevent interference with other systems. All facilities shall comply with applicable
and mandatory regulations.

System failures, including server or device failures, shall be on display at a central control point
failure.
If a server or end device goes out of service, the central control log shall be updated. Therefore,
where practical, a positive relationship (e.g., system heartbeat) shall exist between all
components of the systems at all time.
Operating Environment
Equipment shall be designed, installed, and tested to meet the following minimum
environmental criteria:
 Interior Mounted Equipment:

o Minimum Temperature: +10° Centigrade.
o Maximum Temperature: +30° Centigrade.
o Average Relative Humidity - 40%.
 Exterior Mounted Equipment:
o Minimum Temperature: -10° Centigrade.

12 | SAFETY SYSTEMS
Power requirements
Regarding Energy, the SACS deployment will fulfil the following requirements:
 For the Access - Alarm Controller, Workstations, Servers, it will be necessary to have
electrical connections of safe power, coming from UPS.
 The Access - Alarm Controller has its own power supply.
Supplier.
11.3.11 Project Deliverables.

The following table sums up in a high-level overview the deliverables to be provided by the
SACS supplier during the project:
SACS-DES-1 System Detailed Design for installation Design Phase
SACS-DES-2 Software Detailed Design (system architecture, Design Phase

SACS-DES-3 Testing & Commissioning Plans Design Phase
SACS-DES-4 FAT and SAT test Procedures Design Phase
SACS-DES-5 Maintenance Plan Design Phase
SACS-DES-6 Integration Plan and Interfaces Design Phase
SACS-DES-7 Training Plan Design Phase
SACS-DEL-1 Cable Management Document Delivery Phase
SACS-DEL-2 Configuration Control Document Delivery Phase
SACS-DEL-3 Test & Commissioning Reports Delivery Phase
SACS-DEL-4 Integration tests Reports Delivery Phase
SACS-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
SACS-DEL-6 Application user manuals Delivery Phase
SACS-DEL-7 As Built drawings Delivery Phase
Table 98-SACS Project Deliverables

12 | SAFETY SYSTEMS

The following classes of stakeholders are identified:

Any User Using this system
Maintenance and
03.03.00 Electronics Maintenance
Support
Control and system

05.01.00 Airport Security Control
administration
Design criteria
06.02.00 Technology Systems Design
validation
Table 99-SACS Airport Organizational Units Involved

12 | SAFETY SYSTEMS
11.4 IDMS (Identity Management System)
11.4.1 Introduction
IDMS is a comprehensive airport worker identity management solution designed to work with
highly configurable workflow capabilities to meet all ICAO/TSA/FAA/Local regulations and other
airport specific requirements for managing identities, credentials and the various events
associated with those IDs during their lifecycle as a worker in an airport.
GACA uses IDMS as a centralized solution that allows the integrated management of authorized
identities of national airports and is presented in this document as it is the main interface with
the access control system.

Credentialing is the process by which an individual is issued a credential that visually (and in
some cases electronically) identifies the person as having been granted privileges for unescorted
access to secure and sterile areas on an airport.
The process of creating the Airport Personal Identity Card (APIC) has several major sub-
processes:
 Determining an applicant’s identity through scrutiny of an applicant’s official identity
documents (known as ―breeder documents);
 Verifying the applicant’s identity and biometric information by a regulatory clearance
process to determine if that individual is qualified to have an airport ID badge and
related access privileges;
 Collecting the individual’s ten fingerprint images and biographical data for conducting
a Criminal History Records Check (CHRC) and a Security Threat Assessment (STA) that
checks against a number of Federal data bases by using the facilities of an aviation
channelling service provider (i.e., a fee-based authorized entity that provides and
facilitates the exchange of fingerprint images and biographical data to/from the airport
and TSA for background screening purposes);
 Submitting fingerprint and biographic data for conducting a check against State or local
data bases (only required for some locations);
 Conducting airport specific security training of the applicant;
 Issuing a credential along with appropriate access privileges for that facility.
The IDMS System is not under the Scope of this procurement. The Contractor shall include
in the procurement the integration of the IDMS with the SACS and Bagde System, and the
necessary workstations and HW (see section 11.4.6.2) to connect to the GACA IDMS
11.4.3 General System Requirements.
The IDMS is a web-based solution, policy-driven software solution which includes all capabilities
of a centralized management system to align with security threats and automation of privilege
lifecycle management for physical access.

12 | SAFETY SYSTEMS
It includes:
 Bi-directional data exchange between IDMS and other systems that need to be
integrated. This includes SACS server of each Airport Site and authoritative data
sources like APIC Database Card;
 Pre-defined rules and workflow for acting on the data fed. This system controller, with
algorithms, will enforce all the rule check prior to allowing access;
 A self-service portal, including a security training program for each user that requests
an APIC Card;
 A portal to manage visit and visitor;
 Administrative console to manage all types of cardholders and their processes;
 Reports consoled which include pre-defined reports on enrolled personnel,
provisioned/deprovisioned access, access request and reviews, etc.
Local requirements
Under the current regulations, the credentialing process must be performed by each airport
operator regardless of what privileges or similar credentials an applicant may have at another
airport.
In addition, each airport has a mandatory airport security training program that each individual
must complete before being issued an airport credential. The type of training typically depends
on the nature and scope of access permitted, including special training for persons with ramp
driving privileges.
Therefore, it is not within the scope of this document to carry out the design of the IMDS, already
available from GACA. But as a complement to it, at the Amaala Airport level:
 IMDS workstation, to carry out the APIC application and validation process;
 Equipment for capturing personnel data (photography, fingerprint, ...);
 Equipment for the local production of the APIC and programming of the necessary
information;
 Integration of the IDMS with the local SACS system and with authorized data sources,
such as the APIC and vehicle databases.
Therefore, it is considered that for the adequate coverage of the exposed needs, the production
material of the accreditations should be considered as an auxiliary module of the SACS and be
an additional supply from the same supplier.

At a general level, the procedures for identifying Amaala Airport staff must incorporate three
basic blocks, the databases of which must be fully integrated with each other:
 IDMS:
GACA's centralized solution that provides verification and validation services for an
ID card application, as well as the management of the privileges assigned to it.
 Airport Badge Office:
Equipment that allows local production of the identification card for people, visitors
and vehicles. Likewise, capture the personal data of the accredited subject.
 SACS:
Control and management system for access privileges to the different areas or
areas of the airport, discussed in the previous section.
The following figure shows the logical relationships between the described components:

12 | SAFETY SYSTEMS
Figure 77-IDMS Integration

The IDMS Supplier shall be responsible for providing and maintaining an IP addressing scheme
11.4.6 Hardware requirements

The set of elements that are identified as Airport Badge Office are specified in the following
sections:
Hardware requirements - Workstation

The workstations required by the system shall be provided by the IT Supplier, for the
standardization of the elements of the different control rooms and will meet the requirements
identified in the "Hardware Workstation" section of the Security Operation Centre (SOC).

12 | SAFETY SYSTEMS
Hardware requirements – IDMS

 Accreditation printer
Identification pass printer

Technology
Colour customization by resin thermal transfer
Possibility of two-sided printing by dye sublimation

Process
Possibility of two-sided lamination
Programs Drivers Windows Server 2008 o superior
Network Workstation connection
Electrical supply 220-240 VAC, 50/60Hz

Technology
Possibility of two-sided printing by dye sublimation

Process
Possibility of two-sided lamination
Table 100-Accreditation printer
 Reader-Recorder

Technology
Technology Device through which to enrol the cards in the system
Process With the ability to read and write proximity cards (frequency 13.56 MHz)
Mounting Table mount
Workstation connection
Network
Communication in safe mode (cryptographic key)
Electrical supply 12Vdc (from Workstation)
Table 101-Reader recorder
 Fingerprint reader
Technology Device through which the user fingerprint is registered in the system
Optical sensor with 500 dpi resolution

Process
Fingerprint storage according to ISO 19794-4 formats
Mounting Table mount
Network
Communication in safe mode (cryptographic key)
Table 102-Fingerprint reader

12 | SAFETY SYSTEMS
 Identification camera
Technology User image acquisition element to be incorporated the system
High resolution digital camera Footprint storage according to ISO 19794-

Process
4 formats
Mounting Desktop stand
Network Own software, loaded in the PC, that allows the previous adjustments of
each function of the camera
Table 103-Identification camera IDMS.

The equipment to be supplied will guarantee the following values:
 Shall be implemented and configured to take advantage of the latest technology
available at the time of design;
 Shall support the delivery of an efficient operation;
 It will be modular, allowing easy expansion and adaptation to new needs;
 It will have the capacity to admit 25% of the planned initial production, without having
to adapt hardware or licenses;
 Shall demonstrate an appropriate level of reliability, availability and maintainability;
 The Supplier shall provide within the proposal detailed information regarding technical
specifications of each of the proposed equipment, materials, and accessories
demonstrating integration / interfacing amongst them;
 The Mean Time Between failures (MTBF), Mean Time To Repair (MTTR), Mean Time
Between Critical Failures (MTBCF) and Availability figures of all the equipment proposed
should be provided and the overall system, indicating the method used for the
calculation, such as MIL-HDBK-217;
 Equipment mounted indoors, with the following environmental criteria:
o Minimum Temperature: +10° Centigrade;
o Maximum Temperature: +30° Centigrade;
Power requirements
Regarding Energy, the IDMS deployment will fulfil the following requirements:
 For the Workstations it will be necessary to have electrical connections of safe power,
coming from UPS;
Supplier;

12 | SAFETY SYSTEMS

IDMS supplier during the project:
IDMS-DES-1 Integration Plan and Interfaces Design Phase
IDMS-DES-2 Integration test Procedures Design Phase
IDMS -DES-3 Training Plan Design Phase
IDMS -DEL-1 Cable Management Document Delivery Phase
IDMS -DEL-2 Configuration Control Document Delivery Phase
IDMS -DEL-3 Test & Commissioning Reports Delivery Phase
IDMS -DEL-4 Integration tests Reports Delivery Phase
IDMS -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
IDMS -DEL-6 Application user manuals Delivery Phase
Table 104-IDMS Project Deliverables

05.01.00 Airport Security Control Control and system

administration
05.03.00 Government Entities User Using this system
06.02.00 Technology Systems Maintenance Design criteria

validation
Table 105-IDMS Airport Organizational Units Involved

12 | SAFETY SYSTEMS
11.5 Closed Circuit TV (CCTV) System
11.5.1 Introduction
Closed Circuit Television (CCTV) is a system designed to capture, display and record images of
an enclosure, in this case the Amaala Airport facilities, to which only a certain number of users
should have access.
The equipment technology of CCTV systems is constantly evolving, due to the improvement in
the performance of the products offered by the industry and the regulatory technical standards
that are established.
CCTV design criteria evolve as airport Information Systems /Information Technology (IS/IT)
networks become more capable, video security systems become "digital" and also "smarter" ,
and allows multiple users in the security community to monitor an event in real time and from
different locations through data networks.
Currently the cameras base their operation on the transmission of images through a TCP/IP
network, which can be UTP structured cabling networks, fibre optics and even Wi-Fi networks.
The cameras output is directly digital video streaming.
IP cameras can work with resolutions derived from the computer industry, currently it is common
to achieve image qualities of Megapixel format.
Image recording systems may not be part of the system since any server on the intranet or on
the internet will be able to directly access the cameras and store the images on its own hard
drive. The amount of data coming from the cameras to the storage system is increasing and in
a continuous process, allowing the system to simultaneously view and record the cameras.
In addition, the use of digital video compression techniques simplifies video management and
optimizes the use of system resources by preventing possible network overloads.
To all the above, such as CCTV applications or auxiliary modules, the industry has developed
powerful algorithms for intelligent image analysis or treatment, which offers significant
improvements in certain routines and security services.
All this has promoted that General Authority of Civil Aviation (GACA) of the Kingdom of Saudi
Arabia aims leveraging its airports video surveillance systems to unified one using a common
technology allowing an integrated National Airport Video Surveillance Architecture.

12 | SAFETY SYSTEMS

To ensure compatibility between devices in an IP CCTV installation between different
manufacturers and to achieve true plug-and-play between devices, several standards
development groups have emerged in recent years for standardization and interoperability
throughout the field of company security.

- International Air Transport Association (IATA)
ECAC European level, the European Civil Aviation Conference (ECAC)
OVNIV Open Network Video Interface Forum
PSIA Physical Security Interoperability Alliance

The British Home Office; Scientific Development Branch: CCTV

Operational Requirements Manual
The British Home Office Police Department; Police Scientific

Development Branch: CCTV Operational Requirements Manual
BS EN 62676-1-1 British Standard on minimum requirements for Video Surveillance

Systems
BS EN 62676-1-2 British Standard on Video surveillance systems for use in security

applications, Part 1-2; System requirements – Performance requirements
for video transmission
BSEN62676-4 British Standard on requirements for the selection, planning, installation,

commissioning, maintaining and testing of CCTV systems
BS7958 British standard setting out recommendations on the management and

operation of CCTV systems
BS 8418 British Standard on the design, installation, commissioning,

maintenance, operation and remote monitoring of detector-activated
CCTV
BS 8495 British Standard on the ode of practice for digital CCTV recording
systems for the purpose of image export to be used as evidence
US Homeland Security; Transportation Security Administration:

Recommended Security Guidelines for Airport Planning, Design and
Construction
Table 106-CCTV applicable References, Standards and Regulations

12 | SAFETY SYSTEMS
Basic Security Functions

In the deployment of the actions to be carried out, there is the criterion of obtaining an
"integrated security management" and in particular the CCTV SYSTEM, which has to allow the
optimization of the human resources dedicated to the task of surveillance and facilitate decision
making of those responsible for security.
Airport video surveillance addresses the followings main uses in airport security:
 Monitoring, surveillance, deterrence and intelligence gathering;

 Assessment and response to a possible incident;
 Assessment and response following an actual incident;
 Help ensure an effective security response in emergency situations;
 Forensic and evidentiary analysis after an incident;
 Detect alterations in a stable scenario (Video Analytics).
Other uses
Current CCTV systems allow multiple users to view a given image in real time and from different
locations over data networks. This feature has promoted that the installation of the security
CCTV is also used by other areas of the airport and thus eliminate the duplication of equipment
with similar coverage. The proposed solution would be to have a single CCTV system covering
the whole of the airport, supporting security operations and other checkpoints, for example:
 AOCC (Airport Operations Control Centre);

 CMC (Crisis Management Centre);
 Fire & Rescue Services;
 Maintenance & Utilities;
 Government Entities.
All this under a configuration roles and privileges previously established in the CCTV control
application. A password will be required to "log in" to the system and the workstation passwords
will limit user access to certain cameras, based on assigned personal privileges.
Type of coverage
For airport security, a key issue in establishing surveillance requirements is resolution, i.e., the
ability to resolve operationally significant details at a specified distance.
Internationally, there are different guides or supporting regulations in the design of CCTV
systems to relate the operating requirements to be covered with the requirements of the image
to be obtained, such as those of The British Home Office.

12 | SAFETY SYSTEMS
An adaptation of the aforementioned standards to the needs of the airport determines the
following types of coverage:
Purpose Description
SURVEILLANCE Cameras related with “surveillance” of people, vehicles and its
environment, it must comply with the following requirements:
 Person/vehicle occupies less than 5% of the height of the
monitor. Such a level of detail only allows the presence of
people or vehicles to be detected in a wide area
 Usually it relies with PTZ cameras and operator must know
in advance the zone to control
MONITORING Cameras related with “monitoring” of people, vehicles and its
environment must comply with the following requirements:
 Person/vehicle must take up at least the 5% of the monitor
height. Such detail level is enough to detect the presence
of people or vehicles over a wide area, and the direction of
its movement
 Target distance is usually maximum 50 meters
DETECT Cameras related with “detect” of people and their environment must
comply with the following requirements:
 Person/vehicle must take up at least the 10% of the
monitor height. Such detail level is enough to enable the
operator to act in alert condition, search in the monitor for
one specific person and to confirm or dismiss his presence
with high degree of confidence
 Target distance is usually up to 30 meters
OBSERVE Cameras related with “observe” of people and their environment
must comply with the following requirements:
 Person/vehicle must take up at least the 30% of the
monitor height. Such detail level is enough to identify
specific characteristics like the clothes, its colour, etc, while
having some view about the environment of the monitored
person
RECOGNIZE Cameras related with “recognize” of people must comply with the
following requirements:
 Surveilled person/vehicle must take up at least 50% of the
operator to identify a known person with a high degree of
confidence
IDENTIFY Cameras related with “identify” of people must comply with the
following requirements:
 Surveilled person/vehicle must take up the 100% of the
operator to identify any person without any doubt
Table 107-CCTV Type of coverage

12 | SAFETY SYSTEMS
It is usual to relate the “purpose” of the coverage with the pixels of the image to be obtained,
but this will only be of value when the specific monitor model to be used is defined.
For system operation, account should also be made of the difference between live operation
and playback / review operation when considering image size requirements. For example, in a
live monitoring situation, where a rapid assessment of the scene or situation may be needed, a
higher screen occupation may be required than a system which is required to be more ‘reactive’,
whereby little or no live interaction is anticipated and recordings / events can be reviewed in
slower time.
Video Management System (VMS)

Security personnel have access to all cameras, recordings and other devices on the system from
the VMS workstation, which provides a refined system of access rights that can be assigned to
groups of users or individuals throughout the site.
VMS is an Open Platform Network Video Management System that supports a variety of
hardware (cameras and encoders/decoders) from multiple vendors and offers the ability for
customizing the integration with other systems or devices using the VMS. The aim of a VMS is
to provide a tool that can configure, control and manage video surveillance equipment
independent of the manufacturer.
The viewing flexibility of a VMS makes it the ideal solution for multi-site monitoring applications
such as airport security environments, which require alarm monitoring and rapid access to
recorded video from multiple workstations.
Video Analysis Module

The high quality and resolution of the images currently obtained by CCTV cameras has allowed
the industry to develop powerful algorithms for intelligent image analysis or treatment.
The incorporation of high-performance software for video analysis, in real time, increases the
effectiveness of security personnel by having complementary information to image viewing,
which guides them to locations where there is a greater probability of suspicious or dangerous
activity.
In the airport environment, the most widely applied algorithms for providing intelligence to
cameras are (not limited to):
 Facial recognition;
 Queue control;
 License plate recognition;
 Intrusion detection;
 Temperature detection (thermal cameras).

12 | SAFETY SYSTEMS

According to the exposed, the architecture of the system is the following.
Figure 78-CCTV Architecture

11.5.5.1.1 Adaptation to infrastructure
A CCTV system basically comprises the processes of capturing, transporting, displaying and
recording the images, the set of the processes being what will determine the degree of
functionality that the system provides.
The basic components of the system have been defined, covering the described process:
 IP cameras;
 Transmission through the airport's internal network;
 Management and visualization through VMS application;
 Network recording system.

12 | SAFETY SYSTEMS
Defined the architecture of the system, the value or performance that the captured image
provides us, as a source of information on which the entire process of the CCTV system is based,
is the functional parameter that will further customize the installation to the needs of the Airport
and this will depend on two values:
 Resolution or information capacity that the image provides at an operational level.
This factor has already been defined in the previous section, based on the standards
that are applicable.
 The Scenario presented by the location of the camera. Amaala Airport shall determine
and apply its own camera location requirements for security purposes, considering the
perceived risk within the particular operating environment and its own infrastructure.
o The criteria to apply are:
 By location of controlled doors;
 By Airport processes;
 By common areas.
11.5.5.1.2 Controlled Door Location
From the typology of doors to be protected by the ACS system, most of them have established
the characteristic of "monitoring", that is, they are doors that "have elements for their control
and centralized monitoring of the state of the same.
The monitoring and evaluation process of the alarms or events that may occur requires that the
assigned operators (SOC) carry out the verification thereof. For this, as a general criterion it is
established:
“Every door controlled and monitored in SOC, will have a camera that allows its
visualization”.
 The coverage carried out, by general criteria, will be for the purpose of OBSERVE:
“Person/vehicle shall take up at least the 30% of the monitor height. Such detail
level is enough to identify specific characteristics like the clothes, its colour... etc,
while having some view about the environment of the monitored person”.
 In Type 02 doors (E = F; S = F; T = NO; E.g. = NO / YES; M = YES). The coverage
carried out will be for the purpose of DETECT:
“Person/vehicle shall take up at least the 10% of the monitor height. Such detail
level is enough to enable the operator to act in alert condition, search in the
monitor for one specific person and to confirm or dismiss his presence with high
degree of confidence”.
 Coverage will be carried out in the attack zone, that is, in the zone of least risk, in order
to be able to perform a deterrent function and preventive identification, in the following
types of doors:
o Tipo 02: E=F; S=F; T=NO; E.g.=NO/SI; M=SI;
o Tipo 03: E=C; S=F; T=NO; E.g.=NO; M=SI;
o Tipo 04: E=C; S=F; T=SI; E.g.=NO; M=SI;
o Tipo 09: E=L; S=P; T=NO; E.g.=NO; M=SI;
o Tipo 10: E=C; S=P; T=NO; E.g.=NO; M=SI.
 Coverage will be carried out in both areas of the door, in the following types:
o Type 05: E = C; S = C; T = NO; E.g.= NO; M = YES.
o Type 06: E = C; S = C; T = YES; E.g.= NO; M = YES.

12 | SAFETY SYSTEMS
 Type 07 emergency doors, coverage will be carried out according to the specific
configuration that corresponds to it (02, 03, 04, 05 or 06) and previously defined
requirement.
 Type 08 emergency doors, coverage will be made from the area of origin of the
evacuation, in order to perform a deterrent function and preventive identification.
 It is not necessary to assign one camera per door, being possible to cover different
doors with the same camera if the established purpose of OBSERVE or DETECT is
covered.
Note: E=Entry; S=Exit; T=Temporary; E.g.=Emergency; M=Monitored; C=Controlled; F=Free;
P=Prohibited.
11.5.5.1.3 Location Cameras by Process
The basic security processes of an airport usually are:

 Passengers;
 Authorities;
 Luggage;
 Staff;
 Cargo;
 Airplane;
 Provisions;
 Waste;
 Trolley.
Having control and supervision of the processes is essential for the organization and security of
the airport, for which the CCTV system is a basic tool.
The following sections carry out a specific analysis of these processes and their coverage at the
Amaala airport, where, for any position that coincides with one that has already been considered
in the previous section on door coverage, it is established:
 With the same purpose of coverage, the existing one is considered valid and the camera
position is not duplicated;
 Unlike coverage purpose, the one with the highest requirement (resolution) is applied
and the camera is not duplicated.

12 | SAFETY SYSTEMS
The coverage criteria for basic processes are:
PASSENGER PROCESS
Zone Criteria Coverage

DETECT - 20% of the
Queue Supervision
monitor height
CHECK IN
RECOGNIZE - 50% of
Control of Check in procedure
the monitor height
DETECT - 20% of the
Space and queue monitoring
monitor height
Control of People Inspection RECOGNIZE - 50% of
SECURITY CONTROL
Procedure (WTMD or HHMD) the monitor height
RECOGNIZE - 50% of
Bag Inspection Control (ETD)
the monitor height
DETECT - 20% of the
Space and Queue monitoring
monitor height
PASSPORT CONTROL
IDENTIFY - 100% of the
People identification
monitor height
DETECT - 20% of the
WAITING ROOMS Space Monitoring
monitor height
PRAYER ROOMS Not applicable Not applicable
BOARDING/DISEMBARKING RECOGNIZE - 50% of
Staff Recognition
DOOR the monitor height
RECOGNIZE - 50% of
CUSTOMS Control of Inspection Procedure
the monitor height
Table 108-CCTV Coverage Criteria by Process- Passenger Process
AUTHORITIES

RECOGNIZE–50% of the
Access point control
monitor height
GENERAL
OBSERVE – 30% of the
General lobby supervision
monitor height
Table 109-CCTV Coverage Criteria by Process- Authorities

12 | SAFETY SYSTEMS
LUGAGGE PROCESS

CHECK IN Control of Carrousel
monitor height
LANDSIDE/AIRSIDE RECOGNIZE–50% of the
Shutter control
BOUNDARY monitor height
IDENTIFY – 100% of the
Level 1 machine entry and exit
monitor height
Level 3 inspection points
monitor height
BHS
RECOGNIZE–50% of the
Points of classification
monitor height
Loading / unloading carousel
monitor height
BAGGAGE CLAIM Control carrousel and staff
monitor height
Table 110-CCTV Coverage Criteria by Process- Luggage
STAFF PROCESS

DETECT - 20% of the
monitor height
PEOPLE SECURITY CHECK
RECOGNIZE - 50% of
Control of inspection procedure
the monitor height
DETECT - 20% of the
monitor height
VEHICLE SECURITY Space and queue monitoring
monitor height
RECOGNIZE - 50% of
Control of inspection procedure
the monitor height
Supervision of access, reception and OBSERVE – 30% of the
WORKING AREA
general circulation spaces monitor height
REST AREA Not applicable Not applicable
PRAYER ROOM Not applicable Not applicable
CONTROL ROOMS Space monitoring
monitor height
Table 111-CCTV Coverage Criteria by Process- Staff

12 | SAFETY SYSTEMS
CARGO PROCESS

LOADING-UNLOADING Process Supervision
monitor height
CLASSIFICATION Loading /unloading carousel
monitor height
INSPECTION Entrance and exit of x-ray tunnel
monitor height
Table 112-CCTV Coverage Criteria by Process- Cargo
AIRPLANES PROCESS

RUNWAY
TAXIWAY SURVEILLANCE. Usually
General Supervision
HELICOPTER STAND it relies on PTZ cameras
APRON
MONITORING - 10% of
OVERNIGHT APRON Area monitoring
the monitor height
DETECT - 20% of the
Control of entrances and exits monitor height
HANGARS
MONITORING - 10% of
Control of working areas
the monitor height
Table 113-CCTV Coverage Criteria by Process- Airlines
11.5.5.1.4 Location cameras by common areas
In the development of the processes carried out, certain areas have not been considered as they
are common to the different users of the airport and it is necessary to apply general criteria.
The criteria for covering common areas are:
OUTDOOR PUBLIC AREAS

VEHICLE ROUTES General supervision SURVEILLANCE
DETECT - 20% of the
DROP OFF & PICK-UP Space and queue monitoring
monitor height
MONITORING - 10% of
PEDESTRIAN ROUTES General supervision
the monitor height
Table 114-CCTV Coverage Criteria by Area- Outdoor Public

12 | SAFETY SYSTEMS
PERIMETER

FENCE General supervision
SURVEILLANCE
SERVICE ROAD The location of the cameras will be Usually it relies with PTZ
based on: cameras
EMERGENCY EXITS -Air side buildings;
- Lighting poles.
Table 115-CCTV Coverage Criteria by Area- Perimeter
PARKINGS

Identifications of vehicles and IDENTIFY - 100% of the
ENTRANCE/EXIT
people monitor height
MONITORING - 10% of
PARKING SPACES General supervision
the monitor height
CASH POINTS (IF THEY Control of the process and RECOGNIZE - 50% of
EXIST) environment. the monitor height
Table 116-CCTV Coverage Criteria by Area- Parking
PUBLIC AREAS (Inside)

MONITORING - 10% of
GENERAL LOBBY General supervision
the monitor height
CUSTOMER SERVICE
(INFORMATION, DETECT - 20% of the
CAFETERIA, TICKET SALES, monitor height
...)
LIFTS User identification
monitor height
Table 117-CCTV Coverage Criteria by Area- Public Areas
11.5.5.1.5 Other Cameras Users
The possibility that users can view a certain image in real time and from different locations
through data networks, has promoted the CCTV system, based on certain needs that the present
study has not considered.
Example to this regard are:
 IT requires visual verification of the information presented in FIDS;
 Maintenance, requires verification of technical alarms that may occur in
electromechanical systems;
 General services require visual verification of availability of external transport (taxi, bus,
etc.).

12 | SAFETY SYSTEMS
These needs shall be compiled and unified with security needs.

Likewise, to unify the services in a single CCTV installation, in any position that coincides with
one that has already been considered within the security section, it is established:
 With the same purpose of coverage, the existing one is considered valid and the
position of the camera is not duplicated;
 Unlike coverage purpose, the one with the highest requirement (resolution) is applied
and the camera is not duplicated.
11.5.5.1.6 VMS Operation
The Video Management System (VMS) provide comprehensive user management, alarm
management, status control and configuration.
The basic components of the application are:
 Central Server software, which allows you to manage and control the entire system;
 Video Recording Manager services allow you to manage the recording and playback of
video, audio and data;
 The Configuration Client software, which provides a user interface for system
configuration and management;
 The Operator Client software, which provides a user interface for control and
management of the system.
The VMS user interface will support:
 Location of cameras on the map;
 Selection and display of cameras;
 Consultation of events;
 Multiple types of sensors per window;
 Visual navigation of the video playback timeline;
 Incident management.
Other basic functional requirements of the VMS system are:
 It will provide hierarchical role-based authorization policies;
 Advanced user interface concepts for effective and efficient operation;
 Logical tree configurable with automatic detection of IP device;
 Minimum and maximum recording time adjustments per camera;
 The recording schedule of each camera has quality and image speed settings for live,
normal, motion or alarm recording;
 Assigning events to user groups;
 Event recording based on planning;
 Execution of scripts generated by events according to planning;
 Selectable emergent menu for alarms;
 Activation of alarms based on planning;
 Access to system resources individually controlled by each user group;
 Customized logical tree for each user group: users only see the devices they have access
to;
 The system should allow to configure scenarios. A scenario will be a preprogramed
situation in which the action of a group of elements (cameras, monitors, VDRs, etc.) as
a whole is defined;
 The configured scenarios will be activated either manually or from certain events or
system alarms;
 Support sending live or playback video to external monitors and video walls;

12 | SAFETY SYSTEMS
 All actions on the system shall be recorded, which shall determine the sequence of
events should any historical analysis be required. Reports shall include alarm event
analysis which can be either manually or automatically generated;
 The system will allow live monitoring and recording of peripheral devices with audio
capabilities;
 The application shall provide an audit log per operator which will include:
o Operator log-on/off identification and time;
o Camera and monitor selections by number or description and times and including
all camera functions performed;
o Received and accepted alarms by description and times.
 Bandwidth requirements to be defined by the system vendor;
 Redundancy available, at the software and hardware level, for the Central Server.
11.5.5.1.7 VMS Workstation
Each VMS workstation shall provide:

 A colour Graphic User Interface (GUI) with maps and dynamic icons showing the
location and individual status of all cameras and VDR installed at the airport and provide
easy selection and control of required systems;
 La Workstation shall be programmed with all maps, icons and camera switching
capability and it shall be only preprogramed software partitioning that shall determine
which operator can view and control which camera (depending on the user's login and
password);
 Each workstation can incorporate three screen monitors. Monitors will generally
perform the following functions:
o Monitor 1 - Main Graphics Monitor;
o Monitor 2 - Surveillance Monitor;
o Monitor 3 - Alarm Monitor.
 Workstations should have high-quality local audio playback capability to match the
audio recording capabilities of CCTV cameras;
 Double-click operation on camera selection or drag and drop from a sitemap, logical
tree, or favourite tree.
11.5.5.1.8 VDR Operation
The VMS, through the services of the Video Recording Manager, allows you to manage the
recording and playback of video, audio and data of the Video Digital Register (VDR) and shall
fulfil the following requirements:
 The review of recorded images shall be password protected and shall be restricted to
authorized operators only;
 Deleting recorded images or copying to external memory, shall be allowed only on
supervisor’s level;
 The review of recorded images would be performed at either of the VMS workstations;
however, review software shall reside on all workstations but only enabled as required,
by authorized staff;
 The system shall enable the playback of time lapse, triggered and real time event
recordings as a continuous video stream;
 The system shall include a search function to enable stored data recorded at a specific
time and date to be accessed and reviewed;

12 | SAFETY SYSTEMS
 The system shall automatically present alarm triggered pre/post alarm recorded
sequences to the operator alarm monitor. It shall also be possible to automatically
present local cameras associated with the alarmed camera, to the video wall to provide
the operator with a greater awareness of the alarm scene, and enable individuals
connected to the alarm to be tracked;
 The system shall enable recorded megapixel camera images to be reviewed in zoom
mode;
 Programmable time profiles per camera;
 The system provides video authentication for recordings to external devices;
 Ability to record and deliver incoming audio streams from external devices.
11.5.5.1.9 Operation Video Wall Display Processor
The video wall display is required to be controlled a fully redundant video display processor and
management server located in the SOC and managed by the CCTV Management APP, which
shall provide the following functions:
 The Display processor shall provide a scalable solution to drive from a single display to
an effectively unlimited number of display screens;
 Source input components shall enable the capture of standard video and DVI/RGB
sources and distribute these at full frame rate and resolution to any number of displays
and operator positions for viewing;
 Network streams shall be decoded directly without additional hardware requirements
– the number of these sources that can be viewed simultaneously can easily be
expanded seamlessly – with the addition of more processing units as required for any
future requirement;
 Any networked input (computer or videos etc.) shall be capable of being distributed
over the display surface without any restriction on size and position;
 To manage the display configuration and positioning of applications and video sources
a Video-Wall Management Server will be provided to enable a simple intuitive user
interface with drag and drop capability to the wall from integration with the CCTV
Management Application;
 The video-wall management software shall enable specific pre-configured video display
cameras to be programmed to provide default camera views and sizes to be presented
per operator at log-on to the CCTV Control & Monitoring workstation.

The CCTV system shall be fully integrated and installed as a complete package, covering the
Airport's security needs and also including other CCTV platforms that may be installed at the
Airport for maintenance or operations (such as the BHS cameras), to form a complete system
complying with the requirements and the appropriate standards.
The CCTV System shall be integrated with:
 Access Control System ACS:
The CCTV system shall be integrated with the AACS at such that any alarm generated
by that system (Door Forced, Door Held etc.) shall cause the camera nearest that door
to display the relevant image on a monitor screen. If covered by a Pan/Tilt/Zoom (PTZ)
camera the camera shall pan/tilt and zoom appropriately to present the operator
with the best image available. Integration shall be at data level and interfacing by
dry contacts shall not be permitted.

12 | SAFETY SYSTEMS
 Fire Detection and Alarm System FDAS:

In the event of a fire alarm, the CCTV system shall be able to provide the relevant image
on a monitor screen.
 Master-Clock System MCS:

The CCTV management system shall be time synchronized to the MCS; this
synchronization shall occur through the use of software that requests time from the
Network Time Server at intervals not exceeding 15 minutes. All recorded video images
shall incorporate the time and date as well as the camera ID.

The CCTV system will be integrated with the BMS to report the operational status of its
elements. The connection is limited to energy data and communications for security
aspects.
 Other CCTV platforms:

That could have at the airport, such as Perimeter (PIDS), BHS, Maintenance, Operations,
Parking, etc.
 Video wall:
The CCTV shall interface to the Audio-Visual system to enable the display of video
images on the video wall.
Figure 79-CCTV Integration

12 | SAFETY SYSTEMS

The CCTV shall utilize the Airport LAN to provide services to cameras, servers, recorders, and
workstations.
Images transmitted from IP cameras must be available in the H.264 industry standard formats
(also known as MJPEG-4 AVC), MJPEG-4, or MJPEG, and communicate over the IP network using
the UDP protocol.
When the cameras do not dispose of copper connectivity, the network will communicate via a
fibre optic cable to a media converter located within the nearest communications room or
cabinet where the signal will be converted and enter the local switch.
The primary and backup servers for the system shall be in two different main communication
rooms and shall be connected to the LAN switches via 1000-BaseT Ethernet NICs. Clients shall
be connected to the LAN via 1000-Base-T or 10/100 Mbps Ethernet NICs (auto-negotiating).
The clients shall communicate with the system applications utilizing the TCP/IP network
protocol.
Bandwidth calculations for the CCTV system shall be provided into the Data Network Systems
design report.
The CCTV Supplier shall be responsible for providing and maintaining an IP addressing scheme
VMS Operation
The Video Management System (VMS) provide comprehensive user management, alarm
management, status control and configuration.
The basic components of the application are:
 Central Server software, which allows you to manage and control the entire system;
 Video Recording Manager services allow you to manage the recording and playback of
video, audio, and data;
 The Configuration Client software, which provides a user interface for system
configuration and management;
 The Operator Client software, which provides a user interface for control and
management of the system.
The VMS user interface will support:
 Location of cameras on the map;
 Selection and display of cameras;
 Consultation of events;
 Multiple types of sensors per window;
 Visual navigation of the video playback timeline;
 Incident management.
Other basic functional requirements of the VMS system are:
 It will provide hierarchical role-based authorization policies;
 Advanced user interface concepts for effective and efficient operation;
 Logical tree configurable with automatic detection of IP device;
 Minimum and maximum recording time adjustments per camera;
 The recording schedule of each camera has quality and image speed settings for live,
normal, motion or alarm recording;

12 | SAFETY SYSTEMS
 Assigning events to user groups;

 Event recording based on planning;
 Execution of scripts generated by events according to planning;
 Selectable emergent menu for alarms;
 Activation of alarms based on planning;
 Access to system resources individually controlled by each user group;
 Customized logical tree for each user group: users only see the devices they have access
to;
 The system should allow to configure scenarios. A scenario will be a preprogramed
situation in which the action of a group of elements (cameras, monitors, VDRs, etc.) is
defined;
 The configured scenarios will be activated either manually or from certain events or
system alarms;
 Support sending live or playback video to external monitors and video walls;
 All actions on the system shall be recorded, which shall determine the sequence of
events should any historical analysis be required. Reports shall include alarm event
analysis which can be either manually or automatically generated;
 The system will allow live monitoring and recording of peripheral devices with audio
capabilities;
 The application shall provide an audit log per operator which will include:
o Operator log-on/off identification and time;
o Camera and monitor selections by number or description and times and including
all camera functions performed;
o Received and accepted alarms by description and times.
 Bandwidth requirements to be defined by the system vendor;
 Redundancy available, at the software and hardware level, for the Central Server.
VMS Workstation
Each VMS workstation shall provide:
 A colour Graphic User Interface (GUI) with maps and dynamic icons showing the
location and individual status of all cameras and VDR installed at the airport and provide
easy selection and control of required systems;
 La Workstation shall be programmed with all maps, icons and camera switching
capability and it shall be only preprogramed software partitioning that shall determine
which operator can view and control which camera (depending on the user's login and
password);
 Each workstation can incorporate three screen monitors. Monitors will generally
perform the following functions:
o Monitor 1 - Main Graphics Monitor;
o Monitor 2 - Surveillance Monitor;
o Monitor 3 - Alarm Monitor.
 Workstations should have high-quality local audio playback capability to match the
audio recording capabilities of CCTV cameras;
 Double-click operation on camera selection or drag and drop from a sitemap, logical
tree, or favourite tree.

12 | SAFETY SYSTEMS
VDR Operation
The VMS, through the services of the Video Recording Manager, allows you to manage the
recording and playback of video, audio, and data of the Video Digital Register (VDR) and shall
fulfil the following requirements:
 The review of recorded images shall be password protected and shall be restricted to
authorized operators only;
 Deleting recorded images or copying to external memory, shall be allowed only on
supervisor’s level;
 The review of recorded images would be performed at either of the VMS workstations;
however, review software shall reside on all workstations but only enabled as required,
by authorized staff;
 The system shall enable the playback of time lapse, triggered and real time event
recordings as a continuous video stream;
 The system shall include a search function to enable stored data recorded at a specific
time and date to be accessed and reviewed;
 The system shall automatically present alarm triggered pre/post alarm recorded
sequences to the operator alarm monitor. It shall also be possible to automatically
present local cameras associated with the alarmed camera, to the video wall to provide
the operator with a greater awareness of the alarm scene, and enable individuals
connected to the alarm to be tracked;
 The system shall enable recorded megapixel camera images to be reviewed in zoom
mode;
 Programmable time profiles per camera;
 The system provides video authentication for recordings to external devices;
 Ability to record and deliver incoming audio streams from external devices.
Hardware requirements – Cameras

 IP - Fixed Indoor Dome
Technology
Image sensor CMOS Progressive Scan
Image sensor size (*) 1/1.8”
Megapixel sensor 4 Mpx
IR Yes, - 30 meters range

Minimum illumination 0.05 lux color
Light sensitivity
0 lux B / W with IR on
Day and Night functionality yes
Max video resolution 2592x1944
Frames per second 25/30 ips
Electronic image
yes
stabilization
Varifocal lens (*) 3.6 – 10 mm
Lens mount yes

12 | SAFETY SYSTEMS
Compression H.265, H.264, MJPEG
Generation of video Triple streams of video simultaneously
Noise reduction 3D DNR
Backlight Real WDR backlight compensation
BNC video output. Audio input / output. Alarm input / output. 1 RJ45
Input / output
10/100 Mps port
On-board storage (*) MicroSD slot for recording (up to 64 GB)
Video analysis Motion detection
Protocols Compatible ONVIF protocol

User authentication (ID and PW)
Security Measures Host authentication (MAC address)
IP address filtering
IP66 outdoor protection
Protection
IK10 vandal protection
Use temperature -20 ° C to 50 ° C
Power: 12 Vdc / PoE, consumption 5.5 W (max.)
Support Included according to operation and location needs
Table 118-IP - Fixed Indoor Dome

12 | SAFETY SYSTEMS
 IP - Fixed Outer Dome

The previous camera has the appropriate features to work outdoors, with the
advantage of unifying equipment typology.
 IP - Motorized Indoor Dome

Color: 0.002 Lux @ (F1.6, AGC ON)
Light sensitivity B/W: 0.0002 Lux @ (F1.6, AGC ON)
0 Lux with IR
Video resolution 1920 × 1080
Pan range 360° endless
Pan Speed Configurable, from 0.1°/s to 300°/s
Lens (*) 8 – 32 mm
Aperture range (*) F 1.6
Autofocus yes
Digital zoom 16x
Optical zoom 4x
Number of preset 256
Compression H.265+/H.265 video compression
Noise reduction WDR 120dB
Network Ethernet 10Base -T, /100Base-TX, RJ45 Connector
Privacy masks up to 8 masks
RS-485 Protocols HIKVISION, Pelco-P, Pelco-D, self-adaptive

Protection IP66 outdoor protection
Use temperature -30°C to 60°C
Power 12 VDC, PoE
Table 119-IP - Motorized Indoor Dome.

12 | SAFETY SYSTEMS
 IP - Motorized Outer Dome
IR Yes, >100 meters range

Color: 0.002 Lux @ (F1.5, AGC ON)
Light sensitivity B/W: 0.0002 Lux @ (F1.5, AGC ON)
0 Lux with IR
Video resolution 2560 × 1440

Horizontal speed: 0.1 ° -250 ° / s
Pan Range Vertical speed: 0.1 ° -150 ° / s
Pan Speed Configurable, from 0.1°/s to 210°/s
Lens (*) 5,7 – 153 mm
Aperture range F 1.5 to F 4.5
Autofocus yes
Digital zoom 16x
Optical zoom 32x
Number of preset 256
Compression H.265+/H.265 video compression
Noise reductio WDR 120dB.
Privacy masks up to 8 masks
RS-485 Protocols HIKVISION, Pelco-P, Pelco-D, self-adaptive

Protection IP66 outdoor protection

Use temperature -30 ° C to 60 ° C
Power Hi-PoE / 24VAC
Table 120-IP - Motorized Outer Dome.

12 | SAFETY SYSTEMS
 IP - Panoramic Dome.
Megapixel sensor 4 Mpx.

Light sensitivity
Video resolution 4096×1800 panorama mode
Lens (*) 4×4mm fixed lens
Compression H.265+/H.265/
Noise reduction 3D DNR
On-board storage MicroSD slot for recording (up to 128 GB)

IP67 outdoor protection

Protection
Use temperature -20 ° C to 50 ° C.
Power 12 VDC / PoE
Megapixel sensor 4 Mpx.

Light sensitivity
Video resolution 4096×1800 panorama mode
Table 121-IP - Panoramic Dome.
(*) These data are indicative of market product, others of similar that do not affect
performance and other characteristics will be accepted.

12 | SAFETY SYSTEMS
Hardware requirements – VDR

The demand for video storage capacity to record video surveillance image is growing at an
unprecedented rate driven by increasing high resolution cameras and longer data retention
policy.
The amount of data coming from the cameras to the storage system is huge and continuous.
The factors that affect how much disc storage is required are video resolution, framerate,
number of cameras and the quality of the compression technology deployed.
There are many ways that video surveillance streams can be recorded to digital disk drive media:
 Direct Attached Storage:

It is not considered appropriate as a base option for an installation with the needs and
infrastructure of an airport.
Its application would be suitable for the protection of auxiliary rooms that have their
own management and want to be integrated into the airport's VMS system. (example
an external parking area).
 Storage Area Network:
IP SANs are large capacity storage networks that record or write data to disk drives
in native block format, just as IP network cameras do.
 Network Attached Storage:
NAS systems leverage the Network File System (NFS) protocol, primarily used in
Unix- or Linux based operating systems, and Common Internet File System (CIFS),
usually for Windows-based systems.
The protocol allows a client (such as a PC or workstation) to manipulate files over
the data network as easily as if they were on the local desktop computer.
In principle, SAN and NAS systems are considered appropriate for an airport infrastructure, both
can use IP networks to access the storage of large amounts of data. However, there are big
differences in how SAN and NAS leverage the network and access storage, resulting in:
 NAS is cheaper and easier to manage;

 SAN has higher long-term performance, but fewer market options exist.
In the present case, due to the storage capacity required at Amaala Airport. Both systems are
considered valid and the option to implement will be given by the VMS system provider itself
and the available product catalogue.
In any case, the selected VDR system will meet the following minimum requirements:
 Compatible with ONVIF equipment;

 Memory adequate to keep all records in time of 30 days of recording;
 Supports standard H.264, advanced MPEG4 (CBR, VFR, VGL), MPEG2 and MJPEG
compressions;
 Supports CIF, 2CIF, 4CIF resolution and up to 5 megapixels;
 Unicast, multicast and multiple unicast transmission;
 Continuous time lapse (at least 25 images per min) and pre/post recording
programmable per camera;
 Real time system diagnostics;
 Rack installation;
 Modular and easily expandable;
 RAID 5 is requested at least RAID 6 may be recommended.

12 | SAFETY SYSTEMS
Hardware requirements - Workstation

standardization of the elements of the different control room and will meet the requirements
identified in the "Hardware Workstation" section of the Security Operation Centre.
Hardware requirements – Server

The VMS application must be implemented on a virtual server.
The Supplier shall provide a solution that allows system servers to run on blade server
technology running on VM containers. Suppliers that are unable to accommodate this request
shall state the reason why.
The Customer requests that the Supplier supplies an optional price for the above requirement.
 Variety of redundancy technologies can be implemented to facilitate maximum
uptime. These include RAID, failover, and clustering configurations.
 The server hardware platform shall be state of the art system with the following
capabilities:
o Multi-Core processors;
o Multi CPU servers;
o Capable of running 64-bit enterprise level OS.
 The Server hardware shall have the following as minimum specification:

1) 19” (483mm) Rack mount – 2RU Server Chassis (Standalone)
Device
Processors Two Processors: Each Processor Intel Xeon 2.93 GHz 64-bit Quad-core
Memory 24GB RDIMM DDR3 SDRAM
1) Support for Hot plug, Serial Attached SCSI, 2.5” 15KRPM
Internal Storage Hard drives
1) Minimum 4 USB ports
Additional
3) Redundant 750 Watt (standalone) or 2400 Watt (Blade Server Chassis),
100-240 VAC, 50/60Hz Power Supplies.
Table 122-CCTV – Server specification.

 The number of devices to be controlled by the system is theoretically unlimited;

 The system will not present any design limitation in relation to the theoretical
number of possible simultaneous users who can log in;
those located on the airport campus;
workstations, servers, etc. as designed and installed as part of these specifications,
with a service expansion margin of 50%.

12 | SAFETY SYSTEMS
CCTV system shall comply with the following availability and reliability requirements
 The entire CCTV system shall provide a high availability. All configurations and data
used by the software shall be backed up on a daily basis to prevent data loss;
 The system provided shall be equipped with a UPS solution to maintain the system
stability. Any power variation should not affect the quality of the image nor the
video features;
 The organization of information on the screen shall be clear. The information
(Online Help, Documentation) provided with the system shall be clear and concise.
The Graphic User Interface shall be user friendly;
 The system provided shall work 24 hours a day. The CCTV System shall have a high
MTBF, and a reduced MTTR shall be achievable;
 The Supplier shall provide within the proposal detailed information regarding
technical specifications of each of the proposed equipment, materials, and
accessories demonstrating integration / interfacing amongst them;
Between Critical Failures (MTBCF) and Availability figures of all the equipment
proposed should be provided and the overall system, indicating the method used
for the calculation, such as MIL-HDBK-217;
 The CCTV system shall display the visual information in real time. As minimum
response times values for the CCTV system elements, the following values shall be
considered:
o System start time: 3 min. Maximum;
o Fault detection time: 10’’ maximum.
The required Availability of the main system elements over a period of twelve (12) months
shall be:
System element Availability (%)
Central Servers 99.99
Operator Workstations 99.00
Cameras 99.99
VDRs 99.99
Table 123-CCTV Required Availability.
Maintainability
 The CCTV must support centralized monitoring and fault reporting to minimize
maintenance overhead and operating expenses (OPEX);
 The CCTV will allow technical administrator access that can perform incident
diagnostics and firmware updates remotely.
Scalability & expansion capability:

 The CCTV system will manage security operations throughout the airport campus;
 The CCTV system shall be configurable for assuming the future growth, without
requiring any system upgrade or new investment;
 Cameras: the system must be prepared to expand the number of cameras by (25%)
without adding any extra field elements;

12 | SAFETY SYSTEMS
 System resources (processor speed, memory, disk space, network bandwidth) will
be dimensioned accordingly;
 Reserve spare capacity of the processing time and memory shall be not less than
40% of the available processing time and memory for each processor, based on
average use values.
Redundancy:
In general, the CCTV shall incorporate the following redundancy concepts:
 100% Automatic Redundancy/Failover for all CCTV devices related to head-end

processing. Exceptions include cameras and workstations;
 Failure of anyone processing or network device shall not affect CCTV operation (No
Camera Lost);
 Hot-Standby camera servers, application servers, Database servers, etc;
 Primary and Secondary servers in separate data centres;
 Loss of camera or application server shall not cause any disruption to camera
recording, live viewing, client operation, etc;
 System recovery shall include automatic replication of data to assure seamless
access to stored data prior, during and after instance.
Data Integrity.
 The system will provide a complete logging system for all alarm and event data;
 The solution shall support the integrity and confidentiality of data from source to
point of use;
 The solution shall support the capture of operational and commercial performance
data for analysis and reporting purposes.
Rf interference compliance
The CCTV is to be installed in a major airport and is subject to background RF levels expected
in such an area, including but not limited to aircraft navigation aids and land based mobile radio
systems. All equipment shall comply with statutory radiation limits.
It is the Supplier's responsibility to protect the systems specified here from interference of other
systems and to prevent interference with other systems. All facilities must comply with
applicable and mandatory regulations.

failure.
If a server or end device goes out of service, the central control log shall be updated. Therefore,
where practical, a positive relationship (e.g., system heartbeat) shall exist between all

12 | SAFETY SYSTEMS
Operating Environment
Equipment shall be designed, installed, and tested to meet the following minimum
environmental criteria:
 Interior Mounted Equipment:

o Minimum Temperature: +10° Centigrade.
 Exterior Mounted Equipment:

o Minimum Temperature: -10° Centigrade.
Power requirements
Regarding Energy, the CCTV deployment will fulfil the following requirements:
 For the Workstations, Servers, it will be necessary to have electrical connections of

safe power, coming from UPS;
 The cameras have POE power;
Supplier;

The Supplier shall be responsible for the creation as requested by the client of all necessary
maintaining an “As-Built” CCTV camera schedule for the facility once constructed) and other
handover materials as required by the Design Consultant.

12 | SAFETY SYSTEMS
CCTV supplier during the project:
CCTV-DES-1 System Detailed Design for installation Design Phase
CCTV-DES-2 Software Detailed Design (system architecture, Design Phase

CCTV -DES-3 Testing & Commissioning Plans Design Phase
CCTV -DES-4 FAT and SAT test Procedures Design Phase
CCTV -DES-5 Maintenance Plan Design Phase
CCTV -DES-6 Integration Plan and Interfaces Design Phase
CCTV -DES-7 Training Plan Design Phase
CCTV -DEL-1 Cable Management Document Delivery Phase
CCTV -DEL-2 Configuration Control Document Delivery Phase
CCTV -DEL-3 Test & Commissioning Reports Delivery Phase
CCTV -DEL-4 Integration tests Reports Delivery Phase
CCTV -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
CCTV -DEL-6 Application user manuals Delivery Phase
CCTV -DEL-7 As Built drawings Delivery Phase
Table 124-CCTV Project Deliverables

02.02.xx Airport Operations User Using this system
02.03.01 Fire services User Using this system
05.01.00 Airport Security Control Control and system

administration
05.03.00 Government Entities User Using this system
06.02.00 Technology Systems Maintenance Design criteria

validation
Table 125-CCTV Airport Organizational Units Involved

12 | SAFETY SYSTEMS
11.6 Services

equipment supplied.
parties.

the design consultant following the stablished decision-making processes to be settled

12 | SAFETY SYSTEMS
profile.
11.6.3 Installation
Cabling
location.

12 | SAFETY SYSTEMS

Labelling
 Cable function;
the cable).
 Cable type;
 Cable number;


12 | SAFETY SYSTEMS
prior to testing.
operates correctly.

12 | SAFETY SYSTEMS
cutting power to equipment, pulling out cables, etc) across the different components.
ORAT Activities
 ORAT set-up;
11.6.5 Training

12 | SAFETY SYSTEMS
 Trainers;
 Engineers;
Factory Training
maintenance
On Site Training

necessary.


12 | SAFETY SYSTEMS
trays, pipes, etc.;
completion.

be quoted.
The service life of the equipment shall be at least ten (10) years

12 SAFETY SYSTEMS
12
12 | SAFETY SYSTEMS
12 SAFETY SYSTEMS
12.1 Previous design parameters
12.1.1 Introduction
A fire alarm system is designed to detect the unwanted presence of fire, at the earliest possible
stage, by monitoring the environmental changes associated with combustion.
In general, a fire alarm system has the function of detecting and notifying building occupants
to evacuate in the event of a fire or other emergency. Also, to report the fact to the pre-
established control centres, in order to notify the emergency services, and to prepare the
structure and associated systems to control the spread of fire and smoke.
12.1.2 Integration requirement

According to the related parameters, which aim to include the fire alarm system in all the
construction projects to be carried out, the result obtained will be that for each of facilities of
the Amaala airport campus, a system will be available that will respond to the following scheme:
Figure 80-Scheme of the fire detection and alarm system
System that is expected to comply with applicable local regulations and codes or standards that
exist worldwide for the design, installation, commissioning and service of fire detection systems.
With the airport's operational criteria, which require centralized monitoring and management
of its critical facilities, including fire detection, the need is created to incorporate into the usual
structure of the fire detection system, valid and distributed by the different enclosures, an
integration platform for the different existing plants.
The proposed solution shall have centralized monitoring and management is through the Fire
Alarm System Integration, which is developed in the following section.

12 | SAFETY SYSTEMS
12.2 Fire and Alarm System
12.2.1 Introduction
As a basic definition:
 Fire detection and alarm system

o It is mandatory in each of the airport buildings, within the scope of the
construction project;
o It is a system with the main function of detecting a fire at the earliest possible
stage and issuing the appropriate alarm and location signals so that appropriate
measures can be taken;
o The cabling is dedicated, permanently supervised, and intended for Class "A":
o The system must guarantee locally all kinds of preventive actions that are
required at the level of optical-acoustic warnings, stop-activation of auxiliary
facilities and equipment;
o Likewise, it develops the control of the extinguishing systems, if any.
 Fire Alarm System Integration

o It is the object of this section of IT technologies, optional implementation and
always as an operational improvement in airport management, never as a
substitute for local control;
o It is a centralized monitoring and management system for the different detection
centres existing on the airport premises;
o The system will use an operating system and a common database throughout
the airport's information, communications and telecommunications (ICT)
infrastructure;
o It performs a high-level integration function with other airport systems and
facilities (mainly SACS and BMS).

ISO 7240 International code for fire detection systems for the Design, installation,
commissioning and service of these systems for buildings. Document: in
force since August 2013. Technical committee: ISO / TC21 / SC3
NFPA 72 The United States National Fire Alarm Code for fire detection systems
and establishes the design, installation, commissioning, and
maintenance of these systems. Although it is a national code of the
United States. This has been adopted by several countries in the world.
This code is part of the United States NFPA family of standards.
Document: current 2019. Approved as the National Standard of the
United States in August 2012
NFPA 75 Standard for the Fire Protection of Information Technology Equipment)
NFPA 76 Standard for the Fire Protection of Telecommunications Facilities
NFPA 101 Life Safety Code
TIA-942-B Telecommunications Infrastructure for Data Centres. American National

Standards Institute / Telecommunications Industry Association, ANSI-TIA
NFPA 92 Standard for Smoke-Control Systems Utilizing Barriers and Pressure

Differences

12 | SAFETY SYSTEMS

TS 54-14 European Union code for fire detection systems for Design, installation,
commissioning and service of these systems for buildings. This is an
installation guide and each European country makes additional changes
following national standards. This document was prepared by the CEN /
TC72 committee "Fire detection systems" and is part of the EN 54 series
and standards. Document: in force since October 2018. Technical
committee: CEN / TC72
- Local standards and regulations that the implementation of the Fire

Alarm System Integration should not alter
Table 126-SACS applicable References, Standards and Regulations

The management of signals from fire panels is often difficult because all the information is
dispersed and appears on a display that is normally small and that each message is processed
in writing and individually.
Based on the foregoing, it is the basic objective of the Fire Alarm System Integration to provide
consolidation of the fire alarms with fire detection and alarm systems located in the facilities
throughout the airport campus and thus provide a unique identification and advertisement
solution.
The system must ensure coverage in all existing buildings and with the ability to easily expand
to future facilities, based on the following overview:
Figure 81-Scheme of the fire detection campus coverage
Where it is identified:
 FACP: it is the FA control panel that will be installed in secondary buildings.
 MACP: it is the FA control panel that will be installed in the main buildings (offers
greater capacity than the previous one).
 FA.WS: it is the workstation from which you can monitor and manage the entire
FA system with which you can set different levels of administration according to
user control.
The Fire Alarm System Integration will use a common database and operating system
throughout the airport's Information, Communications and Telecommunications (ICT)
infrastructure.

12 | SAFETY SYSTEMS
Servers will be installed in the main and secondary CPD, to guarantee the operation and
redundancy as it is a critical system, where the application will be installed and from where IP
communications with the different Fire Panels (FACP and MACP) of the existing buildings are
centralized in the airport.
The Airport Rescue & Fire Fighting (ARFF) building and its corresponding FA-Workstation shall
act as the main control position for the fire alarm systems throughout the airport. Similar
monitoring and control capabilities must be provided within the Airport Operations Control
Centre (AOCC) and the Crisis Management Centre (CMC).
Likewise, it is recommended to establish a control terminal of the Fire Alarm System Integration
system in the Security Operation Centre (SOC).
While all Fire Alarm System Integration capabilities are made available on different Workstations,
its use in normal airport operation and fire emergency management generally depends entirely
on operational emergency, preparedness and handling procedures. established elsewhere in
accordance with ICAO and national rules, regulations and procedures.
In general, the basic functions to perform are:
 In Workstations, you can set different levels of administration according to the

user's profile;
 The graphic management systems allow to visualize in a very graphic way and
through plans with representative icons of each element, for an easy location of
the element that has entered alarm or failure, and to act directly on each element
with a click;
 In the case of reception of a fire signal from any facility, the relevant CCTV images
will automatically be displayed on the video wall at the AOCC and SOC;
 The system will also allow the monitoring of the status of the different field
elements and the reception of technical alarms (lack of power, communications cut,
detector failure, etc.);
 There will be the possibility of carrying out remote actions, such as activating an
automatic fire extinguishing system and / or closing fire doors, all directly from the
control post and in a complementary way to the actions that are configured locally;
 The System shall have the possibility of programming from graphical software,
allowing for more complex adjustments in an agile way and sending these
adjustments to the corresponding Fire Panel.

12 | SAFETY SYSTEMS

According to the exposed, the architecture of the system is the following.
Figure 82-Architecture of Fire Alarm System Integration

maintain the system during at least 2h
Functional Requirements.
12.2.5.1.1 Scope of implementation.
The purpose of the Fire Alarm System Integration is the centralized management of fire alarm
systems throughout the Airport campus, whose most important facilities are the following:
 Amaala Terminal;
 ATC control;
 RFF Building;
 Administration Building;
 Power Plant;
 Chillers Plant;
 Technical Building;
 Sewage Treatment Plant.
The fire detection and alarm system will be considered a life safety system, therefore they
will have all the necessary elements to cover the risks to be protected and will be
implemented at the level of each installation in accordance with the established regulatory
standards. Specific requirement in this regard is the provision of the corresponding project
legalized by local authorities.
The integrated operation solution to be implemented shall work on a communications ring
independent of all existing facilities, so that they can be managed, monitored and
controlled from a single centralized platform.

12 | SAFETY SYSTEMS
At the integration level, at Amaala Airport, fire alarms will be consolidated into a central fire
alarm and response post located in the Air Rescue and Fire Fighting Station (ARFFS) and
with a duplicate work post located in the Security Operation Centre (SOC).
While all the capabilities of the Fire Alarm System Integration will be available at the TWO
key locations, their use in normal airport operation, as well as fire emergency management,
is entirely dependent on emergency operational preparedness. and management
procedures established with the GACA rules, regulations and procedures.
Therefore, this design report is not intended to describe or establish guidelines for the
operational relationship between different fire command centres, or for individual
buildings.
12.2.5.1.2 Operation of the Fire Alarm System Integration
The basic functions of the Fire Alarm System Integration are:

 Centralized monitoring of fire detection facilities;
 Receiving alarms;
 Activation of notices and scheduled actions;
 Data registration;
 Integration with other systems.
The Fire Alarm System Integration shall provide:
 It will provide access authorization policies based on user roles, minimum
administrator and operator;
 Password Security that allows alphanumeric passwords with configurable locks for
failed attempts;
 A colour Graphical User Interface (GUI) with dynamic maps and icons that show
each airport facility down to the detector level;
 The solution shall provide easy-to-read data on the location and status of control
panels and detectors.
The fire alarms will automatically display on digitalized drawings:
 Presentation to the location of the alarm origin point;
 Shall use standard fire icons to provide quick information;
 Customized alarms and message system;
 Cascading and tiling in WINDOWS;
 The solution will also monitor the health of the systems.
The solution will also monitor the status of fire detection systems and report any technical alarms
that may occur:
 Communications failure with the detection centre;

 Communications failure with the detection centre;
 Open circuit wiring fault, short circuit or ground loss;
 Handling of any equipment connected to the initiation and notification loop;
 Loss of communication with any equipment connected to the detection,
notification and supervision and command loop;
 Fault in the ground connection or any of the internal circuits of the central panel;
 Failure or abnormal variations in the power supply of the central panel;
 Change the idle state of the backup batteries;
 Error in recharging backup batteries;

12 | SAFETY SYSTEMS
 The identification of an alarm will be complemented with the directory of actions

to be carried out;
 The system will have the ability to generate notes that allow the operator to record
notes associated with events for historical records and recovery;
 Scroll and zoom functions that allow dynamic and precise navigation within a
graphic screen for a quick and convenient selection of the area of interest;
 Configurable coverage areas defined by the user within the graphic screen to
indicate the activity area;
 The ability to view on a videowall provided by third parties, in AOCC and SOC will
be provided;
 The system will provide a complete logging system for all system events;
 The application will provide an audit log by operator;
 ARFFS will have priority over centralized control located in the CCS facilities;
 You will have the possibility of implementing Remote Clients. connected by TCP /
IP LAN / WAN Ethernet communications;
 They will only monitor the system, but not to exercise any control;
 They are applicable in the Airport Operations Control Centre (AOCC) and the Crisis
Management Centre (CMC).
12.2.5.1.3 Identification of Field Equipment Elements
The field elements that make up the fire detection system of the different facilities are:
 Control:
o Central detection and alarm;
o Notifying graphic panel;
o Smoke control panel;
o Remote status indicators for hidden items;
o Directional state monitor modules;
o Auxiliary power supply.
 Detection / Alarm:
o Alarm pushbuttons;
o Smoke detector;
o Thermal / thermovelocimetric detectors;
o Combined Smoke and Temperature Detectors;
o Carbon monoxide detectors;
o Duct detectors;
o Aspiration detectors by air sampling;
o Flow detectors for sprinklers;
o Water pressure detectors;
o Zone supervision detectors;
o Optical acoustic sirens;
o Linear smoke detectors.
The definition of their characteristics is not the object of this document, but it is recommended
that all the elements of the fire detection system be of the same type and manufacturer in order
to standardize the elements, facilitate maintenance and spare parts, and guarantee
homogeneous integration.

12 | SAFETY SYSTEMS
12.2.5.1.4 Field Elements Requirements.
For a correct integration of the mentioned elements, it is required:

 Central Detection and Alarm:
o The panels shall be modular for both communications and control;
o Store the log of alarm and trouble events in a non-volatile history file;
o The historical file will remain intact even with the power cut from the mains
and the battery;
o Circuits for mounting detectors, modules, annunciators etc. they will be
designed for a 30% reserve for future extensions;
o The control panel shall be configurable to have data on events and status of
the intranet system;
o It will have communication modules by TCP/IP protocol;
o The system will provide an end-to-end system response time not to exceed
1second for each Fire Alarm Panel built into the solution.
 Detection and Alarm devices:
o They will be analogy and electronically addressed individually;
o This is the basis for the distributed intelligence architecture, being
permanently questioned by the control panel;
o Each device will continuously monitor its status, make critical decisions and
send them to the control panel;
o Certain detectors will be with user adjustable sensitivity level;
o It is recommended that detectors be available with dual level warnings,
reporting pre-alarm and alarm.

The Fire Alarm System Integration shall be integrated with:
The Fire Alarm System Integration shall be able to interact with the building's systems
and facilities that may facilitate a possible expansion of the fire risk or make it difficult
for people to evacuate.
For this, it shall be integrated into the BMS system, which is capable of controlling and
monitoring the status of the following systems:
o Fire extinguishing system;

o Smoke control system;
o Clime control system;
o Electrical system;
o Lifts.
 Public Address System (PAS):
The PAS will be integrated with the Fire Alarm in such a way that any alarm generated
by that system and activated in an emergency, will activate the warnings that are
determined in the corresponding operations plan.

12 | SAFETY SYSTEMS
 Access Control System ACS:
The SACS will be integrated with the Fire Alarm in such a way that any alarm generated
by the system or activated in an emergency, will release the points affected by the
evacuation routes. The integration at a high level will be done at the data level and at
the installation level in a redundant and obligatory way, the interaction will not be
through dry contacts.
 Closed Circuit TV (CCTV):
In the event of a fire alarm, the CCTV system shall be able to provide the relevant image
on a screen.
 Master-Clock System (MCS):
The Fire Alarm System Integration shall be time synchronized with the MCS, this
synchronization shall occur through the use of software that requests time from the
Network Time Server at intervals not exceeding fifteen (15) minutes. All recorded video
images shall incorporate the time and date as well as the camera ID.
 Video wall:
The CCTV shall interface with the Audio-Visual system to enable the display of video
images on the video wall.
Figure 83-Interfaces of Fire Alarm System Integration.

12 | SAFETY SYSTEMS

The networking of the individual buildings will utilize dedicated fiber cores of the main airport
network cable. Fire rated fiber optic cable will run from the termination point in each building
to the associated fire alarm panel.
The primary and backup servers for the system shall be located in two different main
communication rooms and shall be connected to the LAN switches via 1000-BaseT Ethernet
NICs. Clients shall be connected to the LAN via 1000-Base-T or 10/100 Mbps Ethernet NICs
(auto-negotiating). The clients shall communicate with the system applications utilizing the
TCP/IP network protocol.
The Fire Alarm System Integration Supplier shall be responsible for providing and maintaining
an IP addressing scheme which shall require client approval in accordance to LAN policies of the
Airport.
12.2.8 Software Requirements.

For a correct operation of the Fire Alarm System Integration (FASI), its necessary that:
 The application must be virtualizable and can work in Hot Backup;
 The system will be modular and scalable;
 The system must be accessible from any Client Station, without the need to install
specific client software;
 Client / server configuration;
 The system must support any number of simultaneous alarms;
 Diagnosis of the system in real time;
 Unique and personalized workstation for the security operator, with the following
benefits:
o Provide hierarchical role-based authorization policies;

o Unique operating methodology, independent of the integrated teams;
o Ease of command of the different elements that make up the installation;
o Integration of any equipment transparently to the user;
o Comprehensive information for monitoring and quality control of the
service;
o The software will display all messages until the operator confirms it.
 The FASI must provide a Graphical User Interface (GUI):
o Layer structure;
o Predefined symbol libraries as icons;
o Clarity in the visualization of the state of the elements that make up the
installation;
o Interactive state map of the entire campus with the ability to scroll and
zoom;
o Alerts may overlap on campus map;
o Deactivated security devices and sensors will be indicated on the campus
map.

12 | SAFETY SYSTEMS
 “Workflow” type operation:
o Procedures embedded in the software itself to aid decision-making, which

guides the operator on the steps to be followed in the event of any type
of incident, recording each action carried out by it;
o This operation is reinforced with the possibility of consulting contacts and
integration with SIP telephony for greater agility in dealing with incidents
and thus improving the efficiency of the surveillance service;
o The system complements this procedure with a visual aid to the installation
through integration with the CCTV system;
o Finally, the system obliges the operator to always indicate a cause of any
incident received and thus carry out the deployment of the corresponding
actions, allowing subsequent forensic analysis.
 At the historical record level:
o Historical record of more than 500,000 events with operator notes;

o The registry must allow the preservation of the data in case of total loss of
energy;
o The System shall have an automatic and configurable reporting system;
o Ability to export to XML for the generation and customization of reports.
12.2.9 Hardware Requirements.
Server requirements
The server hardware platform shall be state of the art system with the following capabilities:
 Multi-Core processors;
 Multi CPU servers;
 Capable of running 64 bit enterprise level OS.
The Server hardware shall have the following as minimum specification:
Technology Identification pass printer


Light sensitivity
Day and Night

yes
functionality
Max video resolution 2592x1944
Electronic image
yes
stabilization
Varifocal lens (*) 3.6 – 10 mm

12 | SAFETY SYSTEMS
Device 1) 19” (483mm) Rack mount – 2RU Server Chassis (Standalone)

Processor Two Processors: Each Processor Intel Xeon 2.93 GHz 64-bit Quad-core
Memory: 24GB RDIMM DDR3 SDRAM
Internal Storage 1) Support for Hot plug, Serial Attached SCSI, 2.5” 15KRPM Hard drives
Additional 1) Minimum 4 USB ports

3) Redundant 750 Watt (standalone) or 2400 Watt (Blade Server Chassis),
100-240 VAC, 50/60Hz Power Supplies
Table 127-Fire Alarm – Server specification.
Workstation requirements
standardization of the elements of the different control rooms and will meet the
requirements identified in the "Hardware Workstation" section of the Security Operation
Center.

 The number of devices to be controlled by the system is theoretically unlimited;
 The system will not present any design limitation in relation to the theoretical number
of possible simultaneous users who can log in;
those located on the airport campus;
workstations, servers, etc. as designed and installed as part of these specifications, with
a service expansion margin of 50%.

 The system provided shall work 24 hours a day. It shall have a high MTBF, and a reduced
MTTR shall be achievable;
 The Supplier shall provide within the proposal detailed information regarding technical
specifications of each of the proposed equipment, materials, and accessories
demonstrating integration / interfacing amongst them;
Between Critical Failures (MTBCF) and Availability figures of all the equipment proposed
should be provided and the overall system, indicating the method used for the
calculation, such as MIL-HDBK-217;

12 | SAFETY SYSTEMS
 As minimum response times values for the system elements, the following values shall
be considered:
o System start time: 3 min. Maximum;
o Fault detection time: 10’’ maximum;
o The system must support any number of simultaneous alarms.
Maintainability
 The system will be maintainable according to the guide given in the following
o NFPA 72:2010.
 The FASI must support centralized monitoring and fault reporting to minimize
maintenance overhead and operating expenses (OPEX);
 The FASU will allow technical administrator access that can perform incident diagnostics
and firmware updates remotely.
Scalability & expansion capability:

 The FASI system will manage security operations throughout the airport campus;
 The FASI system shall be configurable for assuming the future growth, without requiring
any system upgrade or new investment;
 System resources (processor speed, memory, disk space, network bandwidth) will be
dimensioned accordingly;
 Reserve spare capacity of the processing time and memory shall be not less than 40%
of the available processing time and memory for each processor, based on average use
values.
Data Integrity.
 The system will provide a complete logging system for all alarm and event data;
 The solution must support the integrity and confidentiality of data from source to point
of use;
 The solution shall support the capture of operational and commercial performance data
for analysis and reporting purposes.

System failures, including server or device failures, shall be on display at a central control point
failure.
In the event that a server or end device fails, the central control log shall be updated. Therefore,
where possible, a positive relationship (e.g., system heartbeat) shall exist between all

12 | SAFETY SYSTEMS
Power requirements
Regarding Energy, the FASI deployment will fulfil the following requirements:
 For the Workstations, Servers, it will be necessary to have electrical connections of safe
power, coming from UPS;
Supplier;

maintaining an “As-Built” Fire Alarm System schedule for the facility once constructed) and other
The following table sums up in a high-level overview the deliverables to be provided by the Fire
Alarm System supplier during the project:
FASI -DES-1 System Detailed Design for installation Design Phase
FASI -DES-2 Software Detailed Design (system architecture, Design Phase

FASI -DES-3 Testing & Commissioning Plans Design Phase
FASI -DES-4 FAT and SAT test Procedures Design Phase
FASI -DES-5 Maintenance Plan Design Phase
FASI -DES-6 Integration Plan and Interfaces Design Phase
FASI -DES-7 Training Plan Design Phase
FASI -DEL-1 Cable Management Document Delivery Phase
FASI -DEL-2 Configuration Control Document Delivery Phase
FASI -DEL-3 Test & Commissioning Reports Delivery Phase
FASI -DEL-4 Integration tests Reports Delivery Phase
FASI -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
FASI -DEL-6 Application user manuals Delivery Phase
FASI -DEL-7 As Built drawings Delivery Phase
Table 128-FAS Project Deliverables

12 | SAFETY SYSTEMS

02.31.01 Fire services User Control and user the

system
03.03.00 Electronics Maintenance Maintenance and

Support
06.02.00 Technology Systems Design Design criteria

validation
Table 129-Fire and Alarm System Airport Organizational Units Involved

12 | SAFETY SYSTEMS
12.3 Services

equipment supplied.
parties.


12 | SAFETY SYSTEMS
profile.
12.3.3 Installation
Cabling
location.

12 | SAFETY SYSTEMS

Labelling
 Cable function;
the cable).
 Cable type;
 Cable number;


12 | SAFETY SYSTEMS
prior to testing.
operates correctly.

12 | SAFETY SYSTEMS
ORAT Activities
 ORAT set-up;
12.3.5 Training

12 | SAFETY SYSTEMS
 Trainers;
 Engineers;
Factory Training
maintenance
On Site Training

necessary.


12 | SAFETY SYSTEMS
trays, pipes, etc.;
completion.

be quoted.

12 | SAFETY SYSTEMS

13 INFRASTRUCTURE SYSTEMS
13
13 | INFRASTRUCTURE SYSTEMS
13 INFRASTRUCTURE SYSTEMS
13.1 Building Management System (BMS)
13.1.1 Introduction
This Section defines and describes the System to be supplied as the Supervisory Control and
Data Acquisition (SCADA) Systems hub. The Building Management System (BMS) will optimise,
operationally and costly wise, facilities maintenance tasks using an integrated automation of
Control processes.
Moreover, the BMS will manage the necessary processed to obtain a joint view of facilities
maintenance operations.
The main aim of this System will consist on:
 Operational improvements (e.g. reliability and life span of the systems);

 Engineering and Maintenance Airport processes automation (e.g. time and money
saving during maintenance);
 Operating cost improvement (e.g. effective monitoring and targeting of energy
consumption);
 System level of integration enhancement, promoting the operation model based
on the Airport Operations Control Centre (AOCC);
 Final Users training support and increased staff productivity.

ISO 16484-2 Building Automation and Control Systems (BACS)
IEC 60050-351 International Electrotechnical Vocabulary — Part 351:

Automatic control
IEC 60529 Degrees of protection provided by enclosures (IP

code)
IEC 60664-1 Insulation coordination for equipment within

low‑voltage systems
IEC 60715 Dimensions of low‑voltage switchgear and control

gear — Standardized mounting on rails for
mechanical support of electrical devices in
switchgear and control gear installations
IEC 61131-3 Programmable controllers
ISO/IEC 7498-1 Information technology — Open Systems

Interconnection — Basic Reference Model: The Basic
Model
ISO/IEC 10746-2 Information technology — Open distributed

processing — Reference model: Foundations
ISO/IEC Guide 2 Standardization and related activities — General

vocabulary
Table 130-BMS applicable References, Standards and Regulations


The BMS is a computer-based control system installed in buildings that controls and monitors
the building's mechanical and electrical equipment such as ventilation, lighting, power systems,
fire systems, and security systems.
BMS consists of software and hardware; the software program, will be configured in a
hierarchical manner, using either C-Bus, Profibus or Internet protocols and open standards such
as DeviceNet, SOAP, XML, BACnet, LonWorks and Modbus.
Data is consolidated onto a single system to improve reporting, information management and
decision-making. Integrating and managing the Heating Ventilation and Air Conditioning
(HVAC), energy, security, digital video and life safety applications from a single workstation
allows facility-wide insight and control for better performance. Some of the related benefits of
this system are:
 Increased operational savings: Efficient resource deployment can result in

reduced operational costs, empowering operators, simplifying training and
decreasing false alarms;
 Energy efficient: Real-time view into facility operations and deep trend analysis
provide data-driven insight to optimize your energy management strategies and
minimize operational costs;
 Flexibility to grow and expand: The powerful combination of open systems
protocols and a scalable platform means the BMS can help support growth and
expansion of the system in the future;
 Reduced risk: Strategic mobile or desktop control, exceptional alarm management
and integrated security solutions helps to see the big picture, helping to speed up
response time and mitigate risks for the property, people and business;
 Intelligent reporting: Comprehensive reporting with functionality for
customizable reports delivers greater transparency into system history and
promotes compliance.
The new BMS system will manage the Engineering and Maintenance Key Performance Indicators
(KPI), unifying the maintenance processes vision and feeding the required information for
decision making on maintenance and control at the Airport Centres. The BMS will allow the
supervision and control of at least the following building subsystems:
 HVAC;
 Energy and electricity subsystems (e.g. LV, MV, etc.);
 Power Plant;
 Lighting subsystem;
 Plumbing subsystem;
 Fire alarm subsystem;
 Intrusion subsystem;
 Public Address System (PAS);
 Gas distribution subsystem (if available);
 Managing and monitoring of aircraft assistance;
 Residues management subsystem;
 Mechanical transportation.


The BMS System controls and monitor all the electrical and mechanical systems in buildings
from BMS workstation or HMI (Human Machine Interfaces).
All systems have their dedicated controllers and processing system due to the different
functionality of each system.
Sensors of the different systems or their particular SCADA systems send their inputs into the
BMS system to integrate all other systems through dedicated networking protocols.
SENSORS
BMS NETWORK
SERVER
MONITOR STATION MONITOR STATION
Figure 84-BMS architecture
13.1.5 General Requirements
The BMS is primarily responsible for obtaining information and coordinating the Systems
supervision. This will allow having all the necessary information to manage the Engineering and
Maintenance processes.
Regarding the management level, the BMS will be in charge of communications with the
different airport management systems and coordination with the future Airport Operations
Control Centre (AOCC).
The BMS will be a SCADA-based system dedicating to monitor and control the technical
installations of Amaala Airport. As such, it shall have the functionalities of status monitoring,
command over devices, process variables reading, process setpoints modification, alarm
treatment, fault treatment, historical and current trends generation, historical data storage and
reporting.
Among others, the functionalities considered are as follows:
13.1.5.1.1 Device usage times
The BMS shall be equipped with the historical running times storage functionality for all
electromechanical equipment under its supervision.

13.1.5.1.2 Energy consumption Control and energy Management
The BMS facilities control system shall implement different functionalities to facilitate Energy
efficient management by Engineering and Maintenance personnel.
The BMS shall allow different levels of energy consumption configuration, depending on
production but without reducing the comfort of the users. The control system shall also be
capable of evaluating the unit energy costs of the installed equipment whose switching on and
off is under supervision.
The control system of the facilities shall allow slumps, in case of overloads when the defined
maximum level is exceeded, turning off equipment or zones programmed by the user so that
the differential jump is avoided, prioritizing safety and comfort at all times.
These actions will facilitate the transmission of clear and reliable information on the energy
efficiency of buildings to other interested systems and areas, such as Environment. The
incorporation of these functionalities to the facilities control system presents both security and
economic and environmental advantages.
13.1.5.1.3 Historical data storage
The BMS will store all the data received and processed. All signals and alarms historic data will
be collected. The latter will be stored without a time limit, while the signals corresponding to
sensor readings will be stored for a minimum of three (3) months on the history server.
In any case, these records shall be configurable, being able to modify the specifications of each
variable at will. The stored data should be easily exportable by the user to other tools for
reporting, analysis and statistics not covered by the basic functionality of the system.
13.1.5.1.4 Via Web System Access
The BMS shall be accessible from any terminal on the network through a simple web browser.
Web access to the system should be restricted by user privileges, with different levels of access.
Through this access, any member of the organization, with the appropriate privileges, will be
able to view and interact with the available information, in real or historical time.
13.1.5.1.5 Database design and structure
The System shall provide a Database on which all the data managed by the BMS will be stored.
The historical database should be relational, capable of recording data in real time, with
extensions in queries for data collected in real time and resistant to errors in communication
with information providers.
13.1.5.1.6 Dashboards
Dashboards are the interface that the user will find to interact with all the functionality of the
system and in particular with the Process Manager.
The operator's screens shall have synoptics that allow viewing with colour codes, at least the
following:
 Operating status of the different elements of the system;
 BMS communications with external systems status;
 System time.
The main characteristics to be fulfilled by the Dashboards will be:
 Control panels and process flow configuration;
 Follow-up and presentation;
 Service indicators;
 Presentation of alarms.

13.1.5.1.7 Analysis and report generation
The BMS should incorporate reporting tools. In addition to the predesigned reports, the system
shall include tools that allow the user to configure their own reports. Any of data presented on
the Database will be available to be incorporated on the reports.
13.1.5.1.8 System monitoring and alarm handling
The BMS will incorporate management screens for the alarms and incidents detected in the
system itself, which allow the operator to supervise its operation in real time and perform a
statistical analysis of failures.
13.1.5.1.9 Alarm Management
The System will incorporate in the BMS, Alarms and Incidents Management Dashboards which
allow an operator to supervise the operation of the system in real time and carry out a
subsequent statistical analysis of incidents.
The Alarms management shall be configurable so that it is feasible to:
 Set an alarm;
 Send messages upon receipt of alarms;
 Deactivation of alarms.
The System will manage technical and operational alarms. Technical alarms will indicate
incidents or failures (and their recovery) such as:
 Failures and recoveries of the elements that the BMS controls and supervises;
 Incidents in BMS communications with external systems.
In general, the system should allow full supervision of the technical and operational environment
under its responsibility.
13.1.5.1.10 Users Management
The BMS will have system administration tools that allow user and usage profiles management.
The System shall implement user keys and password to identify access to the system.
Each user, registered in the system, will be assigned to one or more user groups. Each group
will have a usage profile that will limit the functionality that can be performed by an operator.
BMS Users Management shall have at least the following functionalities:
 Add and remove users;
 Assign a group to a user;
 Configure usage profiles for different groups;
 Configure the functionality of each profile.
13.1.5.1.11 Redundancy Requirements
Much of the information handled by the BMS is crucial for the Engineering and Maintenance
division management. Therefore, high availability characteristics are required in the most
important services of the system. The application core shall be redundant. In this way, in case
of failure of any of the elements of the system, there will be no loss in its functionality.
Likewise, the redundancy in the communication drivers with the field elements shall also be
guaranteed to ensure the reception of data even in the event of a system failure. These drivers
shall also have temporary storage buffers to foresee the possible disconnection of the history
module.
The terminal service shall be installed in suitable equipment to guarantee high availability as
well as the performance characteristics defined in this section.

13.1.5.1.12 Process Management
The BMS Process Management shall provide tools that:

 Allow the supervision and monitoring in real time of the parameters of the facilities;
 Manage the received alarms;
 Undertake the necessary actions in coordination with other areas of the Airport.
The Process Manager shall allow engineering and maintenance processes to be modelled,
implemented and managed. It shall meet scalability, high performance, fault tolerances and
quality of service capabilities to be accepted as an infrastructure mission critical component.
The Process Manager shall be perfectly integrated with the Document Management, so that the
tasks that will involve the Document Manager and especially those that are subject to quality
regulations are explicitly marked.
The main functionalities that the Process Manager shall provide are:
 Assign activities to personnel automatically and according to established criteria, or
according to workloads;
 Remind people of their activities, which are part of a queue in the workflow;
 Optimize collaboration between those who share activities;
 Automate and control the flow of information, documents, data and images;
 Proactively assign to the people who shall execute the activities, all the necessary
resources (Documents, information, Applications, etc.);
 Define and control alarms according to time, event or condition criteria, thus causing a
message to a supervisor, as well as an "escalation" of activities for other people to
resolve, and / or automatic resignation;
 Modify processes and manage exceptions in real time, that is, allow modifying any
process instance already started, without the need to start it again and without the need
for computer programming;
 Provide an online view for Dashboard supervisors that include the status and history of
each process, each activity and human resources performance;
 Send each user their activities and alerts, regardless of their geographical location, (WEB
technologies, e-mail, SMS, mobile devices, RMS);
 Provide metrics for those responsible for the area and quality (ISO standards), both for
the purposes of Continuous Improvement and Indicators of Operational Quality and
Resource Management;
 Easily integrate with other systems, applications (AOCC, CRM, etc.);
 Provide a high level of support for human interaction.
13.1.5.1.13 Document management
Document Manager will be in charge of processing the information available to the Engineering
and Maintenance department so that it can be used when it is needed.
The Document Manager will allow to archive existing information in any format (images, office
application documents, faxes, emails, audio, video, etc.). By associating structured information
to the captured document (indexing), its subsequent consultation, recovery and treatment will
be made possible. In addition, content management will be contemplated that allows the
organized retrieval of system information and the subsequent processing for publication in
other media.
It will also have the automation of documentary workflows (task distribution, monitoring and
archiving), properly integrated with Engineering and Maintenance Process Management, so that
during the evolution of a process, documents and tasks are passed from one participant to
another, according to pre-established rules. Each document profile shall have associated
corresponding security information, which can be defined at multiple levels.

13.1.5.1.14 Analysis and Reports
The BMS should incorporate reporting tools. These reports will be predesigned and will be
generated by the System without any additional configuration by the user. The system will allow
the issuance of customized reports by the user.
13.1.5.1.15 Data Analysis
The BMS will allow to present analysis on the data selected by the operator, both graphically
and numerically:
 It will provide statistical analysis tools that allow calculating the Data series main
parameters;
 It will allow the preselected variables to be measured interactively and presented in the
dashboards incorporated in the HMI;
 Operator will be able to present large volumes of data in multidimensional cubes that
allow you to navigate information in a dynamic and intuitive way. The information will
be available through quick access, without depending on the amount of source data or
the complexity of the queries;
 Sorting and filtering algorithms can be applied to the results of the analysis;
 The analysis carried out will be stored in a common repository that allows a single
access to the information;
 It will allow export to Excel office automation tools to provide formatted output of
reports.
13.1.5.1.16 Data Storage
The system will record all data, both raw information received from external sources and the
one processed and generated by its own operations.
13.1.5.1.17 Database provided information
The system shall incorporate a Database with the relevant and properly structured information
regarding the following points:
 Documentation;
 Alarms and Historical control parameters;
 All the information received from the control systems on the parameters that treat:
o All the alarms generated on the controlled parameters and their evolution over
time;
o Information received from the different control subsystems (measurements).
All these data will be gathered for historical data and subsequent analysis.
13.1.5.1.18 Indicators
Through the information processed in the Process Manager, the BMS will prepare indicators of
the significant parameters to be controlled.
The SGI shall calculate:
 Operational indicators that will reflect the status of activities under the Engineering and
Maintenance responsibility;
 Resource indicators that reflect the workload status of the area's resources.
All these indicators shall be provided to the AOCC system so that the division indicators of the
can be controlled from there.

13.1.5.1.19 Requests and Incidents Management
The System will allow the monitoring and control of incidents, complaints and suggestions from
the airport area.
Once the request or incident has been duly documented and its resolution has been drafted,
the BMS will inform of its closure. The BMS shall also be able to automatically open new requests
or incidents that it will report for its management.
The definition of the necessary fields for each complaint will be configurable by the user.
The system will allow you to predefine various formats of user response documents with the
situations typified as habitual in the management of types of complaints. These formats will be
included in Document Management.
Design Criteria
The facilities that should be under the supervision of the BMS are as follows:
 HVAC;
 Energy and electricity;
 Plumbing and Sewerage;
 Natural gas;
 Illumination;
 Mechanical transport;
 Fire detection;
 Aircraft Assistance Integrated Management and Monitoring System;
 Pneumatic waste collection system;
 Hydrological control system;
 Lighting.
Supplied equipment will on one of the following typology groups:
 PLC’s;
 HMI devices;
 Field elements (sensors and actuators);
 Field buses;
 Cabinets and connectors;
 Any device installed on the field and necessary to control the facilities.
The BMS will be structured in three different levels, as described below:
13.1.5.2.1 Central System
This level is made up of servers and operator workstations. The Central System will be provided
with hardware platforms (servers) and the software that runs on them. All the information
related to control points, associated values and measures of both current and historical status
are stored in a relational database.
The workstations are the consoles through which the operators carry out all kinds of operations.
The latter may access and command, according to the established segregations and privileges,
the control points and functions that are the object of their area of responsibility.

13.1.5.2.2 Controllers
The Programmable Logic Controllers (PLCs) oversee the control and supervision of the processes
and are responsible for reading values and acting according to the readings and parameters set
by the users of the installations. Controlled equipment starts and stops, optimizing its operation,
according to the executed sequences and algorithms. In addition, PLC update the servers'
database and generate alarms when they detect abnormal operations.
PLC connection with the Field Elements is carried out through the corresponding input / output
modules. Each PLC consists of hardware platform, I/O modules, communication hardware
modules, an OS as well as the specific programming of the installation under control.
13.1.5.2.3 Field Elements
Field elements are devices, both sensors and actuators, through which the PLC controls the
installation in question. In the first case, sensors provide information to the automaton and
whilst the actuators are the elements on which the PLC acts.

The System shall implement interfaces with systems that will be operating at the Airport and
such integration will be carried out through the interfaces that each system has developed and
enable the desired functionality.
At least the following interfaces will be considered:
 CCTV interface;
 Master Clock System interface;
 BHS interface;
 GIS interface;
 HVAC;
 Energy and electricity subsystems (e.g. LV, MV, etc);
 Power Plant;
 Lighting subsystem;
 Plumbing subsystem;
 Fire alarm subsystem;
 Intrusion subsystem;
 Gas distribution subsystem (if available);
 Managing and monitoring of aircraft assistance;
 Residues management subsystem;
 Mechanical transportation.

The characteristics of these interfaces will be at least the ones included in the following Figure:
OTHER SYSTEMS
ERP VoIP WLAN PAS

OPERATIONAL
SYSTEMS
BMS MCS
Figure 85-Airport systems to be integrated with the BMS

The BMS Supplier shall be responsible for providing and maintaining an IP addressing scheme

The Supplier shall analyse, design, build, install and implement the applications.
Amaala Airport shall achieve the maximum level of integration in Maintenance Management
and in the Control of Airport facilities in this system. For each of the applications, a dedicated
project team shall be established.
All Systems integration will require testing, adaptation and consolidation processes to be
established. The Supplier shall consider the design and realization of all the information
exchanges between the application and any external entity that needs or provides information,
as well as the field subsystems that are part of the system.
The Supplier shall design and carry out a test plan that guarantees the correct operation of the
system in all its phases.


Software and hardware components such as systems PLC´s, HMI, Field Equipment (Sensors and
Controllers), buses, racks and connectors are included in the scope of the BMS.
manufacturers.
manufacturer.
without hard connections (i.e. using quick-connects, plug-and-socket connections, etc.).
(as pre-installed within the Data Centres and communications rooms), shelving, support
quantity documents.
All systems should operate under Saudi Arabia’s environmental conditions.
Internet access shall not be allowed from BMS workstations.
All peripherals provided shall be certified for use on the BMS platform.
All applications running on the BMS platform shall be certified by the BMS provider. The
equipment shall be standardized and certified by the Supplier. The documents shall be delivered
with them.

The BMS system shall be based on standard components which have already been used in

The BMS shall comply with the following applicable criteria:
 Scalability: The system will allow the expansion of its hardware and software
components without incidents on operability;
 Availability: The System shall support high availability and fault tolerance. It shall have
redundancy of critical elements.
 Integrable and open: It will allow easy integration with other systems in the airport
environment, using standard technologies on the market and subject to the Airport
integration guidelines;
 Reliability: The results and calculations obtained by the system shall reflect a reliable
measure of reality;
 Configurable: The system shall allow the parameterization of its functions to adapt it
to different circumstances of operation;
 Standardization: The System shall comply with the standardization standards defined
and approved by Amaala Airport. The installation, integration and testing of this system
are also subject to Amaala Airport standardization criteria and technological guidelines;
 Legality: The System shall submit to the current legislation regarding metrology and
equipment calibration as well as any other applicable regulations.
Reliability, Mean Time Between Failure (MTBF) and maintainability, Mean Time To Repair (MTTR)
shall be provided, as well as supporting hypotheses and calculations, which make it possible to
determine the availability for the system and, as a consequence, the availability of the
functionality provided. In this regard, the following will be considered:
 The hardware and software architecture of the systems, especially:

o High availability configurations;
o The accessibility and modularity of the replaceable components;
o The reliable demonstration, through real data of reliability, maintainability and
availability, of the suitability of the elements foreseen in other real facilities with
similar levels of demand.
 The level of spare parts;
 The time corresponding to the scheduled shutdowns of the systems for maintenance
work.

The attached table specifies the minimum availability requirements for system elements:
System element Availability (%)

Servers 99.99
Operator positions 99.00
Table 131-System Availability figures

maintaining an “As-Built” BMS equipment schedule for the facility once constructed) and other
The following table sums up in a high-level overview the deliverables to be provided by the BMS
BMS-DES-1 System Detailed Design for installation Design Phase
BMS-DES-2 Software Detailed Design (system architecture, Design Phase

BMS -DES-3 Testing & Commissioning Plans Design Phase
BMS -DES-4 FAT and SAT test Procedures Design Phase
BMS -DES-5 Maintenance Plan Design Phase
BMS-DES-6 Integration Plan and Interfaces Design Phase
BMS -DES-7 Training Plan Design Phase
BMS -DEL-1 Cable Management Document Delivery Phase
BMS -DEL-2 Configuration Control Document Delivery Phase
BMS -DEL-3 Test & Commissioning Reports Delivery Phase
BMS -DEL-4 Integration tests Reports Delivery Phase
BMS -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
BMS -DEL-6 Application user manuals Delivery Phase
BMS -DEL-7 As Built drawings Delivery Phase
Table 132-BMS Project Deliverables


Main organizational units to be involve in BMS use and maintenance are presented below.
Airport Operations – Monitoring and

02.02.01 Maintenance
Mirage Terminal Building Control
Airport Operations – Staff Monitoring and

Terminal Control
Airport Operations – Cargo Monitoring and

Terminal Control
Airport Operations – Monitoring and

Airfield Operations Control
Monitoring of the
02.03.04 Fire Prevention User
alarm system
Monitoring and
03.01.01 Facilities Maintenance
Control
Monitoring and
03.02.XX Utilities & Equipment Maintenance
Control
Monitoring and
03.03.00 Electronics Maintenance
Control
Maintenance Control &

03.04.XX User Reports and Statistics
Evaluation
Alarm and Monitoring

03.06.00 Maintenance Support User
hub
Maintenance of
05.01.00 Airport Security Maintenance
Security Systems
Monitoring equipment
06.XX.00 Technology Maintenance
status
Mirage Terminal - Facilities Monitoring of systems

& Equipment status
Table 133-BMS Airport Organizational Units Involved

13.2 Services

equipment supplied.
parties.


profile.
13.2.3 Installation
Cabling
location.


Labelling
 Cable function;
the cable).
 Cable type;
 Cable number;


prior to testing.

operates correctly.
cutting power to equipment, pulling out cables, etc.) across the different components.
ORAT Activities
 ORAT set-up;

13.2.5 Training
 Trainers;
 Engineers;
Factory Training
maintenance
On Site Training


necessary.

trays, pipes, etc.;
completion.


be quoted.

14 CORPORATE SYSTEMS
14
14 | CORPORATE SYSTEMS
14 CORPORATE SYSTEMS
14.1 Enterprise Resource Planning (ERP)
14.1.1 Introduction
The Enterprise Recourse Planning System (hereafter ERP) software is a central processing facility
or hub, handling all data and processes associated with the business activities involved in the
operation of an airport.
The ERP shall consist of different modules that handle such data or processes like estimating,
purchasing, administrative overheads as well as all accounting and financial activities. The final
result shall be a software system that aggregates all the essential activities of airport business
into one integrated system.

INCITS SQL database standards
ISO 9126 Software Quality
IATA SIS IATA Simplify Interline Settlement
SAF-T Standard Audit File for Tax
IFAC International Standards on Auditing (ISAs) and International

Standard on Quality Control
Table 134-ERP applicable References, Standards and Regulations

The Enterprise Resource Planning System referred to as ERP is a back-office application that
shall be provided in order to enable the Airport Operator to manage his core business processes
from one integrated system.
The system shall be a proven, state-of-the-art, fully scalable, fully redundant solution using COTS
products.
Each module as listed and described below shall provide a comprehensive reporting facility. In
addition, the ERP System shall provide for a full range of ad-hoc and custom reports that can be
predefined or user generated for each module.

All applications in this suite of systems shall have a single consistent set of navigation, ‘look &
feel’ and help functions. The functional architecture of the ERP system could be as follows:
Table 135-ERP Functional Architecture
The ERP shall be able to invoice the aeronautical billing with the income data received from the
AODB about the Flights/Airlines consumptions.
Its deployment is essential to manage and ensure airport incomes and payments.
The Supplier shall provide a proposal for the design, procurement, installation, integration,
testing & commissioning for the ERP System at Amaala International Airport. Including the
following tasks:
 All activities which may be necessary to complete the design and installation of the
ERP devices;
 Installation, setup and configuration and associated activities necessary to deliver
an operationally and ready ERP System. The IP addressing scheme and VLAN
requirements shall be developed with the LAN/WAN Supplier;
 Supply of hardware as specified for the system;
 ERP System application in charge to interface all the other systems that may be
required to make the system fully operational;
 Installation, configuration and testing of the system hardware and software.

A physical representation of the ERP System architecture has been presented below. Integration
with other systems shall be essential to obtain the necessary data to undertake its function.
The ERP shall be integrated with the Aeronautical Billing in order to obtain all data for
aeronautical invoicing.

Further information about integration in section System Integration.

Administrative Offices
ERP WS ERP WS
Printer ERP WS
AIRPORT NETWORK
ERP ERP
Server – A server – B
ESI ESI
ERP Configuration
Workstation
Figure 86-ERP Architecture
The system shall be based on redundant link architecture, such that no single failure in
connections between workstations or central servers will result in any loss of system
performance.
The system shall utilize fibre optic and copper cabling infrastructure for the backbone of the
announcement distribution, management and maintenance operation. Equipment shall provide
the appropriate interfaces to the copper and fibre optic cabling to implement all required paging
and associated functions.
The following elements will compose at least the scope of supply for the ERP system:
 Servers: The server coordinates all activities of the ERP System and provides storage
for databases and system logs. The ERP System shall utilize physical servers. A
variety of redundancy technologies can be implemented to facilitate maximum
uptime. These shall include Redundant Array of Independent Disks (RAID), failover,
and clustering configurations.
 Workstations: specific workstation will be procured for the ERP, but also, the
Supplier shall ensure that the ERP application is accessible from the client
workstations via web.

ERP management tool shall provide access to the data stored in the database through a simple
and intuitive user interface. This tool shall take care of the operational environment functions
related to:
 Financial Module & Accounting Module:

Gathers financial data and generates reports according to International Financial
Reporting Standards such as ledgers (General Ledger, Accounts Payable, Account
Receivable, and Cash Book) or periodic reports for financial reconciliation such as
quarterly financial statements.
The system needs to perform customer billing and to keep and track budgets and
forecasts. The ERP functionality shall be linked to the Aeronautical Billing System.
 CRM Module:
Client management, the module shall manage and store all client information in a
collaborative manner.
 Reports Module:
The system shall be able to create template and custom reports.
 Human Resource Management System:

Collects information about Human Resources (HR) to ensure the easy management of
employee data. The system combines different HR functions such as storing employee
data, managing payrolls, recruitment processes, manpower planning, etc. The time and
attendance functionality shall be linked into the Automatic Access Control System
(AACS).
A compliance reporting mode shall be provided to generate reports for compliance
with government, regulatory, local, IATA/ICAO reporting requirements. The HR data
shall be compiled, formatted and exported according with each specific regulation.
 Business Intelligence System:

This module shall improve Enterprise visibility, increase information capabilities to
support enhanced decision-making process and enhance enterprise consolidation
processes to respond to rapidly business needs.
 Materials Management:
The Materials Management functionality of the ERP System shall be obtained through
five integrated systems and sub-systems:
o Maintenance Management Tool: This tool shall provide status reports and
document giving details or summaries of maintenance activities and shall
include, but not be limited to, Asset Management, Procurement process and
Inventory Accounting.
o Material Requirement Planning: The ERP system shall support maintenance
planning, material planning and purchasing management.
o Procurement Management: Covering all the procurement process stages.

o Procurement Contracts Management: Covering activities such as contract

administration, relationship management and delivery management.
 A flexible and customizable requisition, commitment and approval
workflow process to support procurement of all types of spares and
components and materials at the airport;
 Automatic capture and reporting of vendor performance metrics such as
performance-to-schedule, administrative accuracy;
 Engineering drawings, customer contracts, special mark and pack
instructions, or any other documentation to be linked to purchase orders
for use by buyers and suppliers;
 Seamless integration with the Maintenance Management Tool
requisitioning functionality which shall not be duplicated across systems.
o Inventory Management: This ERP module shall support:
 Tracking and controlling of inventory costs by department;
 Automatic order generation;
 Auditing capabilities;
 Comprehensive receipt and issuance functions;
 Seamless integration with the Maintenance Management Tool Inventory
Management functionality which shall not be duplicated across systems.
 Property and Assets Management:

This ERP module shall track the ownership of each asset, the current value and status
of each asset and the ability to add depreciation models to individual assets. It usually
includes but not limited to:
o Asset Data Capture: Asset Data shall be obtained when required form the
database of assets maintained in the Maintenance Management Tool in addition
to direct entry of data for Financial other types of assets such as Intellectual
Property Assets, Financial Assets or IT Assets.
o Contract & Lease Management: The ERP module shall keep records of all
contracts issued to tenants and it shall generate invoice data based on the
conditions defined in the lease contracts. These Module shall be integrated with
the Financial System module. The System shall provide the ability to perform
Financial Reconciliation activities across the General Ledger accounts on a
periodic basis.
o Non-Aviation Billing: This ERP module shall handle all billing information not
directly associated with the airline or aviation activities such as rents, utilities, IT
services, parking, etc. This information shall be consolidated in a single invoice
for each tenant or customer and this shall require interfacing with the SCADA
system directly or through the BMS System.
o The ERP shall be fully integrated with the Aeronautical Billing System, which shall
take care of all invoicing processes with airlines exchanging such information
later with the ERP for global accounting.

Design Criteria
The ERP system as a whole shall meet an availability rate of 99.95%. This shall require that key
components are duplicated and data maintained concurrent between such duplications, that
access to this data will be distributed, and accessible via alternative communication routes and
the failure of one component shall not impact the performance and availability of other
components.

The ERP System shall be dependent of the Airport Network (LAN/WAN) to provide delivery of
data across network infrastructure between integrated systems. The ERP shall interface to the
following systems:
 Airport Operational Database (AODB): Ongoing Airport operations shall be

supported by the AODB, which shall be linked to the ERP data and systems as required
via Airport Network.
 AODB Aeronautical Billing module;
 Building Management System (BMS);
 Master Clock System (MCS).
Aeronautical
AODB
Billing
AIRPORT NETWORK
MCS BMS ERP
Figure 87-Airport systems to be integrated with the ERP
All invoicing process with the airlines shall be carried out through the aeronautical billing system,
exchanging such information later with the ERP for global accounting through AODB-ERP
integration. If any topic has to be invoiced to the airlines directly from the ERP (non-aeronautical
fees, like the renting of spaces for the tickets selling), such invoicing will follow the guidelines
about IATA Invoice XML Standard, IS-XML (Integrated Settlement XML) indicated at the
aeronautical billing system

The ERP Supplier shall be responsible for providing and maintaining an IP addressing scheme


The ERP operating system must provide a seamless solution. The management software shall
be an industry standard, scalable, reliable, multi-user platform.
The ERP system shall be based solely on TCP/IP and capable of supporting this environment.
All components of the ERP system shall be redundant to ensure the continuation of service.
From multi-path wiring to redundant switches and servers to RAID disk arrays on servers and
interleaving workstations across switch devices, ERP installation shall be protected so that no
single component failure can ‘compromise’ the overall service.
The Core ERP Equipment will be installed at two separate Data Centres with independent Power
Supply Circuits for the ensuring of higher level of the redundancy of the system.
ERP system has to be designed and implemented based on a high-speed LAN architecture with
Different segments of the switched Ethernet LAN shall have the possibility to be configured for
different amounts of traffic in order to economically pair speed with need.
The bandwidth offered by switched Ethernet has to allow the integration of new ERP functions
and applications on the LAN.
The ERP software shall be 64-bit and based on an open system architecture.
development environment.
Software code and functionality shall be well documented in order to facilitate maintenance by
personnel other than the original programmer.
patches applied.

The Supplier shall deliver all required system and application software for a fully functional
system. Each application shall be identified by the generic, off-the-shelf name. Software
provided by the Supplier to operate the system shall be delivered in a ready-to-run form,
including all necessary utility programs and documentation.
Software shall use industry standard components. Software shall not contain any proprietary
interfaces or components. Software shall use industry standard application development
software such as Java, C++, CORBA, and XML. Supplier shall state what application development
software has been used, for Design Consultant’s review.
All supplied software running on servers or clients shall synchronize to a Network Time Protocol
(NTP) source. The Supplier shall coordinate with other entities the exact IP address of the NTP
source.
System updates: The system shall be based on a concept that all necessary software
components shall be downloaded by the workstations at the time of successful log-in. Any
modification to the software configuration shall therefore only be done at the server level. Such
modifications shall take effect by logging a workstation out and in again. Updates to the ERP
systems shall be distributed from the central platform servers and become active at the
individual workstations upon new login.
The ERP configuration as previously described shall be by proprietary software application
applicable to the selected ERP vendor which shall require approval by the Client Design
Consultant. This application software shall be installed to client and server computers provided
by the ERP Supplier, and accessible only with authorized levels of user privileges.

Software and hardware components as application servers are included in the scope of the ERP
System.
manufacturers.
manufacturer.
computers offered by the Supplier are of a make and type in common use in Saudi Arabia

quantity documents.
Internet access shall not be allowed from ERP servers.
All applications running on the ERP platform shall be certified by the ERP provider.
The ERP system shall be based on standard components which have already been used in
Head End Equipment Capacities:

The Supplier shall provide software licenses capable of supporting the quantity of customer
workstations to be connected to the ERP system and servers, etc. as designed and installed as
part of this specifications.
Supply, installation and commissioning of software application and any other software that may
be required to make the system fully operational to meet client requirements.

Regarding communications, the ERP deployment will fulfil the following requirements:
 The ERP system should be an IP-based system, with an Ethernet network and TCP / IP
protocols;
Regarding Energy, the ERP deployment will fulfil the following requirements:
 For the Servers it will be necessary to have electrical connections of safe power, coming
from UPS;
Supplier;
The ERP System shall be an IP-based system and all wiring from all HW stations are expected to
be as high as possible using the CAT-6 UTP cable, with Ethernet and TCP / IP protocols.
System Capacity
At peak demand, system utilization of resources shall not exceed Sixty percent (60%) of capacity.
The systems shall be capable of supporting priority orders data queuing and transmission to
ensure immediate delivery of higher priority and time sensitive messages.
Utilization
For any 20 (twenty) minute sampling period of normal peak hour operation, system utilization
of resources shall not exceed 50% (fifty percent) of capacity. Utilization in this context refers to
CPU usage; CPU usage is obtained through the use of the operating system tool System Activity
Reports (SAR).
Scheduled Downtime
reasons for downtime, however, where components are duplicated there shall be no interruption
to system services. The following reasons shall be acceptable causes of downtime:
 If the operating systems of the servers require maintenance or updates, or if the servers
require system maintenance, each server shall be brought down individually to be
updated/maintained, such that at no time is more than one server down;
 If the operating system of the end devices requires maintenance or updates, or if the
end device requires system maintenance, the end device that requires the maintenance
shall be brought down during non-peak hours of operation;
 The Employer may authorize maintenance/updates on the end devices during other
than non-peak hours if the particular end device is non-functional without having the
maintenance or updates performed.
Response Time
Response time criteria shall be met under maximum loading conditions:

 The transmission delay for on-line critical business transactions shall not exceed 1.0
second total for 95% of all transactions. The remaining 5% of transactions shall not
exceed 2.0 seconds;
 The time required for servers to complete a full fail-over switching shall not exceed one
(1) minute;
failure shall not exceed fifteen (15) minutes (e.g. after an extended system outage or
failure of both main and standby servers).

The system shall be built and installed in accordance with the guidance given in in the following
1. NFPA 72:2010;
2. BS EN 54-2;
3. BS EN 54-4;
4. BS 5839-8:2008;
5. IEC 60849:1998.
The following parameters shall be considering when designing and deploying ERP system:
 Availability:
o The whole of the ERP systems will be backed up via a separate emergency battery
system that will be capable of operating for a specific period.
o The failover and monitoring system shall monitor both hardware and software
elements. The software monitor manages all active services related to the ERP
System. This includes the server-based applications, interfaces, database
elements, web services.
o The ERP System shall support HW monitoring, failover, and failback. During a
failover event, additionally, alerts for failure events can be sent via e-mail with
details of the event including device name, location, amplifier channel and the
system conditions which caused the system to fail over.
 Scalability:
o The ERP central extension and the management application must be scalable to
support a 100% more users, clients, interfaces and incoming data, etc, beyond
the requested values with constant response time when adding hardware. Such
scalability shall support the extension of Amaala Airport according to the current
Airport Master Plan.
 System Stability:
o It should be able to support concurrent use by multiple operators in non-stop
24 hours-a-day operations.
o The whole system shall be equipped with a UPS solution to maintain the system
stability.

 Reliability:
o The system provided shall work 24 hours a day. The system shall have a high
o The Supplier shall provide within the proposal detailed information regarding
technical specifications of each of the proposed equipment, materials, and
accessories demonstrating integration / interfacing amongst them.
o The Mean Time Between Failures (MTBF), Mean Time To Repair (MTTR), Mean
Time Between Critical Failures (MTBCF) and Availability figures of all the
equipment proposed should be provided and the overall system, indicating the
method used for the calculation, such as MIL-HDBK-217. If sub-system MTBF,
MTTR, MTBCF, and Availability numbers are submitted, these shall be rolled up
into an overall system MTBF, MTTR, MTBCF and Availability numbers. The MTBF,
MTTR, and the MTBCF numbers of other sites with similar types of equipment
installed should be provided so the quoted numbers may be verified.
o A list of parts which are unique to the system (such as sensors or locks) and which
in case of failure would be considered critical and cause a suspension of service
should be provided.
o The MTBF, MTTR, MTBCF and Availability numbers for the communication
equipment and its subsystems should be provided separately.

With the progressive development of the different stages of Amaala airport Master Plan and
with the increase in the number of passengers and flights, additional information, charges,
clients and users will have to be added to cover the new environments to be built, although the
system will have capacity to assume this increase in the number of managed devices without
requiring any system upgrade or new investment.
The system and supporting tools and applications selected shall allow for future expansion, with
the ability to expand the total storage and number of users as needed without significant
upgrades or modifications to the system.
ERP servers shall have excess capacity to avoid an increase in processing time in peak hour on a
busy day.
Scalability: The ERP System to be procured shall cover the airport needs for all the phases
regarded at the airport Master Plan.
For future expansion it shall be possible to include additional resources. The ERP environment
will be able to support a future growth in the next years of operation. System resources
(processor speed, memory, disk space, network bandwidth) will be dimensioned accordingly.

Redundancy
System application head-end processors shall be installed in the Data Centres at the Airport.
The server technology to be finally deployed in the Data Centres should be chosen. The use of
blades should be encouraged as should be the use of virtual server technology.
minimum.

reliability available in each component and through redundant servers.
Load Balancing: The system shall run on fully load balanced server hardware. Load Balancing
shall be achieved by allocating messages and distributing load among interchangeable servers
and provide support for transaction queuing.
 Multiple hot-swappable redundant power supplies;

 Servers shall utilize a redundant server pair with automatic fail-over to ensure
that performance and high-availability objectives are met without manual
intervention;
technology;
disruption to the network or applications;
 Multiple load sharing application servers or other configurations shall be
considered viable alternatives to redundant application server pairs if
equivalent or better system redundancy and resiliency can be demonstrated.
To this scope, continuous monitoring of the status of both internal services and servers is
required.
The processing capability of the server configuration shall be configured to take into account
both the message throughput and any other factors such as the processing load required for
each message.


(i.e., the System Administrator's workstation).
A failure shall initiate an alarm and add a failure record. Additionally, the system administrator
shall receive a warning message on the system administrator workstation, notifying of the
failure.
The system shall also be capable of providing pager and e-mail notification. Server failure shall
include any hardware or software-based failure.
All failures of the system shall be logged at a central control point (i.e., Application Server). The
failure shall initiate alarms and reports (e.g., time and date of failure event.

assessments, commissioning plans, FAT/SAT procedures and test certificates, (and other
handover materials as required by the Employer.
The following table sums up in a high-level overview the deliverables to be provided by the ERP
ERP-DES-1 System Detailed Design for installation (controllers’ Design Phase

location, type of controllers, sensors, cabling, fixation… etc)
ERP-DES-2 Software Detailed Design (system architecture, Design Phase

ERP-DES-3 Testing & Commissioning Plans Design Phase
ERP-DES-4 FAT and SAT test Procedures Design Phase
ERP-DES-5 Maintenance Plan Design Phase
ERP-DES-6 Integration Plan and Interfaces Design Phase
ERP-DES-7 Training Plan Design Phase
ERP-DEL-1 Cable Management Document Delivery Phase
ERP-DEL-2 Configuration Control Document Delivery Phase
ERP-DEL-3 Test & Commissioning Reports Delivery Phase
ERP-DEL-4 Integration tests Reports Delivery Phase
ERP-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
ERP-DEL-6 Application user manuals Delivery Phase
ERP-DEL-7 As Built drawings Delivery Phase



Main organizational units to be involve in ERP use and maintenance are presented below.
01.03.00 Leases & Facilities User Lease and Facilities

Administration Administration
06.04.00 IT Support Technology IT Maintenance
09.05.00 Administrative Services User Administrative services
10.XX.00 Finances Affairs Users Financial Accounting
11.XX.00 Corporate Services User Corporate Services
Table 137-ERP Airport Organizational Units Involved

14.2 Services

equipment supplied.
parties.


profile.
14.2.3 Installation
Cabling
location.


Labelling
 Cable function;
the cable).
 Cable type;
 Cable number;


prior to testing.
operates correctly.

ORAT Activities
 ORAT set-up;
14.2.5 Training

 Trainers;
 Engineers;
Factory Training
maintenance
On Site Training

necessary.


trays, pipes, etc.;
completion.

be quoted.

15 OTHER SYSTEMS
15
15 | OTHER SYSTEMS
15 OTHER SYSTEMS
15.1 Airport Operations Control Centre (AOCC)
15.1.1 Introduction
The purpose of the AOCC is to provide the airport the ability to effectively and efficiently
performs, analyses and improves operations and maintenance tasks required to maintain
business continuity. Any disruption to the control and information management will negatively
impact the operation of the Airport.
This chapter describes an infrastructure, unlike the other systems in this document, which
provides fast and reliable services to airlines, passengers, ground handlers and cargo companies
by 24/7 planning, dispatching, and responding to various events at the airport, such as:
 Real time operation coordination;

 Aircraft ground services (load/unload);
 Transit and transfer procedures;
 Runways & taxiway management;
 Stand Management (On block/Off block timings, pushback times, etc.);
 Terminal Resource Allocation (Stand, Gate, Check-In Desk, Security Lane, etc.);
 Maintenance Operations Management (BMS, APM, HVAC, etc.);
 Baggage Operations Management (BHS);
 Incident Emergency Management;
 Radio Dispatch.
Due to these tasks of critical role, the AOCC’s location is one of the most important
requirements, so other ones related to the distribution requirements, ICT requirements, and
visual tools requirements.

IATA IATA Airport Development Reference Manual
(9th Edition – January 2004)
UL Standard on Electrical Components
BS 7807:1995 Standards on design, installation and maintenance

of integrated systems
ISO TC 159(All working groups Ergonomic Standards

and subcommittees)
ISO9001 Quality Management
BS 7671:2008 Incorporating The IET Wiring Regulations.

Amendment 3:2015
BS EN/IEC 62305 Lightning Protection Standard.
IEC 61340-5-1 Electrostatics: Protection of electronic devices from

electrostatic phenomena; General requirements.
Table 138-AOCC applicable References, Standards and Regulations

15 | OTHER SYSTEMS

The facility shall be designed to create a working environment that shall be ergonomic and
suited to the purpose of supporting collaborative working, with the support of the
communications and the IT systems. The facility shall include a wall screen to enable focused
information sharing as well as the working positions design and layout and should include
meeting and discussion spaces along with a range of amenities for staff comfort.
The main objective associated to this infrastructure is to centralize the operative procedures
which are the effective movement around an operation day.
It is important to consider deploying the AOCC in a secure area, with limited access from
passengers and vehicles, ideally it is better to have it at airside in the staff terminal or in the
Mirage Terminal. The AOCC access shall be ensured with CCTV and ACS Systems.
Find below a draft design of the AOCC that is includes all services need it in order to estimate
the room size and be able to find the best location for it.
The scope of this system will include the video wall, the management software, furniture and
any necessary ancillary equipment (conference system, KVM extenders…etc.) but excluding all
MEP necessities.

15 | OTHER SYSTEMS
Figure 88-AOCC Room Distribution

15 | OTHER SYSTEMS

Find below the basic system architecture that includes the video wall and the management
software.
Each system (AODB, FIDS, BHS, BMS…etc.) will include its workstations.
Figure 89-AOCC Architecture

Framed on the Passenger Terminal Building of Amaala Airport, the Airport Operations Control
Centre (AOCC) will take care of real-time operation coordinating the different organizational
units at the airport.
The facility shall be designed to create a working environment that shall be ergonomic and
suited to the purpose of supporting collaborative working, with the support of the
communications and the IT systems. The facility shall include a wall screen to enable focused
information sharing as well as the working positions design and layout and should include
meeting and discussion spaces along with a range of amenities for staff comfort.
There is a list of requirements to be assured in the AOCC location:
 Location: This centre shall be located on the airside, in a security restricted area
avoiding the possibility of any non-authorised person to arrive near the sides of the
AOCC. It will not be located with any of its sides on an outer wall, nor landside either
airside. Its access shall be physically restricted only authorized personnel, although
occasionally the access can be authorized to other visitors for specific purposes (visits,
emergencies…). Besides of these access restrictions each technical room should have
restricted access only IT and maintenance staff.

15 | OTHER SYSTEMS
o Operational hours: This area should be used by airport staff on a 24x7 basis,
the 365 days of the year and should be designed to allow operation to meet
these scheduled time and occasional use outside of these hours by prior
agreement.
Design Criteria
15.1.5.2.1 Distribution Requirements
The AOCC physical distribution shall accommodate at least the areas, as per shown in
Erreur ! Source du renvoi introuvable.:
 Reception/Entrance Room and Administrative room;
 Rest Rooms & Toilets;
 Technical rooms: IT room and power room. Including Videowall technical areas;
 Crisis Room;
 Meeting Room;
 AOCC Director Office;
 Training Room;
 Apron Control Room;
 Control main room: Including the following sub-spaces;
o Operation area:
One (1) resource allocation coordinator and one (1) departure/arrival
operator to carry out the following tasks:
 Resource management, preallocation and resolving conflicts;
 Departure and arrival operations management;
 Coordination with ground handlers and airlines;
 Turnaround management;
 Aircraft incident management;
 Duty Manage;
 operator to carry out the following tasks;
 Queue management;
 Management of all parking areas;
 Management of taxi areas;
 Passenger incident management;
 BHS.
o Ground handler and airline area:
 Turnaround management with operations area;
 Incident management with operations area.
o Coordination area:
 Briefing meetings management;
 AOCC resolving conflicts.
o IT & Maintenance area:
 BMS monitoring;
 Maintenance incident management;
 Other SCADAS monitoring;
 Power, plumbing, HVAC and mechanical equipment monitoring;
 BHS monitoring operator and other SCADAs;
 System monitoring;

15 | OTHER SYSTEMS
 Networks monitoring;
 Critical System Management;
 Data Centre supervision.
o Security Room
 Governmental agencies.
15.1.5.2.2 Working Positions Specification
Each working position to be installed at the AOCC shall have the means required according to
the functions allocated to such position and the following requirements:
 Unification of all position in such a way that its number could be increased, reduced or
moved without major impact on the AOCC configuration;
 Working position design to encourage ergonomics and modularity;
 Each working position shall be totally independent, but able to be assembled to
generate the final configuration required;
 The position shall integrate a working surface which will be manufactured with latest
technology materials and dimensioned to host all the required equipment for the
operator. There will be the possibility to include an embedded box for power, voice
and data plugs at one of the sides of the working place. Also, the configuration shall
enable the emptiness and the clearness of the operator working space, facilitating to
hide all cables or obstacles on it. The length of 2.000mm and should have the possibility
to host the required equipment. At least:
o Three or four (24”-27”) monitors;
o Two workstations;
o Mouse and keyboard;
o IP telephone and radio communication devices;
o CCTV equipment. Joystick and keyboard;
o KVM user station;
o KVM display aggregator. Enabling the user to interact with up to two (2)
computers using a single mouse and keyboard simply moving the cursor
across screen borders;
o Network and power plugs and cables;
o Multiple component and composite video source inputs and outputs for the
following:
 Surveillance camera monitoring;
 Off-Air programming;
 VCR/DVD/Blu-ray sources for all common formats;
 Computer video and audio;
 IPTV;
 HDMI;
 Component Video (Y/Pb/Pr);
 S-Video;
 Optical and Coaxial Audio Output;
 Line Level Audio Output;
 IR Input;
 Composite Video;
 USB.
o Room video and audio teleconferencing;
o Program audio from IPTV;
o Voice reinforcement;

15 | OTHER SYSTEMS
o Universal headset and microphone for each operator (integrating audio from
Workstations, IP Telephony, PA, GSR and IPTV audio);
o Video recording of AV sources;
o Audio recording of Control Centre operations in a digital format to be stored
for a minimum period of thirty (30) days;
o Remote control capabilities via touch panel displays;
o Remote diagnostics;
o Expansion capability;
o Printing capabilities, if required.
Within the working position, in the back side, there shall be a closed area designated to host all
the computer and electronic equipment required for the operator activity. Such equipment will
be attached to removable trays which will facilitate all installation and maintenance tasks.
All working positions shall regard a double cable rising and installation paths, separating data
and electric power distribution to all equipment in the position.
The working position shall be ready to be connected to safety earth. All power supply plugs will
be located in a closed and locked place, although some extra power and data connections may
be supplied through an embedded box with flap-lids.
The chair to be used by the operator at the working position shall be an ergonomic 24x7 one,
guaranteeing the right back and head position at work regarding the anatomy or any operator.
The following picture shows a generic example of an AOCC Position
Figure 90-AOCC standard working position
Working positions computers shall be remotely located at the equipment corridor reducing
noise and heat giving off and enabling a higher flexibility on functions allocation to each working
position. The following diagram details KVM architecture to be deployed at the AOCC.

15 | OTHER SYSTEMS
Figure 91-KVM Architecture for workstation connection to the working positions in the AOCC
15.1.5.2.3 Furniture Requirements
Careful design attention should be given to the desk equipment/furniture, because it should be
provided ready for use including all chairs, tables, screens, storage, mounting brackets etc. Desk
furniture shall comply with the following minimum specifications:
 Furniture:
o Provide four (4) square meters per desk;
o Desks shall be of solid core materials utilizing a post and panel design. Hollow
core panel systems using cantilevered surfaces shall not be acceptable;
o Unified frame construction is required in order to prevent movement of the
monitor surface away from the remainder of the desk;
o Desks shall be modular in design for ease of reconfiguration and upgrading;
o There shall be no obstructions for side-to-side movement by the dispatcher
within desk footprint.
 Furniture Technology Requirements:
o Fixed full-width electronics cavity storage shall be provided for CPU equipment
and cable routing, keeping the knee space below the desks unobstructed;
o Cavities shall be vented to allow for passive airflow and should be designed to
accommodate additional fans if required;
o Concealed cavities for cable management and power distribution;
o Each desk shall include cable access drops;
o Desks shall be clutter free, comprising only of HMI and communications
equipment essential to the role. Processing units shall wherever possible be
located outside the AOCC.
 Desk Equipment (additional to the ones mentioned above):
o Line-level speakers (One (1) pair per workstation);
o Keyboard & Mouse;
o Power strips 6-way, twist locks under raised floor;
o 1 x Personal desk light;
o 1 x Vent/air cooling;

15 | OTHER SYSTEMS
o Integral cable management;

o Adapters and cables as required;
o DVI-D to DVI-D single link cables;
o Cat 6A patch cables;
o DVI-D splitter Y-adapter;
o 3.5mm stereo speaker cable;
o Patch panels;
o 6 x RJ-45 CAT6a ports per desk.
 Chairs:
o Ergonomically designed chairs suitable for control centre desks.
15.1.5.2.4 Videowalls Specification and components
Figure 89 provides an overview of the hardware and software making up the overall video-wall
system to be procured for the AOCC areas which may require it. It shall rely on three main
elements:
AOCC Video-Wall main characteristics will be:
 Such video-wall will have a minimum size of four (4) columns and four (4) rows. With
minimum expansion capacity of one column each side;
 Minimum size of each monitor will be 55’’;
 The vertical view angle for the operators respecting to the video-wall must not exceed
the 25 degrees to facilitate a comfortable view;
 Used to present context information which affect to several operators;
 Used to bring additional elements that need to be taken into account for a quick real
time decision making;
 Enable to ‘free’ one of the operator’s monitor, which can be used to view other
information;
 They will be used in two different ways: permanent and occasional (special situations,
emergencies, meetings, …);
 Information displayed will be of common interest and global vision, with preference
drawings;
 Several images may be presented simultaneously.
The Airport requires the AOCC to support business and operational needs by providing real
time, redundant, secure and dependable video display systems that can be used to enhance
the security and operation processes. In addition to the ability to quickly access video and
data display information as needed by various integrated airport systems, the ability to
reconfigure display information quickly and easily at the Control Centres is of prime
importance.
Manipulation of the images displayed in the video wall will can be restricted to only the
coordinators and operators responsible at that particular schedule depending on the
configuration.
The configuration of the system will be advisable to pre-establish the different space in it
and possible information to be presented and the responsible of the centre will be the
person managing it.

15 | OTHER SYSTEMS
Video wall image distribution shall be stable, the operator needs to know what will find and
where will it be located.
Operators shall have a global overview of the system in order to monitor the current status
in real time.
Each HMI will provide the service manager and system operators with the capability to
select any video sources to any or all video wall segments.
It will be possible to integrate any control software from the different systems (AODB,
RMS,CCTV, ACS, BHS, NMS, etc.) with the control applications needed on the video wall.
Therefore, it is necessary to configure or implement the needed interfaces to transport all
the applications up to the video wall in the scope of this project.
The Application security mechanism will be based on personal or groups control access and
restricted objects. It will allow configuring an individual permission for every user or group
of every object.
The system shall have a historic record with all status changes user accesses, and errors
occurred during operation.
The video wall may be broken into a number of segments with each segment (or segments)
being capable of accepting a video source from any desk in any control room, IPTV or other
input specified in this document.
The following diagram provides an overview of the hardware and software making up the
overall video-wall system to be procured for the AOCC areas which may require it. It shall
rely on three main elements:
 Displays pool:
The video-wall is made up of a set of cubes or displays.
The expected configuration for the AOCC is a 4x4.
 Graphical controller:
Enabling the video-wall to perform as a unique visualization surface, on which any signal
or application can be displayed in anywhere and in any different size.
 Video-wall Control Software:
Handling the technical management of the video-wall as well as the visualization
management.
The displays composing the visualization area of the video wall shall comply with the following
requirements:
 To be designed for a 24x7x365 working environment;

 Enable the image visualization from any angle;
 Avoid the hot-spot effect (brightness concentration on the centre of the image).
Bright uniformity shall be higher than the 80%;
 Reduced depth and weight, making its installation and maintenance easier;
 Tiny separation between the active areas of the displays, less than 2mm;
 High resolution: Each display shall admit HD (1920x1080) resolution;
 Maximum high availability for each display: Double power supply connection,
double projection lamp, etc.;
 Each module will have at least a video digital connection (HDMI, DVI, etc.);

15 | OTHER SYSTEMS
 Each display shall have an intelligent recording of its configuration parameters such
as colour and brightness, so in case of replacement of any component (lamp, colour
wheel…) the system will be able to recover such parameters automatically;
 The Supplier shall select and provide a suitable display technology (or
technologies) for the approval of the Client;
 The displays shall support the video-teleconferencing capability;
 The displays are easy to maintains, don’t need to switch off due to the redundancies
of its components such double power source;
 In case of power failure, the displays shall be able to be configured to turn on
automatically as soon as they have power supply.
The graphical controller shall comply with the following requirements:
 All displays shall include a sensor measuring the brightness, and the graphical
controlled shall be automatically adjust it to uniform the brightness of the whole
system;
 At least sixty-four (64) composite video, S-video or video IP inputs, which may be
presented in a single display if required, without the need of using external
multiplexers. The presentation of such signals on the display shall not increase the
CPU load, or to slow down the system, as it shall use an internal video bus;
 The management software will be based on a client server architecture with
programming open interfaces and accepting local or remote global management;
 If there is a communication problem between management software and graphical
controller, the wall displays will continue working with the last configuration;
 The graphical controller/s will have redundant power supply;
The control software shall comply with the following requirements:
 It shall be accessible from any working position which may require it, being
required that all of them could add/remove presented streams or information, add
new sources, or move or update the existing ones concurrently in real time and
with no interference between the operators;
 This system shall present on the working position managing the video-wall, a
schematic view of the displays grid where it can be appreciated the presented
information and streams and the available information sources. Any update on this
information shall be updated at all positions running the control software in real-
time;
 The operator running the control software shall be able to remove or move existing
sources of information, add new ones just selecting it and choosing the place to
locate it. Such sources shall be:
o Direct video stream signals, coming from the configured video inputs;
o Applications running on the graphical controller or any other remote
application;
o Complete or partial external screens management, enabling the control of
the captured equipment (mouse, keyboard…).
 Also, this software shall allow the recording of layouts (active sources configuration,
including the elements presented, its location… etc.), and manual or automatic
(scheduled) activation of such layouts.

15 | OTHER SYSTEMS
 Finally, this software shall be an open system, programmable and configurable to

enable the operators to include any additional information source for its
presentation on the displays.
Since each operator of the AOCC will have to manage more than two workstations at the
same time, it is needed a system that shall help the operator. This system, or device, is
called a Keyboard Video Mouse switch (KVM).
The KVM system is a solution that allows a user located within AOCC control room, or sub-
spaces, to manage and monitor multiple systems installed in a remote workstation or
server.
A complete KVM infrastructure shall be installed in the control room. Each working position will
have only one keyboard and mouse, independently of the number of workstations connected
to it.
The KVM system shall allow users to access and share the desktop of a remote workstation over
the existing network.
All user applications will run in the remote workstation and will take full advantage of computing
and graphics resources of the workstation. These workstations are not properly a part of the
KVM system.
The KVM system shall support remote audio and USB, which enables a user to connect audio
and USB devices in the local console.
Each working position shall have a maximum of two (2) keyboards and two (2) mice
independently of the number of systems or workstations controlled.
The KVM system shall be compatible with VGA and DVI connectors.
The KVM switch shall handle DDC and EDID transmissions between monitor and workstation
with a pass-through technique (the KVM switch makes communication between the monitor
and the system transparent).
15.1.5.2.5 Performance Requirements
The requirements defined in this section are applicable to the entire installation and the systems
contemplated as a whole. The specific requirements of each system present in the AOCC are
defined in the corresponding section.
Response time criteria for the complete AOCC facility shall be met under maximum loading
conditions:
 The transmission delay for on-line critical business transactions (e.g. end to end flight
update) shall not exceed 1.0 second total for 95% of all transactions. The remaining 5%
of transactions shall not exceed 2.0 seconds;
 The time required for servers to complete a full fail-over switching shall not exceed one
(1) minute;
failure shall not exceed fifteen (15) minutes (e.g. after an extended system outage or
failure of both main and standby servers).

15 | OTHER SYSTEMS
15.1.5.2.6 Availability, Maintainability & Reliability
The AOCC will be used by airport staff on a 24x7 basis, the 365 days of the year.
The AOCC is a mission critical facility, it shall have a reliability of 99.99%. Any disruption to the
control and display of information will negatively impact the operation of the Airport.
Systems within the AOCC shall be high availability, resiliently designed and with no single point
of failure.
All building equipment and plant shall be supplied with two sets of Equipment Manuals.
Equipment Manuals shall as a minimum, describe equipment operation, maintenance tasks and
schedules and fault isolation.
System Manuals shall detail the environmental and electrical power system (i.e. how individual
equipment are configured to form a system and any system level maintenance requirements).
The designer shall provide the Mean Time To Repair (MTTR) for environmental and electrical
equipment.
MTTR shall assume recommended spares and competent personnel are immediately available.
15.1.6 AOCC Management System. Functional Requirements

The AOCC Management Information System(s) to be provided as part of the AOCC supply will
provide to AOCC staff summarized information about the KPIs status of the ongoing processes
taking place at the Airport.
The AOCC Management Information System will provide real-time data on processes managed
from the control centre.
Global status view from the airport, special focusing on the aircraft and passenger processes in
order to looking to their experience improvement.
Monitoring of all steps of passengers along their journey across the airport, in order to detect
bottlenecks, lack of resources or improvement possibilities on its current management while
optimizing cost and maximizing airport revenues.
Aggregated KPI information retrieving data from different systems (such as the AODB, RMS,
CUPPS, security, etc.) or devices (WiFi, Bluetooth, GPS, video, etc.) to compose a global airport
performance picture.
Intuitive dashboards to monitor airport processes status at a glance, with automatic early
detection on main performance parameters deviation (passengers forecasting, resources use
conflict early detection, etc.).
Aircraft operations (punctuality, cancelations, deviations, managed passengers, resources use,
etc.).
Airport infrastructure status (maintenance areas, unavailability, airport access roads congestion,
parking occupation level, etc.).
Airport traffic conditions (Meteorology, airport capacity, etc.).
Alarms and incidents shall be filtered and prioritized according to a user configurable rule base
and displayed on a centralized alarm ‘stack’ viewable by all AOCC staff.

The AOCC Supplier shall be responsible for providing and maintaining an IP addressing scheme

15 | OTHER SYSTEMS
15.1.8 Integration Requirement

Each working position has to be integrated with a list of systems according to the tasks to
be carried out by each operator:
 Operations area:
Working positions will require access to the following systems as a minimum:
o Resource Management System;
o Flight Information Display System;
o AODB;
o CCTV (note that prioritization over camera control shall be provided by the CCTV
system);
o Telephones, including hotline access to the ATC Tower and the Fire Department;
o Baggage Handling System.
 Airlines and ground handlers:

o Flight Information Display System;
o Airline or ground handler systems;
o CCTV;
o Telephones.
 Maintenance area:
o Building Management System;
o Maintenance Control Tool;
o Baggage Handling System;
system);
o Telephones;
o Network Management System;
o BHS SCADA;
o Maintenance Control Tool.
 Government Agencies:
system);
o Telephones;
o Agency system.

15 | OTHER SYSTEMS

AOCC supplier during the project:
AOCC-DES-1 System Detailed Design for installation Design Phase

AOCC-DES-2 Software Detailed Design (system architecture, Design Phase

AOCC-DES-3 Testing & Commissioning Plans Design Phase
AOCC-DES-4 FAT and SAT test Procedures Design Phase
AOCC -DES-5 Maintenance Plan Design Phase
AOCC-DES-6 Integration Plan and Interfaces Design Phase
AOCC-DES-7 Training Plan Design Phase
AOCC-DEL-1 Cable Management Document Delivery Phase
AOCC-DEL-2 Configuration Control Document Delivery Phase
AOCC-DEL-3 Test & Commissioning Reports Delivery Phase
AOCC-DEL-4 Integration tests Reports Delivery Phase
AOCC-DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
AOCC-DEL-6 Application user manuals Delivery Phase
AOCC-DEL-7 As Built drawings Delivery Phase

Main organizational units to be involve in AOCC use and maintenance are presented below.
02.02.XX Airport Operations User Airport Operations

Management
13.01.00 Main Airline User Main Airline

Coordinator
06.04.00 IT Support Maintenance IT Maintenance
Table 140-AOCC Airport Organizational Units Involved

15 | OTHER SYSTEMS
15.2 Security Operational Centre (SOC)
15.2.1 Introduction
The Security Operations Centre (SOC), officially known as Security Control Centre (SCC) as per
all GACA formal documentation, is designed as the only room from which the control,
surveillance and distribution of orders in relation to airport security is exercised.
It is operationally 24 hours a day, 7 days a week (24/7) and manned by specially trained operators
which need to be in permanent contact with the different security posts at the airport.
According to GACA regulations, please note that the SOC or SCC shall be interfaced with the
National Aviation Control Centre (NACC) located on the Jeddah airport and is used to centralize
information from the various KSA airports.
The NACC also regulates and controls the security level for all airports and could manage
important operations and sensitive data in live.

ICAO Doc. 8973 – Restricted ICAO The Aviation Security Manual 10th Edition 2017
EC No. 300/2008 Regulation (EC) No 300/2008 of the European Parliament and of

the council of 11 March 2008 on common rules in the field of civil
aviation security and repealing Regulation (EC) No 2320/2002
EU No. 185/2010 Commission regulation (EU) No 185/2010 of 4 March 2010 laying

down detailed measures for the implementation of the common
basic standards on aviation security
TSA - Title 49 – PART 1540 Civil aviation Security General Rules
TSA - Title 49 – PART 1542 Airport Security
TSA - Title 49 – PART 1544 Aircraft operator Security
TSA - Title 49 – PART 1546 Foreign Air Carrier Security
IATA IATA Airport Development Reference Manual (9th Edition –

January 2004)
UL Standard on Electrical Components
BS 7807:1995 Standards on design, installation and maintenance of integrated

systems
ISO TC 159(All working Ergonomic Standards

groups and
subcommittees)
ISO9001 Quality Management
BS 7671:2008 Incorporating The IET Wiring Regulations

Amendment 3:2015
BS EN/IEC 62305 Lightning Protection Standard
IEC 61340-5-1 Electrostatics: Protection of electronic devices from electrostatic

phenomena; General requirements
Table 141-SOC applicable References, Standards and Regulations

15 | OTHER SYSTEMS
Location
In order to guarantee its operation and safety of the activities, the SOC location criteria are:
 Inside a building (normally the passenger terminal);
 On restricted land side (not accessible to public);
 Next to the Airport Operations Control Centre (AOCC), which would allow sharing
general services.
It is recommended not to be installed against the exterior wall of the building.
Interior layout
The architectural and utilities infrastructure of this facility will be designed to meet planned
activities with comfort, without disruption and shutdown to perform maintenance or repair work.
The Security Control Centre shall be organized as follows:
 Lobby:
Internal distribution area, whose priority objective is that there is no direct access from
the outside to the main room (normally it is designed in a lock operation with the
external door).
 Operation room:
Main room is the nerve centre of the SCC and shall house the management and
command elements, including most of the communication equipment.
Area where the personnel directly responsible for the service are located (Terminal
Security Operator and Duty Manager), equipped with individual work consoles and a
common information panel.
 Technical room:
This room shall host all technical equipment to operate operational systems located at
the Security Control Centre.
In case of the Security Control Centre is too small to install a Technical room, the
cabinets shall be installed directly in an auxiliary technical room.
 Office / Meeting room:
The basic criterion for this space is to have room and equipment that allows access to
the databases and histories of the different systems for a subsequent analysis processes,
individually or in groups, all without having to occupy the operators' spaces.
This room shall be a separate facility immediately adjacent to the main room, but it is
recommended to have acoustic isolation, since the activities that will be carried out in
parallel, are different and are incompatible with the rest of the SOC work.
 Break room, toilets and prayer room:
Security Control Centre shall always be attended and maintain operations 24 hours a
day, for this reason, break room, toilets and prayer room for all staff shall be installed.
A kitchen capable of producing light food and refreshments, with adequate seating
accommodation, shall also be included.
In the case of a physical grouping of the SOC, AOCC and other possible centres, these
auxiliary services can be in common use.

15 | OTHER SYSTEMS
Space sizing
Based on the anticipated operational needs, the dimensioning of the spaces identified in the
SOC would be:
 Lobby, the minimum dimensions that allow the functions of distributor and lock;
 Operations room, for a minimum of three workstation, 30 square meters approx.;
 Technical room, the measures established by IT for a communications room;
 Office / Meeting room, 15 square meters approx.;
 Break room, toilets and prayer room, the usual ones for the service to be provided
considering a maximum simultaneity of three people.
Utilities infrastructure
The Security Control Centre (SCC) maintains operation of the Airport 24 hours a day, 7 days a
week (24/7). Therefore, the utility infrastructure supporting the SCC shall be designed to allow
the SCC to sustain 24/7 operations:
 All communications, IT, video, security, computer and technology related systems shall
be fed from a dual UPS system (2N);
 The entire area has to be served by air-conditioning, but only technical rooms have to
be served by a dual redundant air-conditioning;
 The entire area shall be served by fire protection system;
 The entire area shall be grounded and shall have a distributed ground grid;
 The area shall have a raised access floor;
 Consoles and workstations must be designed with ergonomic and human comfort
features.
Other security support infrastructures are:
 Apron access control;
 Auxiliary security control;
 Airport badge office;
 Screening Centre (Baggage inspection room).

15 | OTHER SYSTEMS

For an initial forecast of two operator positions and one supervisor, the distribution of basic
equipment is as shown in the following figure:
Figure 92-SOC equipment distribution architecture
Design Criteria
15.2.5.1.1 Working Positions Specification
Each working position to be installed at the SOC shall have the means required according to the
functions allocated to such position and the following requirements:
 Unification of all position in such a way that its number could be increased, reduced or
moved without major impact on the SOC configuration;
 Working position design to encourage ergonomics and modularity;
 Each working position shall be totally independent, but able to be assembled to
generate the final configuration required;

15 | OTHER SYSTEMS
 The position shall integrate a working surface which will be manufactured with latest
technology materials and dimensioned to host all the required equipment for the
operator. There will be the possibility to include an embedded box for power, voice
and data plugs at one of the sides of the working place. Also, the configuration shall
enable the emptiness and the clearness of the operator working space, facilitating to
hide all cables or obstacles on it. The length of 2.000mm and should have the possibility
to host the required equipment. At least:
o Three or four (24”-27”) monitors;

o Two workstations;
o Mouse and keyboard;
o IP telephone and radio communication devices;
o CCTV equipment. Joystick and keyboard;
o KVM user station;
o KVM display aggregator. Enabling the user to interact with up to two (2)
computers using a single mouse and keyboard simply moving the cursor
across screen borders;
o Network and power plugs and cables;
o Multiple component and composite video source inputs and outputs for the
following:
 Surveillance camera monitoring;
 Off-Air programming;
 VCR/DVD/Blu-ray sources for all common formats;
 Computer video and audio;
 IPTV;
 HDMI;
 Component Video (Y/Pb/Pr);
 S-Video;
 Optical and Coaxial Audio Output;
 Line Level Audio Output;
 IR Input;
 Composite Video;
 USB.
o Room video and audio teleconferencing;
o Program audio from IPTV;
o Voice reinforcement;
o Universal headset and microphone for each operator (integrating audio from
Workstations, IP Telephony, PA, GSR and IPTV audio);
o Video recording of AV sources;
o Audio recording of Control Centre operations in a digital format to be stored
for a minimum period of 30 days;
o Remote control capabilities via touch panel displays;
o Remote diagnostics;
o Expansion capability;
o Printing capabilities, if required.
Within the working position, in the back side, there shall be a closed area designated to
host all the computer and electronic equipment required for the operator activity. Such
equipment will be attached to removable trays which will facilitate all installation and
maintenance tasks.

15 | OTHER SYSTEMS
All working positions shall regard a double cable rising and installation paths, separating
data and electric power distribution to all equipment in the position.
The working position shall be ready to be connected to safety earth. All power supply plugs
will be located in a closed and locked place, although some extra power and data
connections may be supplied through an embedded box with flap-lids.
The chair to be used by the operator at the working position shall be an ergonomic 24x7
one, guaranteeing the right back and head position at work regarding the anatomy or any
operator.
The following picture shows a generic example of an SOC Position:
Figure 93-SOC standard working position
Working positions computers shall be remotely located at the equipment corridor reducing
noise and heat giving off and enabling a higher flexibility on functions allocation to each
working position. The following diagram details KVM architecture to be deployed at the
AOCC.
Figure 94-KVM Architecture for workstation connection to the working positions in the SOC

15 | OTHER SYSTEMS
15.2.5.1.2 Furniture Requirements
Careful design attention should be given to the desk equipment/furniture, because it

should be provided ready for use including all chairs, tables, screens, storage, mounting
brackets etc. Desk furniture shall comply with the following minimum specifications:
 Furniture:
o Provide 4 square meters per desk;
o Desks shall be of solid core materials utilizing a post and panel design. Hollow
core panel systems using cantilevered surfaces shall not be acceptable;
o Unified frame construction is required in order to prevent movement of the
monitor surface away from the remainder of the desk;
o Desks shall be modular in design for ease of reconfiguration and upgrading;
o There shall be no obstructions for side-to-side movement by the dispatcher
within desk footprint.
 Furniture Technology Requirements:
o Fixed full-width electronics cavity storage shall be provided for CPU equipment
and cable routing, keeping the knee space below the desks unobstructed;
o Cavities shall be vented to allow for passive airflow and should be designed to
accommodate additional fans if required;
o Concealed cavities for cable management and power distribution;
o Each desk shall include cable access drops;
o Desks shall be clutter free, comprising only of HMI and communications
equipment essential to the role. Processing units shall wherever possible be
located outside the AOCC.
 Desk Equipment (additional to the ones mentioned above):
o Line-level speakers (One (1) pair per workstation);
o Keyboard & Mouse;
o Power strips 6-way, twist locks under raised floor;
o 1 x Personal desk light;
o 1 x Vent/air cooling;
o Integral cable management;
o Adapters and cables as required;
o DVI-D to DVI-D single link cables;
o Cat 6A patch cables;
o DVI-D splitter Y-adapter;
o 3.5mm stereo speaker cable;
o Patch panels;
o 6 x RJ-45 CAT6a ports per desk.
 Chairs:
o Ergonomically designed chairs suitable for control centre desks.

15 | OTHER SYSTEMS
15.2.5.1.3 Videowalls Specification and components
Figure 92 provides an overview of the hardware and software making up the overall video-wall
system to be procured for the SOC areas which may require it.
The video wall display is required to be controlled a fully redundant video display processor and
management server located in the SOC and managed by the CCTV Management APP, which
shall provide the following functions:
 The Display processor shall provide a scalable solution to drive from a single display to
an effectively unlimited number of display screens.
 Source input components shall enable the capture of standard video and DVI/RGB
sources and distribute these at full frame rate and resolution to any number of displays
and operator positions for viewing.
 Network streams shall be decoded directly without additional hardware requirements
– the number of these sources that can be viewed simultaneously can easily be
expanded seamlessly – with the addition of more processing units as required for any
future requirement.
 Any networked input (computer or videos etc.) shall be capable of being distributed
over the display surface without any restriction on size and position.
 To manage the display configuration and positioning of applications and video sources
a Video-Wall Management Server will be provided to enable a simple intuitive user
interface with drag and drop capability to the wall from integration with the CCTV
Management Application.
The video-wall management software shall enable specific pre-configured video display
cameras to be programmed to provide default camera views and sizes to be presented per
operator at log-on to the CCTV Control & Monitoring workstation
SOC Video-Wall main characteristics will be:
 Such video-wall will have a minimum size of two (2) columns and two (2) rows. With
minimum expansion capacity of one column each side;
 Minimum size of each monitor will be 55’’;
 The vertical view angle for the operators respecting to the video-wall must not exceed
the 25 degrees to facilitate a comfortable view;
 Used to present context information which affect to several operators;
 Used to bring additional elements that need to be taken into account for a quick real
time decision making;
 Enable to ‘free’ one of the operator’s monitor, which can be used to view other
information;
 They will be used in two different ways: permanent and occasional (special situations,
emergencies, meetings, etc.);
 Information displayed will be of common interest and global vision, with preference
drawings;
 Several images may be presented simultaneously.
The Airport requires the SOC to support business and operational needs by providing real
time, redundant, secure and dependable video display systems that can be used to enhance
the security and operation processes. In addition to the ability to quickly access video and
data display information as needed by various integrated airport systems, the ability to

15 | OTHER SYSTEMS
reconfigure display information quickly and easily at the Control Centres is of prime
importance.
Manipulation of the images displayed in the video wall will can be restricted to only the
coordinators and operators responsible at that particular schedule depending on the
configuration.
The configuration of the system will be advisable to pre-establish the different space in it
and possible information to be presented and the responsible of the centre will be the
person managing it.
Video wall image distribution shall be stable, the operator needs to know what will find and
where will it be located.
Operators shall have a global overview of the system in order to monitor the current status
in real time.
Each HMI will provide the service manager and system operators with the capability to
select any video sources to any or all video wall segments.
It will be possible to integrate any control software from the different systems (SACS,
CCTV…etc.) with the control applications needed on the video wall. Therefore, it is
necessary to configure or implement the needed interfaces to transport all the applications
up to the video wall in the scope of this project.
The Application security mechanism will be based on personal or groups control access and
restricted objects. It will allow configuring an individual permission for every user or group
of every object.
The system shall have a historic record with all status changes user accesses, and errors
occurred during operation.
The video wall may be broken into a number of segments with each segment (or segments)
being capable of accepting a video source from any desk in any control room, IPTV or other
input specified in this document.
The following diagram provides an overview of the hardware and software making up the
overall video-wall system to be procured for the SOC areas which may require it. It shall
rely on three main elements:
 Displays pool:
The video-wall is made up of a set of cubes or displays.
The expected configuration for the SOC is a 2x2.
 Graphical controller:
Enabling the video-wall to perform as a unique visualization surface, on which any signal
or application can be displayed in anywhere and in any different size.
 Video-wall Control Software:
Handling the technical management of the video-wall as well as the visualization
management.
The displays composing the visualization area of the video wall shall comply with the following
requirements:
 To be designed for a 24x7x365 working environment;

 Enable the image visualization from any angle;

15 | OTHER SYSTEMS
 Avoid the hot-spot effect (brightness concentration on the centre of the image).
Bright uniformity shall be higher than the 80%;
 Reduced depth and weight, making its installation and maintenance easier;
 Tiny separation between the active areas of the displays, less than 2 mm;
 High resolution: Each display shall admit HD (1920x1080) resolution;
 Maximum high availability for each display: Double power supply connection,
double projection lamp, etc.;
 Each module will have at least a video digital connection (HDMI, DVI…);
 Each display shall have an intelligent recording of its configuration parameters such
as colour and brightness, so in case of replacement of any component (lamp, colour
wheel…) the system will be able to recover such parameters automatically;
 The Supplier shall select and provide a suitable display technology (or
technologies) for the approval of the Client;
 The displays shall support the video-teleconferencing capability;
 The displays are easy to maintains, don’t need to switch off due to the redundancies
of its components such double power source;
 In case of power failure the displays shall be able to be configured to turn on
automatically as soon as they have power supply.

15 | OTHER SYSTEMS
The graphical controller shall comply with the following requirements:
 All displays shall include a sensor measuring the brightness, and the graphical
controlled shall be automatically adjust it to uniform the brightness of the whole
system;
 At least 64 composite video, S-video or video IP inputs, which may be presented in
a single display if required, without the need of using external multiplexers. The
presentation of such signals on the display shall not increase the CPU load, or to
slow down the system, as it shall use an internal video bus;
 The management software will be based on a client server architecture with
programming open interfaces and accepting local or remote global management;
 If there is a communication problem between management software and graphical
controller, the wall displays will continue working with the last configuration;
 The graphical controller/s will have redundant power supply.
The control software shall comply with the following requirements:
 It shall be accessible from any working position which may require it, being
required that all of them could add/remove presented streams or information, add
new sources, or move or update the existing ones concurrently in real time and
with no interference between the operators;
 This system shall present on the working position managing the video-wall, a
schematic view of the displays grid where it can be appreciated the presented
information and streams and the available information sources. Any update on this
information shall be updated at all positions running the control software in real-
time;
 The operator running the control software shall be able to remove or move existing
sources of information, add new ones just selecting it and choosing the place to
locate it. Such sources shall be:
o Direct video stream signals, coming from the configured video inputs;
o Applications running on the graphical controller or any other remote
application;
o Complete or partial external screens management, enabling the control of
the captured equipment (mouse, keyboard,etc.).
 Also, this software shall allow the recording of layouts (active sources configuration,
including the elements presented, its location… etc.), and manual or automatic
(scheduled) activation of such layouts;
 Finally, this software shall be an open system, programmable and configurable to
enable the operators to include any additional information source for its
presentation on the displays.
Since each operator of the SOC will have to manage more than two workstations at the
same time, it is needed a system that shall help the operator. This system, or device, is
called a Keyboard Video Mouse switch (KVM).

15 | OTHER SYSTEMS
The KVM system is a solution that allows a user located within SOC control room, or sub-
spaces, to manage and monitor multiple systems installed in a remote workstation or
server.
 A complete KVM infrastructure shall be installed in the control room. Each working
position will have only one keyboard and mouse, independently of the number of
workstations connected to it;
 The KVM system shall allow users to access and share the desktop of a remote
workstation over the existing network;
 All user applications will run in the remote workstation and will take full advantage
of computing and graphics resources of the workstation. These workstations are
not properly a part of the KVM system;
 The KVM system shall support remote audio and USB, which enables a user to
connect audio and USB devices in the local console;
 Each working position shall have a maximum of two (2) keyboards and two (2) mice
independently of the number of systems or workstations controlled.
 The KVM system shall be compatible with VGA and DVI connectors.
 The KVM switch shall handle DDC and EDID transmissions between monitor and
workstation with a pass-through technique (the KVM switch makes communication
between the monitor and the system transparent).
15.2.5.1.4 Performance Requirements
The requirements defined in this section are applicable to the entire installation and the systems
contemplated as a whole. The specific requirements of each system present in the SOC are
defined in the corresponding section.
Response time criteria for the complete SOC facility shall be met under maximum loading
conditions:
 The transmission delay for on-line critical business transactions (e.g. end to end
flight update) shall not exceed 1.0 second total for 95% of all transactions. The
remaining 5% of transactions shall not exceed 2.0 seconds;
 The time required for servers to complete a full fail-over switching shall not exceed
one (1) minute;
failure shall not exceed fifteen (15) minutes (e.g. after an extended system outage
or failure of both main and standby servers).
15.2.5.1.5 Availability, Maintainability & Reliability
The SOC will be used by airport staff on a 24x7 basis, the 365 days of the year.
The SOC is a mission critical facility, it shall have a reliability of 99.99%. Any disruption to the
control and display of information will negatively impact the operation of the airport.
Systems within the SOC shall be high availability, resiliently designed and with no single point
of failure.
All building equipment and plant shall be supplied with two sets of Equipment Manuals.
Equipment Manuals shall as a minimum, describe equipment operation, maintenance tasks and
schedules and fault isolation.

15 | OTHER SYSTEMS
System Manuals shall detail the environmental and electrical power system (i.e. how individual
equipment are configured to form a system and any system level maintenance requirements).
The designer shall provide the Mean Time to Repair (MTTR) for environmental and electrical
equipment.
MTTR shall assume recommended spares and competent personnel are immediately available.

The SOC Supplier shall be responsible for providing and maintaining an IP addressing scheme
15.2.7 Integration Requirement

Each working position has to be integrated with a list of systems according to the tasks to
be carried out by each operator:
 SACS;
 CCTV;
 IDMS;
 Telephones, including hotline access to the ATC Tower and the Fire Department;
 CCTV Baggage Handling System;
 CCTV Parking;
 GSR.

15 | OTHER SYSTEMS

SOC-DES-1 System Detailed Design for installation Design Phase

cabling, fixation, etc.)
SOC -DES-2 Software Detailed Design (system architecture, Design Phase

SOC -DES-3 Testing & Commissioning Plans Design Phase
SOC -DES-4 FAT and SAT test Procedures Design Phase
SOC -DES-5 Maintenance Plan Design Phase
SOC -DES-6 Integration Plan and Interfaces Design Phase
SOC -DES-7 Training Plan Design Phase
SOC -DEL-1 Cable Management Document Delivery Phase
SOC -DEL-2 Configuration Control Document Delivery Phase
SOC -DEL-3 Test & Commissioning Reports Delivery Phase
SOC -DEL-4 Integration tests Reports Delivery Phase
SOC -DEL-5 ORAT Assistance & Follow-up Reports Delivery Phase
SOC -DEL-6 Application user manuals Delivery Phase
SOC -DEL-7 As Built drawings Delivery Phase

09.05.00 Airport Security User Airport Security

Management
06.04.00 IT Support Maintenance IT Maintenance
Table 143-SOC Airport Organizational Units Involved


Attachment 4b - Data Center Report

Uploaded by

Copyright:

Available Formats

Attachment 4b - Data Center Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Attachment 4b - Data Center Report

Uploaded by

Copyright:

Available Formats

AMAALA AIRPORT WORK PACKAGE 2

SCHEMATIC DESIGN REPORT (50 %)

AMAALA AIRPORT WORK PACKAGE 2 199/516

10.1.2 Applicable Codes, Standards and Regulations

ANSI/TIA/EIA-568-B Commercial Building Telecommunications Cabling Standard

ANSI/TIA/EIA-569-A Commercial Building Standard for Telecommunications

ANSI/TIA/EIA-569-B Commercial Building Standard for Telecommunications

ANSI/TIA/EIA-606-A Administration Standard for the Telecommunications

ANSI/TIA/EIA-607-A Commercial Building Grounding and Bonding Requirements

ANSI/TIA 942 Telecommunications Infrastructure for Data Centres

BICSI – TDMM Telecommunications Distribution Methods Manual

BICSI - COOPDM Customer-Owned Outside Plant Design Manual

BICSI - ITSIM Information Transport Systems Installation Manual

BICSI - NDRM Network Design Reference Manual

BICSI - WDRM Wireless Design Reference Manual

IEC 603-7 Current capacity for connectors

IEEE 802.1 LAN/MAN Bridging and Management

IEEE 802.3 CSMA/CD Access Methods (Ethernet)

IEEE 802.3ae 10 Gigabit specification

IEEE 802.3z 1000 Base-S specification

IEEE 802.3ab 1000 Base-T specification

IEEE 802.3af/at Power over Ethernet

IEEE 802.3u 100 Base-T specification

IEEE 802.1Q VLAN

IEEE 802.1P Prioritization

IEEE 802.11 a/b/g/n CSMA/CA Access Methods (Wireless LAN)

Class D, E, EA, F, FA ISO/IEC Information Technology – Generic Cabling for Customer

TIA/EIA 606-A Administrative Standard for Commercial Telecommunications

IATA International Air Transport Organization

ICAO International Civil Aviation Organization

NIC National Information Centre

Table 55-LAN/WAN applicable References, Standards and Regulations

AMAALA AIRPORT WORK PACKAGE 2 200/516

10.1.3 System Description and Concept of Operation

10.1.4 System Architecture

Figure 57-LAN/WAN architecture

AMAALA AIRPORT WORK PACKAGE 2 201/516

26. Vip 42.Electrical 40.Power 30.Northern

26. Vip 33.Sec

27. Airside 23. Mirage

30.Northern 29. Parking

39.Water 35.Admin 46.Staff 29.Parking

Figure 58-FO Ring Distribution

10.1.5 General System Requirements

AMAALA AIRPORT WORK PACKAGE 2 202/516

Code/standard identification Title

30 Northern Access Gate

Table 56-LAN/WAN areas to be connected

Quality of service, congestion management and multicast control shall be implemented to

AMAALA AIRPORT WORK PACKAGE 2 203/516

10.1.5.1.1 Security of Information System (SSI)

AMAALA AIRPORT WORK PACKAGE 2 204/516

○ HORIZONTAL LAN CABLING:

○ VERTICAL LAN AND WAN CABLING:

AMAALA AIRPORT WORK PACKAGE 2 205/516

10.1.5.2.3 Core Switches

○ Minimum performance data:

AMAALA AIRPORT WORK PACKAGE 2 206/516

10.1.5.2.4 Aggregation/Distribution Switches