
AIMS Attachment A: AIMS Statement of Work
Page 76 of 130
E. The LDCS implementation includes a minimum of ten (10) airlines. A per
additional airline cost beyond the base is provided in the Contract
Documents.
F. The LDCS shall interface with all DAPP peripheral devices including 2D
Bar Code Printer, BTP, document printer, MSR/OCR, and Bar Code
Scanner.
G. The LDCS shall maintain passenger status (e.g. boarded, not boarded) for
each departing flight and update it as passengers board.
H. The LDCS shall maintain data associated with a departing flight on-line for
a configurable period of time. The LDCS shall be sized to maintain data
for a minimum of twenty-four (24) hours for each departing flight.
I. Reports and queries shall be able to be generated at any point from the
time boarding is begun until the LDCS flight data is purged for that flight.
The CONTRACTOR shall provide a minimum of five (5) standard reports
for review and approval by the County. The LDCS shall provide the
following information (as a minimum):
1. Flight manifests
2. Flight closure report
3. An audit trail of errors encountered during the boarding process.
J. Any DAPP workstation shall have the ability to run the LDCS. These
workstations shall be fully functional DAPP workstations. A simple
pointing device or keyboard action shall allow the agent to switch between
the LDCS and any other available applications.
K. The LDCS shall include the following functionality as a minimum:
1. Ability generate, open, and close flights
2. Provide seat configurations for each aircraft type
3. Ability to add or cancel passengers
4. Ability to check-in a passenger and group of passengers
5. Ability to issue sequenced bag tag numbers and boarding passes
6. Provide positive bag to passenger matching
7. Record number of bags per passenger
8. Address single sector flights
9. Address single class
Exhibit 3
Page 136 of 278
Kommentare zu diesen Handbüchern