
AIMS Attachment A: AIMS Statement of Work
Page 67 of 130
3.4.10 EVIDS Hardware Requirements
A. In addition to the requirements specified herein, the EVIDS shall meet the
requirements of Section 3.9, Hardware Requirements.
B. Refer to drawings for hardware types and quantities.
C. In addition to the components depicted on the drawings, provide twenty-
nine (29) workstations for airlines to utilize as their input workstations.
The location of these workstations shall be coordinated with the County.
3.5 DYNAMIC ASSIGNMENT PASSENGER PROCESSING (DAPP)- The
Contractor shall comply with the requirements set forth in this Section
3.5.
3.5.1 System Requirements
A. The design philosophy behind Terminal 4 is to establish a flexible
environment allowing any mix of dedicated and/or shared use peripherals.
This environment must be sufficiently flexible and scalable to
accommodate changes in the airport‟s business plan over time. To
facilitate shared use peripheral deployment at some point, a DAPP
solution shall be provided as part of the AIMS base bid.
B. The DAPP shall be a flexible solution that provides all airlines the ability to
access their applications via native host connections facilitated through
the system. This connection is facilitated using a shared infrastructure
with dedicated virtual network connections for each airline tenant. The
dedicated virtual network connections along with airline provided software
that is accessible at the local DAPP workstation shall allow an airline to
access their native host interface. The virtual network connections, while
dedicated for each airline, shall be dynamic such that any port on the
network shall be able to utilize any of the virtual network connections
associated with the DAPP.
C. The DAPP shall be integrated with the RMS and other necessary
components to support the following functionality:
1. The RMS shall control and provide all resource allocations for specific
users. The DAPP shall fully support the schedule of resources
developed by the RMS. As such, when the RMS has assigned a
resource to a specific user, the applications and functionality required
by the assigned user shall be available on the assigned resource during
time slot allotted by the RMS. Conversely, if the RMS has not assigned
a specific user to a resource, the resource and all applications and
functions shall not accessible to that user.
Exhibit 3
Page 127 of 278
Kommentare zu diesen Handbüchern