Confidential

Passenger Self-Service Programme

Annexure A – Scope of Work

for

the supply, installation, commission, support, and maintenance of

COMMON USE PASSENGER PROCESSING SYSTEMS (CUPPS),

COMMON USE SELF SERVICE(CUSS) KIOSKS

Scope of work document

Page 1

Confidential
 Confidential

Glossary and Abbreviations

Item Description

2DBC 2-Dimensional Barcode System

ABC Automated Border Control
ACSA Airports Company South Africa
Adapter Server Facilitates sending and receiving of messages from the AMS database and/or e-
Gate to DHA via the ESB
AEA Association of European Airlines
OM Operations Management
AMS Database Contains flight information and aircraft resource allocation
API Application Programming Interface
AVSEC ACSA Aviation Security
AODB Airport Operations Database System
AISI Aerospace Industry Support Initiative
Biometrics Any means by which a person can be uniquely identified by evaluating one or more
distinguishing biological traits. Unique identifiers include fingerprints, facial features,
hand geometry, earlobe geometry, retina and iris patterns, voice waves, DNA, and
signatures
BeMCS Biometric Enhanced Movement Control System – an upgraded version of EMCS
(Enhanced Movement Control System) with full biometric integration. System used
to capture movement records for travellers as they go through Immigration
BMP Bitmap
CMC Crew Member Certificate
CUPPS Common Use Passenger Processing Systems
CUTE Common User Terminal Equipment
CUSS Common Use Self Service
CTIA Cape Town International Airport
DHA Department of Home Affairs
DHA Systems DHA critical systems for this Automated Border Control Project include Biometric
Enhanced Movement Control System which will be fully integrated to the HANIS
System. Another critical system is the Online Biometric Verification system
KSIA King Shaka International Airport

Scope of work document

Page 2

Confidential
 Confidential

EAM Enterprise Asset Management

EIA Environmental Impact Assessment
E-Passport Electronic/ Biometric Passport
FAR False Accept Rate
FIDS Flight Information Display System
FRR False Reject Rate
HANIS Home Affairs National Identification System
ORTIA Oliver Tambo International Airport
JPEG Joint Photographic Experts Group
LED Light Emitting Diode
MRZ Machine Readable Zone
IAM Infrastructure Assets Management
IATA International Air Transport Association
ICAO International Civil Aviation Organization
IEC International Electrotechnical Commission
ISO International Organisation for Standardisation
OHS Occupational Health & Safety
OBL Outside Battery Limits
PNG Portable Network Graphic
REST Representational State Transfer
SACAA South African Civil Aviation Authority
SA South Africa
SAN Storage Area Network
SAPS South African Police Services
SDK Software Development Kit
SOA Service Oriented Architecture
SOAP Simple Object Access Protocol
SOW Scope of Work
UPS Uninterruptible Power Supply.
USB Universal Serial Bus

Scope of work document

Page 3

Confidential
 Confidential

TABLE OF CONTENTS

2 INTRODUCTION................................................................................................................................................... 6
2.1 PURPOSE ............................................................................................................................................................. 6
2.2 OBJECTIVE ........................................................................................................................................................... 6
2.3 APPLICABLE LAWS, CODES, RULES, REGULATIONS AND STANDARDS ................................................................. 9
2.4 SIZE OF WORKS (BILL OF QUANTITIES) ....................................................................................................................... 12
2.4.1 CUSS: BILL OF QUANTITIES ........................................................................................................................ 12
2.4.2 CUPPS: BILL OF QUANTITIES ..................................................................................................................... 13
2.5 CURRENT CHALLENGES RELATING TO CUPPS & CUSS ....................................................................................... 17
3 SCOPE ................................................................................................................................................................18
3.1 IN SCOPE (CUPPS & CUSS) ................................................................................................................................. 18
3.2 OUT OF SCOPE ................................................................................................................................................... 70

Scope of work document

Page 4

Confidential
 Confidential

Tables

Table 1: Airlines DCS………………………………………………………………………………………….………7

Table 2: Bill of Quantities…………………………………………………………………………………………….13

Table 3: CUPPS & CUSS Related Challenges……………………………………………………………………18

Table 4: Supply and Installation of CUPPS……………………………………………………………….……….19

Table 5: CUPPS Accessories & Peripherals Specs………………………………………………………………27

Table 6: Interfacing between CUPPS & Other systems………………………………………………………….28

Table 7: Technical Specification (CUSS Kiosk) ………………………………………………………….……….29

Table 8: WAN Spec………………………………………………………………………………………….……….65

Table 9: IT Infrastructure Requirements……………………………………………………………………………68

Table 10: Testing and Training………………………………………………………………………………………69

Table 11: Implementation…………………………………………………………………………………………….70

Table 12: Enabling Works……………………………………………………………………………………………72

Scope of work document

Page 5

Confidential
 Confidential

2 INTRODUCTION

2.1 PURPOSE

Airports Company South Africa SOC Ltd (ACSA) hereby invites proposals for the supply, installation,
commissioning, support, and maintenance of Common Use Passenger Processing System (CUPPS) and
Common Use Self Service (CUSS) kiosks at its various airports.

CUPPS Replacement is required at the following airports: Oliver Tambo International (ORTIA), Cape Town
International (CTIA), King Shaka International (KSIA), East London (ELS), Port Elizabeth International (PLZ),
George (GRJ), Kimberley (KIM), Bram Fischer (BFN) and Upington (UTN).

CUSS Kiosk Replacement is required at the following airports: Oliver Tambo International (ORTIA), Cape
Town International (CTIA), King Shaka International (KSIA), East London (ELS), Port Elizabeth International
(PLZ), George (GRJ), Kimberley (KIM), Bram Fischer (BFN) and Upington (UTN).

Support and Maintenance requirements form part of the overall Passenger Self Service tender and response
thereto and pricing thereof to be included as part of Service Provider’s response to this tender.

2.2 OBJECTIVE

The purpose of this Scope of Work (SOW) document is to define the high-level technical and functional
requirements related to the supply, installation, commissioning, support, and maintenance of the CUPPS,
CUSS (inclusive but not limited to equipment, software, hardware, networks) for ACSA airports.

Scope of work document

Page 6

Confidential
 Confidential

The following airlines are currently utilising ACSA airport facilities and will/may be utilising the new CUPPS
and CUSS system, dependent on their DCS being certified on the CUPPS platform:

Airline Code DSC

Airlink 4Z Amadeus
Bidair 41 Amadeus
Cemar 5Z Videcom
Air France AF Amadeus
Italia AZ Sabre
Air France AF Vega
British Airways BA British Airways
British Airways BA Amadeus
Air Botswana BP A-ICE
Air China CX Embark
Air China CX Travel Sky
Air China CX CA
Cathay Pacific CX Amadeus
Delta DL Delta
Air Angola DT Amadeus
Ethiopian Airlines ET Sabre
Etihad EY Sabre
FlySafair FA INK
FastJet FN INK
Lift GE INK
Air Seychelles HM HITIT
KLM Royal Dutch KL Amadeus
KLM Royal Dutch KL Vega
Asky KP Sabre
Kenya Airways KQ Amadeus
Latam LAT Sabre
Latam JJ Amadeus
Lufthansa LHG cFront
EL AL Israel Airlines LY Amadeus
EL AL Israel Airlines LY Amadeus
EL AL Israel Airlines LY Amadeus
Air Madagascar MD Amadeus
Air Mauritius MK Amadeus
Qantas Airways MS Amadeus
Proflight P0 Videcom

Scope of work document

Page 7

Confidential
 Confidential

Air Peace P4 Videcom

Maldivian Air Q2 Amadeus
Qatar QR Amadeus
South African Airlines SA Amadeus
Singapore Airlines SQ Amadeus
Saudi Arabian SV Amadeus
Air Tanzania TC HITIT
Turkish Airlines TK Turkish Airlines INC
LAM TM Amadeus
United Airlines UA UA-Suite
RwandAir WB Amadeus
Bidair BR Horizon
Virgin Atlantic VS VSS
Air Austral UU Amadeus
Uganda Air UR HITIT
Menzies MZ INC
Zambia Air ZN Sabre
Table 1: Airlines DCS

NB. Please note that this is not an exhausted list of airlines, and a full list will be shared during kick-off
sessions.

Scope of work document

Page 8

Confidential
 Confidential

2.3 APPLICABLE LAWS, CODES, RULES, REGULATIONS AND STANDARDS

a. The development and installation work shall comply with the System Requirements
Specification, referenced rules, regulations, codes, standards, as well as industry best
practices for each system in a “greenfield” airport the capacity and size planned for
INA.

b. The following are Codes and Standards shall be referenced:

Standard / Code Purpose / Function

1. ISO 9000 Quality Assurance
2. IEC 62381 Automation Systems Testing
3. IEC 60529 Degree of enclosure protection (IP Code)
4. ISO 29119 Software Testing
5. BS 7925‐1 & 2 Software Testing Terms
6. IEEE 829 Software Test Documentation
7. IEEE 1028 Software Review Procedures
8. IEEE 1044 Classification of Software Anomalies
9. ISO 9002 Quality Control Plan and Requirements
10. AEA Association of European Airlines
i. ATB Technical Specifications –
Amended Aug 2020, 2008, 2009
and later.
ii. Parametric Baggage Tag Data
Concept – Aug 2002, 2008, 2009
and later
iii. Self Service Specifications Aug
2001 and later
11. IATA International Air Transport Association
i. CUSS Technical Specifications 1.3
Jun 2013
ii. IATA RP 1797: Common Use
Terminal Equipment (CUPPS)
Systems
iii. IATA RP 1745: Baggage Service

Scope of work document

Page 9

Confidential
 Confidential

Messages
iv. IATA 1722c, 722c, 722d, 722e:
ATB related resolutions
v. IATA RP 740, 740a: BTP related
resolutions
vi. IATA RP 1706c, 1706d, 1706e:
Common Use Self‐Service
vii. Airport Handling Manual (16th
Edition)
viii. Airport Development Reference
Manual (9th Edition)
12. ICAO International Civil Aviation Organization
i. Annex 14
ii. ICAO: Annex 10 to the Convention
on International Civil Aviation. ‐
"Aeronautical Telecommunication"
‐ Volume II ‐ 4.4.2 (IA2), 4.4.15
(IA5)
iii. Annex 17th – 7th Edition April
2002 Including Amendments,
Security Safeguarding
International Civil Aviation Against
Acts of Unlawful Interference
13. EIA i. EIA‐310‐D (1992): Cabinets,
Racks, Panels, and Associated
Equipment
ii. TIA/EIA‐568‐B: Commercial Building
Telecommunications Cabling Standard
14. ITIL v3 i. IT Service Management

Scope of work document

Page 10

Confidential
 Confidential

Scope of work document

Page 11

Confidential
 Confidential

2.4 Size of Works (Bill of Quantities)

At a high-level, the project aims to procure the supply, installation, commissioning, configuration, support,
and maintenance of the following Bill of Quantities (BOQ) in line with the 5-yearly replacement cycle that
ACSA follows with regards to its CUPPS and CUSS solutions. The implementation will follow a phased
approach whereby the phase 1 of the project will be the roll out of the CUSS equipment (103) and the Phase
2 will be the roll out of the CUPPS (5970) equipment.

Below is the Phase 1 scope:

2.4.1 CUSS: BILL OF QUANTITIES

Site Number of CUSS Kiosks

CTIA 20
ORTIA 43
KSIA 18
KIM 2
BFN 3
GRJ 5
ELS 4
PLZ 6
UTN 2
TOTAL 103

Scope of work document

Page 12

Confidential
 Confidential

Below is the Phase 2 scope:

2.4.2 CUPPS: BILL OF QUANTITIES

Transfer Boarding Lost and Training Baggage Spares Total
ORTIA Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including
keyboard and mouse 276 34 142 31 8 6 497 50 547

Wireless cards baggage area 0 0 0 0 0 0 0 0 7

VDU including cables 276 34 142 31 8 6 497 50 547
Screen Arm Bracket 90
Boarding Pass Printer 276 34 71 31 7 6 425 42 467
Magnetic stripe reader&
Optical Character Read 276 34 142 - 8 - 460 46 506
Bag Tag Printer 276 0 71 0 6 0 353 35 388
Boarding Gate Reader 142 2 144 14 158
Barcode Reader 276 34 0 0 6 0 316 32 348
General Purpose Printer 71 1 6 78 7 85
TOTAL 1656 170 781 93 46 24 2770 276 3143

Transfer Boarding Lost and Training Baggage Spares Total

CTIA Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including
keyboard and mouse 120 4 56 8 8 0 196 20 216
VDU including cables 276 4 56 8 8 0 196 20 216
Screen Arm Bracket 8
Boarding Pass Printer 120 4 28 8 7 0 167 17 184
Magnetic stripe reader& Optical
Character Read 120 4 56 0 8 0 188 19 207
Bag Tag Printer 120 0 28 0 6 0 154 15 169
Boarding Gate Reader 56 2 58 6 64
Barcode Reader 120 4 0 0 6 0 130 13 143
General Purpose Printer 28 1 0 29 3 32
TOTAL 876 20 308 24 46 0 1118 113 1239

Scope of work document

Page 13

Confidential
 Confidential

Transfer Boarding Lost and Training Baggage Spares Total

KSIA Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including keyboard
and mouse 72 4 44 4 6 5 135 14 149
Wireless cards baggage area 6
VDU including cables 72 4 44 4 6 5 135 14 149
Screen Arm Bracket
Boarding Pass Printer 72 4 22 4 5 5 112 11 123
Magnetic stripe reader& Optical
Character Read 72 4 44 0 6 0 126 13 139
Bag Tag Printer 72 0 22 0 5 0 99 10 109
Boarding Gate Reader 44 2 46 5 51
Barcode Reader 72 4 0 0 4 0 80 8 88
General Purpose Printer 22 1 5 28 2 30
TOTAL 432 20 242 12 35 20 761 77 844

Transfer Boarding Lost and Baggage Spares Total

Port Elizabeth Check-in Training Room Sub-total
counter Gates Found Make-up 10% Quantity
Cute Workstation including
keyboard and mouse
21 12 33 3 36
Wireless cards baggage
area - - - - - 0 - 0
VDU including cables 21 12 33 3 36
Screen Arm Bracket 0 3 3
Boarding Pass Printer 21 0 6 27 3 30
Magnetic stripe reader&
Optical Character Read 21 12 33 3 36
Bag Tag Printer 21 6 27 3 30
Boarding Gate Reader 12 12 1 13
Barcode Reader 21 21 2 23
General Purpose Printer 6 6 1 7
Total 126 0 66 0 0 0 192 22 214

Transfer Boarding Lost and Training Baggage Spares Total

East London Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including
keyboard and mouse
15 8 23 2 25
Wireless cards baggage
area - - - - - - 0 - 0
VDU including cables 15 8 23 2 25
Screen Arm Bracket 0 0
Boarding Pass Printer 15 0 4 19 2 21
Magnetic stripe reader&
Optical Character Read 15 8 23 2 25
Bag Tag Printer 15 4 19 2 21
Boarding Gate Reader 8 8 1 9
Barcode Reader 15 15 2 17
General Purpose Printer 4 4 0 4
Total 90 0 44 0 0 0 134 13 147

Scope of work document

Page 14

Confidential
 Confidential

Transfer Boarding Lost and Training Baggage Spares Total

George Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including
keyboard and mouse
12 12 24 2 26
Wireless cards baggage
area - - - - - - 0 - 0
VDU including cables 12 12 24 2 26
Screen Arm Bracket 0 0
Boarding Pass Printer 12 0 6 18 2 20
Magnetic stripe reader&
Optical Character Read 12 12 24 2 26
Bag Tag Printer 12 6 18 2 20
Boarding Gate Reader 12 12 1 13
Barcode Reader 12 12 1 13
General Purpose Printer 6 6 1 7
Total 72 0 66 0 0 0 138 13 151

Transfer Boarding Lost and Training Baggage Spares Total

Upington Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation
including keyboard and
mouse 8 6 14 1 15
Wireless cards baggage
area - - - - - - 0 - 0
VDU including cables 8 6 14 1 15
Screen Arm Bracket 0 0
Boarding Pass Printer 8 0 3 11 1 12
Magnetic stripe reader&
Optical Character Read 8 6 14 1 15
Bag Tag Printer 8 3 11 1 12
Boarding Gate Reader 6 6 1 7
Barcode Reader 8 8 1 9
General Purpose Printer 3 3 0 3
Total 48 0 33 0 0 0 81 7 88

Scope of work document

Page 15

Confidential
 Confidential

Transfer Boarding Lost and Training Baggage Spares Total

Bram Fisher Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity

Cute Workstation including

keyboard and mouse 8 6 14 1 15
Wireless cards baggage
area - - - - - - 0 - 0
VDU including cables 8 6 14 1 15
Screen Arm Bracket 0 0
Boarding Pass Printer 8 0 3 11 1 12
Magnetic stripe reader&
Optical Character Read 8 6 14 1 15
Bag Tag Printer 8 3 11 1 12
Boarding Gate Reader 6 6 1 7
Barcode Reader 8 8 1 9
General Purpose Printer 3 3 0 3
Total 48 0 33 0 0 0 81 7 88

Transfer Boarding Lost and Training Baggage Spares Total

Kimberly Check-in Sub-total
counter Gates Found Room Make-up 10% Quantity
Cute Workstation including
keyboard and mouse
5 4 9 1 10
Wireless cards baggage
area - - - - - - 0 - 0
VDU including cables 5 4 9 1 10
Screen Arm Bracket 0 0
Boarding Pass Printer 5 0 2 7 1 8
Magnetic stripe reader&
Optical Character Read 5 4 9 1 10
Bag Tag Printer 5 2 7 1 8
Boarding Gate Reader 2 2 0 2
Barcode Reader 5 5 1 6
General Purpose Printer 2 2 0 2
Total 30 0 20 0 0 0 50 6 56
Table 2: Bill of Quantities

Scope of work document

Page 16

Confidential
 Confidential

2.5 CURRENT CHALLENGES RELATING TO CUPPS & CUSS

ACSA has a 5-yearly replacement cycle pertaining to its CUPPS and CUSS solutions. The current CUPPS &
CUSS solution (including equipment, hardware, and software) is becoming outdated with installed equipment
becoming out-of-warranty with increased breakages plus support and maintenance on an upward trend.
ACSA aims to ensure that passengers are afforded the world-class services they have come to expect from
various ACSA airports while at the same time addressing following challenges.

# Challenge Description

1.3.1 Long Queues & Passenger Without up-to-date and functional CUPPS & CUSS solutions, long
Throughput queues can be experienced when processing passengers through
airports negatively affecting passenger processing times,
passenger experience & satisfaction
1.3.2 Asset Optimisation Expanding building infrastructure to provide additional capacity to
passengers and airlines is not always feasible from a spatial and
financial constraints point of view. CUPPS & CUSS solutions
allow ACSA to optimally use the existing building infrastructure
and delay capital investments through offering common-use
solutions that can be shared by airlines and passengers to
process
Table 3: CUPPS & CUSS Related Challenges

Scope of work document

Page 17

Confidential
 Confidential

3 SCOPE

By responding to this tender, the bidders agree to deliver everything listed below under sections 2, 3, and 4.

3.1 IN SCOPE (CUPPS & CUSS)

The following requirements for the CUPPS Solution are applicable:

BR1 SUPPLY AND INSTALLATION OF CUPPS SOLUTION

BR1.1 BR1.1 The Bidder shall provide, based on specifications as contained in this document, all
equipment, material, labour, and services required to construct and install the CUPPS
including, but not limited to:

BR1.1.1 All configuration and deployment services, equipment & solution drawings,
specifications, equipment, materials, and labour, not specifically mentioned or shown,
which may be necessary to complete the design and installation of the CUPPS.
BR1.1.2 Hardware including servers, computer workstations, peripherals and rack
accessories as specified for the system and any hardware that is specific to the
Service Provider’s system.
BR1.1.3 Software applications – other than the users’ own applications that may be
required to make the system fully operational as specified including the provision of
Databases, interfaces, population of database tables and any other required
configuration.
BR1.1.4 All current airline certified software and applications to be installed on the
new hardware for airlines operating from the defined airports (e.g., BA’s FLY
application)
BR1.1.5 The latest certified version of Airline Check-in and gate Terminal Emulation
software shall be loaded for every airline operating from the defined airports.
BR1.1.6 Installation and setup of the system hardware and software in accordance
with pre-agreed installation standards
BR1.1.7 Final connection of hardware to power (Bidder to provide all power cords for
PCs and peripherals), infrastructure termination and fly leads (provided by others)
connecting system equipment to the data outlets and/or LAN equipment (provided by
others).
BR1.1.8 As-built documentation and technical data for all CUPPS hardware and

Scope of work document

Page 18

Confidential
 Confidential

software components.
BR1.1.9 Delivery of the required interfaces including full documentation.
BR1.1.10 System configuration and integration with interfaced Systems.
BR1.1.11 Complete testing of the System
BR1.1.12 Test plans, system testing and commissioning.
BR1.1.13 Training: User training including providing training manuals (Train the
trainer at every site)
BR1.1.14 Maintenance and Support in accordance with the service levels as specified
in this document.
BR1.1.15 Full Coordination of the works, including decommissioning of existing
CUPPS equipment as installed by current Service Provider, removal of old CUPPS
equipment, storing old equipment in ACSA designated storerooms and installation of
CUPPS equipment.
BR1.1.16 Close monitoring, tracking and record-keeping for old and new CUPPS
equipment is required to ensure no equipment is negligently lost on the part of the
Service Provider.
BR1.1.17 Project management of Service Provider’s scope.
BR1.1.18 Co-ordination with ACSA project manager as required for implementation of
works to completion.

BR1.2 CUPPS System Requirements

BR1.2.1 The CUPPS System shall operate 24 hours per day, 7 days per week, throughout the
year.
BR1.2.2 CUPPS is considered a critical operational system and care with the design
parameters needs to be taken.
BR1.2.3 Device Availability: A device shall be considered available only if all components are
operating and fully functional. Besides scheduled downtime, individual device availability shall
be at least 99.99 %
BR1.2.4 All received messages from, but not limited to, airline host systems and CUPPS
management workstations, shall be processed in less than 300 milliseconds.
BR1.2.5 Based on common practice it is expected that host transactions will be processed in
less than 2 seconds, but at least not more than 4 seconds.
BR1.2.6 The System shall be capable to run multiple terminals as well as airports.
BR1.2.7 The Bidder shall deliver a benchmark document describing:

Scope of work document

Page 19

Confidential
 Confidential

i. The CUPPS System load on a regular basis.

ii. The CUPPS System load on peak hour processing.
iii. Any other information that seems relevant to the Service Provider.
BR1.2.8 Monthly availability reports are produced as per the Performance Level Service
Schedule.
BR1.2.9: The System has to manage at least the following:

iv. Remote control on equipment to analyse, test and maintain.

v. Remote configuration.
vi. Server and software status.
vii. Software distribution.
BR1.2.10 The System shall be scalable and expandable to accommodate future increase of
number of workstations in any of the deployed Airports.
BR1.2.11 The workstations in the ACSA Airports shall be connected to the CUPPS VLAN
either wired through 1 x Gigabit or 10/100/1000 MBit TX NIC or wireless through RF wireless
network (802.11b/g/n) only in baggage make-up areas.
BR1.2.12 The CUPPS Application servers shall be located in the ACSA Core rooms and shall
provide the capability for remote monitoring.
BR1.2.13 For redundancy, each of the CUPPS servers shall be installed in separate Core
rooms. CUPPS is provided at the 3 large (hub) airports and 5 satellite airports, and airlines
using these connections, need not supply additional connectivity. It is required that each
airline shall use the IP circuits provided by the Service Provider.
BR1.2.14 The System and applications software are controlled and configured by working
parameters stored in tables and easy to change without programming actions.
BR1.2.15 User interaction with the System shall incur no noticeable delay in line with airline
application specifications.
BR1.2.16 The System shall be able to accept a wide range of CUPPS compliant input and
output peripherals.
BR1.2.17 The System shall provide multiple levels of password-protected security.
BR1.2.18 The Passenger Processing Systems (CUPPS and CUSS) at ACSA airports shall
operate as an integrated platform performing all required processes. Any of the Passenger
Processing Systems shall exactly perform in a common-use environment.
BR1.2.19 The Passenger processing processes at ACSA airports may require capturing,
scanning, and storing Passenger Travel Documents information. Such process shall use the

Scope of work document

Page 20

Confidential
 Confidential

peripherals provided by the passenger processing systems at the Check-in and gate areas.
BR1.2.20 The CUPPS workstations shall be integrated with scales at the check-in counters
where the airline users can weigh, tag, and drop checked-in luggage.
BR1.2.21 The Bidder shall install all core equipment required for the CUPPS system in order
to be fully operational.
BR1.2.22 The Bidder shall do quarterly redundancy and disaster recovery tests and provide
reports with the results to ACSA. Immediate actions shall be taken to resolve failures.
BR1.2.23 The platform software consists of all the software required to enable CUPPS
functionality, including all operating systems, databases, data exchange software where
required, except those supplied by the application providers (airlines).

BR1.3 CUPPS SYSTEM & CUPPS WORKSTATION SPECS

BR1.3.1 CUPPS workstations shall be connected via the CUPPS communication
infrastructure to the core computer room (provided by ACSA, Bidder to manage). The Bidder
shall provide the routers/gateways required for airline host connectivity.
BR1.3.2 Each workstation shall have various common use hardware connected depending on
the location.
BR1.3.3 Peripherals shall support 2D PDF417 and 1D bar codes per IATA Recommended
Practices. Support of magnetic swipes is required via specified peripheral device.
BR1.3.4 Workstations shall be mutually independent of each other (e.g., two CUPPS
workstations at the same gate counter can access two different hosts simultaneously).
BR1.3.5 From any CUPPS workstation any authorized user shall be able to access non-airline
applications such as the Flight Information Display System interface without rebooting or
otherwise disabling airline interface.
BR1.3.6 Workstations shall be able to spool output to a peripheral device that is physically
connected to another workstation.
BR1.3.7 The airlines identified shall be serviced by the Service Provider’s CUPPS system. It
is the Service Provider’s responsibility to verify/determine airline host and to determine host
requirements.
BR1.3.8 The Service Provider’s CUPPS solution shall store use data, peripheral data, login /
logout times and duration, and other statistical data.
BR1.3.9 The CUPPS System shall be capable of accessing ACSA’s AMS system via their
View direct software (current version AMS 5.16.904.1) to facilitate FIDS transactions from all
counters and/or all gates.

Scope of work document

Page 21

Confidential
 Confidential

BR1.3.10 The CUPPS System shall allow access from any gate to the ACSA Central Search
point Security verification system.
BR1.3.11 The CUPPS System shall allow access from any CUPPS workstation to the
Baggage Reconciliation Systems.
BR1.3.12 The CUPPS PC shall be installed with all the required scale data exchange
software and interface cables ready for accepting data through an interface from the counter
scale to update weight into the DCS.
BR1.3.13 The System shall be of the latest proven technology and widely used in many
international airports by many international airlines.
BR1.3.14 The Bidder shall recommend and provide the hardware and server configuration
that best serves the overall design solution. All hardware shall be from a reputable
manufacturer capable of a high level of maintenance and service.
BR1.3.15 All equipment shall be new and commercially of the Shelf products (COTS).
Hardware specifications detailed in this document are the minimum requirements. The Bidder
is required to supply the latest available hardware at the time of delivery.
BR1.3.16 The System design must permit a server to be taken off-line and replaced without
any disruption to CUPPS operations.
BR1.3.17 The Bidder shall provide all termination components in the cabinets including patch
cords for a fully operational system unless noted otherwise.
BR1.3.18 There shall be no single point of failure in the System.
BR1.3.19 Remote locking of unassigned counter: Software compatibility to remotely lock
counters that are not assigned to airlines for a specific period.
BR1.3.20 The CUPPS Workstation and peripherals shall be IATA CUPPS compliant and be
certified for use by supported airlines at ACSA AIRPORTS. Peripherals shall comply with
IATA recommended practices and initiatives (e.g., Simplifying the Business – StB).
BR1.3.21 The workstation shall be of the latest certified make and model available from the
CUPPS Service Provider.

BR1.3.22 The workstation should be selected so to perform efficiently for the 5-year
maintenance period, should be selected so to accommodate all the peripheral connections
envisaged at every position. Special care should be taken where scale interfaces must be
connected to workstations.

BR1.3.23 The required VDU must be maximum of 17” to be accommodated in the current
desks. All screens to be supplied with swing arm mounting bracket (VESA compatible)

Scope of work document

Page 22

Confidential
 Confidential

mounted to desk.

BR1.4 REPORTING REQUIREMENTS (STATISTICS)

The System shall store and manage at least the following:

BR1.4.1 Up-Time of equipment, including but not limited to:

(a) Per CUPPS workstation.
(b) Per airline user signing on to use the workstation
(c) Per Airline DCS / host system.
(d) Per airport
(e) Additional statistics available to the contracted party.
BR1.4.2 Number of boarding cards printed.
BR1.4.3 Number of baggage tags printed.
BR1.4.4 Number of transactions processed through other peripherals, by peripheral.
BR1.4.5 The System shall be able to provide statistical information on a daily and weekly
basis in a text file format categorised per check-in mode/type (Desk, CUSS, Online). Provide
the breakdown of the Check-in Mode.
Table 4: Supply and Installation of CUPPS

Scope of work document

Page 23

Confidential
 Confidential

BR2 CUPPS ACCESSORIES & PERIPHERALS SPECIFICATIONS

BR2.1 BR2.1.1 The Boarding Pass Printer (BPP) shall meet the following minimum requirements:

(a) A receipt style printer shall be provided that is able to print 1D / 2D (PDF417)
barcodes that meet IATA BCBP (Bar Coded Boarding Pass) requirements. The
barcodes shall include machine-readable boarding pass data formatted to support
single segment, multi-segment, and interline data encoding.
(b) Direct thermal
(c) 200 dpi
(d) LCD display
(e) Single feed path
(f) Interface: USB
(g) Roll paper feeder.

BR2.2 BR2.2.1 The Bag Tag Printer (BTP) shall meet the following minimum requirements:

(a) Identical model to BPP

(b) 1D / 2D (PDF417) barcode printer
(c) Direct thermal
(d) 200 dpi
(e) LCD display
(f) Single feed path
(g) Interface: USB
(h) Roll paper feeder
BR2.3 BR2.3.1 The Boarding Gate Reader (BGR) shall meet the following minimum requirements:

(a) The supplied BGR shall read 1D / 2D bar code printed boarding documents and
mobile device boarding passes and shall support the various functional requirements
of all airlines supported.
(b) LCD display and configurable audio response
(c) Read time: less than 1.0 seconds.
(d) Interface: USB
(e) Firmware download / upgrade capability
(f) Gooseneck type (face-up)

Scope of work document

Page 24

Confidential
 Confidential

BR2.4 BR2.4.1 The keyboard and mouse shall meet the following minimum requirements:

(a) Standard, good quality 101 keyboard,

(b) Laser mouse, good quality (USB)
(c) Interface: USB

BR2.5 BR2.5.1 The Magnetic Stripe Reader (MSR) & Optical Character Reader (OCR) shall meet
the following minimum requirements:
(a) Three-track MSR (conforming to ISO 7811/2-5 tracks 1, 2 and 3.) able to read credit
and debit cards, loyalty cards and frequent flyer cards as well as MRZ’s from
passports, ID cards, machine-readable visas and ICAO9303 travel documents.
(b) Loose standing, including bracket to be fixed to screen/table.
(c) Interface: USB
(d) Bidirectional OCR read.
(e) Bi-colour LED and audible alarm providing good/bad read indication.
(f) Firmware download / upgrade capability

BR2.6 BR2.6.1 The Bar Code Reader shall meet the following minimum requirements:

(a) The supplied BCR shall read 1D / 2D bar code printed boarding documents and
mobile device boarding passes and shall support the various functional requirements
of all airlines supported.
(b) Visible light and audible read confirmation
(c) Face down presentation
(d) Read time: less than 1.0 seconds.
(e) Interface: USB
(f) Firmware download / upgrade capability

BR2.7 BR2.7.1 The General-Purpose Printer (GPP) shall meet the following minimum requirements:

(a) Dot matrix printer.

(b) Multi-form prints capability.
(c) Tractor feed

Scope of work document

Page 25

Confidential
 Confidential

(d) Interface: USB

BR2.8 BR2.8.1 Securing Peripherals: The Bidder shall provide and install brackets, fixtures, or
other mechanisms to secure the peripheral cables to prevent that cables can be loosened by
pulling or moving the peripheral.

BR2.9 BR2.9.1 TRAINING: The Bidder shall provide formal ‘train the trainer’ instruction sessions for
the airline trainers at each CUPPS airport.
BR2.9.2 The sessions shall be formally prepared and presented.
BR2.9.3 The content of the trainer’s training shall be adequate to allow the trainers to present
the training for end users.
BR2.9.4 The training shall cover at least the following:
(a) CUPPS system sign-on and usage
(b) Peripheral activation and usage
(c) Basic troubleshooting
(d) Fault logging
BR2.9.5 The Bidder shall provide a training manual with the appropriate course material for
each trainee. Such training manuals shall be made available in electronic format for airline
trainers to produce their own copies to be used in training sessions.
BR2.9.6 The Bidder shall prepare training schedules to fit into the project implementation
plan, allowing for all ‘train the trainer’ training as well as airline agent training by airline trainer
in time for system implementation.
BR2.9.7 The Bidder shall provide Computer Based Training software covering at least the
items above for continuous use by airline users.
Table 5: CUPPS Accessories & Peripherals Specs

Scope of work document

Page 26

Confidential
 Confidential

BR3 INTERFACING BETWEEN CUPPS & OTHER SYSTEMS

BR 3.1 BR3.1.1 The CUPPS System shall interface with the airlines’ hosts for transactions.
BR3.1.2 The CUPPS System shall interface with the LDCS servers for transactions. (If
installed)
BR3.1.3 The CUPPS System shall interface with the Baggage Handling System on the airport
to provide active/non-active BSM’s.
BR3.1.4 The CUPPS System shall interface to the scales at each check-in counter.

Table 6: Interfacing between CUPPS & Other systems

Scope of work document

Page 27

Confidential
 Confidential

BR4 CUSS TECHNICAL SPECIFICATION

BR 4.1 BR4.1.1 DELIVERY, STORAGE AND HANDLING

(a) General
i. The Contractor shall deliver, store, and handle all materials for the project using
means and methods that shall prevent damage, deterioration, and loss including
theft.
ii. The Contractor shall fully comply with the delivery, storage and handling instructions
pertaining to each product, as recommended by the product manufacturer, industry
standards, project quality and project standards.
(b) Delivery and Handling
i. The Contractor shall coordinate and schedule delivery so as to minimize long‐term
storage at project site and to prevent congestion and overcrowding of project
spaces allocated.
ii. The Contractor shall adequately coordinate delivery with installation schedule to
minimize holding time for items that are flammable, hazardous, easily damaged, or
sensitive to deterioration, theft and other loses.
iii. The Contractor shall deliver materials to the project site in an undamaged condition
in the manufacturer’s original sealed container or package, complete with labels
and handling instruction, storing, unpacking, protecting and installation.
iv. The Contractor shall inspect all materials on delivery to ensure compliance with the
contract and to ensure that all product received are undamaged and properly
stored.
v. The Contractor shall dispose of all unrequired packing materials as required by the
manufacturer and the project HSE plan.
(c) Storage
i. The Contractor shall store the materials in the ACSA ’s warehouse.
ii. The stored materials in the warehouse will be barcoded by ACSA and in case of
installation, the Contractor shall be issued the materials after ACSA scanned and
updated in the CMDB system.
BR4.1.2 SUBMITTALS
(a) The Contractor shall propose a System Development Methodology, project deliverables
and submittals that is based on international standards for Systems Engineering,
Software Engineering and Project Management.

Scope of work document

Page 28

Confidential
 Confidential

(b) The approved methodology will be defined in the Project Management Plan and the list of
project deliverables and submittals will be listed and maintained in the Project Document
Registry by the Contractor.

(c) The Contractor shall prepare and provide the following submittals (non‐exhaustive)
during the project execution phase:

Project Phase Project Task and Deliverable

1. Design
1.1. Project Management Standards
i. Project Management Plan
ii. Project Quality Plan
iii. Project Procurement Plan
iv. Project Communications Plan
v. Project Document Registry
vi. Project Status Review Report.
1.2. System Materials Data (Materials Approval Form)
Project Phase Project Task and Deliverable
vii. Manufacturers datasheets, including full product/software description.
viii. Detailed technical, functional, and operational specifications,
benchmark data (to support hardware configuration) including
storage and handling requirements, environmental
requirements.
1.3. Detailed Design Specification (DDS) – comprehensive requirements and functional
description
1.4. Equipment Rack Elevation Drawings
1.5. Data Cabling Schedule showing all patching details.
1.6. Logical System and Network Diagrams, including proposed VLAN and IP
address schemes obtained in coordination with the ACSA Network LAN team.
1.7. Functional and Physical Interface Control Design (ICD) documents
1.8. Functional Process Flow and Process Description
1.9. Test Plans for Factory/Functional Acceptance Test (FAT), Laboratory
Acceptance Test (LAT), Site Acceptance Test (SAT) and Airport Integration Test (AIT)
1.10. Test Cases and Test Procedures for each test phase
1.11. Training Plan

Scope of work document

Page 29

Confidential
 Confidential

1.12. Warranty Support Plan

2. Installation
i. Installation and Test Plan (ITP)
ii. Inspection Request
iii. Inspection Report
iv. Snag List
3. Testing and Commissioning
i. Test Report
ii. Commissioning Report
4. Training
i. Training Schedule
ii. Training Manual
iii. Training Certification
iv. Training Report.
5. Project Closure
i. As‐Built Documentation and Drawings and Warranty
ii. Detailed Bill of Materials Support
iii. Asset Register
iv. Spare Parts List
v. Operations and Maintenance Manual
vi. Software License Certificates
vii. Maintenance & Warranty
a. Warranty Support Plan
b. Preventive Maintenance Schedule
c. Service Level Agreement
BR4.1.3 WARRANTY
(a) General

i. The warranty shall cover the complete scope of works as per the system
specification and contract documentation, including any additional scope as a
result of Change Order.
ii. The System shall be warranted for a period of 36 months (minimum) after the
Provisional System Acceptance.
iii. The warranty shall include all software, software setup and configuration work,
software modifications, changes and enhancements completed under the scope

Scope of work document

Page 30

Confidential
 Confidential

of work and meet all requirements specified herein and are free of defects and
inconsistencies.

(b) Hardware Warranty

i. The Contractor shall maintain and service all hardware and equipment to
address any and all malfunctions due to manufacturing or installation defects at
no cost to ACSA during the warranty period.
ii. The Contractor shall be solely responsible for the maintenance of all supplied
equipment during this period and shall provide on‐call maintenance including
both preventative and corrective maintenance and replacement parts as required
by the equipment manufacturer or as is necessary for normal operation of the
System.
iii. The warranty shall allow for replacement or repair of failed components.

(c) Software Warranty

i. All software necessary to compile, modify, and maintain the software developed
for this specification shall be included in this warranty.
ii. The software warranty can be supplied by a service contract.
iii. If a service contract is used to provide warranty, the price of the contract shall be
separately identified, and shall include an annual rate for continuing the services
contract.
iv. The warranties shall include the price of all software upgrades and computer
operating system upgrades during the warranty period.
v. If a new version of the system software becomes available during the warranty
period, it shall be upgraded as part of the warranty.

(d) System Performance Warranty Test

i. After completion of testing (SAT), the Contractor shall maintain responsibility for
the system equipment and components for a thirty (30) day period of operations,
during which all the electrical and mechanical equipment, fixtures and connected
devices will be energized and operated by Bidder and airport operators.
ii. The Contractor is required to provide adequate support personnel to perform any
system configuration and technical support activities in order to keep the system
fully operational and the Subcontract shall troubleshoot and fix any system
failures and software bugs.

Scope of work document

Page 31

Confidential
 Confidential

iii. The thirty (30) day system performance warranty test shall commence at a time
agreed between ACSA and the Contractor.
iv. If during the agreed period, the system fails to operate and perform in
accordance with the Contract terms, the Contractor is required the resolve the
issue and the thirty (30) day system performance warranty test shall begin again.
v. ACSA shall commence the System Provisional Acceptance Test procedure, as
per the contract terms.
vi. The Contractor shall repair and replace any equipment or software that fails to
meet the performance criteria or requirements specified and agreed with the
ACSA .

BR4.1.4 SOFTWARE SERVICE AGREEMENT

(a) General

i. In order to maintain optimum operational conditions, as part of fulfilling software

warranty requirements, the Contractor shall undertake the following:
ii. The Contractor shall resolve a software defect by delivering a new version of the
software after completing test certification or installing a temporary software
patch or approved resolution procedure, to allow operations to continue.
iii. The Contractor shall also be responsible to resolve any third‐party software
delivered and installed as part of the integrated system. i.e., FIDS, AMS

(b) Licensing
i. All the software supplied under this project shall be licensed for perpetual use by
ACSA, without the use of any license key or codes.
ii. All the software shall be licensed for use at all installations, as defined in this
specification.

(c) Changes and Upgrades

i. Any software changes as a result of regular upgrades and bug fixes shall be
immediately made available to ACSA during the warranty period and as long as
the software is installed in an operational condition at INA.
ii. Any approved software changes shall be developed and delivered by the
Contractor to the Test Laboratory no longer than two (2) months.
iii. Failure to do so may result in penalties being imposed by ACSA under the
contract terms governing this system package.

Scope of work document

Page 32

Confidential
 Confidential

BR4.1.5 INTELLECTUAL PROPERTY

i. When patented articles, methods, materials apparatus, etc., are used in this
work, the Contractor shall acquire the right to use same.

ii. The Contractor shall hold ACSA harmless for any delay, action, suit, or cost
growing out of the patent rights for all devices or software used on this Project.

iii. When the copyrighted software is used in this work, the Contractor shall acquire
the right to use same.

iv. Operating system software shall be existing, industry accepted, and of a type
widely used in commercial systems.

v. Application software shall have been used for a minimum of two years and shall
be written in a standard; industry accepted computer language.

vi. All software shall be delivered with full documentation including all software error
messages (Codes), code descriptions and troubleshooting guide.

vii. Text based instruction sets for error code resolution shall be provided along with
supporting process and flow charts.

viii. All Commercial‐Off‐The‐Shelf (COTS) software products shall be provided with

documentation stating where the COTS package will be used and be provided
with all license information.

ix. All software delivered or created as part of this project shall be licensed to ACSA
.

x.Fully configured and installable software back‐up copies shall be provided by the
Contractor for all software products provided for use on the project.

BR 4.2 BR4.2.1 SYSTEM REQUIREMENTS

(a) The Contractor shall Design, Supply, Install, Test and Commission all material required
for the CUSS platform.

(b) The CUSS platform specified shall follow the key principles defined in the IATA CUSS
Technical Specifications 1.3 (released in Jun 2013), the best practices adopted by all
major international airlines and major international airports.

(c) The CUSS platform shall utilize the airport installed CUTE/CUPPS System or direct

Scope of work document

Page 33

Confidential
 Confidential

connection for host connectivity to support airline’s DCS applications and peripherals
such as ATB and BTP equipment.

(d) The CUSS platform shall support multi‐lingual capabilities including English and other
languages to be defined by ACSA business.

(e) The CUSS Kiosks shall support multiple data entry methods, such as touch screens,
onscreen keyboards (multi language), 2D Barcode scanners and passport (OCR)
readers/scanners.

(f) The CUSS platform shall include application and system monitoring sensors and tools
that shall provide automatic alerts and warnings to central (internal and external)
monitoring systems.

(g) The CUSS platform shall support multiple airlines.

(h) The CUSS kiosks shall allow passengers to perform all aspects of the passenger
check‐in process, including the following minimum operations:

i. Check‐in
ii. Seat Selection
iii. Print Boarding Pass
iv. Passport Check
v. Security questionnaire
vi. Print Baggage Tag.

(i) The scope of work includes the following:

Preliminary and detailed design including:

i. CUSS Principles
ii. CUSS Kiosk Architecture
iii. CUSS Hardware Architecture
iv. CUSS Software Architecture
v. CUSS Kiosk Application
vi. ICD and other design submittals.
vii. CUSS Kiosk shall include the following:
viii. CUSS Kiosk Enclosure
ix. PC

Scope of work document

Page 34

Confidential
 Confidential

x. CUSS Application
xi. Touch Screen
xii. Boarding Pass Printer and Scanner (2D capable)
xiii. Magnetic Card Reader
xiv. Credit Card Reader and printer
xv. UPS
xvi. Passport Reader and Scanner
xvii. Bag Tag Printer
xviii. Receipt Printer
xix. Door sensor
BR4.2.2 DESIGN REQUIREMENTS
(a) General

i. The CUSS Software Platform shall support multiple concurrent CUSS certified
applications.
ii. The CUSS System shall be designed to support multiple airlines.

(b) Software Architecture

i. A Multi‐tiered Client application is the preferred software architecture.

(c) System Management

i. Automated Remote Updates (ARU) shall be provided for all software

components to facilitate deployment to CUSS Kiosks and or CUSS workstations.

(d) Data Security

i. PCI‐DSS Compliance must be adhered to in all cases.

BR4.2.3 PERFORMANCE REQUIREMENTS

(a) General

i. The following performance parameters are listed to guide the Contractor in

determining the system specifications during the proposal phase.
ii. The Contractor is required to validate the system specifications during the design
and materials approval activities to ensure that these performance parameters,
including spare/growth parameters are met and approved by the ACSA .

Scope of work document

Page 35

Confidential
 Confidential

(b) System Response Time

i. The time that is required to process and on‐line request and respond back with
an appropriate (complete and correct) result.
ii. The response time shall be measured during peak load conditions.
iii. The system query can be both on‐line request and processing of an interface
message.
iv. The on‐line response for a query or update request shall not exceed three (3)
second for 99% of all transactions.
v. The remaining one (1%) percent on‐line response shall not exceed five (5) seconds.
vi. All updates or refresh to any display device shall not exceed three (3) seconds.
vii. The total time to fail‐over from the primary server(s) to the secondary server shall
not exceed sixty (60) seconds, and the user, including interface, shall not be
required to restart or login or select a different server/host address.
viii. No interface messages shall be lost due to system failover or fallback.
ix. The total system start‐up time (cold start) from complete system shutdown, shall
not exceed twenty (20) minutes.

(c) System Changes

i. The CUSS System shall allow on‐line configuration changes without any need to
shut down or restart application services or having to reboot the hardware to
affect changes made.
ii. CUSS System changes shall include installation and connection to newly
installed CUSS Kiosks.
iii. The CUSS Contractor shall be responsible to perform maintenance and system
tuning during the period the system is operated and maintained under the terms
of the contract scope of work.
iv. System changes shall be governed by an approved Change Control Procedure,
submitted as part of the Project Management Plan, and approved by the ACSA .

BR4.2.4 HARDWARE
(a) General
i. The following are guidelines and specification that are fully dependent on the
Contractor in meeting the technical and performance requirements in this
specifications document.

Scope of work document

Page 36

Confidential
 Confidential

ii. The Contractor is required to propose an optimized solution that is able to scale
to meet the construction and operational growth needs for ACSA.
iii. All hardware equipment supplied shall be commercial or Enterprise grade off the
shelf products.
iv. The Contractor shall ensure that upon restoration of a power failure (e.g., during
a longer-term utility power failure where the generators have not come online), all
high-level control related hardware shall automatically power up after a
configurable delay to verify power supply stability.
v. The Contractor shall provide software and hardware as needed to ensure that
the entire configuration is fault tolerant to support the performance requirements
specified herein.
vi. The Contractor shall connect to the provided disconnect switches and provide all
power distribution as needed to the equipment in the server and control rooms.
vii. ACSA shall install power and data outlets for the control room workstations.
viii. The Contractor shall provide network patch cords for the workstations, if
supplied, located outside the server and control rooms.
ix. The Contractor shall utilize the overhead cable trays (installed by others) in the
server rooms for power and data cabling.
x. The Contractor shall note that the requirements for hardware described are the
minimum requirements.
xi. The Contractor shall provide higher specification equipment if required to achieve
any of the performance requirements specified herein.
xii. The Contractor shall, together with ACSA’s approval, select the latest technology
at the time of procurement.
xiii. The servers shall include minimum dual network cards (NIC) that will support at
least 10 Gbit Ethernet connections.
xiv. Additional (lower speed) network connections shall be required for high
availability features and LAN administration support needs.

(b) Server (Application and Database) Configuration

1. The Contractor shall deploy CUSS on physically separated servers for the
application and database system.
2. The configuration of each hardware shall be based on Performance Requirements
defined, including the number of connected devices.

Scope of work document

Page 37

Confidential
 Confidential

3. Nevertheless, the minimum server hardware specification shall include the following:

i. 19” rack mount chassis,

ii. Hot swap redundant power supplies connected to separate power

sources,
iii. Redundant fans,

iv. Redundant LAN interfaces (minimum 10 Gigabit speed),

v. Redundant interfaces to the Data Storage System, if supplied,

vi. Multiple Quad Core CPU to meet performance requirements,

vii. The type and amount of physical memory (RAM) shall be determined
by the Tenderer as per the System architecture and support for the
performance requirements specified herein,

viii. If the operating system is located on a local storage medium the

storage shall be provided in redundant configuration.

ix. Full remote management capability

x. The adequacy of the processing power of the servers shall be

demonstrated though calculations (e.g., number of transactions or
incidents and number of sensors) and comparison to other projects
performance criteria (e.g., number of flight movements, number of
concurrent users, number of system interfaces, etc.) and server
processing power,

xi. Server processing power shall also be demonstrated during stress or

performance testing,

xii. The server processing power must be a minimum 25% above the
calculated required for the operation of the system at full capacity,

xiii. If server virtualization is used, the virtual servers shall be split over a
minimum of at least two (2) physical servers,

xiv. If additional physical servers are needed, sufficient physical servers

shall be provided such that 50% of the physical servers can fail,

Scope of work document

Page 38

Confidential
 Confidential

xv. If server virtualization is used there shall be a non‐virtualized

workstation for the management of the physical and virtual servers,

xvi. If virtualization is proposed, only common virtualization platforms

(VMWare) shall be used.

4. The type and number of application servers shall be determined by the Contractor
based on the proposed solution and estimated number of kiosks planned for the
airport.
5. The final hardware configuration shall be defined during the Detail Design Phase and
included in the Materials Approval Submittals before final purchase is done.
6. The Contractor shall perform a System Performance Test to demonstrate that the
hardware specifications in the Materials Approval Submittals comply with the
Performance Specification, Scalability Requirements and Spare Parts requirements
defined in this specification.

(c) CUSS Kiosk

1. Integrated Kiosk Enclosure

i. Stable free standing chasis.

ii. Maintenance doors or panel to be secured with lock.

iii. All kiosks within the installation to use an identical key.

iv. Locking mechanism to be designed so that key cannot be removed

from the lock unless the panel is securely closed.

2. UPS

i. Battery charging and management system.

ii. PC Software to be configured to initiate the shutdown of the kiosk

after 10 minutes on battery.

3. Card Reader

i. Multi‐format card reader; capable of reading ISO tracks 1, 2 & 3.

ii. Reading 3 track credit card information, ISO 7811/2‐6.

iii. Accepting the following: magnetic cards, such as Credit cards, smart

Scope of work document

Page 39

Confidential
 Confidential

cards, frequent flyer cards, employee travel cards.

iv. Read the following card formats: ISO 7810, ISO 7811, ISO 7812,
ISO 7813.

4. Passport Reader

i. The Passport Reader shall be equipped with extended input tray to

facilitate self‐service operation.
ii. The Passport Reader shall read OCR A as per ISO 1073/I and read
OCR B as per ISO 1073/2.
iii. OCR read rate shall be minimum 95%.
iv. The Passport Reader shall be compliant with ICAO 9303 to accept
Passports and ID cards.
v. The Passport Reader shall have an in‐built functionality to flag
“unreadable” or “ambiguous” characters in the output text stream.
vi. The Passport Reader shall support more than 45 characters per line
of text, with 3 lines read.

vii. The device shall read the ICAO compliant biometric passport
“e‐passport” ISO 14443 Type A and B including anti‐collision, and
auto detection.
5. Barcode Reader

i. The device shall be flatbed model of barcode scanning.

ii. The device shall read BCBP with 2 Dimensional Symbols (2‐D)
PDF417 barcodes.

iii. The device shall read the documents (tickets / bag tags) with 1
dimensional (1‐D) barcodes (code128.code39, Industrial 2 of 5).

iv. The device shall read Mobile Phone 2D (e‐BCBP) barcodes (Aztec,
EAN13, Datamatrix).

v. The device shall have omni‐directional scanning and decoding

without any moving parts and shall utilize LED based illumination.

6. Secure Card Access Devices

Scope of work document

Page 40

Confidential
 Confidential

i. The device shall be complaint to the international standards of ISO

7816, ISO 14443, and ICAO 9303

7. The audio output from the PC to be connected to a stereo amplifier that drives a
stereo pair of 8-watt speakers mounted inside the kiosk and the volume control shall
be adjustable through settings in the CUSS platform.
8. Automated Ticketing and Boarding (ATB) Printer:

i. ATB Printer shall be capable of continuous printing on up to 9-inch-

wide stock.

ii. ATB Printer shall be capable of printing Boarding Pass documents

including 2‐D barcode compliant with IATA PDF 417.

iii. ATB Printer shall have Direct Thermal Technology print‐head

capable of printing high quality 1D/2D barcodes.

iv. ATB Printer shall be connected to the CUSS workstation through

USB or serial port.

v. Print resolution requirements shall be sufficient to conform to the

IATA’s BCBP standard at least 203 dots/inch.

9. Baggage Tag Printers (BTP):

i. Baggage Tag Printer shall be capable of printing a document on bag

tag size stock.

ii. Baggage Tag Printer shall have Direct Thermal Technology

print‐head and it shall be capable of printing high quality 1D
barcodes.

iii. Baggage Tag Printer shall be connected to the CUSS workstation

through the USB or RS232 serial port.

10. Sensors

i. Door position status.

ii. Door‐lock status.

iii. Ticket in output area.

Scope of work document

Page 41

Confidential
 Confidential

iv. Diagnostics switch activated.

v. Low paper status on all printers.

vi. Low paper status and ticket status shall be implemented using
optical detectors.

vii. These sensors shall be connected to an I/O controller.

viii. I/O controller shall have visual indication of sensor status using
LEDs or display panel.

ix. The I/O controller shall interface with the PC using parallel, serial or
USB port.
x. Software device driver and diagnostics shall be installed on the
CUSS platform to provide the status information required under the
CUSS standard.

11. Each Kiosk Enclosure material structure and design shall be based on approved
standards and agreed after coordination with ACSA and Contractors Authorised
Representatives.

BR4.2.5 SOFTWARE
(a) General
i. Each software component must be included as part of the Material
Submittal document for approval by ACSA and Contractor, prior to
being purchased.
ii. The software and system components must meet the operational,
functions and especially meet or exceed the performance
requirements specified.
iii. The software installed in all the environments must be the latest
version with the latest software patches supplied by the
manufacturer.
iv. The software supplied must be out‐of‐the‐box and commercially
off‐the‐shelf (COTS), with no programming changes.
Customization shall be based on configuration changes, through
the use of information exchange standards to be agreed with
ACSA.

Scope of work document

Page 42

Confidential
 Confidential

v. Database objects shall be initiated though a single database

procedure, including changes; Database object changes shall be
strictly controlled via the configuration management and change
management procedure(s).
vi. System Servers shall be hardened, based on industry standard
security measures with appropriate anti‐virus and system
protection applications.

(b) Database System

i. The CUSS database(s) for all systems and subsystems shall be
Oracle™ Enterprise (12.c or later), or Microsoft SQL Enterprise (2019 or
later) or approved equivalent and shall include real time database
mirroring and on‐line archiving.
ii. Field level encryption support with 128‐bit DES/RSA techniques or equivalent
iii. The database system shall support granular data‐access in order to
implement “separation of duties” data security measures.
iv. A fully integrated Database Administration Utility shall be supplied to
manage all functions and operations of the database system.
v. Support for in‐memory database table(s) for high performance transactions
vi. Capable of performing on‐line database back‐up.
vii. The database maintenance system shall be capable of maintaining
configuration control and the maintenance software shall be provided to
enable updating or regenerating of the database tables when inputs are
changed and added.
(c) Operating System (OS)
i. The operating system shall have the following features:
ii. True 64‐bit, multi‐tasking‐multi‐threading OS such as UNIX, Linux, or
Windows Server.
iii. Supports TCP/IP network protocol.
iv. The server OS shall be the latest version and support for scalability and
high availability setup for the system.
(d) Platform Management Application
i. All communication to the peripherals shall be through this defined
platform interface.

Scope of work document

Page 43

Confidential
 Confidential

ii. For the functional requirements of the Component Manager and the
configuration parameters, IATA CUSS standard shall be referred.
iii. The application manager shall handle all requests to start, resume,
suspend and stop CUSS applications.
iv. User interaction with the kiosk shall not incur any noticeable delay and
shall conform with airline application specifications.
(e) Common Launch Screen
i. There shall be a common launch screen in the foreground as long as
there is no active CUSS application.
ii. The screen shall be based on the airline logo for those airlines and
handling agents with a kiosk application.
iii. There shall be an idle screen after a specific period of time when no
CUSS application is active.
iv. The passenger touches the idle screen and reaches the common launch
screen.
v. In the case that all registered kiosk applications are unavailable;
stopped, disabled, or suspended, the platform management application
shall show a “Kiosk not available” type of screen.
vi. All screen layouts shall be according to the ACSA ’s branding standards
and shall be developed during workshops with the Contractor .
(f) System Manager
i. The System Manager is the defined platform interface for remote
management of the kiosk. It is an interface implemented on the kiosk,
allowing for remote connection from authorized system managers.
ii. Functionality provided by the System Manager shall include:
iii. Reporting errors, alerts and alarms encountered by device components.
iv. Reporting of platform events such as application state changes,
application events, etc.
v. Gathering statistical information.
vi. Remote control of the application with the
features of load/stop/suspend/resume.
vii. The System Manager interface shall provide the ability to control and
monitor the platform through interfaces with the device components and
the application manager functions in the platform.

Scope of work document

Page 44

Confidential
 Confidential

viii. The System Manager shall be also responsible for interfacing with the
common launch screen platform to perform various actions, which are
not limited:

• to removing application icons from the selection (launch) screen

when individual applications are disabled, stopped, suspended, or
become unavailable for whatever reasons,

• to display an appropriate general “Kiosk not available” screen

when applications are disabled, stopped, suspended or
unavailable.

(g) Airline Application

i. The Airline Application is the application provided by the airline to enable
the passenger check‐in and print the documents.
ii. The Airline Application has interfaces to the airline kiosk transaction
server and airline kiosk manager. The CUSS platform shall support such
communications according to the CUSS standard.
iii. Applications to be installed on the CUSS platform shall be supplied by
each airline and handling agent. The Contractor shall install the
application according to the documentation supplied with each airline
application.
iv. The Contractor shall coordinate with each airline for the configuration of
network connectivity and network names and IP addresses.
v. Only CUSS certified applications shall be installed on the CUSS platform.
vi. Development of airline applications, certification of application or work
required to achieve certification is not included within this contract.
(h) Security
i. Authorized users shall log into the system using a unique username and
password.
ii. Depending on assigned user access privileges, the user shall be either
granted or denied access to individual application, screen, or data.
iii. System administrator shall be able to add, delete, set, and change user
privileges and access authorization via a GUI built into the general
operations of the application and servers. All system parameters shall be
configurable by the system administrator.

Scope of work document

Page 45

Confidential
 Confidential

iv. The system shall have an idle time period and if any workstation is
determined as inactive, it shall be automatically logged out of the
system. The idle time shall be configurable by the system administrator.
This idle time period shall be recorded in the log file including
workstation identifier, date, and the user information.
v. The system shall provide an audit trail of all the transactions. The audit
file shall log any changes on the application configuration, data structure
or database records and shall contain the details of the change with the
workstation identifier, date, and user information.
vi. All supplied systems and workstations shall be protected by virus
protection software. The Contractor shall submit the exact model and
configuration of it.
(i) Network
i. CUSS shall utilize the Airport Network infrastructure to provide services
to all devices and kiosks. The primary and secondary servers shall be
located in two different main communication rooms and shall be
connected to the network switches via the predefined Airport Network
requirements like 10 Gigabit Ethernet NIC.
ii. All kiosks shall be connected to a dedicated VLAN using an interleaved
approach to avoid total disruption of an entire row of workstations. The
VLAN assignment shall be in a way that in the same area all the kiosks
shall not become down in case of a network failure.
iii. All system shall be capable of being SNMP managed and monitored by the
centralized remote management system.
BR4.2.6 INTEGRATION
(a) Airline Departure Control System

i. The CUSS System shall provide airline host connectivity and shall fully
support airline system hosted peripherals such as ATB and BTP printers
connected over standard communication protocols such as TCP/IP,
ALC, UTS and X.25 via.
ii. Airport installed CUTE System or,
iii. Direct integration with the Departure Control Systems of the airlines.

(b) Local Departure Control System

Scope of work document

Page 46

Confidential
 Confidential

i. The CUSS System shall use an Airline Application provided by the LDCS
supplier for the interface with the LDCS servers for check‐in
transactions.

BR4.2.7 TEST PLATFORMS

(a) General
i. In order to facilitate the development of systems and reduce the risk of
systems integration, a Test Laboratory or Test Centre will be constructed
and managed by The Contractor. The Contractor shall include as part of
the system development plan to install a test system and perform
functions and integration test using the facilities in the Test Centre.
ii. The Contractor shall supply and install a Test System, including
hardware and software systems, for the purpose of functional, integration
and performance testing.
iii. The Test System shall be able to support the following environments:
• Test (TST): This environment shall be initialled used for migration or
upgrades after completion of the SAT phase.
• Training (TRN): This environment shall be the same as when the SAT
phase commences and shall keep pace with upgrades to the
production (PRD) environment.
iv. One unit of kiosk shall be provided to evaluate the material and colour
properties.

(b) Test Phases

i. Below is a diagram showing the different stages of testing in the different

test environment and the proposed software release management
process.
ii. The Test Centre and Training Centre shall be located in the ACSA
Data‐Centre Building.

BR4.2.8 SPARE PARTS

(a) Spare part quantities should be specified and costed.
BR4.3 BR4.3.1 EXECUTION
(a) General
i. The execution of the project shall be fully governed by the approved

Scope of work document

Page 47

Confidential
 Confidential

project management methodology and project management

documentation.

ii. ACSA assumes no responsibility or liability for transportation from

country of origin, storage fees, demurrage, import taxes, duty taxes, or
other costs associated with the delivery and storage of system
components.

iii. The Contractor shall be responsible for any and all loss or damage in the
shipment and delivery of all material until transfer of title to ACSA .

iv. The Contractor shall store products in accordance with manufacturer's

instructions, within Contractor's staging area and with seals and labels
intact and legible.

v. Sensitive products shall be stored in weather‐tight enclosures; maintain

within temperature and humidity ranges required by manufacturer's
instructions.

vi. After installation, the Contractor shall provide coverings to protect

products from damage from other construction operations, and the
protective coverings are to be remove when no longer needed.

vii. The Contractor shall ensure that all work performed under these
Specifications is in accordance with the requirements and standards
defined and referenced in these Specifications.

viii. Any work performed in deviation of these Specifications, any of the

referenced material, or any applicable standards or requirements, shall
immediately be corrected by the Contractor without additional charges,
regardless of the stage of completion.

ix. The Contractor shall record all inspection observations.

x. As a minimum, the record shall include the name(s) of personnel

conducting the inspection, a brief description of the inspection and the
observations.

Scope of work document

Page 48

Confidential
 Confidential

xi. These records shall be available for ACSA to review at any time.

xii. Also, these records shall be delivered to ACSA before issuance of final
acceptance certificate.

xiii. The Contractor shall ensure that only qualified personnel are included in
the project team for the purpose of system installation, system testing,
system commissioning, and system administration activities.

xiv. The Contractor is required to provide detailed personal resumes and

qualification details, including work experiences, relevant (and current)
qualification and training certification from appropriate OEM and software
vendors.

BR4.3.2 INSTALLATION

(a) General

i. All installation inspections shall be undertaken through the performance

of preinstallation, in‐progress, and final inspections activities.
ii. All Installation planning and completion shall be described as part of the
Project Management Plan, Project Quality Plan, Installation Method
Statement and Testing and Commissioning Plan, and shall be approved
by ACSA .

(b) Pre‐Installation Inspection

i. The Contractor shall schedule the detailed inspection of all equipment

and material to be used prior to delivery and installation at site.
ii. All items shall be verified for compliance with the requirements of these
specifications and all other applicable standards.
iii. All equipment, cables, and associated hardware identified for installation
shall be inspected for damage and completeness utilizing standard
practices to determine integrity and acceptability.
iv. Installation Method Statement and HSE method statement
documentation shall be submitted for approval prior to delivery and

Scope of work document

Page 49

Confidential
 Confidential

installation.

(c) In‐Progress Inspection

i. The Approval of Material Inspection documents shall be completed

before any installation inspection is scheduled.
ii. At ACSA 's discretion, the Contractor shall perform in progress
inspections that shall include visual inspections of equipment, wiring
practices, cabling, placement of equipment, marking of cables and
adherence to safety procedures. In addition, ACSA , or its
representative, may conduct additional inspections at any time.

(d) Final Inspection

i. The Contractor shall conduct a final inspection that encompasses all

portions of the installation.
ii. This inspection shall be performed to ensure that all aspects of the
installation have been performed in accordance with these
Specifications, standard industry practices and the publications
referenced herein.
iii. All non‐compliance items shall be noted by the Contractor during this
inspection.
iv. ACSA and the Contractor shall witness the material inspection.

(e) Corrective Action and Verification Inspection

i. The Contractor shall perform corrective actions to ensure that all

non‐compliance items identified during the final inspection have been
corrected.
ii. ACSA shall witness this inspection.

BR4.3.3 COORDINATION
(a) General
i. The Contractor shall initiate and attend all relevant project meetings and
take the lead in the coordination of all aspects of project management,
design, documentation and document review process, interface

Scope of work document

Page 50

Confidential
 Confidential

development, and shall proactively manage the other subsystems that

are required to be tightly integrated to the CUSS System.
ii. The Contractor project manager shall initiate and coordinate weekly
project review meeting and produce weekly status reports as minutes of
the week review meeting.
iii. The project manager shall produce a monthly project status report, within
five working days from the last day of each month.
iv. The CUSS Contractor shall support the ESB Contractor coordinate with
all relevant system subcontractors, and not limited to the following,
ACSA ,Airlines, Ground Handers, and others, in order to facilitate the
development and implementation of required interfaces and integrated
airport operational functions.
v. These coordination activities during the design phase will also result in
the preparation of airport operational business functions process flows,
process description, and ICD documents, and will supplement any
Airport Operations Plan and Procedures, if developed by Operations
team.
vi. Each ICD and Airport Business Rules defined for CUSS shall be
approved by ACSA and other parties involved in the interfaces.

(b) CUSS System Kiosks

i. The Contractor shall coordinate with ACSA in determining the locations
of the CUSS Kiosks and the architectural as well as physical features
that need to be accommodated in the design and final installation.
ii. The CUSS Contractor shall schedule and coordinate a series of
workshops with ACSA , other relevant System contractors, Operations,
Airlines for the development and finalization of ICDs and Business Rules
for the operations of the CUSS Systems and systems that interface with
it.
iii. Coordinate with each system contractors for the development of system
interfaces and ICDs.
iv. Planning and testing of airport business process involving the CUSS
System and its interfaces.

Scope of work document

Page 51

Confidential
 Confidential

BR4.4 CUSS System Requirements:

BR4.4.1 The CUSS System shall operate 24 hours per day, 7 days per week, throughout the
year.
BR4.4.2 CUSS is considered a critical operational system and care with the design parameters
needs to be taken.
BR4.4.3 Device Availability: A device shall be considered available only if all components are
operating and fully functional. Besides scheduled downtime, individual device availability shall
be at least 99.99 %
BR4.4.4 All received messages from, but not limited to, airline host systems and CUSS
management workstations, shall be processed in less than 300 milliseconds.
BR4.4.5 Based on common practice it is expected that host transactions will be processed in
less than 2 seconds, but at least not more than 4 seconds.
BR4.4.6 The System shall be capable to run multiple terminals as well as airports.
BR4.4.7 The Bidder shall deliver a benchmark document describing:
• The CUSS System load on a regular basis.
• The CUSS System load on peak hour processing.
• Any other information that seems relevant to the Service Provider.
• Monthly availability reports are produced as per the Performance Level Service
Schedule.
BR4.5 CUSS Non-Functional Requirements
BR4.5.1 CUSS Kiosks shall be connected via the CUPPS communication infrastructure to the
core computer room (provided by ACSA, Bidder to manage). The Bidder shall provide the
routers/gateways required for airline host connectivity if not provided as part of the CUPPS
communications infrastructure.
BR4.5.2 The CUSS System shall have the capability to simultaneously run multiple airlines
applications performing the Check-in functions for the participants’ airlines passengers on a
shared base.
BR4.5.3 The CUSS solution shall be of the latest technology and widely used in many
international airports by many international airlines – only the latest production model would be
acceptable.
BR4.5.4 The Kiosks shall be equipped with readers to identify the passenger, including bar-
coded e-ticket, paper barcode boarding passes, mobile phone boarding passes, passport,
frequent flyer card, credit card, smart card and produce boarding passes and bag tags after
validating and capturing the passenger travel documents.

Scope of work document

Page 52

Confidential
 Confidential

BR4.5.5 The CUSS solution shall be efficient of processing passengers with and without hold
baggage.
BR4.5.6 Administration and Configuration: The System specific configuration and specific
parameters shall be stored in the System database.
BR4.5.7 The Bidder shall recommend and provide the hardware and server configuration that
best serves the overall design solution. All hardware shall be from a reputable manufacturer
capable of a high level of maintenance and service.
BR4.5.8 Hardware specifications detailed in this document are the minimum requirements. The
Bidder is required to supply the latest available hardware at the time of delivery.
BR4.5.9 The System design must permit a server to be taken off-line and replaced without any
disruption to CUSS operations. BR6.7.1 Other Requirements
BR4.5.10 The System shall be scalable and expandable to accommodate future increase of
number of CUSS kiosks in any of the deployed Airports.
BR4.5.11 The CUSS Kiosks in the ACSA Airports shall be connected to the CUPPS VLAN
either wired through 1 x Gigabit or 10/100/1000 MBit TX NIC or wireless through RF wireless
network (802.11b/g/n) as redundancy option.
BR4.5.12 The CUSS Application servers shall be located in the ACSA Core rooms and shall
provide the capability for remote monitoring.
BR4.5.13 For redundancy, each of the CUSS servers shall be installed in separate Core rooms
– if required. CUSS is provided at the 3 large (hub) airports and 6 satellite airports, and airlines
using these connections, need not supply additional connectivity.
BR4.5.14 The System and applications software are controlled and configured by working
parameters stored in tables and easy to change without programming actions.
BR4.5.15 User interaction with the System shall incur no noticeable delay in line with airline
application specifications.
BR4.5.16 The System shall be able to accept a wide range of CUPPS compliant input and
output peripherals.
BR4.5.17 The CUSS System including its peripherals shall fully support the e-ticketing
requirements as required by IATA.
BR4.5.18 The Passenger Processing Systems (CUPPS and CUSS) at ACSA airports shall
operate as an integrated platform performing all required processes. Any of the Passenger
Processing Systems shall exactly perform in a common-use environment.
BR4.5.19 The Bidder shall install all core equipment required for the CUSS system in order to
be fully operational.

Scope of work document

Page 53

Confidential
 Confidential

BR4.5.20 The platform software consists of all the software required to enable CUSS
functionality, including all operating systems, databases, data exchange software where
required, except those supplied by the application providers (airlines).
BR4.6 BR4.6.1 CUSS Reporting Requirements (Statistics)
BR4.6.1.1 The System shall store and manage at least the following:

BR4.6.1.1.1 Use time of equipment, including but not limited to:

a) Per CUSS kiosk.
b) Per hour per CUSS kiosk
c) Per Airline DCS / host system.
d) Additional statistics to be decided in consultation with ACSA .
BR4.6.1.1.2 Number of boarding cards printed.
(a) Number of baggage tags printed.
(b) Number of transactions processed through other peripherals, by
peripheral.
(c) The System shall be able to print out various customizable reports
(d) The System shall be able to provide statistical information on a daily
and weekly basis in a text file format.
BR4.7 BR4.7.1 CUSS Interfaces
BR4.7.1.1 The CUSS System shall interface with the airlines’ hosts for transactions.
BR4.7.1.2 The CUSS System shall interface with the LDCS servers for transactions. (If
installed)
BR4.7.1.3 The CUSS System shall interface with the Baggage Handling System on the airport
to provide active/non-active BMS’s.
BR4.8 BR4.8.1 Supervision:
BR4.8.1.1 The System has to manage at least the following:

(a) Remote control on equipment to analyse, test and maintain.

(b) Remote configuration.
(c) Server and software status.
(d) Software distribution.
BR4.9 BR4.9.1 CUSS Application Servers, Gateways and Switch Requirements

BR4.9.1.1 All Servers, gateways, routers, and switches should be 19” rack mounted in cabinets
provided by ACSA. Should be provided with all software required to operate and be managed
Scope of work document

Page 54

Confidential
 Confidential

efficiently.
BR4.9.1.2 The CUSS Application servers shall be located in ACSA core rooms and shall
include the CUSS Management Servers as well as the Web servers for providing access to
browsers mainly for remote monitoring.
BR4.9.1.3 For redundancy, each of the CUSS servers shall be installed in separate core
rooms. It is required that each airline shall have two separate WAN Circuits, for ensuring
redundant WAN Connectivity to their hosts. The CUPPS network is provided at ORTIA, KSIA
and CTIA and shall be used as the main WAN links for CUSS connectivity.
BR4.9.1.4 The CUSS servers shall fully monitor and manage the CUSS environment.
BR6.9.1.5 The Bidder shall install all core equipment required for the CUSS system in order to
be fully operational.
BR4.9.1.6 The equipment should be so selected to operate the full 5 years without upgrade or
degradation of service.

BR4.10 BR4.10.1 CUSS Application Software

BR4.10.1.1 The platform software consists of all the software included in the Kiosks except
those supplied by the application providers (airlines).

BR4.10.1 .2 The Bidder is responsible of providing the Kiosks with the latest version of the
following software environment: Microsoft Windows Operating System, Internet browser, Java
virtual machine, miscellaneous software containers and plug-ins.

BR4.11 BR4.11.1 CUSS Management Application

BR4.11.1.1 The platform software is responsible for managing the entire Kiosks System
including and not limited to:

BR4.11.1.1.1 Presentation of all platform processes including browser and device

components.
BR4.11.1.1.2 Providing data and statistical information to the remote management
System via the System manager interface.
BR4.11.1.1.3 Controlling/monitoring components states.
BR4.11.1.1.4 Managing System security.
BR4.11.1.1.5 Displaying common screens while no Kiosk application is active.
BR4.11.1.1.6 The CUSS Management Application shall be a web-based graphical tool
for monitoring and managing a network of Kiosks spread in different locations in the

Scope of work document

Page 55

Confidential
 Confidential

airports.
BR4.11.1.1.7 Allowing management workstations to connect and manage the Kiosks
network.
BR4.11.1.1.8 Each workstation can be configured separately with restricted access to
various functions.
BR4.11.1.1.9 Having the capability of event scheduling such as files transfer, operating
Systems commands, software updates and rebooting.
BR4.11.1.1.10 Ability to display the status of each Kiosk as well as each device and
sub-System connected to each Kiosk.
BR4.11.1.1.11 Maintaining general information and statistics for each Kiosk and its
peripherals.
BR4.11.1.1.12 Allowing Kiosk views to be customized by group or status.
BR4.11.1.1.13 Ability to interface with other Kiosk applications for handling alerts and
events.
BR4.11.1.1.14 The Management Application is also responsible of interfacing with the
Common Launch Application (CLA) to perform various actions not limited to removing
application icons from the selection (launch) screen when individual applications are
disabled, stopped, suspended, or become unavailable for whatever reasons, or to
display an appropriate general “Kiosk not available” screen when applications are
disabled, stopped, suspended or unavailable.
BR4.11.1.1.15 Ensuring the integrity of each Kiosk by periodically polling each Kiosk.
BR4.11.1.1.16 The Management Application web architecture allowing the
management workstations to have access from anywhere in the network with different
access rights.
BR4.11.1.1.17 Ability to communicate any Kiosk problem to the different support
entities.
BR4.11.1.1.18 Monitoring and alarming of paper low and paper out condition on each
printer on each kiosk.
BR4.12 BR4.12.1 Common Launch Application: CLA
BR4.12.1.1 CLA application must be resumed during idle times when no other Kiosk application
is active.
BR4.12.1.2 The CLA must show common launch screen with all application providers’ logos
that have a Kiosk application registered on the Kiosk and that are currently available and
selectable.

Scope of work document

Page 56

Confidential
 Confidential

BR4.12.1.3 The passenger must be able to choose the application provider’s logo. This choice
is reported to the Management Application, which then activates the indicated Kiosk
application.
BR4.12.1.4 In case of all registered Kiosk applications are unavailable, stopped, disabled, or
suspended, the common launch application shall show “Kiosk not available” type of screens.
BR4.12.1.5 The CLA screen shall be informative, attractive, and user-friendly.
BR4.12.1.6 The Application shall be easily customized and controlled.
BR4.12.1.7 The Bidder shall allow for set-up and configuration of the CLA page for each airport
at implementation.

BR4.13 BR4.13.1 CUSS Hardware Requirements: The key design considerations for the Kiosk
hardware are as follows:
BR4.13.1.1 Accessibility: The Kiosks design shall be compliant with the following:
(a) International Civil Aviation Organization (ICAO) Document Number:
Circular 274-AT/114: Access to Air Transport by Persons with Disabilities
([RD4]).
(b) International Standards Organization Document Number: ISO 9999:1998:
Technical Aids for Disabled Persons - Classification ([RD6]).
(c) United States’ Americans with Disabilities Act (“ADA”)
(d) Canada’s Canadian Transportation Act and Canadian Human Rights Act.
(e) United Kingdom’s Disability Discrimination Act.
BR4.13.1.2 Aesthetics: ACSA has the right to select the colour and material of the Kiosk from
a wide range of choices.

BR4.13.1.3 Branding: Kiosks may be branded in a variety of ways:

(f) Customized logos.
(g) Customized graphics for the Common Launch component.
BR4.13.1.4 Durability:
(h) The Kiosks are built from a uni-body welded design of strong, cold-rolled
steel.
(i) The baked-on epoxy paint finish cleans easily and is scratch resistant and
protected against liquid splashes, dust and falling dirt.
(j) The Kiosk shall have adequate ventilation for the components inside via
vent openings at the rear and bottom surfaces.

Scope of work document

Page 57

Confidential
 Confidential

BR4.13.1.5 Flexibility:
(k) The Kiosk profile shall be customizable.
(l) The Kiosk profile shall be expandable for allowing adding any options
ACSA would like to have in the future.
BR4.13.1.6 Modularity: The Kiosk is based on modular components, such as standard off-the-
shelf PCs, printers, readers.
BR4.13.1.7 Serviceability: The Kiosks are designed to allow for easy maintenance and
troubleshooting. The internal components of the Kiosk are accessible via pull-out shelves. The
shelves are made of durable metal with rollers and will be subjected to the following operating
environment:
(m) Environment: Indoor, temperature controlled.
(n) Temperature Range: 10-32 degrees Celsius.
(o) Relative Humidity: 20%-80%, no condensation.
(p) Power: 230v/50Hz.
BR4.14 BR4.14.1 CUSS Servers and Core Equipment:
(q) Clustered, fully redundant CUSS Management Application Servers.
(r) Airline Routers if required.
(s) Connectivity to Airports CUSS VLAN

BR4.15 BR4.15.1 CUSS Management Workstation:

BR4.15.1.1 Workstation hardware specification shall meet or exceed the minimum
requirements needed for the full 5-year service level agreement.

Scope of work document

Page 58

Confidential
 Confidential

BR4.16 BR4.16.1 CUSS Kiosk Configurations: The following requirements are the minimum Kiosk
configuration:
BR4.16.1.1 Integrated Kiosk Enclosure.
BR4.16.1.2 PC.

BR4.16.1.3 Wireless network Card (802.11b/g/n).

BR4.16.1.4 A keyboard with integrated Track-Point device shall be stored inside the Kiosk.

BR4.16.1.5 UPS

BR4.16.1.6 CUSS LCD/touch screen:

(a) 17’’ in /43 cm SAW touch overlay.
(b) The touch screen shall be gasket to minimize the effect of dust built-up that may affect
performance.
(c) The touch screen shall be calibrated before delivery.
(d) The screen shall be equipped with digital push-button control panel for providing
adjustments of the screen contrasts, brightness, and display size.

BR4.16.1.7 CUSS Card Reader:

(e) Multi-format card reader; capable of reading ISO tracks 1, 2 & 3
(f) Reading 3 track credit card information, ISO 7811/2-6
(g) Support for different smart card applications i.e., electronic payment, and electronic
signature
(h) Support PC/SC standard, ISO 7816, and CT-API
(i) Accepting the following: magnetic cards, such as Credit cards, smart cards, frequent
flyer cards, employee travel cards
(j) Read the following card formats: ISO 7810, ISO 7811, ISO 7812, ISO 7813
(k) Read JIS-II formatted cards.
BR4.16.1.8 CUSS Kiosk Passport Reader:
(l) The Passport Reader shall be equipped with extended input tray to facilitate self-
service operation. Read OCR A as per ISO 1073/I.
(m) Read OCR B as per ISO 1073/2.
(n) OCR read rate > 95%.
(o) Compliant with ICAO 9303:

Scope of work document

Page 59

Confidential
 Confidential

(p) Accepting: Passports, ID cards.

(q) Accept Bi-directional swipe.
(r) The minimum lines of OCR text supported must be at least 3.
(s) The minimum characters per line of OCR text must be 45.
(t) Support functionality to flag “unreadable” or “ambiguous” characters.
(u) Support more than 3 lines of text.
(v) Support more than 45 characters per line of text.
BR4.16.1.9 CUSS Kiosk Full page document scanner
(w) Automatically recognize passport and ID cards according to ICAO 9303
(x) The device shall have integrated processor with quad optics.
(y) The device shall be fast, reliable easy to use and shall not contain any moving
components based on LED technology.
(z) UV illumination
(aa) Include visible and audible indicators.
(bb) Resolution 400 dpi
BR4.16.1.10 CUSS Kiosk Bar Code Reader
(a) Flatbed barcode scanning.
1) Reads BCBP with 2 Dimensional Symbols (2-D) PDF417 bar codes

2) Reads documents (tickets / bag-tags) with 1 dimensional (1-D) barcodes

(code128.code39, Industrial 2 of 5)

3) Read Mobile Phone 2D (e-BCBP) barcodes (Aztec, EAN13, Datamatrix)

(b) Scan rate shall be at least 35/second.

(c) Omni-directional scanning and decoding without any moving parts and utilize LED
based illumination.
BR4.16.1.11 CUSS Kiosk Amplifier / Speakers:
(d) The audio output from the PC shall be connected to a stereo amplifier that drives
two (2) 1.5-watt speakers mounted on the inside of the format of the kiosk.
(e) Volume control is achieved through settings in the system software.
BR4.16.1.12 CUSS Kiosk Boarding Pass Printer (BPP) / General Purpose Printer (GPP):
(f) Capable of printing a document on boarding pass size stock as well as many paper
formats including thin ATB that prints in “wide carriage” format on 9inch diameter
rolls.

Scope of work document

Page 60

Confidential
 Confidential

(g) Capable of printing Boarding Pass and Bag Tag documents compliant with IATA
PDF 417, Aztec, QR code, Datamatrix, and fully compliant with IATA specifications.
(h) Capable of printing high quality 1D/2D barcodes.
(i) Modular design uses Direct Thermal Technology with low operating, and
maintenance cost.
(j) The Printer shall be connected to the CUSS workstation through the USB and shall
have the option to connect using the RS232 or directly to the IP network.
(k) Print resolution requirements must be sufficient to conform to the IATA’s Barcoded
Boarding Pass and Bag Tag (BCBP) standard at least 203 dots/inch.
(l) Minimum 5 inches/second (132 mm/second) to create the boarding pass/bag tag
document.
(m) The BPP shall have an on-board display(s) or indicator light(s) showing printer
status, stock fill status.
(n) Compliant with FCC, CE, UL.

BR4.16.1.13 CUSS Kiosk Baggage Tag Printers (BTP):

(o) Capable of printing a document on bag tag size stock.
(p) Capable of printing high quality 1D/2D barcodes.
(q) Including integrated RFID module.
(r)Compliant with IATA 1740C for high-speed RFID encoding.
(s) Modular design uses Direct Thermal Technology with low operating, and
maintenance cost.
(t) The Printer shall be connected to the CUSS workstation through the USB and shall
have the option to connect using the RS232 or directly to the IP network.
(u) Minimum 5 inches/second (132 mm/second) to create the boarding pass/bag tag
document.
(v) Compliant with FCC, CE, UL.

BR4.16.1.14 CUSS Kiosk Input Sensors:

(w) The kiosk shall have the following internal sensors to monitor:
1) Door position status

2) Door-lock status

Scope of work document

Page 61

Confidential
 Confidential

3) Coupon in output area

4) Diagnostics switch requests

5) Low paper status

6) Paper out status

(x) These sensors shall be connected to an I/O controller.

(y) The I/O controller connects to a port of the PC.

Table 7: Technical Specification (CUSS Kiosk)

Scope of work document

Page 62

Confidential
 Confidential

BR5 WAN SPECIFICATION

BR5.1 BR5.1.1 Included in the supply, the Bidder shall provide all labour, Materials, Service
Provider’s Equipment and Plant to fully execute the requirements to furnish, deliver, and install
the WAN connectivity in accordance with the Contract (the tender contract conditions).

BR5.1.2 It is the intent of this Specification section that the work performed pursuant hereto
be complete and acceptable in every respect for its intended purpose. It is further required
that the provisions of this Specification section shall be complementary to, and shall be
correlated with, the requirements of the Contract. Nothing in this Specification section shall
limit the scope of work as required by the Contract.

BR5.1.3 The project entails the replacement of the CUPPS and CUSS systems at OR Tambo
International Airport, Cape Town International Airport, King Shaka International Airport and
Port Elizabeth Airport. It also includes the implementation of CUPPS and CUSS systems at
George Airport, East London Airport, Bram Fischer Airport, Kimberley Airport and Upington
Airport.

BR5.1.4 The scope of works for the CUPPS and CUSS WAN are for the connectivity of the
CUPPS and CUSS cloud site to the main hub sites and in turn connectivity to the satellite
sites via the main hub sites.

BR5.1.5 Integration from the airline Departure Control Systems (DCS) hosts into the CUPPS
and CUSS cloud is also a requirement.

BR5.1.6 The Bidder shall propose a fully redundant, resilient, and secure WAN solution. The
Bidder shall provide a WAN solution inclusive of the supply of all required equipment and
materials, labour, system configuration and integration with interfaced systems, testing,
commissioning, site acceptance test documentation, as built documentation, hand over
documentation, project management, planning management and maintenance.

BR5.1.7 The current ACSA LAN/WAN equipment is Cisco, and it will be advisable to utilise
equipment that is the same or compatible.

BR5.1.8 If the Bidder does not mention in the proposal any issues preventing the completing
of the work as per specifications and drawings, it will be implicitly understood, for both parties,

Scope of work document

Page 63

Confidential
 Confidential

that the Bidder has included the cost of overcoming these issues within his proposal.

BR5.2 BR5.2.1 CUPPS and CUSS Cloud Connectivity

BR5.2.1.1 The Bidder will have a CUPPS and CUSS cloud site and provide connectivity to the
allocated airports in South Africa.

BR5.2.1.2 The supported airlines will provide redundant links from their Departure Control
Systems (DCS) hosts to the Service Providers CUPPS and CUSS cloud ensuring that the
links have sufficient bandwidth so as not to inhibit their services at the airports.

BR5.2.1.3 The CUPPS and CUSS cloud site will provide connectivity to the three main hub
sites located at OR Tambo International Airport, Cape Town International Airport and King
Shaka International Airport. The connectivity to the three main hub sites will be via a fully
redundant WAN solution to prevent any disruptions to the airlines’ connectivity and operations.
Different Telco providers are to be utilised for the redundant links from the CUPPS and CUSS
cloud to each HUB site to ensure a fully redundant solution.

BR5.2.1.4 The CUPPS and CUSS cloud will provide connectivity to the six satellite airports
(George Airport, East London Airport, Bram Fischer Airport, Kimberley Airport & Upington
Airport) via the three hub sites utilising the redundant WAN links.

BR5.2.1.5 This may be achieved with the utilisation of a MPLS WAN provided by one of the
major providers in South Africa.

BR5.5.1.6 HUB SITE Connectivity: The three main hub sites located at OR Tambo
International Airport, Cape Town International Airport and King Shaka International Airport will
be connected to the CUPPS and CUSS cloud site via a fully redundant WAN solution as
depicted in the high-level WAN connectivity requirements diagram (Table 8: below).

Scope of work document

Page 64

Confidential
 Confidential

High Level Design for CUTE & CUSS

WAN Connectivity Requirement
Airlines DCS Host

CUTE & CUSS Cloud

Telco A Telco B Telco A Telco B Telco A Telco B

King Shaka OR Tambo Cap e Town
International Airport International Airport International Airport

Telco A Telco B Telco A Telco B Telco A Telco B Telco A Telco B Telco A Telco B Telco A Telco B

Port Elizabeth Airport East London Airport Bram Fischer Airport George Airport Kimberley Airport Upington Airport

CUTE Work CUTE Work CUTE Work

Station CUSS Kiosk CUSS Kiosk CUSS Kiosk
Station Station
Boarding Gates Check-in LPO

Table 8: WAN Spec

Scope of work document

Page 65

Confidential
 Confidential

BR6 IT INFRASTRUCTURE REQUIREMENTS

Bidders are required to provide a full BOQ and Pricing for all the below infrastructure. At
contracting stage, ACSA will decide if the infrastructure is bought by the bidder or ACSA.
This BOQ and Pricing must form part of the total cost of Acquisition.

BR6.1 BR6.1.1 Number of network points required workstation to be specified by Service Provider
BR6.1.2 WIFI connectivity is require as a backup to physical LAN cabling, Bidder to indicate
how the workstation will be configured for WIFI
BR6.2 BR6.4.1 Bidder to state what server configuration is required for the CUPPS & CUSS solution
as these need to be accommodated in the Data Centre (ACSA will deploy virtual server
infrastructure)
BR6.4.2 The stated server configuration that the CUPPS solution requires should include but
not limited to server specifications, gateways specifications, routers and switches
specifications, and any associated software required to operate and manage efficiently. The
specified server configuration should be so selected to operate the full 5 years without a need
for any upgrade or degradation of service.

BR6.3 BR6.5.1 Bidder to state the server storage requirement, RAID configuration and setup if
required
BR6.4 BR6.6.1 Bidder to state backup strategy (what must be backed up, frequency and retention
period)
BR6.5 BR6.7.1 Bidder to give details pertaining to the data access security, noting that data security
mechanism used, needs to be top-end due to the sensitivity of the data that is captured
BR6.6 BR6.8.1 Bidder to specify any other IT specific requirements not listed above which is a pre-
requisite for deployment of a functional solution.
Table 98: IT Infrastructure Requirements

Scope of work document

Page 66

Confidential
 Confidential

BR7 TESTING AND TRAINING

BR7.1 BR7.1.1 Unit Testing of installed equipment is the responsibility of the Bidder to ensure all
components and modules that make up the CUPPS & CUSS solution can function both as single
units and as combined units forming the end-to-end solution
BR7.2 BR7.2.1 System Integration Testing of installed equipment with its associated software

BR7.3 BR7.3.1 Integration Testing between the installed CUPPS & CUSS solution and other systems
(e.g., BRS)
BR7.3.2 Integration Testing between the installed CUPPS and FIDS/VIEW DIRECT system for
purposes of displaying flight data, however, should a new FIDS system be commissioned, the
new solution should integrate to CUPPS.
BR7.4 BR7.4.1 User Acceptance Testing: Airlines and Handlers are the primary users of the end
solution and will, together with ACSA resources approve and sign-off the success of UAT
BR7.5 BR7.5.1 Training of airlines & handlers’ staff and other stakeholders who will be end-
users/process owners of the CUPPS & CUSS solution.
BR7.6 BR7.6.1 Run the project with ACSA, Airlines and any other involved stakeholders ensuring all
issues and glitches are resolved, post-implementation support is provided
Table 10: Testing and Training

Scope of work document

Page 67

Confidential
 Confidential

BR8 IMPLEMENTATION

BR 8.1 Implementation
BR8.1.1 Bidder to provide an overview of the proposed equipment.
BR8.1.2 The Bidder to provide recommendations that must be in place prior to deployment, and
this information will need to be updated with actual results upon completion of the installation.
BR8.1.3 Bidder to provide ‘before and after’ pictorial design of the CUPPS & CUSS solution, the
envisaged changes that will be made and the impact thereof on the end solution to implement
these during the national rollout.
BR8.1.4 Number of tests performed at identical conditions to the project and repeatability /
variance of test results.
BR8.1.5 Conditions / parameters that will remain the same as those that will prevail during the
national rollout of the full CUPPS & CUSS solution. e.g., voltage required to ‘power-up’
equipment.
BR8.1.6 Conditions / parameters that will be different from those that will prevail during the
national rollout of the full CUPPS & CUSS solution. e.g., number of passengers processed,
length of time equipment is used.
BR8.1.7 Bidder to indicate if there are simulation tools that predict the performance of the
proposed solution.
BR8.1.8 Bidder to provide proposed design margin / differences based upon studies and / or best
practice.
BR8.2 Commercial Design & Operation considerations
BR8.2.1 Bidder to provide typical scale-up strategy including providing a case-study that takes
one through the steps of how CUPPS & CUSS solution was designed, data accumulation,
experimental tests, construction, commissioning, full operation, and information on design vs
actual capacity.
BR8.2.2 Bidder to present value engineering opportunities i.e., how can the expected operating
capacity be expanded through optimization and / or minor capital expenditure.
BR8.2.3 Bidder to detail out quality & process control philosophy for the CUPPS & CUSS process
(instruments such as spec sheets, periodic testing of equipment, quality control measures,
adherence to SLA’s, etc.)
BR8.3 Technology Transfer Issues
BR8.3.1 Bidder to provide information on what is the nature of the guarantee / warranty with a
focus on: (process, equipment, operating life)

Scope of work document

Page 68

Confidential
 Confidential

BR8.3.2 Bidder to provide information on what process simulations / predictive tools the CUPPS
& CUSS solution provides for optimization / trouble shooting purposes.
BR8.3.3 Bidder to give clear description to ACSA on what intellectual property rights accrue to
ACSA and / or Bidder both during and after implementation through the entire life cycle of the
equipment.
BR8.3.4 Bidder to provide duration and conditions for the reliability test, this should cover at a
minimum one maintenance cycle (testing the operating variability over a typical maintenance
cycle)
BR8.3.5 Bidder to conduct factory acceptance testing and provide detailed tests with duly
authorized signoffs
BR8.4 Maintenance and Asset Management
BR8.4.1 Bidder to provide maintenance cost curve over the life of the equipment (1 and 5-year
comparison)
BR8.4.2 Bidder to detail out what specialized training and development for maintenance staff &
refresher programs do they offer, i.e., train IT Service Desk or first line support.
BR8.4.3 Bidder to provide list of critical spares to be kept on site & costs there-of
BR8.4.4 Bidder to present top 5 recurring challenges / issues experience on the solution.
BR8.4.5 Bidder to provide List of approved Service Providers for the technology
components/parts.
BR8.4.6 Bidder to share their prescribed staffing plan for maintenance and operation
BR8.5 Similarities and Differences with the ACSA Application
BR8.5.1 Bidder to state how their proposed CUPPS & CUSS solution vary with other solutions
already implemented.
BR8.5.2 Bidder to provide later during the running of the project, Interpretation of the test work to
date (expected results vs reality) and how this manifest in the design.
BR8.5.3 Bidder to provide information on typical major uncertainties that exist & need to be
further explored during the implementation and running of the project.
BR8.5.4 What are anticipated process conditions for the ACSA implementation.
Table 11: Implementation

Scope of work document

Page 69

Confidential
 Confidential

3.2 OUT OF SCOPE

The following is out of scope for the Service Provider, but in scope for the project, as ACSA will ensure that
this is delivered through an independent consultant as a dependency on this project.

• Enabling work required to accommodate the CUPPS & CUSS installation, i.e., electrical, lighting, power,
etc.

• Associated IT Infrastructure (networks, core rooms, wire centres, telephony) is a dependency for this
project and ACSA IT will provide for such requirements.

• The areas where the CUPPS & CUSS solution will be installed, need to be redesigned to allow for
streamlined passenger queues, passenger processing, placing of airlines service agents & handlers to
process passengers, manage exceptions, etc. There will thus be a need for an Architect(s) that ACSA
will provide to redesign the affected areas and submit plans to municipality where necessary.

• The CUPPS & CUSS equipment that will be installed may need power supply and route for the power
cabling to be redesigned, the equipment might require essential power or external UPS. There will thus
be a need for an Electrical Engineer to assist with documenting all the electrical requirements and
giving expert advice, and ACSA will provide for such resource.

• There may be a need for drilling to create network routes, power cable routes, fix the equipment to the
floor and these tasks may have structural impact.
There will thus be a need for a Structural Engineer to assess this impact and give expert advice, ACSA
to provide such a resource.

• Mechanical Engineers and Quantity Surveyors may be required, and ACSA will provide for such a
resource

• There will be a need for doing some level of building alterations, removing old counters, installing new
counters, remove old equipment, breaking down of walls where needed, carpentry, painting, ceiling
adjustments, lighting, remove rubble, clean-up, building barriers to control queues, etc.

There will thus be a need for Building and Maintenance, Architectural Services resource well-versed
in carrying out such alterations to prepare the area both before and after the CUPPS & CUSS equipment
has been installed, ACSA to provide such resources.
Scope of work document

Page 70

Confidential
 Confidential

• Quality assurance and Quality Control will be needed to ensure that all the tasks have been carried out
following ACSA standards and not compromising quality. There will be a need for a construction /
engineering Project Manager to oversee all the tasks as specified in BR10.1 – BR10.5 above. ACSA
will provide for such resources.

Scope of work document

Page 71

Confidential
 Confidential

Scope of work document

Page 72

Confidential