CITY AND COUNTY OF SAN FRANCISCO

AIRPORT COMMISSION

REQUEST FOR PROPOSALS

Contract No. 11211.83

TERMINAL MANAGEMENT SYSTEM UPGRADE

San Francisco International Airport

Date Issued: May 26, 2017

Addendum 1: June 2, 2017
Addendum 2: June 29, 2017
Addendum 3: July 11, 2017
Proposals due: July 25, 2017 – 3:00 PM
RFP 11211.83: ADDENDUM NO. 3

This Addendum is being issued to modify the above-referenced Request for Proposal (RFP) and
provide the Question and Answer responses. Please review the terms of the RFP and all Addenda
carefully. If there are any inconsistencies between the RFP and the terms of any Addenda, then the
terms of this Addendum shall prevail. Section references below are to the RFP and are provided
for convenience of reference only, and are not necessarily correct or complete.

Modifications to RFP

1. The Table of Contents, Exhibits is hereby amended to add Exhibit J, AIIS RFP Technical
Specifications.

2. RFP Section III. Submission Requirements, C. Content, a. Technical Proposal,

Section 7. Technical Approach, c. Proposed Edge Device Hardware, is amended to remove
‘CUSS kiosks’ from the list of proposed edge devise hardware products.

3. Exhibit D – Agreement for Professional Services, Article 11 Software Requirements,

11.9.3 Maintenance Services is replaced in its entirety with the following:

“Contractor will provide maintenance services for the project in accordance with the
maintenance requirements outlined in this agreement. Such services shall commence
at the determination of the City.”

4. Exhibit D – Agreement for Professional Services, Article 12 General Provisions, 12.3.1

is replaced in its entirety with the following:

“All applicable applications shall be compliant with the Payment Application Data
Security Standard (PA-DSS) and validated by a Payment Application Qualified
Security Assessor (PA-QSA). A Contractor whose application has achieved PA-
DSS certification must then be listed on the PCI Council’s list of PA-DSS approved
and validated payment applications.”

5. Exhibit D – Agreement for Professional Services, Article 12 General Provisions, 12.3.4

is hereby updated to correct the references from “11.3.1” and “11.3.3” to “12.3.1” and “12.3.3”
respectively.

6. Exhibit E – Passenger Processing System Specification Document, Section 1

Introduction, 1.3 Project Expansion is replaced in its entirety with the following:

1. This procurement incorporates implementation activities primarily in the ITB but includes
priced options for expansion services.
2. This project focuses on the ITB and replacing the existing systems. A few locations in the
other terminals that are supported by these systems today are also included. SUS Hardware
and CUSS kiosks in the ITB were recently upgraded. The scope of this project includes
implementing new server hardware, COTS software and all application software associated
 with the systems in the ITB. Software licenses will be enterprise wide and perpetual. The
end user devices, and peripherals in the ITB will be reused. Except for CUSS kiosks units,
the Contractor will need to provide only enough hardware to ensure adequate sparing for
existing locations operations and maintenance.
3. Following successful implementation in the ITB, it is anticipated systems will be expanded
to include all Airport terminal buildings, subject to a schedule to be developed by SFO
management. Later implementations will include T1, which is currently undergoing
renovation. The extent of shared use in T1 is still being determined, but the following
scope will be included:
a. a portion of the check-in area and the gates will use the shared use passenger
processing technology; and
b. AODB and RMS will be expanded to include the management of all shared use
resources in T1.
4. The contractor will provide optional unit pricing to support new hardware and its
implementation throughout the airport. No additional application software licensing fees
will be required.

7. Exhibit E – Passenger Processing System Specification Document, Section 5 Existing

Conditions, 5.5 Baggage Handling System (BHS) is replaced in its entirety with the following:

The current installation of BagLink supports the bi-directional flow of various types
of baggage messages, including but not limited to BSM, BPM, BTM, etc. The
baggage messages are received from the airline host systems via Upline client
connections into BagLink. This supports the receipt of BSMs from the hosts via
several different protocols. The messages are then filtered and forwarded to several
Downline clients including, but not limited to the Brock BHS and BRS systems.
These systems in turn generate BPMs which are received by BagLink and
forwarded on to the appropriate Upline systems, including the airline hosts.

8. Exhibit E – Passenger Processing System Specification Document, Section 7 New

Hardware Specifications, 7.3 CUSS Kiosks is hereby removed in its entirety.

9. Exhibit E – Passenger Processing System Specification Document, Section 6 PPS

Applications Architecture, 6.5.3 Data Exchange Requirements, Table 3 is replaced in its
entirety with the following:

Sending Receiving Data Integration

System System Methodology
AODB IDS Updated Flight Information AIIS
IDS Updated Resource Allocations AIIS
BRS Updated Flight Information AIIS
BRS Updated Resource Allocations
BHS Updated Flight Information AIIS
BHS Updated Resource Allocations AIIS
BICS Updated Resource Allocations AIIS
 Shared Use Updated Resource Allocations AIIS
RMS Updated Flight Information Direct
RMS Seasonal Flight Schedule Direct
RMS Static reference data updates Direct
A-VDGS Aircraft reference data and Direct
gate assignment information
Airport Updated Flight and resource AIIS
Website allocation data
Billing Resource Usage Statistics AIIS
System
Data Updated Flight and resource AIIS
Warehouseallocation data
RMS AODB Updated resource allocations Direct
AODB Seasonal Resource Direct
Allocations
AODB Resource Reference data Direct
updates
CCTV Gate ID for camera display AIIS
Shared Use 15-minute warning for AIIS
resource expiration, log off
indicator
Shared Use Avaya Airline ID AIIS
System VoIP
System
IDS Airline ID for back wall AIIS
display
BHS BSMs Direct
Airline BSMs Direct
Hosts
Airline Passenger processing data Direct
Hosts (airline dependent)
RMS Resource logon/logoff AIIS
indicator
CUSS Kiosks Airline Passengers processing data Direct
Hosts (airline dependent)
BIC AODB First bag/last bag on AIIS
BHS and BRS Airline BPM's AIIS or Direct to Bag
Hosts Message System

Airline Host AODB Real time flight updates Direct

Systems
 IDS Airline specific GIDS data Direct
(upgrade lists/standby
lists/weather at destination)
Shared Use Passenger Processing Data Direct
System (airline dependent)
Third Party AODB Real time flight updates Direct
Flight Data
Sources
Public Address IDS Paging Info for visual display AIIS

Websites IDS HTML5 data feeds, maps, AIIS

weather and advertising
content
A-VDGS AODB Actual arrival/departure times AIIS
Mapping IDS Map display data AIIS
Application
(e.g.
Jibestream,
GIS)
Ground IDS Bus and Train schedules, AIIS
Transportation pickup times
Feeds (e.g.
AVI,
Bombardier,
Uber, Lyft)
Queue IDS Queue wait times AIIS
Management
System

10. Exhibit E – Passenger Processing System Specification Document, Section 8 Security

Requirements, 8.3 PCS-DSS Security, 8.3.2 is replaced in its entirety with the following:

PCI security requirements must be evaluated by the Contractor throughout the life
of the contract.

11. Exhibit E – Passenger Process System Specification Document, Section 11 Functional

Requirements, 11.4 CUSS Kiosk is renamed 11.4 CUSS Kiosk Software and is replaced in its
entirety with the following:
11.4 CUSS Kiosk Software
11.4.1 CUSS KIOSK Software Overview
SFO wishes to upgrade the existing CUSS Kiosk software platform in the ITB and
reuse the existing hardware. During the contract, the Contractor will install its
software platform in their proposed server hosting environment and replace software
in the existing kiosks in the ITB. All kiosks will support bag tag printers for self-
tagging luggage.

The configurations of any existing or new CUSS kiosks shall be coordinated with the
SFO Project Manager during requirements validation.

The Airport anticipates expansion of the SFO CUSS Kiosk system. Future
configurations may include expanding or relocating the kiosks deployed in the initial
contract. In addition, new kiosk locations may be configured in areas such as:
1. T1, T2 and T3;
2. the rental car return facility;
3. the parking garages; and
4. Hotels.

11.4.2 Self Service Application Requirements

1. The solution offered by the contractor shall be capable of utilizing multiple technical
means on the same platform to run airline self-service applications. SFO wishes to
provide three technical options to Airlines who wish to utilize the CUSS Kiosks. Those
options are listed below. All other CUSS kiosk requirements, unless specifically noted,
apply to all three options listed.

a. The Common Use Kiosks applications installed by the Contractor shall support
CUSS applications which adhere to:
i. IATA CUSS RP 1706c and the latest version of the IATA CUSS
Implementation Guide; and
ii. IATA CUSS Technical Specification (TS) Version 1.3.
b. The Common Use Kiosks shall support airline web applications through a common
browser interface. The browser interface must be capable of passenger document
check, printing passenger bag tags and boarding passes, along with processing
credit card transactions for each individual carrier (along with supporting other
requirements listed in section 11.4.2).
c. The Common Use Kiosks shall support a single, native web application which is
common to all carriers, and provides an open API through a hosted middleware
platform, to carrier departure control systems.
i. The front end user interface of this application shall be the same
functionally for all carriers utilizing this methodology of connectivity. It
shall support carrier specific branding, however the functions and layout of
the screen shall remain the same between carriers utilizing this option for
deployment.
ii. The middleware must be capable of retrieving a flight manifest for a given
flight, passenger booking via PNR and/or passenger name, perform
 passenger document check, perform a check in, issue a boarding pass, issue
a bag tag, retrieve a seat map for a given flight and assign/change the seat,
assign baggage to a passenger and update a passenger booking.

11.4.3 CUSS Kiosk Software Requirements

1. Kiosks shall support all SFO tenant airlines through one of the above technical
means.
2. Each Kiosk shall include the following functionality:
a. General splash screen during start-up and initialization.
b. A common launch application that runs all airline self-service applications.
c. Ability to email configured administrators due to platform or application errors.
d. Software Support for a variety of peripherals, including
i. general purpose printer for boarding passes;
ii. magnetic card reader;
iii. touch screen display;
iv. bar code reader;
v. passport reader; and
vi. bag tag printer
vii. NFC Sensor
viii. Facial Recognition Camera/sensor
e. Kiosks software shall be capable of printing bag tags for self-tagging based on
each airline’s ability to support the functionality. Kiosk software must also
support printing of RFID Bag Tags.
f. Kiosks software must be able to accept alternative digital forms of payment if
the airline applications support them. (e.g. credit cards, payment cards, Apple
Pay, etc.)
g. Near Field Communication (NFC) – Kiosks software will support NFC sensors
for airline apps that may use them for functions within their applications (e.g.
alternative payment methodologies)
h. Facial Recognition – Kiosks software will support a camera for future use (e.g.
passenger identification)
i. ADA Compliance – all Kiosk software will be ADA compliant
j. All Kiosk software must be PCI compliant
k. Kiosks software will provide administrative and user access and permissions
based upon login.
l. Kiosks shall be monitored and controlled by the PPS monitoring system
configured for reporting tamper and fault alerts, low stock, loss of
communication, loss of power and other faults that may impact service delivery.
m. Provide systems status refresh updates at least every 30 seconds.
n. Provide warning and error notifications via email, pager, or texting to one or
more users/support providers.
o. Error management will provide specific device status and troubleshooting
information.
p. The CUSS system shall service multiple airlines from the same kiosk without
rebooting.
11.4.4 CUSS Platform Software
1. CUSS Application Manager (CAM)
a. The CUSS kiosk software shall have a CAM which includes an Event Manager,
Environment & Component Repository, and Access Control.
b. The kiosk software in general and the CAM in particular must support all airline
chosen kiosk applications
c. The CAM must allow for the addition, deletion or suspension of specific airline
applications and associated icons and coordinate changes with the common
launch application.
d. The CAM will put the kiosk in Kiosk Not Available Mode when appropriate.

2. Common Launch Application

a. The Contractor must provide a common launch application. It must show the
common launch screen with all application providers' logos that have a kiosk
application registered on the kiosk and that are currently available and
selectable. The customer chooses the application provider's logo.

3. System Manager Interface (SMI)

a. The kiosk must have an SMI which enables authorized users to perform the
functions described under System Management.

4. System Management
a. System Management shall be performed on a computer with access to the CUSS
VLAN. User access must be protected by username and password, administered
by SFO.
b. The system shall allow kiosks to be organized into groups. The kiosks’ group
numbers would display in addition to the unique kiosk ID number on all reports
and screens.
c. The system shall provide warnings and error notifications via email when errors
occur. The kiosk software must have SNMP clients which can notify Contractor
Operations Center when:
i. the kiosk is low on paper;
ii. the kiosk cannot communicate with 3 or more airline hosts for more than
1 minute;
iii. the kiosk cannot communicate with one or two airline host for more than
15 minutes;
iv. the kiosk has restarted;
v. the kiosk is low on memory;
vi. the kiosk is low on hard disk space;
vii. the kiosk service door has been opened;
viii. excessive card reader errors (bad reads);
ix. excessive passport reader errors (bad reads);
x. a peripheral in the Kiosk is malfunctioning;
xi. the current airline application has held the focus of the Operating
System for more than 15 minutes;
xii. the UPS is on battery;
 xiii. the UPS is on commercial AC;
xiv. the UPS battery is low; and
xv. absence of regular SNMP messages.
d. All SNMP messages and operator actions shall be logged in an electronic file
on the system core, including SNMP errors and operator-initiated activity.
Every 15 minutes, the SNMP agent in each kiosk shall report a health and status
message which includes the name of the currently active application.
e. The system shall allow an authorized user to take the following actions to
remotely affect the kiosk:
i. activate a new kiosk;
ii. deactivate an operational kiosk and place it into an out-of-service mode;
iii. reactivate a kiosk which is in out-of-service mode;
iv. set kiosk date & time;
v. load new common kiosk software;
vi. load new airline kiosk applications;
vii. load new airline logos;
viii. reboot a kiosk (may use the UPS for this);
ix. suspend an application;
x. resume an application;
xi. test a specific component;
xii. specify which airline logos appear and where they appear on the screen;
xiii. specify which airline kiosk applications operate on which kiosks; and
xiv. view statistics, print reports and export to Excel the following
information:
1. usage by air carrier;
2. individual kiosk utilization by hour with average transaction time;
3. individual kiosk utilization by airline application with average
transaction time based on:
a. number of transactions;
b. % of active time
c. % of total time
d. # of documents (Boarding passes, receipts, itineraries) issued;
4. individual kiosk availability;
5. system activity logs;
6. disk use over time;
7. memory use over time;
8. # of card reads;
9. # of failed card reads;
10. # of passports swiped;
11. # of failed passport swipes; and
12. # of UPS switchovers.
5. Kiosk Not Available Mode
a. The kiosk shall have the ability to display an out-of-service indicator. The
indication shall be a screen with a different background and words to the effect
of “We Apologize, This Kiosk Is Temporarily Unavailable.” The message must
be configurable.
 b. The out-of-service mode must be initiated when one of the following occurs:
i. the thermal printer jams or is out of paper;
ii. there is no valid network path;
iii. one or more of the peripherals is not responding; and
iv. the kiosk is instructed to enter the mode via SMTP command from an
authorized administrator.

11.4.5 CUSS Kiosk Interface Requirements

1. The CUSS kiosk software will interface directly with airline hosts for
passenger processing data.
2. The CUSS kiosk software will have a messaging capability to send BSM’s
created by the CUSS kiosk software directly to the airline hosts and the
BHS to facilitate baggage handling and routing.

12. Exhibit E – Passenger Processing System Specification Document, Section 12

Appendices, 12.2 Appendix B is amended to remove ‘Combo Printers’ from the table.

13. Exhibit E – Passenger Processing System Specification Document, Section. 12.5

Appendix D, PPS Interface Architecture diagram is replaced in its entirety with the following:
 14. Exhibit F – Passenger Processing Scope of Work, Section 1 Introduction, 1.3 Project
Expansion is replaced in its entirety with the following:

1. This procurement incorporates implementation activities primarily in the ITB but includes
priced options for expansion services.
2. This project focuses on the ITB and replacing the existing systems. A few locations in the
other terminals that are supported by these systems today are also included. SUS Hardware
and CUSS kiosks in the ITB were recently upgraded. The scope of this project includes
implementing new server hardware, COTS software and all application software associated
with the systems in the ITB. Software licenses will be enterprise wide and perpetual. The
end user devices, and peripherals in the ITB will be reused. Except for CUSS kiosks units,
the Contractor will need to provide only enough hardware to ensure adequate sparing for
the ITB operations and maintenance.
3. Following successful implementation in the ITB, it is anticipated systems will be expanded
to include all terminal buildings, subject to a schedule to be developed by SFO
management. Later implementations will include T1, which is currently undergoing
renovation. The extent of shared use in T1 is still being determined, but the following
scope will be included:
a. a portion of the check-in area and the gates will use the shared use passenger processing
technology;
b. AODB and RMS will be expanded to include the management of all shared use
resources in T1; and
4. The contractor will provide optional unit pricing to support new hardware and its
implementation throughout the Airport. No additional application software licensing fees
will be required.

15. Exhibit F – Passenger Processing Scope of Work, Section 4 Roles and Responsibilities,
Table Project Lifecycle Roles and Responsibilities is replaced in its entirety with the following:

ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
Owns all existing and
subsequent purchases of
X
hardware and software
licenses
HARDWARE PROCUREMENT
All server hardware for all
X
applications
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
Existing shared use WS and
X
peripheral hardware
Existing and Future CUSS
X
Kiosk Hardware
Expansion Hardware for all
systems in new locations, X
except for CUSS kiosks
New User/admin workstations
X
for AODB/RMS
SOFTWARE PROCUREMENT X
Operating system, DBMS, VM
software, all required COTS X
software
Shared Use Platform software
X
(w/LDCS)
Self Service Kiosk Platform
X
Software
AODB Application Software X
RMS Application software X
Airline passenger processing
X
applications
Airline self-service kiosk
X
applications
Hosted middleware kiosk
X
application w/ API
IMPLEMENTATION
LAN provisioning and
X
maintenance
Internet Connection X
Airline Connections X X X
AIIS Integration X X
Space for Test lab, production
staging and training platform X
servers on premise
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
Space for 2 geo diverse
production server platforms X
on premise
Optional - Off premise hosting
X
facility
Space for training and test
X
facility
Space for storage and staging
of all equipment (new or X
reused)
Installation of all servers,
operating systems and VM X
software
Coordinates with airlines for
X
WAN connections
Shipping and delivery of any
X
new equipment
Staging and configuration of
X
all hardware (new and reused)
Asset tagging X
Implementation of
X
applications
Installation of any new
X
hardware, except CUSS kiosks
System testing X
User, Admin & Support
X
Training
Cleanup of Facility X
Transition planning X
System cutover X
Submittals X
OPERATIONS AND
MAINTENANCE
Support Functions
Answer help desk phone calls
24 hrs/day, receives problem X X
reports from users
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
Creates Trouble tickets X X
Tracks trouble tickets until
resolution (non-network X
related)
1st level maintenance- initial
problem triage, pulls and
replaces faulty hardware, calls X
vendor for 2nd level support if
problem unresolved
Preventative maintenance X
Keep operating system
software current to latest X
releases
Keeps application software
X
current to latest releases
Implements software
X
fixes/patches
Monitors all systems X X X
Receives alerts and event
notifications for all X X X X
applications
Runs statistics and reports for
X X
all apps
Views dashboards for PPS
X X X
applications
Asset management quarterly
X
reports/updates
Routine MACs of hardware X
Measures and reports Service
X
Levels monthly
2nd level maintenance -
trouble shooting all problems
X
not resolvable by 1st level
maintenance
Software warranty, fixes,
X
updates and maintenance
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
24x7 2nd level customer
X
support
Quarterly Service Level
X
Reports
On-going, on-site technical
X
resource
Hardware
warranty/maintenance for
X
new hardware, except CUSS
kiosks
Hardware
warranty/maintenance of X
reused hardware
Ordering replacement spares
X
for faulty(reused) equipment
Ordering replacement spares
X
for faulty(new) equipment
Fixes any airline WAN issues X
Fixes any airline host problems X
Keeps airline applications
X X
current
System Administration
Functions
PPS software change
X
management
PPS user access and account
X
management
Configuration Management of
X X
all hardware and software
Network
X
Management/Monitoring
Server Management
X X
Monitoring
Password administration X
Defines user roles and
X X
privileges
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
Administers user roles and
X
privileges
Reports operational issues to
X X X
Help Desk
SHARED USE SYSTEM
Facilitates Shared Use
operations at ticket counters X
and gates
Activates new ticket
X
counter/gate locations
Facilitates Shared Use
operations in airline back X
office
Adding/Removes airline
X
applications
Replace consumables stock at
ticket counters and gates, as X X
needed
CUSS Kiosks
Activates/Deactivates kiosk X
Configures groups of kiosks X
Configures splash screen,
X
add/delete logos
Adds/Removes airline
X
applications
Support passengers with kiosk
X
operations
Replaces consumable stock in
X X
kiosks
RMS
Facilitates RMS Ramp Tower
X
Operations
Facilitates RMS seasonal
X
resource scheduling
Adds/Changes/Deletes
X X
resources in RMS
Updates business rules in RMS X X
 ROLES AND RESPONSIBILITIES

PPS
PPS Tech SFO Terminal
SFO ITT AIRLINES Support GNOC
Contractor TECH Systems
Contractor
AODB
Facilitates AODB real time
operations- manual flight X
updates
Facilitates Seasonal Flight
X
Scheduling
Updates business rules of
X
AODB
Integrates AODB with new
X
applications and AIIS
Adds new interfaces/sources
X
of data

16. Exhibit F – Passenger Processing Scope of Work, Section 6 Discovery/System

Requirements Validation, 6.2 Shared Use System and CUSS Kiosks, 6.2.1 is replaced in its
entirety with the following:

6.2.1 Validate locations of existing shared use equipment and CUSS kiosks.

17. Exhibit F – Passenger Processing Scope of Work, Section 6 Discovery/System

Requirements Validation, 6.2 Shared Use System and CUSS Kiosks, 6.2.3 is hereby removed
in its entirety.

18. Exhibit F – Passenger Processing Scope of Work, Section 7 System Design, 7.1.7 is
hereby removed in its entirety.

19. Exhibit F – Passenger Processing Scope of Work, Section 9 System Installation and
Test, 9.3 Test Lab Environment Installation, 9.2.2.3 is hereby removed in its entirety.

20. Exhibit F – Passenger Processing Scope of Work, Section 14 Submittals and

Documentation, 14.3.25 has been removed in its entirety, and Section 14.4 Submittal Schedule,
Table 2 has been updated to remove the ‘Backup Copy of Source Code’ requirement from the
schedule.

21. Exhibit I – Pricing Form, Section Unit Pricing is amended to remove the first two items
from the table, “Pedestal Kiosks” and “Counter top Kiosks”. The remainder of the table remains
the same.
22. New Exhibit J – AIIS Technical Specification Diagram is hereby added to the RFP.

END OF CHANGES