Unimark EC3000 Series Specifications

Exhibit 3
Page 1 of 278
SYSTEM AND SERVICES AGREEMENT
between
BROWARD COUNTY
and
AIR-TRANSPORT IT SERVICES, INC.
RFP No. 20070514-0-AV-01
This is a SYSTEM AND SERVICES AGREEMENT ("System Agreement"), made
and entered into by and between BROWARD COUNTY, a political subdivision of the
State of Florida, hereinafter referred to as "County,"
and
AIR-TRANSPORT IT SERVICES, INC., a Delaware corporation, authorized to do
business in the State of Florida, hereinafter referred to as "Contractor,"
WHEREAS, this System and Services Agreement ("System Agreement") and
the concurrent Software License and Maintenance Agreement ("License Agreement")
are the result of County’s Request for Proposal (RFP) process designated as Airport
Information Management System, RFP No. 20070514-0-AV-0, including all addenda
thereto; and
WHEREAS, Contractor has represented that it has application Software that
when used with other third party products and/or Goods provided by Contractor, as
identified in the Agreement, will provide County with an Airport Information Management
System. Contractor’s Software and the third party products and other Deliverables make
up the System, as defined below, and Contractor represents that its personnel or those
subcontracted by Contractor have the knowledge, proficiency and skills to provide (a)
the Services, including any programming/configuration Services needed to modify the
Licensed Software and/or establish interfaces between the Licensed Software and other
County entities, data processing programs and Software applications as may be
hereinafter described, (b) consulting and project management Services, (c) data
conversion, (d) training, mentoring and Documentation, (e) infrastructure and millwork
installation and (f) maintenance of the System, including, but without limitation, those
parts of the System not procured from and/or owned by Contractor; however, those
parts not procured from and/or owned by Contractor shall meet or exceed Contractor
recommendations/ specifications; and
WHEREAS, the parties understand that County may be directly acquiring from
other vendors Hardware, Software, and other items needed to configure, install and
otherwise establish the proper data processing environment needed by Contractor in
order for Contractor to furnish and provide the System; and
AIMS System and Services Agreement
Page 1 of 60
Exhibit 3
Page 2 of 278
WHEREAS, County is not acquiring the Goods, Services, Hardware, Software
and other equipment and products and entering into a license for the Contractor
Licensed Software as separate entities. Rather, Contractor acknowledges that County
is purchasing these items and licensing the Contractor provided Licensed Software to
operate as a whole with the items to be supplied by County and Contractor so that
together all items will provide County with the System in a multi-user environment, with
the interfaces with other County entities, data processing programs and Software
applications and that this is the essential purpose to be served by County's acquisition
of the System, Services and licensing from Contractor; and
WHEREAS, Resolution No. 95-937 of the Board of County Commissioners of
Broward County, Florida, relating to County’s Computer Software Policy, established a
requirement for inspection of all computer application Software systems purchased or
developed for Broward County by third parties costing over Twenty Thousand Dollars
($20,000.00) prior to its acceptance by County. Contractor recognizes that all computer
application Software purchased or licensed by Broward County from Contractor, and
without limiting the foregoing, in particular, the System acquired under the Agreement,
shall be inspected and tested by the County’s Office of Information Technology prior to
acceptance of the System. Also, all contracts for the purchase of computer application
Software costing more than Twenty Thousand Dollars ($20,000.00) shall include
clauses providing (i) for inspection and testing by the Office of Information Technology
of such computer application Software prior to formal acceptance of that Software by
Broward County, and (ii) that final payment shall not be made prior to formal acceptance
of the System by County. The Office of Information Technology will coordinate its
acceptance responsibilities with those of other County entities utilizing the standards for
acceptance set forth and described in the Agreement. The Office of Information
Technology’s failure to accept the System shall constitute non-acceptance by County.
In the event of such non-acceptance and only after full repayment by Contractor of any
and all monies paid by County to Contractor pursuant to the System Agreement and the
License Agreement, subject to third party claims against Contractor, County shall return
the Licensed Software, as hereinafter defined, Documentation and the Goods received
from Contractor and promptly remove the Licensed Software from any and all County
Hardware upon which the Licensed Software may reside. The parties also recognize
and agree that County's obligations under the System Agreement and the License
Agreement are specifically conditioned upon its accepting the System as set forth and
described in this System Agreement.
NOW, THEREFORE, IN CONSIDERATION of the mutual terms, conditions,
promises, covenants and payments which follow, County and Contractor agree to the
following:
AIMS System and Services Agreement
Page 2 of 60
Exhibit 3
Page 3 of 278
ARTICLE 1
PREAMBLE
1.1
Recitations. The foregoing recitations are true and correct and are hereby
incorporated into this System Agreement by this reference.
1.2
Funding. Contractor recognizes that funding for County requirements, including
the funding for monies to pay for the System and Services, is done on a budget
year basis, October 1 through September 30. Contractor further recognizes that
the Board of County Commissioners for Broward County is the authority which
establishes, allocates or otherwise provides for County's budget year funding. If
in any budget year, funding, for any reason, is not provided for any monetary
obligation hereunder, then such obligation may be terminated by County without
penalty.
ARTICLE 2
DEFINITIONS
2.1
Airport or FLL: means the Fort Lauderdale-Hollywood International Airport,
Broward County, Florida, as described in the Master Plan Update, including such
additional property that may be acquired to implement development as described
therein.
2.2
Agreement or Contract: Each reference herein to "Agreement" or "Contract"
means collectively this System Agreement, the concurrent License Agreement
and the Contract Documents. Any references in an exhibit attached hereto or in
the Contract Documents or in the License Agreement, to the "Agreement" or the
"Contract" shall be deemed to mean this System Agreement, the License
Agreement and the Contract Documents.
2.3
Aviation Department or BCAD:
means the Broward County Aviation
Department, or any successor agency.
2.4
Board or Commission: means the Board of County Commissioners of Broward
County, Florida, which is the governing body of the Broward County government
created by the Broward County Charter.
2.5
County Business Enterprise("CBE"): means a firm duly certified as a County
Business Enterprise by the County under criteria and eligibility requirements of
Broward County Ordinance No. 2009-40 (County Business Enterprise Act of
2009).
2.6
Consultant: means Convergent Strategies Consulting, Inc., its successors and
assigns, who are providing consulting services for this project.
AIMS System and Services Agreement
Page 3 of 60
Exhibit 3
Page 4 of 278
2.7
Contract Administrator: means the Director of the Broward County Aviation
Department, or his or her designee, pursuant to written delegation by the Director
of the Broward County Aviation Department, or some other employee expressly
designated as Contract Administrator in writing by the County Administrator. The
primary responsibilities of the Contract Administrator are to coordinate and
communicate with Contractor and to manage and supervise Services hereunder
and the other terms and conditions of this System Agreement. In the
administration of this System Agreement, as contrasted with matters of policy, all
parties may rely on the instructions or determinations made by the Contract
Administrator, provided, however, that such instructions and determinations do
not change the terms and provisions of this System Agreement. Amendments to
this System Agreement must comply with the Procurement Code (Chapter 21 of
the Broward County Administrative Code).
2.8
Contract Documents: means this System Agreement, the project manual
including drawings (plans) and specifications, the Request for Proposal (RFP)
designated as Airport Information Management System, RFP No. 20070514-0AV-0, all addenda thereto and Contractor's response thereto, the record of the
award, all Notices to Proceed under this System Agreement, all Work
Authorizations issued hereunder, all purchase orders, change orders, field
orders, supplemental instructions, all performance bond(s) and payment bond(s),
all Documentation, and all other documents the submission of which is required
by this System Agreement or any Contract Documents, and all exhibits to any of
the foregoing, all of which Contract Documents are expressly incorporated herein
by this reference.
2.9
Contractor: means Air-Transport IT Services, Inc., its approved successors and
assigns.
2.10
County: means Broward County, a body corporate and politic and a political
subdivision of the State of Florida.
2.11
County Administrator: means the administrative head of the County pursuant
to Sections 3.02 and 3.03 of the Broward County Charter.
2.12
County Attorney: means the chief legal counsel for County who directs and
supervises the Office of the County Attorney pursuant to Section 2.10 of the
Broward County Charter.
2.13
County Work Day: means Monday through Friday of each week, excluding
County holidays.
2.14
Critical Cut-over: means the point in the implementation where the MUFIDS
component is fully cut-over to the System, or when any of the FLL airlines are
using the DAPP component to perform any function associated with passenger
processing.
AIMS System and Services Agreement
Page 4 of 60
Exhibit 3
Page 5 of 278
2.15
Defects: means incorrect implementation or failure to conform to specifications
resulting in incompleteness, inadequacy, or imperfection. Defects will be logged,
prioritized and corrected in accordance with the definition of Event found below.
Defects identified during Preliminary Reviews, any testing steps and Final
Acceptance shall be corrected in accordance with the terms and conditions of
this System Agreement. Following Final Acceptance, Defects will be corrected in
accordance with the License Agreement.
2.16
Deliverables: means all Licensed Software, Third Party Software, Goods, and
Documentation to be delivered by and all items of Services to be performed for
and provided to County by Contractor under the Agreement.
2.17
Documentation: means such documentation as delivered by Contractor to
County and accepted by County at Final Acceptance of the System relating to
the use, function and support of the System, as may be amended from time to
time by Contractor. Such Documentation shall include, but not be limited to, the
Statement of Work, the Preliminary and Final Acceptance Criteria and the
changes, modifications, alterations and configurations made by Contractor or its
subcontractors to the Software hereunder to provide County the System. For
purposes hereof, Documentation also includes the User and/or System
Administrators’ Guides, Deliverables, and other written or electronic material as
made generally available by Contractor to its customers relating to the use,
function and support of the Software, as may be amended from time to time, by
including any derivative works thereto.
2.18
Effective Date: means the date that this System Agreement is executed by the
County.
2.19
Event: means an incident whereby the System is either not working or its
operation is inconsistent with the Documentation. Events are divided into
categories. The categories are Priority 1, 2, 3 and 4 as further defined below.
Priority 1 - Critical Business Impact Event: means the impact of the
reported Defect is such that the County is unable to either use the System
or reasonably able to continue working using the System.
Priority 2 - Significant Business Impact Event: means important
features of the System are not working properly. While other areas of the
System may not be impacted, the reported Defect has created a
significant, negative impact on County's productivity and/or service level.
Priority 3 - Some Business Impact Event: means important features of
the Software are not working properly. County impact is minimal loss of
operational functionality.
AIMS System and Services Agreement
Page 5 of 60
Exhibit 3
Page 6 of 278
Priority 4 - Minimal Business Impact Event: means the County submits
an Event, information request, Software enhancement or Documentation
clarification which has no operational impact. The implementation or use
of the System by the County is continuing and there is no material
negative impact on productivity.
2.20
Final Acceptance: means the acceptance of the System by County as required
by Resolution No. 95-937 of the Board of County Commissioners of Broward
County, Florida, which established a requirement for inspection and testing of all
computer application Software purchased or developed for County by third
parties costing over Twenty Thousand Dollars ($20,000.00).
2.21
Goods: means all tangible property, equipment and Hardware, to be provided by
Contractor pursuant to the Agreement, including but not limited to, the items as
set forth, described and designated as "to be provided by Contractor" in the
Agreement or in any exhibit to the Agreement.
2.22
Hardware: means the physical components or equipment which make up a
computer system including the programs that control the operations of the
computer and support the Software.
2.23
License Agreement: means the Software License and Maintenance Agreement
entered into by County and Contractor concurrently with this System Agreement
and all Work Authorizations issued thereunder, together with the exhibits and
schedules which are attached to the License Agreement and all Work
Authorizations thereunder, which License Agreement is incorporated herein by
this reference.
2.24
Licensed Software: means the Licensed Software described in Exhibit C to this
System Agreement (as it may be updated pursuant to the Agreement), to be
provided by Contractor and includes each computer program or module,
application and patent which makes up the Licensed Software and each copy,
translation, Update, Upgrade or modification of all or any part of the Licensed
Software in any medium, delivered to the County by, and capable of running on
Hardware recommended by Contractor and identified in Exhibit B to this System
Agreement (as it may be updated pursuant to the Agreement), together with any
materials related thereto, such as, any human readable program listings, flow
charts, logic diagrams, output forms, manuals, specifications, instructions,
Documentation, and other materials, and any copies of the foregoing, in any
medium, related to the Licensed Software and normally provided by Contractor to
any other licensee of the Licensed Software and all released modifications,
enhancements, Upgrades, or Updates provided by Contractor pursuant to the
Agreement.
2.25
Lump Sum: When the method of compensation is that of "Lump Sum" such
phrase means that Contractor shall perform or cause to be performed the
described services for total compensation in the stated amount.
AIMS System and Services Agreement
Page 6 of 60
Exhibit 3
Page 7 of 278
2.26
Maintenance Services: means any activity intended to eliminate or remedy
faults, to improve or to keep the System in satisfactory working condition,
including tests, measurements, adjustments, changes, modifications,
enhancements, repairs, Updates, and Upgrades all as provided in the License
Agreement.
2.27
Master Plan Update: means the then current Master Plan Update for the Airport
that was developed in accordance with FAA Advisory Circular 150-5070-6A,
Airport Master Plans, as it may be amended from time to time.
2.28
Maximum Amount Not-To-Exceed: when the method of compensation is that
of "Maximum Amount Not-To-Exceed" or "Maximum Not-To-Exceed Amount"
such phrase means that Contractor shall perform or cause to be performed all
services during the period set forth for total compensation based on actual hours
and costs incurred, in the amount of, or less than, the stated amount.
2.29
Notice to Proceed: with respect to this System Agreement means a written
notice to proceed, authorizing the Contractor to commence work under the
System Agreement, or under a Work Authorization or under a subsequent phase
or task of Services under this System Agreement or a Work Authorization. The
written Notice to Proceed that authorizes the Contractor to commence work
under the System Agreement shall be issued by the Contract Administrator
("Initial NTP"). The written Notice(s) to Proceed ("NTP") for subsequent phases
or tasks, shall be issued by the Contract Administrator.
2.30
Preliminary Acceptance: means the acceptance of Deliverables that constitute
a phase or subphase as defined in the Statement of Work (Exhibit A).
Preliminary Review and/or Preliminary Acceptance shall have no bearing on
County’s Final Acceptance determination.
2.31
Preliminary Review: means the fifteen (15) County Work Day time period,
subsequent to County’s receipt of a Deliverable(s) for County to perform a review
of the submitted Deliverable(s). Preliminary Review and/or Preliminary
Acceptance shall have no bearing on County’s Final Acceptance determination.
2.32
Project Manager: means the County's Project Manager and the Contractor's
Project Manager, as applicable pursuant to Section 20.7.
2.33
Releases: means those versions of the Licensed Software which add
functionality to the Software, including any Updates and Upgrades provided
under the Agreement.
2.34
Services: means the work, duties and obligations to be carried out and
performed by Contractor under the Agreement, including without limitation,
Exhibit A, "Statement of Work," to this System Agreement, and the Contract
AIMS System and Services Agreement
Page 7 of 60
Exhibit 3
Page 8 of 278
Documents and under any exhibit thereto. Without limiting the foregoing, the
Services to be performed by Contractor fall into the following general categories:
(i) consulting, (ii) installation and configuration of equipment, Hardware and
Software, (iii) modification/configuration and integration of the Software with the
existing equipment, Hardware and/or Software, (iv) project management, (v)
programming agreed upon interfaces, (vi) conversion of County’s current data,
(vii) training of County staff, (viii) infrastructure and millwork installation, (ix)
Optional Services under a Work Authorization, if authorized under this System
Agreement, (x) Maintenance Services under the License Agreement, (xi) and
Services under such Work Authorizations as may be issued under the License
Agreement.
2.35
Site License: means an unlimited number of copies of the Licensed Software
running in County Hardware, with an unlimited number of server copies and an
unlimited number of concurrent end user licenses, including Third Party User
Licenses for on and off-site, wired and wireless access of the Licensed Software.
2.36
Software: means programs in any form (i.e., object or source code) which (i) tell
a computer what to do, and (ii) perform the tasks specified in the Agreement,
whether or not the programs are to be supplied by Contractor.
2.37
Subcontractor: means a firm, partnership, corporation or combination thereof
having a direct contract with the Contractor for all or any portion of the work.
2.38
Sublicense: means a sublicense in Third Party Software that is granted to the
County by the Contractor pursuant to the Contractor's license rights in such
Software.
2.39
System or AIMS: means the Airport Information Management System as well as
the Software, enhancements, Third Party Software, Hardware, Goods, Services,
Documentation, licenses and other items, tangible and intangible, which together
will (i) allow County's Aviation Department to have and maintain an integrated
Airport Information Management System in a multi-user environment employing
microcomputer technology, and (ii) provide the Documentation and Services
required by the Agreement.
2.40
System Agreement: means Articles 1 through 23, inclusive, inclusive, of this of
this System and Services Agreement, all Work Authorizations issued hereunder,
the Contract Documents, and the exhibits and schedules which are attached to
this System Agreement, any Work Authorizations issued hereunder and the
Contract Documents, all of which are incorporated herein by this reference. Any
references in an exhibit listed below to the "System Agreement" or "Contract
Documents" shall be deemed to mean this System Agreement, together with all
Work Authorizations issued hereunder, all Contract Documents and all exhibits to
the foregoing. The following exhibits and schedules are attached hereto and
incorporated into this System Agreement by this reference:
AIMS System and Services Agreement
Page 8 of 60
Exhibit 3
Page 9 of 278
Exhibit A
Exhibit B
Exhibit B-1
Exhibit C
Exhibit D
Exhibit E
Exhibit F
Exhibit G
Exhibit H
Exhibit I
Exhibit J
Exhibit J-1
Exhibit J-2
Exhibit J-3
Exhibit J-4
Exhibit K
Exhibit L
Exhibit M
Exhibit N
Attachment I
Attachment II
Attachment III
Statement of Work
Goods and System Hardware
(as it may be updated pursuant to the Agreement)
Existing EVIDS Devices
(as it may be updated pursuant to the Agreement)
Licensed Software and Third Party Software
(as it may be updated pursuant to the Agreement)
Rates and Fees to be Charged by Contractor/Subcontractor
Master Price List
(as it may be updated pursuant to the Agreement)
Payment Schedule
Key Staff
Certificates of Insurance
Work Authorization Forms;
Contract Administrator, Purchasing, Board
Schedule of Subcontractor Participation
Schedule of CBE Participation and Letters of Intent
Certification of Payments to Subcontractors and Suppliers
CBE Utilization Report
Final CBE Utilization Report
Payment Forms
Change Order Form
Optional Services
Form of Performance Bond and Payment Bond
Nondiscrimination Requirements
Provisions Pertaining to Airport Projects
Off Shore Statement
2.41
Third Party Users: means those individuals or entities authorized to use the
System by County.
2.42
Third Party Software: means the Third Party Software described on Exhibit C
(as it may be updated pursuant to the Agreement). Third Party Software is nonContractor Software that is necessary for the System to perform its functions and
is sublicensed to County under the License Agreement. Unless otherwise
specified or otherwise clear from the context, the term "Third Party Software"
also includes any utility, application and patch to the Third Party Software that is
required to operate the System, and all released modifications, enhancements,
Upgrades and Updates thereto provided by Contractor pursuant to the
Agreement.
2.43
Updates: mean periodic Releases of Software that may contain fixes or
incremental enhancements to the Software.
2.44
Upgrades: shall mean new versions of Software that add features, improve
functionality, and/or increase capacity of the Software to process information.
AIMS System and Services Agreement
Page 9 of 60
Exhibit 3
Page 10 of 278
2.45
Work Authorization: means a written authorization substantially in the
appropriate form attached as Exhibit I, authorizing Optional Services identified in
Exhibit M, and in accordance with Article 9, hereof.
ARTICLE 3
REQUEST FOR PROPOSAL
The parties understand that the System Agreement and the License Agreement are the
result of County’s procurement process. County published a Request for Proposal
designated as Airport Information Management System, RFP No. 20070514-0-AV-01,
which together with other subsequent documentation (all hereinafter "RFP") described
and set forth the standards and requirements for the System and the contractual
relationship to be entered into and to which the parties agree reference can be made as
if the RFP and other documentation are set forth fully herein. After the review of the
responses, County selected Contractor as the entity that best met its criteria for the
above and with whom it would negotiate for the System Services and the Software
License and Maintenance Services. The parties agree reference can be made to
Contractor’s responses to the RFP as if Contractor’s responses to the RFP are set forth
fully herein. Contractor understands that County, after entering into this System
Agreement and the License Agreement, has no need for Contractor’s products nor for
the products of third parties, both Goods and intangible properties, unless the System
performs as represented nor does it need the Services if it does not accept the System
and unless the Acceptance Criteria described and set forth in the System Agreement
are met. Contractor acknowledges that County’s acquisitions made as a part of the
Agreement are subject to the Acceptance Criteria described and set forth in the System
Agreement being met and such is an essential element and condition of the System
Agreement.
ARTICLE 4
RESOLUTION NO. 95-937
Resolution No. 95-937, of the Board of County Commissioners of Broward County,
Florida, relating to County’s Computer Software Policy, established a requirement for
inspection of all computer application Software purchased or developed for County by
third parties costing over Twenty Thousand Dollars ($20,000.00) prior to its acceptance
by County. Contractor recognizes that all computer application Software purchased or
licensed by County from Contractor, and without limiting the foregoing, in particular, the
System, shall be inspected and tested by County’s Office of Information Technology
prior to acceptance of the System. Also, all contracts with third parties for the purchase
of computer application Software costing more than Twenty Thousand Dollars
($20,000.00) shall include clauses providing (i) for inspection and testing by the Office
of Information Technology of such computer application Software prior to formal
acceptance of that Software by County, and (ii) that final payment shall not be made
prior to formal acceptance of the System by County. The Office of Information
Technology will utilize the standards for acceptance set forth and described in the
AIMS System and Services Agreement
Page 10 of 60
Exhibit 3
Page 11 of 278
Agreement. In the event of non-acceptance of the System and only after full repayment
by Contractor of any and all monies paid to it by County pursuant to the Agreement,
subject to third party claims against Contractor, County shall return the Goods, Licensed
Software, Documentation and other items and materials received from Contractor and
remove the Licensed Software from any and all County Hardware upon which the
Licensed Software may reside. The parties also recognize and agree that County's
obligations under the System Agreement and the License Agreement are specifically
conditioned upon its accepting the System as set forth and described in this System
Agreement.
ARTICLE 5
STATEMENT OF WORK
5.1
Contractor shall perform all work identified in this System Agreement and Exhibit
A, "Statement of Work," attached to and made a part of this System Agreement.
The parties agree that the Statement of Work is a description of Contractor’s
obligations and is deemed to include preliminary consideration and prerequisites,
labor, materials, equipment, and tasks which are such an inseparable part of the
work described that exclusion would render performance by Contractor
impractical, illogical, or unconscionable.
5.2
Contractor has executed the License Agreement concurrent with this System
Agreement and shall execute the Master Preferred Escrow Agreement within
thirty (30) calendar days following Final Acceptance and Contractor agrees that
Contractor is bound by the terms and conditions contained therein upon the
execution of the same by County. The Director of County’s Purchasing Division
is hereby authorized to execute the Master Preferred Escrow Agreement on
behalf of County.
5.3
For a period of ten (10) years from the Final Acceptance of the System by
County, Contractor agrees to provide consulting, programming, and support
Services as requested by County for customization and/or enhancements to the
System. County shall pay Contractor for the Services, object code related to any
programming, and documentation related to the development work at the rate for
the service categories as set forth and described in Exhibit D, "Rates and Fees
to be Charged by Contractor/Subcontractor," attached to and made a part of this
System Agreement. Where the programming to be provided by Contractor is for
custom Software, Contractor will also provide the source code for such
programming.
5.4
During performance of Services under this System Agreement (as it may be
amended), Contractor shall communicate and coordinate with County staff and
other County contractors, consultants and stakeholders and Contractor shall give
due consideration to such input in Contractor’s analysis.
AIMS System and Services Agreement
Page 11 of 60
Exhibit 3
Page 12 of 278
ARTICLE 6
COMPENSATION AND METHOD OF PAYMENT
6.1
County agrees to pay Contractor, in the manner specified in Section 6.2, the total
maximum not to exceed amount of Five Million Four Hundred Thirty-Eight
Thousand Nine Hundred Twenty Dollars ($5,438,920.00) as follows:
6.1.1 Four Million Three Hundred Ninety-Nine Thousand Nine Hundred Twenty
Dollars ($4,399,920.00) for the Deliverables, Goods and Services actually
performed and completed pursuant to this System Agreement, which
amount shall be accepted by Contractor as full compensation for all such
items. It is acknowledged and agreed by Contractor that this amount is
the maximum payable and constitutes a limitation upon County's
obligation to compensate Contractor for such Deliverables, Goods and
Services related to this System Agreement. This maximum amount,
however, does not constitute a limitation, of any sort, upon Contractor's
obligation to perform all items of work required by, or which can be
reasonably inferred from, the Statement of Work.
6.1.2 A Maximum Not-To-Exceed Amount of Five Hundred Eighty Thousand
Dollars ($580,000.00) for Optional Services described in Exhibit M,
attached hereto, as may be authorized pursuant to Article 9 hereof.
Contractor shall have no right to compensation for any Optional Services,
unless and until any such Optional Services are authorized by a Work
Authorization issued pursuant to Article 9.
6.1.3 The sum of Four Hundred Fifty-Nine Thousand Dollars ($459,000.00) for
the license to the Licensed Software.
6.1.4 The amounts set forth above includes any and all of Contractor's
overhead, operating costs, outlays, profit, and other out-of-pocket costs
and associated out-of-pocket costs, including, but not limited to, travel (air
& cab fare, lodging, auto rental, per diem, etc.), photocopying, long
distance telephone, special mailings and the like. Contractor shall also
bear all of its own expenses arising from its performance of the obligations
under this System Agreement and the Statement of Work including
(without limitation) expenses for facilities, work spaces, utilities,
management, clerical and reproduction services, supplies, and the like.
The prices and costs stated above include all taxes. It is understood that
County is a tax exempt entity and shall only be responsible for the
payment of applicable taxes, if any, if and when it loses tax exempt status.
6.2
Method Of Billing And Payment
6.2.1 Software. County shall pay Contractor for the Licensed Software, if
accepted by County, a total one time License Fee of Four Hundred Fifty-
AIMS System and Services Agreement
Page 12 of 60
Exhibit 3
Page 13 of 278
Nine Thousand Dollars ($459,000.00) for the license to the Licensed
Software. Payment for such Software shall be made in the following
manner:
(a)
Fifty percent (50%) of the License Fee for the Licensed Software
shall be due Contractor upon County’s Preliminary Acceptance of
the completion of Phase One (FAT) (Exhibit F). This payment shall
be made by County following Preliminary Acceptance of Phase
One and receipt of a proper invoice from Contractor.
(b)
Fifty percent (50%) of the License Fee for the Licensed Software
shall be due Contractor upon County’s Final Acceptance of the
System. This payment shall be made by County following Final
Acceptance of the System and receipt of a proper invoice from
Contractor.
(c)
Contractor will provide and install the Licensed Software and Third
Party Software on the Hardware identified in Exhibit B, attached
hereto and made a part hereof, as it may be updated pursuant to
the Agreement. Installation Services shall include the initial
installation of the Licensed Software and Third Party Software
configured for County by Contractor. Although Contractor will
perform the configuration and installation of the such Software,
Contractor will also furnish County with sufficient instructions,
Documentation or other written materials as may be necessary to
install the configured Software in an efficient and expeditious
manner.
6.2.2 Invoices - Statement of Work and Work Authorizations. The
Contractor shall submit invoices for all subphases identified in Exhibit F
and for all phases or subphases of all Work Authorizations that have
received Preliminary Acceptance during the preceding monthly period.
The invoices shall be in a format designated by Contract Administrator
and approved by the appropriate County offices. Contractor may be
required to include a submittal of an electronic copy using Software
specified by the Contract Administrator and as approved by the
appropriate County offices, as well as the number of hard copies required
by the Contract Administrator. In addition, all costs must be classified and
sorted based on the work breakdown structure (WBS) provided by the
Contract Administrator. Contractor may submit invoices only after the
Services/Deliverables/Goods for which the invoices are submitted have
been completed and achieved Preliminary Acceptance. An original invoice
is due in the month following Preliminary Acceptance of each phase or
subphase as identified in the Payment Schedule (Exhibit F) or as detailed
in the payment schedule in a Work Authorization, as applicable, except
the final invoice which must be received no later than sixty (60) calendar
AIMS System and Services Agreement
Page 13 of 60
Exhibit 3
Page 14 of 278
days after Final Acceptance. Invoices shall comply with the requirements
of County’s Prompt Payment Ordinance (Section 1-51.6, Broward County
Code of Ordinances, as it may be amended).
(a)
When requested, Contractor shall provide detailed backup for past
and current invoices that record actual hours, unit prices, rates and
fees on an item basis, and by employee category so that total hours
and costs by item may be determined. These records must be
made available to the Contract Administrator upon request. For
each invoice, the Contractor shall submit an original invoice and at
least two copies (with all back-up) to the Contract Administrator.
(b)
Billings shall also indicate the cumulative amount of CBE
participation for the period covered by the billing as well as the
cumulative amount to date. Contractor shall also submit with each
invoice a Certification of Payments to Subcontractors and
Suppliers, using the form attached as Exhibit J-2. The certification
shall be accompanied by a copy of the notification sent to each
subcontractor and supplier listed in item 2 of the form, explaining
the good cause why payment has not been made. In addition, the
Contractor shall submit with each invoice Exhibit J-3, "CBE
Utilization Report," and shall submit with the final invoice, Exhibit
J-4, "Final CBE Utilization Report," listing only those subcontractors
certified as CBE's to show expenditures made to date to achieve
compliance with the assigned goals.
(c)
Contractor shall submit billings which are identified by the specific
project number on a not more than monthly basis, following
Preliminary Acceptance for a phase or subphase. Billings shall not
exceed the amount allocated to the respective phase or subphase.
These billings shall identify the phase or subphase performed. The
statement shall show a summary of costs with accrual of the total
and credits for portions paid previously. Invoices must contain a
project number and project title and must clearly indicate the phase
or subphase completed. County shall not pay Contractor any
additional sum for additional services, over and about the amount
allocated for the phase, subphase or Work Authorization, except as
may be provided for in this Agreement.
6.2.3 Payments - Statement of Work and Work Authorizations. Payments
shall be made for the Services set forth in the Statement of Work (Exhibit
A), based on the "Payment Schedule," attached to the System Agreement
as Exhibit F. Payments shall be made for Services as set forth in a Work
Authorization, based on the payment schedule contained therein.
AIMS System and Services Agreement
Page 14 of 60
Exhibit 3
Page 15 of 278
(a)
Contractor shall notify County in writing when Contractor is satisfied
that a phase or subphase is completed and ready for Preliminary
Review by County. Within fifteen (15) County Work Days following
receipt of Contractor’s written notice, County shall issue its written
statement of Preliminary Acceptance or its written notice that the
work comprising the phase or subphase has not achieved
Preliminary Acceptance. Preliminary Review shall include, at a
minimum, a scheduled meeting between County and Contractor to
review all Deliverables to this point, discuss outstanding or known
issues, and determine whether to proceed with the next phase or
subphase. County will not unreasonably withhold Preliminary
Acceptance if Contractor has provided the required Deliverables to
County in a timely manner and each Deliverable satisfies its
associated Acceptance Criteria. Contractor shall not submit any
invoice for payment until County has agreed to Preliminary
Acceptance of the particular phase or subphase. Preliminary
Review and/or Preliminary Acceptance shall have no bearing on
County’s Final Acceptance determination as set out in Article 12.
(b)
Following Preliminary Acceptance of any subphase(s) within Phase
Zero or Phase One (Exhibit F), County shall pay Contractor ninety
percent (90%) of the total shown to be due on the invoice as
detailed in the Payment Schedule (Exhibit F). The remaining ten
percent (10%) retainage shall be remitted as provided for in Section
6.2.5 and Article 12 below.
(c)
Following Preliminary Acceptance of any subphase(s) within Phase
Two (Exhibit F), County shall pay Contractor ninety-two and one
half percent (92.5%) of the total shown to be due on the invoice as
detailed in the Payment Schedule (Exhibit F). The remaining seven
and one half percent (7.5%) retainage shall be remitted as provided
for in Section 6.2.5 and Article 12 below.
(d)
Following Preliminary Acceptance of any subphase(s) within Phase
Three (Exhibit F), County shall pay Contractor ninety-five percent
(95%) of the total shown to be due on the invoice as detailed in the
Payment Schedule (Exhibit F). The remaining five percent (5%)
retainage shall be remitted as provided for in Section 6.2.5 and
Article 12 below.
(e)
Following Preliminary Acceptance of any phase(s) or subphase(s)
within any Work Authorization, County shall pay Contractor ninetytwo and one half percent (92.5%) of the total shown to be due on
the invoice as detailed in the Work Authorization. The remaining
seven and one half percent (7.5%) retainage shall be remitted as
provided for in Section 6.2.5 and Article 12 below.
AIMS System and Services Agreement
Page 15 of 60
Exhibit 3
Page 16 of 278
6.2.4 County shall pay Contractor within twenty-five (25) County Work Days of
receipt of Contractor's proper statement, as required by the Broward
County Prompt Payment Ordinance. To be deemed proper, all invoices
must comply with the requirements set forth in this System Agreement and
must be submitted on the form and pursuant to instructions prescribed by
Contract Administrator. Payment may be withheld for failure of Contractor
to comply with a term, condition, or requirement of the Agreement.
6.2.5 Contractor agrees that all Software that is part of the System shall be
inspected and tested by County together with the Licensed Software and
the System as a whole as set forth herein and final payment shall not be
made until County has completed the Final Acceptance of the System
(including all Services under Work Authorizations that have been issued
by the County pursuant to Article 9), as set forth in Exhibit A, "Statement
of Work," and Article 12 below.
6.2.6 The parties acknowledge that Exhibit A, "Statement of Work," may not
delineate every detail and minor work task required to be performed by
Contractor to complete its Services and provide the Deliverables and the
System. If, during the course of the performance of the Services,
Contractor determines that work should be performed to complete the
System which, in Contractor's opinion, is outside the level of effort
originally anticipated in Exhibit A, "Statement of Work," whether or not
Exhibit A, "Statement of Work," identifies the work items, Contractor shall
notify the Contract Administrator in writing in a timely manner. If
Contractor proceeds with said work without notifying the Contract
Administrator, said work shall be deemed to be within the original level of
effort, whether or not specifically addressed in Exhibit A, "Statement of
Work." Notice to the Contract Administrator by Contractor does not
constitute authorization or approval by County to perform the work.
Performance of work by Contractor outside the originally anticipated level
of effort without prior written County approval is at Contractor's sole risk.
6.2.7 Change Orders. Change orders shall be in accordance with Article 16.
6.2.8 The provisions of Article 12 are also applicable to Contractor's invoicing
and payment obligations.
AIMS System and Services Agreement
Page 16 of 60
Exhibit 3
Page 17 of 278
6.2.9 Payment will be made to Contractor at:
Chris Keller
Air-Transport IT Services, Inc.
5950 Hazeltine National Drive
Orlando, FL 32822
Facsimile: 407-370-4657
ARTICLE 7
NOTICE TO PROCEED; LIQUIDATED DAMAGES
7.1
Notice to Proceed. Prior to beginning the performance of this System
Agreement, Contractor must receive an Initial NTP from the Contract
Administrator. Prior to beginning each phase of Services in the Statement of
Work, and prior to beginning any phase or task in a Work Authorization,
Contractor must also receive a Notice to Proceed from the Contract
Administrator.
7.2
Initial Notice to Proceed ("Initial NTP"). Prior to the execution of this System
Agreement, Contractor shall provide County with a properly completed Insurance
Certificate, the completion of, and submittal of, which is considered a condition
precedent to the execution of this System Agreement. County shall not issue the
Initial NTP until Contractor has complied with the requirements of this Section
7.2.
7.3
Completion of System Timetable/Liquidated Damages. Contractor shall
complete the System (including Services under such Work Authorizations as may
be issued pursuant to Article 9 hereof), through Final Acceptance, within twentyfour (24) months from the date of the issuance of the Initial NTP ("Completion
Date"). If Contractor is unable to complete the System (including Services under
such Work Authorizations as may be issued hereunder), including Final
Acceptance, County shall have the option to terminate the Agreement and
Contractor shall then refund all monies received from County. Alternatively,
County is entitled to liquidated damages of Five Hundred Dollars ($500.00) per
day for each calendar day following the Completion Date, up to the date of Final
Acceptance. The Contract Administrator shall have the option to extend the
completion time period prior to the commencement of liquidated damages for
good cause shown, including without limitation a Force Majeure Event as
described in Section 20.21 or delay caused by the County. In the event of any
termination hereunder the Contractor shall not be required to a refund any
monies for or Goods, Hardware, or Software subsystems that were purchased by
the County from Contractor and retained by County after the termination of the
Agreement.
AIMS System and Services Agreement
Page 17 of 60
Exhibit 3
Page 18 of 278
7.4
Contractor acknowledges that County retains the sole discretion of whether to
exercise the remedy of liquidated damages, in addition to other remedies
available pursuant to the Agreement, at law and in equity. The parties further
stipulate that the amount of liquidated damages provided for in Section 7.3 is not
intended to be a penalty and is purely intended to reasonably compensate
County for unknown and unascertainable damages. The parties agree that if
County allows Contractor to continue completion of the work to be provided
pursuant to the System Agreement, or any part of it, after the expiration of the
time allowed above, including extensions of time granted to Contractor by
County, that County’s action shall in no way act as a waiver on the part of County
of the liquidated damages due under Section 7.3.
ARTICLE 8
INDEMNIFICATION OF COUNTY
8.1
Contractor shall, at all times hereafter, indemnify, hold harmless and, at the
County Attorney’s option, defend or pay for an attorney selected by the County
Attorney to defend County, its officers, agents, servants and employees from and
against any claims, demands, causes of action, losses, liabilities, and
expenditures of any kind or nature, including all costs, expenses, and attorneys’
fees, arising out of any negligent, reckless, or intentional act, error or omission of
Contractor, its officers, agents, servants or employees in the performance of
Services under this Agreement, or accruing, resulting from, or related to the
subject matter of this Agreement including, without limitation, any and all claims,
demands, or causes of action of any nature whatsoever resulting from injuries or
damages sustained by any person or property.
8.2
Contractor further agrees, at all times hereafter, to indemnify, hold harmless and,
at the County Attorney’s option, defend or pay for an attorney selected by the
County Attorney to defend County, its officers, agents, servants and employees
from and against any claim, demand or cause of action of any kind or nature,
including all costs, expenses, and attorneys fees, arising out of any misconduct
of Contractor, its officers, agents, servants or employees during the performance
of Services under this Agreement not included in 8.1 above.
8.3
The above indemnifications shall survive the expiration or termination of this
Agreement.
8.4
To the extent considered necessary by Contract Administrator and County
Attorney, any sums due Contractor under this Agreement may be retained by
County until all of County's claims for indemnification pursuant to this Agreement
have been settled or otherwise resolved; and any amount withheld shall not be
subject to payment of interest by County.
AIMS System and Services Agreement
Page 18 of 60
Exhibit 3
Page 19 of 278
ARTICLE 9
WORK AUTHORIZATIONS
9.1
Authorization of Work; Optional Services: The Services contained within
Exhibit M attached hereto represent Optional Services that may be requested by
the County. In the event County desires that Contractor provide any of the
Services listed in Exhibit M, such Services shall be performed and provided by
Contractor following issuance of a written Work Authorization (in form similar to
the samples attached as part of Exhibit I)("Work Authorization") for any of such
items. Any or all of the Services set forth in Exhibit M shall be required at the
sole and exclusive discretion of the County. Nothing set forth herein shall require
County to provide a Work Authorization for any of the items listed in Exhibit M.
County shall compensate Contractor for such Optional Services as provided in
Article 6.
9.1.1 The Optional Services identified in Exhibit M, attached hereto and made a
part hereof, as Items 1 through 4 are Maximum Not-To-Exceed amounts.
(a)
Any Work Authorizations issued under Item 4 on Exhibit M,
"General Services," shall be subject to the approval of the Board,
Purchasing Director, or Contract Administrator, as appropriate,
pursuant to Subsection 9.1.2, below.
(b)
Items 1 through 3 have been authorized by the Board subject only
to the maximum amount established for each item (as may be
increased pursuant to Subsection 9.1.6, below). The completion
dates for the listed Services shall be set forth in such Work
Authorizations as may be issued by the Contract Administrator.
Only the issuance of a Work Authorization by the Contract
Administrator shall be required before any Services described in
Items 1 through 3 may begin. Such Services may be authorized
by the Contract Administrator, using the form Work Authorization
attached as Exhibit I-1, in his or her sole discretion, subject to the
maximum amounts established for each item (as may be increased
pursuant to 9.1.6, below) and the maximum amount set forth in the
Work Authorization. The Contractor's compensation under a Work
Authorization for Services under Items 1 through 3 shall not
exceed the amount approved in the Work Authorization. If
additional Services are required over the amount set forth in the
Work Authorization, any additional compensation must be reflected
in an amendment to the Work Authorization, signed by the Contract
Administrator and the Contractor, provided total compensation shall
not exceed the amount identified in the applicable item listed in
Exhibit M (as may be increased pursuant to 9.1.6, below).
AIMS System and Services Agreement
Page 19 of 60
Exhibit 3
Page 20 of 278
9.1.2 With respect to any Services performed under Item 4, on Exhibit M,
"General Services," Work Authorizations must be issued in accordance
with the provisions of this subsection. Any such Services shall be subject
to the approval of the Contract Administrator, Purchasing Director, or
Board, as appropriate, pursuant to the terms of this subsection. Work
Authorizations shall be in a format similar to the samples attached in
Exhibit I, depending upon the award authority.
(a)
Before any Services are performed pursuant to Item 4, "General
Services," the Contractor shall supply the Contract Administrator
with an estimate for all charges expected to be incurred for such
Services, which estimate shall be reviewed by the Contract
Administrator and the Contractor and a final amount for
Contractor's compensation shall be approved in the manner set
forth below.
(b)
Work Authorizations that will cost County Thirty Thousand Dollars
($30,000.00) or less shall be signed by Contract Administrator and
Contractor, using the applicable Work Authorization Form included
in Exhibit I.
(c)
Work Authorizations that will cost County more than Thirty
Thousand Dollars ($30,000.00) and up to $100,000.00 shall be
signed by County's Purchasing Director and Contractor. Work
Authorizations that will cost County more than One Hundred
Thousand Dollars ($100,000.00) shall be signed by the Board and
Contractor. Work Authorizations within the Purchasing Director’s
delegated authority shall be prepared using the applicable Work
Authorization form included in Exhibit I. Work Authorizations that
require approval by the Board shall be prepared using the
applicable Work Authorization form included in Exhibit I.
(d)
Any charges in excess of the amount approved in a Work
Authorization for General Services shall require a modification
thereto approved by Contract Administrator, Purchasing Director, or
Board as follows: Contract Administrator shall sign in instances
where the cumulative total of the modifications (the amount
approved in the original Work Authorization plus the modifications
thereto) does not exceed Thirty Thousand Dollars ($30,000.00).
County’s Purchasing Director shall sign in instances where the
cumulative total of the modifications exceeds Thirty Thousand
Dollars ($30,000) but does not exceed One Hundred Thousand
Dollars ($100,000.00). The Board shall sign in those instances
where the cumulative total of the modifications exceeds One
Hundred Thousand Dollars ($100,000.00). Notwithstanding
anything contained in this subsection to the contrary, Contractor's
AIMS System and Services Agreement
Page 20 of 60
Exhibit 3
Page 21 of 278
compensation shall not exceed the amount approved in a Work
Authorization unless such additional amount has received written
County approval as outlined above. In the event County does not
approve an increase in the amount, and the need for such action is
not the fault of Contractor, the authorization shall be terminated,
and Contractor shall be paid in full for all Services completed to that
point, but shall in no case exceed the maximum amount of the
Work Authorization. The information contained in the budget shall
be in sufficient detail so as to identify the various elements of costs.
9.1.3 All Work Authorizations shall contain, at a minimum, the following
information and requirements:
(a)
A description of the Services to be undertaken and the deliverables
to be provided, a statement of the item on Exhibit M pursuant to
which such Services are to be performed, a statement of the
method of compensation (i.e., Lump Sum or Maximum Amount NotTo-Exceed), and, if payment is to be made upon completion of
phases, identification of such stages of completion and the
payment applicable to each stage of completion.
(b)
A budget establishing the amount and method of compensation and
fees to be paid, and the applicable method for calculating same.
The amount shall be set forth as either a Lump Sum or a Maximum
Amount Not-To-Exceed, and shall not be exceeded unless written
approval of the Contract Administrator, Purchasing Director or
Board (as applicable) is obtained. The information contained in the
budget shall be in sufficient detail so as to identify the various
elements of costs.
(c)
A time established for completion of the Services undertaken by
Contractor or for the submission to County of documents, reports,
and other information.
(d)
Any other additional instructions or provisions.
(e)
Authorizations shall be dated, serially numbered, and signed by the
Contract Administrator, the Purchasing Director, or the Board, as
required by this Article 9.
9.1.4 Subsequent to County issuing a Work Authorization pursuant to this
article, Contract Administrator will issue a Notice to Proceed for those
authorized Optional Services under the Work Authorization. Contractor
shall not commence such Services until after receipt of the Contract
Administrator’s Notice to Proceed.
AIMS System and Services Agreement
Page 21 of 60
Exhibit 3
Page 22 of 278
9.1.5 If it appears during the progress of services under a Work Authorization
(and in no event later than seventy-five percent (75%) of task completion)
that the actual costs may exceed the amounts established by the Work
Authorization, Contractor shall immediately submit to the Contract
Administrator a written request for additional compensation accompanied
by substantiation of costs. The Contract Administrator shall determine
whether the request is reasonable under the circumstances. The amount
set forth in any Work Authorization shall not be exceeded, except pursuant
to a written amendment to the Work Authorization. When changes in the
services to be provided under a Work Authorization are required by the
Contract Administrator or requested by the Contractor, the Contractor
shall promptly estimate their effect on the cost of the services and on the
schedule for completion, and provide notice thereof in writing to the
Contract Administrator.
9.1.6 For any of the items identified in Exhibit M, the Contract Administrator
may transfer an annual aggregate maximum of thirty percent (30%) of the
initial value of each category to any other category. Notwithstanding the
foregoing, the receiving category may not be increased by the aggregate
amount that is greater than the Director of Aviation's change order
authority (as provided in Section 21.73(c) of the Procurement Code)
unless Board approval is first obtained. Work Authorizations utilizing such
transferred amounts shall be subject to the limitations and requirements
set forth in this Agreement.
9.1.7 The parties acknowledge that Final Acceptance of the System shall not
occur until all issued Work Authorizations have been completed. The
deliverables under all issued Work Authorizations shall be included in the
Preliminary Review(s) and shall be required to satisfy Final Acceptance
criteria, as part of the System. Upon Final Acceptance of the System, no
further Work Authorizations shall be issued.
ARTICLE 10
TERMINATION
10.1
Contractor may terminate the Agreement if County materially breaches any term
of the Agreement and/or fails to pay Contractor any money that is due under the
Agreement, and County fails to cure said breach within sixty (60) calendar days
after Contractor provides County with written notice of said material breach.
10.2
County may terminate the Agreement if Contractor materially breaches any term
of this Agreement, and Contractor fails to cure said breach within sixty (60)
calendar days after County provides Contractor with written notice of said
material breach. An erroneous termination for cause shall be considered a
termination for convenience.
AIMS System and Services Agreement
Page 22 of 60
Exhibit 3
Page 23 of 278
10.3
County reserves the right and option to terminate the Agreement for convenience
by action of the Board upon not less than thirty (30) calendar day’s written notice
to the Contractor by the Contract Administrator. At the end of which time, this
System Agreement and the License Agreement will automatically terminate
without the necessity of any further action.
10.3.1 In the event the Agreement is terminated for convenience prior to Final
Acceptance, Contractor will be paid for all Services, including labor and
programming costs, incurred prior to the effective date of termination, and
Contractor shall refund to County the full license fee paid by County for
any Licensed Software and Third Party Software included in the System,
any Maintenance Services Fee previously paid by the County under the
License Agreement that would apply to any period after the date of
termination, and all amounts paid by County to Contractor for any
materials, Equipment, Goods, and Hardware returned to Contractor. After
full repayment by Contractor of the license fee amounts received from
County for the Licensed Software and Third Party Software, the applicable
portion of the Maintenance Services Fee, and the amounts previously paid
by County for materials, Equipment, Goods and Hardware that are
returned to Contractor, County shall promptly remove any Licensed
Software and Third Party Software from any County-owned Hardware
upon which such may reside. Additionally, Contractor may, in the
reasonable, professional discretion of the Contract Administrator, subject
to Board approval, be allowed direct termination expenses and fixed
settlement costs which become firm prior to the date of the notice of
termination. No payment will be made for lost or future profits. Upon
receipt of notice of termination, Contractor shall discontinue all work,
cease any deliveries, shipment, or carriage of Goods, and make available
to the Contract Administrator any and all reports, data, specifications,
estimates, summaries, and information as are required by this System
Agreement and the License Agreement as of the date of termination.
Contractor acknowledges and agrees that ten dollars ($10.00) of the
compensation to be paid by County, the adequacy of which is hereby
acknowledged by Contractor, is given as specific consideration to
Contractor for County’s right to terminate for convenience under this
Subsection 10.3.1.
10.3.2 In the event this System Agreement is terminated for convenience after
Final Acceptance, then County shall keep all Goods, Equipment,
Hardware and Software supplied by Contractor, provided County has paid
in full the license fee and purchase price, as installed, for same, and if the
License Agreement is also terminated for convenience, Contractor shall
reimburse County for any Maintenance Services Fee previously paid by
the County that would apply to any period after the termination of the
License Agreement. Contractor acknowledges and agrees that ten dollars
($10.00) of the compensation to be paid by County, the adequacy of which
AIMS System and Services Agreement
Page 23 of 60
Exhibit 3
Page 24 of 278
is hereby acknowledged by Contractor, is given as specific consideration
to Contractor for County’s right to terminate for convenience.
10.4
County may also terminate the Agreement pursuant to Section 12.4 hereof.
10.5
Any notice of termination of this System Agreement shall be provided in
accordance with the "NOTICES" section of this System Agreement, except that
notice of termination by County Administrator which County Administrator deems
necessary to protect the public health, safety, or welfare may be verbal notice
which shall be promptly confirmed in writing in accordance with the "NOTICES"
section of this System Agreement. Upon any termination of this System
Agreement by the County, whether for cause or convenience, the County at its
option, may also terminate the License Agreement.
10.6
In addition, the County shall have the right, at its sole and exclusive discretion
and upon seven (7) calendar days notice in writing, to terminate any one or more
items identified on Exhibit M, or phases or tasks described in a Work
Authorization, and to procure Services for such items, phases or tasks from
another source. In such event: (i) Contractor shall be paid for Services performed
through the date of termination then due or incurred to termination date); and (ii)
any items, phases or tasks not terminated by such written notice shall continue to
be covered by this System Agreement and the issued Work Authorization(s) and
Contractor shall perform the Services required pursuant to the applicable terms
and conditions. However, Contractor shall refrain from performing further
Services or incurring under any terminated items, phases and tasks.
10.7
If the term of this System Agreement extends beyond a single fiscal year of
County, the continuation of this System Agreement beyond the end of any fiscal
year shall be subject to the availability of funds from County in accordance with
Chapter 129, Florida Statutes, as it may be amended.
10.8
In the event of any termination of this System Agreement (whether a termination
of the entire System Agreement or any item listed in Exhibit M, or any phase or
task of a Work Authorization), Contractor shall deliver all documents and records,
including without limitation, all data, studies, surveys, drawings, maps, models,
photographs and reports prepared or provided by Contractor in connection with
this System Agreement (in whatever state they may be in at the date of
termination) to the County within seven (7) calendar days following receipt of the
written notice of termination. Any compensation due Contractor shall be withheld
until all documents and records are received by County as provided herein.
10.9
This System Agreement may also be terminated by the Board:
10.9.1 Upon the disqualification by County’s Director of Small Business
Development Division of Contractor as a CBE if Contractor’s status as
AIMS System and Services Agreement
Page 24 of 60
Exhibit 3
Page 25 of 278
CBE was a factor in the award of this System Agreement and such
status was misrepresented by Contractor;
10.9.2 Upon the disqualification by County’s Director of Small Business
Development Division of Contractor if Contractor obtained this System
Agreement or attempted to meet its CBE contractual obligations through
fraud, misrepresentation, or material misstatement;
10.9.3 Upon the disqualification by County’s Director of Small Business
Development Division of one or more of Contractor’s CBE participants if
any such participant’s status as a CBE was a factor in the award of this
System Agreement and such status was misrepresented by Contractor
or such participant;
10.9.4 Upon the disqualification by County’s Director of Small Business
Development Division of one or more of Contractor’s CBE participants if
such CBE participant attempted to meet its CBE contractual obligations
through fraud, misrepresentation, or material misstatement; or
10.9.5 If Contractor is determined by County’s Director of Small Business
Development Division to have been knowingly involved in any fraud,
misrepresentation, or material misstatement concerning the CBE status
of its disqualified CBE participant. If so determined, Contractor shall not
be awarded CBE participation credit.
ARTICLE 11
CONFIDENTIAL INFORMATION
11.1
11.2
Restrictions upon Disclosure of Information. Each party agrees:
(a)
To treat the other's confidential information as proprietary to the other;
(b)
To not knowingly disclose to any person, other than its employees or
contractors, or entity not a party to this Agreement any confidential
information belonging to the other party; and
(c)
To inform its employees and contractors of the confidential nature of the
other's information and of the requirement of nondisclosure.
In the event either party has actual knowledge of a breach of the nondisclosure
requirements of this Article, the party acquiring such knowledge shall promptly
inform the other party and assist that party in curing the disclosure, where
possible, and preventing future disclosures. For the purposes of this provision,
the term "confidential information" shall be that information specifically
designated in writing as confidential by the claiming party. Nothing in this
provision shall prevent a party from disclosing information of the other, whether
confidential or not, where such disclosure is required by law.
AIMS System and Services Agreement
Page 25 of 60
Exhibit 3
Page 26 of 278
11.3
11.4
Nondisclosure by County shall not apply to information that:
(a)
Is or becomes known to the public without fault or breach on the part of
County;
(b)
Contractor regularly discloses to third parties without restriction on
disclosure; or
(c)
County receives from a party other than Contractor without restriction on
disclosure.
Notwithstanding anything to the contrary contained above or elsewhere in this
Agreement, County shall have the right to use the Licensed Software and Third
Party Software to provide access to the public to the data base, files or
information derived from the use of the Licensed Software and Third Party
Software and/or to generate reports from such data, files or information or to
provide such data, files or information on electronic media to the public where
required or allowed by the laws of the State of Florida or other laws allowing
disclosure by County. Contractor acknowledges and agrees that County is the
owner and custodian of its information and data, whether or not such is
electronically retained and regardless of the retention media and that the use of
the Licensed Software and Third Party Software in relation to such information or
data does not in any way restrict County in County's rights of disclosure of its
data and information.
ARTICLE 12
TESTING, ACCEPTANCE OR REJECTION OF THE SYSTEM
12.1
There shall be testing periods during which the System can be tested/used by
County. The purpose of the testing periods is to permit County to determine
whether the System has been properly installed as defined at that point in time
so that it:
12.1.1 Properly functions in accordance with the Agreement, Statement of Work
and Acceptance Criteria and provides the capabilities described therein;
12.1.2 Properly functions together with the operating Software, if any, and other
items as described in the Documentation so as to provide the functions
described in the Documentation;
12.1.3 Properly functions in accordance with the Documentation and provides
the capabilities described therein; and
12.1.4 Properly functions as a part of the Hardware configurations as agreed
upon, by and between Contractor and County.
AIMS System and Services Agreement
Page 26 of 60
Exhibit 3
Page 27 of 278
12.2
There are three testing periods: Factory Acceptance Testing, Performance
Verification Testing, and Endurance Testing. Each of these tests is further
defined in Exhibit A.
12.3
During any testing period, County may, at its option, notify Contractor in writing of
any defect or malfunction within a reasonable time after it is determined such
exists so that Contractor, at its option, can commence making any needed
changes, modifications, adjustments or repairs to the System or parts thereof.
County shall notify Contractor of its Preliminary Acceptance or rejection of the
System, or any part thereof, within fifteen (15) County Work Days after the end of
any testing period. If County rejects the System, or any part thereof, it shall
specify the reasons therefore which reasons shall specify the Acceptance Criteria
that the System failed to meet. Upon receiving the notice of rejection, Contractor
shall have fifteen (15) County Work Days (or such length of time as mutually
agreed by the parties) after receipt of notice within which to either (a) modify,
repair, adjust or replace the System or any portion thereof, or (b) set forth the
reasons the System or portion thereof meet the Acceptance Criteria specified in
County’s notice. Any dispute as to whether the System or portion thereof
complies shall be determined pursuant to Article 13 of this System Agreement. If
Contractor modifies, repairs, adjusts or replaces the System or portion thereof,
then County shall have fifteen (15) additional County Work Days to retest the
System, or portion thereof, to confirm its proper operation and shall notify
Contractor of any rejection or Preliminary Acceptance in the same manner as
specified above.
12.4
In the event that for any testing period, Contractor is unable to remedy the
reason or reason(s) for rejection, or any part thereof, within fifteen (15) County
Work Days (or such length of time as mutually agreed by the parties pursuant to
12.3, above) after receipt of County’s initial notification, County shall elect either
to accept the System as it then exists or reject the System and terminate the
System Agreement and the License Agreement. If County elects to accept the
System as it then exists (partial acceptance), Contractor shall continue to remedy
the reason(s) for County’s partial acceptance and shall provide County with the
complete System meeting the Acceptance Criteria set out in the System
Agreement, prior to any final payment being made by County. If Contractor fails
to remedy the reason(s) for County’s partial acceptance within thirty (30) County
Work Days (or such length of time as mutually agreed by the parties after
Contractor’s receipt of County’s partial acceptance notification, including testing
by County, then County shall be entitled to deduct from any final payment, or be
paid by Contractor, the value of the rejected portion of the System as mutually
determined by the Contract Administrator and Contractor. In the event the
parties cannot mutually agree to such a value within thirty (30) County Work
Days after Contractor’s receipt of County’s partial acceptance notification, then
all retainage held by County as set forth in Article 6 shall be retained or paid to
County as reimbursement for accepting a System that has failed to meet the
Acceptance Criteria. If County elects to reject the System as a whole and
terminate this System Agreement and the License Agreement, Contractor shall
AIMS System and Services Agreement
Page 27 of 60
Exhibit 3
Page 28 of 278
refund to County any and all monies paid by County to Contractor under the
System Agreement and the License Agreement within fifteen (15) County Work
Days after the notice of termination. In the event of termination by County
pursuant to this Section 12.4, and after full repayment by Contractor, County
shall return the items, their Documentation, if any, and any other tangible
materials received from Contractor and promptly remove any Software provided
by Contractor from any and all Hardware upon which such may reside and the
System Agreement and the License Agreement, including any license granted by
Contractor, shall automatically terminate.
ARTICLE 13
RESOLUTION OF DISPUTES
13.1
To provide a means of resolving disputes, reducing delays in performance and
lessening the likelihood of litigation, it is agreed by the parties hereto that all
questions, claims, difficulties and disputes of whatever nature which may arise
relative to the provisions of this System Agreement will first be submitted in
writing to the Contract Administrator, the Consultant and the designated
representative of Contractor who will meet and confer in good faith in an effort to
resolve the matter. Such claims, questions, difficulties and disputes shall be
submitted to the referenced individuals in writing as soon as practicable after the
issue arises.
13.2
In the event a dispute between the Contract Administrator and Contractor arises
over whether requested Services constitute additional work or Services or is
outside the level of effort originally anticipated in Exhibit A and such dispute
cannot be resolved by the Contract Administrator, the Consultant and Contractor,
such dispute shall be promptly presented for resolution pursuant to the
procedures set forth in this Article 13. During the pendency of any dispute, if
requested in writing by the Contract Administrator, Contractor shall promptly
perform the disputed Services.
13.3
In the event a dispute between the Contract Administrator and Contractor cannot
be resolved by the Contract Administrator and Contractor, such dispute shall be
presented to the Aviation Director for resolution. In the event the Contractor
does not agree with the Aviation Director’s decision, the Contractor shall file a
written notice of dispute with the Director of Purchasing, in writing, within seven
(7) calendar days from the date of the Aviation Director’s decision, which notice
of dispute shall be filed in accordance with Subsection 21.22.d of the Broward
County Administrative Code. Proceedings regarding such dispute shall be
conducted pursuant to Subsection 21.22.d of the Broward County Administrative
Code. During the pendency of any dispute, Contractor shall promptly perform
the disputed Services and Contractor and County shall act in good faith to
mitigate any potential damages or delays in the project referenced in this System
Agreement.
AIMS System and Services Agreement
Page 28 of 60
Exhibit 3
Page 29 of 278
13.4
In the event a determination of a dispute pursuant to Section 13.3 is
unacceptable to any of the parties hereto, the party objecting to the determination
must notify the other party and the Director of Purchasing in writing within ten
(10) calendar days of receipt of the written determination. The notice must state
the basis of the objection and must be accompanied by a statement that any
Contract price adjustment claimed is the entire adjustment to which the objecting
party has reason to believe it is entitled to as a result of the determination.
Within sixty (60) calendar days after such notice, the parties may participate in
mediation to address all objections to any mediator mutually agreed upon by the
parties. Should any objection not be resolved in mediation, the parties retain all
their legal rights and remedies provided under state law. If the parties agree to
mediation, the prevailing party shall be entitled to reimbursement of any costs of
mediation incurred by such prevailing party.
ARTICLE 14
DATE STANDARDS
Contractor warrants that each item of Software that it delivers, develops, modifies, or
recommends to County for use under the Agreement shall be able to accurately store
and process date/time data in four (4) digit year fields (including, but not limited to,
calculating, comparing, interfacing and sequencing) from, into, and between the
fourteenth through the twenty-second centuries, and leap year calculations. The
duration of this warranty and the remedies available to County for breach of this
warranty shall be as defined in, and subject to, the terms and limitations of Contractor’s
warranties contained in the Agreement; provided that notwithstanding any provision to
the contrary in any such warranty provision(s), or in the absence of any such warranty
provision(s), the remedies available to County under this warranty shall include repair or
replacement, at no cost to County of any of the products whose noncompliance is
discovered and made known to Contractor in writing, within three (3) years after Final
Acceptance of the System by County. Nothing in this warranty shall be construed to
limit any rights or remedies County may otherwise have under the Agreement with
respect to defects.
ARTICLE 15
WORK MADE FOR HIRE
"Custom Work Products" means all finished or unfinished documents, data, studies,
maps, models, photographs, reports, etc., or any portions thereof, (including all
information, ideas, results, data, improvements, developments, functional and technical
designs, routines, subroutines, data diagrams and the like) created by Contractor after
the Effective Date which are the result of or derived from any of the Services provided
by Contractor in furtherance of the work performed under Exhibit A, "Statement of
Work," or other Services rendered to County under this System Agreement. "Custom
Work Products" also means application Software or computer programs, documentation
and technical information or any portions thereof, finished or unfinished, (including any
project specific information, ideas, results, data, improvements, developments,
AIMS System and Services Agreement
Page 29 of 60
Exhibit 3
Page 30 of 278
functional and technical designs, routines, subroutines, modules, flowcharts, data
diagrams, and documentation), created by Contractor after the Effective Date which are
the result of the Services provided by Contractor under this System Agreement. For the
purposes of this System Agreement, County shall own all right, title and interest to all
Custom Work Products which are clearly identified as Deliverables in Exhibit A,
"Statement of Work," to this System Agreement. Contractor expressly acknowledges
and agrees that the Custom Work Products shall be deemed to constitute "work made
for hire" under the Federal copyright laws (17 USC Sec. 101) and, alternatively,
Contractor hereby exclusively and irrevocably assigns all ownership or other rights
Contractor might have in Custom Work Products to County. Without limiting the
foregoing, Contractor shall: (a) assign and transmit all Custom Works Products only to
County; (b) regard the Custom Work Products as County’s exclusive property; and (c)
maintain the Custom Work Products as confidential and shall not disclose the same to
any other person or entity without County's written consent. Without limiting the
foregoing, it is understood and agreed that County may assign, transfer or otherwise
convey the Custom Work Products to others without restriction. Except for Custom
Work Products specifically identified as such in Exhibit A, "Statement of Work," to this
System Agreement, the term "Custom Work Products" shall not include the Licensed
Agreement, or any released modifications, enhancements, Upgrades, or Updates to
such Software that are created by Contractor generally for Contractor's customers, or
any copyrighted Software of Contractor or a third party, or any previously developed
trade secret, previously developed copyrighted material, or other previously developed
proprietary material of Contractor, or any modifications or changes to Contractor’s
Licensed Software. Where applicable, Contractor will provide County with the source
code and object code for Custom Work Products upon Final Acceptance of the System
or within thirty (30) calendar days after receipt of a written request by the Contract
Administrator.
ARTICLE 16
ADDITIONAL SERVICES, CHANGES IN STATEMENT OF WORK,
CHANGE ORDERS
16.1
County or Contractor may request changes that would increase, decrease, or
otherwise modify the Statement of Work. Such changes must be made in
accordance with the provisions of the Broward County Procurement Code and
must be contained in a written document executed by the parties hereto prior to
any deviation from the terms of this System Agreement.
16.2
The budget for this Contract includes a budgeted change order allowance
amount. Changes in the quantity or character of the work within the scope of this
Agreement which are not properly the subject of field orders or supplemental
instructions, including all changes resulting in changes in the compensation, or
the Contract time, shall be authorized only by written change orders approved
and issued in accordance with the provisions of this Article 16 and the County
Procurement Code, as amended from time to time. Pursuant to the County
Procurement Code, all changes must be approved in advance in accordance with
AIMS System and Services Agreement
Page 30 of 60
Exhibit 3
Page 31 of 278
the value of the change order or the calculated value of the time extension. All
change orders with a value of Two Hundred Fifty Thousand Dollars
($250,000.00) or more shall be approved in advance by the Board of County
Commissioners. All change orders with a value of less than Two Hundred Fifty
Thousand Dollars ($250,000.00) must be approved in advance by the Director of
Aviation.
16.3
Change orders and additional Services shall be at the rates and costs set forth
on Exhibits D and E. When both additions and decreases are involved in any
one change order, the combined effect shall be figured on the basis of the net
change in the compensation, if any.
16.4
Contractor shall not start work on any changes requiring an increase in the
compensation or the Contract time until a change order setting forth the
adjustments is approved and issued by the County. Upon receipt of a change
order, Contractor shall promptly proceed with the work set forth within the
document.
16.5
In the event satisfactory adjustment cannot be reached for any item requiring a
change in the compensation or Contract time, and a change order has not been
issued, County reserves the right at its sole option to either terminate the
Agreement as it applies to the items in question and make such arrangements as
may be deemed necessary to complete the disputed work, or submit the matter
in dispute to Consultant as set forth in Article 13 of this Agreement. During the
pendency of the dispute, and upon receipt of a change order, Contractor shall
promptly proceed with the change in the work involved and advise the Consultant
and Contract Administrator in writing within five (5) calendar days of Contractor's
agreement or disagreement with the method, if any, provided in the change order
for determining the proposed adjustment in the compensation or Contract time.
16.6
To avoid delays to completion of the Statement of Work and to mitigate damages
to the parties, change orders may be issued unilaterally by County, under
circumstances determined necessary by the Contract Administrator.
16.7
Value of Change Order Work. The value of any work covered by a change
order or of any claim for an increase or decrease in the Contract price shall be
determined in one of the following ways:
16.7.1 Unit Price. Where the work involved is covered by rates and costs in
Exhibits D and E, by application of such rates and costs.
16.7.2 Lump Sum. By mutual acceptance of a lump sum which Contractor and
County acknowledge contains a component for overhead and profit.
Whenever a change in the work is to be based on mutual acceptance of
a lump sum, whether the amount is an addition, credit or no change-in-
AIMS System and Services Agreement
Page 31 of 60
Exhibit 3
Page 32 of 278
cost, Contractor shall submit an initial cost estimate acceptable to
Contract Administrator or designee.
(a)
The breakdown shall list the quantities and unit costs for materials,
labor, equipment and other items of cost.
(b)
Whenever a change involves Contractor and one or more
subcontractors and the change is an increase in the Contract price,
overhead and profit percentage for Contractor and each
subcontractor shall be itemized separately.
16.7.3 Each change order must state within the body of the change order
whether it is based upon unit price or lump sum.
16.8
Notification and Claim for Change of Contract Time or Contract Price.
16.8.1 Any claim for a change in the Contract time or Contract price shall be
made by written notice by Contractor to the Contract Administrator within
five (5) calendar days of the commencement of the event giving rise to
the claim and stating the general nature and cause of the claim.
Thereafter, within twenty (20) calendar days of the termination of the
event giving rise to the claim, written notice of the extent of the claim
with supporting information and documentation shall be provided unless
Contract Administrator or designee allows an additional period of time to
ascertain more accurate data in support of the claim and such notice
shall be accompanied by Contractor's written notarized statement that
the adjustment claimed is the entire adjustment to which the Contractor
has reason to believe it is entitled as a result of the occurrence of said
event. All claims for changes in the Contract time or Contract price shall
be determined by Contract Administrator in accordance with this Article
16, if County and Contractor cannot otherwise agree and any dispute
shall be resolved in accordance with Articles 13 and 16. IT IS
EXPRESSLY AND SPECIFICALLY AGREED THAT ANY AND ALL
CLAIMS FOR CHANGES TO THE CONTRACT TIME OR CONTRACT
PRICE SHALL BE WAIVED IF NOT SUBMITTED IN STRICT
ACCORDANCE WITH THE REQUIREMENTS OF THIS SECTION.
16.8.2 The Contract time will be extended in an amount equal to time lost on
critical work items due to delays beyond the control of and through no
fault or negligence of Contractor or any of its subcontractors if a claim is
made therefor as provided in this Article 16. Such delays shall include,
but not be limited to, acts or neglect by any separate contractor
employed by County, fires, floods, labor disputes, epidemics, abnormal
weather conditions or acts of God.
AIMS System and Services Agreement
Page 32 of 60
Exhibit 3
Page 33 of 278
16.9
No Damages for Delay.
No claim for damages or any claim, other than for an extension of time, shall be
made or asserted against County by reason of any delays except as provided
herein. Contractor shall not be entitled to an increase in the Contract price or
payment or compensation of any kind from County for direct, indirect,
consequential impact or other costs, expenses or damages, including but not
limited to costs of acceleration or inefficiency, arising because of delay,
disruption, interference or hindrance from any cause whatsoever, whether such
delay, disruption, interference or hindrance be reasonable or unreasonable,
foreseeable or unforeseeable, or avoidable or unavoidable; provided, however,
that this provision shall not preclude recovery of damages by Contractor for
actual delays due solely to fraud, bad faith or active interference on the part of
County or the Consultant or its Contractor Administrator or designee. Otherwise,
Contractor shall be entitled only to extensions of the Contract time as the sole
and exclusive remedy for such resulting delay, in accordance with and to the
extent specifically provided above.
16.10 Excusable Delay; Compensable; Non-Compensable.
16.10.1 Excusable Delay. Delay which extends the completion of the work and
which is caused by circumstances beyond the control of Contractor or its
subcontractors, suppliers or vendors are Excusable Delay. Contractor is
entitled to a time extension of the Contract time for each day the work is
delayed due to Excusable Delay. Contractor shall document its claim for
any time extension as provided in this Article 16. Failure of Contractor to
comply with this Article 16 as to any particular event of delay shall be
deemed conclusively to constitute a waiver, abandonment or
relinquishment of any and all claims resulting from that particular event
of delay. Excusable Delay may be compensable or non-compensable:
16.10.2 Compensable Excusable Delay. Excusable Delay is compensable
when (i) the delay extends the Contract time, (ii) is caused by
circumstances beyond the control of the Contractor or its subcontractors,
suppliers or vendors, and (iii) is caused solely by fraud, bad faith or
active interference on the part of County or its agents. In no event shall
Contractor be compensated for interim delays which do not extend the
Contract time. Contractor shall be entitled to its direct costs for
Compensable Excusable Delay. Direct costs recoverable by Contractor
shall be limited to its actual additional costs.
16.10.3 Non-Compensable Excusable Delay When Excusable Delay is
(i) caused by circumstances beyond the control of Contractor, its
subcontractors, suppliers and vendors, and is also caused by
circumstances beyond the control of the County or its Consultant, or
Contract Administrator or designee or (ii) is caused jointly or concurrently
AIMS System and Services Agreement
Page 33 of 60
Exhibit 3
Page 34 of 278
by Contractor or its subcontractors, suppliers or vendors and by the
County or Consultant, or Contract Administrator or designee, then
Contractor shall be entitled only to a time extension and no further
compensation for the delay.
16.11 Each proposed modification request that, by itself or aggregated with previous
modification requests, increases the Contract value by ten percent (10%) or more
of the initial Contract value, or Fifty Thousand Dollars ($50,000.00), whichever is
less, shall be reviewed by County for opportunities to include or increase CBE
participation. Contractor shall demonstrate good faith efforts to include CBE
participation in change order work and shall report such efforts to the Small
Business Development Division.
ARTICLE 17
EEO AND CBE COMPLIANCE
17.1 NONDISCRIMINATION, EQUAL EMPLOYMENT OPPORTUNITY, AND
AMERICANS WITH DISABILITIES ACT.
17.1.1 Contractor shall not unlawfully discriminate against any employee or
applicant for employment because of race, religion, age, color, sex or
national origin, sexual orientation (including but not limited to Broward
County Code, Chapter 16½), marital status, political affiliation, or
physical or mental disability if qualified. Contractor shall take affirmative
action to ensure that applicants are employed, and that employees are
treated during their employment without regard to their race, religion,
color, sex or national origin, sexual orientation, marital status, political
affiliation, or physical or mental disability. Such actions shall include, but
not be limited to the following: employment, upgrading, demotion, or
transfer, recruitment or recruitment advertising, layoff or termination,
rates of pay or other forms of compensation; and selection of training,
including apprenticeship. Contractor agrees to post in conspicuous
places available to employees and applicants for employment, notices
setting forth the provisions of this non-discrimination clause.
17.1.2 The Contractor shall also require that any subcontractor selected to
perform Services on a County project include the foregoing or similar
language in its contracts with any subcontractors, except that any project
funded from sources as defined in 49 CFR Section 26.3 shall comply
with the requirements of 49 CFR Parts 23 and 26, as amended and as
applicable. The subcontractors, if any, will be made aware of and will
comply with this nondiscrimination clause. Failure to comply with above
requirements is a material breach of the Contract, and may result in the
termination of this Contract or such other remedy as the County deems
appropriate.
AIMS System and Services Agreement
Page 34 of 60
Exhibit 3
Page 35 of 278
17.1.3 Contractor shall comply with Title I of the Americans with Disabilities Act
regarding nondiscrimination on the basis of disability in employment and
further shall not discriminate against any employee or applicant for
employment because of race, age, religion, color, gender, sexual
orientation, national origin, marital status, political affiliation, or physical
or mental disability. In addition, Contractor shall take affirmative steps to
ensure nondiscrimination in employment against disabled persons. Such
actions shall include, but not be limited to, the following: employment,
upgrading, demotion, transfer, recruitment or recruitment advertising,
layoff, termination, rates of pay, other forms of compensation, terms and
conditions of employment, training (including apprenticeship) and
accessibility.
17.1.4 Contractor shall take affirmative action to ensure that applicants are
employed and employees are treated without regard to race, age,
religion, color, gender, sexual orientation (Broward County Code,
Chapter 16½), national origin, marital status, political affiliation, or
physical or mental disability during employment. Such actions shall
include, but not be limited to, the following: employment, upgrading,
demotion, transfer, recruitment or recruitment advertising, layoff,
termination, rates of pay, other forms of compensation, terms and
conditions of employment, training (including apprenticeship), and
accessibility.
17.1.5 Contractor shall not engage in or commit any discriminatory practice in
violation of the Broward County Human Rights Act (Broward County
Code, Chapter 16½) in performing the Statement of Work or Services
under this Agreement.
17.1.6 By execution of this Agreement, Contractor represents that it has not
been placed on the discriminatory vendor list (as provided in Section
287.134, Florida Statutes). County hereby materially relies on such
representation in entering into this Agreement. An untrue representation
of the foregoing shall entitle County to terminate this Agreement and
recover from Contractor all monies paid by County pursuant to this
Agreement, and may result in debarment from County’s competitive
procurement activities.
17.1.7 Contractor agrees to abide by the nondiscrimination requirements set
forth on Attachment I, attached hereto and made a part hereof.
17.2
COUNTY BUSINESS ENTERPRISE PROGRAM ("CBE") COMPLIANCE.
17.2.1 The County Business Enterprise Act of 2009 (Broward County
Ordinance No. 2009-40) ("Business Enterprise Act") establishes the
County's policy for participation by small Broward-based firms in County
AIMS System and Services Agreement
Page 35 of 60
Exhibit 3
Page 36 of 278
contracting opportunities. Contractor agrees to and shall comply with the
Business Enterprise Act. The County shall review each proposed
modification to this System Agreement that, by itself or aggregated with
previous modifications, increase the Contract value of this System
Agreement by ten percent (10%) of the initial Contract value, or Fifty
Thousand Dollars ($50,000) whichever is less, for opportunities to
include or increase the participation of CBE’s.
17.2.2
The Participation goals for this System Agreement is sixteen percent
(16%).
17.2.3
Contractor has committed to the CBE performance delineated on the
attached Exhibit J-1, "Schedule of CBE Participation" which indicates
the names, addresses, scope of services and dollar value or
percentage of participation. Contractor understands that each CBE
firm utilized on the project to meet County's participation goal must be
certified by County.
17.2.4
County and Contractor agree that prime and subcontract awards to
CBE’s are crucial to the achievement of County's participation goals. In
an effort to assist County in achieving its established goal for this
project, Contractor agrees to take affirmative actions to meet the
current CBE participation goal established by County.
17.2.5
Unless the time for submission of same is extended in writing by the
Broward County Small Business Development Division, a Letter of
Intent to perform as a subcontractor executed by each CBE
subcontractor listed on the Schedule of CBE Participation must be
submitted to the Broward County Small Business Development
Division prior to execution of this System Agreement. A Letter of Intent
form may be obtained at the Broward County Small Business
Development Division office. The information contained within the
Letter of Intent and the information contained within the Schedule of
CBE Participation should be the same as to content.
17.2.6
Contractor understands that it is the responsibility of the Contract
Administrator and the Broward County Small Business Development
Division to monitor compliance with the CBE requirements.
(a)
Contractor shall submit with each invoice a Certification of
Payments to Subcontractors and Suppliers, using the form
attached as Exhibit J-2 for all subcontractors, including CBE and
non-CBE subcontractors. The certification shall be accompanied
by a copy of the notification sent to each subcontractor and
supplier listed in paragraph 2 of the form, explaining the good
cause why payment has not been made. In that regard,
AIMS System and Services Agreement
Page 36 of 60
Exhibit 3
Page 37 of 278
Contractor agrees to furnish an updated CBE Utilization Report
(Exhibit J-3) to the Contract Administrator with each invoice for
payment or upon request of the Contract Administrator or the
Broward County Small Business Development Division, showing
all expenditures made to achieve compliance with its assigned
goals or other contractual conditions agreed to by Contractor
pursuant to the County Business Enterprise Act of 2009. All
reports shall include the name, business address, description of
the Services performed, or product supplied by each CBE; the
date and amount of each expenditure; verification of the CBE
status of any contractor performing any portion of this System
Agreement; and any other information requested by County
which may assist County in determining the Contractor’s
compliance with its contractual obligations, or may assist in the
implementation and enforcement of the County Business
Enterprise Act of 2009.
(b)
17.2.7
The Final CBE Utilization Report (Exhibit J-4) must be submitted
with the final invoice for payment (in lieu of Exhibit J-3), listing
only those subcontractors certified as CBE's, to show
expenditures made to date to achieve compliance with the
assigned CBE goal. The submission of the reports required by
this subparagraph shall be a condition of payment to Contractor.
In the event of Contractor’s noncompliance with its participation
commitment to a CBE (including without limitation the unexcused
reduction of CBE participation), the affected CBE shall have the right
to exercise the following remedies if the noncompliance is or was due
to no fault of the CBE, and due to the willful action or omission of
Contractor:
(a)
The affected CBE shall be entitled to damages pursuant to its
agreement with Contractor.
(b)
If a subcontractor, material supplier, or other similarly-situated
person institutes an arbitration proceeding claiming noncompliance with the County Business Enterprise Act of 2009 by
Contractor, then only in such event shall the remedies include an
undertaking by Contractor to submit any dispute concerning such
damages to binding arbitration by an independent arbitrator.
However, binding arbitration shall not be available as to any
dispute between Contractor and County; nor shall County incur
any cost, fee, or liability relative to any arbitration proceedings.
An arbitrator may award reasonable attorney's fees and costs
against a non-prevailing party.
AIMS System and Services Agreement
Page 37 of 60
Exhibit 3
Page 38 of 278
(c)
Nothing under this Section 17.2 shall be construed to limit the
rights of and remedies available to County, including the right to
seek its own damages pursuant to this System Agreement.
17.2.8
County shall have access, without limitation, to Contractor’s books and
records, including payroll records, tax returns and records, and books
of account, on five (5) calendar day’s notice, to allow County to
determine Contractor’s compliance with its commitment to the CBE
participation goal and the status of any CBE performing any portion of
this System Agreement.
17.2.9
Upon request by the Contract Administrator, Contractor agrees to
furnish the County with a copy of its Affirmative Action Policy.
17.2.10
The Contractor must inform the Broward County Small Business
Development Division immediately, in writing, when a CBE
subcontractor is not able to perform. If the Contractor is unable to
substitute the unavailable CBE with another certified CBE, the actual
substitute of a non- CBE subcontractor may not occur until the
Broward County Small Business Development Division has verified the
good faith efforts of the Contractor to substitute the unavailable CBE
with another certified CBE.
17.2.11
Contractor shall pay its subcontractors and suppliers within ten (10)
calendar days following receipt of payment from the County for such
subcontractors Services or supplies. Contractor agrees that if it
withholds an amount as retainage from its subcontractors or suppliers,
that it will release such retainage and pay same within ten (10)
calendar days following receipt of payment of retained amounts from
County.
17.2.12
Contractor agrees that it cannot terminate a CBE subcontractor for
convenience and then perform the Services with its own forces or its
affiliate. If a situation arises that a CBE subcontractor needs to be
replaced or removed from the team, Contractor must submit a written
request to the Small Business Development Division with detailed
explanation or justification for the submission of such request. If the
request is due to a voluntary cessation of the CBE firm from the team,
documentation supporting the voluntary cessation must accompany the
request. Requests for substitution or termination of CBE subcontractors
will only be approved on a case-by-case basis, provided that reasons
cited are properly justified. When a CBE subcontractor is terminated, or
fails to complete its Services, Contractor must make good faith efforts to
find another CBE subcontractor to substitute for the original CBE.
17.2.13
Contractor agrees that nonpayment of a CBE subcontractor or supplier
as required by Subsection 17.2.11 shall be a material breach of this
AIMS System and Services Agreement
Page 38 of 60
Exhibit 3
Page 39 of 278
System Agreement and that County’s Contract Administrator may, at
its option, increase allowable retainage or withhold progress payments
unless and until Contractor demonstrates timely payments of sums due
to such subcontractors or suppliers. Contractor agrees that the
presence of a "pay when paid" provision in a subcontract shall not
preclude County or its representatives from inquiring into allegations of
nonpayment. The foregoing remedies under this Section 17.2 shall not
be employed when Contractor demonstrates that failure to pay results
from a bona fide dispute with its subcontractor or supplier.
ARTICLE 18
INSURANCE
18.1
Contractor shall, at a minimum, provide, pay for, and maintain in force at all times
during the term of this System Agreement (unless otherwise provided), the
insurance coverages set forth below in accordance with the terms and conditions
required by this Article.
18.2
Such policy or policies shall be without any deductible amount unless otherwise
noted in this System Agreement.
18.3
Such policy or policies shall be issued by approved companies authorized to do
business in the State of Florida and having agents upon whom service of process
may be made in the State of Florida. Contractor shall specifically protect County
and the Broward County Board of County Commissioners by naming County and
the Broward County Board of County Commissioners as additional insureds
under the Comprehensive General or Commercial Liability Insurance policy
hereinafter described, as well as on excess liability.
18.3.1 Professional Liability Insurance shall be provided with the limits of
liability provided by such policy to be no less than Two Million Dollars
($2,000,000.00) each claim, with a maximum deductible of $150,000.00.
Contractor shall be responsible for the deductible.
Contractor shall notify County in writing within thirty (30) calendar
days of any claims filed or made against the Professional Liability
Insurance Policy.
18.3.2 Workers' Compensation Insurance shall be provided to apply for all
employees in compliance with Chapter 440, Florida Statutes, as
amended, the "Workers' Compensation Law" of the State of Florida and
all applicable federal laws.
18.3.3 Comprehensive General or Commercial Liability Insurance with
minimum limits of Two Million Dollars ($2,000,000.00) per occurrence
combined single limit for Bodily Injury Liability and Property Damage
AIMS System and Services Agreement
Page 39 of 60
Exhibit 3
Page 40 of 278
Liability and Five Million Dollars ($5,000,000.00) in the aggregate.
Coverage must be afforded on a form no more restrictive than the latest
edition of the Commercial General Liability Policy, without restrictive
endorsements, as filed by the Insurance Services Office, and must
include:
Premises and/or Operations.
Independent Contractors.
Broad Form Property Damage.
Products/Completed Operations Hazard.
Broad Form Contractual Coverage applicable to this specific
System Agreement.
Personal Injury Coverage with Employee and Contractual
Exclusions removed with minimum limits of coverage equal to those
required for Bodily Injury Liability and Property Damage Liability.
18.3.4 Business Automobile Liability Insurance shall be provided with minimum
limits of Five Million Dollars ($5,000,000.00) per occurrence combined
single limit for Bodily Injury Liability and Property Damage Liability.
Coverage must be afforded on a form no more restrictive than the latest
edition of the Business Automobile Liability Policy, without restrictive
endorsements, as filed by the Insurance Services Office and must
include:
Comprehensive Form
Owned vehicles
Hired and non-owned vehicles
Any Auto, if applicable
Employers' non-ownership
18.4
Contractor shall provide to the County Risk Management Division certificate(s) of
insurance for all insurance policies required by this Article including any
subsection thereunder within ten (10) calendar days prior to the commencement
of the Contractor’s work as described herein, which certificate(s) of insurance
must be satisfactory to the Risk Management Division in all
respects. Certificate(s) of said insurance shall be in the form attached as Exhibit
H. County reserves the right to require a certified copy of such policies upon
request. All certificates and endorsements required herein shall state that
County shall be given at least thirty (30) calendar days notice prior to expiration,
cancellation or restriction of the policy. If any of the insurance coverages will
expire prior to the completion of the work, copies of renewal certificates shall be
furnished at least thirty (30) calendar days prior to the date of their expiration.
Any insurance coverage that is written on a "claims made" basis must remain in
force for two (2) years after the acceptance of the project by the County.
AIMS System and Services Agreement
Page 40 of 60
Exhibit 3
Page 41 of 278
18.5
Additional Insured. Contractor agrees to endorse County as additional insured
to the Commercial General Liability, Umbrella or Excess Liability. The additional
insured shall read "Broward County Board of County Commissioners, Florida."
18.6
Right to Revise or Reject. Broward County’s Risk Management Division
reserves the right, but not the obligation, to review and revise any insurance
requirements at the time of Contract renewal or any amendments, including but
not limited to, deductibles, limits, coverages and endorsements based on
insurance market conditions affecting the availability or affordability of coverage,
or changes in the scope of work/specifications affecting the applicability of
coverage.
ARTICLE 19
DOCUMENTATION
19.1
Contractor agrees to provide County with all Documentation in electronic format,
and, hereby grants County permission to copy or reproduce, in whatever form,
electronic, machine readable, hard copy or otherwise, any Documentation
supplied by it to County, including material related to subsequent Upgrades,
Updates and enhancements. County agrees to make only the number of copies
of the material as may be necessary to meet the reasonable business and
governmental needs of County. Under no circumstances will County sell or
distribute any copies of the Documentation, including copies made, to other than
its employees or individuals assisting County in its business or governmental
operations. County shall include on all copies or reproductions the copyright
inscription of Contractor which is contained in the original Documentation.
19.2
Contractor agrees to provide County with revised, modified, and/or updated
Documentation that reflects the enhancements, changes, modifications resulting
from any Work for Hire undertaken pursuant to this System Agreement.
ARTICLE 20
MISCELLANEOUS PROVISIONS
20.1
Ownership of Documents. All finished or unfinished documents, data, studies,
surveys, drawings, maps, models, photographs and reports prepared or provided
by Contractor in connection with this System Agreement are and shall become
the property of County, whether the project for which they are made is completed
or not, and shall be delivered by Contractor to County in the requested form or
format within seven (7) calendar days of the earlier to occur of: (i) written request
from the Contract Administrator, or (ii) the termination of the System Agreement
by either party.
20.1.1
If any funding for the System Agreement is provided by the Federal
Aviation Administration (FAA) or any other federal agency, then all
rights to inventions and materials generated under this Contract are
subject to regulations issued by the FAA or any such other federal
AIMS System and Services Agreement
Page 41 of 60
Exhibit 3
Page 42 of 278
agency, and the sponsor of any grant under which this Contract is
executed. Information regarding these rights is available from the FAA
and the sponsor.
20.2
20.1.2
County may withhold any payments then due to Contractor until
Contractor complies with the provisions of this section.
20.1.3
Tangible items of non-consumed equipment, materials, supplies and
furnishings purchased by the Contractor and its subcontractors, the
costs of which have been reimbursed to the Contractor as a direct
cost, shall be turned over to the County at completion or earlier
termination of the System Agreement, or disposed of as directed by
the Contract Administrator, and the proceeds of any such disposal
shall be credited to, or paid to, the County.
Audit Right and Retention of Records. County shall have the right to audit the
books, records, and accounts of Contractor that are related to the System
Agreement.
20.2.1
Contractor shall keep such books, records and accounts and shall
require any and all subcontractors to keep such books, records and
accounts as may be necessary in order to record complete and correct
entries related to the System Agreement. All books, records and
accounts of Contractor shall be kept in written form, or in a form
capable of conversion into written form within a reasonable time, and
upon request to do so, Contractor shall make same available at no
cost to County in written form. Incomplete or incorrect entries in such
books and records and accounts will be grounds for County's
disallowance and recovery of any amounts based upon such entries.
20.2.2
Contractor shall preserve and make available, at reasonable times for
examination and audit by County, all books, records and accounts
relating to the project and the System Agreement, including without
limitation, financial records, supporting documents, statistical records,
and any other documents pertinent to the System Agreement, all of
which shall be preserved for the required Retention Period (as
hereinafter defined). The "Retention Period" is defined as the greater
of: (i) the required retention period of the Florida Public Records Act
(Chapter 119, Florida Statutes), or if any audit has been initiated and
audit findings have not been resolved at the end of such period, the
books, records and accounts shall be retained until resolution of the
audit findings, or (ii) for a period of three (3) years after final payment
and the completion of all work to be performed pursuant to the System
Agreement, or if any audit has been initiated and audit findings have
not been resolved at the end of the three years, the books, records and
accounts shall be retained until resolution of the audit findings, or (iii) if
AIMS System and Services Agreement
Page 42 of 60
Exhibit 3
Page 43 of 278
the project is subject to Florida Department of Transportation grants,
for a period of five (5) years after final payment and the completion of
all work to be performed pursuant to the System Agreement, or if any
audit has been initiated and audit findings have not been resolved at
the end of the five years, the books, records and accounts shall be
retained until resolution of the audit findings. If the Florida Public
Records Act is determined by County to be applicable to Contractor's
records, Contractor shall comply with all requirements thereof;
however, no confidentiality or non-disclosure requirement of either
federal or state law shall be violated by Contractor.
20.3
20.4
Public Entity Crimes Act. Contractor represents that the execution of the
System Agreement will not violate the Public Entity Crimes Act (Section 287.133,
Florida Statutes), which essentially provides that a person or affiliate who is a
contractor, contractor or other provider and who has been placed on the
convicted vendor list following a conviction for a Public Entity Crime may not
submit a bid on a contract to provide any goods or services to County, may not
submit a bid on a contract with County for the construction or repair of a public
building or public work, may not submit bids on leases of real property to County,
may not be awarded or perform work as a contractor, supplier, or subcontractor
under a contract with County, and may not transact any business with County in
excess of the threshold amount provided in Section 287.017, Florida Statutes, for
category two purchases for a period of 36 months from the date of being placed
on the convicted vendor list.
20.3.1
Violation of this section shall result in termination of the System
Agreement and recovery of all monies paid by County pursuant to the
System Agreement, and may result in debarment from County’s
competitive procurement activities.
20.3.2
In addition to the foregoing, Contractor further represents that there
has been no determination, based on an audit, that it committed an act
defined by Section 287.133, Florida Statutes, as a public entity crime
and that it has not been formally charged with committing an act
defined as a public entity crime regardless of the amount of money
involved or whether Contractor has been placed on the convicted
vendor list.
No Contingent Fee. Contractor warrants that it has not employed or retained
any Contractor or person, other than a bona fide employee working solely for
Contractor, to solicit or secure the System Agreement and that it has not paid or
agreed to pay any person, Contractor, corporation, individual or firm, other than a
bona fide employee working solely for Contractor any fee, commission,
percentage, gift, or other consideration contingent upon or resulting from the
award or making of the System Agreement. For the breach or violation of this
provision, County shall have the right to terminate the System Agreement without
AIMS System and Services Agreement
Page 43 of 60
Exhibit 3
Page 44 of 278
liability at its discretion, to deduct from the Contract price, or otherwise recover,
the full amount of such fee, commission, percentage, gift, or consideration.
20.5
Subcontractors.
20.5.1
Contractor shall utilize the subcontractors identified in the proposal that
was a material part of the selection of Contractor to provide the
Services for the project. The list of subcontractors submitted is set forth
on Exhibit J, and the rates and fees are set forth on Exhibit D.
Contractor shall obtain written approval of Contract Administrator prior
to changing or modifying the list of subcontractors submitted by
Contractor. Where Contractor's failure to use a subcontractor results in
Contractor's noncompliance with CBE participation goals, such failure
shall entitle the affected CBE subcontractor to damages available
under local and state law.
20.5.2
Invoices for any Services performed by any subcontractors shall be
passed through to County without additional charge by the Contractor.
All such Services shall be itemized on invoices from such
subcontractors, showing Services performed and charges incurred.
20.5.3
Contractor shall cause subcontractors to submit a completed Exhibit
D, in the form attached hereto, detailing such rates for authorization
prior to utilizing such subcontractor. Should any subcontractor fail to
submit a completed Exhibit D, in the form attached hereto, or fail to
submit a properly completed Exhibit D, as determined by the County
Auditor, the Contractor shall notify the Broward County Small Business
Development Division ("SBDD") of any such event, and until the failure
is cured the Contractor may withhold payment of any sums due the
subcontractor. In addition, the Contractor may make written request to
the Contract Administrator (with a copy to the County Auditor and the
SBDD) to replace such subcontractor with a subcontractor that is in
compliance with the provisions hereof. If the Contract Administrator
approves any change or modification of subcontractors pursuant
to Subsection 20.5.1, then Exhibits J and D shall be updated
accordingly and attached to this License Agreement by the
Contract Administrator.
20.5.4
Contractor shall bind each and every approved subcontractor to the
terms stated in this System Agreement, provided that this provision
shall not, in and of itself, impose the insurance requirements set forth
in Article 18 on Contractor's subcontractors. Contractor shall be
responsible for recommending to the Broward County Risk
Management Division the insurance coverages it will require of each of
its subcontractors, after taking into consideration the Services to be
provided by each of its subcontractors. The Broward County Risk
AIMS System and Services Agreement
Page 44 of 60
Exhibit 3
Page 45 of 278
Management Division may either (i) accept the recommendation(s) of
the Contractor, or (ii) require any coverages that the Risk Management
Division determines are necessary to protect the County's interests.
Contractor shall require the proper licensing of each of its
subcontractors and shall provide the insurance coverage’s as finally
determined in the sole discretion of the Risk Management Division.
20.5.5
If any of the Services outlined in this System Agreement are furnished
by Contractor by obtaining the Services of subcontractors, Contractor
shall provide County with proposals and contracts between the
subcontractors and Contractor outlining the Services to be performed
and the charges for same, together with any other documentation
required by County.
20.6
Contractor Certification. The Contractor hereby certifies that the System
Agreement is made in good faith, and without fraud, collusion of any kind with
any other contractor for the same work, and that the Contractor is acting solely
on its own behalf without connection with, or obligation to, any undisclosed
person or firm.
20.7
Representative of County and Contractor - Project Managers.
20.8
20.7.1
The parties recognize that questions in the day-to-day conduct of the
project will arise. The Contract Administrator, upon Contractor's
request, shall advise Contractor in writing of County's Project Manager
to whom all matters pertaining to the day-to-day conduct of the project
shall be addressed.
20.7.2
Contractor shall inform the Contract Administrator in writing of
Contractor's Project Manager to whom all matters pertaining to the
day-to-day conduct of the project shall be addressed.
No Conflicts.
20.8.1
The employees and officers of Contractor, its subcontractors, and the
subsidiaries of Contractor and its subcontractors shall not, during the
term of the System Agreement, serve as an expert witness against
County in any legal or administrative proceeding in which he or she or
Contractor is not a party, unless compelled by court process. Further,
Contractor agrees that such persons shall not give sworn testimony or
issue a report or writing, as an expression of his or her expert opinion,
which is adverse or prejudicial to the interests of County or in
connection with any such pending or threatened legal or administrative
proceeding. The limitations of this section shall not preclude such
persons from representing themselves in any action or in any
administrative or legal proceeding.
AIMS System and Services Agreement
Page 45 of 60
Exhibit 3
Page 46 of 278
20.9
20.8.2
Contractor, its subcontractors, and the subsidiaries, officers, and
personnel of Contractor and its subcontractors shall not acquire any
interest in any parcel of land or improvement thereon located within the
Airport boundaries, as described in the Master Plan Update, including
such additional property that may need to be acquired to implement
the development described in the Master Plan Update.
20.8.3
Contractor, its subcontractors, and the subsidiaries, officers and
personnel of Contractor and its subcontractors shall not perform
consulting work or provide legal services that would in any way be in
conflict with the project or detrimental to the project, for any
municipality, developer, tenant or landowner developing or having
property within the Airport boundaries, as described in the Master Plan
Update, including such additional property that may need to be
acquired to implement the development described in the Master Plan
Update. At least ten (10) calendar days prior to undertaking any work
for any of the listed entities, the Contractor shall provide the Contract
Administrator with a written description of the contemplated work and
the Contract Administrator shall promptly advise as to whether such
work would be detrimental to the project or in conflict therewith.
20.8.4
Contractor, its subcontractors, and the subsidiaries, officers, and
personnel of Contractor and its subcontractors shall not have or hold
any continuing or frequently recurring employment or contractual
relationship that is substantially antagonistic or incompatible with such
party's loyal and conscientious exercise of judgment and care related
to its performance under the System Agreement.
20.8.5
In the event Contractor is permitted pursuant to the System Agreement
to utilize subcontractors to perform any Services required by the
System Agreement, Contractor agrees to require such subcontractors,
by written contract, to comply with the provisions of this section.
All Prior Agreements Superseded / Amendments.
20.9.1
The Agreement incorporates and includes and supersedes all prior
negotiations, correspondence, conversations, agreements and
understandings applicable to the matters contained therein and
represents the final and complete understanding of the parties. The
parties agree that there is no commitment, agreement or
understanding concerning the subject matter of the Agreement that is
not contained in the written Agreement. Accordingly, the parties agree
that no deviation from the terms of the Agreement shall be predicated
upon any prior representation or agreement whether oral or written.
AIMS System and Services Agreement
Page 46 of 60
Exhibit 3
Page 47 of 278
20.9.2
No modification, amendment or alteration in the terms or conditions
contained in the Agreement be effective unless set forth in a written
document and executed by the parties hereto.
20.10 Truth-In-Negotiation Certificate. Signature of the System Agreement by
Contractor shall act as the execution of a truth-in-negotiation certificate stating
that wage rates and other factual unit costs supporting the compensation of the
System Agreement are accurate, complete, and current at the time of
contracting. The original Contract price and any additions thereto shall be
adjusted to exclude any significant sums by which County determines the
Contract price was increased due to inaccurate, incomplete, or noncurrent wage
rates and other factual unit costs. All such Contract adjustments shall be made
within one (1) year following the end of the System Agreement.
20.11 Interpretation. The language of this System Agreement has been agreed to by
both parties to express their mutual intent and no rule of strict construction shall
be applied against either party hereto. The headings contained in this System
Agreement are for reference purposes only and shall not affect in any way the
meaning or interpretation of this System Agreement. All personal pronouns used
in this System Agreement shall include the other gender, and the singular shall
include the plural, and vice versa, unless the context otherwise requires. Terms
such as "herein," "hereof," "hereunder," and "hereinafter" refer to this System
Agreement as a whole and not to any particular sentence, paragraph, section or
article where they appear, unless the context otherwise requires. Whenever
reference is made to a sentence, paragraph, section or article of this System
Agreement, such reference is to the sentence, paragraph, section or article as a
whole, including all of the subsections thereof, unless the reference is made to a
particular subsection or subparagraph.
20.12 Contractor's Key Staff.
20.12.1
Contractor will provide the key staff identified on Exhibit G for the
project as long as said key staff are in Contractor's employment.
Contractor's key staff shall not be changed without the prior written
approval of the Contract Administrator as set forth below.
20.12.2
Prior to changing any key staff set forth on Exhibit G, Contractor shall
provide Contract Administrator with such information as necessary to
determine the suitability of proposed new key staff. The Contract
Administrator will be reasonable in evaluating the qualifications of any
proposed key staff.
20.12.3
If Contract Administrator desires to request removal of any of
Contractor's staff, the Contract Administrator shall first meet with
Contractor and provide reasonable justification for said removal.
AIMS System and Services Agreement
Page 47 of 60
Exhibit 3
Page 48 of 278
20.13 Drug-Free Workplace. It is a requirement of County that it enter into contracts
only with firms that certify the establishment of a drug-free work place in
accordance with Chapter 21.31(a) of the Broward County Procurement Code.
Execution of the System Agreement by Contractor shall serve as Contractor's
required certification that it either has or that it will establish a drug-free work
place in accordance with Chapter 21.31(a) of the Broward County Procurement
Code and will continue to maintain same during the term of the System
Agreement.
20.14 Certain Additional Provisions Pertaining To Airport Projects. Contractor
agrees to abide by the provisions pertaining to airport projects set forth on
Attachment II, attached hereto and made a part hereof.
20 .15 Assignment and Subcontract.
20.15.1
County's Limited Right to Transfer. County may, upon prior written
notice to Contractor, assign this System Agreement to a surviving
governmental entity in the event of any change in the manner or form
by which County is organized. Otherwise, without the prior written
consent of Contractor, the County's rights to any licensed programs or
materials shall not be assigned, licensed, or otherwise transferred,
voluntarily or otherwise, by the County, provided that such consent
shall not be unreasonably withheld. Any such assignee must agree in
writing to be bound by all of the terms and conditions of the System
Agreement before any such assignment is effected.
20.15.2
Contractor's Right to Assign. Upon prior written notice to County,
Contractor may assign the System Agreement to an affiliate in
connection with a corporate reorganization. Otherwise, without the
prior written consent of the County, the Contractor shall not assign its
obligations under the System Agreement. The County's Director of
Purchasing is authorized to provide such consent on behalf of the
County.
20.16 Applicable Law, Venue and Waiver of Jury Trial. The System Agreement shall
be interpreted and construed in accordance with and governed by the laws of the
State of Florida. Any controversies or legal problems arising out of the System
Agreement and any action involving the enforcement or interpretation of any
rights hereunder shall be submitted to the jurisdiction of the state courts of the
Seventeenth Judicial Circuit of Broward County, Florida. Venue for litigation
arising out of the System Agreement shall be in such state courts. To encourage
prompt and equitable resolution of any litigation that may arise hereunder, each
party hereby expressly waives any rights it may have to a trial by jury of any civil
litigation related to the System Agreement.
AIMS System and Services Agreement
Page 48 of 60
Exhibit 3
Page 49 of 278
20.17 Taxes. Contractor acknowledges that County is a tax exempt entity and County
agrees to provide Contractor with written proof of such status, if requested.
20.18 Effective Date. This System Agreement is effective upon the date signed by
County.
20.19 Independent Contractor; Third Party Beneficiaries; No Joint Relationship.
20.19.1
Contractor is an independent contractor under the System Agreement.
Services provided by Contractor shall be subject to the supervision of
Contractor. In providing the Services, Contractor, its subcontractors,
and their agents shall not be acting and shall not be deemed as acting
as officers, employees or agents of the County.
20.19.2
The parties expressly acknowledge that it is not their intent to create
any rights or obligations in any third person or entity under the System
Agreement. Neither Contractor nor County intend to directly or
substantially benefit a third party by the System Agreement.
Therefore, the parties agree that there are no third party beneficiaries
to the System Agreement and that no third party shall be entitled to
assert a right or a claim against either of them based upon the System
Agreement.
20.19.3
The System Agreement shall not constitute or make the parties a
partnership or joint venture or create any other joint relationship.
County does not extend to Contractor or Contractor’s subcontractors or
any of their agents any authority of any kind to bind County in any
respect whatsoever.
20.20 Notices and Writings. Whenever either party desires to give notice to the other,
such notice must be in writing, sent by certified United States Mail, postage
prepaid, return receipt requested, or by overnight commercial carrier, return
receipt requested, addressed to the party for whom it is intended at the place last
specified. Transmission by Facsimile (Fax) shall constitute written notice
hereunder. The place for giving notice shall remain the same as set forth herein
until changed in writing in the manner provided in this section. For the present,
the parties designate the following for notice:
AIMS System and Services Agreement
Page 49 of 60
Exhibit 3
Page 50 of 278
BROWARD COUNTY
With a copy to:
Director of Aviation
Aviation Department
100 Aviation Boulevard
Fort Lauderdale, FL 33315
Facsimile : (954) 359-0027
Director of Business
Aviation Department
100 Aviation Boulevard
Fort Lauderdale, FL 33315
Facsimile: (954) 359-1331
CONTRACTOR
Chris Keller
Air-Transport IT Services, Inc.
5950 Hazeltine National Drive
Orlando, FL 32822
Facsimile: 407-370-4657
20.21 Force Majeure. Either party desiring to rely upon such a cause shall, when the
cause arises, give prompt written notice thereof to the other party and, when the
cause ceases to exist, shall give prompt written notice thereof to the other party.
Contractor shall not be liable for any non-delivery or delay in delivering, installing,
repairing, maintaining, and/or servicing any of the items covered by the System
Agreement, if such non-delivery or delay is due to any "Force Majeure Event" (as
hereinafter defined). County shall not be liable for any non-performance or delay
in performing any obligation of County under the System Agreement, if such nonperformance or delay is due to any Force Majeure Event. A "Force Majeure
Event" is defined as one or more of the following events: acts of God, fires,
strikes, acts of vandalism, terrorist act, lockouts, disputes with workers,
epidemics, flood, hurricane, accidents, delays in transportation, shortage of
modes of transportation, labor, fuel or materials, war blockades, embargos,
foreign or domestic governmental regulations or requirements, restraining orders
or decrees of any court or judge, or any other causes whatsoever not within the
control of the party affected by the Force Majeure Event. A "Force Majeure
Event" shall not include any non-delivery or delay in delivering, installing,
repairing, maintaining, and/or servicing any of the items covered by the System
Agreement if such is directly caused by any action or inaction of the party
affected or claiming to be affected by a Force Majeure Event, or any event that
arises or is due to any fault or inaction of such party. In the event of any Force
Majeure Event as to the Contractor's obligations hereunder, the Contractor shall
immediately deliver, install, repair, maintain, and/or service any item covered by
the System Agreement as soon as it is reasonably possible for the Contractor to
undertake such actions.
20.22 Incorporation by Reference. The truth and accuracy of each "Whereas" clause
set forth above is acknowledged by the parties. The attached Exhibits A
through N and Attachments I through III are incorporated into and made a part
of the System Agreement by this reference
AIMS System and Services Agreement
Page 50 of 60
Exhibit 3
Page 51 of 278
20.23 Priority of Provisions. If there is a conflict or inconsistency between any term,
statement, requirement, or provision of any exhibit attached to this System
Agreement, any document or events referred to in this System Agreement, or
any document incorporated into this System Agreement by reference and a term,
statement, requirement, or provision of this System Agreement, the term,
statement, requirement, or provision contained in Articles 1-23 of this System
Agreement shall prevail and be given effect. In the event of any conflict between
any exhibit attached hereto and any other exhibit attached hereto, the following
shall be the order of priority in determining which exhibit shall prevail and be
given effect over another exhibit, with a higher exhibit on the list having priority
over any exhibit that follows it:
Exhibit A
Exhibit B
Exhibit B-1
Exhibit C
Exhibit D
Exhibit E
Exhibit F
Exhibit G
Exhibit H
Exhibit I
Exhibit J
Exhibit J-1
Exhibit J-2
Exhibit J-3
Exhibit J-4
Exhibit K
Exhibit L
Exhibit M
Exhibit N
Attachment I
Attachment II
Attachment III
Statement of Work
Goods and System Hardware
(as it may be updated pursuant to the Agreement)
Existing EVIDS Devices
(as it may be updated pursuant to the Agreement)
Licensed Software and Third Party Software
(as it may be updated pursuant to the Agreement)
Rates and Fees to be Charged by Contractor/Subcontractor
Master Price List
(as it may be updated pursuant to the Agreement)
Payment Schedule
Key Staff
Form Certificate of Insurance
Work Authorization Forms;
Contract Administrator, Purchasing, Board
Schedule of Subcontractor Participation
Schedule of CBE Participation
Certification of Payments to Subcontractors and Suppliers
CBE Utilization Report
Final CBE Utilization Report
Payment Forms
Change Order Form
Optional Services
Form of Performance Bond and Payment Bond
Nondiscrimination Requirements
Provisions Pertaining to Airport Projects
Off Shore Statement
20.24 Representation of Authority. Each individual executing the System Agreement
on behalf of a party hereto does hereby represent that he or she is, on the date
he or she signs the System Agreement, duly authorized by all necessary and
appropriate action to execute the System Agreement on behalf of such party.
AIMS System and Services Agreement
Page 51 of 60
Exhibit 3
Page 52 of 278
20.25 Compliance with Laws. Throughout the term of the System Agreement, the
Contractor shall keep fully informed of all federal, state, County and local laws,
ordinances, codes, rules, and regulations, and all orders and decrees of bodies
or tribunals having jurisdiction or authority which, in any manner, affect work
authorized under the terms of the System Agreement, and shall further take into
account all known pending changes to the foregoing. The Contractor shall at all
times observe and comply with all such laws, ordinances, codes, rules,
regulations, orders, and decrees in performing its duties, responsibilities, and
obligations related to the System Agreement.
20.26 Agreement Severable; Waiver of Breach and Materiality.
20.26.1
In the event the System Agreement or a portion thereof is found by a
court of competent jurisdiction to be invalid, the remaining provisions
shall continue to be effective, unless County or Contractor elects to
terminate the System Agreement. Any election to terminate the
System Agreement based upon this provision shall be made within
seven (7) calendar days after the finding by the court becomes final.
20.26.2
Failure by County to enforce any provision of the System Agreement
shall not be deemed a waiver of such provision or modification of the
System Agreement. A waiver of any breach of a provision of the
System Agreement shall not be deemed a waiver of any subsequent
breach and shall not be construed to be a modification of the terms of
the System Agreement.
20.26.3
County and Contractor agree that each requirement, duty, and
obligation set forth herein is substantial and important to the formation
of the System Agreement and, therefore, is a material term hereof.
20.27 Joint Preparation. The parties acknowledge that they have sought and received
whatever competent advice and counsel necessary for them to form a full and
complete understanding of all rights and obligations herein and that the
preparation of the System Agreement has been their joint effort. The language
agreed to expresses their mutual intent and the resulting document shall not,
solely as a matter of judicial construction, be construed more severely against
one of the parties than any other.
20.28 No Interest. Unless required by the Broward County Prompt Payment
Ordinance, any monies which are the subject of a dispute regarding the System
Agreement and which are not paid by County when claimed to be due shall not
be subject to interest. All requirements inconsistent with this provision are
hereby waived by Contractor.
20.29 References to County. Contractor agrees that during the term of the System
Agreement, Contractor may not reference County in Contractor’s Web site,
AIMS System and Services Agreement
Page 52 of 60
Exhibit 3
Page 53 of 278
and/or press releases, and, may not place County’s name and logo on
Contractor’s Web site or in collateral marketing materials relating to Contractor’s
products and services without the prior written consent of the County. Further,
Contractor agrees that it may not use County’s name, logo or any other
trademarks (including in any press releases, customer "case studies," and the
like) without County’s prior written consent. Termination of the System
Agreement shall not affect Contractor’s obligation in this regard. Additionally,
upon termination or expiration of the System Agreement, Contractor agrees it will
discontinue any previously authorized use of County’s name and/or logo on any
Web site, press release, promotional literature or customer list.
20.30 Most Favored Nation Pricing and Exclusive Arrangement. The parties agree
that the term "Most Favored Nation" shall mean that Services are offered to
County by Contractor on terms and conditions, including price, that are at least
as favorable as those offered to other entities that are comparable in size and
scope to County. Contractor commits that the pricing provided to County shall be
at least as low as for comparable volume levels and similar Services as that
provided to any other Contractor customer. Contractor agrees and covenants
that it shall not enter or offer to enter into an agreement with any other entity to
provide services comparable to the Services in the System Agreement on pricing
terms which are more favorable to such other entity than those set forth in the
System Agreement.
20.31 Time of the Essence. Time is of the essence throughout this System
Agreement.
20.32 Offshore Limitation. Contractor shall not source any development and/or
support for the System Agreement outside the territorial limits of the United
States of America, without the written approval of the Contract Administrator. The
County acknowledges and consents to the matters described on Attachment III,
attached hereto and made a part hereof.
20.33 Remote Access. The parties envision that support to County’s development
and or test environment may be provided by remote electronic means (remote
access). The manner, including any security restrictions, method, equipment,
Software and other considerations for remote access shall be provided by remote
access (high speed on County end) on a request by request basis subject to the
Aviation Department's internal network security policies. Current Aviation
Department policy prohibits the use of direct remote "dial" connections for access
to the Airport network (this policy may be changed from time to time, at the
Aviation Department's discretion). For the purpose of remote access to the
Airport network, the Aviation Department provides a secure and encrypted
access control mechanism via Checkpoint firewall. The authorized connection
type is a Virtual Private Network (VPN) connection through the internet. County,
at its own expense, shall provide the equipment and Software at its location to
permit remote access. Contractor, at its expense, shall provide the equipment,
AIMS System and Services Agreement
Page 53 of 60
Exhibit 3
Page 54 of 278
operating and Checkpoint VPN client Software at its location to permit the remote
access via a secure and encrypted VPN to the Airport's network. Contractor will
assume its respective telephone and/or internet access costs incurred to perform
support on the system by remote access. Contractor represents and warrants
that while performing support by remote access it will use all commercially
available methods to not transmit any type of undocumented Software routines or
other elements which are designed to or capable of permitting, allowing or
causing: (a) unauthorized access to or intrusion upon; (b) disabling of; (c)
erasure of; or (d) interference with any Hardware, Software, data or peripheral
equipment whether directly or by transference. In the event of a breach of this
representation and warranty, Contractor shall be responsible for and pay the
County for any and all actual harm, injury, damages, costs and expenses
incurred by County by reason of the breach.
20.34 Warranty as to Intellectual Property Infringement. Contractor represents and
warrants that at the time of entering into the System Agreement no claims have
been asserted or action or proceeding brought against Contractor which alleges
that all or any part of the Licensed Software to be supplied by Contractor or the
operation or use thereof by County, infringes or misappropriates any patent,
copyright, mask copyright or any trade secret or other intellectual or proprietary
right of a third party, nor is Contractor aware of any such potential claim.
Contractor also represents and warrants that its Services to be provided pursuant
to the System Agreement to modify the Licensed Software will not infringe or
misappropriate any patent, copyright, mask copyright or any trade secret or other
intellectual or proprietary right of a third party.
20.35 Codes/Regulations. Contractor, as it relates to the Services required to be
performed herein, represents and acknowledges to the County that it and its
subcontractors are knowledgeable as to any and all codes, rules and regulations
applicable in the jurisdictions in which the project is located and the funding
sources for the project and any Optional Services, including without limitation,
County and local ordinances and codes, Florida laws, rules, regulations and
grant requirements, and Federal laws, rules, regulations, advisory circulars and
grant requirements, including without limitation, Passenger Facility Charge
requirements, requirements of the Americans with Disabilities Act, and
requirements of the Federal Aviation Administration ("FAA"), and the Federal
Transportation Security Administration ("TSA") and the Florida Department of
Transportation ("FDOT"). In the performance of Services under the Agreement,
the Contractor and its subcontractors shall comply with all such laws, codes,
rules, regulations, advisory circulars and requirements now in effect and as may
be amended or adopted at any time during the term of the System Agreement,
and shall further take into account in the performance of its Services hereunder,
all known or publicly announced pending changes to the foregoing. The
Contractor and its subcontractors shall provide any and all certifications to the
County as to compliance with such laws, codes, rules, regulations, advisory
circulars and requirements, as may be required by any governmental body,
including FAA, TSA, FDOT and County agencies, or as may be requested by the
AIMS System and Services Agreement
Page 54 of 60
Exhibit 3
Page 55 of 278
Aviation Department. The Contractor will incorporate the provisions of this
Section 20.35 without modification into all agreements with its subcontractors.
20.36 Licensing. Contractor represents that it and its subcontractors are experienced
and fully qualified to perform the Services contemplated by the System
Agreement, and that it and its subcontractors are properly licensed pursuant to
all applicable laws, rules and regulations to perform such Services.
20.37 Knowledge and Skills. Contractor represents that it and its subcontractors
have the knowledge and skills, either by training, experience, education, or a
combination thereof, to adequately and competently perform the duties,
obligations, and Services to be provided by such person pursuant to the System
Agreement and to provide and perform such Services to County's satisfaction for
the agreed compensation.
20.37.1
Contractor shall perform its duties, obligations, and Services under the
System Agreement in a skillful and respectable manner, and shall
cause its subcontractors to also perform their duties, obligations and
Services under the System Agreement in a skillful and respectable
manner.
20.37.2
The quality of Contractor’s and its subcontractors' performance and all
interim and final product(s) provided to or on behalf of County shall be
comparable to the best local practices and national standards.
20.37.3
Nothing in the System Agreement shall relieve the Contractor of its
prime and sole responsibility for the performance of the work under the
System Agreement. In addition to all other rights and remedies that
County may have under the System Agreement, Contract
Administrator may require the Contractor to correct any deficiencies
which result from Contractor's failure to perform in accordance with the
above standards.
20.38 Physical access for Contractor personnel to the system as necessary during
support to allow Contractor to perform support shall be provided by County. In
addition, County shall provide, within County’s premises, adequate space for
support to be performed on site.
20.39 Governmental Immunity - Liability. Nothing herein is intended to serve as a
waiver of sovereign immunity by County nor shall anything included herein be
construed as consent to be sued by third parties in any matter arising out of this
Agreement or any other contract. County is a political subdivision of the State of
Florida, as defined in Chapter 768.28, Florida Statutes. No commissioner,
director, officer, agent or employee of the County shall be charged personally or
held contractually liable under any provision of this Agreement or of any
AIMS System and Services Agreement
Page 55 of 60
Exhibit 3
Page 56 of 278
supplement, modification or amendment to this Agreement or because of any
breach thereof, or because of its or their execution or attempted execution.
ARTICLE 21
WARRANTY REGARDING VIRUSES
The term "Virus" means any computer code that could (a) disrupt, disable, harm, or
otherwise impede in any manner the proper operation of a computer program or
computer system, or (b) damage or destroy any data or files residing on a computer
system without the user's consent, including (without limitation) any "back door," "time
bomb ... .. Trojan Horse," "worm," "drop dead device", spyware, and "virus" (as these
terms are commonly used in the computer Software field). Contractor warrants that the
Licensed Software does not and will not contain any Virus. Contractor warrants that it
will use state-of-the-art anti-virus screening Software to screen the media containing the
Licensed Software for Viruses before delivery of such media to County. Contractor will
indemnify County for any and all losses, damages, liabilities, costs, and expenses
caused by any such Virus; provided that such Virus was not the result of the intentional
or malicious actions of County or any County employees. Contractor further warrants
that it will not perform any action that will hinder County's freedom to use or physically
and electronically transport the Licensed Software within County's facilities, and that it
has not included in the Licensed Software any Software, Hardware, electronic, or other
security mechanism (including password, CPU serial number validation or dependency,
electronic initialization protection, and time dependent execution) or any other
disablement, de-installation, deactivation, or deletion mechanism.
ARTICLE 22
GOODS TO BE SUPPLIED BY CONTRACTOR
22.1
Contractor will sell and County will purchase from Contractor the following Goods
described in Exhibit A, Exhibit B, and Exhibit C as to be delivered to County by
Contractor. Prior to Final Acceptance of the System the Contractor shall submit
the following revised and updated exhibits: Exhibit B "Goods and Systems
Hardware," Exhibit B-1, "Existing EVIDS Devices," Exhibit C "Licensed
Software and Third Party Software," and Exhibit E "Master Price List." The
updated exhibits shall be reviewed and approved by the Contract Administrator,
and once approved, they shall be initialed by the Contract Administrator and the
Contractor's Project Manager and attached to this System Agreement and to the
License Agreement as replacement and final exhibits for the License Agreement
and this System Agreement. The revised Exhibits B, B-1, C, and E submitted by
the Contractor shall be based on actual installed components and quantities.
22.2
For purposes of the System Agreement, and unless otherwise stated, the term
"Goods" includes any associated firmware and operating Software licensed as an
integral part of the Goods. Contractor (or the applicable third party owner, as the
case may be) retains all right, title and interest in all firmware and associated
Software, whether operating or application Software, delivered under the System
Agreement subject only to the following license rights. Any firmware delivered as
AIMS System and Services Agreement
Page 56 of 60
Exhibit 3
Page 57 of 278
a component of Goods shall be deemed licensed to County on a nonexclusive
basis strictly for use as an integral part of the Goods. Any associated Software
delivered with the Goods shall be deemed licensed to County according to the
terms and conditions of the Software license agreement included with the
Documentation or, if not so included, then County shall be deemed granted a
nonexclusive license in object code form to install, store, load, execute and
display (collectively, "Use") the Software as part of using the Goods for the
purposes contemplated herein. All Goods will be new and unused except normal
manufacturers’ testing for product control and verification of quality. County shall
have the right to sell the Goods and, in such event, it is understood and agreed
that County may transfer the licenses to all Software, including any elements of
the Licensed Software, that are an integral part of the Goods to the purchaser(s)
of the Goods, but only if the purchaser agrees to accept and be bound by the
terms and conditions of the licenses being assigned with the Goods.
22.3
Contractor represents and warrants that it will convey to County good and
marketable title to the Goods free and clear of all liens and encumbrances or a
proper license to use the Software. Risk of Loss and title to the Goods shall pass
to the County upon Final Acceptance and final payment by the County.
Contractor will install those elements of the Licensed Software to be furnished by
Contractor described in the Statement of Work, so that such Software will
function with the Goods as set forth and described in the Statement of Work.
Contractor or the owner of the Software associated with the Goods retains title to
such Software. All patent, copyright, trade secret, trademark, and other
intellectual property rights remain solely with Contractor or the owner of the
Software.
ARTICLE 23
PERFORMANCE AND PAYMENT GUARANTY
Within five (5) calendar days after the date County executes this System Agreement,
Contractor shall furnish County with a Performance Bond and Payment Bond ("Bond"),
either in the form and containing all the provisions of Exhibit N, "Form of Performance
Bond and Payment Bond" ("Surety Bond") attached hereto and incorporated herein, or a
letter of credit ("Letter of Credit") in form and substance satisfactory to the County. The
Bond shall be in an amount equal to Five Million Four Hundred Thirty-Eight Thousand
Nine Hundred Twenty Dollars ($5,438,920.00). Said Bond shall be in full force and
effect until commencement of the "First Maintenance Fee Term" (as defined in Section
8.2 of the License Agreement). The Bond required hereunder shall secure the
performance of all work under this System Agreement, payment of liquidated damages,
if any, required under this System Agreement and any other payments or
reimbursements by the Contractor to the County that may be required under this
System Agreement. The Bond shall be in form and substance satisfactory to the
County’s Risk Management Division. The Bond posted by the Contractor shall be in
effect and shall provide coverage from the effective date of this System Agreement and
shall be kept in full force and effect until commencement of the First Maintenance Fee
AIMS System and Services Agreement
Page 57 of 60
Exhibit 3
Page 58 of 278
Term under Section 8.2 of the License Agreement. The County shall have no obligation
to make any payments under this System Agreement to the Contractor until a Bond in
amount and form acceptable to the County has been provided to the County by the
Contractor. In the event that the County exercises its option to terminate this System
Agreement for cause then in addition to any other rights and remedies available to the
County at law or in equity, County shall be entitled to draw down upon the Bond and
apply the proceeds of such draw to all fees, damages and amounts secured by the
Bond. Any cancellation of the Bond without the consent of the County Risk
Management Division prior to the aforesaid time period shall be a default of this System
Agreement. At least ninety (90) calendar days prior to the termination or expiration of
the Bond, the bonding company and Contractor shall notify County in writing of such
event. Not less than ninety (90) calendar days prior to any expiration date or termination
date of the Bond, Contractor shall submit evidence in form satisfactory to County that
said Bond has been renewed or replaced.
Each Surety Bond provided hereunder shall be executed by a surety company of
recognized standing authorized to do business in the State of Florida and having been
in business with a record of successful continuous operation for at least five (5) years.
Furthermore, such surety company must have at least a "A-" rating in the latest revision
of Best’s Insurance Report, or such other rating as has been approved by the County
Risk Management Division. In the event of any requirement hereunder that the Bond
amount be adjusted, a Bond in the adjusted amount shall be submitted to the Contract
Administrator no later than twenty (20) calendar days following the effective date of the
requirement for the adjustment. Each Surety Bond shall be in form and substance
satisfactory to the County.
Each Letter of Credit provided hereunder shall be provided by a financial institution of
recognized standing authorized to do business in the State of Florida. Throughout the
term of the Letter of Credit, the financial institution that has issued the Letter of Credit
must maintain a relationship with a financial institution having an office in Broward,
Miami-Dade, or Palm Beach County, Florida at which the Letter of Credit may be
presented for drawing down, and the financial institution that has issued the Letter of
Credit must have been in business with a record of successful continuous operation for
at least five (5) years. Each Letter of Credit shall be in form and substance satisfactory
to the County.
On approval of any contract change increasing the contract price, Contractor shall
ensure that the Bond is increased to reflect the total contract price as increased.
IN WITNESS WHEREOF, the parties have made and executed this System and
Services Agreement on the respective dates under each signature: BROWARD
COUNTY, by and through its BOARD OF COUNTY COMMISSIONERS, signing by and
through its Mayor or Vice Mayor, authorized to execute same by Board action on the
____ day of ________________, 2009, and AIR-TRANSPORT IT SERVICES, INC.,
Contractor, signing by and through its _______________, duly authorized to execute
same.
AIMS System and Services Agreement
Page 58 of 60
Exhibit 3
Page 59 of 278
Exhibit 3
Page 60 of 278
Exhibit 3
Page 61 of 278
EXHIBIT A
IMPLEMENTATION STATEMENT OF WORK
Exhibit 3
Page 62 of 278
1
GENERAL
The following constitutes the Statement of Work for this Contract. This
document is intended to be supplemental to County‟s RFP, and
CONTRACTOR‟s proposal response which are incorporated by this reference
as though fully set forth herein.
1.1
PROJECT OVERVIEW
The CONTRACTOR shall design and implement an integrated System
(AIMS) at the Fort Lauderdale-Hollywood International Airport which includes
the following subsystems:
1.1.1 Airport Operational Database (AODB):
This database will support the real-time data warehousing and retrieval of
data and will provide the mechanism for the integration of systems throughout
the campus.
1.1.2 Electronic Visual Information Display System (EVIDS):
The EVIDS will provide flight and baggage information to the traveling public
and operational information to other systems and to aviation and airline staff
members.
1.1.3 Dynamic Assignment Passenger Processing (DAPP):
The DAPP will allow multiple airlines to operate in the facility using their host
software and a common set of compatible hardware, increasing the flexibility
and efficiency of the facility.
1.1.4 Resource Management System (RMS):
A RMS will be provided to assist operations in the assigning of common use
resources including gates, ticket counters, baggage claim carousels, and
baggage makeup conveyors. The RMS will provide planning functions, “best
fit” recommendations, and real-time conflict warnings to assist operations in
the management of these resources.
1.1.5 Local Area Network (LAN) and Voice Over Internet Protocol System
(VoIP) (Integration with Existing Systems):
The Local Area Network (LAN) to be provided includes all materials,
equipment, software, and labor to install and make ready for use, a Multi-Use
AIMS Attachment A: AIMS Statement of Work
Page 2 of 130
Exhibit 3
Page 63 of 278
LAN utilizing IP based protocols. The Multi-Use LAN shall support all
systems that require connectivity throughout FLL. These systems shall
include, but not be limited to the EVIDS, DAPP, RMS, LDCS, and VoIP. It is
the responsibility of the CONTRACTOR to coordinate with County staff to
perform the necessary coordination and ensure all AIMS networking
requirements are met by the installed LAN/VoIP system.
1.1.6 Local Departure Control System (LDCS):
The Local Departure Control System (LDCS) will provide automated check-in
and departure control for non-hosted airlines and irregular flight operations.
1.2
SUMMARY STATEMENT OF WORK
The CONTRACTOR shall provide the following systems as part of the AIMS
base solution:
Airport Operational Database (AODB)
Electronic Video Information Display System (EVIDS)
Dynamic Assignment Passenger Processing (DAPP) and end user
hardware including:
o Ticket Counter Hardware
o Curbside Counter Hardware
o In Line CUSS Kiosk at Ticket Counters
o Open Area CUSS Kiosks without Bag Tag Printer (BTP)
o Open Area CUSS Kiosks with BTP
o Gate Counter Hardware
o Loading Bridge Podium Hardware
o DAPP Operational Workstation Hardware
Common Use Self Service (CUSS)
Local Departure Control System (LDCS)
Resource Management System (RMS)
Coordination of required modifications to the existing Local Area Network
(LAN) with County as necessary to establish the required integration.
Coordination of required modifications to the existing Voice over Internet
Protocol (VoIP) with County as necessary to establish the required
integration.
AIMS Attachment A: AIMS Statement of Work
Page 3 of 130
Exhibit 3
Page 64 of 278
Thorough review, analysis, and acceptance of existing systems, software,
and components that will be utilized by, or integrated with the AIMS.
The CONTRACTOR shall provide the following components:
All software and hardware components necessary for the AIMS to function
as specified.
All patch cords required to connect to the campus-wide Premises
Distribution System (PDS) and to interconnect AIMS components.
Uninterruptible Power Supplies (UPS) for all servers.
System training as specified.
System warranty as specified.
System testing and acceptance plans as specified.
The installed AIMS and all components shall be compliant with the most current
Payment Card Industry (PCI) Data Security Standard and Payment Application
Data Security Standard‟s at the time of installation.
The CONTRACTOR shall be responsible for all data level integration
interfaces as identified in this document. To support these interfaces
integration, Interface Design Documents (IDD) shall be developed by
CONTRACTOR for each identified interface. The IDDs shall be submitted
approved prior to proceeding with any integration work.
and
and
the
and
The CONTRACTOR shall be responsible for performing all documentation
reviews, field audits, inspections, and other methods necessary for analyzing the
existing conditions of infrastructure (power, cabling, and Local Area Network),
systems, software, and components that are to be utilized by, or integrated with
the new AIMS. The CONTRACTOR shall submit a formal deliverable stating that
the existing conditions are acceptable, or detailing any required modifications to
existing conditions that will be necessary for the AIMS to function as specified.
The CONTRACTOR shall be responsible for closely coordinating with County‟s
network administration staff to complete all necessary configuration and
integration with the LAN system to ensure the network port and Virtual Local
Area Network (VLAN) requirements of the PDS are properly configured to
support the AIMS. The County‟s network administration staff will provide all
system architecture and configuration requirements and must approve any LAN
modifications prior to implementation. All requested modifications to the LAN
must be submitted in writing for approval by the County.
The CONTRACTOR shall be responsible for providing any new Local Area
Network equipment that will be required to support the additional end user and
system devices provided by the Contract Documents.
AIMS Attachment A: AIMS Statement of Work
Page 4 of 130
Exhibit 3
Page 65 of 278
The CONTRACTOR shall be responsible for close coordination with the County‟s
staff to complete all necessary configuration and integration with the existing
Nortel VoIP telephony system to ensure the system is properly configured to
support the AIMS. All requested modifications to the VoIP system must be
submitted in writing for approval by the County.
The CONTRACTOR shall be responsible for performing all necessary
coordination with airline representatives and County to ensure each airline‟s
DAPP peripheral requirements are met by the AIMS.
The CONTRACTOR shall be responsible for coordinating with the County to set
up a test/training lab on the premises (location to be determined by County) to
facilitate training, system configuration, testing, and deployment. This lab will be
used by the County post implementation to support system administration and
modifications.
The CONTRACTOR shall be responsible for providing eleven (11) new ticket
counter double inserts. The CONTRACTOR shall ensure that all new equipment
provided by AIMS will be accommodated within the existing millwork at the ticket
and gate counters. The CONTRACTOR shall be responsible for performing the
appropriate coordination with the County, the project manager, and other
construction package coordinators to ensure the new and existing counter inserts
will be accommodated by the counter millwork and other architectural elements
that will be provided by others. As a minimum, the CONTRACTOR shall perform
shop drawing reviews and provide component drawings detailing the exact
mounting requirements for each component and device to be supplied by the
Contract Documents.
The CONTRACTOR shall be responsible for analyzing and integrating all existing
display devices into the AIMS. This shall include all necessary hardware,
software, and interface components necessary to allow the AIMS to display
information on the existing display devices. All existing devices must also be
supported during the initial warranty period, post warranty maintenance period,
and any optional maintenance period(s). A listing of the existing EVIDS
equipment is provided in Exhibit B-1.
The CONTRACTOR shall be responsible for performing all necessary
coordination, including attendance at weekly construction meetings, with other
related County projects.
The CONTRACTOR shall be responsible for participating in all County safety
programs and adhering to the established safety guidelines.
The CONTRACTOR shall be responsible for providing all warranty and
maintenance related work.
AIMS Attachment A: AIMS Statement of Work
Page 5 of 130
Exhibit 3
Page 66 of 278
The CONTRACTOR shall provide and pay for all labor, materials, and
equipment. This shall include all required gross receipts, sales, and other taxes.
The CONTRACTOR shall secure and pay for plan check fees, permits, fees, and
licenses necessary for the execution of work as needed for the project
The CONTRACTOR shall provide all required notices.
The CONTRACTOR shall comply with all codes, ordinances, regulations, and
any other legal requirements of public authorities which will bear on the
implementation of work for the project.
The CONTRACTOR shall be required to coordinate and administer design
workshops with the appropriate Airport and tenant stakeholders to discuss and
finalize AIMS functionality. Up to six (6) workshops shall be held. These
workshops shall be split into functional areas of the AIMS, including system
interface requirements, operational requirements (such as the supply of printing
stock), and shall be coordinated with the County.
It is the intent that the infrastructure requirements for the AIMS (data cabling and
power) will currently exist or will be provided by others. However the
CONTRACTOR shall be responsible for the following items on an as-needed
basis:
Installation of the necessary passive infrastructure components (racks,
cabinets, cabling, terminations, etc.) to support the AIMS.
All
infrastructure components shall be installed in accordance with the latest
County technology standards.
Installation of new electrical outlets to support new AIMS equipment. All
electrical installations shall conform to the latest County standards as well
as NEC and local codes and requirements.
1.3
CONTRACTOR RESPONSIBILITIES
The CONTRACTOR shall be responsible for the following:
All software and hardware components necessary for the AIMS to function
as specified
All patch cords required to connect to the campus-wide PDS.
Uninterruptible Power Supplies for all servers and other critical equipment.
System training as specified.
System warranty as specified.
AIMS Attachment A: AIMS Statement of Work
Page 6 of 130
Exhibit 3
Page 67 of 278
System testing and acceptance plans as specified.
Acceptance of existing conditions for infrastructure, systems, software,
and components that will be utilized by, or integrated with the AIMS.
Data level integration and interfaces as identified in the Contract
Documents. To support these interfaces and integration, Interface Design
Document (IDD) shall be developed by the CONTRACTOR for each
identified interface. The IDDs shall be submitted and approved prior to
proceeding with any integration work.
Coordinating with County staff to complete configuration and integration of
the VoIP system to ensure the telephony integration requirements of the
AIMS are satisfied.
Coordinating with County staff to complete configuration and integration
with the LAN system to ensure the network port and VLAN requirements
are properly configured to support the AIMS.
All necessary coordination with airline representatives to ensure each
airline‟s DAPP peripheral requirements are met by the AIMS.
Performing all appropriate coordination with the County, the project
manager, and other construction package coordinators to ensure all AIMS
equipment (display devices, workstations, gate and ticket counter
equipment, etc.) will be accommodated by casework and other
architectural elements that will be provided by others. The CONTRACTOR
shall perform shop drawing reviews and provide component drawings
detailing the exact mounting requirements for each component and device
to be supplied by the Contract Documents.
Performing all necessary coordination, including attendance at weekly
construction meetings, including participating in all County safety
programs and adhering to the established safety guidelines.
Provide all warranty and maintenance related work.
Provide and pay for all labor, materials, and equipment. This shall include
all required gross receipts, sales, and other taxes.
AIMS Attachment A: AIMS Statement of Work
Page 7 of 130
Exhibit 3
Page 68 of 278
Secure and pay for plan check fees, permits, fees, and licenses necessary
for the execution of work as needed for the project.
Providing all required notices
Complying with all codes, ordinances, regulations and any other legal
requirements of public authorities which will bear on the implementation of
work for the project.
Providing maintenance and support services during the interim period
while the AIMS is partially functional and in use, but prior to the formal
commencement of maintenance and support services. CONTRACTOR
shall coordinate with the County to determine the level of support that will
be required during this time.
1.4
COUNTY RESPONSIBILITIES
The County shall be responsible for the following:
Installation of the necessary passive infrastructure components (cabling,
terminations, etc.) to support the AIMS, with the exception of patch cords.
Development of Communications Rooms which meet the required
standards and codes to support the AIMS.
Electrical work; with the exception of grounding for the installed equipment
within cabinets and racks in the Communications Rooms and UPS where
required.
1.5
PHASES OF IMPLEMENTATION
A. The implementation of the AIMS shall be phased as necessary in order to
minimize any disruption of normal Airport operations. Discussions with the
County have contributed to the development of the phasing requirements
which follow. CONTRACTOR shall provide a detailed Phasing Plan as
part of the overall Project Plan for acceptance by the County prior to
commencing work under Phase One.
B. Within 45 calendar days after the Initial NTP the CONTRACTOR shall
submit a detailed Project Schedule in accordance with the submittal
requirements identified in the Contract Documents.
C. The existing EVIDS is to remain operational during the implementation of
the AIMS. Parallel systems shall be in place (existing EVIDS and new
AIMS Attachment A: AIMS Statement of Work
Page 8 of 130
Exhibit 3
Page 69 of 278
EVIDS) and integrated to ensure that displayed information is current. In
addition, to the end users, a single data entry update shall update all
information in both EVIDS systems. The CONTRACTOR shall include in
the Project Plan a detailed procedure of how these parallel systems will be
implemented and how the cutover to the new EVIDS will occur.
D. Historical information (minimum five (5) years) from the existing Resource
Management System shall be migrated to the AIMS to allow for retrieval of
historical data. The interface required to achieve this functionality shall be
included in an Interface Design Document that describes the interface
between the existing system and the AIMS.
E. The DAPP and CUSS implementations will be performed in stages with
the individual airlines for each stage identified in Section 1.6.6. of this
Statement of Work. Unless written approval from the County is obtained,
all stages of the DAPP and CUSS implementations must be completed
prior to Final Acceptance.
F. Phase Zero
1. The initial phase of the project (Phase Zero) will consist of the
development, submittal, and acceptance of the Project Plan that
includes an overall Project Schedule. In addition, this phase will
include the review, analysis, and acceptance of existing systems,
software, and components that will be utilized by, or integrated with the
AIMS and the submission of a formal deliverable stating the
acceptance and/or listing any items requiring modifications. This
review and subsequent documentation will include logic drawings
showing equipment quantities and logical connectivity.
G. Phase One
1. Phase One of the implementation will consist of the development of the
final design, system, equipment, and component submittals,
County/tenant coordination workshops, and Factory Acceptance
Testing ("FAT").
2. This phase will also include of the development and finalization of all
Interface Design Documents as specified herein.
3. In Phase One the CONTRACTOR shall develop, coordinate, and
administer design workshops to finalize the following components with
input from the required stakeholders. The exact list of workshops
along with each workshops agenda shall be submitted for review and
approval by the County. These design workshops shall included, but
not be limited to, the following:
i
EVIDS distribution architecture and display driving technical
workshop
AIMS Attachment A: AIMS Statement of Work
Page 9 of 130
Exhibit 3
Page 70 of 278
ii
Screen formats and displayed information workshops (all displays)
iii Tenant Gate Operational functionality workshops (i.e. boarding
sequence, etc.)
iv Airline functional requirements workshop with all airlines
v
Detailed technical requirements workshop for all airlines identified
for implementation in stage one of DAPP. These airlines are
identified in Section 1.6.6 of this Statement of Work.
vi Resource Management System functional workshops
vii AIMS report workshops.
4. Development and implementation of a test lab at the FLL site. The test
lab shall include the following, as a minimum:
i
A two server cluster configuration that will provide a scaled down
version of the production system. The configuration shall allow for:
a Application testing
b Application updates
c
Server patch testing
d Database patch testing
e Symantec storage foundation patch set testing
ii
EASE ticket and gate counter workstation configurations will all
associated peripherals. This configuration shall allow for:
a Installation and configuration of airline software
b Testing and validation of software upgrades
c
Training area for airline staff
iii FIDS displays to be used for layout design and to allow on-site staff
members to monitor the FIDS in production.
iv AODB/RMS workstations
v
CUSS Kiosk
5. Installation of the AIMS head-end equipment and all access layer
(LAN) components. This will include the installation of hardware and
the operating system(s).
6. Installation of the AIMS head-end equipment and all access layer
(LAN) components. This will include the installation of hardware and
the operating system(s).
7. Performance of Factory Acceptance Testing. Factory Acceptance
Testing shall be performed no later than ninety (90) calendar days after
successful submittal of the final software specifications. Testing shall
AIMS Attachment A: AIMS Statement of Work
Page 10 of 130
Exhibit 3
Page 71 of 278
not commence until the testing procedure has been submitted and
approved by the County. Factory Acceptance Testing shall be
performed on-site at the test lab. DAPP testing will include the LDCS
functionality in lieu of individual airline interfaces. CUSS testing will
only include those airlines included as part of stage one of the CUSS
implementation.
H. Phase Two
1. Phase Two of the implementation process will be the integration of
existing EVIDS display devices throughout all terminals, the installation
of new AIMS devices within Terminal 4, and the installation of all
baggage input devices. The fluid nature of the airport business
environment will be reflected in this phase and careful coordination
with County, stakeholders and others must be performed to eliminate
any disruption to the traveling public. This phase will also include all
necessary training that will be required prior to cutting over to the
AIMS.
2. Phase Two will also include the successful configuration, testing, and
acceptance of all associated software and hardware components for
each stage two and three airlines associated with DAPP and CUSS, if
these optional services are selected by the County. These airlines are
listed in Section 1.6.6 of this Statement of Work.
I. Phase Three
1. Phase Three will consist of performance verification testing, formal cutover to the AIMS, Endurance Testing, and final project close-out.
1.6
DELIVERABLES
1.6.1 Phase Zero
Item #
Deliverable
0001
0002
0003
Provide finalized detailed project plan including
Project Schedule
Provide finalized submitted Project Schedule
Provide acceptance of existing conditions
documentation with detailed requirements for
any modifications.
AIMS Attachment A: AIMS Statement of Work
Acceptance
Criteria
Review against
specifications
Review against
specifications
County Preliminary
Acceptance
Page 11 of 130
Exhibit 3
Page 72 of 278
1.6.2 Phase One
Item #
Deliverable
101
101.1
101.2
101.3
101.4
101.5
101.6
101.7
101.8
102
102.1
102.2
102.3
102.4
102.5
102.6
102.7
102.8
Acceptance
Criteria
Provide Submittals associated with Phase One,
Review against
including the following:
specifications
Provide finalized system, equipment, and
Review against
component submittals
specifications
Provide finalized products list
Review against
specifications and
requirements
Provide
finalized
system
environmental Review against T4 1B
requirements
requirements
Provide finalized Interface Design Documents
Review against
(IDDs) for each identified interface/integration.
specifications
For DAPP and CUSS, IDDs are required for
stage one airlines only.
Provide finalized display formats for each
County Preliminary
functional display
Acceptance
Provide finalized database structure and schema
Review against
documentation
specifications
Provide
finalized
set
of
all
software
Review against
documentation and utilities
specifications
Provide
finalized
system
administration
Review against
documentation
specifications
Complete County/tenant workshops (as listed)
County Preliminary
including
development,
coordination,
Acceptance
administration, and documentation
Complete EVIDS distribution architecture and
County Preliminary
display driving workshop
Acceptance
Complete screen formats and displayed
County Preliminary
information (all system displays) workshops
Acceptance
Complete tenant gate operational functionality
County Preliminary
(i.e. boarding sequence, etc.) workshops
Acceptance
Complete airline functional workshop with all
County Preliminary
airlines
Acceptance
Complete airline technical (individual per
County Preliminary
airline) workshops for all stage one DAPP and
Acceptance
CUSS airlines*
Complete Resource Management System
County Preliminary
preliminary functionality workshops
Acceptance
Complete
AIMS
preliminary
reporting
County Preliminary
requirements workshops
Acceptance
Complete other workshops as required
County Preliminary
AIMS Attachment A: AIMS Statement of Work
Page 12 of 130
Exhibit 3
Page 73 of 278
103
104
Complete head-end equipment installation
(hardware and operating system(s))
Installation and configuration of test lab
105
Complete Factory Acceptance Testing including
items listed.
Note: FAT for DAPP will
demonstrate LDCS functionality in lieu of
individual stage one DAPP airline interfaces.*
FAT will not include CUSS.
105.1
Complete CONTRACTOR‟s Quality Assurance
organization review of FAT test procedures
105.2
Provide finalized FAT test plan/procedures
105.3
105.4
105.5
Complete pre-test setup and verification of test
configuration
Conduct and pass all FAT test requirements
and verify documentation
Provide finalized FAT test report
106
Acceptance
Pre-Installation
Verification
Pre-Installation
Verification
Review against
specifications
Review against
specifications
Review against
specifications
Field Verification
Field Verification
against FAT test plan
(105.1)
Review against
specifications
Receive
Contract
Administrator's
written
Preliminary Acceptance of Phase One
*Refer to Section 1.6.5 of this Statement of Work for a listing of airlines associated
with each DAPP and CUSS stage
1.6.3 Phase Two
Item #
Deliverable
201
AIMS configured to accommodate all EVIDS
functionality and complete deployment of all
components required to support the existing
EVIDS
and
associated
infrastructure
coordination, including the items listed.
201.1
All inputs to EVIDS through the new AIMS;
interface to existing EVIDS (Infax) complete.
201.2
EVIDS Training Complete.
201.3
201.4
201.5
201.6
All existing EVIDS displays driven by new
AIMS
Interface to Infax system complete
Airline feeds for Delta, Southwest, and
American complete
All screen layouts complete
AIMS Attachment A: AIMS Statement of Work
Acceptance
Criteria
Field Verification
Field Verification
County Preliminary
Acceptance
Field Verification
Field Verification
Field Verification
Review against
workshop design
Page 13 of 130
Exhibit 3
Page 74 of 278
202
Existing EVIDS in Terminal One cut over to new
system.
203
Existing EVIDS in Terminal Two cut over to new
system.
204
Existing EVIDS in Terminal Three cut over to new
system.
205
Existing EVIDS in Terminal Four cut over to new
system.
206
New EVIDS Displays installed, configured, and
tested.
207
Configuration of all DAPP Stage One Airlines
208
Configuration of all CUSS Stage One Airlines
209
DAPP Training Complete (Stage One Airlines)
210
Installation, configuration, and testing of DAPP
end user devices
211
Installation, configuration, and testing of CUSS
stations
212
Installation, configuration, and testing of AODB
including third party feed
213
Installation, configuration, and testing of RMS
and associated end user devices
214
Provide Deliverables associated with Phase Two
including the following:
214.1 Provide finalized parts lists and breakdowns that
identify each hardware component (to the lowest
repairable unit) for the AIMS
214.2 Provide finalized spare parts list for the AIMS
214.3 Provide finalized as-built drawings for the AIMS
214.4 Provide finalized user documentation for the
AIMS
214.5 Provide finalized response escalation plan for the
AIMS
214.6 Provide finalized COTS (common off-the-shelf)
software report and license information for the
AIMS
214.7 Provide finalized maintenance schedule for the
AIMS
214.8 Provide finalized disaster recovery plan for the
AIMS
214.9 Provide required software backup copies for the
AIMS
AIMS Attachment A: AIMS Statement of Work
documents
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Field Verification
Review against
specifications
Review against
specifications
Review against
specifications
Review against
specifications and
field verification
Review against
specifications
Review against
specifications
Review against
specifications and
field verification
Review against
specifications
Review against
specifications
Review against
specifications and
Page 14 of 130
Exhibit 3
Page 75 of 278
215
Complete installation of all stage two
airlines, if required
Complete installation of all stage three
airlines, if required
Complete installation of all stage two
airlines, if required
Receive
Contract
Administrator's
Preliminary Acceptance of Phase Two
216
217
218
DAPP
field verification
Field Verification
DAPP
Field Verification
CUSS
Field Verification
written
1.6.4 Phase Three
Item #
Deliverable
301
302
303
303.1
303.2
303.3
303.4
304
305
306
307
307.1
307.2
307.3
Complete installation of AIMS and complete
individual and joint Testing to ensure proper
operation
Receive
Contract
Administrator
written
permission to proceed with Performance
Verification Test
Complete Performance Verification Testing
including items listed below
Complete
CONTRACTOR‟s
Quality
Assurance organization review of test
procedures
Provide finalized Performance Verification
Testing test plan/procedures
Conduct and pass all test requirements
Provide finalized Performance Verification
Testing report
Complete all remaining training
Complete correction of all AIMS deficiencies
Receive
Contract
Administrator
written
permission to proceed with Endurance Testing
(Stage One airlines only)*
Complete Endurance Testing including items
listed below
Complete CONTRACTOR‟s Quality Control
Assurance Organization review of test
procedures
Provide finalized Endurance Testing test
plan/procedures
Provide personnel to operate and monitor
AIMS Attachment A: AIMS Statement of Work
Acceptance
Criteria
Field Verification
Field Verification
Review against
specifications
Review against
specifications
Field Verification
against Performance
Verification test plan
(303.2)
Review against
specifications
Field Verification
Field Verification
Field Verification
Review against
specifications
Review against
specifications
Field Verification
Page 15 of 130
Exhibit 3
Page 76 of 278
AIMS 24 hours 7 days a week throughout
testing periods
307.4
Maintain a continuous log of AIMS'
Field Verification
performance during testing periods
307.5
Provide required AIMS maintenance during
Field Verification
testing periods
307.6
Conduct Step I Endurance Testing
Field Verification
307.7
Conduct Step II Endurance Testing as
Field Verification
required
307.8
Conduct Step III Endurance Testing, if
Field Verification
required
307.9
Conduct Step IV Endurance Testing
Field Verification
307.10
Make required modification and adjustments
Field Verification
as directed in writing by Contract
Administrator
307.11
Complete and pass all phases of Endurance
Field Verification
Testing
407.12
Provide finalized Endurance Testing report
Review against
and log
specifications
308
Complete final project close-out including items
Review against
listed below
specifications
308.1
Provide a finalized list and cross-reference of
Review against
all supplied documents
specifications
308.2
Complete work site cleaning as required
Field Verification
308.3
Provide finalized statement of completion of
Review against
work and request for final inspection
specifications
*Refer to Section 1.6.5 of this Statement of Work for a listing of airlines associated
with each DAPP and CUSS stage
1.6.5 Dynamic Assignment Passenger Processing and Common Use Self
Service Staging
A. The DAPP and CUSS implementations shall be implemented in a staged
manner to accommodate the operational environment at FLL. The airlines
associated with each stage of implementation are provided in the tables
below. All airlines shall be configured, tested, and accepted prior to Final
Acceptance, unless written authorization from the County is obtained.
Table 1.6.5-1:
Airline
Air Transat
American
Avianca
Caribbean
Spirit
DAPP Staging
Location
T4
T4 – Recheck
T4
T4
T4
AIMS Attachment A: AIMS Statement of Work
Stage
Stage 1A
Stage 1A
Stage 1A
Stage 1A
Stage 1B
Page 16 of 130
Exhibit 3
Page 77 of 278
Air Jamaica
Allegiant
Frontier
JetBlue
Air Canada
AirTran
Bahamas Air
Comair
CanJet
Continental
Continental Connection
(Gulfstream)
Delta/Delta Connection
Northwest/KLM
US Airways
Air Sunshine
Chalks
Lynx Air International
Yellow Air Taxi
Skyservice
Southwest
Sunwing
Westjet
Table 1.6.5-2:
Airline
T4
Stage 1B
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
T4 Commuter
T4 Commuter
T4 Commuter
T4 Commuter
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 3 (Optional Service)
Stage 3 (Optional Service)
Stage 3 (Optional Service)
Stage 3 (Optional Service)
CUSS Staging
Stage
American
JetBlue
Air Canada
Continental
Continental Connection
(Gulfstream)
Delta/Delta Connection
Northwest/KLM
AIMS Attachment A: AIMS Statement of Work
Stage 1
Stage 1
Stage 1
Stage 1
Stage 1
Stage 1
Stage 1
Page 17 of 130
Exhibit 3
Page 78 of 278
Air Jamaica
Air Transat
Avianca
Caribbean
Comair
Spirit
Allegiant
Frontier
AirTran
Bahamas Air
CanJet
Skyservice
Southwest
Sunwing
US Airways
Westjet
Air Sunshine
Chalks
Lynx Air International
Yellow Air Taxi
1.7
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
Stage 2 (Optional Service)
PROJECTED IMPLEMENTATION TIME
These preliminary milestones represent projected project dates and are
subject to change at the direction of the Contract Administrator.
Milestone
Submittal of detailed project plan
Completion of Phase Zero
Completion of Phase One
Completion of Phase Two
Completion of Phase Three
AIMS Attachment A: AIMS Statement of Work
Working Days After NTP
45
45
120
130
60
Page 18 of 130
Exhibit 3
Page 79 of 278
2
PROJECT REQUIREMENTS
2.1
PROJECT MANAGEMENT
2.1.1 Project Management Requirements
A. Within 45 calendar days after execution of the Initial NTP, the
CONTRACTOR shall develop and submit to the County a detailed draft
Project Management Plan (Project Plan or, PMP) addressing all aspects
of implementing and accomplishing the services set forth in the Contract
Documents. It shall be a comprehensive plan for assisting the County to
control, direct, coordinate and evaluate the work performed during each
project phase.
In developing this plan and its updates, the
CONTRACTOR must work closely with the County and the Consultant,
and other appropriate firms and individuals involved with the project.
Following a County review of the draft PMP, the CONTRACTOR shall
incorporate County‟s comments, and issue a final PMP within 10 calendar
days of receipt of County‟s comments.
B. Contents
The PMP must be detailed and fully describe the project and requirements
for executing the work planned for each project phase, and the
participating organizations. To achieve desirable uniformity in preparation
and use, the plan must include all of the following sections, topics, and
data, which will be kept current:
i
Project Description/Goals. Known characteristics of the project
described in general terms that reflect the requirements of the
County, including security clearance requirements.
ii
Project Objectives. The County‟s basic schedule; budget; physical,
technical, and other objectives for the project, defined and updated;
cost reduction alternatives; quality standards; controls affecting
access to and use of proprietary information.
iii Work Statements.
A task performance breakout showing
coordination among disciplines, and narrative descriptions of the
work to be performed by the CONTRACTOR during each Project
Phase. The CONTRACTOR will update the work statements as
required by the County. This includes initiatives as to who will act
when project responsibilities are unfulfilled and/or when other
contractors or participants experience delays.
iv Work Flow Chart. A diagram to show the flow of work during each
stage of the project. During the construction stage, additional
AIMS Attachment A: AIMS Statement of Work
Page 19 of 130
Exhibit 3
Page 80 of 278
detailed charts maybe required to accurately convey the flow of
information/work.
v
Organization Chart. A summary chart showing interrelationships
among the CONTRACTOR (including subcontractors), and the
County, supporting organizational elements participating in the
project. Included shall be a project directory.
vi Duties. All CONTRACTOR staff personnel shown on an
organizational chart with their individual duties being fully
described. Include lines of authority and communication, daily
duties, and avoidance/control of non-complying work.
vii Schedules.
Computer generated system and schedules for
maintaining the real time status of all project phases. A precedence
diagram method network for the entire project will be used. The
system must include computer-generated initial and updating major
milestone schedules using the Critical Path Method (CPM) for all
project activities. The County may require that time divisions be in
terms of days and/or weeks. Both controllable and uncontrollable
time obligations must be shown, such as submissions made on
time and subsequent agency review times. During each project
phase, the CONTRACTOR must supplement these schedules with
analyses on the impact of delays, and show milestone conflicts,
major constraints, adjustments to keep the construction completion
dates intact, and decision tracking.
viii Budget/Financial Control.
A narrative description of
budget/financial control methods during each project phase, cost
reporting, and methods to be used for cost containment. Include an
estimate of the total project separated in each phase including a
breakdown/budget of all proposed services/equipment and
materials.
2.1.2 Project Coordination
A. The CONTRACTOR must manipulate information as specified herein. In
turn, information may be delivered to the CONTRACTOR and the County
in electronic format. For each employee located full time at the site, the
CONTRACTOR shall provide its own hardware/computer equipment and
software to fully satisfy all operational requirements of the Contract
Documents. All associated costs must be included in the established
pricing for the Contract Documents as no reimbursement is authorized for
such items. The CONTRACTOR's equipment and software must be
compatible with the system and software used by the County, including
the appropriate version of Microsoft Office, Auto-CAD, and electronic
Project management systems.
B. CONTRACTOR shall coordinate with the County at all times.
AIMS Attachment A: AIMS Statement of Work
Page 20 of 130
Exhibit 3
Page 81 of 278
1. CONTRACTOR shall provide a project directory/contact list, which is a
detailed directory of the team and contact points, including (but limited
to) company, name, title, address, telephone number, fax number, and
email address.
2. CONTRACTOR shall coordinate implementation activities included
under the various sections of these specifications to assure efficient
and orderly installation of each part of the work.
3. CONTRACTOR shall coordinate installation of different components to
assure maximum performance and accessibility for required
maintenance, service and repair of all components. The
CONTRACTOR shall have sole responsibility to coordinate the work to
meet this requirement within the dimensions indicated on the drawings
and to notify the County of all conflicts that cannot be accommodated
through proper coordination of the installations. CONTRACTOR shall
review requirements prior to formal submission of shop drawings and
notify the County of any problems affecting serviceability and
maintenance.
4. Make adequate provisions to accommodate items scheduled for later
installation.
5. Coordinate construction activities to ensure that operations are carried
out with consideration given to conservation of energy, water, utilities,
and materials.
C. The County may have other contracts in progress at these sites with which
this CONTRACTOR may have to coordinate and cooperate during the
performance of this work. The County will coordinate this effort as
required.
D. The County may award additional separate contracts for additional work to
be performed at each site with which this CONTRACTOR may have to
coordinate and cooperate during the performance of the work. The
County will coordinate this effort as required.
E. Any coordination required of any of CONTRACTOR's subcontractors shall
be conducted through the CONTRACTOR.
2.1.3 Project Schedule
A. Within 45 calendar days after the Initial NTP, CONTRACTOR shall submit
to the County a schedule for effectively planning and reporting on the
status of each project component to ensure completion within the
approved schedules. The schedule shall include computer-generated
reports and master Critical Path Method (CPM) milestones of all project
activities.
AIMS Attachment A: AIMS Statement of Work
Page 21 of 130
Exhibit 3
Page 82 of 278
B. The schedule shall identify activities, scheduling, and show relationships
between activities such as "develop concepts, approve initial and final
concepts, completion of design documents, completion of design and
similar milestone activities. The level of detail shall be satisfactory to the
County and sufficient to identify:
1. The work components of the project
2. The types of work and services involved
3. Design and program development phases of work
4. Procurement, fabrication, delivery, installation, and testing of major
materials and equipment
5. Access to and availability of work areas
6. Interfaces and dependencies with other contractors
7. Manpower, material, and equipment restraints
8. Startup and testing activities
C. Format for Project Schedule:
1. Prepare schedules as horizontal bar chart with separate bar for each
major portion of work or operation, identifying first workday of each
week.
2. List individual tasks of work in chronological order of the start of each
item of work.
3. Provide space for notations and revisions.
4. Sheet size shall be a minimum 8-1/2 x 11 inches.
5. Schedule shall be delivered in hardcopy and electronic format
D. Revisions to Schedules
1. Indicate progress of each activity to date of submittal and projected
completion date of each activity.
2. Identify activities modified since previous submittal, major changes in
scope, and other identifiable changes.
3. Provide narrative report to define problem areas, anticipated delays,
and impact on schedule. Report corrective action taken or proposed
and its effect.
4. Seasonal weather conditions should be considered and included in the
planning and scheduling of all work influenced by high or low ambient
AIMS Attachment A: AIMS Statement of Work
Page 22 of 130
Exhibit 3
Page 83 of 278
temperatures, precipitation and/or saturated soil conditions, to ensure
completion of all work within the Contract period. Time extensions
granted for abnormal weather are not allowed.
5. The CONTRACTOR is solely responsible for the scheduling of the
scope of work. The CONTRACTOR‟s management personnel shall
actively participate in the development of the schedule so that the
intended sequences and procedures are clearly understood by the
CONTRACTOR‟s organization. The CONTRACTOR is solely
responsible for the costs of fulfilling the requirements.
6. The CONTRACTOR‟s Project Schedule shall begin on the day after
issuance of the Initial NTP and conclude with the date of Final
Acceptance. Float or slack time within the schedule is not for the
exclusive use or benefit of either the County or the CONTRACTOR,
but is jointly owned, expiring project resource available to both parties
as needed to meet the Contract Milestones ("Contract Milestones").
E. Three-Week Rolling Schedule
1. The CONTRACTOR shall submit a Three (3) Week Rolling Schedule
each week to be used as the basis for discussion of project progress in
the weekly CONTRACTOR meetings. The Three (3) Week Rolling
Schedule shall represent the actual detailed work plan used by the
CONTRACTOR in meeting the Project Schedule and Contract
Milestones.
2. The Schedule shall be in bar chart format and reflect the previous
week‟s activity progress as well as a projection of the activities
expected to be in progress during the following two-week period. The
activities in the Three (3) Week Rolling Schedule shall be in detail than
that of the Project Schedule and shall support the activity time frames
shown therein.
F. Schedule Revisions and Time Impact Analysis
1. Updating the Project Schedule to reflect actual progress shall not be
considered a revision to the schedule. The CONTRACTOR shall
complete a “Project Change Control Form” and submit to the County
for review of its intent to revise the Project schedule due to one or
more of the following conditions:
i
When an event or change order impacts any intermediate
milestone dates, or the date of Final Acceptance.
ii
When the CONTRACTOR elects to change any sequence of
activities affecting the critical path or significantly changes the
previously reviewed Project Schedule.
AIMS Attachment A: AIMS Statement of Work
Page 23 of 130
Exhibit 3
Page 84 of 278
2. Within fifteen (15) calendar days of notification of an initiating event
which impacts the critical path or an intermediate milestone date, the
CONTRACTOR shall submit to the County a Time Impact Analysis
illustrating the influence of the event on the appropriate intermediate
milestone or milestones and/or critical path.
3. The Time Impact Analysis shall be complete in all respects and shall
include, as a minimum, a narrative describing the initiating event and
how it impacted the Schedule, a critical path analysis, and all
supporting documentation.
4. The Time Impact Analysis shall reflect activity duration from the update
of the Project Schedule just before the effect of the change. The
CONTRACTOR shall compare the status of the Project Schedule as
modified by the initiating event with the status of the Project Schedule
Update immediately before the initiating event to determine schedule
impact. The number of days of schedule impact shall be analyzed, with
delay apportioned to the initiating event and/or the CONTRACTOR‟s
own actions.
5. Upon County review and subsequent agreement with the
CONTRACTOR on the number of days of schedule impact, the
influence of the initiating event shall be incorporated in the next
monthly Project Schedule update. Agreement between the County
and the CONTRACTOR on the number of days of schedule impact
does not imply County concurrence on the number of days of impact,
or availability of a Change Order or of any amendment.
6. When agreement has been reached on the number of days to be
included in an overall time extension or an extension to an
intermediate milestone, the revised Project Schedule with the
extensions will become the basis for any future approved changes to
the schedule.
7. The CONTRACTOR shall incorporate activities representing the total
value of approved Change Orders (i.e., approved pursuant to Article 16
of the Agreement) as each is approved. Change Order activities shall
be assigned unique activity codes such that they can be segregated in
the Project Schedule.
G. No later than forty-five (45) calendar days after Initial NTP is issued by the
County, the CONTRACTOR shall be required to commence the
installation process according to the schedule submitted (e.g., order
material, site survey, installation).
2.1.4 Reporting
A. Weekly Progress Report
AIMS Attachment A: AIMS Statement of Work
Page 24 of 130
Exhibit 3
Page 85 of 278
The
CONTRACTOR
must
keep
accurate
and
detailed
computerized/written records of progress on the project during all stages
and maintain frequent contacts by telephone, site visits, meetings, etc.,
with all parties involved in the project. CONTRACTOR must submit
weekly hard copy/written progress reports to the County including, but not
limited to, information concerning the work of the project. Initiatives taken
by the CONTRACTOR to preclude delays, percentages of completion,
number and amounts of modifications and claims, analyses of the
schedule, and other analyses necessary to compare actual performance
with planned performance. The CONTRACTOR must use any applicable
County forms and procedures.
B. Monthly Report
1. The CONTRACTOR shall submit a Monthly Report with a progress
cutoff to be established by the County.
2. The first Monthly Report shall be submitted before payment for the first
pay request and shall be a prerequisite for payment for all subsequent
pay requests.
3. Before approval of the Project Schedule, the interim Project Schedule
shall be updated as the basis of the Monthly Report.
C. The Monthly Report shall consist of the following:
1. Narrative Report - Report shall state the percentage of work
completed, a description of the physical progress achieved during the
period, plans for the forthcoming period, problem areas and proposed
solutions, delaying factors and their impacts, and an explanation of
corrective actions taken or proposed.
2. Project Schedule - Updated through the current period to show actual
progress against activities in the Project Schedule.
3. Special Reports - Except as otherwise indicated, submit special reports
directly to the County within one (1) County Work Day of an
occurrence requiring a special report, with copies to others affected by
the occurrence.
4. Reporting Unusual Events: When an event of unusual and significant
nature occurs at the site, prepare and submit a special report listing
chain of events, persons participating, and response by
CONTRACTOR‟s personnel, evaluation of results or effects, and
similar pertinent information. When such events are known or
predictable in advance, advise County in advance at earliest possible
date.
AIMS Attachment A: AIMS Statement of Work
Page 25 of 130
Exhibit 3
Page 86 of 278
5. Reporting Accidents: Prepare and submit reports of any significant
accident at the work site to the County Project Manager. Record and
document data and actions; comply with industry standards. For this
purpose, a significant accident is defined to include events where
personal injury is sustained, property loss of substance is sustained, or
where the event posed a significant threat of loss or personal injury.
6. Monitor and enter all Change Orders on the CPM data files. Analyze
the effects of all Change Orders entailing time delays and their impacts
on the construction schedules. Make periodic reports when and as
required by the County. These reports must include the compatible
CPM schedule; all Change Orders issued to that point in time, and
narratives addressing cause and effect relationships.
7. The CONTRACTOR shall assist the County in monitoring the budget
by maintaining budget records and reporting on the status of the
budget in the CONTRACTOR's monthly progress reports. The monthly
report includes design, programming, all other software and hardware
costs, and related administrative costs in a format that includes actual
obligations and projected obligations against available funds. The
County shall specify the specific content and format for budget
reporting for each phase of the project. The CONTRACTOR shall
monitor the status of the budget continuously, advising the County of
observed shortfalls or potential shortfalls.
8. The CONTRACTOR shall maintain current quality control records, on
County approved forms, of all inspections and tests performed. These
records shall include factual evidence that the required inspections or
tests have been performed, including: precise location of test or
inspection made, type and number of inspections or tests involved;
results of inspections or tests; nature of defects, causes for rejection,
etc.; proposed remedial action; and corrective actions taken.
9. These records must cover both conforming and defective or deficient
features, and must include a statement that all supplies and materials
incorporated in the work are in full compliance with the terms of the
Contract Documents. Legible copies of these records must be
furnished to the County daily. The records shall cover all work placed
subsequent to the previously furnished records and shall be verified by
the CONTRACTOR‟s Quality Control Supervisor. The CONTRACTOR
shall document inspection and tests as specified in the technical
provisions of the specifications. These records shall be available for
review by the County throughout the duration of the Contract.
D. Record Maintenance
1. Weekly Quality Control Summary Reports: The CONTRACTOR‟s
Quality Control Supervisor shall submit signed Weekly Quality Control
AIMS Attachment A: AIMS Statement of Work
Page 26 of 130
Exhibit 3
Page 87 of 278
Summary Reports to the County. These reports shall address both
project progress and project quality control activity:
2. Project Progress: shall identify CONTRACTOR personnel on site,
equipment on site, idle equipment and personnel, material deliveries,
weather conditions, work accomplished and any other additional
information as specified.
3. Project Quality Control Activity: shall summarize inspection and testing
activity including: meetings; preparatory, initial and follow-up
inspections, Quality Control problems encountered or resolved; failing
test results received or corrected; and other significant events
impacting project quality or Contract Documents compliance.
4. Inspector‟s Reports and Test Reports shall be attached to the Quality
Control Summary Report. Quality Control Summary Reports shall
include the following, or similar, certification:
i
On behalf of (Name of CONTRACTOR), I certify that this report and
the Inspector‟s Daily Reports are complete and correct, and that all
materials and equipment used, and work performed, during this
reporting period are in compliance with the drawings, specifications
and Contract Documents provisions, except as noted in the
Inspector‟s Reports.
5. Inspector‟s Daily Reports: Each inspector shall maintain a daily log of
all inspections he/she performs for both CONTRACTOR and
subcontractor operations on the appropriate County form. These
Inspector‟s Daily Reports shall provide factual evidence that
continuous quality control inspections and tests have been performed
including, but not limited to, the following: compliance with approved
shop drawings, proper storage of materials and equipment, job safety,
and computations employed in the work.
6. The Inspector‟s Daily Reports shall identify: inspection and tests
conducted, results of inspections and tests, location and nature of
defects found, causes for rejection, and remedial or corrective actions
taken or proposed.
7. The original and one copy each of Weekly Progress Report and the
Inspectors‟ Daily Reports shall be provided to the County by noon of
the Monday (or next County Work Day) following the week of record.
8. Testing Control Log: The CONTRACTOR shall maintain a log to
record and track each test performed. The log shall indicate date of
test, test designation or type, location, specification test-result
requirements, initial test results, causes for failing test, recommended
remedial actions, and reference to subsequent re-tests and their
results.
AIMS Attachment A: AIMS Statement of Work
Page 27 of 130
Exhibit 3
Page 88 of 278
9. Punch-List: The CONTRACTOR shall maintain a continuous log, or
“rolling punch-list,” to record and track all inspections and tests, which
remain “open” or uncorrected at the close of each workday or shift.
The log shall number each item in successive, chronological order and
shall briefly describe the nature and location of the work, the nature of
the inspection or test, cause(s) for rejection, corrective action(s)
recommended, identity of inspector or technician, date the item was
corrected, and identity of inspector or technician who verified the
corrective action.
10. Sign-Off Sheets: The CONTRACTOR will be responsible for
establishing a system of sign-off sheets certifying that all work required
prior to the construction or start-up of critical work elements has been
constructed and installed in accordance with the plans and
specifications. Critical work elements are defined as:
i
Work activities concealing any feature of the work from subsequent
inspection, for example: paving, concrete placement, spray
fireproofing, installation of suspended ceilings.
ii
Start-up activities potentially damaging to work in place (i.e.,
energizing transformers and switchgear, bumping motors).
11. Sign-off sheets shall be initialed by each inspector responsible for
insuring the quality of the work and signed by the CONTRACTOR‟s
Quality Control Supervisor.
12. CONTRACTOR shall provide a copy of the completed sign-off sheet to
the County prior to performing each critical work element.
2.1.5 Meetings
A. Pre-Implementation Conference
1. The County will schedule a Pre-Implementation Conference during
Phase Zero.
2. The purpose of the Pre-Implementation Conference is to review
responsibilities
and
understand
CONTRACTOR‟s
personnel
assignments.
3. The Pre-Implementation Conference shall be chaired by the County's
Project Manager.
4. Authorized representatives of the County, the Consultant, the
CONTRACTOR, and other concerned parties shall each be at the PreImplementation Conference. All attendees shall be persons familiar
with and authorized to conclude matters relating to the work.
5. The Pre-Implementation Conference agenda will be set by the County.
AIMS Attachment A: AIMS Statement of Work
Page 28 of 130
Exhibit 3
Page 89 of 278
6. The following submittals shall be provided by the CONTRACTOR at
the Pre-Implementation Conference: emergency contingency plan,
CONTRACTOR‟s emergency contact numbers, notifications to be sent
to the County and other entities at the work site, copies of notification
to all appropriate agencies, proposed schedule of work, proposed
schedule of shop drawings and sample submittals, with delivery times
for associated equipment and materials, and letter designating
CONTRACTOR‟s competent person on general safety and security
measures.
B. Pre-Installation Conference
1. The CONTRACTOR will call a Pre-Installation Conference, with at
least five (5) calendar days‟ notice to the County.
2. The Pre-Installation Conference is conducted at the site before work
activity commences.
3. The purpose of the Pre-Installation Conference is to ensure final
coordination with the County and with other Airport projects.
4. The Pre-Installation Conference shall be chaired by the County's
Project Manager.
5. Authorized representatives of the County, the Consultant, the
CONTRACTOR, and other concerned parties shall each be at the PreInstallation Conference. All attendees shall be persons familiar with
and authorized to conclude matters relating to the work.
6. The Pre-Installation Conference agenda will be set by the County.
Items to be covered shall include a review of the progress of other
activities and preparations for the work performed under this project.
7. CONTRACTOR shall record significant discussions and agreements
and disagreements, along with any changes to the County-approved
schedule and shall distribute the record of the meeting to everyone
concerned, including the County.
8. CONTRACTOR shall not proceed if the Pre-Installation Conference
cannot be successfully concluded. CONTRACTOR shall initiate
whatever actions are necessary to resolve impediments to
performance of work and reconvene the Pre-Installation Conference
at the earliest feasible date.
C. Preparatory Inspection Meetings
1. CONTRACTOR shall call for a preparatory inspection meeting at least
one week prior to beginning work on each new element of work,
including all items, which have been identified in this Statement of
AIMS Attachment A: AIMS Statement of Work
Page 29 of 130
Exhibit 3
Page 90 of 278
Work as requiring testing, and inspection or which has code-required
special inspections.
2. This meeting shall be conducted by the CONTRACTOR‟s Quality
Control Supervisor and shall be attended by other CONTRACTOR'S
staff and subcontractors as required, the County's Project Manager,
and other County personnel and consultants, as required. Refer to the
Quality Control section of this document for further information.
D. Weekly Progress Meetings
1. The County shall set and conduct weekly Progress Meetings at a
location designated by the County.
2. In addition to the County Project Manager, the CONTRACTOR‟s
Project Manager, plus representatives of subcontractors, suppliers,
consultants, and other entities, as required, concerned with current
progress or involved in planning, coordination or performance of future
activities shall be at these meetings. These individuals shall be familiar
with the project and authorized to conclude matters relating to
progress.
3. Review and correct or approve minutes made by the County of the
previous Progress Meeting. Review other items of significance that
could affect progress. Include topics for discussion as appropriate to
the status of the project.
4. Review the schedule for progress since the last meeting. Determine
where each activity is in relation to the schedule, whether on time,
ahead or behind schedule. Determine how tasks behind schedule will
be expedited; secure commitments from parties involved to do so.
Discuss whether schedule revisions are required to ensure that current
and subsequent activities will be completed within the Contract time.
5. Review the present and future needs of each entity present.
6. No later than three (3) County Work Days after each progress meeting
date, the CONTRACTOR shall distribute copies of minutes of the
meeting to each party present and to other concerned parties who
were not present. Included will be a brief summary, in narrative form, of
progress since the previous meeting. Such minutes shall be reviewed
and commented on by the all of the meeting attendees within two (2)
County Work Days. The comments are to be incorporated by the
CONTRACTOR and then the meeting minutes shall be distributed to
the meeting attendees in their final form.
7. Revise the County-approved CONTRACTOR‟s schedule after each
Progress Meeting where revisions to the schedule have been made or
AIMS Attachment A: AIMS Statement of Work
Page 30 of 130
Exhibit 3
Page 91 of 278
recognized. Issue the revised schedule concurrently with the minutes
of each Progress Meeting.
E. Coordination Meetings
1. From time to time, there may be need of either the County or the
CONTRACTOR to call for a Coordination Meeting.
2. Coordination Meetings may be required by either of the parties.
3. Attendees shall as determined by the County and/or CONTRACTOR.
4. The meeting agenda shall be determined by the County and/or
CONTRACTOR.
5. No later than three (3) County Work Days after each Coordination
Meeting, the County or CONTRACTOR shall distribute minutes of the
meeting to each party present and to other parties as considered
appropriate. Included will be a brief summary, in narrative form, of the
meeting. The minutes will be reviewed and commented on by the all of
the meeting attendees within two (2) County Work Days. The
comments are to be incorporated by the CONTRACTOR and then the
meeting minutes shall be distributed to the meeting attendees in their
final form.
2.1.6 Use Of Premises
A. General Information
1. CONTRACTOR shall use the delivery route and staging area identified
by County.
2. Portions of the Airport beyond the work areas of this project are not to
be disturbed. CONTRACTOR shall conform to site rules and
regulations affecting the work while engaged in the project.
3. CONTRACTOR shall keep existing driveways, roads and entrances
serving the premises clear and available to traffic at all times. These
areas are not to be used for CONTRACTOR vehicle parking or storage
of material.
4. CONTRACTOR shall take all precautions necessary to protect premise
buildings, premise occupants, and personnel from injury or damage.
5. The staging areas to be used by the CONTRACTOR on-Airport shall
be as specified by the County. Additional staging area/storage space
needs to be coordinated with the County on an as-needed basis.
6. CONTRACTOR shall establish and initiate use of temporary facilities at
the time first required for proper performance of the work.
AIMS Attachment A: AIMS Statement of Work
Page 31 of 130
Exhibit 3
Page 92 of 278
CONTRACTOR shall terminate use and remove facilities at earliest
reasonable time, or when no longer needed.
7. CONTRACTOR shall provide, operate, maintain and protect temporary
facilities in a manner that is safe, non-hazardous, sanitary and
protective of persons and property, and free of deleterious effects.
Maintenance includes CONTRACTOR furnishing all required janitorial,
waste collection and disposal services.
8. CONTRACTOR shall surround the staging area with fencing and other
means necessary protect CONTRACTOR‟s and County‟s property
2.1.7 Safety/Security
A.
CONTRACTOR is responsible for protecting the integrity of work areas
to protect CONTRACTOR‟s operations from theft, vandalism, and
unauthorized entry. The use of any security guards shall be
coordinated with the County.
B.
CONTRACTOR shall initiate a security program in coordination with
the County‟s existing overall security program at project mobilization.
C.
CONTRACTOR shall maintain the security program until Final
Acceptance.
D.
CONTRACTOR shall restrict entrance of unauthorized persons and
vehicles into the construction area and existing facilities.
E.
CONTRACTOR shall allow entrance only to County approved and
CONTRACTOR authorized persons.
F.
CONTRACTOR shall maintain a log of workers and visitors under its
control. CONTRACTOR shall make the log available to the County on
request.
G.
CONTRACTOR shall coordinate access of County‟s personnel to the
site in coordination with County‟s security forces.
H.
CONTRACTOR shall comply with the provisions of Attachment II,
Provisions Pertaining to Airport Projects, which is attached to the
Contract Documents and made a part hereof.
2.1.8 Cleaning
A. The CONTRACTOR shall, at all times, keep the site free from
accumulations of waste material or rubbish caused by its employees or
work. Remove all crates, cartons, and other waste materials or trash from
the working areas at the end of each working day. All rubbish and debris,
AIMS Attachment A: AIMS Statement of Work
Page 32 of 130
Exhibit 3
Page 93 of 278
combustible or not, shall be discarded in covered metal containers daily
and removed from the premises at least weekly and legally disposed of at
the expense of the CONTRACTOR.
B. The CONTRACTOR shall be responsible for the general cleaning and
maintenance of the premises and for the coordination and direction of the
cleanup work of its employees.
2.2
SUBMITTAL PROCESS - SUBSTITUTIONS
A. In requesting substitutions, the CONTRACTOR shall prepare an
exceptions, substitutions and product options form, with the following data
provided on the form:
i
Number of Copies Provided
ii
Product/Fabrication/or Installation Originally Specified
iii Specification Section
iv Drawing Number
v
Product/Fabrication/or Installation Proposed Product
B. CONTACTOR shall provide complete product data, drawings and
description of products, and fabrication and installation procedures.
C. CONTRACTOR shall provide samples where applicable or requested.
D. CONTRACTOR shall provide a detailed comparison of the quality
assurance and performance requirements of the proposed substitution
with those of the work originally specified. Requirements shall include
elements such as size, weight, durability, performance, and visual effect
where applicable.
E. CONTRACTOR shall provide complete coordination information, including
all changes required in other elements of the project to accommodate the
substitution, including products installed by the County and separate
contractors.
1. CONTRACTOR shall provide a statement indicating the effect the
substitution will have on the project schedule in comparison to the
schedule without approval of the proposed substitution, including
information regarding the effect of the proposed substitution on the
Contract time.
F. CONTRACTOR shall provide complete cost information, including a
proposal of the net change, if any, in the Contract amount.
G. CONTRACTOR shall provide certification to the County that, in
CONTRACTOR‟s opinion, after thorough evaluation, the proposed
AIMS Attachment A: AIMS Statement of Work
Page 33 of 130
Exhibit 3
Page 94 of 278
substitution shall result in a product that in every significant respect is
equal to or better than the product required by the County's Request for
Proposal, and that it will perform as well or better in the application
indicated. This certification shall include CONTRACTOR‟s waiver of rights
to any additional payment or Contract time as a result of any failure of the
substitution to perform adequately. Such waiver shall be in form and
substance satisfactory to the County's Office of County Attorney.
2.3
QUALITY CONTROL PROGRAM
2.3.1 General
A. In addition to the requirements set forth, CONTRACTOR will comply with
the County's Building Code and the Uniform Building Code to the extent
not in conflict with the County's Building Code. CONTRACTOR shall
perform and document all inspections, tests, and other activities listed in
the Contract Documents. CONTRACTOR's quality control services shall
include inspections and tests and related requirements including
administration, management, supervision, reports, record keeping, or
other services.
B. CONTRACTOR's quality control services do not include quality monitoring
or Contract enforcement activities performed by the County.
C. Quality control activities as described in the specifications shall be
provided by the CONTRACTOR unless specifically stated to be provided
by the County.
D. Quality control services are required to verify compliance with
requirements specified or indicated. These services do not relieve the
CONTRACTOR of responsibility for compliance with the Contract
Documents.
E. Specific quality control requirements for individual construction, fabrication
and procurement activities are as included in the Contract Documents.
F. The quality control services described herein are a minimum and not
intended to limit the CONTRACTOR‟s quality control activities which may
be necessary to achieve full compliance with the Contract Documents.
G. The provisions of the Contract Documents do not limit requirements for
the CONTRACTOR to provide quality control services or other inspections
for the County or other agencies having jurisdiction over the work.
H. A Quality Control Supervisor whose sole responsibility is to ensure
compliance with the Contract Documents is to be included in the Quality
Control Program. This person is to be assisted by other quality control
staff as warranted by specific construction activities and workload.
AIMS Attachment A: AIMS Statement of Work
Page 34 of 130
Exhibit 3
Page 95 of 278
2.3.2 Description of Quality Control Program
A. CONTRACTOR shall provide full and complete documentation of all
quality control activities including: the Quality Control Plan, Detailed
Quality Control Procedures, Progress Reports, Inspection Reports and
Inspection Control Log, Deficiency Log, Weekly Deficiency Reports, Test
Reports, Sign-Off Sheets, Quality Awareness and Training Records, and
project record documents. Copies of this documentation are to be
provided to the County in both hard copy and electronic format.
B. CONTRACTOR shall establish a Quality Control Program to perform
inspection and tests of all items of work, including that of its
subcontractors. This Quality Control Program shall ensure conformance to
applicable specifications and drawings with respect to the materials,
codes, workmanship, construction, finish, functional performance, and
identification. This Quality Control Program shall be established for all
implementation work performed under the Contract Documents. The
CONTRACTOR‟s Quality Control Program shall specifically include
surveillance and tests of equal or better detail as those provided in the
CONTRACTOR's Response to RFP No. 20070514-0-AV-01, dated August
14, 2007.
C. The CONTRACTOR shall describe the Quality Control Program in a
detailed Quality Control Plan that must be approved by the County prior to
the start of the Pre-Installation Conference.
The CONTRACTOR‟s Quality Control Program is the means by which the
CONTRACTOR assures the County that its work complies with the
requirements of applicable laws, codes, Contract drawings, and
specifications. The controls established by the Quality Control Program
shall be adequate to cover all operations, including both on-site and offsite activities and shall be tied to the Phasing Plan. The controls shall
include, at a minimum, at least three phases of inspection for all definable
features of work at the Airport site, as required in Section 2.3.3 of this
Statement of Work. The CONTRACTOR shall notify the County at least 24
hours in advance of every inspection in 2.3.3. All preparatory, initial, and
follow-up inspections shall be made a matter of record in the
CONTRACTOR‟s quality control documentation.
2.3.3 Inspections
A. Preparatory Inspection Meetings - CONTRACTOR shall perform a
preparatory inspection meeting at least one week prior to beginning work
on each new element of work, including all items which have been
identified in the specifications as requiring testing and inspection or which
has code-required special inspections. These meetings shall be
conducted by the CONTRACTOR‟s Quality Control Supervisor and shall
AIMS Attachment A: AIMS Statement of Work
Page 35 of 130
Exhibit 3
Page 96 of 278
be attended by the personnel who will perform the work and a
representative of the County. Each preparatory inspection meeting shall
include:
1. A review of the project requirements, including applicable code
requirements. The purpose is to make sure the people actually doing
the work clearly understand the level of quality required.
2. A check to assure that all materials and equipment have been tested,
submitted and approved.
3. A check to assure that provisions to provide required control testing
have been made.
4. Examination of the work area to ascertain that all preliminary work has
been completed.
5. A physical examination of materials and equipment to assure that they
conform to approved shop drawings or submittal data and that all
materials and equipment are on hand and properly stored.
B. Initial Inspections - CONTRACTOR shall perform an initial inspection as
soon as a representative portion of the particular feature of work is started
and such inspection shall include:
1. An examination of the quality of workmanship.
2. A review of control testing for compliance with Contract requirements.
3. An inspection to make sure there is no use of defective or damaged
materials, omissions and dimensional requirements.
C. Follow-up Inspections - CONTRACTOR shall perform daily follow-up
inspections to assure continuing compliance with Contract requirements,
including control testing, until completion of the particular feature of work.
2.3.4 Quality Control Plan - The CONTRACTOR shall furnish a Quality Control
Plan to the County prior to the Pre-Installation Conference. The Quality
Control Plan shall be updated as required. The Quality Control Plan shall
include the personnel, procedures, instructions and records to be used. The
Quality Control Plan shall include as a minimum:
A. Organization - A description of the CONTRACTOR‟s Quality Control
Organization, including: An organization chart showing lines of authority
and relationship of the Quality Control Organization to other
CONTRACTOR management and project personnel; names and
qualifications of personnel in the Quality Control Organization; area of
responsibility; and authority of each individual in the Quality Control
Organization.
AIMS Attachment A: AIMS Statement of Work
Page 36 of 130
Exhibit 3
Page 97 of 278
B. Inspection - Methods of performing quality control inspections including
those for each subcontractor‟s work,
C. Testing- Description of how testing will be performed, including detailed
lists of testing activities for each specification section.
D. Documentation - Method of documenting quality control operations,
inspection and testing.
E. Administration - Methods of administering quality control operations,
inspection and testing.
F. Quality Awareness and Training - Method of implementing the Quality
Awareness and Training Program including making subcontractors and
suppliers aware of the importance of quality control.
G. Letter of Authority - A copy of a letter of direction to the CONTRACTOR‟s
Quality Supervisor outlining its duties and responsibilities and signed by a
responsible officer of the firm. This letter shall include the authority to halt
construction, reject materials, and to direct removal and replacement of
work not in compliance with the Contract Documents.
H. Forms -Sample copies of all forms and reports to be used, a flow chart
describing their distribution, and identification of those documents to be
retained by the CONTRACTOR.
I. Schedule - A test and inspection schedule organized sequentially by
technical specification section and keyed to the construction schedule.
J. Submittals - CONTRACTOR shall submit the following to the County as
part of the Quality Control Plan:
1. The procedures to be used for scheduling, managing and reviewing all
submittals (shop drawings, calculations, samples, catalogue cuts,
certificates, manuals, etc.) including those of subcontractors, off-site
fabricators, suppliers and purchasing agents.
2. A matrix defining distribution requirements for all submittals required by
the Contract Documents.
3. A submittal status log listing all submittals required by the Contract
Documents, including the scheduled submittal date and the person
and/or organization responsible for each submittal.
K. Subcontractors‟ Quality Control - The CONTRACTOR shall include, as
part of its Quality Control Plan, specific methods of performing quality
control inspections of his on-site and off-site subcontractors.
AIMS Attachment A: AIMS Statement of Work
Page 37 of 130
Exhibit 3
Page 98 of 278
2.3.5 Quality Control Procedures - This is a detailed description of quality control
activities for work under each section of the specifications. It includes a list of
all tests, inspections and frequencies, personnel, instructions, checklists,
procedures, and records. CONTRACTOR shall submit descriptions at least
30 calendar days before starting such work.
A. Before the CONTRACTOR‟s Quality Control Plan is submitted, the
CONTRACTOR shall meet with the County and discuss the
CONTRACTOR‟s Quality Control Plan. The meeting shall develop a
mutual understanding of the details of the plan, including the forms to be
used for recording the quality control operations, inspections,
administration of the plan for both on-site and off-site work, and the
interrelationship of CONTRACTOR and County inspections. The
CONTRACTOR shall prepare minutes of the meeting which shall be
incorporated in the CONTRACTOR‟s Quality Control Plan.
B. Unless specifically authorized by the County, no construction or off-site
fabrication shall be started until the CONTRACTOR‟s entire Quality
Control Plan is approved. Construction of any feature of the work will only
be permitted after approval of the Quality Control Plan, or at least approval
of that portion of the plan applicable to the specific feature of the work. At
the election of the County, no request for payment will be processed until
the entire Quality Control Plan has been approved.
C. If the County determines that the Quality Control Plan, personnel,
inspections, tests, or records are not adequate, corrective actions shall be
taken immediately as appropriate to cure the problem.
D. The CONTRACTOR shall notify the County in writing of any proposed
change to the CONTRACTOR‟s Quality Control Plan; no such change
shall be implemented prior to approval in writing by the County.
E. Implementation of the Quality Control Plan is the responsibility of the
CONTRACTOR. This implementation will be closely monitored by the
County and deficiencies therein will be corrected by or at the expense of
the CONTRACTOR.
2.3.6 Requirements and Standards
A. All Hardware, Equipment, Software, Goods, firmware, and operating
system requirements stated in the Contract Documents are the minimum
requirements. The CONTRACTOR's product shall meet or exceed such
requirements.
B. Equipment and materials shall be standard products of manufacturer(s)
regularly engaged in the manufacture of Equipment specified herein and
shall be the manufacturer‟s latest standard design.
AIMS Attachment A: AIMS Statement of Work
Page 38 of 130
Exhibit 3
Page 99 of 278
C. Provided Goods shall meet the following requirements:
1. Electrically powered Equipment shall be UL approved.
2. Electronic Equipment shall meet the requirements of CFR 47 Part 15.
D. Items of the same classification shall be identical. This requirement
Includes equipment, modules, assemblies, parts, and components.
E. All similar types of personal computers and servers shall be of the same
manufacturer.
F. All similar types of peripherals shall be of the same manufacturer.
2.3.7 Monitoring By the County
A. The County will perform a Quality Monitoring role, closely monitoring
performance of the CONTRACTOR‟s Quality Control Program as to its
effectiveness. The basic measure of effectiveness is that the work is
performed correctly the first time. Secondarily, if a problem does occur,
must be immediately taken by the CONTRACTOR to correct the problem
and to make sure it will not occur again.
B. The County inspectors will spot-check construction primarily for determine
whether the CONTRACTOR‟s Quality Control Program is functioning.
County inspection does not supplement CONTRACTOR inspection.
County testing is independent of CONTRACTOR testing and does not
replace or complement CONTRACTOR Quality Control Testing.
C. All items of materials and Equipment shall be subject to quality control
surveillance by the County at the point of production, manufacture or
shipment to determine if the producer, manufacturer or shipper maintains
an adequate inspection system which insures conformance to the
applicable specifications and drawings with respect to materials,
workmanship, construction, finish, functional performance and
identification. In addition, all items of materials, equipment and work in
place shall be subject to surveillance by the County at the site for the
same purposes. Surveillance by the County does not relieve the
CONTRACTOR of performing quality control inspections of either on-site
or off-site CONTRACTOR‟s or subcontractor‟s work, relieve
CONTRACTOR of any of the requirements imposed on CONTRACTOR
by the Contract Documents.
D. Upon determination by the County that an item will require surveillance by
the County at the point of production, manufacture or shipment, the
CONTRACTOR will be notified in writing of such determination. The
CONTRACTOR shall furnish to the County three (3) copies of all purchase
orders, for all tiers of subcontractors or suppliers for each such item. Also,
AIMS Attachment A: AIMS Statement of Work
Page 39 of 130
Exhibit 3
Page 100 of 278
copies of documented quality control operations, inspections and tests
shall be made available to the County at the points of production,
manufacture and/or shipment.
2.4
PROJECT CLOSEOUT
2.4.1 Contract Closeout Procedures
A. "Contract Closeout" is defined to include general requirements near end of
Contract time in preparation for Final Acceptance.
B. CONTRACTOR shall submit record drawings and project manual for
County‟s review a minimum of 30 calendar days prior to Final Acceptance.
Reviewed documents will be returned to CONTRACTOR should additional
information or revisions be required. All completed record documents
shall be turned over to the County prior to Final Acceptance.
C. CONTRACTOR shall submit written certification that work has been
inspected and is complete in accordance with the Contract Documents
and is ready for final inspection.
D. CONTRACTOR shall provide all required deliverables and submittals to
the County.
E. CONTRACTOR shall deliver written guarantees and warranties prepared
in duplicate, and certificates of inspection to the County for its review and
delivery to County‟s records.
F. CONTRACTOR shall demonstrate to the County the operation and
maintenance requirements.
G. CONTRACTOR shall turn over to the County all COUNTY-issued
identification media, including but not limited to Airport vehicle passes,
personal passes, SIDA media, and other identification.
H. CONTRACTOR shall submit one (1) full set of all required deliverables.
2.4.2 Final Cleaning and Adjusting. Prior to Final Acceptance, CONTRACTOR
shall satisfy the following requirements:
A. General cleaning during progress of work is specified elsewhere. Provide
final cleaning of the work consisting of cleaning the work and staging
areas to normal “clean” condition, which allows use of the work, installed
without additional cleaning. The following are examples, but not by way of
limitation, of cleaning levels required:
1. Clean work and staging areas of litter and foreign objects/substances.
Sweep paved areas to a broom-clean condition.
AIMS Attachment A: AIMS Statement of Work
Page 40 of 130
Exhibit 3
Page 101 of 278
2. Remove pavement stains and other foreign deposits.
B. CONTRACTOR shall clean and remove from site all surplus and
discarded materials, temporary security fencing, and debris of every kind.
CONTRACTOR shall leave site of the work in a neat and orderly
condition. Surplus and waste materials shall be removed from the site of
the work. Waste and debris shall be disposed of in an approved disposal
area off-Airport satisfactory to the County.
C. CONTRACTOR shall remove temporary labels, stains, and foreign
substances from all installed materials.
D. Except as otherwise indicated or requested by the County,
CONTRACTOR shall remove temporary protecting devices and facilities
installed during the course of the work.
E. CONTRACTOR shall comply with safety standards and governing
regulations for cleaning operations. CONTRACTOR shall not burn waste
materials at site, or bury debris or excess materials on the County‟s
property, or discharge volatile or other harmful or dangerous materials into
drainage systems. CONTRACTOR shall remove waste materials from site
and dispose of in a lawful manner at the expense of the CONTRACTOR.
2.4.3 Project Record Documents
A. CONTRACTOR will provide record documentation to the County at the
completion of each phased installation and prior to Final Acceptance. To
ensure that this submittal reflects proper record keeping by the
CONTRACTOR during the course of the work, CONTRACTOR shall
maintain on-site one (1) set of the Contract drawings, specifications,
addenda, change orders and other modifications to the Contract
Documents, and reviewed shop drawings and product data.
B. CONTRACTOR shall legibly mark and record at each specification section
a description of actual products installed, including the manufacturer‟s
name and product model number, product substitutions or alternates
approved and utilized, and changes made by Change Orders or Contract
amendments.
C. CONTRACTOR shall legibly mark record documents and shop drawings
to record actual construction including communication conduit, cabling and
pathways used, field changes of dimensions and detail, changes in details
from those indicated on drawings, details not on original Contract
drawings, and provide make and model of actual product installed.
D. CONTRACTOR shall mark whichever drawing is most appropriate to
showing “field” conditions fully and accurately. If necessary,
AIMS Attachment A: AIMS Statement of Work
Page 41 of 130
Exhibit 3
Page 102 of 278
CONTRACTOR shall provide scaled drawings of modifications and give
particular attention to concealed work, which would be difficult to measure
and record at a later date. CONTRACTOR shall note related change
order numbers where applicable. CONTRACTOR shall organize record
drawing sheets into manageable sets, and print suitable titles, dates,
name of subcontractor, name and signature of job superintendent, and
other identification on cover of each set.
E. CONTRACTOR shall provide to the County at each stage of the phased
installation and prior to Final Acceptance the above records including
“Record Drawings” and all “As-Built Drawings."
2.5
Personnel for Project - The CONTRACTOR shall provide secretarial,
clerical, administrative, technical, and professional personnel as required to
perform the work specified for all project phases. The CONTRACTOR shall
provide a dedicated, stable, and technically qualified staff to maintain
continuity in the level of services. The people named in Exhibit G to the
System Agreement shall actually perform the work required by the Contract
Documents. Requests for substitutions in the original staffing proposed,
evaluated, and accepted are undesirable and will be stringently reviewed. If
possible, the CONTRACTOR shall submit requests for any Key Staff
substitutions in writing to the County 30 calendar days in advance of the
expected date of substitution. The CONTRACTOR is not allowed to make
any Key Staff substitutions without receiving subsequent written authorization
from the County. In addition to the provisions of this Section 2.5, all applicable
provisions of the System Agreement shall apply, including without limitation,
Sections 20.5 and 20.12 of the System Agreement.
A. Special Personnel Qualifications - Personnel possessing unique technical
specialties may be required for supplementary services related to the
scope of regular services. Such personnel shall have qualifications as
required and approved by the County which are appropriate to the nature
of the services that will be provided.
AIMS Attachment A: AIMS Statement of Work
Page 42 of 130
Exhibit 3
Page 103 of 278
3
TECHNICAL REQUIREMENTS
3.1
TECHNICAL OVERVIEW
3.1.1 Integration Requirements
A. The CONTRACTOR shall be responsible for performing all data level
systems integration and interfaces for the EVIDS, RMS, DAPP, CUSS,
LDCS and other identified systems as depicted on drawing T-DG-001.
B. The CONTRACTOR shall be responsible for the development of Interface
Design Documents as follows:
1. The Interface Design Document (IDD) shall be developed for each
interface and shall provide the functional and technical descriptions
and guidelines for the required data, hardware, transport, protocol, and
software configurations for each interface.
2. Each IDD shall include the following sections: general characteristics,
general architecture, functional characteristics, data formats (as
applicable), translation tables (as applicable), transport definition,
physical characteristics, and required Hardware/Software configuration
items.
3. Each IDD shall be submitted for review and approval by the County in
accordance with the overall submittal schedule.
3.2
GENERAL REQUIREMENTS - The Contractor shall comply with the
requirements set forth in this Section 3.2.
3.2.1 References
A. The publications listed below form a portion of this specification.
publications are referred to in the text by basic designation only.
The
B. All specific references in the specifications to codes, rules, regulations,
standards, manufacturer‟s instructions, or requirements of regulatory
agencies shall mean the latest edition in print of each that is in effect at
the date of Contract, unless the document is shown dated.
C. Conflicts:
1. Conflicts between referenced requirements: Comply with the one
which establishes the more stringent requirements.
2. Conflicts between referenced requirements and Contract Documents:
Comply with the one which establishes the more stringent
requirements.
AIMS Attachment A: AIMS Statement of Work
Page 43 of 130
Exhibit 3
Page 104 of 278
3. When conflicts arise, County Project Manager shall have the final
determination as to which document should be adhered to.
D. CONTRACTOR shall comply with the Broward County
Department (BCAD) Communications Policy, latest revision.
Aviation
E. General References - the CONTRACTOR shall comply with the following:
1. Telecommunication Industry Association / Electronic Industries
Association
(TIA /
EIA) 568A
– Commercial Building
Telecommunications Wiring Standards
2. ANSI / TIA / EIA 607 – Commercial Building Grounding and Bonding
Requirements
3. Underwriters Laboratory (UL®) Cable Certification and Follow-Up
Program
4. National Electrical Manufacturers Association (NEMA)
5. American Society for Testing Materials (ASTM)
6. National Electric Code (NEC®)
7. UL Testing Bulletin
8. Institute of Electrical and Electronics Engineers
9. Americans with Disabilities Act (ADA) and County ADA standards.
10. Federal Communications Commission (FCC):
i
49 CFR Part 18 - Transportation: Uniform Administrative
Requirements for Grants and Cooperative Agreements to State and
Local Governments.
ii
49 CFR Part 19 - Uniform Administrative Requirements for Grants
and Agreements with Institutions of Higher Education, Hospitals,
and Other Non-Profit Organizations
11. Section 508 of the Rehabilitation Act, including, but not limited to the
following subsections:
i
The full text of Section 508 is available on www.section508.gov
ii
Section 1194.21 Software applications and operating systems.
iii Section 1194.22 Web-based intranet and internet information and
applications.
iv Section 1194.23 Telecommunications products.
v
Section 1194.25 Self-contained, closed products.
vi 1194.31 Functional performance criteria.
AIMS Attachment A: AIMS Statement of Work
Page 44 of 130
Exhibit 3
Page 105 of 278
12. Part 1193 of the Telecommunications Act Accessibility Guidelines:
i
www.access-board.gov/telecomm/html/telfinl2.htm#21
13. International Organization For Standardization (ISO):
i
ISO 9001; Quality Assurance in Design/Development, Production,
Installation, and Servicing
ii
ISO 9003; Quality Assurance in Final Inspection and Test
iii ISO 9004; Quality Management and Quality System Elements
Guidelines
14. International Air Transport Association (IATA):
i
IATA RP 1706c; Common Use Self-Service (CUSS)
ii
IATA PDF417 2D Bar Code Standard (once established)
15. Software Standards:
i
J2EE™, CORBA®, XML, and SOAP (latest version of software
standards at time of first product submittal).
3.2.2 Contractor Submittals
A. All submittals are subject to County approval. Contract submittals shall be
submitted for one round of review and comment by the County. The
CONTRACTOR shall be responsible for incorporating all comments and
resubmitting. If a revised submittal is rejected by the County, additional
review and comment of the submittal shall be conducted by the County at
the CONTRACTOR‟s expense.
B. The delivery dates of submittals will be negotiated unless specified herein.
The CONTRACTOR shall supply any submittal within five (5) County Work
Days if requested by the County.
C. The CONTRACTOR shall provide the following submittals in addition to
those already required throughout the document:
1. Submittal Schedule
2. Detailed Project Schedule as described in Section 2.1.3.
3. System Environmental Requirements: Provide the environmental
specifications for each system component that will be located in an
Airport communications room. This information shall include heat load
documentation, electrical requirements, equipment dimensions and
weight, and any special requirements or limitations of each system
component.
AIMS Attachment A: AIMS Statement of Work
Page 45 of 130
Exhibit 3
Page 106 of 278
4. Acceptance of existing conditions statement:
Provide written
documentation that confirms the existing infrastructure, systems,
software, and components that are to be utilized by, or integrated with
the new AIMS are acceptable. If upgrades, enhancements, or other
modifications are required, provide detailed information pertaining to
the specific changes that are required for the AIMS to function as
specified.
5. Proposed Products List: Include name of manufacturer, trade name,
model number, related section number, specification paragraph
numbers, and reference standards for each listed product.
6. Interface
Design
interface/integration.
Documents
(IDD)
for
each
identified
7. System Drawings: The CONTRACTOR shall submit drawings that
clearly illustrate the proposed system(s) architecture and show the
normal flow of data throughout the system(s).
8. Head-end Configuration: The CONTRACTOR shall submit drawings
and documentation clearly indicating the AIMS head-end and server
configuration. Configuration details shall include rack layout, server
hardware and software configuration, and storage area network
configuration.
9. System Administration Documentation: The CONTRACTOR shall
supply system administration documentation that details the operation
of all the AIMS.
This documentation shall provide complete
information on the operation, maintenance, and trouble-shooting of the
systems and shall include a parts list and sources of supply for parts.
The manuals are to be bound in three ring or spiral binders with a table
of contents and a tab for each section or division. The information
included in this documentation shall be covered during system training
provided by the CONTRACTOR. In addition, electronic copies in a
County approved format, shall be provided.
10. User Documentation: The CONTRACTOR shall supply user
documentation that explains how the system(s) operates from a user
perspective. This documentation shall be in accordance with and
contain at least as much information as that included within the
system(s) online help system. The manuals are to be bound in three
ring or spiral binders with a table of contents and a tab for each section
or division. The information included in this documentation shall be
covered during system training provided by the CONTRACTOR. In
addition, electronic copies in a County approved format, shall be
provided.
11. As-built drawings: The CONTRACTOR shall supply system as-built
drawings prior to Final Acceptance. These drawings shall be in a
AIMS Attachment A: AIMS Statement of Work
Page 46 of 130
Exhibit 3
Page 107 of 278
drawing format approved by the County and shall detail system
component interconnectivity, component locations, and room/rack
layouts.
12. Parts List:
The CONTRACTOR shall supply complete parts lists and
breakdowns that identify each hardware component (to the lowest
repairable unit) as well as ordering information for these parts.
i
A separate spare parts list shall be provided and include an
itemized list of manufacturers‟ part numbers, model numbers,
budgetary pricing, supplier‟s address, supplier‟s phone numbers
and any single source components identified as such.
13. Documentation Reference: The CONTRACTOR shall supply a
complete list and cross-reference of all supplied documents (i.e.,
name, brief description, and document number).
14. Test Plans: The CONTRACTOR shall supply system test plans
(similar to those submitted with the proposal) for each phase of testing
(i.e., Factory Acceptance Testing, Performance Verification Testing,
and Endurance Testing) as well as all related test results and reports.
Each test shall include a purpose/goal, detailed procedure, and clear
pass or fail criteria. Each specification requirement shall be tested and
referenced. A summary cross-reference between each test and the
specification shall be provided and sorted in the order of the
specification requirements.
15. Display Formats:
The CONTRACTOR shall supply each of the
monitor display formats required for each functional display.
16. Training Plan: Training plan and course materials.
17. COTS Software Report: The CONTRACTOR shall provide a
document identifying each Common Off-The-Shelf (COTS) software
package. The submittal shall state the purpose of the software
package, where it shall be used, and how it shall be used. The
software license information shall be included.
18. Maintenance Schedule:
A recommended schedule for preventative,
routine, and emergency maintenance indicating frequency and
response time. Preventative maintenance services during peak activity
periods shall be avoided. The CONTRACTOR shall coordinate with
the County to define peak activity periods. The CONTRACTOR shall
submit a finalized preventative maintenance schedule for County
approval.
19. Response Escalation Plan: The CONTRACTOR shall submit a
recommended response escalation plan that defines the level of
severity of a problem and the associated service response time. The
use of this response plan and its details will be negotiated with the
AIMS Attachment A: AIMS Statement of Work
Page 47 of 130
Exhibit 3
Page 108 of 278
County. Repairs are to be made as expeditiously as possible. If parts
are immediately unavailable, the fastest means of shipment shall be
used, including overnight-expedited shipping.
20. Disaster Recovery Plan:
Due to the critical nature of airport
operations, the CONTRACTOR shall prepare a disaster recovery plan
for the AIMS. The CONTRACTOR shall include a description of how
the CONTRACTOR will be able to respond with the necessary labor,
hardware, software, technical support, materials, equipment and other
requirements to ensure that the County systems are up and running
properly throughout a disaster scenario. Provide a time table detailing
actions in a “cause and event” scenario. A summary description of the
CONTRACTOR‟s plan shall be provided with the proposal response, a
detailed disaster recovery plan shall be delivered to the County within
90 calendar days of notice to proceed.
21. Software Documentation and Utilities: All software shall be delivered
with full documentation. Documentation shall include software error
messages, description, and troubleshooting guide. The documentation
shall include textual explanations and instructions and be supported by
appropriate graphs, flowcharts and/or block diagrams. Adequacy of
the flowcharts and the block diagrams shall be at the discretion of the
County.
22. Software Backup Copy:
A backup copy of all the configured system
software shall be provided on CD-ROM media. All original distribution
software shall be delivered with an installable backup. While CD-ROM
is the preferred media, tape or diskette is acceptable if required by the
specific software. The backup copy shall be appropriately labeled.
23. Prior to Final Acceptance the CONTRACTOR shall submit revised
Exhibit B “Goods and Systems Hardware”, Exhibit B-1, “Existing
EVIDS Devices”, Exhibit C “Licensed Software and Third Party
Software, and Exhibit E “Master Price List” from the AIMS System and
Services Agreement.
The CONTRACTOR shall submit revised
Exhibits B, B-1, C, and E based on actual installed components and
quantities. These Exhibits shall be initialed by both parties and
attached to the AIMS System and Services Agreement and the
Software License and Maintenance Agreement.
3.2.3 System Documentation
A. System Administration Documentation:
The CONTRACTOR shall
supply system administration documentation that details the operation of
each of the provided systems and integration components.
This
documentation shall provide complete information on the operation,
maintenance, and trouble-shooting of the AIMS and will include a parts list
and sources of supply for parts. The manuals are to be bound in three
AIMS Attachment A: AIMS Statement of Work
Page 48 of 130
Exhibit 3
Page 109 of 278
ring or spiral binders with a table of contents and a tab for each section or
division. The information included in this documentation shall be covered
during system training provided by the CONTRACTOR.
This
documentation shall be provided for each of the individual AIMS including
the AODB, EVIDS, DAPP (including LDCS as applicable), and RMS. In
addition, electronic copies of all documentation shall be provided on CD.
B. User Documentation: The
CONTRACTOR
shall
supply
user
documentation that shall explain how each of the AIMS operates from a
user perspective. This documentation shall be in accordance with and
contain at least as much information as that included within the online help
system. The manuals are to be bound in three ring or spiral binders with a
table of contents and a tab for each section or division. The information
included in this documentation shall be covered during system training
provided by the CONTRACTOR. This documentation shall be provided
for each of the individual AIMS including the AODB, EVIDS, DAPP
(including LDCS as applicable), and RMS. In addition, electronic copies of
all documentation shall be provided in a County approved format.
C. As-built drawings:
CONTRACTOR shall supply system as-built
drawings prior to final system acceptance. These drawings shall be in a
drawing format approved by the County and shall detail system
component interconnectivity, component locations, and room/rack layouts.
The drawings will detail both the physical and logical connections of
system devices. Drawings shall include appropriate labeling for cabling
and devices. In addition, electronic copies of all documentation shall be
provided in a County approved format.
D. Software Documentation and Utilities:
CONTRACTOR shall deliver
All software with full documentation. Documentation shall include software
error messages, description, and troubleshooting guide.
The
documentation shall include textual explanations and instructions and be
supported by appropriate graphs, flowcharts and/or block diagrams.
Adequacy of the flowcharts and the block diagrams shall be at the
discretion of the County representative.
E. Database Structure and Schema:
CONTRACTOR
shall
provide
detailed documentation on any database structure and schema.
Documentation shall include field type, field length, table dependencies,
etc.
F. Maintenance Manuals: Manuals including maintenance instructions and
other descriptive material as received from the manufacturers shall be
provided that will enable County personnel to maintain equipment and test
equipment. This documentation shall include descriptions, specifications,
theory of operation (where applicable), layout drawings (showing
component types and positions), and back-panel and assembly wiring
AIMS Attachment A: AIMS Statement of Work
Page 49 of 130
Exhibit 3
Page 110 of 278
diagrams. This documentation shall be provided for each of the individual
AIMS including the AODB, EVIDS, DAPP (including LDCS as applicable),
and RMS. In addition, electronic copies of all documentation shall be
provided in a County approved format.
G. Preventative Maintenance: Instructions shall be provided for preventive
maintenance procedures that include examinations, tests, adjustments,
and periodic cleaning. The manuals shall provide guidelines for isolating
the causes of hardware malfunctions and for localizing faults. The
manuals shall provide thorough instructions on the use of any specialized
test equipment needed for hardware maintenance. This documentation
shall be provided for each of the individual AIMS including the AODB,
EVIDS, DAPP (including LDCS as applicable), and RMS. In addition,
electronic copies of all documentation shall be provided in a County
approved format.
H. Parts Lists: Complete parts lists and breakdowns that identify each
hardware component (to the lowest repairable unit) as well as ordering
information for these parts shall be provided. Recommended spare parts
lists shall be included in the maintenance manuals. This documentation
shall be provided for each of the individual AIMS components including
the AODB, EVIDS, DAPP (including LDCS as applicable), and RMS.
3.2.4 Delivery and Storage
A. Store products in accordance with manufacturer's instructions, within
CONTRACTOR's staging area and with seals and labels intact and
legible. Store sensitive products in weather-tight enclosures; maintain
within temperature and humidity ranges required by manufacturer's
instructions.
Storage containers shall include adequate security
mechanisms to safeguard all equipment.
B. After installation, provide coverings to protect products from damage from
traffic and construction operations, remove when no longer needed.
3.3
AIRPORT OPERATIONAL DATABASE (AODB) - The Contractor shall
comply with the requirements set forth in this Section 3.3.
3.3.1 General
A. The Airport Operational Database (AODB) will serve as an archival and
retrieval database and an information exchange mechanism.
The
principle role of the AODB is to be the primary holder of all data that
relates to all operational activity both flight and facility related. It will
perform several important support roles including, but not limited to those
listed below.
1. Holds the airport Master Tables and acts as a data validation point
AIMS Attachment A: AIMS Statement of Work
Page 50 of 130
Exhibit 3
Page 111 of 278
2. Includes the ability to receive data both digitally from other systems
and manually by data entry
3. Automatically send data either initiated by a digital transaction or by a
time trigger
4. Collates all data pertaining to a flight record from the time that the
record becomes an active flight record until the total completion of the
planned activity
5. Provides the completed flight record to the appropriate billing
application for the necessary charges to be made
6. Alerts users to irregular operations that are either flight or facility
related
7. Individual system interfaces (data level)
8. Perform data record archiving
9. Provide for data record retrieval
10. Provide alarm notification and logging
11. Provide and support information dissemination to other airport systems
and applications.
3.3.2 AODB Functionality
A. The AODB shall be capable of holding numerous flight related fields
including, but not limited to:
1. Aircraft dimensional data
2. Airline data
3. Registration (tail) number
4. Start and stop times of aircraft rotational activity
5. Start and stop times of aircraft parking activity
6. Code share information
7. Origins
8. Destinations
9. Resource elements such as check-in desk, gate, carousel, and
baggage break down and make up area data.
B. The design of the AODB shall permit the inclusion of additional fields and
tables on an as-needed basis. The amount of additional fields and tables
AIMS Attachment A: AIMS Statement of Work
Page 51 of 130
Exhibit 3
Page 112 of 278
to be supported shall be no less than a minimum of two times the amount
of initially populated database structure.
C. All manual entry of data into the AODB shall be via a graphical user
interface and not directly input into data tables. All manual updates shall
be verified as being valid records prior to any updates being implemented.
D. Interfaces to other systems to automatically input data into the AODB shall
be defined as part of the development of the IDD for each interface.
Electronic data transfer shall be validated by the AODB prior to the record
being automatically updated.
E. The graphical user interface shall also be used to create and update the
Master Tables.
F. At the initial set up of the AODB and for the on-going operations, it is
required that data entered either manually or electronically shall conform
to a set of rules. By applying these rules, erroneous data entry is avoided,
and thus cannot be passed to other systems. These rules are referred to
as the Master Tables and it is against these tables that the AODB shall
verify that the data being sent is not only correct in structure but also that
the content is bona fide.
G. The AODB shall “manage” the Master Tables, in order to ensure
maintenance of a uniform set of Master Table data across all related
systems. The information shall be distributed to other systems such as
EVIDS and RMS. Subsequent updates and distribution of data shall occur
as and when new or amended entries are made into the AODB Master
Tables
H. The AODB shall provide an archive capability that provides “near time”
retrieval of archived data. The data held within the “operational” portion of
the database shall include a minimum of 7 calendar days of operational
data. The CONTRACTOR shall propose, and submit for approval, the
maximum amount of operational data to be stored for real time access that
will not impact the efficiency of the database. In addition to real-time
(daily) operational data, the AODB shall provide the ability to generate
real-time reports for operational data for a minimum of thirty-six (36)
months.
I. All transactions occurring within the AODB shall be logged to provide audit
and tracking capabilities. The system shall also support the creation of a
tracking report detailing all database transactions within a specific, user
definable, time period.
J. The Airport Operational Database (AODB) will serve as an archival and
retrieval database and an information exchange mechanism.
The
AIMS Attachment A: AIMS Statement of Work
Page 52 of 130
Exhibit 3
Page 113 of 278
principle role of the AODB is to be the primary holder of all data that
relates to all operational activity both flight and facility related. It will
perform several important support roles including, but not limited to those
listed below.
1. Holds the Airport Master Tables and acts as a data validation point
2. Includes the ability to receive data both digitally from other systems
and manually by data entry
3. Automatically send data either initiated by a digital transaction or by a
time trigger
4. Collates all data pertaining to a flight record from the time that the
record becomes an active flight record until the total completion of the
planned activity
5. Provides the completed flight record to the appropriate billing
application for the necessary charges to be made
6. Alerts users to irregular operations that are either flight or facility
related
7. Individual system interfaces (data level)
8. Perform data record archiving
9. Provide for data record retrieval
10. Provide alarm notification and logging
11. Provide and support information dissemination to other airport systems
and applications.
K. The County currently uses the PROPworks® Property and Revenue
management system to conduct billing of airlines at FLL. The AIMS must
be capable of communicating airline resource usage information to the
PROPworks® system using the PROPworks® vendor's published API's.
Coordination with BCAD stakeholders shall be performed by the
CONTRACTOR to fully define all interface requirements and final
functionality. As a minimum, the following information shall be made
available to the billing system via these interfaces:
1. Airline RON information.
2. Ticket counter usage information.
3. Gate usage information.
4. Landings information.
AIMS Attachment A: AIMS Statement of Work
Page 53 of 130
Exhibit 3
Page 114 of 278
L. For each and every interface to the AODB, the CONTRACTOR shall be
responsible for developing IDD as described in Section 3.1.1. In
developing these documents, the CONTRACTOR shall coordinate with
the appropriate airport and tenant stakeholders.
M. The AODB shall conform to all requirements in this Statement of Work.
3.3.3 Integration Requirements
A. The AIMS shall have interface capabilities with Network Time Protocol
obtained through the local area network.
B. The AIMS shall have the capability of providing read only flight data to
locations that are external to the Airport. The data interface shall be
standard leased lines or other mediums as necessary.
C. The AIMS shall include an interface with the Airport web server to provide
the ability to display flight information on the Airport‟s web site.
1. As an alternate, the CONTRACTOR shall propose and provide pricing
for a solution that includes an AIMS interface to a CONTRACTOR
hosted web server to provide the ability to display real time flight
information.
The Airport web site shall include a link to the
CONTRACTOR hosted web site.
D. The AODB shall interface with the existing property revenue management
system as defined in Section 3.3.2. The final functionality of this interface
shall be determined during design workshops and coordinated with the
County.
E. For each and every interface listed above, the CONTRACTOR shall be
responsible for developing IDD as described in Section 3.1.1. In
developing these documents, the CONTRACTOR shall coordinate with
the appropriate airport and tenant stakeholders.
F. For additional database system requirements refer to Section 3.10,
System and Software Requirements.
G. The AIMS shall support future interfaces / integration with an audio paging
system to provide an integrated audio/visual paging solution.
H. The AIMS shall support interfaces with an external system(s) to obtain
real-time “on/off block” information for aircraft operations at gates. This
interface shall provide the ability for the AIMS to accept actual arrival and
departure times for aircraft movement at gates. The data obtained from
this interface shall be accessible through the AODB to provide report
generation capabilities and the ability to interface with County‟s property
and revenue management system.
AIMS Attachment A: AIMS Statement of Work
Page 54 of 130
Exhibit 3
Page 115 of 278
3.4
ELECTRONIC VIDEO INFORMATION DISPLAY SYSTEM (EVIDS) - The
Contractor shall comply with the requirements set forth in this Section
3.4.
3.4.1 System Overview
A. An Electronic Video Information Display System (EVIDS) shall be installed
to support the entire airport campus. The system installed will replace the
existing system and will utilize existing display hardware to the extent
feasible.
B. The EVIDS shall be configured to run on a full-time basis, twenty-four (24)
hours per day, seven (7) days per week, in order to provide accurate and
timely information.
C. The EVIDS shall provide flight, baggage, visual paging, and other BCAD
defined information to various displays throughout the campus.
D. The EVIDS shall fully support all code share flights and be able to provide
mechanisms for displaying the appropriate code share information on
public displays. In addition, the system shall not require duplicate entry of
information for code share flights (i.e. a single data input will update
multiple flight records where code sharing exists).
E. The information displayed on the video monitors for the EVIDS will vary
depending on the monitor‟s location and function; however, all monitors
shall have the capability to display all types of information.
F. Time obtained from the Local Area Network using Network Time Protocol
shall be displayed on EVIDS screens as part of the page header as well
as on dedicated displays. Displays that are part of EVIDS banks shall be
used to display arriving and departing flight information.
G. The displays located in the baggage claim area shall display flight
baggage carousel assignments. These assignments shall be determined
by the RMS and verified prior to unloading baggage by inputting the flight
assignment into the Baggage Input Consoles (BICs). The BICs shall be
located in the baggage breakdown area and connected to the PDS via the
assigned EVIDS VLAN.
H. EVIDS workstations shall be used to update flight information and to
administer the EVIDS. Each airline shall have access to an EVIDS
workstation to perform their required updates.
Certain EVIDS
workstations shall be configured to access multiple airline information for
service providers that handle multiple airlines. Coordination shall be
performed with the County representative to determine the final
configuration of these workstations.
AIMS Attachment A: AIMS Statement of Work
Page 55 of 130
Exhibit 3
Page 116 of 278
I. EVIDS flight information shall be integrated with the Airport‟s web site to
provide real-time flight information to the general public. This integration
and all requirements associated with the web site interface shall be
coordinated with the County.
1. As an alternate, the CONTRACTOR shall propose and include pricing
for a solution that utilizes a CONTRACTOR hosted website providing
real-time flight information for all FLL flights. Coordination with the
County shall be performed to establish a link to this site from the
airport website.
3.4.2 EVIDS Configuration Requirements
A. The current configuration of the EVIDS at FLL is a mixed environment of
various distribution architectures.
This includes the use of video
extenders where a single DDC (Display Devices Controller) (located within
communications rooms) is used to drive multiple displays, single DDCs
attached to display devices, serial connectivity to LED devices, and the
use of thin clients (Wyse V90 and Wyse V90LE terminals) in a one to one
configuration.
In supporting the existing display environment, the
CONTRACTOR‟s solution shall support all existing architectures. All new
display devices installed as part of this project shall be configured as
described herein.
B. Each video monitor in the system shall be connected to a single DDC
(Wyse V90LE terminals or current equivalent) that is used to control the
display of the data on the monitor.
C. Baggage Input Consoles (BICs) shall be connected to and controlled by
the EVIDS. All BICs shall be IP addressable and utilize an Ethernet
protocol to communicate with the EVIDS servers. CONTRACTOR shall
specify any specific BIC protocol requirements that deviate from the IP
protocol. The functionality of the BIC devices shall include the following:
1. The ground operator shall be able to indicate which flight is being
unloaded onto the particular baggage carousel using the keypad. The
EVIDS shall not allow the operator to specify a flight that is not an
arriving flight contained in the current day's active flight schedule. After
the operator has specified a valid flight number on the keypad, the
operator shall press a key designated as "first bag on", and shall
update all EVIDS information (including BIDS information) pertaining to
this flight and carousel.
2. “Canned” messages as defined by the County shall be selected and
displayed via the BIC assigned display.
D. The DDCs shall be capable of supporting the display of flight data, graphic
images, text messages, and full motion video.
AIMS Attachment A: AIMS Statement of Work
Page 56 of 130
Exhibit 3
Page 117 of 278
E. The CONTRACTOR shall provide an interface to each airline host system
to provide for automated flight information input into the EVIDS. For each
airline present at the time of installation, the EVIDS shall receive
automatic downloads and update from the airline host. The airline
interface shall not require any customization by the airlines to their
systems and shall include appropriate security to ensure that the EVIDS
and all data within the system is properly secured. The CONTRACTOR
shall supply all interface hardware and software required for each airline.
The airline data from the airline system shall be formatted as necessary
for use in the EVIDS database. Pricing for airline host interfaces shall be
itemized and pricing for adding an airline shall be provided. The following
list of current airlines serving FLL shall interface with the EVIDS:
1. Air Canada
2. Air Jamaica
3. Air Sunshine (commuter)
4. Air Transat
5. Allegiant
6. AirTran
7. American
8. Avianca
9. Bahamas Air
10. CanJet
11. Caribbean
12. Chalks (commuter)
13. Comair
14. Continental
15. Continental Connection (Gulfstream)
16. Delta/Delta Connection
17. Frontier
18. JetBlue
19. Lynx Air International (commuter)
20. Northwest/KLM
21. Skyservice
22. Southwest
23. Spirit
24. Sunwing
25. US Airways
26. Westjet
27. Yellow Air Taxi (commuter)
28. In addition to the airlines listed above, the CONTRACTOR shall be
responsible for providing a direct interface for additional airlines that
may be present at the time of installation.
F. The EVIDS shall fully support airlines that brand different airlines under a
single IATA airline code.
AIMS Attachment A: AIMS Statement of Work
Page 57 of 130
Exhibit 3
Page 118 of 278
G. The EVIDS shall fully support the storage, display, and manipulation of
information for airlines that operate out of multiple terminals and that may
split terminals in terms of check in operations, gate operations, and
baggage operations.
H. The EVIDS shall support an interface to a third party flight information
system to provide real-time accurate flight information into the system.
The system shall include rules to determine which source of flight
information to utilize (third party, host feed, or local input) in the case of
conflicting information.
The CONTRACTOR shall provide this
functionality. The solution shall include all hardware, software, equipment,
licensing fees, and subscription fees to accomplish this functionality.
3.4.3 Display Requirements
A. General: The CONTRACTOR shall make a concerted effort to create
display formats that eliminate or reduce, to the extent feasible, ghosting
and image retention. Coordination shall be performed with the County
representative to identify potential solutions for reducing these effects.
B. Fonts: The EVIDS shall be able to display video monitor screens in a
variety of fonts. CONTRACTOR shall supply a minimum of twelve (12)
different font styles with the EVIDS. The default font shall be approved by
the County.
1. The user shall be able to specify the font to be used and the size of the
font, per field.
2. The capability shall exist to use multiple fonts within one display
format.
3. Scalable outline font technology shall be used in the DDCs to display
fonts on the video monitors.
4. The provided font selection shall address ADA compliance issues.
The CONTRACTOR shall recommend fonts that meet the needs of
visually impaired individuals.
The CONTRACTOR shall provide
documentation to support their recommendations.
C. Colors: The user shall be able to specify the colors to be used in any
screen format from a palette of no less than 65,000 colors.
1. Color shall be able to be specified for the format background and
foreground.
2. Colors shall be able to be assigned on a per-field basis, defaulting to
the specified foreground color.
AIMS Attachment A: AIMS Statement of Work
Page 58 of 130
Exhibit 3
Page 119 of 278
3. Colors shall be able to be assigned based on field content. For
example, color coding within a field may be used where "On Time" is
color #1, "Delayed" is color #2, and "Canceled" is color #3.
D. Graphics: The user shall be able to specify graphic images to be used
within a video monitor display format.
1. The graphic image shall be stored in any industry-standard graphic
format. Supported formats shall include PCX and GIF. Other formats
will be converted to either PCX or GIF formats.
2. The user shall be able to specify the size of the frame for the graphic
image. The graphic image shall auto scale to fit the frame.
3. The system shall provide the capability to display a graphic image as a
screen "wallpaper" (i.e., a full screen graphic that data including text
and/or other graphics are overlaid onto).
4. Multiple graphics shall be displayable simultaneously within a single
display format.
E. Display configuration: The system shall support the display of all screens
both horizontally and vertically on the display devices.
F. Video Clips:
The user shall be able to specify graphic images to be
used within a video monitor display format. A variety of video clip formats
shall be supported including AVI and MPEG formats.
G. Multiple Formats/Split Screen: The EVIDS shall have the capability to
display multiple formats on a display device using both of the following
methods:
1. A "split screen" where some data is shown in one defined part and
other data is shown in a separately defined part. An example would be
a video monitor displaying flight data for a specific airline with limited
flights, with Arriving Flights shown in the upper half of the monitor and
Departing Flights shown in the lower half of the monitor.
2. A display device that has been designated to display certain formats in
a rotating fashion. For example, Format „A' would be shown for a userdefined number of seconds, then Format „B' would be shown for a
user-defined number of seconds, then repeat. Rotating formats shall
allow up to eight (8) different formats to continuously cycle.
H. User-Defined Parameters & Triggers: The authorized user shall be able to
specify a number of parameters or "triggers" that define how and when
data will be displayed using any specific display format (e.g., color
change, text appear/disappear, graphic appear/disappear, font change).
AIMS Attachment A: AIMS Statement of Work
Page 59 of 130
Exhibit 3
Page 120 of 278
These parameters or triggers include but are not limited to the items
below:
1. Length of time a flight is displayed with a "DEPARTED" (or similar)
status after the flight has actually departed. This shall be definable
both on a system-wide basis, and on an airline-specific basis.
2. Length of time before a flight arrives to display the arriving flight
information. This shall be definable both on a system-wide basis, and
on an airline-specific basis.
3. For flight departures, the user shall be able to specify how long before
departure time the flight status changes to "Boarding" and/or "Final
Boarding". This shall be definable both on a system- wide basis, and
on an airline-specific basis.
4. In conjunction with this trigger, there shall be a parameter, changeable
by the authorized user, which indicates whether or not to utilize this
automatic timing feature, or to require manual input from an authorized
user.
5. For flight arrivals, the user shall be able to manually specify how long
before the flight actually arrives that the flight status changes to "In
Range" and/or "Landing", and finally "At Gate".
I. Sort Order: The user shall be able to specify the sort order for data being
displayed where there is more than one data record being displayed.
1. The user shall be able to specify either ascending or descending order.
The default shall be ascending order.
2. The system shall have the capability to specify multiple fields for the
sort and to select the sort priority of each field. If more than one field is
specified, each may be designated as either ascending or descending
order.
3. The fields which may be specified to be sorted include, but are not
limited to:
i
Flight number
ii
Airline
iii Domestic/International
iv Gate
v
County name (origin/destination)
vi Scheduled time of arrival/departure
vii Actual time of arrival/departure.
AIMS Attachment A: AIMS Statement of Work
Page 60 of 130
Exhibit 3
Page 121 of 278
4. Override of Automatic Status Updates: The authorized EVIDS user
shall have the capability to override any of the automatic update flight
status remarks. If the scheduled time of a flight is changed, the default
Remark for that flight shall be automatically changed to show "ARR AT
<new time>" for an arriving flight, or "DEP AT <new time>" for a
departing flight. The user shall also have the capability to edit the
remark and shall not be limited to "canned" remarks.
5. Display Format Re-Assignment: Any monitor that is displaying a
specific format, controlled by the DDC, shall be capable of displaying a
different format upon command from the EVIDS server(s), initiated via
an authorized user using any of the input devices (i.e., EVIDS server,
EVIDS workstation, BIC, Touch Screen).
6. The authorized user shall be able to view the name of the format that is
currently being displayed on any display device by accessing the
particular record in the device table. When the user makes a change
to the format being used by that device, the DDC is notified of the
change via the network. The device shall use the new format
immediately.
7. There shall be no restrictions in format reassignment.
8. No shutting down or rebooting of any equipment shall be required in
order to change the format being used by any DDC.
J. Free-Text Formats
1. The EVIDS shall allow a free-text format (e.g., a monitor displaying
"Welcome ABC Convention attendees, please pre-register for the
conference at the airport information desk") to be displayed on a
monitor. This format is different from other formats in that there may
be no data coming from the EVIDS databases to update the contents
of the display. The data to be displayed shall be determined by the
authorized user.
2. The authorized user shall enter and format text, choosing font style,
type, and size in the same manner as is allowed with other formats.
3. The user shall also be allowed to insert graphic image(s) into the freetext format, resizing the graphic image(s) to fit the defined location(s)
as is allowed with other formats.
4. The EVIDS shall allow any number of free-text formats to be used and
shown simultaneously on different monitors, or in a "slide show" format
on the same monitor. The parameters of the “slide show” shall be user
definable (i.e., show x number of screens for x seconds each).
5. The system shall allow a location for free-text to be pre-defined on a
display format. Check-in agents or other authorized users shall have
AIMS Attachment A: AIMS Statement of Work
Page 61 of 130
Exhibit 3
Page 122 of 278
the ability to change the free-text message displayed. The system
input devices (i.e., EVIDS server(s), EVIDS workstation, Touch
Screen) shall be capable of updating the free-text message.
K. Synchronized time (obtained through the local area network via NTP) shall
be displayable in the header of an EVIDS page. The time display shall be
active when there is a signal from the PDS. If this connection is broken,
the time display on the EVIDS shall go blank. The display shall not "free
wheel" from the internal DDC clock.
L. Initial display screens provided shall include, but not be limited to; airline
directory, rental car agency directory, airport contact directory, flight
information display, ticket counter displays, gate displays, baggage
information display, visual paging displays, and general information
displays.
3.4.4 Screen Designer Requirements
A. The EVIDS shall include a Screen Designer Module (SDM) that shall allow
an authorized user to create display formats.
B. Via the SDM, the user shall be able to create display formats for
displaying data on video monitors. Data to be displayed includes, but not
limited to, flight data, baggage data, flight operations data, graphic data,
and free-text data.
C. Each display format shall be saved in the database. Based on a “County”
field within the record the format may be utilized by other users for the
display of data.
D. Minimum display characteristics shall be specified in the SDM include, but
not limited to:
1. Background and foreground color
2. Font type, style, and size, per field
3. Blink attributes; blinking on/off colors
4. Header and footer placement and content
5. Sort order of data; ascending or descending order, sort on one or more
of the following: flight number, city name, gate, time, airline
6. Background “wallpaper”
7. Color graphics; exact placement on the screen and graphic resizing
8. The SDM shall include the capabilities for the user to “test” the new or
revised format by showing it on the screen of a workstation in the same
AIMS Attachment A: AIMS Statement of Work
Page 62 of 130
Exhibit 3
Page 123 of 278
manner as it would be seen on a monitor or other display device, using
live data from the actual EVIDS database.
9. CONTRACTOR shall provide a minimum of two (2) different types of
screen formats for each type of data display that will be used by the
system (e.g. flight arrivals, flight departures, gate information, baggage
master display, baggage carousel display, baggage handler‟s back
room display, etc. The authorized user shall be able to create new
formats and modify existing formats via the SDM.
3.4.5 Airline Interface Requirements
A. Airlines shall have the ability to update EVIDS information from an
external source (i.e., through their host systems). The interface must be
capable of accepting ASCII formatted data via various connections
including, but not limited to, TCP/IP, serial RS-232 connection, and others
as defined in the IDD. This interface shall be coordinated with the County
and the airlines‟ technical representatives. Any interface to an external
system shall include the appropriate security measures to ensure that the
integrity of the EVIDS system, and all data supported, is maintained. As a
minimum, all interfaces shall be through a firewall and demilitarized zone
(DMZ).
3.4.6 Timing Window
A. The term "timing window" is used to refer to the amount of time prior to a
scheduled event that an item becomes eligible for display. It is typically
used for monitors showing flight arrivals or flight departures. For arrivals,
the timing window is the amount of time prior to the scheduled arrival time
of a flight before the flight is considered eligible for display. For
departures, the timing window is the amount of time prior to the scheduled
departure time before a flight is considered eligible for display. For
example, if the current time is 11:00 a.m. and the timing window for
departures is set to 120 minutes, flights scheduled for departure between
11:00 a.m. and 1:00 p.m. would be displayed, while those departing after
1:00 p.m. would not yet be eligible for display on departures monitors.
The timing window shall be adjustable to allow the EVIDS displays to be
“full” at all times.
B. The EVIDS shall support two types of timing windows: a static mode and a
dynamic mode.
C. The static mode timing window shall be definable by the authorized user.
A separate time window shall be definable for both arriving and departing
flights. There shall be an option to allow these timing windows to be set
on both a system-wide basis and on an airline-specific basis.
AIMS Attachment A: AIMS Statement of Work
Page 63 of 130
Exhibit 3
Page 124 of 278
D. When operating in dynamic mode, the timing window shall automatically
adjust based on the number of flight operations at a given time. For a
grouped set of monitors (e.g., monitor bank, portion of monitor bank), the
EVIDS shall keep all monitors filled with flight records. In order to
accomplish this, the EVIDS shall dynamically adjust the timing window to
be a higher or lower value, as required. The minimum range of timing
window adjustment will be from thirty (30) minutes to forty-eight (48) hours
in increments of one (1) minute.
E. The system shall default to dynamic mode timing window.
3.4.7 Video Advertising Requirements
A. The EVIDS shall have the capability to display full-motion video (minimum
30 frames per second) on all video monitors throughout the system.
B. The user shall be able to specify a section of the video monitor format
(where "section" may be a subset of the entire screen or may be the entire
screen) for displaying full motion video.
C. The video source shall be from a video data file that was previously
downloaded from the host computer system to the hard disk of the DDC,
or through the network, if available bandwidth is available.
D. The system shall also support interfacing to third party systems and / or
web sites for the retrieval of advertising files (video, still images, and audio
files) to be broadcast on the EVIDS.
E. Scheduling requirements: The system shall have the capability to allow
an authorized user to schedule the playing of video files on all monitors
throughout the system from any workstation. As a minimum, the system
shall possess the following attributes regarding the scheduling of video
files:
1. The schedule for display of video files shall have the ability to predefine a schedule for all monitors throughout the system. The schedule
shall also allow any number or combination of monitors to be included
in the schedule (i.e., only monitors 1, 3, 5, etc.).
2. Local override capabilities shall also be included to allow authorized
users to modify the schedule or playing of video clips on an ad-hoc
basis.
3. The system shall also include a “dynamic” mode that allows video files
to be played on monitors that are not displaying flight information due
to lack of flight activity. For instance, if a monitor bank of eight (8)
monitors is only utilizing six (6) monitors to display the required timing
window for flights, the remaining two (2) monitors shall display the preAIMS Attachment A: AIMS Statement of Work
Page 64 of 130
Exhibit 3
Page 125 of 278
selected video files. This capability shall be integrated with the
scheduling features to allow video files to be played when select
monitors become available (i.e., no flight activity is being displayed).
4. The system shall include a tracking feature that logs all video files that
have been played and details the time, length, the display monitor that
was used, and a summary of the number of times each video was
played on each monitor as well as the total number of times each video
was played in a given time period throughout the airport.
3.4.8 EVIDS System Requirements
A. The EVIDS shall meet the requirements of Section 3.10, System and
Software Requirements as a minimum. Additional system requirements
are provided in the Contract Documents.
B. All EVIDS modules (i.e., end user workstation, visual paging, video
advertising, Screen Designer Module) shall have a Graphical User
Interface (GUI) and use a true windowing (i.e., not DOS-based windows)
navigation interface.
C. All display devices controlled by the EVIDS shall have the ability to display
public “evacuation” messages. The system shall support the ability to
display these messages on display devices that are zoned/targeted to
specific areas of the campus. The control of the evacuation messages,
including the ability to choose the areas/zones where the messages will
be displayed, shall be available from workstations located in the
communications center.
D. Data input screens (i.e., forms) shall be provided. In no instance shall
data be input directly into data tables.
E. Airline data availability shall be limited to authorized user login. In no
case, shall any user identified via user name and password as an airline
employee or any other user without proper authorization gain access to
any other airline's data, other than that pertaining to their own flights and
baggage. Data that can be viewed at the user's workstation pertaining to
other airlines shall be limited to data that can be viewed on public EVIDS
video monitors.
F. Server failure shall not affect the DDCs operation or monitor displays.
G. System Management:
1. All failures of the system shall be viewable at a central control point
(i.e., the system administrator's workstation). The failure shall initiate
an alarm and add a failure record to the failure database table.
AIMS Attachment A: AIMS Statement of Work
Page 65 of 130
Exhibit 3
Page 126 of 278
2. Additionally, upon such a failure, the system administrator shall receive
a warning message on the system administrator workstation and an email, pager, or text message notification, notifying him of the failure.
Server failure shall include any hardware or software based failure.
Should a DDC fail, the system shall immediately notify the system
administrator via the EVIDS management system.
The
CONTRACTOR is responsible for providing all hardware, software,
and WAN/PSTN access necessary to support the notification functions.
3. Each DDC shall have remote administration and monitoring
capabilities. This capability shall allow the specific machine to be
remotely configured and to provide a status report to the management
system. Data included in the reporting capabilities shall include: data
pertaining to the machine's memory, storage devices, network
connections, and general health of the machine.
4. All failures of the system shall be logged at a central control point (i.e.,
EVIDS Application Server). The failure shall initiate alarms and reports
(e.g., time and date of failure event). In the event that a workstation
component goes out of service, the central control log shall be
updated. Therefore, where practical, a positive relationship (e.g.,
system heart beat) shall exist between all components of the systems
at all times.
3.4.9 EVIDS Performance Requirements
A. In addition to the performance requirements listed in Section 3.10, the
EVIDS shall conform to the following:
1. The system shall be capable of supporting all DDCs and display
devices as specified in this document within the performance
requirements as outlined herein.
2. In the event of a failure of a DDC that is used to control a display within
a public display bank, the system shall automatically reconfigure the
page displays within the display bank to ensure that the flight
information that was to be displayed on the failed DDC/monitor is
displayed on other monitors. In the instance of a DDC failure, the
system shall automatically reconfigure the timing window, or utilize
another mechanism, to ensure that no gaps in the displayed flight
information are present. For example, if a DDC supporting a display
showing flights from 10:15 AM to 10:45 AM fails, the system shall
reconfigure the displays such that the other DDCs display the flights
during this time period.
AIMS Attachment A: AIMS Statement of Work
Page 66 of 130
Exhibit 3
Page 127 of 278
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 twentynine (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.
AIMS Attachment A: AIMS Statement of Work
Page 67 of 130
Exhibit 3
Page 128 of 278
2. The RMS and DAPP shall provide the ability to block any user from the
utilization of any resource. The default configuration at each DAPP
resource shall be to deny access, unless it has been assigned by the
RMS.
3. The workstations shall run the native tenant applications.
D. The DAPP shall provide „transparent‟ access to each airline‟s native host
application. The DAPP solution shall not require an on-going certification
process once final system acceptance is complete. Individual airline
upgrades and modifications to point of sale and other operational software
shall not require any certification (or recertification) to utilize the DAPP.
This does not apply to certifications required by legacy common use
applications (IATA RP 1797 compliant) that may utilize the flexible
provisioned environment provided by the DAPP.
E. The DAPP shall provide 2D Bar Code Printing for boarding passes.
Traditional IATA ATB magnetic swipe boarding coupons are not required,
unless specifically requested by airline tenants during the implementation
process.
F. The DAPP shall provide use of each airline‟s native system from all
locations within the Terminal 4. The DAPP shall provide any agent the
ability to access their own applications from any assigned DAPP
workstation via authorized airline-host login. The DAPP shall allow each
airline to run its own native point-of-sale application in its own operating
environment. At the DAPP workstation, the screen and keyboard interface
shall be no different than a direct host connection. Any applications which
are available on the host system shall also be accessible through the
DAPP. This system shall provide each airline the ability to perform
ticketing, check-in, local boarding, passenger matching, etc. using their
system software without modifications to the host system.
G. The DAPP shall fully support individual airline requirements for
workstation and peripheral addressing. This shall include the ability for
airlines to dynamically assign workstation addresses on an ad-hoc basis
from a pool of addresses, eliminating the need to have dedicated
workstation addresses for every device associated with DAPP. Individual
airline software licensing issues must also be addressed by the
CONTRACTOR in a manner that is acceptable to all stakeholders. This
topic shall be included in the design workshops that are required as part of
the implementation process.
H. The system shall provide connection for the DAPP workstations to each
participating airline‟s host computer (e.g., System One, Sabre, etc.) via an
airline-provided interface (e.g., gateway, router, etc.). This shall allow for
the required airline applications and operating systems to be loaded at the
AIMS Attachment A: AIMS Statement of Work
Page 68 of 130
Exhibit 3
Page 129 of 278
workstation on an airline by airline basis. Access to the airline interface
shall be over the assigned virtual network. The location of airline specific
software required to utilize a DAPP workstation shall be stored either on a
local partitioned hard drive, a centralized location such as a boot server, or
a CONTRACTOR determined location.
It is the responsibility of the
CONTRACTOR to perform the necessary airline coordination to ensure
the system supports the individual requirements of each identified airline.
I. An unassigned DAPP station shall provide a generic login screen that
allows access to any DAPP applications that may be required for system
maintenance or other functions. This access shall be for authorized users
only via the appropriate login credentials.
J. The DAPP workstation shall use the common system hardware with the
individual airline‟s native applications. The printers can either be loaded
with common printing stock, or each airline can load their own stock when
utilizing a position. It is the responsibility of the CONTRACTOR to perform
the necessary coordination with airline representatives to ensure each
airline‟s peripheral requirements are met by the system.
K. The DAPP shall utilize an open architecture. To the extent possible,
hardware components of the DAPP shall be standard “off-the-shelf”
computer components.
L. The system shall provide access to the airline host computer system
applications. From any DAPP workstation any authorized user shall be
able to access host applications. Typical host applications which the
system shall access include (but are not limited to):
1. Departure Control
2. Reservations
3. Ticketing
4. Check in
5. Local Boarding Application
6. Baggage Tracing
7. Flight Operations Control
8. Message Switching
9. Information Systems such as FIDS
10. Aircraft Maintenance Systems
11. Cargo Systems
AIMS Attachment A: AIMS Statement of Work
Page 69 of 130
Exhibit 3
Page 130 of 278
12. Baggage Sorting/Reconciliation System
13. E-mail.
M. The DAPP shall support and be interoperable with the addition of nonhosted Airlines and County applications operating in a client/server (peer
to peer) or web-based environment.
N. Any DAPP workstation shall be able to be assigned to any airline and
access any airline host system.
O. Workstations shall be mutually independent of each other (e.g., two DAPP
workstations at the same gate counter can access two different hosts
simultaneously).
P. Workstations shall be able to direct output to a peripheral device that is
physically connected to another workstation on the same virtual network.
As such, the ability to print boarding passes and bag tags from any
workstation to any other workstation shall be provided. The system shall
support this functionality whether at the host level or at the individual
workstation level.
Q. Each airline's host and operating environment shall be supported by the
CONTRACTOR's system.
R. The DAPP shall maintain the latest airline point of sale software on all
devices. Any DAPP resource shall be available for any airline use at any
given time, at the discretion of the County.
3.5.2 Airline Requirements
A. The airlines listed below shall be serviced by the DAPP. It is the
CONTRACTOR‟s responsibility to verify/determine airline host and to
determine host application and peripheral interface requirements.
B. Cost for integrating each airline into the DAPP shall be listed as a line
item. Additionally, per airline cost shall be provided for adding additional
airlines to the DAPP.
C. Airlines to be serviced include, but are not limited to:
1.
2.
3.
4.
5.
6.
7.
Air Canada
Air Jamaica
Air Sunshine (commuter)
Air Transat
Allegiant
AirTran
American
AIMS Attachment A: AIMS Statement of Work
Page 70 of 130
Exhibit 3
Page 131 of 278
8. Avianca
9. Bahamas Air
10. CanJet
11. Caribbean
12. Chalks (commuter)
13. Comair
14. Continental
15. Continental Connection (Gulfstream)
16. Delta/Delta Connection
17. Frontier
18. JetBlue
19. Lynx Air International (commuter)
20. Northwest/KLM
21. Skyservice
22. Southwest
23. Spirit
24. Sunwing
25. US Airways
26. Westjet
27. Yellow Air Taxi (commuter)
3.5.3 DAPP Performance Requirements
A. In addition to the performance requirements listed in Section 3.10, the
DAPP shall conform to the following:
1. DAPP Latency: The time from when a DAPP position (and any
associated CUSS position) is assigned to an airline via the RMS
interface and the position is fully operational for passenger processing
shall not be more than three (3) minutes.
2. In Line CUSS: For an in-line CUSS kiosk, the time from when an
airline is selected for self-service check-in and the selected self-service
check-in application is fully operational for use shall not be more than
ten (10) seconds. A “loading” or other similar screen shall be
displayed within 1.0 seconds after the airline is selected.
3.5.4 DAPP Hardware Requirements
A. The DAPP shall meet the requirements outlined in Section 3.9
B. Refer to drawings for hardware types and quantities.
C. In addition to the components shown on the drawings, the CONTRACTOR
shall provide five (5) DAPP workstations to be used in baggage offices.
The location of these devices shall be coordinated with the County.
AIMS Attachment A: AIMS Statement of Work
Page 71 of 130
Exhibit 3
Page 132 of 278
3.5.5 CONTRACTOR Responsibility
A. The CONTRACTOR shall be responsible for performing the appropriate
coordination with the airline representatives to ensure that all specific
airline peripheral requirements are met by the system. In addition, the
CONTRACTOR shall be responsible for performing the appropriate
coordination with the County and the project manager to ensure all
peripheral equipment (PCs, monitors, bag tag printers, boarding pass
printers, document printers, etc.) will be accommodated by the counter
casework and inserts that currently exist.
As a minimum, the
CONTRACTOR shall be required to perform shop drawing reviews and
provide component drawings detailing the exact mounting requirements
for each component and device to be supplied by the Contract
Documents.
3.6
COMMON USE SELF SERVICE - The Contractor shall comply with the
requirements set forth in this Section 3.6.
3.6.1 CUSS Kiosks
A. The CONTRACTOR shall provide a CUSS hardware and software system
that meets the functional requirements as established in IATA RP 1706.
B. The final configuration and architectural requirements of the CUSS kiosks
shall be coordinated with the County.
C. The assigned use (in-line) kiosks shall provide self-service check-in
services for the airline assigned to the associated ticket counter position.
The assigned use kiosks shall boot to the associated airlines system and
run the airline specific self-service check-in application. For airlines that
will use the LDCS for passenger processing, the CONTRACTOR shall
provide a CUSS application that is compatible with the LDCS. The
assigned use kiosk shall be assigned via the RMS and operate in the
assigned airlines native environment.
D. The general use kiosks shall be used for self-service check-in for any
supported airline. The general use kiosks shall include a common GUI
interface with each airlines name/logo shown. The traveler shall select the
airline for check-in via the touch screen. The selected airline‟s self-service
application shall be initiated by the selection. The traveler shall be able to
perform self-service check for the selected airline via the airline specific
self-service check-in application. The general use kiosks shall service the
supported airlines (refer to Airline Requirements) from the same kiosk
without rebooting. Once a traveler has completed self-service check-in
with a given airline, the kiosk shall return to the main airline selection
screen.
AIMS Attachment A: AIMS Statement of Work
Page 72 of 130
Exhibit 3
Page 133 of 278
E. The pricing breakout for the following components is included in the
Contract Documents.
1. Base CUSS system cost
2. Per airline software cost
3. Per kiosk cost
3.6.2 AIRLINE REQUIREMENTS
A. The airlines listed below shall be serviced by the CUSS. It is the
CONTRACTOR‟s responsibility to verify/determine airline interface
requirements and to determine peripheral interface requirements.
B. Cost for integrating each airline into the CUSS shall be listed as a line
item. Additionally, per airline cost shall be provided for adding additional
airlines to the CUSS.
C. Airlines to be serviced include, but are not limited to:
1. Air Canada
2. Air Jamaica
3. Air Sunshine (commuter)
4. Air Transat
5. Allegiant
6. AirTran
7. American
8. Avianca
9. Bahamas Air
10. CanJet
11. Caribbean
12. Chalks (commuter)
13. Comair
14. Continental
15. Continental Connection (Gulfstream)
16. Delta/Delta Connection
17. Frontier
18. JetBlue
19. Lynx Air International (commuter)
20. Northwest/KLM
21. Skyservice
22. Southwest
23. Spirit
24. Sunwing
25. US Airways
26. Westjet
27. Yellow Air Taxi (commuter)
AIMS Attachment A: AIMS Statement of Work
Page 73 of 130
Exhibit 3
Page 134 of 278
3.6.3 CUSS PERFORMANCE REQUIREMENTS
A. The time from when an airline is selected for self-service check-in and the
selected self-service check-in application is fully operational for use shall
not be more than ten (10) seconds. A “loading” or other similar screen
shall be displayed within 1.0 second after the airline is selected.
B. The CUSS shall meet all performance requirements set by the IATA
CUSS Manual and IATA RP 1706c.
3.6.4 CUSS HARDWARE REQUIREMENTS
A. The CUSS shall meet the hardware requirements in Section 3.9.
B. The CONTRACTOR shall be responsible for performing the appropriate
coordination with the airline representatives to ensure that all specific
airline peripheral requirements are met by the system.
C. The CONTRACTOR shall provide shop drawings and component
drawings detailing the exact mounting requirements for each component
and device(s) to be supplied by the Contract Documents.
D. Each CUSS kiosk shall be equipped with a Personal Computer (PC) and a
touch screen LCD Monitor (minimum 15” diagonal). All peripherals at the
location shall either be directly connected to the workstation (via USB,
parallel, or serial as appropriate) or to the system via the local area
network. Specific make and model is included in the Contract Documents.
E. The CUSS devices shall provide functionality equivalent to airline
proprietary installations. All peripheral devices shall be supplied with the
necessary interface cabling. Peripherals to be included in the CUSS will
include as a minimum
1. Receipt Type Printer (include ability to print 2D barcodes - PDF417)
2. Magnetic Stripe Reader (MSR)
3. Bag Tag Printer (BTP)
4. Optical Character Recognition (OCR) Reader.
5. Passport reader.
F. CUSS machines shall accommodate new hardware as upgradeable
features such as bar code scanners, RFID tag printers, and biometrics.
The CUSS kiosks shall accommodate swap-outs of subcomponents.
AIMS Attachment A: AIMS Statement of Work
Page 74 of 130
Exhibit 3
Page 135 of 278
3.7
LOCAL DEPARTURE CONTROL SYSTEM (LDCS) - The Contractor shall
comply with the requirements set forth in this Section 3.7.
3.7.1 System Overview
A. A Local Departure Control System (LDCS) provides automated check-in
and departure control for non-hosted airlines and irregular flight
operations.
The LDCS enables these airlines/flights to perform
computerized passenger check-in and boarding using a common
Graphical User Interface (GUI). The LDCS includes a locally-based
database that stores the passenger reservation information for each airline
and flight. At FLL, the database used shall be the Airport Operational
Database (AODB). Reservation information is entered into the AODB
database prior to the irregular flight operation or periodically depending on
the airline. The flight data is initially entered using download, data entry,
removable storage media, or other County agreed upon method. Once
flight data is entered into the AODB, the authorized airline agent can
check-in passengers, issue boarding passes, print bag tags, and scan
boarding passes using the LDCS software and GUI. The LDCS shall
utilize the DAPP common equipment including the DAPP workstation and
peripherals.
B. The LDCS shall maintain passenger status (e.g. boarded, not boarded) for
each departing flight and update it as passengers board. Other LDCS
functionality shall include the ability to generate, open, and close flights,
record number of bags and generate bag tags, and provide seat selection
and assignment.
C. The LDCS shall provide computerized passenger check-in and boarding
services for airlines that lack a host-based Carrier Reservation System
(CRS). The LDCS shall include a locally -based database that stores the
passenger reservation information for each participating airline and flight.
Each participating airline shall have the ability to load reservation
information (Passenger Name List – PNL data) into the LDCS database by
one of several methods (download, data entry, removable, storage media
or other County agreed upon method). Any data links to a CRS or other
PNL source is the responsibility of the CONTRACTOR. Agents shall be
able to check-in passengers and issue boarding passes and bag tags as if
using a host-based system. Agents shall use the common equipment
(DAPP workstations, etc.) to access the LDCS and perform check-in and
boarding processes.
D. The LDCS shall include an interface to the government “no fly” list and
provide the ability to cross reference PNL data to this list. If matches are
found, the system shall flag the passenger for further action by the airline
using the system.
AIMS Attachment A: AIMS Statement of Work
Page 75 of 130
Exhibit 3
Page 136 of 278
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
AIMS Attachment A: AIMS Statement of Work
Page 76 of 130
Exhibit 3
Page 137 of 278
10. Ability to handle charter and domestic flights
11. Issue (and cancel) bag tags, boarding passes, and itineraries on
demand using the common use peripherals
12. Provide ability for manual bag tag number recording
13. Provide split seating of groups
14. Ability to handle standby passengers
15. Manual, free, and charter seating logic
16. Seat selection and assigning
17. Storing of seat preferences
18. Provide aircraft operation information
19. Ability to support 30 flights opened at the same time
20. Resynchronization of LDCS data to host systems, where applicable.
L. The LDCS shall support the generation of IATA compliant Baggage
Service Messages (BSM) that may be sent to a baggage sortation system.
3.7.2 LDCS System Requirements
A. The LDCS shall meet the requirements defined in Section 3.10, System
and Software Requirements as a minimum.
3.7.3 LDCS Hardware Requirements
A. The LDCS shall meet the requirements defined in Section 3.9, Hardware
Requirements.
3.8
RESOURCE MANAGEMENT SYSTEM (RMS) - The Contractor shall
comply with the requirements set forth in this Section 3.8.
3.8.1 System Overview
A. A Resource Management System (RMS) shall be installed to support the
AIMS related resources within the FLL airport campus. The RMS installed
at the Airport shall be used to allocate and manage County controlled
resources including spots, gates, ticket counters, baggage makeup
conveyors, baggage breakdown carousels, and remote parking stands.
The RMS shall provide the tools to assist the County RMS operators in
allocation and management of County controlled resources with the least
impact to airlines, ground crews, passengers, and County personnel.
AIMS Attachment A: AIMS Statement of Work
Page 77 of 130
Exhibit 3
Page 138 of 278
B. The Resource Management System (RMS) shall include the following
software modules:
1. Spot/Gate Allocation and Real-time Management Module (Gate
Module)
2. Ticket Counter Allocation and Real-time Management Module (Ticket
Module)
3. Baggage Makeup Carousel Allocation and Real-time Management
Module (Bag Makeup Module)
4. Baggage Breakdown Carousel Allocation and Real-time Management
Module (Bag Breakdown Module).
C. Rule Base: The RMS shall include a rule base that allows definition of
Airport specific rules. The rule base shall be flexible enough to take into
account the many factors involved in assigning resources. The rule base
shall assist in both the planning of gates and in real-time conflict
resolution. The RMS shall provide user definable rule-definitions including
physical limitations (e.g., gate can‟t support wide body aircraft),
convenience rules (e.g., ground handling equipment location), and carrier
preferences or restrictions. The initial configuration of the rule-base shall
be performed by the supplying CONTRACTOR in direct coordination with
the Airport representatives. The rule-base shall provide a simple to use
rule-definition interface (no programming required) to facilitate long-term
maintenance of the rule-base by Airport without CONTRACTOR support.
The rule-base shall be coupled with an optimization routine. The
optimization routine shall include the necessary algorithms to properly
apply the rule-base to produce “best-fit” assignment(s).
D. Spot/Gate Module: The RMS Spot/Gate Module shall provide both a
planning mode and a real-time (day of operation) mode. The RMS shall
facilitate creation of seasonal schedules via a planning mode. The realtime mode shall assist Airport in managing changes due to various factors
including delayed flight, ground equipment failure, and weather delays.
E. Ticket Counter Module: The RMS Ticket Counter Module shall assist in
the assignment of airlines to ticket counters and in-line DAPP positions.
The system shall take into account flight departure schedules and aircraft
size to determine ticket counter demand per airline throughout the day,
however, the system shall allow assignments to be made and adjusted
independently of flight departure schedules.
F. Bag Claim Module: The RMS Bag Claim Module shall assist in the
assignment of airlines and flights to baggage claim carousels. The system
shall take into account flight arrival schedules and aircraft size to
determine baggage claim carousel demand throughout the day and
AIMS Attachment A: AIMS Statement of Work
Page 78 of 130
Exhibit 3
Page 139 of 278
provide BCAD with a recommended assignment schedule. The system
shall also include the optional ability to fully automate the assignments of
carousels. In this capacity bag claim carousel assignments shall be based
on load balancing of carousels. As a flight arrives at the loading bridge,
the bag claim carousel with the least demand shall be assigned. Other
requirements such as airline bag claim sharing restrictions or bag claim
out of service shall be accessed by the system when making bag claim
assignments.
G. Bag Makeup Module: The RMS Bag Makeup Module shall provide flight
to makeup module assignments. These assignments shall be based on
the defined rule set. Assignments will typically be made the day prior to
operation and passed to the Baggage Handling System (BHS) to ensure
proper bag routing. This data shall be passed automatically via a BHSAODB interface.
H. AODB: The AODB shall serve as the database for the RMS. The RMS
shall be fully integrated with the AODB. The AODB development shall
include defining control of shared fields between RMS, EVIDS, and other
applications.
3.8.2 Module Requirements
A. Spot/Gate Module: The RMS shall have a module for planning /
scheduling and real-time management of Gate allocation.
1. The Spot/Gate Module shall provide an integrated planning function
and real-time gate allocation function for aircraft spots, gates and offgate parking positions.
2. The module shall be able to manage a minimum of 53 gates and 15
off-gate parking positions.
3. The Spot/Gate Module shall optimize allocation of gates and off-gate
parking positions using the RMS software, defined rule-base for the
gates, and current flight information as a minimum.
4. The Spot/Gate Module shall aid in the planning of seasonal gate
assignments for a minimum of up to two (2) years in advance. The
gate planning shall occur off-line. The ability to save changes off-line
and to upload changes into the on-line database shall be provided.
5. The real-time portion of the Spot/Gate Module shall aid ground control
personnel in directing aircraft to their assigned gates and in
reassigning gates, as conditions require. The module shall respond to
changes in flight data by providing warnings and/or recommendations
of optimal solutions.
AIMS Attachment A: AIMS Statement of Work
Page 79 of 130
Exhibit 3
Page 140 of 278
B. Ticket Module: The RMS shall have an expandable module for planning /
scheduling and real-time management of Ticket Counter and Re-check
Counter allocation.
1. The Ticket Module shall provide an integrated planning function and
real-time allocation function for assignment of ticket counters (i.e.,
main ticket counters, recheck-in counters, etc.) to specific carriers.
2. The module shall be able to manage a minimum of 400 ticket counter
positions.
3. The Ticket Module shall aid in the planning of seasonal ticket counter
assignments for a minimum of up to two (2) years in advance. The
ticket planning shall occur off-line. The ability to save changes off-line
and to upload changes into the on-line database shall be provided.
4. The
Ticket
Module
planning
planning/scheduling off-line.
function
shall
allow
for
5. The real-time function shall actively respond to changes in flight data,
equipment
failures,
etc.
by
providing
warnings
and/or
recommendations to the operator.
C. Bag Makeup Module: The RMS shall include a module for planning /
scheduling and real-time management of Bag Makeup carousel allocation.
1. The Bag Makeup Module shall provide an integrated planning function
and real-time function for the assignment of flights to baggage makeup
carousels.
2. The module shall be able to manage a minimum of 40 makeup
carousels.
3. The Bag Makeup Module shall aid Baggage Handling System (BHS)
personnel in efficiently („optimally‟) allocating flights to baggage
makeup carousels to ensure balanced bag loads on each carousel.
4. The module shall be capable of both advanced planning and real-time
adjustments to compensate for changes in flight schedules, etc.
5. The Bag Makeup Module shall aid in the planning of seasonal bag
makeup carousel assignments for a minimum of up to two (2) years in
advance.
The planning shall occur off-line. The ability to save
changes off-line and to upload changes into the on-line database shall
be provided.
D. Bag Breakdown Module: The RMS shall have an expandable module for
planning / scheduling and fully automatic real-time management of Bag
Breakdown pier allocation.
AIMS Attachment A: AIMS Statement of Work
Page 80 of 130
Exhibit 3
Page 141 of 278
1. The Bag Breakdown Module shall provide an integrated planning
function and real-time function for the assignment of flights to baggage
breakdown piers.
2. The Bag Breakdown Module shall aid in the planning of seasonal bag
breakdown carousel assignments for a minimum of up to two (2) years
in advance.
The planning shall occur off-line. The ability to save
changes off-line and to upload changes into the on-line database shall
be provided.
3. The module shall be able to manage a minimum of 40 breakdown
piers.
4. The module shall be able to provide for advanced planning of
breakdown pier-to-flight assignments.
5. The module shall provide for adjustments to flight-to-pier assignments
in real-time. The module shall have the ability to run in fully automatic
in real-time optimizing flight-to-pier assignments without user
intervention.
6. The system shall provide a configurable cutoff point for changes to the
flight-to-claim assignment, when operating in fully automatic mode, so
that the displayed flight and baggage information shall remain
constant.
3.8.3 RMS Functionality
A. Changes to data in external systems (e.g., EVIDS) that impacts the RMS
shall be updated in the RMS in real-time.
B. Changes to data in the RMS that impacts external systems (e.g., EVIDS)
shall be updated to the external system(s) in real-time.
C. This data shall be passed via the AODB implemented by the
CONTRACTOR.
D. Planning / Scheduling: The RMS shall aid in short and long term planning
for all resources in order to prevent committing to over utilization of
resources, to schedule for maintenance and construction, and to evaluate
future variables (e.g., passenger demand, marketing requirements).
1. The software shall allow seasonal schedules to be loaded.
2. The software shall provide an off-line mode for planning.
3. The software shall allow the schedule created to be saved and then
retrieved later for further manipulations.
AIMS Attachment A: AIMS Statement of Work
Page 81 of 130
Exhibit 3
Page 142 of 278
4. The software shall support the ability to store and work with multiple
scheduling scenarios for all resources supported.
5. The ability to transfer the schedule from off-line to on-line shall be
provided.
E. Real-Time: The RMS shall aid Airport personnel in managing terminal
resources during day-to-day operations.
1. The software shall respond to changes in external data that affect the
allocation of terminal resources (e.g., flight arrival time updates in
EVIDS)
2. The software shall allow authorized users to directly input changes into
the RMS (e.g., loading bridge out of commission).
3. The software shall provide warnings/recommendations or automatically
adjust resource assignments based on the external system data
changes and authorized user input changes. The ability for the
software to provide a recommendation or automatically adjust
resources shall be a user configurable option.
4. Changes to resource assignments shall update to external systems via
the AODB.
5. A minimum of ten (10) users shall be able to view resource
assignments and concurrently modify allocations that are assigned to
their control. The Gantt chart shall provide an indication of which user
“owns” a resource.
F. Optimization Algorithms: The RMS shall utilize optimization algorithms.
The optimization routines shall meet the following minimum requirements:
1. Logically evaluate rules and provide “best fit” resource assignments.
2. Take into account rule weighting factors.
3. Account for all time-based information (e.g., flight arrival and
departure).
4. Analyze a minimum of five resolutions when a conflict occurs.
5. Optional: The system should utilize artificial intelligence (i.e., adapt its
problem solving algorithms as it encounters and „learns‟ from different
scenarios).
6. The RMS shall provide the ability to perform “what if” scenarios. For
example, a gate can be temporarily removed as an available gate, then
optimization routines can be run.
AIMS Attachment A: AIMS Statement of Work
Page 82 of 130
Exhibit 3
Page 143 of 278
G. Modes: The RMS shall provide the following modes of control for both
planning and real-time operations for all resources:
1. Manual Planning: All resource assignments are performed manually.
The system shall provide recommended resolutions at the user‟s
request. The system shall provide warnings if any rules are violated by
an assignment.
2. Manual Real-time:
All resource re-assignments are performed
manually. The system shall automatically detect conflict conditions
but only provide a warning. The system shall provide recommended
resolutions at the user‟s request. The system shall provide warnings if
any rules are violated by an assignment.
3. Semi-Automatic Planning:
The RMS shall generate step by step
recommended resource assignments with user confirmation required
prior to committing each assignment.
4. Semi-Automatic Real-time:
The RMS shall automatically detect
conflict conditions and provide recommended resolutions (in a
prioritized list) requiring user confirmation.
5. Automatic Planning: The automatic mode shall generate a complete
resource plan for a given schedule. The RMS shall automatically
identify and assign the “best fit” resource allocation based on the rule
base and schedule.
6. Automatic Real-time: The automatic mode shall automatically detect
resource conflicts and rule violations and automatically re-assign the
resource(s) as required. The system shall notify the user of any reassignments as they occur. The system shall have a configurable cut
off time for re-assigning any flight. The system shall allow manual
override of assignments by an authorized user. Additionally, any flight
or group of flights can be designated as‟ fixed‟ so that it cannot be reassigned in automatic mode.
3.8.4 Rule Base
A. Rule-base: The RMS shall have a rule-base defined for each of the
modules. The rule-base shall be an expert system as defined herein.
1. The rule-base shall logically define various physical limitations,
operational restraints, preferences, etc.
2. The RMS shall utilize the rule-base to optimize resource allocation
both for planning and in real-time.
3. Changes to operational conditions (e.g., flight delayed, equipment
breakdown) shall generate warnings of resource assignment conflicts,
recommendations of optimal solutions, or automatic resource reAIMS Attachment A: AIMS Statement of Work
Page 83 of 130
Exhibit 3
Page 144 of 278
assignment (depending on the mode of operation). The warnings,
recommendations, and/or re-assignments shall be based on the
defined rule-base and the RMS optimization algorithms.
4. The CONTRACTOR shall provide the knowledge engineering required
to set up the rule-base. The system shall allow authorized users to
change resource constraints and rule definitions.
B. The rule-base shall be an expert system thereby providing easy to define
rules as follows:
1. The rules shall be formatted with sentence-like structure.
2. No programming skills shall be required to define the rule-base.
C. Rules shall be definable for the following:
1. Physical restraints for a resource:
i
Resource limits (e.g., gate limitations - location of fuel pits, wide
body gate, narrow body gate, secondary lead-in lines, aircraft
adjacency, and pushback conflicts).
ii
Resource closed or out of commission.
2. Carrier considerations:
i
Preferred resource for a carrier.
ii
Carrier adjacency considerations (two carriers should/should not be
placed adjacent)
3. Ground crew considerations:
i
Location of ground handling equipment relative to resource.
ii
Location of baggage make-up carousels relative to gate.
4. Passenger convenience (e.g., gate location relative to another gate).
5. Financial considerations (e.g., tow-on/tow-off costs).
6. Off-gate parking location relative to a gate.
7. Flight types (e.g., freight, charter).
8. Resource preference based on various factors:
i
Flight arrival/departure time.
ii
Flight turn around time.
iii Origin/destination of flight.
iv A flight with multiple flight numbers.
AIMS Attachment A: AIMS Statement of Work
Page 84 of 130
Exhibit 3
Page 145 of 278
D. Hard and soft rules shall be definable. The ability to weight rules (e.g.,
importance of one through ten (1-10)) shall be provided.
E. The ability to logically combine rules shall be provided (e.g., AND, NOT,
OR, NOR, XOR). The ability to layer rules shall be provided (e.g., if, then,
else).
3.8.5 Knowledge Engineering
A. The CONTRACTOR shall carry-out all work required to develop and
implement the rule-base for the RMS. The initial knowledge engineering
shall be for a minimum of fifty-three (53) gates and fifteen (15) off gate
parking positions.
B. The CONTRACTOR shall provide, at a minimum, the following services
related to Knowledge Engineering:
1. Determine physical constraints of each resource.
2. Conduct personnel interviews as necessary and work closely with the
various Airport Divisions involved.
3. Develop logic.
4. Define rules in the RMS.
5. Document rule development process (shall have detail such that
another party could update the rule-base without duplicating effort or
consulting original RMS CONTRACTOR).
3.8.6 RMS System Requirements
A. The RMS shall meet the requirements of Section 3.10, System and
Software Requirements as a minimum. Additional system requirements
are provided in the Contract Documents.
B. The RMS shall have an interface to manage data and the individual
modules. The user interface shall provide a common look and feel for all
RMS modules. Via the user interface, authorized users have the ability to
select authorized module(s) to execute.
C. The RMS user interface shall include a color-coded Gantt chart listing
each resource (i.e., gate, ticket counter, baggage make-up carousel,
baggage breakdown pier) shall be used for each of the resource
management modules. Time shall be shown on the horizontal axis and
the resource shall be shown on the vertical axis.
AIMS Attachment A: AIMS Statement of Work
Page 85 of 130
Exhibit 3
Page 146 of 278
D. When modifications are performed to certain areas of data, the RMS shall
support the “re-building” of the affected areas only i.e., a complete
schedule re-build will not be required.
E. The planning mode of all modules shall support multiple planning
scenarios that can be individually saved. All saved scenarios shall have
the capability to be input into active mode.
F. Resource status shall be updated using text, color coding, and other
graphical coding (e.g., flashing). The color-code shall be user definable.
G. The Gantt chart shall be able to display contiguous resource allocations
for multiple days. The User shall be able to easily and dynamically adjust
the amount of time displayed from a minimum range of eight (8) hours to
four (4) calendar days.
H. Pan and zoom features shall be provided. The zoom shall allow
increasing/decreasing the number of resources and/or time frame
displayed up/down to the maximum and minimum time frame. Pan shall
allow the user to dynamically change the portion of the Gantt chart being
displayed.
I. The real-time Gate Module shall provide a graphical representation of an
aerial view of the Airport in addition to the Gantt chart view. On this
display gate status shall be updated using aircraft icons, color-coding, and
other graphical coding. The user shall be able to toggle between the
Gantt chart and aerial view when in real-time Gate Management mode.
J. The system shall provide standard templates for developing schedules
and planning. The ability to create user definable templates shall also be
provided
K. The user shall be able to assign resources to resource groups and easily
display one (1) or more resource groups dynamically as needed (for
example, DAPP stands may be one (1) group and remote stands another
group).
L. The system shall be able to display both allocated resources and
unassigned resources.
M. The RMS shall provide standard and custom reporting capabilities.
N. Various levels of access shall be definable and controlled based on user
login. The following levels of access shall be provided at a minimum:
1. View: User shall only be able to view planning and real-time
information. The user shall not be able to make any changes.
AIMS Attachment A: AIMS Statement of Work
Page 86 of 130
Exhibit 3
Page 147 of 278
2. Planning: User shall only be able to make changes in the resource
planning mode.
3. Real-time: User shall only be able to make changes in the real-time
mode.
4. Full: User shall be able to make changes in the planning and real-time
mode.
5. The system shall have the ability to limit a user‟s access to a specified
set of resources (e.g., gates 1-4, 9 and 10, Airlines A and C, etc.).
O. RMS Performance Requirements
1. In addition to the performance requirements identified in Section 3.10,
the following is required:
i
Response Time: The CONTRACTOR shall state the maximum and
minimum time required for a full optimization routine to run and
schedule twenty-four (24) hours for fifty-three (53) gates and four
hundred (400) flight operations (departures and arrivals). Any
assumptions shall be noted (e.g., number of rules evaluated). The
following criteria for system response shall be met:
a The maximum time for any optimization routine to run from the
initiation of the request by the user to the screen update shall
not exceed five (5.0) minutes.
b The maximum time for the system to respond to a change in
flight data in the AODB shall not exceed one (1.0) minute.
P. Interface/Integration Requirements:
1. The RMS shall integrate with the AODB, EVIDS, DAPP, and LAN
systems as necessary to provide the following functionality:
i
Control resource assignments and initiate resource changes
affecting LAN and DAPP. RMS assignments shall result in the LAN
and DAPP assigning the required virtual network to the specific
network port to allow communications only by the assigned airline
at the assigned gate.
ii
Activate specific gate, ticket counter, and passenger loading bridge
equipment (including workstation and other peripherals, and VoIP
telephone handset) upon assignment of the affiliated resource
position. This functionality shall also require the VoIP telephone set
to be provisioned to the appropriate defined class of service for the
particular tenant. The County is utilizing a Nortel PBX/VoIP hybrid
solution to provide telephony service throughout the FLL campus.
The CONTRACTOR shall provide all necessary integration with this
system to provide the described functionality.
AIMS Attachment A: AIMS Statement of Work
Page 87 of 130
Exhibit 3
Page 148 of 278
iii Other specific requirements shall be defined by CONTRACTOR
during the development of the Interface Design Documents.
2. The RMS shall accommodate the various schedule input
methodologies of the airlines present at FLL. Individual airline
schedule interfaces to the RMS shall be defined and documented in
Interface Definition Documents.
3.8.7 RMS Hardware Requirements
A. The RMS shall meet the requirements defined in Section 3.9, Hardware
Requirements.
B. The CONTRACTOR shall provide ten (10) workstations. The location of
these devices shall be coordinated with the County.
3.8.8 Expansion
A. The system shall be designed such that adding a workstation, gate,
carousel, conveyor, counter, or airline shall not have a negative impact on
the RMS. For example, adding an airline to the RMS shall have no impact
on the overall system design. The system shall be able to expand to
include:
1. 100 gates
2. 800 ticket counters
3. 100 baggage breakdown / makeup conveyors.
B. At the time of Final System Acceptance, all hardware shall have a
minimum of fifty percent (50%) reserve capacity, with the capability to
double the capacity with no change in design. Hard disk, CD-ROMs, and
tape units capacities shall be based on formatted capacity. System
reserve capacity shall be based on the maximum continual working load.
3.9
HARDWARE REQUIREMENTS - The Contractor shall comply with the
requirements set forth in this Section 3.9.
3.9.1 General Requirements
A. The AIMS, as defined in this document, shall include all configured
hardware necessary for a fully functional system. The CONTRACTOR
shall supply all cabling, connectors, adapters, and termination equipment
necessary to interconnect all system hardware. All hardware and
materials shall be new.
B. Hardware requirements given are the minimum requirements. The
CONTRACTOR's product shall meet or exceed these requirements. The
AIMS Attachment A: AIMS Statement of Work
Page 88 of 130
Exhibit 3
Page 149 of 278
hardware selected shall meet the operational, functional, and performance
requirements specified herein.
C. Refer to drawings for hardware quantities to be provided.
D. The CONTRACTOR may propose a substitution for specific hardware
requirements for approval from the County. Requests for hardware
substitution shall be submitted in writing and include the hardware cut
sheet, the exact configuration being proposed, and a comparison of the
proposed equipment versus the specified equipment.
E. The CONTRACTOR is responsible for providing fans, shelves, drawers,
special power wiring, ground connections, cables, connectors,
appurtenances, and adapters of any kind necessary to accommodate the
system installation, operation, testing, and maintenance.
3.9.2 Contemporary Technical and Operational Equivalent
A. Due to the rapid advancement and antiquation of hardware technology,
the supplied hardware shall be the “contemporary technical and
operational equivalent” of the specified hardware.
The following
requirements shall be met:
1. Contemporary technical and operational equivalent shall be based on
a comparison of technology at the time of Contract to the technology at
the time of ordering the equipment for each phase.
2. Hardware shall be ordered as close to the actual installation date for a
given phase as reasonable (i.e., latest responsible date). Final
hardware approval and scheduled order date are at the sole discretion
of the County.
3. Hardware equivalence shall be based on both technical equivalence
and operational equivalence.
4. Contemporary technical equivalence shall be based on device
performance and class specifications. For example, if a 1.4 GHz Intel
Pentium 4 processor was specified in January of 2001, then the
contemporary technical equivalent in September of 2004 would be a
3.40 GHz Intel Pentium 4 processor.
5. Contemporary operational equivalence shall be based on industry
standards and function. For example, if a 48x EIDE CD-RW drive was
specified in January 2001, then the contemporary technical equivalent
in September of 2004 would be a 16X DVD+RW/+R drive.
AIMS Attachment A: AIMS Statement of Work
Page 89 of 130
Exhibit 3
Page 150 of 278
3.9.3 Supporting Infrastructure
A. Passive Infrastructure: Provide final equipment connection to network.
Provide the necessary patch cables, equipment cables, and work area
cables. It is the CONTRACTOR‟s responsibility to fully review the passive
infrastructure components not provided by this project and identify in
writing where the infrastructure does not meet the CONTRACTOR‟s
requirements.
B. Hardware Structures: The CONTRACTOR is responsible for providing all
hardware and case work required for final installation. The
CONTRACTOR shall be responsible for performing the appropriate
coordination with the County, and other construction package coordinators
to ensure all AIMS equipment (display devices, workstations, gate and
ticket counter equipment, etc.) will be accommodated by casework. The
CONTRACTOR will be required to create and submit shop drawing
component drawings detailing the exact mounting requirements for each
component and device to be supplied by the Contract Documents as well
as the detail information for the casework that is to be installed to support
the AIMS devices.
C. Equipment racks: The CONTRACTOR shall be responsible for supply and
installation of any additional equipment racks that may be required for
equipment installation with the telecommunication rooms. The
CONTRACTOR shall coordinate with the County‟s Project Manager to
determine installation location for all equipment that is to be placed with
the telecommunication rooms.
1. Equipment located in the telecommunication rooms shall be rack
mounted in standard 19-inch racks within a cabinet enclosure.
2. The CONTRACTOR shall provide the appropriate factory or custom
rack mount adapters for all equipment installed in the equipment rack,
whether specifically itemized or not.
3. The CONTRACTOR shall cover unused slots using blank panels.
3.9.4 Environmental Rating
A. Equipment shall be rated for continuous operation under the ambient
environmental temperature, humidity, and vibration conditions
encountered at the installed location. For devices located in harsh
environments such as interior uncontrolled or exterior environments, the
CONTRACTOR shall provide the necessary industrialization or enclosures
to ensure proper equipment operation and performance.
B. The equipment shall meet the following requirements based on installation
location:
AIMS Attachment A: AIMS Statement of Work
Page 90 of 130
Exhibit 3
Page 151 of 278
1. Interior controlled environment: 60°F to 100°F dry bulb and 20 to 90
percent relative humidity, non-condensing. Communication rooms
shall be considered this type of environment.
2. Interior, uncontrolled environment: 0°F to 130°F dry bulb and 10 to 95
percent relative humidity, non-condensing. Baggage make-up and
breakdown areas shall be considered this type of environment
3. Exterior environments: 0°F degrees to 130°F dry bulb and 10 to 100
percent relative humidity, condensing.
3.9.5 HEAD-END DEVICES
A. Minimum Server Requirements
1. The CONTRACTOR shall recommend and provide the server
configuration that best serves the CONTRACTOR‟s overall design
solution. Servers shall be from a reputable manufacturer capable of a
high level of maintenance and service. The various server
requirements stated herein are not intended to limit the AIMS. The
CONTRACTOR may submit alternative solutions to any of the server
configuration requirements. A brief explanation of equivalency or
benefits shall accompany alternative solutions.
2. The servers shall be fault tolerant via clustering, mirroring or other
vendor technology. The implemented configuration shall allow a
server to be powered down and replaced without disruption to the
network or applications. Server failover shall occur if the primary
server fails for any number of reasons including: power failure,
hardware failure, software failure, and network connection failure.
Multiple load sharing application servers or other configurations shall
be considered viable alternatives to redundant application server pairs
if equivalent or improved system redundancy and resiliency can be
demonstrated. The system shall support the ability to locate all servers
in separate locations to provide physical redundancy.
3. Servers shall be standard 19-inch rack mountable.
4. Servers shall be capable of upgrading the number of processor units
by simply adding another processor or processor card.
5. Servers shall be “dual-homed” to the LAN core switches via server
grade Gigabit Ethernet NICs. Final requirements and configuration
shall be coordinated with the County.
6. Disk Storage: Total useable disk capacity shall be at least 4 times the
estimated storage requirements of the application and operating
system. RAID shall be implemented as best suits the application.
Internal RAID 5 shall be provided unless justification for alternative
AIMS Attachment A: AIMS Statement of Work
Page 91 of 130
Exhibit 3
Page 152 of 278
configuration is provided. RAID shall not be implemented via the
operating system, but by a hardware controller. Disk arrays shall have
open frames to allow the capacity to be doubled by addition of RAID
drives without system shutdown. At least one drive per array should be
in hot standby with automatic failover controlled by the RAID controller.
7. Monitor:
Shared rack-mounted monitor per rack (provide rackmounted input switching device). The monitor provided shall meet the
requirements provided under the section titled AIMS Monitors.
8. Servers shall be configured to meet or exceed the minimum hardware
requirements detailed below and also meet or exceed the
performance, operational, and functional requirements of this
Specification.
B. File Server Requirements
1. Two (2) 2.8 GHz processors (latest version) with 1MB cache.
Architecture should be Intel or RISC as required by the operating
system.
2. 1 GB DDR2 400 MHz RAM. Sufficient memory shall be provided to
meet the maximum transaction load and ensure the memory is never a
restriction on system performance
3. Minimum 72 GB useable internal hardware RAID 5 disk storage
(10,000 rpm)
4. Two (2) NICs (server-class card) for LAN connection (coordinate
network requirements with network administrator)
5. Minimum 72 GB internal Tape Backup Unit with SCSI card and back
up software
6. 24X IDE CD-RW/DVD ROM drive
7. Remote Access Card
8. Multiple hot-pluggable redundant power supplies
9. Standard windows keyboard and USB 2-button wheel mouse
10. Minimum of two (2) USB 2.0 ports
C. Application Server Requirements
1. Two (2) 3.2 GHz processors (latest version) with 1MB cache.
Architecture should be Intel or RISC as required by the operating
system.
AIMS Attachment A: AIMS Statement of Work
Page 92 of 130
Exhibit 3
Page 153 of 278
2. 4 GB DDR2 400 MHz RAM. Sufficient memory shall be provided to
meet the maximum transaction load and ensure the memory is never a
restriction on system performance
3. Minimum 36 GB useable internal hardware RAID 5 disk storage
(10,000 rpm)
4. Two (2) NICs (server-class card) for LAN connection (coordinate
network requirements with network administrator)
5. Minimum 36 GB internal Tape Backup Unit with SCSI card and back
up software
6. 24X IDE CD-RW/DVD ROM drive
7. Remote Access Card
8. Multiple hot-pluggable redundant power supplies
9. Standard windows keyboard and USB 2-button wheel mouse
10. Minimum of two (2) USB 2.0 ports
D. Database Server Requirements
1. Four (4) 2.7 GHz processors (latest version) with 2 MB cache.
Architecture should be Intel or RISC as required by the operating
system.
2. 8 GB DDR Mirroring. Sufficient memory shall be provided to meet the
maximum transaction load and ensure the memory is never a
restriction on system performance
3. Minimum 144 GB useable internal hardware RAID 5 disk storage
(10,000 rpm)
4. Two (2) Host Bus Adapters for redundant data storage system
interface (refer to data storage system requirements for further details)
5. Two (2) NICs (server-class card) for LAN connection (coordinate
network requirements with network administrator)
6. Minimum 144 GB internal Tape Backup Unit with SCSI card and backup software
7. 24X IDE CD-RW/DVD ROM drive
8. Remote Access Card
9. Minimum of two (2) USB ports
10. Multiple hot-pluggable redundant power supplies
AIMS Attachment A: AIMS Statement of Work
Page 93 of 130
Exhibit 3
Page 154 of 278
11. Standard windows keyboard and USB 2-button wheel mouse
E. Data Storage System
1. Network Attached Storage (NAS) shall be provided to accommodate
data archival.
2. The NAS shall meeting the following minimum requirements:
i
3 GHz processor
ii
Configured as a RAID Level 5 array
iii Minimum of 1 TB of useable disk space and expandable to 3 TB of
useable disk space
iv ATA IDE hard drives
v
Dual-homed to LAN via 10/100/1000 Gigabit Ethernet NICs
3. The NAS shall utilize Veritas Enterprise (latest version) archiving
software and the CONTRACTOR shall provide the necessary licenses
4. The NAS shall include a tape back up that meets the following
requirements:
i
SDLT 320 tape technology
ii
Minimum storage capacity shall be 1 TB uncompressed and
expandable to 3 TB storage capacity uncompressed
iii Backup rate of 120GB/hr uncompressed
F. Uninterruptible Power Supplies
1. All server and local area network equipment installed in
telecommunication rooms shall be UPS backed to prevent
unnecessary service interruptions. The CONTRACTOR shall be
responsible for coordinating with the County to ensure that existing
UPS capacity will support the additional load of the new equipment. In
any case where new hardware is installed in a location where the
capacity of the existing UPS is exceeded, it shall be the responsibility
of the CONTRACTOR to supplement or replace the UPS in such a
fashion that the UPS is capable of supporting required load for the
minimum period of time.
2. The UPS equipment shall have batteries that are capable of being
replaced in the field.
3. The UPS interface port shall have a 10 Base-T Ethernet for LAN
management.
4. Each UPS shall provide a minimum of 30 minutes standby power at full
load.
AIMS Attachment A: AIMS Statement of Work
Page 94 of 130
Exhibit 3
Page 155 of 278
5. The UPS shall be rack mountable in a standard 19 inch equipment
rack/cabinet.
6. The control panel shall have a LED status display for load and battery
bar-graphs in addition to replace battery and overload indicators.
7. Each UPS shall include software and interface card to provide
Web/SNMP management through 10Base-T Ethernet port.
Management software shall include the following attributes:
i
Shall allow complete configuration of the UPS devices from a
remote location
ii
Shall provide periodic UPS self-tests
iii Shall provide full control over UPS transfer settings
iv Shall provide user name and password security
v
Shall log all power events with a description
8. Standard UPS warranty of two years shall be provided.
CONTRACTOR shall submit recommended standard and optional
warranty and maintenance plan per the Contract Documents.
3.9.6 System PC’s
A. Performance Workstation
1. 3.6 GHz Pentium 4 processor with hyper threading technology
2. 4 GB DDR2 SDRAM
3. 160 GB ATA Hard Drive (7200 rpm)
4. 10/100/1000 Mbps Ethernet card
5. 128 MB PCI Video card
6. 48x CD-RW drive plus 16x DVD+RW/+R drive
7. 2 serial ports, 1 parallel port, and 4 2.0 USB 2.0 ports
8. Standard windows keyboard and USB 2-button wheel mouse
9. 21-in LCD monitor (refer to monitor requirements)
B. Standard Workstation
1. 3.2 GHz Pentium 4 processor with 1 MB cache
2. 1 GB RDRAM
3. 80 GB ATA Hard Drive (7200 rpm)
AIMS Attachment A: AIMS Statement of Work
Page 95 of 130
Exhibit 3
Page 156 of 278
4. 10/100 Mbps Ethernet card (auto-negotiating)
5. 64 MB PCI Video card
6. 48x CD-ROM
7. 2 serial ports, 1 parallel port, and 4 USB 2.0 ports
8. Standard windows keyboard and USB 2-button wheel mouse
9. 17-in LCD monitor (refer to monitor requirements)
C. Display Device Controllers
1. Device Display Controller (DDC): The Device Display Controller
(DDC) shall be used by the EVIDS to control the display output of
video monitors. Each DDC shall have a unique TCP/IP address and
shall communicate via the EVIDS Virtual Local Area Network (VLAN).
Currently County is using the Wyse V90 LE.
i
1.2 GHz VIA C7 Eden
ii
1 GB DDR RAM
iii 1 GB Flash Memory
iv 10/100 Mbps Ethernet card (auto-negotiating)
v
Dual Display, Embeded Video
vi 1 serial RS232 port, 1 parallel port, and 3 USB 2.0 ports
vii Standard windows keyboard and USB 2-button wheel mouse
3.9.7 Integrated system devices
A. CUSS Kiosk
1. The CUSS Kiosks shall be full function kiosk with a modular design for
improved scalability. It shall provide ease of use. A lockable panel
shall be provided for easy authorized access to internal components
for maintenance. The kiosks shall conform to the following, as a
minimum:
i
Compliance with IATA/ATA
ii
Compliance with ADA
iii Stand-alone version
iv 17-in touch screen, card reader, and ticket printer
v
Powered by a PC meeting the requirements of a performance
workstation
vi Baggage tag printer
AIMS Attachment A: AIMS Statement of Work
Page 96 of 130
Exhibit 3
Page 157 of 278
vii Thermal 1D/2D barcode printer
viii Card reader (credit card or frequent flyer card)
ix Passport reader
x
Optional 1D/2D barcode reader
xi Compatible with IEEE 802.11 wireless communications
xii Ability to provide customization with County specific signage and
markings (to be coordinated with the County)
xiii Include a leaflet holder (May be included as part of millwork)
xiv Be supported by CUSS middleware
xv Include CUSS remote monitoring software to manage both the
hardware and the CUSS applications of the kiosk
3.9.8 Gate Input Workstation (GIW)
A. The gate input workstations will be used to interact with the EVIDS
including visual paging and to update and view EVIDS data. All GIW
workstations shall include a 15” flat touch-screen.
B. The GIW workstations shall be used in the following locations:
1. Gate Counters
2. Passenger Loading Bridge (PLB) area
3. Ticket Counters
C. Hardware requirements for the GIW workstations shall meet the minimum
requirements of the “Standard Workstation” defined under System PCs.
3.9.9 Airport Communications Center Workstations
A. Ten (10) positions located in the Communications Center and other areas
throughout the Airport shall incorporate a flat-screen workstation for
interaction / administration of the RMS. These workstations with flatscreen shall adhere to the following requirements, at a minimum.
B. Quantity: Ten (10)
C. Location: Communications Center and other areas to be determined
D. Flat-screen component shall meet the following requirements:
1. 20-inch viewable TFT LCD flat-screen
2. Color-range of 16.7 million colors (8-bit color depth).
AIMS Attachment A: AIMS Statement of Work
Page 97 of 130
Exhibit 3
Page 158 of 278
3. Graphics and text shall be displayed at up to 1024 x 768 pixels.
4. Workstation components shall meet the minimum requirements of the
“Standard Workstation” defined under System PCs.
3.9.10 Workstation Monitors
A. 17-in flat screen monitor shall meet the following minimum requirements:
1. 1280 x 1024 @ 75 Hz refresh rate
2. Pixel Pitch 0.264mm (H) × 0.264mm (V)
3. 4:3 aspect ratio
4. 17-in viewable area
5. Viewing angle of 140 degrees
6. Contrast ratio of 400:1
7. Brightness of 250 candelas/meter2
B. 20-in LCD monitor shall meet the requirements of 20-in LCD displays
under LCD displays.
3.9.11 LCD Information Displays
A. 20-in LCD: 20-in LCD monitor shall meet the following minimum
requirements:
1. 1600 x 1200 native resolution
2. 0.255 mm pixel pitch
3. 16:9 aspect ratio
4. Response time 16 ms
5. Viewing angle minimum 170 degrees
6. Contrast ratio of 400:1
7. Brightness of 250 candelas/meter2
8. NEC Model LCD2070NX-BK
B. 32-in LCD: 32-in LCD monitor shall meet the following minimum
requirements:
1. 1366 x 768
2. 0.511 mm pixel pitch
AIMS Attachment A: AIMS Statement of Work
Page 98 of 130
Exhibit 3
Page 159 of 278
3. 16:9 aspect ratio
4. Viewing angle of 176 degrees
5. Contrast ratio of 600:1
6. Response time 18 ms
7. Brightness of 500 candelas/meter2
8. NEC Model LCD3210-BK
C. 40-in LCD: 40-in LCD monitor shall meet the following minimum
requirements:
1. 1366 x 768
2. 0.641 mm pixel pitch
3. 16:9 aspect ratio
4. Viewing angle of 176 degrees
5. Contrast ratio of 1000:1
6. Brightness of 450 candelas/meter2
7. NEC Model LCD4010-BK
D. 46-in LCD: 46-in LCD monitor shall meet the following minimum
requirements:
1. 1366 x 768
2. 0.746 mm dot pitch
3. Viewing angle of 178 degrees
4. Contrast ratio of 1000:1
5. Brightness of 450 candelas/meter2
6. NEC Model LCD4610-BK
3.9.12 LED Information Displays
A. LED Pixel Type:
1. The LED display shall contain a tri-colored full LED matrix.
2. The matrix shall display messages that are continuous, uniform and
unbroken in appearance to the intended viewing audience.
AIMS Attachment A: AIMS Statement of Work
Page 99 of 130
Exhibit 3
Page 160 of 278
3. The matrix panel shall consist of three-color options: Red, Green, and
Amber (Yellow).
4. The Amber (Yellow) color shall be achieved by turning on the Red and
Green LEDs in sequence.
5. The matrix panel background shall be black.
6. Each display pixel shall be comprise of Red (660 nm dominate
wavelength) and Green (565 nm dominate wavelength) LEDs within a
single chip.
7. LED pixel size shall maintain a consistent diameter of 0.2 inches or
0.05 centimeters
8. LED pixel spacing is required to maintain a minimum center-to-center
spacing of 0.3 inches (0.8 centimeters) for 2.1-inch character height.
9. The LEDs shall maintain intensity greater than 80% for a minimum of
three years.
10. All LED chips shall have a minimum of 120-degree (180 degree
preferred) horizontal (x-axis) viewing angle in low ambient light
conditions and/or 35 degrees in sunlight conditions.
11. Pixels shall be constructed with chip-type (surface mount) LEDs. Chiptype (surface mount) LEDs shall conform to the following
specifications:
i
LEDs shall be high-bright, 70 mcd minimum, solid-state light
emitting diodes for in-door applications.
ii
LED use in direct sunlight conditions requires ultra-bright, 300 mcd
minimum, and solid-state light emitting diodes for in-door
applications.
iii LEDs of the same color shall be from the same manufacturer and
of the same part number.
iv Maximum LED wavelength variance shall be +/- 2 nanometers
(nm).
v
LED half-life shall be a minimum of 100,000 hours of continuous
use.
vi Letter of certification from the LED manufacturer is required for
proper testing and binning according to International Commission
on Illumination (CIE 127 (1997) standards).
B. LED Module:
1. The failure of a single pixel shall not cause the failure of any other pixel
in the display.
AIMS Attachment A: AIMS Statement of Work
Page 100 of 130
Exhibit 3
Page 161 of 278
C. LED Display:
1. LED Dot Matrix/Pixel Array
i
The pixel matrix shall be capable of displaying alphanumeric
character fonts and shall be two lines with twenty-four characters
on each line.
ii
The character set shall support an International character set. This
set shall include block (sans serif), decorative (serif), upper/lower
case, slim, wide, and doublewide characters.
iii The sign shall be able to display messages composed of any
combination of alphanumeric text, punctuation symbols, and
graphic images.
D. Housing Characteristics:
1. The LED display housing shall be constructed of new high quality
material that resists corrosion, degradation, and oxidation despite
scratches to the housing.
2. The housing design shall be weather-tight and shall include protection
from vandalism.
3. All housing materials must be pre-approved by a licensed Engineer
before acceptance.
4. The display housing shall provide safe and convenient front service
access for all modular assemblies, components, wiring and other
materials located within the housing.
5. Service access shall be easily obtained by removing individual LED
modules. Internal components shall be accessed by removing the
associated modules.
6. Housing Frame:
i
Extruded Aluminum
7. Mounting Options:
i
Brackets
ii
Hardware to accommodate ceiling and wall mounting methods, per
manufacturing specifications.
8. Lens Panel:
i
The lens panel of LED display shall be covered with an impact
resistant polycarbonate (PC), non-glare, LEXAN material or
approved equal.
AIMS Attachment A: AIMS Statement of Work
Page 101 of 130
Exhibit 3
Page 162 of 278
ii
The LED display must be readable in all ambient light conditions
including direct sunlight.
iii Lens surface material must contain a 90% ultraviolet (UV) inhibitors
clear glazing to protect from fading and/or yellowing to lens panel.
iv All lens materials must be pre-approved by a licensed Engineer
before acceptance.
E. Maintenance Access Door
1. The display housing shall provide safe and convenient front service
access for all modular assemblies, components, wiring and other
materials located within the housing.
2. Front service access panel must be able to stay opened, in a locked
position, for servicing.
3. Service access shall be easily obtained by removing individual LED
modules.
4. Removing the associated modules shall access internal components.
F. Controller:
1. The primary face of the display shall have its own controller, which can
be individually addressed by its hardware and shall be able to run
independently from the controlling computer allowing displays to
operate even when computer or software is turned off.
2. Communication to the LED display(s) shall be via the LAN (TCP/IP).
The LED devices shall include all required Network Interface Cards
(NIC) and appurtenances to support this communication.
3. Any new controllers shall be fully compatible with the existing LED
devices.
G. Electrical:
1. The LED modules shall be powered with regulated switching DC power
supplies.
2. Power supplies shall protect the LED pixel matrix and driver circuitry in
the event of power spikes and surges.
3. Wiring for the LED display modules and other internal components
shall be installed in the housing in a neat and professional manner.
Wiring shall not impede the removal of display modules, power
supplies or other sign components. Wires shall not make contact with
or be bent around sharp metal edges. All wiring shall conform to the
National Electric Code (NEC).
AIMS Attachment A: AIMS Statement of Work
Page 102 of 130
Exhibit 3
Page 163 of 278
4. All high voltage electrical components used within the display shall be
UL listed.
5. Power Supply:
i
The display power supplies shall operate from a 120 VAC, 60Hz
single-phase power source, including neutral and earth grounding.
6. Safety:
i
Thermal-magnetic circuit breaker must be installed at display
housing for additional protection.
ii
No exposed wiring is permitted outside of display.
H. Testing
1. Letter of certification from the LED manufacturer is required for proper
testing and binning according to International Commission on
Illumination (CIE 127 (1997) standards).
3.9.13 Peripherals
A. Baggage Input Console
1. Baggage Input Consoles (BIC): There will be Baggage Input Consoles
located throughout the baggage breakdown area for use by the
baggage handlers. The BICS shall have the following minimum
attributes:
i
The BIC shall be a workstation with an integrated touch-screen with
the following minimum requirements:
a Pentium III 500 MHz.
b 256 MB DRAM.
c
Internal 10 GB hard drive.
d Integrated, bus-mastering Fast Ethernet (10 / 100 Mbps)
controller.
e 8 MB video adapter.
f
15” LCD TFT resistive touch-screen capable of 1024x768
resolution.
g Rugged, spill resistant ABS housing suitable for harsh, high-use
environments such as the baggage make-up levels of the
Airport.
ii
The CONTRACTOR shall provide materials to mount and attach
the BICs in the required area of intended operation.
The
CONTRACTOR shall coordinate exact BIC mounting locations with
the County.
AIMS Attachment A: AIMS Statement of Work
Page 103 of 130
Exhibit 3
Page 164 of 278
B. 2D Ticket Printer
1. A receipt style printer shall be provided that is able to print 2D
(PDF417) barcodes. The barcodes shall include machine-readable
boarding pass data formatted to support single segment, multisegment, and interline data encoding.
2. Interface: USB
3. The CONTRACTOR is required to determine additional 2D printer
requirements in coordination with tenant requirements.
C. Bag Tag Printer (BTP)
1. Provide IER 512 or County approved equivalent substitution for the
BTP
2. Interface: Ethernet LAN (TCP/IP)
3. The printers shall be set up for direct thermal printing only.
printers shall not include a cutter or burster.
The
4. The BTP shall conform to the IATA resolutions relating to ATB‟s and
shall be compatible with the AEA specification for PECTAB's. All
required firmware shall be provided and installed.
5. The CONTRACTOR is required to determine additional bag tag printer
requirements in coordination with tenant requirements.
D. Magnetic Strip Reader (MSR) / Optical Character Recognition (OCR)
1. Desko BMOL 4000 with integrated OCR, MSR or County approved
equivalent substitution. Option pricing shall be provided for the AiT
PAX Reader.
2. The MSR at a minimum shall be a 4-Track uni-directional MSR. The
MSR shall be capable of reading IATA standard encoded magnetic
strips and ISO 7811. The device shall be cable of reading ATB1 and
ATB2 Tickets, frequent flyer cards, and credit cards.
3. The OCR shall be capable of reading passports and other standard
travel documents.
4. Per unit option pricing shall be provided for a bar code scanner, smart
card reader, photo ID scanner, and fingerprint sensor along with the
required drivers.
5. The CONTRACTOR is required to determine additional MSR/OCR
requirements in coordination with tenant requirements.
E. Boarding Gate Reader (BGR)
AIMS Attachment A: AIMS Statement of Work
Page 104 of 130
Exhibit 3
Page 165 of 278
1. The supplied BGR shall read 2D bar code printed boarding documents
and shall support the various functional requirements of all airlines
supported by the AIMS.
2. All required firmware shall be provided and installed.
3. The CONTRACTOR is required to determine additional boarding gate
reader requirements in coordination with tenant requirements.
F. DAPP Standard Printer (DOC)
1. LaserJet printer with the following minimum specifications:
i
Print speed up to 25 pages per minute (ppm)
ii
Utilize laser print technology
iii 1200 x 1200 dpi resolution
iv Two (2) paper trays
v
Support 8.5 x 11 and 8.5 x 14 inch paper
vi Minimum memory 64 MB
vii IP addressable
2. The CONTRACTOR is required to determine additional document
printer requirements in coordination with tenant requirements.
G. General Document Printer
1. Provide two (2) general document printers. The location of the printers
shall be coordinated with the County.
2. The specifications shall be that of the DAPP Standard Printer.
3.9.14 Local Area Network Equipment
A. Access Layer Network Switch
1. Minimum 24 Port Standard Multi-Layer Software Image (SMI) switch,
must include a minimum 10% spare ports
2. Support Power Over Ethernet (PoE)
3. Include two (2) Gigabit Small Form Factor Pluggable (SFP) ports
4. Include two SFP Gigabit LX (long haul, single mode/multi mode fiber)
modules
5. Provide appropriate GBIC or SFP modules for connection to the core
network switch
6. 110V power
AIMS Attachment A: AIMS Statement of Work
Page 105 of 130
Exhibit 3
Page 166 of 278
7. Include annual maintenance agreement
8. Cisco 3560 series device
3.10
SYSTEM AND SOFTWARE REQUIREMENTS
- The Contractor shall
comply with the requirements set forth in this Section 3.10.
3.10.1 General Requirements
A. The requirements throughout this section apply to each of the AIMS, as
defined in the Contract Documents, unless specifically noted otherwise. Each
individual system and application provided now or in the future shall meet
these standards as a minimum.
B. The AIMS shall facilitate integration of other applications.
C. The AIMS shall facilitate the implementation of any federally mandated
applications.
3.10.2 Software
A. Software provided shall be at least 32-bit based applications. Software shall
be built around a compliant operating system as defined in the Contract
Documents.
B. The CONTRACTOR shall deliver all required system and application software
for a fully functioning Integrated AIMS. Each shall be identified by the
generic, off-the-shelf name. The software provided by the CONTRACTOR to
operate the AIMS shall be delivered in a ready-to-run form, including all
necessary utility programs and documentation.
C. The software shall be fully date compliant.
D. The systems shall use industry standard components. The systems shall not
contain any proprietary interfaces or components. The system shall use
industry standard application development software such as Java, JavaScript,
Perl, Visual Basic, C/C++ and XML. County approval shall be required for
use of alternative application development software.
E. All new inter-relationships between the applications, databases, and
operating system shall be the responsibility of the CONTRACTOR.
3.10.3 User Interface
A. The AIMS shall have an interface to manage data and the individual
applications. The user interface shall provide a common look and feel for
each Integrated AIMS Component application.
AIMS Attachment A: AIMS Statement of Work
Page 106 of 130
Exhibit 3
Page 167 of 278
B. The user interface shall, to the extent feasible, be web enabled to provide
additional flexibility for the users of the system.
C. The client Operating System user interface shall be configured to limit access
to each application based on user login. Authorized users shall select an
authorized application(s) to execute (e.g., DAPP, EVIDS, AODB, RMS
application) from the client desktop.
D. Software modules shall have a Graphical User Interface (GUI) and use a true
windowing navigation interface.
E. The system shall support a pointing device, touch screen, and keyboard
interface. Standard pointing device actions shall have a "hot key" equivalent.
Pointing device functions without a “hot key” equivalent shall be noted.
F. The systems shall provide context sensitive, on-line help capabilities. The
online help system shall contain enough information to inform the user of the
nature of the current form/window, and provide a reference for the user to
gather further information. The CONTRACTOR shall populate the on-line
help messages prior to Performance Verification Testing and provide a facility
for maintenance and update of online help.
3.10.4 Architecture Requirements
A. Operating System
1. Server Operating System:
The CONTRACTOR shall select a
standardized Operating System to use across all servers such as
Windows (latest version).
The server operating system shall support
Symmetric Multi-Processing (SMP). AIMS applications provided shall
take advantage of the SMP server capabilities.
2. Client Operating System: Client and desktop devices shall use the
Windows XP Professional operating system, or County approved
equivalent.
3. The operating system for the CONTRACTOR‟s products shall meet the
minimum criteria below. All exceptions shall be noted in the Proposal
response.
i
64-bit, multi-tasking, multi-threading.
ii
Support TCP/IP network protocol.
iii Latest version and service pack of the operating system at time of
initiation of systems testing.
B. System Architecture
AIMS Attachment A: AIMS Statement of Work
Page 107 of 130
Exhibit 3
Page 168 of 278
1. The systems shall adhere to a Client / Server model. The end devices
shall be the clients to the primary/secondary servers. All information
shall be communicated between the server(s) and the clients via the
assigned Virtual Local Area Network (VLAN).
2. Network connectivity shall be via the assigned VLAN on the FLL PDS.
Network communications shall utilize TCP/IP network communications
protocol. The CONTRACTOR shall identify the network bandwidth
requirements such as 10 Mb, 100 Mb, or Gigabit Ethernet.
3. End device addressing shall be coordinated with the County.
4. Sufficient resiliency / redundancy and logic shall be provided to assure
that the availability objectives (refer to Performance Requirements,
Section 3.10.5) can be met without manual intervention. All major
system hardware components shall be designed so that there is not
any single point of failure that can cause operations to be disrupted.
5. The system shall synchronize the date and time on all devices. The
system servers shall receive a time synchronization signal from the
local area network using the Network Time Protocol (NTP)..
6. The systems shall use industry standard components. The systems
shall not contain any proprietary interfaces or components.
7. System components shall be independent and capable of co-existing
on the system to allow for an increased level of capacity. Modular
design and flexibility shall be provided for easy expansion of the
system without degradation to the system's performance.
C. Database
1. The requirements below apply to the portions of the AIMS that require
database features.
2. The provided database(s) shall be capable of supporting real time data
warehousing.
The database(s) shall use a common relational
database to store all data. The database(s) shall be based on
accepted and recognized industry standards.
3. The database(s) shall be open database connectivity (ODBC)
compliant and support the simple object access protocol (SOAP).
4. Database Architecture:
requirements:
The database(s) shall meet the following
i
Provide read consistency (data seen by a statement is consistent
with respect to a single point-in-time)
ii
Provide creation of a read-consistent set of data when a table is
being queried (read) and simultaneously updated (written)
AIMS Attachment A: AIMS Statement of Work
Page 108 of 130
Exhibit 3
Page 169 of 278
iii Provide original data values upon query when updated transaction
remains uncommitted
iv Utilize rollback methodology for uncommitted transactions
v
Utilize record locking mechanisms to prevent simultaneous updates
to the same record. Only the record(s) being updated shall be
locked.
vi Provide support for both distributed processing and distributed
multiple databases along with standard DML operations, including
queries, inserts, updates, and deletes of remote table data
vii Provide support for automatic recovery from system or network
failures (i.e., automatically commits or rolls back any in-doubt
distributed transactions consistently on all involved nodes when a
failure occurs)
a Provide referential integrity for all data such that modifications to
current data does not affect historical data
b Provide capability of online “live” backup of all database objects
c
Provide capability of “point of failure” recovery of all database
objects within one hour of the failure (i.e., dump transaction logs
hourly) with a native utility package.
5. Database Security: Third-party database and reporting tools shall
support database security functions. Database security shall include
the following items as a minimum:
i
Encryption capability for defined data fields within database objects
such as tables or views
ii
Prevention of unauthorized database access
iii Prevention of unauthorized access to schema objects
iv Control of system resource usage (such as CPU time)
v
Auditing of user actions and database transactions
vi Assignment of valid username/password combinations
vii Assignment and control of resource limits for a user including
hardware, database and application resources
viii Control of user access rights including database, table, record and
field level authority
ix Control of which system functions a user can perform.
6. The CONTRACTOR shall submit all database schema(s) for review
and approval. The CONTRACTOR shall coordinate with the County,
airlines, and applicable third party vendors to identify unique database
requirements.
The CONTRACTOR shall add needed fields as
AIMS Attachment A: AIMS Statement of Work
Page 109 of 130
Exhibit 3
Page 170 of 278
requested by the County. The database(s) shall be designed such that
the addition of fields and/or tables is easily accommodated. The
database schema shall be provided in a chart format showing all
tables, key fields, and hierarchical relationships.
7. SQL: The utilized native structured programming language shall be
storable in the database. The database shall employ a native
structured programming language that can utilize standard Structured
Query Language (SQL) which includes the following:
i
Data Definition Language (DDL) statements
ii
Data Manipulation Language (DML) statements
iii Transaction control statements
iv Session control statements
v
System control statements
vi Embedded SQL statements
8. Database Maintenance: The database maintenance system shall be
capable of maintaining configuration control (i.e., keep track of
changes and compare versions of the database).
Database
maintenance software shall be provided to allow modification of
designated database fields.
Database documentation shall be
provided to enable the updating or regeneration of the database tables
when inputs are changed and added and as programs are modified or
added.
9. Archival Viewing: The database shall provide an archive capability
that provides “near time” retrieval of archived data. The data held
within the “operational” portion of the database shall include a
minimum of 7 calendar days of operational data. The CONTRACTOR
shall propose, and submit for approval, the maximum amount of
operational data to be stored for real time access that will not impact
the efficiency of the database.
In addition to real-time (daily)
operational data, the database shall provide the ability to generate
real-time reports for operational data for a minimum of thirty-six (36)
months.
10. The database shall include the functionality and capability to allow the
authorized user to view or report on historical data. If the user wishes
to view or report on data which has been archived, an automated
mechanism shall be provided to have the requested data put online.
The methodology for providing this functionality must be approved by
the County prior to implementation.
AIMS Attachment A: AIMS Statement of Work
Page 110 of 130
Exhibit 3
Page 171 of 278
3.10.5 Security, Performance and Management
A. Security
1. Authorized users shall log into the system using a unique user name
and password. Depending on assigned user access privileges, the
user shall be either granted or denied access to individual applications.
In no case shall any user identified via user name and password as an
airline employee or any other user without proper authorization gain
access to any other airline's data, other than that pertaining to their
own flights and baggage.
Data that can be viewed at the user's
workstation pertaining to data by airlines other than the user's airline
shall be limited to data that can be viewed on public displays.
2. The system administrator shall be able to add, delete, set, and change
user privileges and access authorization via a GUI. System security
parameters shall be configurable by the system administrator.
3. The AIMS workstations shall have an "inactivity timeout period" such
that if any workstation is determined to be inactive by having no
input/output performed at that workstation for the defined timeout
period, that workstation shall be automatically logged out of the
application.
4. The timeout feature shall be turned on or off by the system
administrator. The timeout period shall be configurable by the system
administrator.
5. The occurrence of an inactivity timeout occurring as described above
shall be recorded in the fault log, showing date, time, workstation
identifier, and the user name of the user who was logged in at the time
when the inactivity timeout occurred.
6. The AIMS shall prevent a user name from being logged in more than
one time concurrently.
7. The AIMS shall provide an audit trail of all transactions. The audit trail
shall track on a per user basis. The audit trail file shall indicate any
changes that occurred to applications configuration, data structure, or
database fields/records, and shall contain the date and time of the
change, the user identification of the user who made the change, and
the details of the change.
8. The AIMS shall provide automated tracking of the audit trail database,
and shall alert the system administrator when this file has exceeded
pre-determined size restrictions. The system administrator shall then
have the ability to archive this database, along with the ability to
restore it for reporting purposes. The system shall also include the
option of a “rolling window”. In this case, the audit trail database shall
AIMS Attachment A: AIMS Statement of Work
Page 111 of 130
Exhibit 3
Page 172 of 278
use a rolling window with a System Administrator configurable window
(i.e., after defined period of time oldest records are automatically
dumped).
9. If remote access is required for system administration, a security
feature such as secure VPN encryption shall be used and coordinated
with County.
B. Availability Requirements
1. System Availability:
i
Software and system devices shall execute, without degradation, at
the scheduled periods and response times for the systems to be
considered available.
ii
The systems shall operate as specified twenty-four (24) hours per
day, seven 7 days per week.
iii Availability of the overall AIMS shall be at least 99.97 percent (2
hours 38 minutes maximum downtime per year).
2. Device Availability:
i
A system server and PC shall be considered available only if all
components are operating and fully functional.
ii
A peripheral device shall be considered unavailable if it cannot be
placed on-line and perform its intended function(s).
iii Besides scheduled downtime, as identified below, individual device
availability shall exceed 99.80 percent (17 hours 30 minute
maximum downtime per year).
3. Scheduled Downtime:
i
Downtime to update the computer operating system or repair a
component shall be acceptable reasons for downtime, but at no
time shall more than 5 percent of the system be non-operational.
ii
Scheduled downtime shall be anticipated to be between 12:01am
and 3:59am, or during County approved hours and must be
coordinated with the County a minimum of 48 hours in advance of
any work being performed using the County‟s change control
procedures.
iii If the operating system or the servers require maintenance or
updates, or if the servers require system maintenance, each server
shall be brought down individually to be updated/maintained, such
that at no time is more than one server down at the same time.
iv If the operating system of the end device computer requires
maintenance or updates, or if the end device computers require
AIMS Attachment A: AIMS Statement of Work
Page 112 of 130
Exhibit 3
Page 173 of 278
system maintenance, the end device that requires the maintenance
shall be brought down during non-peak hours of operation.
v
It shall be acceptable to perform maintenance/updates on an end
device computer system during other than non-peak hours if the
particular end device is non-functional without having the
maintenance or updates performed.
C. Performance Requirements
1. The system shall be capable of supporting the AIMS within the
performance requirements as outlined herein.
2. The performance requirements in this section are for system design
and testing and not service response time.
3. Capacity: The AIMS shall be designed to support the operational,
functional, and performance requirements, specified herein, for a
minimum of 400 flight operations per hour and 40 different airlines with
a total of 200 users simultaneously conducting 60 user operations per
minute with a minimum of 750 end devices being updated.
4. Response time criteria shall be met under maximum capacity
conditions as defined above.
5. External System Interface: The total additional delay for a transaction
between an AIMS workstation to an external system shall not exceed
1.5 seconds for 95 percent of all transactions. The remaining 5
percent of delays shall not exceed 3.0 seconds.
6. Database Transactions: For 95 percent of database transactions, there
shall be no more than a 0.5 second delay between the time that a user
selects an action and the system responds in some way that the input
has been received. The remaining 5 percent of transactions shall not
exceed 1.0 second.
7. Peripheral Command: For 95 percent of peripheral commands, there
shall be no more than a 3.0 second delay between the time that a user
selects an action and the associated peripheral responds to the
request. The remaining 5 percent of command responses shall not
exceed 5.0 seconds.
8. Peripheral Configuration: For 95 percent of peripheral configuration
changes, there shall be no more than a 6.0 second delay between the
time that a user selects an action and the associated peripheral
responds to the request. The remaining 5 percent of peripheral
configuration changes shall not exceed 10.0 seconds.
9. Display: For 95 percent of dynamic display device changes, there
shall be no more than a 30.0 second delay between the time that a
AIMS Attachment A: AIMS Statement of Work
Page 113 of 130
Exhibit 3
Page 174 of 278
user inputs a database change and the affected display devices reflect
the change. The remaining 5 percent of transactions shall not exceed
45.0 seconds.
D. System Management
1. The devices connected to the network shall be SNMP manageable. A
positive relationship (e.g., system heart beat) shall exist between the
system devices and the controlling server(s) at all times.
2. Managed system failures shall include, but not be limited to, PC failure,
display device failure, application failure (server and local applications),
network connectivity failure, and server failure. Server failure shall
include hardware, software, network, and power based failure.
3. System failures shall be viewable at a central control point (i.e., the
system administrator's workstation). A failure shall initiate an alarm
and add a failure record to the failure database table. The system
administrator shall receive a warning message on the system
administrator workstation, notifying them of the failure. The system
shall provide e-mail, pager, and text messaging notification. The
CONTRACTOR is responsible for providing all hardware, software,
and WAN/PSTN access necessary to support the notification functions.
4. End user devices shall have remote administration and monitoring
capabilities. This capability shall allow the specific machine to be
remotely configured and to provide a status report to the management
system. Data included in the reporting capabilities shall include: data
pertaining to the machine's memory, storage devices, network
connections, and general health of the machine.
3.11
REPORTING REQUIREMENTS - The Contractor shall comply with the
requirements set forth in this Section 3.11.
3.11.1 General
A. The AIMS shall have full reporting capabilities. The system shall support
the utilization of a generic report writer module providing the ability to
develop customized reports. The reporting tool shall be capable of
building reports from any fields in the database and on any subset of
records that user authority allows.
B. The CONTRACTOR shall detail the capabilities, functionality, and the user
interface for both types of reporting.
C. For any and all reports, including both "canned" reports and "ad hoc"
reports, only authorized users shall have access to the reporting features.
AIMS Attachment A: AIMS Statement of Work
Page 114 of 130
Exhibit 3
Page 175 of 278
D. For any and all reports, including both "canned" reports and "ad hoc"
reports, only the system administrator, or users with a sufficient level of
security access authorization shall be able to see all airlines‟ information
on the reports. Airline users shall be limited to reporting data from their
airline only.
E. To ensure the County‟s reporting requirements are fully met, the
CONTRACTOR shall be required to coordinate and administer workshops
with the appropriate airport and tenant stakeholders to define the initial
“canned” reports to be provided with the system. Up to six (6) workshops
shall be held. These workshops shall be split into functional areas of the
AIMS and should include, as a minimum:
1. EVIDS (ADA requirements, display formats, user interfaces, and
reports)
2. Resource Management System Reports
3. Common Use Passenger Processing System Reports
4. Airport Operational Database Reports
3.11.2 Business Intelligence Tool
A. In addition to the reporting requirements specified herein, and further
identified during the implementation process, the CONTRACTOR shall
provide a business intelligence tool to BCAD to allow them to customize
reporting, analysis information, and to develop “dashboards” for
information management. The business intelligence tool shall include the
following, as a minimum:
1. Utilize a multi-tier architecture using modern Web standards, including
but not limited to; XML, SOAP, and WSDL.
2. Utilize a single API to allow programmers to customize BI capabilities.
3. Be scalable to support the entire Airport requirements.
4. Support multiple exporting formats including, but not limited to; Excel,
.pdf, XML, HTML, and CSV.
5. Support flexible data distribution methods including centralized access,
e-mail, application integration, and MS Office.
B. To support the Business Intelligence Tool features and functionality,
training shall be provided by the CONTRACTOR. This training shall be
included in, and coordinated with the training requirements specified in
Section 4.3.
AIMS Attachment A: AIMS Statement of Work
Page 115 of 130
Exhibit 3
Page 176 of 278
3.11.3 EVIDS Reporting Requirements
A. EVIDS Master Flight Database (MFD) Report.
1. CONTRACTOR shall provide a report which lists flights contained in
the MUFIDS Master Flight Database (MFD). The user shall be able to
select records for the report based on various criteria including but not
limited to the following fields:
i
Starting date of the flights.
ii
Ending date of the flights.
iii Day(s) of the week that the flights operate.
iv County name of origin/destination.
v
Assigned gate(s).
vi Assigned baggage carousel(s).
vii Airline(s).
viii Aircraft type(s).
2. For this report, the user shall be able to specify the sort order for the
report. The default sort order, if not specified by the user, shall be by
ascending airline code and flight number. The user shall be able to
specify multiple sorting fields, including but not limited to the following
fields:
i
Day of the week the flight operates.
ii
Assigned gate.
iii Assigned baggage carousel.
iv Airline.
v
Flight number.
vi County name of origin/destination.
B. EVIDS Active Flight Database (AFD) and Historical Flight Database (HFD)
Report. The system shall provide a report which lists flights contained in
the MUFIDS Active Flight Database (AFD) or the Historical Flight
Database (HFD). The user shall be able to select records for this report
based on various criteria, including but not limited to:
1. Assigned gate(s).
2. Assigned baggage carousel(s).
3. County name.
4. Airline(s).
AIMS Attachment A: AIMS Statement of Work
Page 116 of 130
Exhibit 3
Page 177 of 278
5. Aircraft type(s).
6. For the EVIDS AFD and HFD reports, the user shall be able to specify
the sort order for the report. The default sort order, if not specified by
the user, shall be by ascending airline code and flight number. The
user shall be able to specify multiple sorting fields, including but not
limited to the following fields:
i
Assigned gate.
ii
Assigned baggage carousel.
iii County name.
iv Airline.
v
Flight number.
C. Gate Utilization Report: The system shall provide a Gate Utilization Report
which shall list, for each selected gate, the flights utilizing that gate
throughout the defined time period. For this report, the user can specify
the reporting criteria based on the following:
1. Gate(s), default is all gates if not specified.
2. Starting time period, default is 12:01 a.m.
3. Ending time period, default is 12:00 a.m.
D. Video Advertising Report:
The system shall provide a report detailing
the tracking information for the display of video advertising files. The
report shall include the time, length, the display monitor that was used for
all advertisements, and a summary of the number of times each video was
played on each monitor as well as the total number of times each video
was played in a given time period throughout the airport.
E. The initial reporting requirements for EVIDS shall be fully defined during
the stakeholder workshops. The base system shall provide up to fifteen
(15) canned reports to be defined during this process.
3.11.4 Resource Management System Reports
A. The initial reporting requirements of the RMS shall be defined during the
stakeholder workshops. The base system shall provide up to fifteen (15)
canned reports to be defined during this process.
3.11.5 Common Use Passenger Processing Reports
A. The initial reporting requirements of the DAPP shall be defined during the
stakeholder workshops. The base system shall provide up to fifteen (15)
canned reports to be defined during this process.
AIMS Attachment A: AIMS Statement of Work
Page 117 of 130
Exhibit 3
Page 178 of 278
3.11.6 Airport Operational Database Reports
A. The initial reporting requirements of the AODB shall be defined during the
stakeholder workshops. The base system shall provide up to fifteen (15)
canned reports to be defined during this process.
AIMS Attachment A: AIMS Statement of Work
Page 118 of 130
Exhibit 3
Page 179 of 278
4
IMPLEMENTATION
4.1
INSTALLATION REQUIREMENTS
4.1.1 General
A. System installation and construction methods shall conform to the
requirements of the Federal Communications Commission and the
Broward County Aviation Department.
B. Where undefined by codes and standards, CONTRACTOR shall apply a
safety factor of at least 2 times the rated load to all fastenings and
supports of system components.
C. The CONTRACTOR shall install all system components including
furnished equipment in accordance with the manufacturer's instructions,
NFPA 70, ANSI-C2 and shall furnish all cables, connectors, terminators,
interconnections, services, and adjustments required for a complete and
operable system.
D. Grounding shall be installed as necessary to preclude ground loops,
noise, and surges from adversely affecting system operation.
E. For equipment mounted in drawers or on slides, provide the
interconnecting cables with a service loop of not less than three feet and
ensure that the cable is long enough to allow full extension of drawer or
slide.
F. The CONTRACTOR's inspector shall conduct a visual inspection of all
installations to verify that the installations are in accordance with the
County‟s and manufacturer's specifications. Records of the inspections
signed and dated by the inspector shall be provided to the County. The
County shall be notified by the CONTRACTOR of any inspection(s) and
the County Project Manager may elect to participate in any inspection(s).
4.1.2 Software Installation
A. The CONTRACTOR shall test all custom and packaged software in
development and production environments, and have successfully passed
Factory Acceptance Testing, prior to installation on-site.
4.1.3 Hardware Installation
A. Final hardware selected and installation of hardware shall be coordinated
with the County Project Manager. Additionally, the CONTRACTOR shall
ensure the ventilation requirements for all the hardware components are
met.
AIMS Attachment A: AIMS Statement of Work
Page 119 of 130
Exhibit 3
Page 180 of 278
B. The CONTRACTOR shall install and inspect all hardware required in this
specification in accordance with the manufacturer's installation
instructions. Final placement of hardware is subject to the County‟s
approval.
C. 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 the County.
D. The CONTRACTOR shall obtain written permission from the County
before proceeding with any work which requires cutting into or through any
part of the building structures such as, but not limited to, girders, beams,
concrete, carpeted or tiled floors, partitions or ceilings.
The
CONTRACTOR shall obtain written permission from the County before
cutting into or through any part of the building structures where
fireproofing or moisture proofing could be impaired. In any such case the
CONTRACTOR shall be responsible for restoring the affected area to
“like-new” condition or to a condition to match the existing conditions.
E. The CONTRACTOR shall take all steps necessary to ensure that all public
areas remain clear or are properly marked during installation or
maintenance.
F. The CONTRACTOR shall coordinate installation with the County, to
minimize disruption of existing business functions at the Airport.
G. The CONTRACTOR shall place materials only in those locations that have
been previously approved. Any other locations shall be approved, in
writing, by the County.
H. The CONTRACTOR shall label all cabling and patch cords in accordance
with the BCAD approved labeling plan. Coordination with the County shall
be performed, and all labeling shall be approved, prior to implementation.
4.1.4 System Startup
A. The CONTRACTOR shall not apply power to the system until after:
1. System and components have been installed and inspected in
accordance with the manufacturer's installation instructions.
2. A visual inspection of the system components has been conducted to
ensure that defective equipment items have not been installed and that
there are no loose connections.
3. System wiring has been tested and verified as correctly connected as
indicated.
4. All system grounding and transient protection systems have been
verified as properly installed and connected, as indicated.
AIMS Attachment A: AIMS Statement of Work
Page 120 of 130
Exhibit 3
Page 181 of 278
5. Power supplies to be connected to the system and equipment have
been verified as the correct voltage, phasing, and frequency as
indicated.
B. Satisfaction of the above requirements shall not relieve the
CONTRACTOR of responsibility for incorrect installations, defective
equipment items, or collateral damage as a result of CONTRACTOR
work/equipment.
4.2
TESTING REQUIREMENTS
4.2.1 General
A. Testing Steps:
1. On-Site Factory Acceptance Testing
2. On-Site Performance Verification Testing
3. On-Site Endurance Testing
B. Test Plan/Procedure: The CONTRACTOR shall provide six (6)
hardcopies and an electronic copy of the test plan/procedures for each
testing phase for the review and approval of the County. The test plan for
each phase shall detail the objectives of all tests. The tests shall clearly
demonstrate that the system and its components fully comply with the
requirements specified herein. The test plan shall be provided at least
forty-five (45) calendar days prior to the scheduled start of each test. Test
plans shall contain at a minimum:
1. Functional procedures including use of any test equipment
2. Test equipment is to be identified by manufacturer and model
3. Interconnection of test equipment and steps of operation shall be
defined
4. Test records shall include test equipment serial number, calibration
date and calibration certification of test equipment
5. Expected results required to comply with specifications
6. Traceability matrix referencing specification requirements with specific
test procedures
7. Record of test results with witness initials or signature and date
performed
8. Pass or fail evaluation with comments.
AIMS Attachment A: AIMS Statement of Work
Page 121 of 130
Exhibit 3
Page 182 of 278
C. The test procedures shall provide conformity to all specification
requirements. Satisfactory completion of all test procedures is necessary
as a condition of Final Acceptance.
D. The CONTRACTOR's Quality Control Organization shall review all formal
test procedures prepared by the CONTRACTOR and deliverable under
the Contract to assure the tests cover all requirements and that there is a
conformity between the conducted test, the test results and specification
requirements
E. Documentation verification, both interconnects and functionality shall be
part of the test. Where documentation is not in accordance with the
installed system interconnect and operating procedures, the system shall
not be considered accepted until the system and documentation correlate.
F. All testing must be witnessed by the County representative(s). The
CONTRACTOR shall cooperate with fully with the County in this regard.
G. Test Reports: The CONTRACTOR shall prepare, for each test, a test
report document that shall certify successful completion of that test. Six
(6) hardcopies and one electronic version of the test report shall be
submitted to the County for review and acceptance within seven (7)
calendar days following each test. The test report shall contain, at a
minimum:
1. Commentary on test results.
2. A listing and discussion of all discrepancies between expected and
actual results and of all failures encountered during the test and their
resolution.
3. Complete copy of test procedures and test data sheets with
annotations showing dates, times, initials, and any other annotations
entered during execution of the test.
4. Signatures of persons who performed and witnessed the test.
H. Test Resolution: Any discrepancies or problems discovered during these
tests shall be corrected by the CONTRACTOR at no cost to the County.
The problems identified in each phase shall be corrected and the
percentage of the entire system re-tested determined by the County,
before any subsequent testing phase is performed.
4.2.2 Factory Acceptance Testing (FAT)
A. Test Setup Equipment: Equipment shall be actual products or identical
models of products to those designated to be delivered and installed at the
site. The following equipment shall be setup and used for conducting predelivery test:
AIMS Attachment A: AIMS Statement of Work
Page 122 of 130
Exhibit 3
Page 183 of 278
1. Operator equipment associated with system.
2. End devices and displays associated with system.
3. Software associated with system.
4. Administrative console equipment.
5. Sufficient signal transmission media (STM) and associated equipment
and accessories to provide a fully integrated system model. Include at
least one of each type STM circuit.
6. Number of field processors required for system to be installed at site.
7. Enough load and data simulators to provide simulation of full load
operational conditions as required by design. Loads shall be manually
or software generated.
B. Preparation:
Ensure that development of system is complete, required
approvals of submittals have been obtained, and sufficient equipment
procured to completely demonstrate and test system. Schedule FAT with
County Project Manager at least 45 calendar days prior to test:
C. Time: Conduct during County Work Day.
D. Location: FLL test lab.
E. Test: The purpose is to test the complete computer software package and
equipment of the system and demonstrate that all specified features and
performance criteria are met. All requirements of the specification shall be
tested including, but not limited to:
1. Functionality including reporting and response.
2. System capacity.
3. Hardware interaction.
4. Hardware and software interaction.
5. Demonstrate report generation.
F. Acceptance: Acceptance of system to perform sufficiently and provide
specified functions shall be determined by the County representatives
witnessing the Factory Acceptance Test.
1. Acceptance Criteria: Performance of system shall equal or exceed
criteria stated in individual specification sections.
2. If system does not perform satisfactorily, the CONTRACTOR shall
make corrections and modifications and schedule new test with the
AIMS Attachment A: AIMS Statement of Work
Page 123 of 130
Exhibit 3
Page 184 of 278
County. Compliance is at the sole discretion of the County. If the
County deems that compliance cannot be met, or is insufficient, they
shall have the right to terminate the Contract.
3. Expenses for County representatives to attend re-testing shall be
borne by CONTRACTOR.
G. Completion:
1. At successful completion of test, dismantle equipment so as to prevent
damage. Replace all defective or worn items.
2. Re-pack in original containers all equipment to be field deployed during
phase three of the implementation. Mark on containers that items
were used in FAT.
H. Reporting:
1. Record all test procedures and results.
2. Submit report in accordance with reporting requirements in General
Testing Requirements Section.
4.2.3 Performance Verification Testing
A. Complete operational testing of all components and systems shall be
witnessed by designated County Representatives.
B. Schedule test with County. Do not begin testing until:
1. All systems have been installed and individually and jointly tested to
ensure they are operating properly.
2. Written permission from County has been received.
C. Testing: As part of Performance Verification Testing, test all components
of system. The tests shall demonstrate system features.
D. Verification: Verify correct operation of the required system functionality
as defined in these specifications.
E. Adjustment, Correction, and Completion:
1. Correct deficiencies and retest affected components.
2. Make necessary adjustments and modification to system after
obtaining approval of the County.
3. Completion: Performance Verification Testing shall be complete when
testing or retesting of each component has produced a positive result
and has been approved in writing by the County.
AIMS Attachment A: AIMS Statement of Work
Page 124 of 130
Exhibit 3
Page 185 of 278
F. Recording:
1. Describe actual operational tests performed and equipment used and
list personnel performing tests.
2. Record in tabular form all test results, deficiencies, and corrective
measures.
G. Termination
1. Performance Verification Testing shall be terminated by the County
when:
i
Individual components, subsystems, or the AIMS fail to perform as
specified.
ii
It is determined that system is missing components or installation is
not complete.
2. Upon termination, corrective work shall be performed and Performance
Verification Testing rescheduled with the County.
3. Retesting shall be performed by CONTRACTOR at no additional
expense.
4. CONTRACTOR shall continue to perform corrective actions and retest
until system passes all tests to satisfaction of the County.
4.2.4 Endurance Testing
A. CONTRACTOR to provide personnel to monitor the system operation 24
hours per day, including weekends and holidays during endurance testing.
B. Start test after:
1. Successful completion of Performance Verification Testing.
2. Training as specified has been completed.
3. Correction of deficiencies has been completed.
4. Receipt of written start notification from the County.
C. Monitor all systems during Endurance Testing.
with the County.
Coordinate monitoring
D. Recording: Record data on approved forms so as to provide a continuous
log of systems performance. Include:
1. Date and time for all entries.
2. Name of individual making entry.
AIMS Attachment A: AIMS Statement of Work
Page 125 of 130
Exhibit 3
Page 186 of 278
3. Environmental conditions.
4. Authority activities in process.
5. Description of all alarm annunciations, responses, corrective actions,
and causes of alarms. Classify as to type of alarm.
6. Description of all equipment failures, including software errors.
7. Description of all maintenance and adjustment operations performed
on system.
8. Daily and weekly tabulations.
9. Daily entries of performance data shall be reviewed by the County‟s
representative designated to observe monitoring of system.
E. The County may terminate testing at any time when the system fails to
perform as specified. Upon termination of testing the CONTRACTOR
shall commence an assessment period as described in Step II.
F. Testing
1. Step I - Initial Testing:
i
Time: 24 hours per day for 30 calendar days.
ii
CONTRACTOR to make no repairs during this phase unless
authorized in writing by the County.
iii If system experiences no failures, proceed to Step III - Final
Testing.
2. Step II - Initial Assessment:
i
After conclusion of Step I or termination of testing, CONTRACTOR
to identify all failures, determine causes, and repair. Submit report
explaining: Nature of each failure, corrective action taken, results
of tests performed to verify corrective action as being successful,
and recommended point for resumption of testing.
ii
After CONTRACTOR‟s submission of report, schedule review
meeting at job site. Schedule date and time with the County.
iii At review meeting, demonstrate that all failures have been
corrected by performing Performance Verification Testing.
iv Based on report and review meeting, the County will direct
CONTRACTOR to conclude endurance testing, or proceed to Step
III - Final Testing.
3. Step III - Final Testing:
i
Time: 24 hours per day for 30 calendar days.
AIMS Attachment A: AIMS Statement of Work
Page 126 of 130
Exhibit 3
Page 187 of 278
ii
CONTRACTOR to make no repairs during this phase unless
authorized in writing by the County.
4. Step IV - Final Assessment:
i
After successful completion of Step I, conclusion of Step III, or
termination of testing, CONTRACTOR to identify all failures,
determine causes, and repair. Submit explaining the nature of
each failure, corrective action taken, results of tests performed, and
recommended point for resumption of testing.
ii
After submission of report schedule review meeting at job site.
CONTRACTOR to schedule date and time with the County.
iii At review meeting, demonstrate that all failures have been
corrected by performing Performance Verification Testing.
iv Based on report and review meeting, the County will approve
endurance test or direct CONTRACTOR to repeat all or part of
Steps III and IV.
4.2.5 Adjustment, Correction, and Maintenance
A. During Endurance Testing CONTRACTOR is to make adjustments and
corrections to system only after obtaining written approval of the County.
B. During Endurance Testing, CONTRACTOR is to perform required
maintenance on systems including provision of replacement parts.
4.2.6 Final Inspection
A. After Endurance Testing is complete, review tabulated records with the
County.
B. The CONTRACTOR will not be responsible for failures caused by:
1. Outage of main power in excess of backup power capability provided
that automatic initiation of all backup sources was accomplished and
automatic shutdowns and restarts of systems performed as specified.
2. Failure of any County furnished power, communications, and control
circuits provided failure was not due to CONTRACTOR furnished
equipment, installation, or software.
3. Failure of existing County equipment provided failure was not due to
CONTRACTOR furnished equipment, installation, or software.
C. When performance of AIMS does not fall within the above rates,
CONTRACTOR shall determine cause of deficiencies, correct, and retest.
AIMS Attachment A: AIMS Statement of Work
Page 127 of 130
Exhibit 3
Page 188 of 278
1. When requested by the County, CONTRACTOR shall extend
monitoring period for a time as designated by the County.
2. Period shall not exceed 60 calendar days exclusive of retesting periods
caused by termination of Steps I or III and assessment period of Steps
II and IV.
3. CONTRACTOR shall Submit final report of endurance testing
containing all recorded data.
D. The CONTRACTOR shall submit written certification that:
1. All documents have been reviewed.
2. All required as-built documentation has been submitted and approved
by the County.
3. The Project had been inspected for compliance with the Contract
Documents.
4. The work has been completed in accordance with the Contract
Documents.
5. The equipment and systems have been tested and are shown
operational in the presence of the County.
6. The Project is completed, and is ready for final inspection.
E. When the County considers the work is finally complete and in accordance
with the requirements of the Contract Documents, the County shall
request the CONTRACTOR to provide project closeout submittals.
4.3
TRAINING
4.3.1 General
A. By means of training classes augmented by individual instruction as
necessary, the CONTRACTOR shall fully instruct the County‟s designated
staff and Airline personnel in the operation, adjustment and maintenance
of all AIMS software and equipment. The CONTRACTOR shall be
required to provide all training aids, e.g., notebooks, manuals. The
CONTRACTOR shall provide an appropriate training area equipped with
all required equipment. The location of the training area shall be
coordinated with the County.
B. All training shall be completed a minimum of two weeks prior to the AIMS
or any subcomponent of AIMS being used in a production environment.
Training schedule shall support the various work shifts of airport and
tenant personnel and shall be subject to the County approval.
AIMS Attachment A: AIMS Statement of Work
Page 128 of 130
Exhibit 3
Page 189 of 278
C. Training shall be conducted by experienced personnel and supported by
training aids. An adequate number and amount of training material shall
be provided by the CONTRACTOR. The following is considered a
minimum.
1. Functional flow-charts, overall block diagrams, and descriptive material
for all software;
2. Schematic drawings for each of the hardware components;
3. All procedure manuals, specification manuals, and operating manuals;
4. As-built drawings.
D. Participants shall receive individual copies of technical manuals and
pertinent documentation at the time the course is conducted. The courses
shall be scheduled such that County personnel can participate in all
courses (no overlap).
E. A final course schedule and syllabus shall be prepared by the
CONTRACTOR for each course to be conducted for Airport personnel,
and submitted for review at least four (4) weeks prior to the scheduled
date of the course commencement.
F. Each course outline shall include, in addition to the subject matter, a short
review of the prerequisite subjects (where appropriate); how this course
fits into the overall training program; the objective; the standards of
evaluation; and any other topics that will enhance the training
environment.
G. A DVD of each course shall be provided to the County.
H. All training requirements identified are minimum requirements.
4.3.2 Types of Training
A. User Training: System users shall be instructed in all aspects of
operations of the system, including the business intelligence tool and all
reporting functions. Twelve (12) hours of basic user training shall be
provided (2 hour class repeated 6 times with 10 system users per class).
Additionally, twelve (12) hours of advanced user training shall be provided
(4 hour class repeated 3 times with six advanced users per class). User
training shall be conducted at a location that is coordinated with the
County.
B. Technician Training: Twenty-four (24) hours of maintenance training (24
hours of training repeated 1 time for 4 maintenance technicians per class)
shall be provided. Training for maintenance technicians shall be provided
on site, and shall include, but not be limited to, installation, operation,
AIMS Attachment A: AIMS Statement of Work
Page 129 of 130
Exhibit 3
Page 190 of 278
renovation, alteration, inspection, maintenance and service on each
system and subsystem provided, so as to enable troubleshooting and
repair to the component level. Maintenance training shall be conducted at
a location that is coordinated with the County.
C. System Administrator Training: System administrator training shall be
provided. System administrator training shall include both classroom work
and on the job training.
1. Classroom Training: Forty-eight (48) hours of software training (48
hours of training repeated 1 time for 2 system administrators) shall be
provided. The CONTRACTOR shall structure the course to describe
all systems, software and applications and support programs. This
course shall include a functional overview of the complete software
system. The course material must be presented in depth with the
instructor covering detailed design, structure, and algorithms. Location
of this training shall be coordinated with the County‟s Project Manager.
2. On the Job Training: An additional six (6) weeks of on the job training
shall be provided. On the job training of the designated County
personnel shall commence no later than two months prior to expiration
of the equipment warranty period. This training shall be conducted on
site at the Airport. The CONTRACTOR shall provide County specified
trainees with daily job supervision and direction by a CONTRACTOR
Engineer. The CONTRACTOR shall answer any and all questions
regarding the operation, repair, and maintenance of the AIMS software
and equipment.
AIMS Attachment A: AIMS Statement of Work
Page 130 of 130
Exhibit 3
Page 191 of 278
EXHIBIT B
GOODS AND SYSTEM HARDWARE
Project No:
RFP No. 20070514-0-AV-01
Project Title:
AIMS: Airport Information Management System
Facility Name: Ft. Lauderdale/Hollywood International Airport
Item
Server Hardware
File Server
Database Server
Application Server
Data Storage System
UPS
System PCs
Performance Workstation
Standard Workstation
Display Device Controller
Integrated System Devices
CUSS Kiosk
DAPP Input W/S
LCD Information Displays 32”
LCD Information Displays 40”
LED Information Displays
Peripherals
Baggage Input Console
2D Ticket Printer
Bag Tag Printer
Magnetic Stripe Reader
Boarding Gate Reader
DAPP Standard Printer
General Document Printer
EPM
10 meter network jumper
3 meter network jumper
Network Switch – 48 Port
Printer Stand
Wall Mount w/Tilt
Manufacturer
Model
Qty
Dell
Dell
Dell
Dell
APC
PowerEdge 2950 III
PowerEdge 2950 III
PowerEdge 2950 III
PowerVault MD3000i
Smart-UPS XL 2200VA 120V
2
3
3
4
4
Dell
Dell
Dell
Optiplex 755
Optiplex 755
Optiplex 755
13
43
37
IER
ELO
NEC
NEC
Daktronics
918B
15A2 Touch Computer
48
177
11
28
19
ELO
Vidtronix
Vidtronix
Access
Unimark
Okidata
HP
Quatech
15A2 Touch Computer
MAP Mark-IV
MAP Mark-IV
ATB-421
EC-3000
Microline 320/321
1200 Laser
ESE-100D
Cisco
Vidtronix
Chief
3560
Galaxy AF-3010-16x128-7.62RC
PRO 2241
23
62
62
119
12
11
2
232
30
500
1
10
30
CRT
CRT
CRT
CRT
CRT
CRT
EVIDS Flight Information
EVIDS Flight Information
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
031
032
033
034
035
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
NEC
NEC
NEC
NEC
NEC
NEC
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
CRT
EVIDS Flight Information
EVIDS Flight Information
022
030
CRT
EVIDS Flight Information
021
029
CRT
EVIDS Flight Information
020
CRT
CRT
EVIDS Flight Information
019
EVIDS Flight Information
CRT
EVIDS Flight Information
018
028
CRT
EVIDS Flight Information
017
CRT
CRT
EVIDS Flight Information
016
EVIDS Flight Information
CRT
EVIDS Flight Information
015
027
CRT
EVIDS Flight Information
014
CRT
CRT
EVIDS Flight Information
013
EVIDS Flight Information
CRT
EVIDS Flight Information
012
026
CRT
EVIDS Flight Information
011
CRT
CRT
EVIDS Flight Information
010
EVIDS Flight Information
CRT
EVIDS Flight Information
009
025
CRT
EVIDS Flight Information
008
CRT
LCD
CRT
EVIDS Flight Information
007
CRT
LCD
EVIDS Flight Information
006
EVIDS Flight Information
LCD
Counter Airline Logo
005
EVIDS Flight Information
LCD
Counter Airline Logo
004
023
CRT
LCD
Counter Airline Logo
003
024
CRT
LCD
Counter Airline Logo
002
NEC
LCD
Counter Airline Logo
001
Manufacturer
Display Type
Use Description
Location
Ref. #
Flight Info & Times
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
CRT
CRT
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Displayed Data
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 1 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
Distribution Point
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T4 Gate H4 (Extron TR/RC Used)
T4 Gate H3 (Extron TR/RC Used)
T4 Gate H2 (Extron TR/RC Used)
T4 Gate H1 (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Concoure H (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Ticket Level (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Bag Claim (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs (Extron TR/RC Used)
T4 Customs Bag Claim
T4 Customs Bag Claim
FIS Counter 5 (Extron TR/RC Used)
FIS Counter 4 (Extron TX/RX Used)
FIS Counter 3 (Extron TX/RX Used)
FIS Counter 2 (Extron TX/RX Used)
FIS Counter 1 (Extron TX/RX Used)
Notes
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 192 of 278
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
Counter Airline Logo
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
064
065
066
067
Daktronics
Daktronics
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
CRT
CRT
CRT
CRT
CRT
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
LCD
Counter Airline Logo
045
Bag Claim Informatiom
LCD
Counter Airline Logo
044
070
LCD
Counter Airline Logo
043
LED
LCD
Counter Airline Logo
042
LCD
CRT
Gate Airline Logo
041
Counter Airline Logo
CRT
Gate Airline Logo
040
Bag Claim Informatiom
CRT
Gate Airline Logo
039
069
NEC
CRT
Gate Airline Logo
038
068
NEC
CRT
Gate Airline Logo
037
CRT
CRT
Gate Airline Logo
036
Manufacturer
Display Type
Use Description
Location
Ref. #
Galaxy 32X192 Tri
Galaxy 32X192 Tri
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
CRT
CRT
CRT
CRT
CRT
CRT
Model #
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 2 of 41
Serial
Serial
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Airline Logo
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Displayed Data
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
Distribution Point
T4-1003
T4-1003
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T4 Bag Claim #1 Back (Lantronix Server)
T4 Bag Claim #1 Front (Lantronix Server)
T4 Counter 53 & 54 (Extron TR/RC Used)
T4 Counter 51 & 52 (Extron TR/RC Used)
T4 Counter 49 & 50 (Extron TR/RC Used)
T4 Counter 47 & 48 (Extron TR/RC Used)
T4 Counter 45 & 46 (Extron TR/RC Used)
T4 Counter 43 & 44 (Extron TR/RC Used)
T4 Counter 41 & 42 (Extron TR/RC Used)
T4 Counter 39 & 40 (Extron TR/RC Used)
T4 Counter 37 & 38 (Extron TR/RC Used)
T4 Counter 35 & 36 (Extron TR/RC Used)
T4 Counter 33 & 34 (Extron TR/RC Used)
T4 Counter 31 & 32 (Extron TR/RC Used)
T4 Counter 29 & 30 (Extron TR/RC Used)
T4 Counter 27 & 28 (Extron TR/RC Used)
T4 Counter 25 & 26 (Extron TR/RC Used)
T4 Counter 23 & 24 (Extron TR/RC Used)
T4 Counter 21 & 22 (Extron TR/RC Used)
T4 Counter 19 & 20 (Extron TR/RC Used)
T4 Counter 17 & 18 (Extron TR/RC Used)
T4 Counter 15 & 16 (Extron TR/RC Used)
T4 Counter 13 & 14 (Extron TR/RC Used)
T4 Counter 11 & 12 (Extron TR/RC Used)
T4 Counter 9 & 10 (Extron TR/RC Used)
T4 Counter 7 & 8 (Extron TR/RC Used)
T4 Counter 5 & 6 (Extron TR/RC Used)
T4 Counter 3 & 4 (Extron TR/RC Used)
T4 Counter 1 & 2 (Extron TR/RC Used)
T4 Gate H10 (Extron TR/RC Used)
T4 Gate H9 (Extron TR/RC Used)
T4 Gate H8 (Extron TR/RC Used)
T4 Gate H7 (Extron TR/RC Used)
T4 Gate H6 (Extron TR/RC Used)
T4 Gate H5 (Extron TR/RC Used)
Notes
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 193 of 278
LED
LED
LED
Bag Claim Informatiom
Clock
Passenger Paging
076
077
078
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Clock
Passenger Paging
Clock
Passenger Paging
Clock
Passenger Paging
Clock
Passenger Paging
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
082
083
084
085
086
087
088
089
090
091
092
093
094
095
096
097
098
099
100
101
102
103
104
105
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Clock
Passenger Paging
081
LED
LED
Bag Claim Informatiom
075
LED
LED
Bag Claim Informatiom
074
Clock
LED
Bag Claim Informatiom
073
Passenger Paging
LED
Bag Claim Informatiom
072
080
LED
Bag Claim Informatiom
071
079
Display Type
Use Description
Location
Ref. #
Serial
Serial
Psgr Info Scripts
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 3 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Serial
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Serial
Serial
Time
Serial
Serial
Serial
Psgr Info Scripts
Psgr Info Scripts
Time
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Serial
Protocol
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Displayed Data
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Model #
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Distribution Point
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
T4-1003
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T4 Jet Bridge H5 (Lantronix Server)
T4 Jet Bridge H4 (Lantronix Server)
T4 Jet Bridge H3 (Lantronix Server)
T4 Jet Bridge H2 (Lantronix Server)
T4 Jet Bridge H1 (Lantronix Server)
T4 Gate H10 (Lantronix Server)
T4 Gate H9 (Lantronix Server)
T4 Gate H8 (Lantronix Server)
T4 Gate H7 (Lantronix Server)
T4 Gate H6 (Lantronix Server)
T4 Gate H5 (Lantronix Server)
T4 Gate H4 (Lantronix Server)
T4 Gate H3 (Lantronix Server)
T4 Gate H2 (Lantronix Server)
T4 Gate H1 (Lantronix Server)
T4 H Conc South (Lantronix Server)
T4 H Conc South (Lantronix Server)
T4 H Conc North (Lantronix Server)
T4 H Conc North (Lantronix Server)
T4 H Checkpoint (Lantronix Server)
T4 H Checkpoint (Lantronix Server)
T4 Ticketing West (Lantronix Server)
T4 Ticketing West (Lantronix Server)
T4 Ticketing East (Lantronix Server)
T4 Ticketing East (Lantronix Server)
T4 Bag Claim West (Lantronix Server)
T4 Bag Claim West (Lantronix Server)
T4 Bag Claim East (Lantronix Server)
T4 Bag Claim East (Lantronix Server)
T4 Bag Claim #4 Back (Lantronix Server)
T4 Bag Claim #4 Front (Lantronix Server)
T4 Bag Claim #3 Back (Lantronix Server)
T4 Bag Claim #3 Front (Lantronix Server)
T4 Bag Claim #2 Back (Lantronix Server)
T4 Bag Claim #2 Front (Lantronix Server)
Notes
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 194 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
INFAX
INFAX
INFAX
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Displayed Data
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infax Built
Infax Built
Infax Built
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Flight Input
Flight Input
Flight Input
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Cat 5E
Cat 5E
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Distribution Point
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 4 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Protocol
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Model #
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4 #27 TC Display (Lantronix Server)
T4 #26 TC Display (Lantronix Server)
T4 #25 TC Display (Lantronix Server)
T4 #24 TC Display (Lantronix Server)
T4 #23 TC Display (Lantronix Server)
T4 #22 TC Display (Lantronix Server)
T4 #21 TC Display (Lantronix Server)
T4 #20 TC Display (Lantronix Server)
T4 #19 TC Display (Lantronix Server)
T4-2041A
T4-2041A
T4 #18 TC Display (Lantronix Server)
T4 #17 TC Display (Lantronix Server)
T4 #16 TC Display (Lantronix Server)
T4 #15 TC Display (Lantronix Server)
T4 #14 TC Display (Lantronix Server)
T4 #13 TC Display (Lantronix Server)
T4 #12 TC Display (Lantronix Server)
T4 #11 TC Display (Lantronix Server)
T4 #10 TC Display (Lantronix Server)
T4 #9 TC Display (Lantronix Server)
T4 #8 TC Display (Lantronix Server)
T4 #7 TC Display (Lantronix Server)
T4 #6 TC Display (Lantronix Server)
T4 #5 TC Display (Lantronix Server)
T4 #4 TC Display (Lantronix Server)
T4 #3 TC Display (Lantronix Server)
T4 #2 TC Display (Lantronix Server)
T4 #1 TC Display (Lantronix Server)
T4 BTID West (Lantronix Server)
T4 BTID East (Lantronix Server)
T4 BTID East (Lantronix Server)
T4 Jet Bridge H10 (Lantronix Server)
T4 Jet Bridge H9 (Lantronix Server)
T4 Jet Bridge H8 (Lantronix Server)
T4 Jet Bridge H7 (Lantronix Server)
T4 Jet Bridge H6 (Lantronix Server)
Notes
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-1003
T4-2041A
T4-2041A
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 195 of 278
LED
LED
LED
LED
LCD
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Counter Airline Logo
163
164
165
166
167
168
NEC
NEC
Dell
Dell
Dell
Dell
NEC
NEC
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LCD
LED
Ticket Counter Display
162
EVIDS Flight Information
LED
Ticket Counter Display
161
175
LED
Ticket Counter Display
160
LCD
LED
Ticket Counter Display
159
LCD
LED
Ticket Counter Display
158
EVIDS Flight Information
LED
Ticket Counter Display
157
EVIDS Flight Information
LED
Ticket Counter Display
156
174
LED
Ticket Counter Display
155
173
LED
Ticket Counter Display
154
LCD
LED
Ticket Counter Display
153
EVIDS Flight Information
LED
Ticket Counter Display
152
172
LED
LED
Ticket Counter Display
151
LCD
LED
Ticket Counter Display
150
EVIDS Flight Information
LED
Ticket Counter Display
149
171
LED
Ticket Counter Display
148
LCD
LED
Ticket Counter Display
147
LCD
LED
Ticket Counter Display
146
Counter Airline Logo
LED
Ticket Counter Display
145
EVIDS Flight Information
LED
Ticket Counter Display
144
170
LED
Ticket Counter Display
143
169
Daktronics
Daktronics
LED
Ticket Counter Display
142
Daktronics
LED
Ticket Counter Display
141
Manufacturer
Display Type
Use Description
Location
Ref. #
LCD4010BK(A)-IT
LCD4010BK(A)-IT
17" Monitor
17" Monitor
17" Monitor
17" Monitor
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Airline Logo
Airline Logo
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 5 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Serial
Serial
Serial
Serial
Serial
Serial
Airline/Open/Closed
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
T3-2054
T3-2054
T3-2054
T3-2054
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Distribution Point
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
T4-2041A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T3 Bag Claim North
T3 Bag Claim North
T3 Flight Deck
T3 Flight Deck
T3 Flight Deck
T3 Flight Deck
T3 Ticket Counter 5 & 6
T3 Ticket Counter 3 & 4
T4 #54 TC Display (Lantronix Server)
T4 #53 TC Display (Lantronix Server)
T4 #52 TC Display (Lantronix Server)
T4 #51 TC Display (Lantronix Server)
T4 #50 TC Display (Lantronix Server)
T4 #49 TC Display (Lantronix Server)
T4 #48 TC Display (Lantronix Server)
T4 #47 TC Display (Lantronix Server)
T4 #46 TC Display (Lantronix Server)
T4 #45 TC Display (Lantronix Server)
T4 #44 TC Display (Lantronix Server)
T4 #43 TC Display (Lantronix Server)
T4 #42 TC Display (Lantronix Server)
T4 #41 TC Display (Lantronix Server)
T4 #40 TC Display (Lantronix Server)
T4 #39 TC Display (Lantronix Server)
T4 #38 TC Display (Lantronix Server)
T4 #37 TC Display (Lantronix Server)
T4 #36 TC Display (Lantronix Server)
T4 #35 TC Display (Lantronix Server)
T4 #34 TC Display (Lantronix Server)
T4 #33 TC Display (Lantronix Server)
T4 #32 TC Display (Lantronix Server)
T4 #31 TC Display (Lantronix Server)
T4 #30 TC Display (Lantronix Server)
T4 #29 TC Display (Lantronix Server)
T4 #28 TC Display (Lantronix Server)
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 196 of 278
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
199
200
201
202
203
204
205
206
207
208
209
210
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LCD
LCD
EVIDS Flight Information
192
LCD
LCD
EVIDS Flight Information
191
EVIDS Flight Information
LCD
EVIDS Flight Information
190
EVIDS Flight Information
LCD
EVIDS Flight Information
189
198
LCD
EVIDS Flight Information
188
197
LCD
EVIDS Flight Information
187
LCD
LCD
EVIDS Flight Information
186
EVIDS Flight Information
LCD
EVIDS Flight Information
185
196
LCD
EVIDS Flight Information
184
LCD
LCD
EVIDS Flight Information
183
EVIDS Flight Information
LCD
EVIDS Flight Information
182
195
LCD
EVIDS Flight Information
181
LCD
LCD
EVIDS Flight Information
180
LCD
LCD
EVIDS Flight Information
179
EVIDS Flight Information
LCD
EVIDS Flight Information
178
EVIDS Flight Information
LCD
EVIDS Flight Information
177
193
LCD
EVIDS Flight Information
176
194
Display Type
Use Description
Location
Ref. #
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Model #
Cable
T3 E Conc East
T3 E Conc East
T3 E Conc East
T3 E Conc East
T3 TC Center
T3 TC Center
T3 TC Center
T3 TC Center
T3 TC Center
T3 TC Center
T3 Ticketing South
T3 Ticketing South
T3 Ticketing South
T3 Ticketing South
T3 Ticketing South
Flight Info & Times
T3 E Conc West
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3 Ticketing North
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
T3 Ticketing South
T3 Ticketing North
T3 Ticketing North
T3 Ticketing North
T3 Ticketing North
T3 Ticketing North
T3 Bag Claim South
T3 Bag Claim South
T3 Bag Claim South
T3 Bag Claim South
T3 Bag Claim South
T3 Bag Claim South
T3 Bag Claim North
T3 Bag Claim North
T3 Bag Claim North
T3 Bag Claim North
Notes
T3 E Conc East
Nearest IDF
T3 E Conc East
Distribution Point
Flight Info & Times
Page 6 of 41
Protocol
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Displayed Data
Existing EVIDS Display Devices Inventory Sheet
Exhibit 3
Page 197 of 278
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
Gate Airline Info Logo
220
221
222
223
224
225
226
227
228
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
Gate Airline Info Logo
236
237
238
239
240
241
242
243
244
245
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
NEC
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LCD
LCD
Gate Airline Info Logo
Gate Airline Info Logo
234
235
LCD
LCD
Gate Airline Info Logo
Gate Airline Info Logo
232
233
LCD
LCD
EVIDS Flight Information
219
Gate Airline Info Logo
LCD
EVIDS Flight Information
218
231
LCD
EVIDS Flight Information
217
LCD
LCD
EVIDS Flight Information
216
LCD
LCD
EVIDS Flight Information
215
Gate Airline Info Logo
LCD
EVIDS Flight Information
214
Gate Airline Info Logo
LCD
EVIDS Flight Information
213
229
LCD
230
LCD
EVIDS Flight Information
EVIDS Flight Information
211
212
Display Type
Use Description
Location
Ref. #
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Model #
Cable
T3 Gate F5
T3 Gate F4
T3 Gate F3
T3 Gate F2
T3 Gate F1
T3 Gate E10
T3 Gate E9
T3 Gate E8
T3 Gate E7
T3 Gate E6
T3 Gate E5
T3 Gate E4
T3 Gate E3
T3 Gate E2
Fllight Info & Logo
T3 Gate F8
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3 Gate E1
T3
T3 F Conc West
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
T3 F Conc West
T3 F Conc West
T3 F Conc West
T3 F Conc West
T3 F Conc West
T3 F Conc East
T3 F Conc East
T3 F Conc East
T3 F Conc East
T3 F Conc East
T3 F Conc East
T3 E Conc West
T3 E Conc West
T3 E Conc West
T3 E Conc West
T3 E Conc West
Notes
T3 Gate F7
Nearest IDF
T3 Gate F6
Distribution Point
Fllight Info & Logo
Page 7 of 41
Protocol
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Fllight Info & Logo
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Displayed Data
Existing EVIDS Display Devices Inventory Sheet
Exhibit 3
Page 198 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Clock
Passenger Paging
Clock
Passenger Paging
Clock
Passenger Paging
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
LED
LED
Clock
280
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
NEC
NEC
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Clock
LED
Passenger Paging
277
Passenger Paging
LED
Clock
276
279
LED
278
LED
Clock
Passenger Paging
275
LED
273
274
LED
Clock
Passenger Paging
272
LED
LED
Bag Claim Informatiom
250
LED
LED
Bag Claim Informatiom
249
Clock
LED
Bag Claim Informatiom
248
Passenger Paging
LCD
Gate Airline Info Logo
247
271
LCD
Gate Airline Info Logo
246
270
Display Type
Use Description
Location
Ref. #
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Model #
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 8 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Time
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Psgr Info Scripts
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Time
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Serial
Flt Nbr Arrival Arpt
Protocol
Flt Nbr Arrival Arpt
Fllight Info & Logo
Fllight Info & Logo
Displayed Data
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
Distribution Point
T3-1061
T3-1061
T3-1061
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T3 Ticketing CS (Lantronix Server)
T3 Ticketing CN (Lantronix Server)
T3 Ticketing CN (Lantronix Server)
T3 Ticketing North (Lantronix Server)
T3 Ticketing North (Lantronix Server)
T3 Bag Claim North (Lantronix Server)
T3 Bag Claim North (Lantronix Server)
T3 BC CN Back (Lantronix Server)
T3 BC CN Back (Lantronix Server)
T3 BC CN Front (Lantronix Server)
T3 BC CN Front (Lantronix Server)
T3 BC CS Back (Lantronix Server)
T3 BC CS Back (Lantronix Server)
T3 BC CS Front (Lantronix Server)
T3 BC CS Front (Lantronix Server)
T3 Bag Claim South (Lantronix Server)
T3 Bag Claim South (Lantronix Server)
T3 Bag Claim #8 Back (Lantronix Server)
T3 Bag Claim #8 Front (Lantronix Server)
T3 Bag Claim #7 Back (Lantronix Server)
T3 Bag Claim #7 Front (Lantronix Server)
T3 Bag Claim #6 Back (Lantronix Server)
T3 Bag Claim #6 Front (Lantronix Server)
T3 Bag Claim #5 Back (Lantronix Server)
T3 Bag Claim #5 Front (Lantronix Server)
T3 Bag Claim #4 Back (Lantronix Server)
T3 Bag Claim #4 Front (Lantronix Server)
T3 Bag Claim #3 Back (Lantronix Server)
T3 Bag Claim #3 Front (Lantronix Server)
T3 Bag Claim #2 Back (Lantronix Server)
T3 Bag Claim #2 Front (Lantronix Server)
T3 Bag Claim #1 Back (Lantronix Server)
T3 Bag Claim #1 Front (Lantronix Server)
T3 Gate F10
T3 Gate F9
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 199 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
303
304
305
306
307
308
309
310
311
312
313
314
315
Daktronics
Daktronics
Daktronics
Daktronics
INFAX
INFAX
INFAX
INFAX
INFAX
INFAX
INFAX
INFAX
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Clock
Passenger Paging
302
LED
Passenger Paging
301
Passenger Paging
295
LED
LED
Clock
294
Clock
LED
Passenger Paging
293
300
LED
Clock
292
LED
LED
Passenger Paging
291
Passenger Paging
LED
Clock
290
299
LED
Passenger Paging
289
LED
LED
Clock
288
Clock
LED
Passenger Paging
287
298
LED
Clock
LED
LED
LED
Passenger Paging
285
286
LED
LED
Clock
284
Clock
LED
Passenger Paging
283
Passenger Paging
LED
Clock
282
297
LED
Passenger Paging
281
296
Display Type
Use Description
Location
Ref. #
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infax Built
Infax Built
Infax Built
Infax Built
Infax Built
Infax Built
Infax Built
Infax Built
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Model #
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Flight Input
Flight Input
Flight Input
Flight Input
Flight Input
Flight Input
Flight Input
Flight Input
Psgr Info Scripts
Time
Psgr Info Scripts
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 9 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Serial
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Serial
Protocol
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Displayed Data
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
Distribution Point
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1061
T3-1061
T3-1061
T3-1061
T3-1050A
T3-1050A
T3-1611
T3-1611
T3-1611
T3-1611
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1106
T3-1106
T3-1106
T3-1106
T3-1050B
T3-1050B
T3-1050A
T3-1050A
T3-1050B
T3-1050B
T3-1061
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T3 #4 TC Display (Lantronix Server)
T3 #3 TC Display (Lantronix Server)
T3 #2 TC Display (Lantronix Server)
T3 #1 TC Display (Lantronix Server)
T3 BTID Bag Claim #8 (Lantronix Server)
T3 BTID Bag Claim #7 (Lantronix Server)
T3 BTID Bag Claim #6 (Lantronix Server)
T3 BTID Bag Claim #5 (Lantronix Server)
T3 BTID Bag Claim #4 (Lantronix Server)
T3 BTID Bag Claim #3 (Lantronix Server)
T3 BTID Bag Claim #2 (Lantronix Server)
T3 BTID Bag Claim #1 (Lantronix Server)
T3 E Conc West Back (Lantronix Server)
T3 E Conc West Back (Lantronix Server)
T3 E Conc West Front (Lantronix Server)
T3 E Conc West Front (Lantronix Server)
T3 E Conc East Back (Lantronix Server)
T3 E Conc East Back (Lantronix Server)
T3 E Conc East Front (Lantronix Server)
T3 E Conc East Front (Lantronix Server)
T3 E Conc West Back (Lantronix Server)
T3 E Conc West Back (Lantronix Server)
T3 E Conc West Front (Lantronix Server)
T3 E Conc West Front (Lantronix Server)
T3 E Conc East Back (Lantronix Server)
T3 E Conc East Back (Lantronix Server)
T3 E Conc East Front (Lantronix Server)
T3 E Conc East Front (Lantronix Server)
T3 Conc F Check (Lantronix Server)
T3 Conc F Check (Lantronix Server)
T3 Conc E Check (Lantronix Server)
T3 Conc E Check (Lantronix Server)
T3 Ticketing South (Lantronix Server)
T3 Ticketing South (Lantronix Server)
T3 Ticketing CS (Lantronix Server)
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 200 of 278
Daktronics
Daktronics
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
LED
Ticket Counter Display
316
Manufacturer
Display Type
Use Description
Location
Ref. #
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 10 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Airline/Open/Closed
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
Distribution Point
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
T3-1050B
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T3 #39 TC Display (Lantronix Server)
T3 #38 TC Display (Lantronix Server)
T3 #37 TC Display (Lantronix Server)
T3 #36 TC Display (Lantronix Server)
T3 #35 TC Display (Lantronix Server)
T3 #34 TC Display (Lantronix Server)
T3 #33 TC Display (Lantronix Server)
T3 #32 TC Display (Lantronix Server)
T3 #31 TC Display (Lantronix Server)
T3 #30 TC Display (Lantronix Server)
T3 #29 TC Display (Lantronix Server)
T3 #28 TC Display (Lantronix Server)
T3 #27 TC Display (Lantronix Server)
T3 #26 TC Display (Lantronix Server)
T3 #25 TC Display (Lantronix Server)
T3 #24 TC Display (Lantronix Server)
T3 #23 TC Display (Lantronix Server)
T3 #22 TC Display (Lantronix Server)
T3 #21 TC Display (Lantronix Server)
T3 #20 TC Display (Lantronix Server)
T3 #19 TC Display (Lantronix Server)
T3 #18 TC Display (Lantronix Server)
T3 #17 TC Display (Lantronix Server)
T3 #16 TC Display (Lantronix Server)
T3 #15 TC Display (Lantronix Server)
T3 #14 TC Display (Lantronix Server)
T3 #13 TC Display (Lantronix Server)
T3 #12 TC Display (Lantronix Server)
T3 #11 TC Display (Lantronix Server)
T3 #10 TC Display (Lantronix Server)
T3 #9 TC Display (Lantronix Server)
T3 #8 TC Display (Lantronix Server)
T3 #7 TC Display (Lantronix Server)
T3 #6 TC Display (Lantronix Server)
T3 #5 TC Display (Lantronix Server)
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 201 of 278
Daktronics
Daktronics
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LCD
LCD
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Counter Airline Logo
Counter Airline Logo
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
NEC
NEC
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
LED
Ticket Counter Display
351
Manufacturer
Display Type
Use Description
Location
Ref. #
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Flight Info & Times
Flight Info & Times
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 11 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Airline/Open/Closed
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
Distribution Point
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1050A
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T2 Ticket Counter 3 & 4
T2 Ticket Counter 1 & 2
T3 #72 TC Display (Lantronix Server)
T3 #71 TC Display (Lantronix Server)
T3 #70 TC Display (Lantronix Server)
T3 #69 TC Display (Lantronix Server)
T3 #68 TC Display (Lantronix Server)
T3 #67 TC Display (Lantronix Server)
T3 #66 TC Display (Lantronix Server)
T3 #65 TC Display (Lantronix Server)
T3 #64 TC Display (Lantronix Server)
T3 #63 TC Display (Lantronix Server)
T3 #62 TC Display (Lantronix Server)
T3 #61 TC Display (Lantronix Server)
T3 #60 TC Display (Lantronix Server)
T3 #59 TC Display (Lantronix Server)
T3 #58 TC Display (Lantronix Server)
T3 #57 TC Display (Lantronix Server)
T3 #56 TC Display (Lantronix Server)
T3 #55 TC Display (Lantronix Server)
T3 #54 TC Display (Lantronix Server)
T3 #53 TC Display (Lantronix Server)
T3 #52 TC Display (Lantronix Server)
T3 #51 TC Display (Lantronix Server)
T3 #50 TC Display (Lantronix Server)
T3 #49 TC Display (Lantronix Server)
T3 #48 TC Display (Lantronix Server)
T3 #47 TC Display (Lantronix Server)
T3 #46 TC Display (Lantronix Server)
T3 #45 TC Display (Lantronix Server)
T3 #44 TC Display (Lantronix Server)
T3 #43 TC Display (Lantronix Server)
T3 #42 TC Display (Lantronix Server)
T3 #41 TC Display (Lantronix Server)
T3 #40 TC Display (Lantronix Server)
Notes
September 23, 2008
T2
T2
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 202 of 278
LCD
LCD
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Gate Airline Info Logo
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
NEC
NEC
NEC
NEC
NEC
NEC
NEC
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LCD
LCD
Counter Airline Logo
389
Counter Airline Logo
LCD
Counter Airline Logo
388
Gate Airline Info Logo
LCD
Counter Airline Logo
387
391
LCD
Counter Airline Logo
386
390
Display Type
Use Description
Location
Ref. #
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
LCD4010BK(A)-IT
Model #
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Fllight Info & Logo
Fllight Info & Logo
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Displayed Data
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Page 12 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Cat 5E
Cat 5E
TCP/IP
TCP/IP
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-2041B
T2-2041B
T2-1016
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
Nearest IDF
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
Distribution Point
Existing EVIDS Display Devices Inventory Sheet
T2 D Conc West (Extron TR/RC Used)
T2 D Conc East (Extron TR/RC Used)
T2 D Conc East (Extron TR/RC Used)
T2 D Conc East (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing West (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Ticketing East (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim West (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Bag Claim East (Extron TR/RC Used)
T2 Gate F4
T2 Gate F3
T2 Ticket Counter 1 3 & 14
T2 Ticket Counter 11 & 12
T2 Ticket Counter 9 & 10
T2 Ticket Counter 7 & 8
T2 Ticket Counter 5 & 6
Notes
September 23, 2008
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
Location
Exhibit B-1
Exhibit 3
Page 203 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Clock
Passenger Paging
Clock
Passenger Paging
426
427
428
429
430
431
432
433
434
435
LED
LED
LED
LED
Clock
Passenger Paging
Clock
Passenger Paging
452
453
454
455
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
INFAX
INFAX
INFAX
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
CRT
CRT
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Passenger Paging
449
LED
LED
Clock
Clock
LED
LED
Passenger Paging
447
448
Passenger Paging
LED
Clock
446
451
LED
450
LED
Clock
Passenger Paging
445
LED
444
LED
Clock
Passenger Paging
443
LED
442
LED
Clock
Passenger Paging
441
LED
439
440
LED
Clock
Passenger Paging
438
LED
LED
Bag Claim Informatiom
425
LED
LED
Bag Claim Informatiom
424
Clock
LED
Bag Claim Informatiom
423
Passenger Paging
CRT
EVIDS Flight Information
422
437
CRT
EVIDS Flight Information
421
436
Display Type
Use Description
Location
Ref. #
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Infax Built
Infax Built
Infax Built
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
CRT
CRT
Model #
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 13 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Time
Serial
Serial
Serial
Psgr Info Scripts
Psgr Info Scripts
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Time
Flight Input
Flight Input
Flight Input
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
TCP/IP
TCP/IP
Protocol
Flt Nbr Arrival Arpt
Flight Info & Times
Flight Info & Times
Displayed Data
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
Distribution Point
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1009A
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T2 D Conc FC West (Lantronix Server)
T2 D Conc FC West (Lantronix Server)
SPARE in Storage T4-1003
SPARE in Storage T4-1003
T2 D Check Back (Lantronix Server)
T2 D Check Back (Lantronix Server)
T2 D Check Front (Lantronix Server)
T2 D Check Front (Lantronix Server)
T2 Ticketing West (Lantronix Server)
T2 Ticketing West (Lantronix Server)
T2 TC Center Back (Lantronix Server)
T2 TC Center Back (Lantronix Server)
T2 TC Center Front (Lantronix Server)
T2 TC Center Front (Lantronix Server)
T2 Ticketing East (Lantronix Server)
T2 Ticketing East (Lantronix Server)
T2 Bag Claim West (Lantronix Server)
T2 Bag Claim West (Lantronix Server)
T2 BC Center Back (Lantronix Server)
T2 BC Center Back (Lantronix Server)
T2 BC Center Front (Lantronix Server)
T2 BC Center Front (Lantronix Server)
T2 Bag Claim East (Lantronix Server)
T2 Bag Claim East (Lantronix Server)
T2 BTID Bag Claim #3 (Lantronix Server)
T2 BTID Bag Claim #2 (Lantronix Server)
T2 BTID Bag Claim #1 (Lantronix Server)
T2 Bag Claim #3 Back (Lantronix Server)
T2 Bag Claim #3 Front (Lantronix Server)
T2 Bag Claim #2 Back (Lantronix Server)
T2 Bag Claim #2 Front (Lantronix Server)
T2 Bag Claim #1 Back (Lantronix Server)
T2 Bag Claim #1 Front (Lantronix Server)
T2 D Conc West (Extron TR/RC Used)
T2 D Conc West (Extron TR/RC Used)
Notes
September 23, 2008
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
Location
Exhibit B-1
Exhibit 3
Page 204 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Clock
Passenger Paging
463
LED
462
LED
Clock
LED
Passenger Paging
459
Passenger Paging
LED
Clock
458
461
LED
457
460
LED
Clock
Passenger Paging
456
Display Type
Use Description
Location
Ref. #
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Model #
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Psgr Info Scripts
Time
Psgr Info Scripts
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
Cat 5E
Cat 5E
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
Distribution Point
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 14 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Protocol
Time
Psgr Info Scripts
Time
Displayed Data
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
T2-1059
T2-1059
T2-1009A
T2-1009A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T2 #27 TC Display (Lantronix Server)
T2 #26 TC Display (Lantronix Server)
T2 #25 TC Display (Lantronix Server)
T2 #24 TC Display (Lantronix Server)
T2 #23 TC Display (Lantronix Server)
T2 #22 TC Display (Lantronix Server)
T2 #21 TC Display (Lantronix Server)
T2 #20 TC Display (Lantronix Server)
T2 #19 TC Display (Lantronix Server)
T2 #18 TC Display (Lantronix Server)
T2 #17 TC Display (Lantronix Server)
T2 #16 TC Display (Lantronix Server)
T2 #15 TC Display (Lantronix Server)
T2 #14 TC Display (Lantronix Server)
T2 #13 TC Display (Lantronix Server)
T2 #12 TC Display (Lantronix Server)
T2 #11 TC Display (Lantronix Server)
T2 #10 TC Display (Lantronix Server)
T2 #9 TC Display (Lantronix Server)
T2 #8 TC Display (Lantronix Server)
T2 #7 TC Display (Lantronix Server)
T2 #6 TC Display (Lantronix Server)
T2 #5 TC Display (Lantronix Server)
T2 #4 TC Display (Lantronix Server)
T2 #3 TC Display (Lantronix Server)
T2 #2 TC Display (Lantronix Server)
T2 #1 TC Display (Lantronix Server)
T2 D Conc D9 (Lantronix Server)
T2 D Conc D9 (Lantronix Server)
T2 D Conc D6 (Lantronix Server)
T2 D Conc D6 (Lantronix Server)
T2 D Conc D4 (Lantronix Server)
T2 D Conc D4 (Lantronix Server)
T2 D Conc D2 (Lantronix Server)
T2 D Conc D2 (Lantronix Server)
Notes
September 23, 2008
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
Location
Exhibit B-1
Exhibit 3
Page 205 of 278
CRT
CRT
LED
LED
LED
LED
LED
LED
LCD
LCD
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Dell
Dell
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
LED
Ticket Counter Display
491
Manufacturer
Display Type
Use Description
Location
Ref. #
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
CRT
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
17" Moniror
17" Moniror
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 15 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
T1-3155
T1-3155
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1010
T1-1010
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
Distribution Point
T1-3155
T1-3155
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1010
T1-1010
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 Ticketing East (Extron TR/RC Used)
T1 Ticketing East (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance West (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Entrance East (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim West (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 Bag Claim East (Extron TR/RC Used)
T1 P Club
T1 P Club
T2 #34 TC Display (Lantronix Server)
T2 #33 TC Display (Lantronix Server)
T2 #32 TC Display (Lantronix Server)
T2 #31 TC Display (Lantronix Server)
T2 #30 TC Display (Lantronix Server)
T2 #29 TC Display (Lantronix Server)
T2 #28 TC Display (Lantronix Server)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T2
T2
T2
T2
T2
T2
T2
Location
Exhibit B-1
Exhibit 3
Page 206 of 278
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
Gate Airline Logo
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
EVIDS Flight Information
526
Manufacturer
Display Type
Use Description
Location
Ref. #
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Airline Logo
CRT
Flight Info & Times
CRT
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Displayed Data
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
CRT
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 16 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1010
T1-1010
T1-1010
T1-1010
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3155
T1-3155
T1-3155
T1-3155
Distribution Point
T1-1010
T1-1010
T1-1010
T1-1010
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3155
T1-3155
T1-3155
T1-3155
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 Gate C4 (Extron TR/RC Used)
T1 Gate C3 (Extron TR/RC Used)
T1 Gate C2 (Extron TR/RC Used)
T1 Gate C1 (Extron TR/RC Used)
T1 Gate B9 (Extron TR/RC Used)
T1 Gate B8 (Extron TR/RC Used)
T1 Gate B7 (Extron TR/RC Used)
T1 Gate B6 (Extron TR/RC Used)
T1 Gate B5 (Extron TR/RC Used)
T1 Gate B4 (Extron TR/RC Used)
T1 Gate B3 (Extron TR/RC Used)
T1 Gate B2 (Extron TR/RC Used)
T1 Gate B1 (Extron TR/RC Used)
T1 C Conc South (Extron TR/RC Used)
T1 C Conc South (Extron TR/RC Used)
T1 C Conc South (Extron TR/RC Used)
T1 C Conc North (Extron TR/RC Used)
T1 C Conc North (Extron TR/RC Used)
T1 C Conc North (Extron TR/RC Used)
T1 B Conc South (Extron TR/RC Used)
T1 B Conc South (Extron TR/RC Used)
T1 B Conc South (Extron TR/RC Used)
T1 B Conc North (Extron TR/RC Used)
T1 B Conc North (Extron TR/RC Used)
T1 B Conc North (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing West (Extron TR/RC Used)
T1 Ticketing East (Extron TR/RC Used)
T1 Ticketing East (Extron TR/RC Used)
T1 Ticketing East (Extron TR/RC Used)
T1 Ticketing East (Extron TR/RC Used)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 207 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Bag Claim Informatiom
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
Baggage Tug Input
571
572
573
574
575
576
577
578
579
580
581
LED
LED
LED
LED
Clock
Passenger Paging
Clock
Passenger Paging
592
593
594
595
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
INFAX
INFAX
INFAX
INFAX
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
CRT
CRT
CRT
CRT
CRT
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Passenger Paging
589
LED
LED
Clock
Clock
LED
LED
Passenger Paging
587
588
Passenger Paging
LED
Clock
586
591
LED
585
590
LED
Clock
Passenger Paging
584
LED
LED
Bag Claim Informatiom
570
LED
LED
Bag Claim Informatiom
569
Clock
LED
Bag Claim Informatiom
568
Passenger Paging
LED
Bag Claim Informatiom
567
583
LED
582
CRT
CRT
Gate Airline Logo
564
Gate Airline Logo
CRT
Gate Airline Logo
563
Bag Claim Informatiom
CRT
Gate Airline Logo
562
566
CRT
Gate Airline Logo
561
565
Display Type
Use Description
Location
Ref. #
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Infax Built
Infax Built
Infax Built
Infax Built
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
Galaxy 32X192 Tri
CRT
CRT
CRT
CRT
CRT
Model #
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 17 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Time
Serial
Serial
Serial
Serial
Serial
Psgr Info Scripts
Flight Input
Flight Input
Flight Input
Flight Input
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
Flt Nbr Arrival Arpt
Serial
Flt Nbr Arrival Arpt
Serial
Serial
Flt Nbr Arrival Arpt
TCP/IP
Airline Logo
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
Flt Nbr Arrival Arpt
Airline Logo
Airline Logo
Airline Logo
Airline Logo
Displayed Data
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Distribution Point
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1302
T1-1302
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 Ticketing West (Lantronix Server)
T1 Ticketing West (Lantronix Server)
T1 TC East Back (Lantronix Server)
T1 TC East Back (Lantronix Server)
T1 TC East Front (Lantronix Server)
T1 TC East Front (Lantronix Server)
T1 Entr West Back (Lantronix Server)
T1 Entr West Back (Lantronix Server)
T1 Entr East Front (Lantronix Server)
T1 Entr East Front (Lantronix Server)
T1 BC West Back (Lantronix Server)
T1 BC West Back (Lantronix Server)
T1 BC East Front (Lantronix Server)
T1 BC East Front (Lantronix Server)
T1 BTID Bag Claim #4 (Lantronix Server)
T1 BTID Bag Claim #3 (Lantronix Server)
T1 BTID Bag Claim #2 (Lantronix Server)
T1 BTID Bag Claim #1 (Lantronix Server)
T1 Bag Claim #6 Back (Lantronix Server)
T1 Bag Claim #6Back (Lantronix Server)
T1 Bag Claim #5 Back (Lantronix Server)
T1 Bag Claim #5 Front (Lantronix Server)
T1 Bag Claim #4 Back (Lantronix Server)
T1 Bag Claim #4 Front (Lantronix Server)
T1 Bag Claim #3 Back (Lantronix Server)
T1 Bag Claim #3 Front (Lantronix Server)
T1 Bag Claim #2 Back (Lantronix Server)
T1 Bag Claim #2 Front (Lantronix Server)
T1 Bag Claim #1 Back (Lantronix Server)
T1 Bag Claim #1 Front (Lantronix Server)
T1 Gate C9 (Extron TR/RC Used)
T1 Gate C8 (Extron TR/RC Used)
T1 Gate C7 (Extron TR/RC Used)
T1 Gate C6 (Extron TR/RC Used)
T1 Gate C5 (Extron TR/RC Used)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 208 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Clock
Passenger Paging
Clock
Passenger Paging
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LED
Passenger Paging
613
LED
LED
Clock
Clock
LED
LED
Passenger Paging
611
612
Passenger Paging
LED
Clock
610
615
LED
614
LED
Clock
Passenger Paging
609
LED
608
LED
Clock
Passenger Paging
607
LED
606
LED
Clock
Passenger Paging
605
LED
604
LED
Clock
Passenger Paging
603
LED
602
LED
Clock
LED
Passenger Paging
599
Passenger Paging
LED
Clock
598
601
LED
597
600
LED
Clock
Passenger Paging
596
Display Type
Use Description
Location
Ref. #
Serial
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 18 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Serial
Serial
Serial
Time
Serial
Psgr Info Scripts
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Serial
Time
Psgr Info Scripts
Time
Psgr Info Scripts
Time
Serial
Serial
Time
Serial
Serial
Serial
Psgr Info Scripts
Psgr Info Scripts
Time
Psgr Info Scripts
Serial
Serial
Psgr Info Scripts
Time
Serial
Serial
Serial
Protocol
Time
Psgr Info Scripts
Time
Displayed Data
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Galaxy 48X160 Tri
Galaxy 16X64 Tri
Model #
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 Jet Bridge B2 (Lantronix Server)
T1 Jet Bridge B1 (Lantronix Server)
T1 Gate B9 (Lantronix Server)
T1 Gate B8 (Lantronix Server)
T1 Gate B7 (Lantronix Server)
T1 Gate B6 (Lantronix Server)
T1 Gate B5 (Lantronix Server)
T1 Gate B4 (Lantronix Server)
T1 Gate B3 (Lantronix Server)
T1 Gate B2 (Lantronix Server)
T1 Gate B1 (Lantronix Server)
T1 B Conc North Back (Lantronix Server)
T1 B Conc North Back (Lantronix Server)
T1 B Conc North Front (Lantronix Server)
T1 B Conc North Front (Lantronix Server)
T1 B Conc South Back (Lantronix Server)
T1 B Conc South Back (Lantronix Server)
T1 B Conc South Front (Lantronix Server)
T1 B Conc South Front (Lantronix Server)
T1 B Check Back (Lantronix Server)
T1 B Check Back (Lantronix Server)
T1 B Check Front (Lantronix Server)
T1 B Check Front (Lantronix Server)
T1 C Conc North Back (Lantronix Server)
T1 C Conc North Back (Lantronix Server)
T1 C Conc North Front (Lantronix Server)
T1 C Conc North Front (Lantronix Server)
T1 C Conc South Back (Lantronix Server)
T1 C Conc South Back (Lantronix Server)
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
September 23, 2008
T1 C Conc South Front (Lantronix Server)
T1 C Conc South Front (Lantronix Server)
T1 C Check Back (Lantronix Server)
T1 C Check Back (Lantronix Server)
T1 C Check Front (Lantronix Server)
T1 C Check Front (Lantronix Server)
Notes
Exhibit B-1
Exhibit 3
Page 209 of 278
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Flt Departure Information
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Displayed Data
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 19 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Galaxy 64X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Serial
Serial
Serial
Protocol
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Galaxy 48X160 Tri Gate/Flt# Dest/Time
Model #
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 #10 TC Display (Lantronix Server)
T1 #9 TC Display (Lantronix Server)
T1 #8 TC Display (Lantronix Server)
T1 #7 TC Display (Lantronix Server)
T1 #6 TC Display (Lantronix Server)
T1 #5 TC Display (Lantronix Server)
T1 #4 TC Display (Lantronix Server)
T1 #3 TC Display (Lantronix Server)
T1 #2 TC Display (Lantronix Server)
T1 #1 TC Display (Lantronix Server)
T1 Jet BridgE C9 (Lantronix Server)
T1 Jet BridgE C8 (Lantronix Server)
T1 Jet BridgE C7 (Lantronix Server)
T1 Jet BridgE C6 (Lantronix Server)
T1 Jet BridgE C5 (Lantronix Server)
T1 Jet BridgE C4 (Lantronix Server)
T1 Jet BridgE C3 (Lantronix Server)
T1 Jet BridgE C2 (Lantronix Server)
T1 Jet BridgE C1 (Lantronix Server)
T1 GatE C9 (Lantronix Server)
T1 GatE C8 (Lantronix Server)
T1 GatE C7 (Lantronix Server)
T1 GatE C6 (Lantronix Server)
T1 GatE C5 (Lantronix Server)
T1 GatE C4 (Lantronix Server)
T1 GatE C3 (Lantronix Server)
T1 GatE C2 (Lantronix Server)
T1 GatE C1 (Lantronix Server)
T1 Jet Bridge B9 (Lantronix Server)
T1 Jet Bridge B8 (Lantronix Server)
T1 Jet Bridge B7 (Lantronix Server)
T1 Jet Bridge B6 (Lantronix Server)
T1 Jet Bridge B5 (Lantronix Server)
T1 Jet Bridge B4 (Lantronix Server)
T1 Jet Bridge B3 (Lantronix Server)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 210 of 278
Daktronics
Daktronics
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
LED
Ticket Counter Display
666
Manufacturer
Display Type
Use Description
Location
Ref. #
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 20 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Airline/Open/Closed
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
T1-3155
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 #45 TC Display (Lantronix Server)
T1 #44 TC Display (Lantronix Server)
T1 #43 TC Display (Lantronix Server)
T1 #42 TC Display (Lantronix Server)
T1 #41 TC Display (Lantronix Server)
T1 #40 TC Display (Lantronix Server)
T1 #39 TC Display (Lantronix Server)
T1 #38 TC Display (Lantronix Server)
T1 #37 TC Display (Lantronix Server)
T1 #36 TC Display (Lantronix Server)
T1 #35 TC Display (Lantronix Server)
T1 #34 TC Display (Lantronix Server)
T1 #33 TC Display (Lantronix Server)
T1 #32 TC Display (Lantronix Server)
T1 #31 TC Display (Lantronix Server)
T1 #30 TC Display (Lantronix Server)
T1 #29 TC Display (Lantronix Server)
T1 #28 TC Display (Lantronix Server)
T1 #27 TC Display (Lantronix Server)
T1 #26 TC Display (Lantronix Server)
T1 #25 TC Display (Lantronix Server)
T1 #24 TC Display (Lantronix Server)
T1 #23 TC Display (Lantronix Server)
T1 #22 TC Display (Lantronix Server)
T1 #21 TC Display (Lantronix Server)
T1 #20 TC Display (Lantronix Server)
T1 #19 TC Display (Lantronix Server)
T1 #18 TC Display (Lantronix Server)
T1 #17 TC Display (Lantronix Server)
T1 #16 TC Display (Lantronix Server)
T1 #15 TC Display (Lantronix Server)
T1 #14 TC Display (Lantronix Server)
T1 #13 TC Display (Lantronix Server)
T1 #12 TC Display (Lantronix Server)
T1 #11 TC Display (Lantronix Server)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 211 of 278
Daktronics
Daktronics
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
LED
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
Ticket Counter Display
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
LED
Ticket Counter Display
701
Manufacturer
Display Type
Use Description
Location
Ref. #
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 21 of 41
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Airline/Open/Closed
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1 #80 TC Display (Lantronix Server)
T1 #79 TC Display (Lantronix Server)
T1 #78 TC Display (Lantronix Server)
T1 #77 TC Display (Lantronix Server)
T1 #76 TC Display (Lantronix Server)
T1 #75 TC Display (Lantronix Server)
T1 #74 TC Display (Lantronix Server)
T1 #73 TC Display (Lantronix Server)
T1 #72 TC Display (Lantronix Server)
T1 #71 TC Display (Lantronix Server)
T1 #70 TC Display (Lantronix Server)
T1 #69 TC Display (Lantronix Server)
T1 #68 TC Display (Lantronix Server)
T1 #67 TC Display (Lantronix Server)
T1 #66 TC Display (Lantronix Server)
T1 #65 TC Display (Lantronix Server)
T1 #64 TC Display (Lantronix Server)
T1 #63 TC Display (Lantronix Server)
T1 #62 TC Display (Lantronix Server)
T1 #61 TC Display (Lantronix Server)
T1 #60 TC Display (Lantronix Server)
T1 #59 TC Display (Lantronix Server)
T1 #58 TC Display (Lantronix Server)
T1 #57 TC Display (Lantronix Server)
T1 #56 TC Display (Lantronix Server)
T1 #55 TC Display (Lantronix Server)
T1 #54 TC Display (Lantronix Server)
T1 #53 TC Display (Lantronix Server)
T1 #52 TC Display (Lantronix Server)
T1 #51 TC Display (Lantronix Server)
T1 #50 TC Display (Lantronix Server)
T1 #49 TC Display (Lantronix Server)
T1 #48 TC Display (Lantronix Server)
T1 #47 TC Display (Lantronix Server)
T1 #46 TC Display (Lantronix Server)
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 212 of 278
LCD
LCD
LCD
LED
LED
LCD
LCD
LCD
LCD
LCD
LED
LCD
LCD
LCD
LCD
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
CLOCK
CLOCK
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
CLOCK
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
NEC
NEC
NEC
NEC
Daktronics
NEC
NEC
NEC
NEC
NEC
Daktronics
Daktronics
NEC
NEC
NEC
NEC
NEC
NEC
NEC
Daktronics
NEC
NEC
NEC
NEC
NEC
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
LCD
EVIDS Flight Information
LCD
EVIDS Flight Information
750
755
LCD
EVIDS Flight Information
749
LCD
LCD
EVIDS Flight Information
748
EVIDS Flight Information
LCD
EVIDS Flight Information
747
754
LCD
EVIDS Flight Information
746
LCD
LCD
EVIDS Flight Information
745
EVIDS Flight Information
LCD
EVIDS Flight Information
744
753
LED
Ticket Counter Display
743
LCD
LED
Ticket Counter Display
742
LED
LED
Ticket Counter Display
741
CLOCK
LED
Ticket Counter Display
740
EVIDS Flight Information
LED
Ticket Counter Display
739
752
NEC
LED
Ticket Counter Display
738
751
NEC
LED
Ticket Counter Display
737
Daktronics
LED
Ticket Counter Display
736
Manufacturer
Display Type
Use Description
Location
Ref. #
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
Galaxy 16X64 Tri
LCD4010BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
Galaxy 16X64 Tri
Galaxy 16X64 Tri
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
Galaxy 16X64 Tri
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Infonet 7x120 Mono
Model #
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
VPD
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 22 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
VPD
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Serial
Protocol
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
VPD
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Airline/Open/Closed
Displayed Data
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
T1
T1
T1
T1
T1
T1
T1
T1
Location
September 23, 2008
RCC 3nd Level West (Extron TR/RC Used)
RCC 3nd Level West (Extron TR/RC Used)
RCC 3nd Level West (Extron TR/RC Used)
RCC 3nd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3nd Level East (Extron TR/RC Used)
RCC 3nd Level East (Extron TR/RC Used)
RCC 3nd Level East (Extron TR/RC Used)
RCC 3nd Level East (Extron TR/RC Used)
RCC 3nd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
T1 #88 TC Display (Lantronix Server)
T1 #87 TC Display (Lantronix Server)
T1 #86 TC Display (Lantronix Server)
T1 #85 TC Display (Lantronix Server)
T1 #84 TC Display (Lantronix Server)
T1 #83 TC Display (Lantronix Server)
T1 #82 TC Display (Lantronix Server)
T1 #81 TC Display (Lantronix Server)
Notes
Exhibit B-1
Exhibit 3
Page 213 of 278
Infocus
Infocus
LED
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
LCD
CLOCK
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
EVIDS Flight Information
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
Directory
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
Infocus
NEC
NEC
NEC
NEC
NEC
Daktronics
NEC
LCD
EVIDS Flight Information
771
Manufacturer
Display Type
Use Description
Location
Ref. #
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
30" Infocus
LCD4010BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
LCD4000BK(A)-IT
Galaxy 16X64 Tri
LCD4000BK(A)-IT
Model #
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 23 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Airline/Rental Car info
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
VPD
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Flight Info & Times
Displayed Data
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
Distribution Point
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
Location
September 23, 2008
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 9th Level East (Extron TR/RC Used)
RCC 8th Level East (Extron TR/RC Used)
RCC 7th Level East (Extron TR/RC Used)
RCC 6th Level East (Extron TR/RC Used)
RCC 5th Level East (Extron TR/RC Used)
RCC 4thd Level East (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2ndd Level West (Extron TR/RC Used)
RCC 2nd Level Center (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2rd Level West (Extron TR/RC Used)
RCC 3nd Level West (Extron TR/RC Used)
Notes
Exhibit B-1
Exhibit 3
Page 214 of 278
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW
AIW-ContinentalBC
AIW-Continental
AIW-Frontier
AIW-HudsonGeneral
AIW-JetBlue
AIW-NortwestOps
AIW-NortwestTC
AIW-Spirit
AIW-USAirways
INT-American
INT-Delta
INT-Southwest
829
830
831
832
833
834
835
836
837
838
839
840
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
Philips
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
AIW
AIW-CommCtr
AIW-Commuter
828
AIW
AIW-Cayman
826
827
AIW
AIW-BCADOps
AIW
AIW-AirJamaica
820
825
AIW
AIW-AirCanada
819
AIW
LCD
Directory
818
AIW-BahamasAir
LCD
Directory
817
824
LCD
Directory
816
AIW
LCD
Directory
815
AIW-American
LCD
Directory
814
823
LCD
Directory
813
AIW
LCD
Directory
812
AIW
LCD
Directory
811
AIW-AirTran
LCD
Directory
810
AIW-AirTranSat
LCD
Directory
809
822
LCD
Directory
808
821
Philips
Philips
LCD
Directory
807
Philips
LCD
Directory
806
Manufacturer
Display Type
Use Description
Location
Ref. #
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
GX110
Airline Flifo Input
GX110
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Airline/Rental Car info
Displayed Data
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
GX110
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
20" Brillance
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 24 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1666
T2-1059
T3-1061
T3-1133B
T4-1034B
T1-3104
T1-1010
T1-1010
T4-1036N
T1-3155
T1-1010
T1-1114
T4-2041A
FS-Comp-Rm
T4-2041A
T4-2213
T3-2054
T3-1611
T4-2041A
T3-1106
T4-2041A
T2-1059
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
Distribution Point
T1-1666
T2-1059
T3-1061
T3-1133B
T4-1034B
T1-3104
T1-1010
T1-1010
T4-1036N
T1-3155
T1-1010
T1-1114
T4-2041A
FS-Comp-Rm
T4-2041A
T4-2213
T3-2054
T3-1611
T4-2041A
T3-1106
T4-2041A
T2-1059
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1-Southwest Opeartions Office
T2-1062
T3-2114
T3-1117
T4-1036A
T1-Northwest Ticket Office
T1-1020
T1-JetBlue Operations Office
T4-1059
T1-Frontier Ticket Office
T1-Continental Operations Office
T1-1115
T4-Commuter Counter
FS-Comm Center
T4-2011
BCAD Admin Ops Office
T3-2057
T3-1709
T4-2010E
T3-1005
T4-2030B
T2-1053A
T1
T2
T3
T3
T4
T1
T1
T1
T1
T1
T1
T1
T4
CC
T4
Admin
T3
T3
T4
T4
T4
T2
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
Location
September 23, 2008
RCC 9th Level West (Extron TR/RC Used)
RCC 8th Level West (Extron TR/RC Used)
RCC 8th Level West (Extron TR/RC Used)
RCC 7th Level West (Extron TR/RC Used)
RCC 7th Level West (Extron TR/RC Used)
RCC 6th Level West (Extron TR/RC Used)
RCC 6th Level West (Extron TR/RC Used)
RCC 5th Level West (Extron TR/RC Used)
RCC 5th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
Notes
Exhibit B-1
Exhibit 3
Page 215 of 278
Dell
Dell
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
T1-1010-02-6CH
T1-1010-03-6CH
T1-1114-01-6CH
T1-1114-02-6CH
T1-1302-01-6CH
T1-1302-02-6CH
T1-1666-01-6CH
T1-1666-02-6CH
T1-1666-03-6CH
T1-3104-01-6CH
T1-3155-01-6CH
T2-2041B-01-6CH
T2-1016-01-6CH
T2-1059-01-6CH
DVC-T2CD-G3
DVC-T2CD-G4
DVC-T2L2-P1
DVC-T2L2-P2
DVC-T2L2-P3
DVC-T2L2-P4
DVC-T2L2-P5
DVC-T2L2-P6
DVC-T2L2-P7
DVC-T3L1N-A1
DVC-T3L1N-A2
DVC-T3L1N-A3
DVC-T3L1N-D1
DVC-T3L1N-D2
DVC-T3L1N-D3
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
DVC
Dell
DVC
DVC
T1-PCLUB-01
844
Dell
T1-PCLUB-02
AIW
CUSTOMS-3
843
Dell
Dell
T1-1010-01-6CH
AIW
CUSTOMS-2
842
846
AIW
CUSTOMS-1
841
Manufacturer
845
Display Type
Use Description
Location
Ref. #
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Airline Flifo Input
Airline Flifo Input
Airline Flifo Input
Displayed Data
V90
V90
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
GX110
GX110
Dell 620
Dell 620
Dell 620
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 25 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
T2-1059
T2-1016
T2-2041B
T1-3155
T1-3104
T1-1666
T1-1666
T1-1666
T1-1302
T1-1302
T1-1114
T1-1114
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-1034B
T4-2213
T4-2213
Distribution Point
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1059
T2-1059
T2-1059
T2-1016
T2-2041B
T1-3155
T1-3104
T1-1666
T1-1666
T1-1666
T1-1302
T1-1302
T1-1114
T1-1114
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-3104
T4-2213
T4-2213
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
Ticket Counter Plasma
Ticket Counter Plasma
Ticket Counter Plasma
Ticket Counter Plasma
Ticket Counter Plasma
Ticket Counter Plasma
Ticket Counter Plasma
Concourse D Gate 4
Concourse D Gate 3
Concourse D Kiosks
West Bag Claim & Ticketing Kiosks
East Bag Claim & Ticketing Kiosks
East Ticketing Level Kiosk
West Ticketing Level Kiosk
Concourse B Gates 7-9
Concourse B Gates 1-6
Concourse B Kiosks
East Bag Claim Kiosk
East Entrance Kiosk
West Bag Claim Kiosk
West Entrance Kiosk
Concourse C Gates 7-9
Concourse C Gates 1-6
Concourse C Kiosks
T1-P Club
T1-P Club
Customs Office under H Concouse
Customs Office
Customs Office
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 216 of 278
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC-T3L2C-A2
DVC-T3L2C-A3
DVC-T3L2C-D1
DVC-T3L2C-D2
DVC-T3L2C-D3
DVC-T3CFE-A1
DVC-T3CFE-A2
895
896
897
898
899
900
901
DVC
DVC
DVC-T3CFW-D2
909
910
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
DVC
DVC-T3CFW-A3
DVC-T3CFW-D1
908
DVC
DVC
DVC-T3L2C-A1
894
DVC-T3CFW-A2
DVC
DVC-T3L2S-D3
893
907
DVC
DVC-T3L2S-D2
892
DVC
DVC
DVC-T3L2S-D1
891
DVC-T3CFW-A1
DVC
DVC-T3L2S-A3
890
906
DVC
DVC-T3L2S-A2
889
DVC
DVC
DVC-T3L2S-A1
888
DVC-T3CFE-D3
DVC
DVC-T3L1S-D3
887
905
DVC
DVC-T3L1S-D2
886
DVC
DVC
DVC-T3L1S-D1
885
DVC-T3CFE-D2
DVC
DVC-T3L1S-A3
884
904
DVC
DVC-T3L1S-A2
883
DVC
DVC
DVC-T3L1S-A1
882
DVC
DVC
DVC-T3L2N-D3
881
DVC-T3CFE-A3
DVC
DVC-T3L2N-D2
880
DVC-T3CFE-D1
DVC
DVC-T3L2N-D1
879
903
Wyse
DVC
DVC-T3L2N-A3
878
902
Wyse
DVC
DVC-T3L2N-A2
877
Wyse
DVC
DVC-T3L2N-A1
876
Manufacturer
Display Type
Use Description
Location
Ref. #
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Displayed Data
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 26 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
Distribution Point
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-1073A
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
T3-2054
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Concourse F Kiosks
Ticketing Center Kiosks
Ticketing Center Kiosks
Ticketing Center Kiosks
Ticketing Center Kiosks
Ticketing Center Kiosks
Ticketing Center Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
South Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
North Bag Claim & Ticketing Kiosks
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 217 of 278
Wyse
Wyse
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC-T3CF-G1
DVC-T3CF-G2
DVC-T3CF-G3
DVC-T3CF-G4
DVC-T3CF-G5
DVC-T3CF-G6
DVC-T3CF-G7
DVC-T3CF-G8
DVC-T3CF-G9
DVC-T3CF-G10
DVC-T3CEE-A1
DVC-T3CEE-A2
DVC-T3CEE-A3
DVC-T3CEE-D1
DVC-T3CEE-D2
DVC-T3CEE-D3
DVC-T3CEW-A1
DVC-T3CEW-A2
DVC-T3CEW-A3
DVC-T3CEW-D1
DVC-T3CEW-D2
DVC-T3CEW-D3
DVC-T3CE-G1
DVC-T3CE-G2
DVC-T3CE-G3
DVC-T3CE-G4
DVC-T3CE-G5
DVC-T3CE-G6
DVC-T3CE-G7
DVC-T3CE-G8
DVC-T3CE-G9
DVC-T3CE-G10
DVC-T3L2-P2
DVC-T3L2-P3
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
Wyse
DVC
DVC-T3CFW-D3
911
Manufacturer
Display Type
Use Description
Location
Ref. #
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
V90
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Displayed Data
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
V90
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 27 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T3-2079A
T3-2079A
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1611
T3-1611
T3-1611
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
Distribution Point
T3-2079A
T3-2079A
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1133B
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1106A
T3-1611
T3-1611
T3-1611
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
T3-1308A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Ticket Counter Plasma
Ticket Counter Plasma
Concourse E Gate 10
Concourse E Gate 9
Concourse E Gate 8
Concourse E Gate 7
Concourse E Gate 6
Concourse E Gate 5
Concourse E Gate 4
Concourse E Gate 3
Concourse E Gate 2
Concourse E Gate 1
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse E Kiosks
Concourse F Gate 10
Concourse F Gate 9
Concourse F Gate 8
Concourse F Gate 7
Concourse F Gate 6
Concourse F Gate 5
Concourse F Gate 4
Concourse F Gate 3
Concourse F Gate 2
Concourse F Gate 1
Concourse F Kiosks
Notes
September 23, 2008
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
T3
Location
Exhibit B-1
Exhibit 3
Page 218 of 278
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Wyse
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Wyse
Wyse
Wyse
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Dell
Wyse
Wyse
Wyse
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
DVC
RAC-232B-4CH-02
980
DVC
RAC-232A-DVC-01
971
DVC
DVC
RAC-232A-4CH-02
970
RAC-232B-4CH-01
DVC
RAC-232A-4CH-01
969
979
DVC
RAC-232A-1CH-06
968
DVC
DVC
RAC-232A-1CH-05
967
RAC-232B-1CH-06
DVC
RAC-232A-1CH-04
966
978
DVC
RAC-232A-1CH-03
965
DVC
DVC
RAC-232A-1CH-02
964
RAC-232B-1CH-05
DVC
RAC-232A-1CH-01
963
977
DVC
DVC-T4L1-CUSB
962
DVC
DVC
DVC-T4L1-CUSA
961
RAC-232B-1CH-04
DVC
Bagrecheck
960
976
DVC
T4-BRC-01-4CH
959
DVC
DVC
T4-2213-08-6CH
958
RAC-232B-1CH-03
DVC
T4-2213-06-6CH
957
975
DVC
T4-2213-05-6CH
956
DVC
DVC
T4-2213-04-6CH
955
RAC-232B-1CH-02
DVC
T4-2213-03-6CH
954
974
DVC
T4-2213-02-6CH
953
DVC
DVC
T4-1036N-01-6CH
952
DVC
DVC
T4-1034B-02-6CH
951
DVC-RACL2-V1
DVC
T4-1034B-01-6CH
950
RAC-232B-1CH-01
DVC
DVC-T3-L2-CLUB4
949
973
Dell
DVC
DVC-T3-L2-CLUB3
948
972
Dell
DVC
DVC-T3-L2-CLUB2
Wyse
DVC
DVC-T3-L2-CLUB1
946
947
Manufacturer
Display Type
Use Description
Location
Ref. #
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
V90
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
Dell 280
V90
V90
V90
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
Dell 240
V90
V90
V90
V90
Model #
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Displayed Data
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 28 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
T4-2213
T4-2213
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1034B
T4-1034B
T3-2054
T3-2054
T3-2054
T3-2054
Distribution Point
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
T4-2213
T4-2213
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1034B
T4-1034B
T3-2054
T3-2054
T3-2054
T32054
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Fids East side 5-6 screens 3rd floor
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T3
T3
T3
T3
Location
September 23, 2008
Fids East side 1-4 screens 2nd and 3rd floor
Dir Podium 4th floor
DIR Podium 2nd floor
ELV DIR East side 8th and 9th floor
ELV DIR East side 6th and 7th floor
ELV DIR East side 4th and 5th floor
VP 2nd floor
ELV DIR East side 2nd and 3rd floor
VP 2nd and 3rd floor
Fids West side 5-6 screens 3rd floor
Fids West side 1-4 screens 2nd and 3rd floor
DIR Podium 4th floor
DIR Podium 2nd floor
ELV DIR West side 8th and 9th floor
ELV DIR West side 6th and 7th floor
ELV DIR West side 4th and 5th floor
Customs, Bag Claim
ELV DIR West side 2nd and 3rd floor
Customs, Bag Claim
FIS Ticket Counter LCD 2
FIS Ticket Counter LCD 1-3-4-5
Customs, Bag Claim, Ticketing Kiosks
Ticket Counter LCD 25-27
Ticket Counter LCD 19-24
Ticket Counter LCD 13-18
Ticket Counter LCD 7-12
Ticket Counter LCD 1-6
Concourse H Gates 6-10
Concourse H Gates 1-5
Concourse H Kiosk
Flight Deck
Flight Deck
Flight Deck
Flight Deck
Notes
Exhibit B-1
Exhibit 3
Page 219 of 278
Access Switch
Access Switch
Access Switch
Access Switch
Access Switch
Access Switch
Access Switch
Access Switch
Access Switch
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
A_T3_COMMCTR_3X_1
A_T4_1003_2X_1
A_T4_1034B_3X_1
A_T4_1036N_3X_1
A_T4_2041A_3X_1
A_T4_2213_2X_RP
A_T4_2213_3X_1
A_T4_2213_3X_2
A_T4_FIS_3X_1
A_T4_FIS_3X_2
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
Extron
Extron
Extron
Extron
Extron
Extron
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
Cisco
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Access Switch
A_T3_1611_3X_1
Access Switch
A_T3_1061_3X_1
995
999
Access Switch
A_T3_1050B_3X_1
994
Access Switch
Access Switch
A_T3_1050A_3X_1
993
A_T3_1308A_3X_1
Access Switch
A_T2_1059_3X_1
992
998
Access Switch
A_T2_1016_3X_1
991
Access Switch
Access Switch
A_T2_1009A_3X_1
990
Access Switch
Access Switch
A_T1_3155_3X_1
989
A_T3_1106_3X_1
Access Switch
A_T1_3104_3X_1
988
A_T3_1133B_3X_1
Access Switch
A_T1_1666_3X_1
987
997
Cisco
Access Switch
A_T1_1302_3X_1
986
996
Cisco
Access Switch
A_T1_1114_3X_1
985
Dell
Cisco
DVC
Access Switch
DVC-CELL-2
Dell
Dell
A_T1_1010_3X_1
DVC
DVC-CELL-1
982
983
DVC
RAC-232B-DVC-01
981
Manufacturer
984
Display Type
Use Description
Location
Ref. #
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C2950
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
C3524/3550
Network Access
C3524/3550
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Network Access
Display Flifo/Logo
Display Flifo/Logo
Display Flifo/Logo
Displayed Data
C3524/3550
C2950
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
C3524/3550
Dell 260
Dell 260
Dell 280
Model #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
MM Fiber
Cat 5E
Cat 5E
Cat 5E
Cable
Page 29 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2041A
T4-1036N
T4-1034B
T4-1003
T3-COMMCTR
T3-1611
T3-1308A
T3-1133B
T3-1106
T3-1061
T3-1050B
T3-1050A
T2-1059
T2-1016
T2-1009A
T1-3155
T1-3104
T1-1666
T1-1302
T1-1114
T1-1010
RCC-118
RCC-118
RCC-232B
Distribution Point
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2041A
T4-1036N
T4-1034B
T4-1003
T3-COMMCTR
T3-1611
T3-1308A
T3-1133B
T3-1106
T3-1061
T3-1050B
T3-1050A
T2-1059
T2-1016
T2-1009A
T1-3155
T1-3104
T1-1666
T1-1302
T1-1114
T1-1010
RCC-118
RCC-118
RCC-232B
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Concourse C Kiosks Flifo Monitor #6
Concourse C Kiosks Flifo Monitor #5
Concourse C Kiosks Flifo Monitor #4
Concourse C Kiosks Flifo Monitor #3
Concourse C Kiosks Flifo Monitor #2
Concourse C Kiosks Flifo Monitor #1
24 Total ports
24 Total ports
24 Total ports
24 Total ports
12 Total ports
24 Total ports
24 Total ports
24 Total ports
12 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
24 Total ports
Cell Lot Screen 3-4
Cell Lot Screen 1-2
VP 2nd and 3rd floor
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T4
T4
T4
T4
T4
T4
T4
T4
T4
Comm Center
T3
T3
T3
T3
T3
T3
T3
T2
T2
T2
T1
T1
T1
T1
T1
T1
Cell Lot
Cell Lot
RCC
Location
Exhibit B-1
Exhibit 3
Page 220 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Extron
TP T BNC DA4
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 30 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Distribution Point
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
West Bag Claim Kiosk Flifo Monitor #5
West Bag Claim Kiosk Flifo Monitor #4
West Bag Claim Kiosk Flifo Monitor #3
West Bag Claim Kiosk Flifo Monitor #2
West Bag Claim Kiosk Flifo Monitor #1
West Entrance Kiosk Flifo Monitor #6
West Entrance Kiosk Flifo Monitor #5
West Entrance Kiosk Flifo Monitor #4
West Entrance Kiosk Flifo Monitor #3
West Entrance Kiosk Flifo Monitor #2
West Entrance Kiosk Flifo Monitor #1
Gate B9 Monitor
Gate B8 Monitor
Gate B7 Monitor
Gate B6 Monitor
Gate B5 Monitor
Gate B4 Monitor
Gate B3 Monitor
Gate B2 Monitor
Gate B1 Monitor
Concourse B Kiosks Flifo Monitor #6
Concourse B Kiosks Flifo Monitor #5
Concourse B Kiosks Flifo Monitor #4
Concourse B Kiosks Flifo Monitor #3
Concourse B Kiosks Flifo Monitor #2
Concourse B Kiosks Flifo Monitor #1
Gate C9 Monitor
Gate C8 Monitor
Gate C7 Monitor
Gate C6 Monitor
Gate C5 Monitor
Gate C4 Monitor
Gate C3 Monitor
Gate C2 Monitor
Gate C1 Monitor
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 221 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP T BNC DA4
Video over Cat 5
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Extron
TP T BNC DA4
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 31 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T2-1016
T2-1016
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
Distribution Point
T2-1016
T2-1016
T2-1016
T2-1016
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T2-1009A
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
West BC/TKT Kiosk Flifo Monitor #4
West BC/TKT Kiosk Flifo Monitor #3
West BC/TKT Kiosk Flifo Monitor #2
West BC/TKT Kiosk Flifo Monitor #1
East BC/TKT Kiosk Flifo Monitor #6
East BC/TKT Kiosk Flifo Monitor #5
East BC/TKT Kiosk Flifo Monitor #4
East BC/TKT Kiosk Flifo Monitor #3
East BC/TKT Kiosk Flifo Monitor #2
East BC/TKT Kiosk Flifo Monitor #1
East Ticketing Kiosk Flifo Monitor #6
East Ticketing Kiosk Flifo Monitor #5
East Ticketing Kiosk Flifo Monitor #4
East Ticketing Kiosk Flifo Monitor #3
East Ticketing Kiosk Flifo Monitor #2
East Ticketing Kiosk Flifo Monitor #1
West Ticketing Kiosk Flifo Monitor #6
West Ticketing Kiosk Flifo Monitor #5
West Ticketing Kiosk Flifo Monitor #4
West Ticketing Kiosk Flifo Monitor #3
West Ticketing Kiosk Flifo Monitor #2
West Ticketing Kiosk Flifo Monitor #1
East Bag Claim Kiosk Flifo Monitor #6
East Bag Claim Kiosk Flifo Monitor #5
East Bag Claim Kiosk Flifo Monitor #4
East Bag Claim Kiosk Flifo Monitor #3
East Bag Claim Kiosk Flifo Monitor #2
East Bag Claim Kiosk Flifo Monitor #1
East Entrance Kiosk Flifo Monitor #6
East Entrance Kiosk Flifo Monitor #5
East Entrance Kiosk Flifo Monitor #4
East Entrance Kiosk Flifo Monitor #3
East Entrance Kiosk Flifo Monitor #2
East Entrance Kiosk Flifo Monitor #1
West Bag Claim Kiosk Flifo Monitor #6
Notes
September 23, 2008
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 222 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP T BNC DA4
Video over Cat 5
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Extron
TP T BNC DA4
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 32 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
Distribution Point
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Ticket Counter LCD #11
Ticket Counter LCD #10
Ticket Counter LCD #9
Ticket Counter LCD #8
Ticket Counter LCD #7
Ticket Counter LCD #6
Ticket Counter LCD #5
Ticket Counter LCD #4
Ticket Counter LCD #3
Ticket Counter LCD #2
Ticket Counter LCD #1
Gate H10 Monitor
Gate H9 Monitor
Gate H8 Monitor
Gate H7 Monitor
Gate H6 Monitor
Gate H5 Monitor
Gate H4 Monitor
Gate H3 Monitor
Gate H2 Monitor
Gate H1 Monitor
Concourse H Kiosk Flifo Monitor #6
Concourse H Kiosk Flifo Monitor #5
Concourse H Kiosk Flifo Monitor #4
Concourse H Kiosk Flifo Monitor #3
Concourse H Kiosk Flifo Monitor #2
Concourse H Kiosk Flifo Monitor #1
Concourse D Kiosks Flifo Monitor #6
Concourse D Kiosks Flifo Monitor #5
Concourse D Kiosks Flifo Monitor #4
Concourse D Kiosks Flifo Monitor #3
Concourse D Kiosks Flifo Monitor #2
Concourse D Kiosks Flifo Monitor #1
West BC/TKT Kiosk Flifo Monitor #6
West BC/TKT Kiosk Flifo Monitor #5
Notes
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T2
T2
T2
T2
T2
T2
T2
T2
Location
Exhibit B-1
Exhibit 3
Page 223 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP T BNC DA4
Video over Cat 5
TP T BNC DA4
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Extron
TP T BNC DA4
Extron
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
TP T BNC DA4
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 33 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Distribution Point
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
T1
T1
T1
T1
T1
T1
T1
T1
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
September 23, 2008
Concourse C South Kiosk Flifo Monitor #2
Concourse C South Kiosk Flifo Monitor #1
Concourse C North Kiosk Flifo Monitor #6
Concourse C North Kiosk Flifo Monitor #5
Concourse C North Kiosk Flifo Monitor #4
Concourse C North Kiosk Flifo Monitor #3
Concourse C North Kiosk Flifo Monitor #2
Concourse C North Kiosk Flifo Monitor #1
FIS Ticket Counter LCD #5
FIS Ticket Counter LCD #4
FIS Ticket Counter LCD #3
FIS Ticket Counter LCD #2
FIS Ticket Counter LCD #1
CUS/TKT/BC Kiosks Flifo Monitor #6
CUS/TKT/BC Kiosks Flifo Monitor #5
CUS/TKT/BC Kiosks Flifo Monitor #4
CUS/TKT/BC Kiosks Flifo Monitor #3
CUS/TKT/BC Kiosks Flifo Monitor #2
CUS/TKT/BC Kiosks Flifo Monitor #1
Ticket Counter LCD #27
Ticket Counter LCD #26
Ticket Counter LCD #25
Ticket Counter LCD #24
Ticket Counter LCD #23
Ticket Counter LCD #22
Ticket Counter LCD #21
Ticket Counter LCD #20
Ticket Counter LCD #19
Ticket Counter LCD #18
Ticket Counter LCD #17
Ticket Counter LCD #16
Ticket Counter LCD #15
Ticket Counter LCD #14
Ticket Counter LCD #13
Ticket Counter LCD #12
Notes
Exhibit B-1
Exhibit 3
Page 224 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 34 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1114
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Distribution Point
T1-1114
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1666
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
T1-1010
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
West Entrance Kiosk Flifo Monitor #1
Gate B9 Monitor
Gate B8 Monitor
Gate B7 Monitor
Gate B6 Monitor
Gate B5 Monitor
Gate B4 Monitor
Gate B3 Monitor
Gate B2 Monitor
Gate B1 Monitor
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
September 23, 2008
Concourse B South Kiosk Flifo Monitor #6
Concourse B South Kiosk Flifo Monitor #5
Concourse B South Kiosk Flifo Monitor #4
Concourse B South Kiosk Flifo Monitor #3
Concourse B South Kiosk Flifo Monitor #2
Concourse B South Kiosk Flifo Monitor #1
Concourse B North Kiosk Flifo Monitor #6
Concourse B North Kiosk Flifo Monitor #5
Concourse B North Kiosk Flifo Monitor #4
Concourse B North Kiosk Flifo Monitor #3
Concourse B North Kiosk Flifo Monitor #2
Concourse B North Kiosk Flifo Monitor #1
Gate C9 Monitor
Gate C8 Monitor
Gate C7 Monitor
Gate C6 Monitor
Gate C5 Monitor
Gate C4 Monitor
Gate C3 Monitor
Gate C2 Monitor
Gate C1 Monitor
Concourse C South Kiosk Flifo Monitor #6
Concourse C South Kiosk Flifo Monitor #5
Concourse C South Kiosk Flifo Monitor #4
Concourse C South Kiosk Flifo Monitor #3
Notes
Exhibit B-1
Exhibit 3
Page 225 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 35 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
Distribution Point
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3155
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-3104
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1302
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
T1-1114
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
East Ticketing Kiosk Flifo Monitor #6
East Ticketing Kiosk Flifo Monitor #5
East Ticketing Kiosk Flifo Monitor #4
East Ticketing Kiosk Flifo Monitor #3
East Ticketing Kiosk Flifo Monitor #2
East Ticketing Kiosk Flifo Monitor #1
West Ticketing Kiosk Flifo Monitor #6
West Ticketing Kiosk Flifo Monitor #5
West Ticketing Kiosk Flifo Monitor #4
West Ticketing Kiosk Flifo Monitor #3
West Ticketing Kiosk Flifo Monitor #2
West Ticketing Kiosk Flifo Monitor #1
East Bag Claim Kiosk Flifo Monitor #6
East Bag Claim Kiosk Flifo Monitor #5
East Bag Claim Kiosk Flifo Monitor #4
East Bag Claim Kiosk Flifo Monitor #3
East Bag Claim Kiosk Flifo Monitor #2
East Bag Claim Kiosk Flifo Monitor #1
East Entrance Kiosk Flifo Monitor #6
East Entrance Kiosk Flifo Monitor #5
East Entrance Kiosk Flifo Monitor #4
East Entrance Kiosk Flifo Monitor #3
East Entrance Kiosk Flifo Monitor #2
East Entrance Kiosk Flifo Monitor #1
West Bag Claim Kiosk Flifo Monitor #6
West Bag Claim Kiosk Flifo Monitor #5
West Bag Claim Kiosk Flifo Monitor #4
West Bag Claim Kiosk Flifo Monitor #3
West Bag Claim Kiosk Flifo Monitor #2
West Bag Claim Kiosk Flifo Monitor #1
West Entrance Kiosk Flifo Monitor #6
West Entrance Kiosk Flifo Monitor #5
West Entrance Kiosk Flifo Monitor #4
West Entrance Kiosk Flifo Monitor #3
West Entrance Kiosk Flifo Monitor #2
Notes
September 23, 2008
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
T1
Location
Exhibit B-1
Exhibit 3
Page 226 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 36 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
Distribution Point
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1059
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-1016
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
T2-2041B
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
West Concourse D Kiosk Flifo Monitor #5
West Concourse D Kiosk Flifo Monitor #4
West Concourse D Kiosk Flifo Monitor #3
West Concourse D Kiosk Flifo Monitor #2
West Concourse D Kiosk Flifo Monitor #1
East Concourse D Kiosk Flifo Monitor #6
East Concourse D Kiosk Flifo Monitor #5
East Concourse D Kiosk Flifo Monitor #4
East Concourse D Kiosk Flifo Monitor #3
East Concourse D Kiosk Flifo Monitor #2
East Concourse D Kiosk Flifo Monitor #1
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
T2
Location
September 23, 2008
West Ticketing Level Kiosk Flifo Monitor #6
West Ticketing Level Kiosk Flifo Monitor #5
West Ticketing Level Kiosk Flifo Monitor #4
West Ticketing Level Kiosk Flifo Monitor #3
West Ticketing Level Kiosk Flifo Monitor #2
West Ticketing Level Kiosk Flifo Monitor #1
West Bag Claim Kiosk Flifo Monitor #6
West Bag Claim Kiosk Flifo Monitor #5
West Bag Claim Kiosk Flifo Monitor #4
West Bag Claim Kiosk Flifo Monitor #3
West Bag Claim Kiosk Flifo Monitor #2
West Bag Claim Kiosk Flifo Monitor #1
East Ticketing Level Kiosk Flifo Monitor #6
East Ticketing Level Kiosk Flifo Monitor #5
East Ticketing Level Kiosk Flifo Monitor #4
East Ticketing Level Kiosk Flifo Monitor #3
East Ticketing Level Kiosk Flifo Monitor #2
East Ticketing Level Kiosk Flifo Monitor #1
East Bag Claim Kiosk Flifo Monitor #6
East Bag Claim Kiosk Flifo Monitor #5
East Bag Claim Kiosk Flifo Monitor #4
East Bag Claim Kiosk Flifo Monitor #3
East Bag Claim Kiosk Flifo Monitor #2
East Bag Claim Kiosk Flifo Monitor #1
Notes
Exhibit B-1
Exhibit 3
Page 227 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 37 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T2-1059
Distribution Point
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1036N
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T4-1034B
T2-1059
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Ticket Counter Plasma #18
Ticket Counter Plasma #17
Ticket Counter Plasma #16
Ticket Counter Plasma #15
Ticket Counter Plasma #14
Ticket Counter Plasma #13
Ticket Counter Plasma #12
Ticket Counter Plasma #11
Ticket Counter Plasma #10
Ticket Counter Plasma #9
Ticket Counter Plasma #8
Ticket Counter Plasma #7
Ticket Counter Plasma #6
Ticket Counter Plasma #5
Ticket Counter Plasma #4
Ticket Counter Plasma #3
Ticket Counter Plasma #2
Ticket Counter Plasma #1
Gate H10 Monitor
Gate H9 Monitor
Gate H8 Monitor
Gate H7 Monitor
Gate H6 Monitor
Gate H5 Monitor
Gate H4 Monitor
Gate H3 Monitor
Gate H2 Monitor
Gate H1 Monitor
Concourse H Kiosk Flifo Monitor #6
Concourse H Kiosk Flifo Monitor #5
Concourse H Kiosk Flifo Monitor #4
Concourse H Kiosk Flifo Monitor #3
Concourse H Kiosk Flifo Monitor #2
Concourse H Kiosk Flifo Monitor #1
West Concourse D Kiosk Flifo Monitor #6
Notes
September 23, 2008
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T2
Location
Exhibit B-1
Exhibit 3
Page 228 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 38 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
RCC-232A
RCC-232A
RCC-232A
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Distribution Point
RCC-232A
RCC-232A
RCC-232A
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-FIS
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
FIDS West 3rd floor LCD #3
FIDS West 3rd floor LCD #2
FIDS West 3rd floor LCD #1
FIS Ticket Counter LCD #5
FIS Ticket Counter LCD #4
FIS Ticket Counter LCD #3
FIS Ticket Counter LCD #2
FIS Ticket Counter LCD #1
Ticketing Level Kiosk Flifo Monitor #6
Ticketing Level Kiosk Flifo Monitor #5
Ticketing Level Kiosk Flifo Monitor #4
Ticketing Level Kiosk Flifo Monitor #3
Ticketing Level Kiosk Flifo Monitor #2
Ticketing Level Kiosk Flifo Monitor #1
Bag Claim Kiosk Flifo Monitor #6
Bag Claim Kiosk Flifo Monitor #5
Bag Claim Kiosk Flifo Monitor #4
Bag Claim Kiosk Flifo Monitor #3
Bag Claim Kiosk Flifo Monitor #2
Bag Claim Kiosk Flifo Monitor #1
Customs Kiosk Flifo Monitor #6
Customs Kiosk Flifo Monitor #5
Customs Kiosk Flifo Monitor #4
Customs Kiosk Flifo Monitor #3
Customs Kiosk Flifo Monitor #2
Customs Kiosk Flifo Monitor #1
Ticket Counter Plasma #27
Ticket Counter Plasma #26
Ticket Counter Plasma #25
Ticket Counter Plasma #24
Ticket Counter Plasma #23
Ticket Counter Plasma #22
Ticket Counter Plasma #21
Ticket Counter Plasma #20
Ticket Counter Plasma #19
Notes
September 23, 2008
RCC
RCC
RCC
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
T4
Location
Exhibit B-1
Exhibit 3
Page 229 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 39 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
Distribution Point
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
Location
September 23, 2008
RCC 2nd Level West (Extron TR/RC Used)
RCC 2ndd Level West (Extron TR/RC Used)
RCC 2nd Level Center (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
FIDS West 2nd floor LCD #5
FIDS West 2nd floor LCD #4
FIDS West 2nd floor LCD #3
FIDS West 2nd floor LCD #2
FIDS West 2nd floor LCD #1
FIDS East 3rd floor LCD #5
FIDS East 3rd floor LCD #4
FIDS East 3rd floor LCD #3
FIDS East 3rd floor LCD #2
FIDS East 3rd floor LCD #1
FIDS West 3rd floor LCD #5
FIDS West 3rd floor LCD #4
FIDS West 3rd floor LCD #3
FIDS West 3rd floor LCD #2
FIDS West 3rd floor LCD #1
FIDS East 3rd floor LCD #6
FIDS East 3rd floor LCD #5
FIDS East 3rd floor LCD #4
FIDS East 3rd floor LCD #3
FIDS East 3rd floor LCD #2
FIDS East 3rd floor LCD #1
FIDS West 3rd floor LCD #6
FIDS West 3rd floor LCD #5
FIDS West 3rd floor LCD #4
Notes
Exhibit B-1
Exhibit 3
Page 230 of 278
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Video Transmitter
Serial Server
Serial Server
Serial Server
Serial Server
Serial Convertor
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
Video Receiver
T1-Lantronix
T2-Lantronix
T3-Lantronix
T4-Lantronix
RS-232 - RS-422
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
Daktronics
Lantronix
Lantronix
Lantronix
Lantronix
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
LL-2301
ETS8P
ETS8P
ETS8P
ETS8P
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Serial Signal
Serial Over Cat 5
Serial Over Cat 5
Serial Over Cat 5
Serial Over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
TP R 15 HD A
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Video over Cat 5
Displayed Data
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Extron
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
TP R 15 HD A
Model #
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Extron
Manufacturer
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Display Type
Use Description
Location
Ref. #
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 40 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T1-1302
T4-2213
T3-1061
T2-1016
T1-1302
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232A
RCC-232A
Distribution Point
T1-1302
T4-2213
T3-1061
T2-1016
T1-1302
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232A
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232B
RCC-232A
RCC-232A
RCC-232B
RCC-232B
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Terminal 1 Bag Claim Serial Run
Terminal 4 Serial LED Devices
Terminal 3 Serial LED Devices
Terminal 2 Serial LED Devices
Terminal 1 Serial LED Devices
T1
T4
T3
T2
T1
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
RCC
Location
September 23, 2008
RCC 9th Level West (Extron TR/RC Used)
RCC 8th Level West (Extron TR/RC Used)
RCC 8th Level West (Extron TR/RC Used)
RCC 7th Level West (Extron TR/RC Used)
RCC 7th Level West (Extron TR/RC Used)
RCC 6th Level West (Extron TR/RC Used)
RCC 6th Level West (Extron TR/RC Used)
RCC 5th Level West (Extron TR/RC Used)
RCC 5th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 3rd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 2nd Level West (Extron TR/RC Used)
RCC 9th Level East (Extron TR/RC Used)
RCC 8th Level East (Extron TR/RC Used)
RCC 7th Level East (Extron TR/RC Used)
RCC 6th Level East (Extron TR/RC Used)
RCC 5th Level East (Extron TR/RC Used)
RCC 4thd Level East (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 3rd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 2nd Level East (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level West (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
RCC 4th Level East (Extron TR/RC Used)
Notes
Exhibit B-1
Exhibit 3
Page 231 of 278
Daktronics
Daktronics
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
Serial Convertor
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
RS-232 - RS-422
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
There is a project currently underway to replace all CRTs and
“multi-channel” DVCs in T1 and T2 with NEC LCDs and
Wyse V90 LEs. Similar projects are in the design phase for
T4 and the RCC.
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Serial Convertor
Serial Convertor
RS-232 - RS-422
1406
Serial Convertor
Serial Convertor
RS-232 - RS-422
1405
Daktronics
RS-232 - RS-422
Serial Convertor
RS-232 - RS-422
1404
Daktronics
RS-232 - RS-423
Serial Convertor
RS-232 - RS-422
1403
Daktronics
Daktronics
1407
Serial Convertor
1402
Manufacturer
1408
Serial Convertor
RS-232 - RS-422
RS-232 - RS-422
1401
Display Type
Use Description
Location
Ref. #
IC-08SS
LL-2301
LL-2301
LL-2301
LL-2301
IC-08SS
LL-2301
LL-2301
LL-2301
LL-2301
IC-08SS
LL-2301
LL-2301
LL-2301
IC-08SS
LL-2301
LL-2301
LL-2301
Model #
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Serial Signal
Displayed Data
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cat 5E
Cable
Page 41 of 41
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
Protocol
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T2-1016
T2-1016
T2-1016
T2-1016
T1-1302
T1-1302
T1-1302
T1-1302
Distribution Point
T4-2213
T4-2213
T4-2213
T4-2213
T4-2213
T3-1061
T3-1061
T3-1061
T3-1061
T3-1061
T2-1016
T2-1016
T2-1016
T2-1016
T1-1302
T1-1302
T1-1302
T1-1302
Nearest IDF
Existing EVIDS Display Devices Inventory Sheet
Terminal 4 Bag Tug Input Serial Run
Terminal 4 Jetway Serial Run
Terminal 4 Gate Display Serial Run
Terminal 4 Ticket Counter Serial Run
Terminal 4 Bag Claim Serial Run
Terminal 3 Bag Tug Input Serial Run
Terminal 3 Jetway Serial Run
Terminal 3 Gate Display Serial Run
Terminal 3 Ticket Counter Serial Run
Terminal 3 Bag Claim Serial Run
Terminal 2 Bag Tug Input Serial Run
T4
T4
T4
T4
T4
T3
T3
T3
T3
T3
T2
T2
T2
T2
T1
T1
T1
T1
Location
September 23, 2008
Terminal 2 Concourse VPD Display Serial Run
Terminal 2 Ticket Counter Serial Run
Terminal 2 Bag Claim Serial Run
Terminal 1 Bag Tug Input Serial Run
Terminal 1 Jetway Serial Run
Terminal 1 Gate Display Serial Run
Terminal 1 Ticket Counter Serial Run
Notes
Exhibit B-1
Exhibit 3
Page 232 of 278
Exhibit 3
Page 233 of 278
Exhibit 3
Page 234 of 278
AIMS: Airport Information Management System
Project Title:
AirIT Sr. Software Engineer
AirIT Software Engineering Manager
AirIT System Engineer
AirIT Sr. System Engineer
AirIT System Engineering Manager
AirIT Solution Engineer
AirIT Sr. Solution Engineer
AirIT Solution Manager
AirIT Project / Program Mgr. / Consulting Mgr.
Network Engineer
Dato Electric Electrician
Dato Electric Installation Labor
2
3
4
5
6
7
8
9
10
11
12
13
Exhibit D – Rates and Fees charged by Contractor/Subcontractor
AirIT Software Engineer
SYSTEM OR OPTIONS
1
REF. #
1
1
1
1
1
1
1
1
1
1
1
QTY
1
1
Subcontractor (Dato Electric)
Contractor (AirIT)
LABOR RATES
Facility Name: Ft. Lauderdale/Hollywood International Airport
RFP No. 20070514-0-AV-01
Project No:
HR
HR
HR
HR
HR
HR
HR
HR
HR
HR
HR
HR
HR
TYPE OR
UNIT
98
78
150
150
100
120
140
140
100
120
140
120
100
UNIT COST
RATES AND FEES TO BE CHARGED BY CONTRACTOR / SUBCONTRACTORS
EXHIBIT D
1 of 1
98
78
150
150
100
120
140
140
100
120
140
120
100
EXTENDED
COST
Exhibit 3
Page 235 of 278
AIMS: Airport Information Management System
Project Title:
QTY
TYPE OR
UNIT
File Server
Application Server
Database Server
Performance Workstation
Standard Workstation
Display Device Controller
Gate Input Workstation
17" LCD
20" LCD
32" LCD
40" LCD
46" LCD
Indoor LED
Baggage Input Consoles
2D Ticket Printer
Bag Tag Printer
MSR / OCR Peripheral
Boarding Gate Reader
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
12,375
12,375
12,375
12,063
2,438
1,438
2,438
875
1,563
1,213
1,625
5,436
3,126
2,688
3,733
3,733
1,188
3,075
UNIT COST
UNIT PRICES (incl. all cost assoc. w/ Delivery excluding taxes)
SYSTEM OR OPTIONS
Exhibit E – Master Price List
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
REF. #
Facility Name: Ft. Lauderdale/Hollywood International Airport
RFP No. 20070514-0-AV-01
Project No:
MASTER PRICE LIST
EXHIBIT E
1 of 2
12,375
12,375
12,375
12,063
2,438
1,438
2,438
875
1,563
1,213
1,625
5,436
3,126
2,688
3,733
3,733
1,188
3,075
EXTENDED
COST
Exhibit 3
Page 236 of 278
DAPP Standard Doc Printer
General Doc Printer
DAPP 2 Position Ticket Counter
CUSS Kiosk In-line
CUSS Kiosk w/o BTP
CUSS Kiosk w/ BTP
DAPP 2 Position Gate Counter
DAPP Loading Bridge Podium
DAPP Operational Workstation
Cisco 3560
UPS
SYSTEM OR OPTIONS
Exhibit E – Master Price List
19
20
21
22
23
24
25
26
27
28
29
REF. #
1
1
1
1
1
1
1
1
1
1
1
QTY
MASTER PRICE LIST
EXHIBIT E
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
EA
TYPE OR
UNIT
624
624
16,296
12,813
13,063
15,938
13,214
7,244
2,438
6,276
4,360
UNIT COST
2 of 2
624
624
16,296
12,813
13,063
15,938
13,214
7,244
2,438
6,276
4,360
EXTENDED
COST
Exhibit 3
Page 237 of 278
EVIDS Deployment
2001
EVIDS Training Complete
Existing EVIDS Displays configured and
driven by new system - Terminal One
complete
Prices do not reflect Retainage percentage or amount.
2001.03
2001.02
New EVIDS workstations and input
devices installed, configured, and tested
(all inputs to EVIDS through AIMS,
interface to Infax system complete, airline
2001.01
feeds - Delta, Southwest, and American
complete, screen layouts complete, AIMS
configured to accommodate all EVIDS
functionality)
Completion of phase #1 (50% license fee)
Completion and preliminary acceptance of
Detailed Project Schedule and Submittal
Schedule
Preliminary acceptance of existing
conditions documentation
Completion and preliminary acceptance of
all Phase 1 Deliverables as detailed in
Exhibit A 1.6.2 item 101
Completion and preliminary acceptance of
all Phase 1 Workshops as detailed in
Exhibit A 1.6.2 item 102
Installation, configuration, and preliminary
acceptance of all AIMS head-end
equipment (equipment and operating
system)
Installation, configuration, and preliminary
acceptance of test lab
Completion and preliminary acceptance of
the FAT (LDCS for DAPP, CUSS
excluded)
Deliverable/Milestone Description
1006
1005
1004
1003
1002
1001
0002
0001
Sub-phase
$459,000.00
$229,500.00
1
1
$25,000.00
$186,519.00
1
1
$350,000.00
1
$15,000.00
$110,000.00
1
1
$140,000.00
1
$250,000.00
$175,000.00
1
1
$115,000.00
Unit Cost
1
Units
Airport Information Management Systems (AIMS)
Payment Schedule
Ft. Lauderdale-Hollywood International Airport
$25,000.00
$15,000.00
$250,000.00
$229,500.00
$459,000.00
$186,519.00
$350,000.00
$110,000.00
$140,000.00
$175,000.00
$115,000.00
Value
Payment Schedule
Exhibit F
$175,000
$115,000
Phase 0
$229,500
$459,000
$186,519
$350,000
$110,000
$140,000
Phase 1
$25,000
$15,000
$250,000
Phase 2
Phase 3
1 of 3
Optional
Services
Exhibit 3
Page 238 of 278
2002
$100,000.00
1
2002.10
2002.09
$75,000.00
$75,000.00
1
$165,000.00
1
1
Installation, configuration, and testing of
DAPP end user devices - 100% complete
2002.07
$165,000.00
$145,000.00
1
Installation, configuration, and testing of
DAPP end user devices - 75% complete
2002.06
$187,750.00
$187,750.00
$20,000.00
1
1
Installation, configuration, and testing of
DAPP end user devices - 50% complete
2002.05
Installation, configuration, and testing of
CUSS stations - 25% complete
Installation, configuration, and testing of
CUSS stations - 50% complete
Installation, configuration, and testing of
CUSS stations - 75% complete
1
Installation, configuration, and testing of
DAPP end user devices - 25% complete
2002.04
2002.08
1
DAPP Training Complete - Stage 1
Airlines
2002.03
$150,000.00
$100,000.00
1
1
$25,000.00
1
2002.02 Configuration of all CUSS stage 1 Airlines
$25,000.00
1
$250,000.00
$25,000.00
1
Unit Cost
1
Existing EVIDS Displays configured and
driven by new system - Terminal Two
complete
Existing EVIDS Displays configured and
driven by new system - Terminal Three
complete
Existing EVIDS Displays configured and
driven by new system - Terminal Four
complete
New EVIDS Displays installed, configured,
and tested - 50% complete
New EVIDS Displays installed, configured,
and tested - 100% complete
DAPP Deployment
Units
2002.01 Configuration of all DAPP stage 1 Airlines
2001.08
2001.07
2001.06
2001.05
2001.04
Deliverable/Milestone Description
Prices do not reflect Retainage percentage or amount.
Sub-phase
Airport Information Management Systems (AIMS)
Payment Schedule
Ft. Lauderdale-Hollywood International Airport
$75,000.00
$75,000.00
$145,000.00
$165,000.00
$165,000.00
$187,750.00
$187,750.00
$20,000.00
$150,000.00
$250,000.00
$100,000.00
$100,000.00
$25,000.00
$25,000.00
$25,000.00
Value
Payment Schedule
Exhibit F
Phase 0
Phase 1
$75,000
$75,000
$145,000
$165,000
$165,000
$187,750
$187,750
$20,000
$150,000
$250,000
$100,000
$100,000
$25,000
$25,000
$25,000
Phase 2
Phase 3
2 of 3
Optional
Services
Exhibit 3
Page 239 of 278
3005
3004
3003
3002
3001
2004
2003
Total Base Services
Installation, configuration, and testing of
CUSS stations - 100% complete
RMS/AODB Deployment
Installation, configuration, and testing of
2003.01 AODB including third party feed - 100%
complete
Installation, configuration, and testing of
2003.02 RMS and associated end user devices 100% complete
Completion and preliminary acceptance of
all phase 2 deliverables associated with
stage 1 airlines as detailed in Exhibit A
1.6.3 item 214
Completion and preliminary acceptance of
Performance Verification Testing for AIMS
including stage 1 airlines
Completion and preliminary acceptance of
all remaining training
Completion and preliminary acceptance of
Endurance Testing for AIMS including
stage 1 airlines
Completion and preliminary acceptance of
all Phase 3 deliverables for stage 1
airlines as detailed in Exhibit A 1.6.4 item
308
Final Acceptance by County (50% license
fee)
2002.11
Deliverable/Milestone Description
Prices do not reflect Retainage percentage or amount.
Sub-phase
$300,000.00
$150,000.00
$100,000.00
$70,000.00
$20,000.00
$70,000.00
$93,901.00
$229,500
1
1
1
1
1
1
1
$75,000.00
Unit Cost
1
1
Units
Airport Information Management Systems (AIMS)
Payment Schedule
Ft. Lauderdale-Hollywood International Airport
$4,858,920.00
$229,500.00
$93,901.00
$70,000.00
$20,000.00
$70,000.00
$100,000.00
$150,000.00
$300,000.00
$75,000.00
Value
Payment Schedule
Exhibit F
Phase 0
Phase 1
$100,000
$150,000
$300,000
$75,000
Phase 2
$229,500
$93,901
$70,000
$20,000
$70,000
Phase 3
3 of 3
Optional
Services
Exhibit 3
Page 240 of 278
Exhibit 3
Page 241 of 278
EXHIBIT G
KEY STAFF
Project No:
RFP No. 20070514-0-AV-01
Project Title:
AIMS: Airport Information Management System
Facility Name: Ft. Lauderdale/Hollywood International Airport
NAME
TITLE
Jeff Shull
SVP Airport Solutions – Project Executive
Marc Dormoy
AirIT Project Manager
Carmen Dobre
VP Engineering / Solution Design
James Smith
Program Manager – Operational Systems
Ray Vecchiarelli Manager – IT Support
Don Casey
System Architect
Exhibit 3
Page 242 of 278
Exhibit 3
Page 243 of 278
Exhibit 3
Page 244 of 278
EXHIBIT "I-1"
Work Authorization No. ____
Under Contract Administrator's Authority
Project Title:
RFP No:
Contractor:
AIRPORT INFORMATION MANAGEMENT SYSTEM
RFP 20070514-0-AV-01
AIR-TRANSPORT IT SERVICES, INC., a Delaware corporation
This Work Authorization is between Broward County and Contractor as required pursuant to a SYSTEM
AND SERVICES AGREEMENT approved by the Broward County Board of County Commissioners on
____________, 2009 ("Agreement").
This Work Authorization provides for Services consistent with the Agreement referenced above and as
specifically described in the attached proposal and scope. Payment(s) for such services shall be in
accordance with the Agreement. The time period for this Work Authorization will consist of ____ (___)
calendar days, or as set forth in the attachment hereto.
Budget
__________________
Purchase Order Number
________________________
Department Name
Aviation Department
Fee Determination: Payment for services under this Work Authorization shall be as follows:
Total Lump Sum/Maximum Not-to-Exceed
$___________________
Contractor
Attest:
AIR-TRANSPORT IT SERVICES, INC.
By: ______________________________
Secretary
Date
____________________________________
Date
Corporate Seal
Name & Title:__________________________
County
Recommended by Consultant:
Broward County,
through its Contract Administrator
________________________
Convergent Strategies
Consulting, Inc.
__________________________________
Date
Date _______________
Name & Title: ________________________
Exhibit 3
Page 245 of 278
EXHIBIT "I-2"
Work Authorization No. ____
Under Purchasing Director's Authority
Project Title:
RFP No:
Contractor:
AIRPORT INFORMATION MANAGEMENT SYSTEM
RFP 20070514-0-AV-01
AIR-TRANSPORT IT SERVICES, INC., a Delaware corporation
This Work Authorization is between Broward County and Contractor as required pursuant to a SYSTEM
AND SERVICES AGREEMENT approved by the Broward County Board of County Commissioners on
____________, 2009 ("Agreement").
This Work Authorization provides for Services consistent with the Agreement referenced above and as
specifically described in the attached proposal and scope. Payment(s) for such services shall be in
accordance with the Agreement. The time period for this Work Authorization will consist of ____ (___)
calendar days, or as set forth in the attachment hereto.
Budget
__________________
Purchase Order Number
________________________
Department Name
Aviation Department
Fee Determination: Payment for services under this Work Authorization shall be as follows:
Total Lump Sum/Maximum Not-to-Exceed
$___________________
Contractor
Attest:
AIR-TRANSPORT IT SERVICES, INC.
By: ___________________________________
Secretary
Date
___________________________________
Date
Corporate Seal
Name & Title ________________________
Recommended by Consultant:
____________________________
Convergent Strategies
Date
Consulting, Inc.
County
Broward County,
through its Director of Purchasing
_____________________________
Director of Purchasing
Date
Recommended by
Contract Administrator:
Approved as to form by
Office of County Attorney
Broward County, Florida
JEFFREY J. NEWTON, County Attorney
___________________________
Date
Name & Title: _______________
By: ______________________________
Assistant County Attorney
Exhibit 3
Page 246 of 278
EXHIBIT "I-3"
Work Authorization No. ____
Under Board of County Commissioners' Authority
Project Title:
RFP No:
Contractor:
AIRPORT INFORMATION MANAGEMENT SYSTEM
RFP 20070514-0-AV-01
AIR-TRANSPORT IT SERVICES, INC., a Delaware corporation
This Work Authorization is between Broward County and Contractor as required pursuant to a SYSTEM
AND SERVICES AGREEMENT approved by the Broward County Board of County Commissioners on
____________, 2009 ("Agreement").
This Work Authorization provides for Services consistent with the Agreement referenced above and as
specifically described in the attached proposal and scope. Payment(s) for such services shall be in
accordance with the Agreement. The time period for this Work Authorization will consist of ____ (___)
calendar days, or as set forth in the attachment hereto.
Budget
__________________
Purchase Order Number
________________________
Department Name
Aviation Department
Fee Determination: Payment for services under this Work Authorization shall be as follows:
Total Lump Sum/Maximum Not-to-Exceed
$___________________
Attest:
AIR-TRANSPORT IT SERVICES, INC.
By: ___________________________________
Secretary
Date
Corporate Seal
____________________________________
Date
Name & Title __________________________
COUNTY
_________________________________________
County Administrator and Ex-Officio
Clerk of the Board of County Commissioners
Broward County, Florida
Recommended by Consultant
_________________________________________
Convergent Strategies
Date
Consulting, Inc.
Recommended by Contract Administrator:
_______________________________________
Date
Name & Title: ___________________________
BROWARD COUNTY, through its
Board of County Commissioners
____________________________
Mayor
Date
Approved as to form by
Office of the County Attorney
Broward County, Florida
JEFFREY J. NEWTON, County Attorney
By:___________________________
Assistant County Attorney
Risk Management Division:
By: ____________________
Date
Exhibit 3
Page 247 of 278
EXHIBIT J
SCHEDULE OF SUBCONTRACTOR PARTICIPATION
Project No:
RFP No. 20070514-0-AV-01
Project Title:
AIMS: Airport Information Management System
Facility Name: Ft. Lauderdale/Hollywood International Airport
No.
1.
2
3
4
5.
6.
7
8
9.
10.
Firm Name
Discipline
Dato Electric, Inc.
Electrical, data, equipment supply
and installation
Exhibit 3
Page 248 of 278
Exhibit J-2
Exhibit 3
Page 249 of 278
Exhibit J-2
Exhibit 3
Page 250 of 278
Exhibit 3
Page 251 of 278
Exhibit 3
Page 252 of 278
Fort Lauderdale, Florida 33315
100 Aviation Blvd.
c/o Airport Development
Broward County Aviation Department
( Columns F )
_____% of Stored Material
( Columns D + E )
_____% of Completed Work
Additions
-
Deductions
My Commission Expires:
Notary Public:
$
TOTALS $
-
Date:
Print Name:
Date:
The undersigned, after examination of the attached payment request, notes that: (1) The Project Manager's review has conformed to
established BCAD procedural standards, (2) that the Project Manager has received sufficient information and backup documentation
from the Contractor for analysis and his subsequent recommendation for payment, and (3) that such recommended payment amount
appears to be fair and reasonable.
By:
DIRECTOR, AIRPORT DEVELOPMENT
Print Name:
By:
PROJECT MANAGER for BCAD
(Attach explanation if amount certified differs from the amount applied for. Initial all figures on this Application and on the Continuation Sheet (Schedule of
Values) that are changed to conform to the amount certified.)
AMOUNT CERTIFIED
Name:
Date:
This Certificate is not negotiable. The AMOUNT CERTIFIED is payable only to the Contractor named herein. Issuance, payment and
acceptance of payment are without prejudice to any rights of the Owner or Contractor under this Contract.
By:
NET CHANGES by Change Order,
Amendments
Date:
Project Manager Certificate for Payment
In accordance with the Contract Documents, based on on-site observations and the data comprising this Application, the Project
Manager certifies to the Owner that to the best of his knowledge, information and belief, the Work has progressed as indicated,
including all quantities, materials, work percentages completed, and the quality of the Work is in accordance with the Contract
Documents and the Contractor is entitled to payment of the AMOUNT CERTIFIED.
day of
County of:
Total approved this month
-
NTP Date:
Request for Payment No.:
Project Manager:
Work Authorization No.:
OWNER: BROWARD COUNTY AVIATION DEPARTMENT, CONTRACT ADMINISTRATOR
$
-
-
-
-
RLI No.:
Project Name:
Total changes approved in previous months
by Owner.
Change Order, Amendments Summary
(Line 3 less Line 6)
$
$
$
9) Balance to Finish, Including Retainage
-
-
$
$
$
8) Current Payment Due
(Line 6 from prior Certificate)
7) Less Previous Applications for Payment
(Lines 4 less Line 5 Total)
6) Total Earned Less Retainage
(Line 5a + 5b or Total in Column M)
Total Retainage:
b)
a)
5) Retainage:
(Column G on Schedule of Values Form)
me this
Subscribed and sworn to before
3) Contract Sum To Date (Line 1+2)
-
State of:
CONTRACTOR:
2) Net change by Change Orders, Amendments
4) Total Completed and Stored to Date
Date:
Period To/From:
The undersigned Contractor certifies that to the best of the Contractor's knowledge, information and belief, the Work covered by this
Application for Payment has been completed in accordance with the Contract Documents, that all amounts have been paid by the
Contractor for Work for which previous Certificates for Payment were issued and payments received from the Owner, and that current
payment shown herein is now due.
By:
$
P.O. NO.:
Vendor Code:
APPLICATION AND CERTIFICATE FOR PAYMENT
1) Original Contract Sum
CONTRACTOR'S APPLICATION FOR PAYMENT
Application is made for payment, as shown below, in
connection with the contract. Continuation Sheet Schedule of Values Form is attached.
Contract For:
From Contractor:
To Owner:
EXHIBIT K
Exhibit 3
Page 253 of 278
DESCRIPTION OF WORK
CONSULTANT
TOTAL ALL CATEGORIES
SUBTOTAL
REIMBURSABLES:
SUBTOTAL
TASK
B
A
D
METHOD LS or NTE
C
SCHEDULE
D VALUE
F
WORK
COMPLETE
WORK
D
COMPLETE
PREVIOUS
D THIS
APPLICATI APPLICATI
ON
ON
E
The Consultant's Payment Request, containing the Consultant's signed Certification, is attached.
Use the final column on contracts where retainage is applicable.
CONTINUATION SHEET - Schedule of Values
Consultant's Payment Request
TOTAL
AMOUNT
INVOICED
TO DATE
G
EXHIBIT K (page 2)
I
J
K
L
M
N
O
THIS
THIS
TOTAL TO TOTAL TO
%
%
APPROVED
INVOICE
INVOICE
DATE
DATE
COMPLETE CONTRACT REMAINING RETAINAGE RETAINAGE RETAINAGE RETAINAGE
FOR
NTP
LIMIT
BALANCE
HELD
RELEASED
HELD
RELEASED PAYMENT
H
Date:
Period To/From:
RLI No.:
Project Name:
Work Authorization No.:
BCAD Project Manager:
Request for Payment No.:
NTP Date:
Consultant Invoice Number
Exhibit 3
Page 254 of 278
Exhibit 3
Page 255 of 278
EXHIBIT L
Board of County Commissioners, Broward County, Florida
CHANGE ORDER
REGULAR
CHANGE ORDER NO.:
PROJECT TITLE:
BUDGET NO.:
CONTRACT NO.:
REQUISITION NO.:
PROJECT NO.:
PURCHASE ORDER NO.:
TO:
CONTRACTOR
THE FOLLOWING CHANGES ARE HEREBY AUTHORIZED upon approval of the County Administrator or Designee and
signature below:
DESCRIPTIONS OF CHANGES, REASONS THEREFORE, AND COST AND/OR TIME CHANGE FOR EACH:
COST BASIS:
Description of Change:
CONTRACT AMOUNT BEFORE THIS CHANGE: $
TOTAL CHANGE IN CONTRACT AMOUNT:
INCREASE $
DECREASE $
TOTAL CHANGE IN CONTRACT PERIOD:
Signature:
NO CHANGE
ADD:
0 CALENDAR DAYS
DEDUCT:
0 CALENDAR DAYS
New Contract Time: _______________ Days
New Contract Amount: $_____________________
Title:
Date:
RECOMMENDED BY:
(Agent(s) for Board)
ACCEPTED BY CONTRACTOR: (Unless separately
requested acknowledged in writing)
Signature:
Signature:
Title:
Title:
Date:
Date:
Signature:
APPROVED BY:
Title:
COUNTY ADMINISTRATOR OR DESIGNEE:
Date:
Signature:
Signature:
Title:
Title:
Date:
Date:
C:\Documents and Settings\bgreenberg\Desktop\AIMS To Date\CO Page 1 Template.doc
Exhibit 3
Page 256 of 278
Optional Services Category 1
Exhibit M
Ft. Lauderdale-Hollywood International Airport
Airport Information Management Systems (AIMS)
Optional Services Category 1 Detail *
Category 1
Deliverable/Milestone Description
Units
Unit Cost
Value
Configuration, testing, and preliminary acceptance of all DAPP stage 2 Airlines
Configuration, testing, and preliminary
1.01 acceptance of all DAPP related components
for Allegiant
Configuration, testing, and preliminary
1.02 acceptance of all DAPP related components
for Frontier
Configuration, testing, and preliminary
1.03 acceptance of all DAPP related components
for JetBlue
Configuration, testing, and preliminary
1.04 acceptance of all DAPP related components
for Air Canada
Configuration, testing, and preliminary
1.05 acceptance of all DAPP related components
for AirTran
Configuration, testing, and preliminary
1.06 acceptance of all DAPP related components
for Bahamas Air
Configuration, testing, and preliminary
1.07 acceptance of all DAPP related components
for CanJet
Configuration, testing, and preliminary
1.08 acceptance of all DAPP related components
for Continental
Configuration, testing, and preliminary
1.09 acceptance of all DAPP related components
for Continental Connection (Gulfstream)
Configuration, testing, and preliminary
1.10 acceptance of all DAPP related components
for Delta/Delta Connection
Configuration, testing, and preliminary
1.11 acceptance of all DAPP related components
for Northwest/KLM
Configuration, testing, and preliminary
1.12 acceptance of all DAPP related components
for US Airways
Configuration, testing, and preliminary
1.13 acceptance of all DAPP related components
for Air Sunshine
*Specific Airlines and Order are Subject to Change
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1 of 3
Exhibit 3
Page 257 of 278
Optional Services Category 1
Exhibit M
Ft. Lauderdale-Hollywood International Airport
Airport Information Management Systems (AIMS)
Optional Services Category 1 Detail *
Category 1
Deliverable/Milestone Description
Configuration, testing, and preliminary
1.14 acceptance of all DAPP related components
for Chalks
Configuration, testing, and preliminary
1.15 acceptance of all DAPP related components
for Lynx Air International
Configuration, testing, and preliminary
1.16 acceptance of all DAPP related components
for Yellow Air Taxi
Units
Unit Cost
Value
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
Configuration, testing, and preliminary acceptance of all CUSS stage 2 Airlines
Configuration, testing, and preliminary
1.17 acceptance of all CUSS related components
for Air Jamaica
Configuration, testing, and preliminary
1.18 acceptance of all CUSS related components
for AirTran
Configuration, testing, and preliminary
1.19 acceptance of all CUSS related components
for Continental Connection (Gulfstream)
Configuration, testing, and preliminary
1.20 acceptance of all CUSS related components
for Frontier
Configuration, testing, and preliminary
1.21 acceptance of all CUSS related components
for Southwest
Configuration, testing, and preliminary
1.22 acceptance of all CUSS related components
for Spirit
Configuration, testing, and preliminary
1.23 acceptance of all CUSS related components
for US Airways
Configuration, testing, and preliminary
1.24 acceptance of all CUSS related components
for Westjet
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
Configuration, testing, and preliminary acceptance of all DAPP Stage 3 Airlines
Configuration, testing, and preliminary
1.25 acceptance of all DAPP related components
for Southwest
*Specific Airlines and Order are Subject to Change
1
$10,000.00
$10,000.00
2 of 3
Exhibit 3
Page 258 of 278
Optional Services Category 1
Exhibit M
Ft. Lauderdale-Hollywood International Airport
Airport Information Management Systems (AIMS)
Optional Services Category 1 Detail *
Category 1
Deliverable/Milestone Description
Configuration, testing, and preliminary
1.26 acceptance of all DAPP related components
for Skyservice
Configuration, testing, and preliminary
1.27 acceptance of all DAPP related components
for Sunwing
Configuration, testing, and preliminary
1.28 acceptance of all DAPP related components
for Westjet
Units
Unit Cost
Value
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
1
$10,000.00
$10,000.00
Total Optional Services
*Specific Airlines and Order are Subject to Change
$280,000
3 of 3
Exhibit 3
Page 259 of 278
EXHIBIT M
Optional Services
Categories
Limit
1.
Stage 2/3 DAPP CUSS Airlines
This category covers implementation of additional airlines (not Stage 1)
on to the DAPP and CUSS platforms. Twenty-eight additional airlines
have been identified that could potentially require either DAPP or CUSS
applications as well as their associated integration with the overall AIMS.
This component provides the coordination, software and integration
required to support these airlines. Pricing is provided on a per airline
basis ($10,000 per airline). See attached Category 1 detail.
$ 280,000
2.
Purchase and Installation of Additional DAPP/CUSS Locations
This category covers the hardware, software, millwork, and all other
appurtenances including electrical and low voltage cabling, and labor to
extend AIMS to selected new areas in the terminal complex. These
optional services will be required in the instance(s) where new locations
for DAPP and/or CUSS devices are identified. Potential areas for these
services include, but are not limited to, new CUSS kiosk locations in the
rental car center, additional CUSS kiosks throughout any of the
Terminals, and DAPP workstations at gates and/or ticket counters in
Terminals 1, 2, or 3.
$ 250,000
3.
Test Lab Infrastructure
This category includes modifications to test lab infrastructure including
electrical and low voltage cabling. This optional service will provide any
additional data cabling required to connect test lab equipment to the
BCAD/AIMS network, and will provide electrical augmentations to
support the power requirements of the AIMS equipment to be located in
the test lab.
$ 50,000
Total
Maximum Optional Services:
$580,000
Exhibit 3
Page 260 of 278
Exhibit N
00710.
FORM OF PERFORMANCE BOND
BY THIS BOND, We _______________________________________, as Principal,
hereinafter called Contractor, and _______________________________, as Surety, are bound
to the Board of County Commissioners of Broward County, Florida, as Obligee, hereinafter
called County, in the amount of ____________________________ Dollars ($__________) for
the payment whereof Contractor and Surety bind themselves, their heirs, executors,
administrators, successors and assigns, jointly and severally.
WHEREAS, Contractor has by written agreement entered into a Contract, Bid/Contract
No.:
_____________, awarded the _______ day of __________________, 20____, with
County which Contract Documents are by reference incorporated herein and made a part
hereof, and specifically include provision for liquidated damages, and other damages identified,
and for the purposes of this Bond are hereafter referred to as the "Contract";
THE CONDITION OF THIS BOND is that if Contractor:
1)
Performs the Contract between Contractor and County for construction of
_______________________________________________, the Contract being made a
part of this Bond by reference, at the times and in the manner prescribed in the Contract;
and
2)
Pays County all losses, liquidated damages, expenses, costs and attorney’s fees
including appellate proceedings, that County sustains as a result of default by Contractor
under the Contract; and
3)
Performs the guarantee of all work and materials furnished under the Contract for the
time specified in the Contract; then THIS BOND IS VOID, OTHERWISE IT REMAINS IN
FULL FORCE AND EFFECT.
Whenever Contractor shall be, and declared by County to be, in default under the
Contract, County having performed County obligations thereunder, the Surety may
promptly remedy the default, or shall promptly:
Exhibit N
1
Exhibit 3
Page 261 of 278
FORM OF PERFORMANCE BOND
(Continued)
a)
Complete the project in accordance with the terms and conditions of the Contract
Documents; or
b)
Obtain a bid or bids for completing the project in accordance with the terms and
conditions of the Contract Documents, and upon determination by Surety of the
lowest responsible Bidder, or, if County elects, upon determination by County
and Surety jointly of the lowest responsible Bidder, arrange for a contract
between such Bidder and County, and make available as work progresses (even
though there should be a default or a succession of defaults under the Contract
or Contracts of completion arranged under this paragraph) sufficient funds to pay
the cost of completion less the balance of the Contract price; but not exceeding,
including other costs and damages for which the Surety may be liable hereunder,
the amount set forth in the first paragraph hereof. The term "balance of the
Contract price," as used in this paragraph, shall mean the total amount payable
by County to Contractor under the Contract and any amendments thereto, less
the amount properly paid by County to Contractor.
No right of action shall accrue on this bond to or for the use of any person or corporation
other than County named herein.
The Surety hereby waives notice of and agrees that any changes in or under the
Contract Documents and compliance or noncompliance with any formalities connected
with the Contract or the changes does not affect Surety's obligation under this Bond.
Signed and sealed this ______ day of _____________________, 20_____.
Exhibit N
2
Exhibit 3
Page 262 of 278
FORM OF PERFORMANCE BOND
(Continued)
WITNESSES:
__________________________
Secretary
(CORPORATE SEAL)
IN THE PRESENCE OF:
__________________________
__________________________
__________________________________
(Name of Corporation)
By______________________________
(Signature and Title)
__________________________________
(Type Name and Title Signed Above)
INSURANCE COMPANY:
By________________________________
Agent and Attorney-in-Fact
Address: __________________________
(Street)
________________________________
(City/State/Zip Code)
Telephone No.: __________________
Exhibit N
3
Exhibit 3
Page 263 of 278
00720.
FORM OF PAYMENT BOND
BY THIS BOND, We _______________________________________, as Principal,
hereinafter called Contractor, and _______________________________, as Surety, are bound
to the Board of County Commissioners of Broward County, Florida, as Obligee, hereinafter
called County, in the amount of ______________________________ Dollars ($____________)
for the payment whereof Contractor and Surety bind themselves, their heirs, executors,
administrators, successors and assigns, jointly and severally.
WHEREAS, Contractor has by written agreement entered into a Contract, Bid/Contract
No.:
_____________, awarded the _______ day of __________________, 20____, with
County which Contract Documents are by reference incorporated herein and made a part
hereof, and specifically include provision for liquidated damages, and other damages identified,
and for the purposes of this Bond are hereafter referred to as the "Contract";
THE CONDITION OF THIS BOND is that if Contractor:
1)
Pays County all losses, liquidated damages, expenses, costs and attorney’s fees
including appellate proceedings, that County sustains because of default by Contractor
under the Contract; and
2)
Promptly makes payments to all claimants as defined by Florida Statute 255.05(1) for all
labor, materials and supplies used directly or indirectly by Contractor in the performance
of the Contract;
THEN CONTRACTOR'S OBLIGATION SHALL BE VOID; OTHERWISE, IT SHALL
REMAIN IN FULL FORCE AND EFFECT SUBJECT, HOWEVER, TO THE
FOLLOWING CONDITIONS:
a)
A claimant, except a laborer, who is not in privity with Contractor and who has
not received payment for its labor, materials, or supplies shall, within forty-five
(45) calendar days after beginning to furnish labor, materials, or supplies for the
prosecution of the work, furnish to Contractor a notice that he intends to look to
the bond for protection.
b)
A claimant who is not in privity with Contractor and who has not received
payment for its labor, materials, or supplies shall, within ninety (90) calendar
days after performance of the labor or after complete delivery of the materials or
supplies, deliver to Contractor and to the Surety, written notice of the
performance of the labor or delivery of the materials or supplies and of the
nonpayment.
Exhibit N
4
Exhibit 3
Page 264 of 278
FORM OF PAYMENT BOND
(Continued)
c)
No action for the labor, materials, or supplies may be instituted against
Contractor or the Surety unless the notices stated under the preceding conditions
have been given.
d)
Any action under this Bond must be instituted in accordance with the Notice and
Time Limitations provisions prescribed in Section 255.05(2), Florida Statutes.
The Surety hereby waives notice of and agrees that any changes in or under the
Contract Documents and compliance or noncompliance with any formalities connected with the
Contract or the changes does not affect the Surety's obligation under this Bond.
Signed and sealed this ______ day of _______________________, 20____.
ATTEST:
__________________________
Secretary
(CORPORATE SEAL)
IN THE PRESENCE OF:
__________________________
__________________________
____________________________
(Name of Corporation)
By _______________________________
(Signature and Title)
________________________________
(Type Name and Title Signed Above)
INSURANCE COMPANY:
By______________________________
Agent and Attorney-in-Fact
Address: _________________________
(Street)
________________________________
(City/State/Zip Code)
Telephone No.: ___________________
Exhibit N
5
Exhibit 3
Page 265 of 278
ATTACHMENT I
NONDISCRIMINATION REQUIREMENTS
I.
NONDISCRIMINATION - 49 CFR PART 21 REQUIREMENTS
During the performance of this contract, the Contractor for itself, its personal
representatives, assigns and successors in interest (hereinafter referred to
collectively as the "Contractor") agrees as follows:
(a)
Compliance With Regulations. The Contractor shall comply with the
Regulations relative to nondiscrimination in Federally Assisted Programs of
the Department of Transportation (hereinafter, "DOT") Title 49, Code of
Federal Regulations, Part 21, as they may be amended from time to time
(hereinafter referred to as the "Regulations"), which are herein incorporated
by reference and made a part of this contract.
(b)
Nondiscrimination. The Contractor shall not discriminate on the grounds of
race, color, religion, gender, national origin, age, marital status, political
affiliation, familial status, physical or mental disability, or sexual orientation in
the selection and retention of subcontractors, including procurement of
materials and leases of equipment. The Contractor shall not participate either
directly or indirectly in the discrimination prohibited by Section 21.5 of the
Regulations, including employment practices when the contract covers a
program set forth in Appendix B of the Regulations.
(c)
Solicitation for Subcontractors, Including Procurement of Materials and
Equipment. In all solicitation either by competitive bidding or negotiation
made by the Contractor for work to be performed under a subcontract,
including procurement of materials or leases of equipment, each potential
subcontractor or supplier shall be notified by the Contractor of the
Contractor's obligation under this Contract and the Regulations relative to
nondiscrimination on the grounds of race, color, religion, gender, national
origin, age, marital status, political affiliation, familial status, physical or
mental disability, or sexual orientation.
(d)
Information and Reports. The Contractor shall provide all information and
reports required by the Regulations or directives issued pursuant thereto and
shall permit access to its books, records, accounts, other sources of
information, and its facilities as may be determined by the County or the
Federal Aviation Administration (FAA) to be pertinent to ascertain compliance
with such Regulations, orders, and instructions. Where any information
required of Contractor is in the exclusive possession of another who fails or
refuses to furnish this information, the Contractor shall so certify to the
County or the FAA, as appropriate, and shall set forth what efforts it has
made to obtain the information.
AIMS System and Services Agreement – Attachment I
Page 1 of 4
Exhibit 3
Page 266 of 278
(e)
In the event of the Contractor's
Sanctions for Noncompliance.
noncompliance with the nondiscrimination provisions of this Contract, the
County shall impose such Contract sanctions as it or the FAA may determine
to be appropriate, including, but not limited to: (1) withholding of payments
under the Contract until there is compliance, and/or (2) cancellation,
termination, or suspension of the contract, in whole or in part. In the event of
cancellation or termination of the Contract(if such contract is a lease), the
County shall have the right to re-enter the Premises as if said lease had
never been made or issued. These provisions shall not be effective until the
procedures of Title 49 CFR Part 21 are followed and completed, including
exercise or expiration of appeal rights.
(f)
Incorporation of Provisions. The Contractor shall include the provisions of
paragraphs (a) through (e), above, in every subcontract, including
procurement of materials and leases of equipment, unless exempt by the
Regulations or directives issued pursuant thereto. The Contractor shall take
such action with respect to any subcontract or procurement as the County or
the FAA may direct as a means of enforcing such provisions including
sanctions for noncompliance.
Provided, however, that in the event
Contractor becomes involved in, or is threatened with, litigation with a
subcontractor or supplier as a result of such direction, the Contractor may
request the County to enter into such litigation to protect the interests of the
County and, in addition, the Contractor may request the United States to
enter into such litigation to protect the interests of the United States.
(g)
The Contractor, as a part of the consideration hereof, does hereby covenant
and agree that in the event facilities are constructed, maintained, or
otherwise operated on the said property described in this contract, for a
purpose for which a DOT program or activity is extended or for another
purpose involving the provision of similar services or benefits, the Contractor
shall maintain and operate such facilities and services in compliance with all
other requirements imposed pursuant to 49 CFR Part 21, Nondiscrimination
in Federally Assisted Programs of the Department of Transportation, and as
said Regulation may be amended.
(h)
The Contractor, as a part of the consideration hereof, does hereby covenant
and agree that: (1) no person on the grounds of race, color, religion, gender,
national origin, age, marital status, political affiliation, familial status, physical
or mental disability, or sexual orientation shall be excluded from participation
in, denied the benefits of, or be otherwise subjected to discrimination in the
use of said facilities, (2) that in the construction of any improvements on,
over, or under the premises and the furnishing of Services thereon, no
person on the grounds of race, color, religion, gender, national origin, age,
marital status, political affiliation, familial status, physical or mental disability,
or sexual orientation shall be excluded from participation in, denied the
benefits of, or otherwise be subjected to discrimination, and (3) that the
AIMS System and Services Agreement – Attachment I
Page 2 of 4
Exhibit 3
Page 267 of 278
Contractor shall use the premises in compliance with all other requirements
imposed by or pursuant to 49 CFR Part 21, Nondiscrimination in Federally
Assisted Programs of the Department of Transportation, and as said
Regulations may be amended.
II.
NONDISCRIMINATION - 14 CFR PART 152 REQUIREMENTS
During the performance of this contract, the Contractor, for itself, its assignees and
successors in interest agrees as follows:
The Contractor agrees to undertake an affirmative action program as required by
14 CFR Part 152, Subpart E, to insure that no person shall on the grounds of race,
color, religion, gender, national origin, age, marital status, political affiliation,
familial status, physical or mental disability, or sexual orientation be excluded from
participation in any employment, contracting, or leasing activities covered in 14
CFR Part 152, Subpart E. The Contractor agrees that no person shall be
excluded on these grounds from participating in or receiving the services or
benefits of any program or activity covered by this Subpart. The Contractor
agrees that it will require its covered suborganizations to provide assurances to
the Contractor that they similarly will undertake affirmative action programs and
that they will require assurances from their suborganizations as required by 14
CFR Part 152, Subpart E, to the same effect.
The Contractor agrees to comply with any affirmative action plan or steps for equal
employment opportunity required by 14 CFR Part 152, Subpart E, as part of the
affirmative action program, and by any federal, state, County or local agency or
court, including those resulting from a conciliation agreement, a consent decree,
court order or similar mechanism. The Contractor agrees that state or County
affirmative action plans will be used in lieu of any affirmative action plan or steps
required by 14 CFR Part 152, Subpart E, only when they fully meet the standards
set forth in 14 CFR 152.409. The Contractor agrees to obtain a similar assurance
from its covered organizations, and to cause them to require a similar assurance
of their covered suborganizations, as required by 14 CFR Part 152, Subpart E.
If required by 14 CFR Part 152, Contractor shall prepare and keep on file for
review by the FAA Office of Civil Rights an affirmative action plan developed in
accordance with the standards in Part 152. The Contractor shall similarly require
each of its covered suborganizations (if required under Part 152) to prepare and to
keep on file for review by the FAA Office of Civil Rights, an affirmative action plan
developed in accordance with the standards in Part 152.
If Contractor is not subject to an affirmative action plan, regulatory goals and
timetables, or other mechanism providing for short and long-range goals for equal
employment opportunity under Part 152, then Contractor shall nevertheless make
good faith efforts to recruit and hire minorities and women for its aviation workforce
as vacancies occur, by taking any affirmative action steps required by Part 152.
AIMS System and Services Agreement – Attachment I
Page 3 of 4
Exhibit 3
Page 268 of 278
Contractor shall similarly require such affirmative action steps of any of its covered
suborganizations, as required under Part 152.
Contractor shall keep on file, for the period set forth in Part 152, reports (other
than those submitted to the FAA), records, and affirmative action plans, if
applicable, that will enable the FAA Office of Civil Rights to ascertain if there has
been and is compliance with this subpart, and Contractor shall require its covered
suborganizations to keep similar records as applicable.
Contractor shall, if required by Part 152, annually submit to the County the reports
required by Section 152.415 and Contractor shall cause each of its covered
suborganizations that are covered by Part 152 to annually submit the reports
required by Section 152.415 to the Contractor who shall, in turn, submit same to
the County for transmittal to the FAA.
III.
NONDISCRIMINATION - GENERAL CIVIL RIGHTS PROVISIONS
The Contractor, for itself, its assignees and successors in interest agrees that it
will comply with pertinent statutes, Executive Orders and such rules as are
promulgated to assure that no person shall, on the grounds of race, color, religion,
gender, national origin, age, marital status, political affiliation, familial status,
physical or mental disability, or sexual orientation be excluded from participating in
any activity conducted with or benefiting from Federal assistance. This provision
obligates the Contractor or its transferee, for the period during which Federal
assistance is extended to the airport program, except where Federal assistance is
to provide, or is in the form of personal property or real property or interest therein
or structures or improvements thereon. In these cases, the Provision obligates the
party or any transferee for the longer of the following periods: (a) the period during
which the property is used by the sponsor or any transferee for a purpose for
which federal assistance is extended, or for another purpose involving the
provision of similar services or benefits; or (b) the period during which the airport
sponsor or any transferee retains ownership or possession of the property. In the
case of contractors, this Provision binds the contractors from the bid solicitation
period through the completion of the contract.
IV.
NONDISCRIMINATION - 49 CFR PART 26
Contractors shall not discriminate on the basis of race, color, religion, gender,
national origin, age, marital status, political affiliation, familial status, physical or
mental disability, or sexual orientation in the performance of this contract. Failure
by the Contractor to carry out these requirements is a material breach of this
contract, which may result in the termination of this Contractor such other remedy
as the County deems appropriate.
AIMS System and Services Agreement – Attachment I
Page 4 of 4
Exhibit 3
Page 269 of 278
ATTACHMENT II
PROVISIONS PERTAINING TO AIRPORT PROJECTS
ALL AGREEMENTS:
1.
SECURITY
Airport Security Program and Aviation Regulations. Contractor agrees to observe
all security requirements and other requirements of the Federal Aviation
Regulations applicable to Contractor, including without limitation, all regulations of
the United States Department of Transportation, the Federal Aviation
Administration and the Transportation Security Administration, and the Contractor
agrees to comply with the County's Airport Security Program and the Air
Operations area (AOA) Vehicle Access Program, and any amendments thereto,
and to comply with such other rules and regulations as may be reasonably
prescribed by the County, and to take such steps as may be necessary or directed
by the County to insure that sublessees, employees, invitees and guests observe
these requirements. If required by the Aviation Department, Contractor shall
conduct background checks of its employees in accordance with applicable
Federal Regulations. If as a result of the acts or omissions of Contractor, its
sublessees, employees, invitees or guests, the County incurs any fines and/or
penalties imposed by any governmental agency, including without limitation, the
United States Department of Transportation, the Federal Aviation Administration or
the Transportation Security Administration, or any expense in enforcing any
federal regulations, including without limitation, airport security regulations, or the
rules or regulations of the County, and/or any expense in enforcing the County's
Airport Security Program, then Contractor agrees to pay and/or reimburse to
County all such costs and expenses, including all costs of administrative
proceedings, court costs, and attorneys' fees and all costs incurred by County in
enforcing this provision.
Contractor further agrees to rectify any security
deficiency or other deficiency as may be determined as such by the County or the
United States Department of Transportation, Federal Aviation Administration, the
Transportation Security Administration, or any other federal agency with
jurisdiction. In the event Contractor fails to remedy any such deficiency, the
County may do so at the sole cost and expense of Contractor. The County
reserves the right to take whatever action is necessary to rectify any security
deficiency or other deficiency.
(a)
Access to Security Identification Display Areas and Identification Badges.
The Contractor shall be responsible for requesting the Aviation Department to
issue identification badges ("SIDA Badges") to all employees who are authorized
access to Security Identification Display Areas ("SIDA") on the Airport, as
designated in the Airport Security Program. In addition, Contractor shall be
AIMS System and Services Agreement – Attachment II
Page 1 of 9
Exhibit 3
Page 270 of 278
responsible for the immediate reporting of all lost or stolen SIDA Badges and the
immediate return of the SIDA Badges of Contractor's personnel transferred from
the Airport, or terminated from the employ of the Contractor, or upon termination of
this System Agreement. Before a SIDA Badge is issued to an employee,
Contractor shall comply with the requirements of applicable federal regulations
with regard to employment history, verification and criminal history checks, and
shall require that each employee complete the SIDA training program conducted
by the Aviation Department. The Contractor shall pay or cause to be paid to the
Aviation Department such charges as may be established from time to time for lost
or stolen SIDA Badges and those not returned to the Aviation Department in
accordance with this section. Recovery of such charges for lost, stolen, or nonreturned badges may be assessed through retainage of that portion of final
payment due to the contractor. The Aviation Department shall have the right to
require the Contractor to conduct background investigations and to furnish certain
data on such employees before the issuance of SIDA Badges, which data may
include the fingerprinting of employee applicants for such badges.
(b)
Operation of Vehicles on the AOA: Before the Contractor shall permit any
employee of Contractor or of any subcontractor to operate a motor vehicle
of any kind or type on the AOA (and unless escorted by an Aviation
Department approved escort), the Contractor shall ensure that all such
vehicle operators possess current, valid, and appropriate Florida driver's
licenses. In addition, any motor vehicles and equipment of Contractor or of
any subcontractor operating on the AOA must have an appropriate vehicle
identification permit issued by the Aviation Department, which identification
must be displayed as required by the Aviation Department.
(c)
Consent to Search/Inspection: The Contractor agrees that its vehicles,
cargo, goods and other personal property are subject to being inspected and
searched when attempting to enter or leave and while on the AOA. The
Contractor further agrees on behalf of itself and its subcontractors, that it
shall not authorize any employee or other person to enter the AOA unless
and until such employee or other person has executed a written consent-tosearch/inspection form acceptable to the Aviation Department. Contractor
acknowledges and understands that the foregoing requirements are for the
protection of users of the Airport and are intended to reduce incidents of
cargo tampering, aircraft sabotage, thefts and other unlawful activities at the
Airport. For this reason, Contractor agrees that persons not executing such
consent-to-search/inspection form shall not be employed by the Contractor or
by any subcontractor at the Airport in any position requiring access to the
AOA or allowed entry to the AOA by the Contractor or by any subcontractors.
(d)
The provisions hereof shall survive the expiration or any other termination of
this System Agreement.
AIMS System and Services Agreement – Attachment II
Page 2 of 9
Exhibit 3
Page 271 of 278
2.
PROHIBITED INTERESTS
If this System Agreement is funded by any federal or state grants, then, in that
event, no member, officer, or employee of County during his or her tenure or for
two (2) years thereafter shall have any interest, direct or indirect, in this System
Agreement or the proceeds thereof.
Contractor agrees to insert the foregoing sentence in any agreements between
Contractor or subcontractors engaged to provide Services pursuant to this System
Agreement.
If any such present or former member, officer, or employee has such an interest
and if such interest as set forth above is immediately disclosed to the County, the
County with prior approval of the funding agency, may waive the prohibition
contained in this subsection; provided that any such present member, officer, or
employee shall not participate in any action by the County relating to such System
Agreement.
3.
RECORDS
Contractor shall keep such books, records and accounts and require any and all
consultants/contractors or subcontractors to keep such books, records and
accounts as may be necessary in order to record complete and correct entries as
to personnel hours charged to the project and any expenses for which Contractor
expects to be reimbursed. In addition, to the above, the Contractor shall maintain
an acceptable cost accounting system. All work, materials, payrolls, books,
accounts, documents, and records relative to the project, or directly pertinent to
the specific contract for the purposes of making an audit, examination, excerpt or
transcription shall be available at all reasonable times for examination and audit by
County, and in the event such System Agreement is subject to federal or state
funding or grants, by the Federal Aviation Administration, the Comptroller General
of the United States, the Florida Department of Transportation, or any of their duly
authorized representatives. Such books, records and accounts shall be kept for
the "Retention Period" (as hereinafter defined). Incomplete or incorrect entries in
such books, records or accounts shall be grounds for County's disallowance of any
fees or expenses based upon such entries. All books, records and accounts
which are considered public records shall, pursuant to Chapter 119, Florida
Statutes, be kept by Contractor in accordance with such statutes. The "Retention
Period" shall be defined as the greater of: (i) the required retention period of the
Florida Public Records Act (Chapter 119, Fla. Stat.), if applicable, or (ii) for a
period of three (3) years after final payment and the completion of all work to be
performed pursuant to this System Agreement, or if any audit has been initiated
and audit findings have not been resolved at the end of the three years, the books
and records shall be retained until resolution of the audit findings, or (iii) if this
project is subject to Florida Department of Transportation grants, for a period of
five (5) years after final payment and the completion of all work to be performed
AIMS System and Services Agreement – Attachment II
Page 3 of 9
Exhibit 3
Page 272 of 278
pursuant to this System Agreement, or if any audit has been initiated and audit
findings have not been resolved at the end of the five years, the books and
records shall be retained until resolution of the audit findings.
4.
PROTECTION OF RECORDS
Contractor shall protect from harm and damage all data, drawings, specifications,
designs, models, photographs, reports, surveys and other data created or
provided in connection with this System Agreement (collectively, "County
Property"), while such data and materials are in consultant's/contractor's
possession. Such duty may include, but is not limited to, making back-up copies
of all data stored by electronic device on any media, taking reasonable actions to
prevent damage by impending flood or storm (including, but not limited to,
removing the County Property to a safe location), and establishing and enforcing
such security measures as are reasonably available, considering the customary
practice within consultant's/contractor's trade or profession. If requested by
County, Contractor shall furnish to County copies of any and all disks containing
drawings and other pertinent data prepared by consultant/ contractor in
conjunction with this System Agreement.
5.
BREACH OF CONTRACT TERMS - SANCTIONS
Any violation or breach of the terms of this Contract on the part of the Contractor
or subcontractor may result in the suspension or termination of this Contractor
such other action which may be necessary to enforce the rights of the parties of
this agreement.
6.
RIGHT TO INVENTIONS
All rights to inventions and materials generated under this Contract are subject to
regulations issued by the FAA and the County. Information regarding these rights
is available from the FAA and the County.
7.
TRADE RESTRICTION CLAUSES TO BE INCLUDED IN ALL
SOLICITATIONS, CONTRACTS, AND SUBCONTRACTS
The Contractor or subcontractor, by submission of an offer and/or execution of a
contract, certifies that it:
a.
Is not owned or controlled by one or more citizens of a foreign country
included in the list of countries that discriminate against U.S. firms
published by the Office of the United States Trade Representative (USTR);
and
b.
Has not knowingly entered into any contract or subcontract for this project
with a person that is a citizen or national of a foreign country on said list, or
AIMS System and Services Agreement – Attachment II
Page 4 of 9
Exhibit 3
Page 273 of 278
is owned or controlled directly or indirectly by one or more citizens or
nationals of a foreign country on said list; and
c.
Has not procured any product nor subcontracted for the supply of any
product for use on the project that is produced in a foreign country on said
list.
Unless the restrictions of this clause are waived by Secretary of Transportation in
accordance with 49 CFR 30.17, no contract shall be awarded to a contractor or
subcontractor who is unable to certify to the above. If the Contractor knowingly
procures or subcontracts for the supply of any product or service of a foreign
country on said list for use on the project, the Federal Aviation Administration may
direct through the County cancellation of the Contract at no cost to the
Government.
Further, the Contractor agrees that, if awarded a Contract resulting from this
solicitation, it will incorporate this provision for certification without modification in
each Contract and in all lower tier subcontracts. The consultant/ contractor may
rely on the certification of a prospective subcontractor unless it has knowledge
that the certification is erroneous.
The Contractor shall provide immediate written notice to the County if the
Contractor learns that its certification or that of a subcontractor was erroneous
when submitted or has become erroneous by reason of changed circumstances.
The subcontractor agrees to provide written notice to the Contractor if at any time
it learns that its certification was erroneous by reason of changed circumstances.
This certification is a material representation of fact upon which reliance was
placed when making the award. If it is later determined that the consultant/
contractor or subcontractor knowingly rendered an erroneous certification, the
Federal Aviation administration may direct through the County cancellation of the
Contractor subcontract for default at no cost to the Government.
Nothing contained in the foregoing shall be construed to require establishment of
a system of records in order to render, in good faith, the certification required by
this provision. The knowledge and information of a Contractor is not required to
exceed that which is normally possessed by a prudent person in the ordinary
course of business dealings.
This certification concerns a matter within the jurisdiction of an agency of the
United States of America and the making of a false, fictitious, or fraudulent
certification may render the maker subject to prosecution under Title 18, United
States Code, Section 1001.
AIMS System and Services Agreement – Attachment II
Page 5 of 9
Exhibit 3
Page 274 of 278
8.
TERMINATION OF CONTRACT (ALL CONTRACTS IN EXCESS OF
$10,000)
a.
The County may, by written notice, terminate this Contract in whole or in
part at any time, either for the County's convenience or because of failure to
fulfill the Contract obligations. Upon receipt of such notice, Services shall
be immediately discontinued (unless the notice directs otherwise) and all
materials as may have been accumulated in performing this contract,
whether completed or in process, delivered to the County.
b.
If the termination is for the convenience of the County, an equitable
adjustment in the Contract price shall be made, but no amount shall be
allowed for anticipated profit on unperformed Services.
c.
If the termination is due to failure to fulfill the consultant's/contractor's
obligations, the County may take over the work and prosecute the same to
completion by Contract or otherwise. In such case, the consultant/
contractor shall be liable to the County for any additional cost occasioned to
the County thereby.
d.
If, after notice of termination for failure to fulfill Contract obligations, it is
determined that the Contractor had not so failed, the termination shall be
deemed to have been effected for the convenience of the County. In such
event, adjustment in the Contract price shall be made as provided in
paragraph b of this clause.
e.
The rights and remedies of the County provided in this clause are in
addition to any other rights and remedies provided by law or under this
contract.
9.
SUSPENSION AND DEBARMENT REQUIREMENTS FOR ALL
CONTRACTS OVER $25,000 (AND FOR ALL CONTRACTS FOR
AUDITING SERVICES REGARDLESS OF THE AMOUNT)
The Contractor certifies, by submission of this proposal or acceptance of this
contract, that neither it nor its principals is presently debarred, suspended,
proposed for debarment, declared ineligible, or voluntarily excluded from
participation in this transaction by any Federal department or agency. It further
agrees by submitting this proposal that it will include this clause without
modification in all lower tier transactions, solicitations, proposals, contracts, and
subcontracts. Where the Contractor or any lower tier participant is unable to
certify to this statement, it shall attach an explanation to this solicitation/proposal.
AIMS System and Services Agreement – Attachment II
Page 6 of 9
Exhibit 3
Page 275 of 278
10.
RESTRICTIONS ON LOBBYING
The Contractor agrees that no federal appropriated funds have been paid or will
be paid by or on behalf of the Contractor, to any person for influencing or
attempting to influence any officer or employees of any federal agency, a Member
of Congress, an officer or employee of Congress, or an employee of a Member of
Congress in connection with the awarding of any federal contract, the making of
any federal grant, the making of any federal loan, the entering into of any
cooperative agreement, and the extension, continuation, renewal, amendment or
modification of any federal contract, grant, loan or cooperative agreement.
If any funds other than federal appropriated funds have been paid by the
Contractor to any person for influencing or attempting to influence an officer or
employee of any federal agency, a Member of Congress, an officer or employee of
Congress, or an employee of a Member of Congress in connection with this
System Agreement, the undersigned shall complete and submit Standard FormLLL, "Disclosure Form to Report Lobbying," in accordance with its instructions.
Contractor agrees to insert the foregoing provisions in any agreements between
Contractor or subcontractors engaged to provide Services pursuant to this System
Agreement and all contractors and subcontractors shall certify and disclose
accordingly.
11.
PROMPT PAYMENT - FOR FEDERALLY ASSISTED CONTRACTS
If the System Agreement is funded by any federal grants, then Contractor hereby
agrees to pay its subcontractors and suppliers within ten (10) calendar days
following receipt of payment from the County. Contractor further agrees, if
Contractor has withheld retainage from its subcontractors, to release such
retainage and pay same within ten (10) calendar days following receipt of payment
of retained amounts from the County, or within ten (10) calendar days after a
subcontractor has satisfactorily completed its work, whichever shall first occur.
This clause applies to both DBE and non-DBE subcontractors.
A finding of non-payment is a material breach of this contract. County may, at its
option, increase allowable retainage or withhold progress payments unless and
until the Contractor demonstrates timely payments of sums due subcontractor.
The presence of a "pay when paid" provision in a Contract shall not preclude
County inquiry into allegations of non-payment. Further that the remedies above
shall not be employed when the Contractor demonstrates that failure to pay results
from a bonafide dispute with its subcontractor or supplier. The Contractor shall
incorporate this provision into all subcontracts involving federally assisted
contracts.
AIMS System and Services Agreement – Attachment II
Page 7 of 9
Exhibit 3
Page 276 of 278
The Assistant Disadvantaged Business Enterprise Liaison Officer will conduct
meetings with parties involved in prompt payment disputes to facilitate an
amicable resolution
CONSULTANT'S AGREEMENTS THAT INCLUDE
CONSTRUCTION MANAGEMENT
Contractor shall provide to County an Engineer's Design Report, together with
plans and specifications.
AGREEMENTS FOR CONSTRUCTION
1.
CONSTRUCTION MANAGEMENT PLAN
Contractor shall provide to County a Construction Management Plan which shall
include a Quality Assurance Report.
2.
VETERAN'S PREFERENCE (ALL CONSTRUCTION CONTRACTS)
In the employment of labor (except in executive, administrative, and supervisory
positions), preference shall be given to veterans of the Vietnam-era and disabled
veterans. However, this preference may be given only where the individuals are
available and qualified to perform the work to which the employment relates.
3.
CLEAN AIR AND WATER POLLUTION CONTROL REQUIREMENTS
FOR ALL CONSTRUCTION CONTRACTS AND SUBCONTRACTS
EXCEEDING $100,000
Contractors and subcontractors agree:
a.
That any facility to be used in the performance of the Contract or
subcontract or to benefit from the Contract is not listed on the
Environmental Protection Agency (EPA) List of Violating Facilities;
b.
To comply with all the requirements of Section 114 of the Clean Air Act, as
amended, 42 USC 1857 et seq. and Section 308 of the Federal Water
Pollution Control Act, as amended, 33 USC 1251 et seq. relating to
inspection, monitoring, entry, reports, and information, as well as all other
requirements specified in Section 114 and Section 308 of the Acts,
respectively, and all other regulations and guidelines issued thereunder;
AIMS System and Services Agreement – Attachment II
Page 8 of 9
Exhibit 3
Page 277 of 278
c.
That, as a condition for the award of this contract, the contractor or
subcontractor will notify the awarding official of the receipt of any
communication from the EPA indicating that a facility to be used for the
performance of or benefit from the Contract is under consideration to be
listed on the EPA List of Violating Facilities;
d.
To include or cause to be included in any construction Contract or
subcontract which exceeds $100,000 the aforementioned criteria and
requirements.
AIMS System and Services Agreement – Attachment II
Page 9 of 9
Exhibit 3
Page 278 of 278
ATTACHMENT III
OFFSHORE STATEMENT
The Contractor (Air-Transport IT Services, Inc.) is a wholly owned
subsidiary of Fraport AG, Frankfurt Airport Services Worldwide, located at
60547 Frankfurt am Main, Germany.
AIMS System and Services Agreement – Attachment III
Page 1 of 1