INVITATION TO NEGOTIATE

26-XXX-ITN

MULTI-USER FLIGHT INFORMATION DISPLAY (MUFID) SYSTEM, OPERATION, MAINTENANCE, AND SUPPORT

GREATER ORLANDO AVIATION AUTHORITY

26-XXX-ITN

Multi-User Flight Information Display System, Operation, Maintenance, and Support

TABLE OF CONTENTS

GENERAL INFORMATION

INSTRUCTIONS TO RESPONDENTS

SCOPE OF WORK/SPECIFICATIONS

MINIMUM REQUIREMENTS

SMALL BUSINESS PROGRAM

INSURANCE REQUIREMENTS

OTHER REQUIREMENTS

PRICING

EVALUATION CRITERIA AND SELECTION PROCESS

VENDOR QUESTIONNAIRE

AVIATION AUTHORITY STANDARD TERMS AND CONDITIONS

SAMPLE CONTRACT AND CONTRACT INSTRUCTIONS

Attachments

A – display device list and locations

B – FIBER OPTIC EQUIPMENT AND ETHERNET HUBS

GENERAL INFORMATION

Project Summary The Aviation Authority is requiring qualified and experienced Respondents to provide all necessary software, software licenses, materials, supplies, labor, and professional services to design, configure, implement, content development, schedule and deliver content, operate, maintain and support the Respondent’s provided Multi-User Flight Information System (the “MUFID System” or “System”) Platform, at the Orlando International Airport. This Solicitation will result in a seven (7) years Contract to commence on or about XXX 1, 2026. The awarded Contract must be licensed to do business in the state of Florida and perform under the laws of the State of Florida. This ITN seeks:

a. To address the following being explored: What is the current status of technology for this purpose, what are the advantages and disadvantages of each technology and how can each be used for this solution; What lessons can be learned from other airports, large convention centers and theme parks?

b. To better understand the following facts: What is the typical pricing and risk model or the best pricing and risk model to best serve the needs and interests of the Aviation Authority?

c. A solution for using the latest technology for the installation, integration and maintenance of a Multi-User Flight Information System.

The MUFID System must operate using the existing components and equipment (listed on Attachments “A” and “B”) in conjunction with certain additional new equipment provided by the Authority and installed by the Contractor. During the term of this Contract, the Authority anticipates that certain components of the existing system shall require replacement or upgrade and the MUFID System provided for under this Contract must be capable of supporting these replacements and/or upgrades without interruption of operation. During the term of this Contract, the Authority will provide supplies, parts and operating system compatible equipment, and the Contractor shall provide the labor to install, operate, maintain, and support the equipment.

The Aviation Authority shall not be obligated to renegotiate or increase any price for any work during the initial term of the Contract based on a Respondent's mistake or miscalculation of prices, underestimation of costs, or for any other reason.

Disclaimer: Participation in this opportunity is voluntary, and the Aviation Authority will not pay/reimburse for the preparation of any information submitted by a respondent or for the Aviation Authority’s use of that information.

Background The Orlando International Airport (MCO), managed and operated by the Greater Orlando Aviation Authority (Aviation Authority), currently handles over 56.4 million domestic and international passengers. MCO experienced a 14.5% growth in passenger traffic in the 12 months ended June 2025 compared to the 12 months ended June 2019, including 16.3% growth in international passenger traffic which now stands at over 8.2 million passengers annually. MCO is currently served by 39 commercial passenger airlines and 7 cargo carriers. Orlando International Airport (MCO) is the busiest airport in the State of Florida and has been ranked the 9th busiest airport in the United States and 25th in the world.

The Aviation Authority is committed to ensuring quality services and a seamless passenger journey through exceptional experiences, collaboration, and creativity, by focusing on People, Connection, Community, and Innovation.

Definitions Airport – Refers to MCO and/or ORL.

Agency – Means any official, officer, department, board, commission, division, bureau, section, district, office, authority, committee, or council, or any other unit of organization, however designated, of the executive branch of state government, and the Public Service Commission.

AIDB – Airport Integrated Data Broker AOC – Airport Operations Center ASP – Application Service Provider Aviation Authority Board – The objective of the Aviation Authority Board is to administer the provisions of the Florida Legislative Act that created the Greater Orlando Aviation Authority. Its purpose is to serve the public interest through the coordination of the planning, financing, construction, and operation of the aviation facilities operated by the Aviation Authority in Orlando, Orange County, FL.

Aviation Authority – See Greater Orlando Aviation Authority.

Aviation Authority Authorized Representative (“AAR”) – Refers to the Aviation Authority-designated employee responsible for specific functions for daily coordination of all activities under the executed Contract.

Award Recommendation (“Recommendation to Award”) – Refers to the proposed consideration of contract award to a responsive and responsible bidder.

BAFO – Refers to “Best and Final Offer” and is the most definitive and advantageous pricing to the Aviation Authority submitted by a Respondent for a specific solicitation.

Best Value – Refers to the greatest overall benefit in response to the requirement; This can that include quality, design, craftsmanship, delivery, etc. When assessing the best value, price is not the most important factor that is considered.

BIDS - Baggage Information Display System BPEL – Business Process Execution Language Competitive Range – Refers to the range of replies reasonably susceptible of award of an ITN solicitation. Only Respondents in the competitive range are considered for negotiations.

Contract – Refers to an executed agreement between parties with binding legal and moral force, for the provision of goods and/or services in exchange of money or other type of compensation.

Contractor – Refers to any individual or business who has been awarded a contract.

Display Devices – LCD and LED Display Devices.

Display Device Controller (DDC) – Computer hardware that requires no end-user interaction used to drive the FIDS monitors. Dynamically update the Flight Information Display System (FIDS) pages on airport monitors. Delivers real-time content and page layouts to displays.

Greater Orlando Aviation Authority (“Aviation Authority”) – Means the local governmental agency created by action of the Florida State Legislature for the purpose of developing and operating aviation facilities in Orlando, Orange County, FL, i.e., managing and operating MCO and ORL. The Greater Orlando Aviation Authority is, in turn, directed and governed by the Aviation Authority Board.

Hardware - Objects that you can touch, like servers, disk drives, Display Devices, keyboards, tape drives, and chips.

ITN – Means Invitation to Negotiate and refers to a competitive solicitation process intended to obtain the best value by means of achieving a specific goal through direct negotiations with one or more responsive and responsible bidders, prior to an award recommendation.

ICAO - International Civil Aviation Organization.

INTERNATIONAL AIR TRANSPORT ASSOCIATION (IATA) - The governing Body that creates regulations for international air transport.

IT - Information Technology LAN - Local Area Network List-of-Values - A scrollable pop-up window that provides the end User with a single or multi-column selection list.

MCO – Refers to Orlando International Airport in the City of Orlando, Orange County, State of Florida, United States of America.

MUFID – Respondent’s Multi-User Flight Information Display Platform MUFID Equipment – Multi-User Flight Information Display Equipment MUFID System - The hardware and software components that run the servers and Display Devices, having the ability to collect, store and display flight information (arrival/departure, gate, and related information).

MUFID System Application - A program or group of programs designed for end users. This includes Report Generation Programs, Input/Entry Programs, and Database Management Systems.

MUFID System Database - A relational database management system (RDBMS) that stores data in the form of related tables. Relational databases are powerful because they require few assumptions about how data is related or how it will be extracted from the database. As a result, the same database can be viewed in many different ways.

Network Basic Input Output System (NetBIOS) - An API that augments the DOS BIOS by adding special functions for local-area networks (LANs).

Negotiation Team – Refers to a group of professionals who review responses to an ITN and negotiate with responsive and responsible Respondents to secure a BAFO for the Solicitation.

Notice of Award – Notification letter to a Respondent stating that the contract has been awarded to them in accordance with their response to the Solicitation requirements. This allows for work coordination to commence while the contract is drafted for execution.

Notice of Intent to Award – Public notice issued to announce an intended award and to also signal the beginning of the time period allowed for protest submittals.

Notice to Proceed – Notification letter to a Respondent that marks the beginning of the contracted performance period. It serves as official approval for the Contractor to begin work.

ORL – Refers to Orlando Executive Airport in the City of Orlando, Orange County, State of Florida, United States of America.

Performance Deduction – Refers to the monetary deduction applied to the Contractor’s monthly invoice based on the AAR’s evaluation of the Contractor’s performance.

Quality Assurance – Refers to a planned and systematic approach to ensure adequate service requirements are established; that the services conform to established requirements; and that satisfactory performance is achieved. Quality Assurance refers to actions by the Aviation Authority to determine whether the Contractor’s performance conforms to the Scope of Work.

Quality Control – Refers to a program developed by the Contractor to ensure that its services meet the requirements of the Aviation Authority.

Rentable Space – Refers to unoccupied areas inside airport terminals that are available for revenue generation.

Respondent (“Bidder” or “Proposer”) – Refers to an individual or business submitting a response to a Solicitation.

RGU - Report Generator Utility.

RMS - Resource Management System.

Solicitation – Document package used to request responses for the purpose of entering into a Contract with the Aviation Authority.

SMS – Short Message Service SOA – Service-Oriented Architecture SOP – Refers to Standard Operating Procedure, a set of step-by-step instructions designed as guidance to carry out routine operations and consistent practices.

Staffing Schedule – Refers to a staffing schedule submitted by the Contractor and approved by the AAR identifying the positions to be filled by personnel of the Contractor in performance of this Contract and the minimum number of personnel that shall be working in each such position during the schedule period.

TCP/IP - Transport Control Protocol / Internet Protocol.

UOM – Refers to Unit of Measure, a standard/definite magnitude of a quantity.

USER – Authority staff or other designated personnel authorized to access the MUFID System and its data.

VDC - Video Display Controllers.

WAP Capabilities – Wireless Application Protocol Wayfinding - Enabling a person to find his or her way to a given destination using effective signage.

WEB FIDS System - A part of the MUFID System that provides the public with real-time flight information, via the internet.

WSDL – Web Service Definition Language XML – Extensible Markup Language Characteristics of an ITN An ITN is a solicitation process to select one or more vendors with which to commence negotiations for the procurement of goods and/or contractual services.

When the Aviation Authority determines that procurement by an Invitation to Bid or other solicitation method is not in the best interest of the Aviation Authority, and that negotiation may be necessary for the Aviation Authority to obtain the Best Value, the ITN process may be used. In making the determination to utilize the ITN process, the Aviation Authority may consider, in addition to any other relevant considerations, the following:

a. The simultaneous use of competitive negotiations would be beneficial to achieve the goal of Best Value within the Aviation Authority’s budget.

b. Price is an important factor but not significant enough by itself to justify award to a low bidder.

c. Limited availability of competition.

d. Non-standard products or services are required.

e. Multiple options for achieving the desired results likely exist.

f. A contract of high complexity may be required.

g. Uncertainty of the ability to obtain results within the budget or time requirements.

h. Requirements for needed products or services cannot be specified with certainty.

i. There is an emphasis on new technology with innovative solutions and a range of options are available.

j. Flexibility in determining the Best Value for the Aviation Authority is paramount.

k. Items or services are mission critical to the Aviation Authority’s operation.

l. A process of re-engineering may be required.

m. The marketplace is experiencing constant change and updated solutions are pertinent.

Professional and technical expertise and qualifications of firms are critical to the success of the project or provision of services.

Americans with Disabilities Act (ADA) The Aviation Authority does not discriminate upon the basis of any individual’s disability status. Anyone requiring reasonable accommodations as provided for the Americans with Disabilities Act or Section 86.26, Florida Statutes, should contact the ADA Coordinator at 407-825-2006 as soon as possible, at least one full business day prior to any scheduled meeting.

Responsible Vendor Determination Respondents are hereby notified that Section 287.05701, Florida Statutes, requires that the Aviation Authority may not request documentation of or consider a vendor's social, political, or ideological interests when determining if the vendor is a responsible vendor.

Notice of Intent to Award Contract Unless all Responses are rejected by the Aviation Authority, a Notice of Intent to Award is anticipated to be provided within 120 days from the opening of received responses to the responsible and responsive Respondent submitting a Response deemed to be most advantageous to the Aviation Authority, all factors being considered after a BAFO is received. For all procurements, the Aviation Authority reserves the right to reject any or all Responses and to cancel the procurement or to solicit new Responses.

Public Meetings/Public Records Please be aware that all meetings of the Aviation Authority’s Board and Procurement Committee are duly noticed public meetings and all documents submitted to the Aviation Authority as a part of or in connection with a Solicitation will constitute public records under Florida law regardless of any person’s claim that proprietary or trade secret information is contained therein. Public meetings are posted on the Aviation Authority's website: https://flymco.com/airport-business/sunshine-meetings/. The Negotiation Team meetings will be conducted in accordance with Florida Statute 286.0113.

Code of Ethics and Business Conduct Policy The Aviation Authority has adopted a Code of Ethics and Business Conduct Policy # 101-02, which addresses the obligation of the Aviation Authority’s Board members and employees to follow the Florida Statutes in reference to these issues. A copy of this policy (101.02) is available on the Aviation Authority’s website: https://flymco.com/airport-business/policies/ Non-Governmental Entity Declaration Regarding the Use of Coercion for Labor and Services Contractor shall complete the affidavit “Non-governmental Entity Declaration Regarding the Use of Coercion for Labor and Services”, per the Anti-Human Trafficking Affidavit Sub-section.

INSTRUCTIONS TO RESPONDENTS

Response Submittal

a. To successfully submit a response to a Solicitation, Vendors are required to submit their electronic response via OpenGov - https://procurement.opengov.com/portal/goaa.

b. Sealed electronic responses will be received for this Solicitation through the Greater Orlando Aviation Authority e-Procurement Portal (Portal) located at https://procurement.opengov.com/portal/goaa. By way of the Portal, responses will be locked and digitally encrypted until the submission deadline passes.

c. Mailed, faxed, emailed, and hand delivered submissions will not be accepted. Responses will only be accepted via OpenGov.

d. The Aviation Authority shall not be responsible for delays caused by any occurrence, including a technology issue. Any late response will not be accepted.

e. The time/date stamp clock located in the Portal shall serve as the official authority to determine lateness of any response.

f. Respondents shall submit one Response only.

Submitting Questions and Receiving Responses Respondents shall submit all inquiries regarding this Solicitation via the e-Procurement Portal, https://procurement.opengov.com/portal/goaa. Please note the deadline for submitting inquiries. All answers to inquiries will be posted on the Aviation Authority e-Procurement Platform. Respondents may also click “Follow” on this Solicitation to receive an email notification when answers are posted. It is the responsibility of the Respondent to check the website for answers to inquiries.

Lobbying Statement Do not contact Aviation Authority Board members or Staff concerning this Solicitation. Public meetings and public deliberations of the Evaluation Committee are the only acceptable forum for the evaluation of any Responses received pursuant to this Solicitation. Written correspondence concerning questions may be submitted to the Procurement Services Department via the e-Procurement Platform during the specified period. Any official communication from a Respondent during the Solicitation process should be submitted in writing to the Greater Orlando Aviation Authority via the e-Procurement Platform as directed in the Solicitation. Copies of the Aviation Authority's Policies (Sections 180.01 and 180.03) are available at https://flymco.com/airport-business/policies. Failure to adhere to these requirements could result in action to disqualify your firm from consideration of the award. Respondents to this Solicitation or persons acting on their behalf may not contact, between the release of the Solicitation and the end of the 72-hour period following the agency posting the notice of intended award, excluding Saturdays, Sundays, and state holidays, any employee or officer of the executive or legislative branch concerning any aspect of this Solicitation, except in writing to the procurement officer or as provided in the Solicitation documents. Violation of this provision may be grounds for rejecting a response. (F.S. 287.057 (25)) Proprietary Information

a. In accordance with Chapter 119 of the Florida Statutes (Public Records Law) and except as may be provided by other applicable State and Federal Law, all Respondents should be aware that the Solicitation and the responses thereto are public records. However, the Respondents are requested to identify specifically any information contained in their Response, which they believe to be exempt from disclosure, citing specifically the applicable exempting law. The Aviation Authority will consider Respondents' opinions regarding the applicability of Chapter 119, Florida Statutes, but shall not be obligated to concur in such opinions.

b. All information and documents received from Respondents in response to this Solicitation will become the property of the Aviation Authority, will not be returned to the Respondents, and will be incorporated in the final Agreement in the event of Agreement award, with the exception of any financial information exempt from the Public Records Laws. Any work product produced as part of the Agreement will become the exclusive property of the Aviation Authority.

Performance and Invoicing

a. The Aviation Authority shall, at regular intervals, monitor the performance of the Contractor to determine whether the work to be performed under the Contract has in fact been accomplished to the Aviation Authority’s satisfaction and/or completed in a timely manner.

b.

c. The Aviation Authority shall notify the Contractor of any specific services that are unsatisfactory to the Aviation Authority, and if the Contractor has not addressed such item or items set forth in the notice to the Aviation Authority’s satisfaction within the time frame set forth in the Aviation Authority’s notice, the Aviation Authority in addition to all other rights provided under this Contract or by law or equity, may either remedy such unsatisfactory services itself or through a third party and the cost of providing the remedial services shall be deducted from the Contractor’s invoice.

d. The Aviation Authority shall pay the undisputed amount of Contractor’s invoice per The Florida Prompt Payment Act. Items in dispute shall be paid upon the resolution of the dispute in accordance with the Florida Prompt Payment Act.

e. The Contractor’s invoice shall generally describe the services rendered by work area and location, type of service, date rendered, and shall contain such other information and is accompanied by such supporting documentation and other materials as the Aviation Authority shall request. The forms to be used will be provided by the Contractor, with approval of the Aviation Authority.

f. The Aviation Authority will reimburse the Contractor for reasonable freight and shipping charges incurred with respect to any such reimbursable items, at actual cost, for which parts, materials, equipment rental and other reimbursable items are approved in writing by the Aviation Authority in advance of such shipment. The cost of overnight delivery shall be approved in writing in advance by the AAR.

g. Contractor shall be obligated to pay promptly all proper charges and costs incurred by Contractor for labor and materials used for the work performed hereunder. The Aviation Authority shall have the right, but not the obligation, to pay directly to third parties (including Subcontractors) all past due amounts owed by Contractor to third parties for labor and materials used for the work hereunder, based on invoices submitted by such third party, and all such amounts paid by the Aviation Authority shall be applied toward, and shall reduce, amounts owed to Contractor hereunder.

h. The Contractor shall submit all invoices to: Greater Orlando Aviation Authority, Finance Manager, P.O. Box 620125, Orlando, Florida 32862-0125. Invoices may be sent electronically to accounts payable goaa-ap@goaa.org Pricing, Payment, and Freight Terms

a. Provide pricing in OpenGov, using the pricing table and the Authority's excel pricing form. Responses in any other format (such as a quote on the Respondent’s template) will not be accepted or reviewed.

b. Unit prices provided must be valid for at least seven years from the date of contract execution. Anticipated increases in Respondent's costs during the term must be reflected in its prices set forth in its response.

c. The Aviation Authority shall not be obligated to renegotiate or increase any price on a Respondent's mistake or miscalculation of prices, underestimation of costs, or for any other reason. All of the Respondent's overhead costs, including, but not limited to, costs of the required bonds and insurance coverages, shall be included in such Respondent's prices listed in its Solicitation.

d. Freight Terms are FOB Destination, Freight Prepaid. Respondent pays and bears the freight charge, owns goods in transit and files claims if any.

e. Payment Terms are Net 45

f. Unit prices provided shall be for materials/items/parts/equipment that are new, unused, or a current year and model, and are fully supported by the manufacturer’s warranty to the initial purchaser, as applicable.

g. The Aviation Authority is exempt from Federal excise taxes and all sales taxes.

SCOPE OF WORK/SPECIFICATIONS

Overview The Multi-User Flight Information Display System (MUFIDS) is a mission-critical component of the Orlando International Airport (MCO) designed to provide real-time flight information to passengers, airport staff, and airline partners. MUFIDS supports the seamless display of arrivals, departures, gate assignments, and other operational data across the airport campus. The system plays a vital role in passenger wayfinding, operational coordination, and overall customer experience.

MCO’s MUFIDS infrastructure has evolved over time to accommodate increasing passenger volumes, expanded terminal facilities, and enhanced data integration with airline and airport systems. The system is designed to support multiple stakeholders simultaneously, ensuring consistent and accurate information delivery across all display endpoints.

Scope of Work

a. The Contractor shall provide a Multi-User Flight Display (MUFID) system platform, content, content development, content delivery software, labor, supervision, professional services, user interface software, software to control display devices, server software, tools, licenses, materials, and all other items necessary for the design, programming, content, delivery, installation, integration, testing, system and administration documentation, training, operation, maintenance, repair, and support for the MUFID platform and software provided by the Contractor at the Orlando International Airport (“MCO”), in accordance with this Specification.

b. The System must operate using the existing components and equipment (Attachments “A” and “B”) in conjunction with certain additional new equipment provided by the Authority and installed by the Contractor. During the term of this Contract, the Authority anticipates that certain components of the existing system require replacement or upgrade, and the System provided for under this Contract must be capable of supporting these replacements and/or upgrades without interruption of operation. During the term of this Contract, the Authority will provide supplies, parts and components, and the Contractor shall provide the labor to install and maintain the equipment at peak performance.

c. The System Platform to be provided and installed by the Contractor shall operate or work in conjunction with other equipment and systems, such as, but not limited to:

1. Gate Information Display System (GIDS)

2. Baggage Information Display System (BIDS) (Manufacturer: DAKTRONICS)

3. Local Information Display System (LIDS)

d. At a minimum, the System must be capable of interfacing with the following systems:

1. Individual Airlines interface flight data directly into MUFIDS (Currently American Airlines, Delta Airlines, Frontier, JetBlue, Southwest Airlines, Spirit, and United Airlines)

2. Passur (RightETA feed for arriving flights). The Respondent could propose their own solution for arriving flights ETA.

3. Brightline (to display train schedules on designed displays)

4. Veovo RMS (bi-direction exchange of aircraft detail)

5. Weather (via Weather Icons or comparable)

6. Beonic Skyfii (checkpoint wait time data for display on designed displays)

7. Flight Insight (Maps for display on designed displays)

8. Outbound data feeds to display flight details (MCO Website, Dynamic Signage system, and Interactive Voice Response (IVR))

9. ATLASIED Text to Speech Courtesy Announcement System (TCAS) - Visual Paging

e. The System shall provide the capability to perform visual paging and shall have the capability to create and maintain public information messages, which shall be displayed on areas designated (via a specific display format) through either static or dynamic messages. These shall be free-text messages and allow Users to specify the format of how these messages are displayed on Display Devices (i.e. font size, text color, duration of message display before automatic deletion, static or dynamic display, scrolling rate, etc.).

f. At a minimum, the System shall be able to display the following information on the Display Devices located throughout the Airport, and for all airline flights operating at the Airport, as approved by the AAR:

1. Airline

2. Flight Number

3. Flight Origin or Destination

4. International Flight Marker (i.e., whether or not the flight requires Federal Inspection Services (F.I.S.) clearance at the Airport)

5. Time of Arrival or Departure

6. Gate Assignment

7. Flight Status (e.g., On-Time, Delayed, Boarding, etc.)

8. Baggage Claim Assignment

9. Airline Logo

10. Current Date and Time

11. Code Shares/Partners

g. The System must generate the displayed information from data obtained from the System’s communication with individual Airlines and/or third-party data feeds.

h. The Contractor shall coordinate with the AAR prior to making any connections to the Aviation Authority's LAN. The connection from the System network to the Aviation Authority's LAN shall be accomplished via a routed interface. The application provided must support operation through this router interface. All applications provided shall communicate via unicast or multicast TCP/IP. The Contractor shall provide the AAR with a list of the IP communication ports that are used and the purpose of each of the ports. It is the Aviation Authority’s intent to have the communications accomplished through designated IP ports, rather than random IP port assignment.

1. The System shall operate on the Aviation Authority’s common network infrastructure.

2. The Authority’s LAN is configured as follows:

a. Network Topology: Switched Ethernet, 100/1000

b. Network Protocol: TCP/IP (assigned by the Aviation Authority)

c. Network Wiring: Cat 6 & 6A UTP

d. Network Fiber Optic Cable: 9-micron single mode fiber optic cabling.

3. Any cabling that is installed by the Contractor shall be labeled and recorded in accordance with the Aviation Authority’s established standards.

i. The System shall interface with the Aviation Authority’s network in a manner that allows an Aviation Authority employee (with the appropriate password security access) to utilize the Aviation Authority’s LAN and workstations or devices located throughout the Airport to operate, at a minimum, the MUFID System’s functions as described in the Specifications.

System Features and Functions

a. At a minimum, the System shall accommodate the following capacity criteria:

1. 40,000 flights per month, with expansion capabilities to 60,000 flights per month without any hardware or software modifications.

2. 400 airlines, using an IATA 2-letter identifier code with text and an ICAO 3-letter identifier code with text.

3. 200 gates.

4. 1,500 Display Devices (addressable) with expansion capabilities to 2,500 Display Devices (addressable). The location and quantity of the Display Devices are to be determined by the Aviation Authority. Attachment “A” is provided solely to show the locations of the existing Display Devices operated by the existing system.

5. 1,000 destination cities, using an IATA 3 letter identifier code and text.

6. Multiple display location designators (example: Monitor #37, Gate 46, bank 5, group 3, Airside 1, all airsides, main terminal, all Airport).

b. The System must provide a messaging interface to accomplish an exchange of data between the system and the Authority’s Airport Integrated Data Broker (AIDB). The AIDB deploys Service-Oriented Architecture (SOA) Web Service Definition Language (WSDL) services based on Business Process Execution Language (BPEL). These services are utilized to broker data transactions between the MUFID System and Aviation Authority’s Resource Management System (RMS) system. The System must be able to send specially formatted data describing events, requests, and replies to the AIDB.

c. The System shall have the capability to create and display an Aviation Authority approved carrier logo as a color graphic in place of or adjacent to the alphanumeric designation of the carrier’s name or flight.

d. The System shall perform the following functions:

1. Seasonal Flight Schedules: The seasonal flight schedules shall contain data for all flights within the schedule period, at a minimum including flight number, flight origin and destination, time of arrival or departure, validity period, operational days, and aircraft type. The seasonal flight schedule will be used to create the daily flight schedule. The System shall allow a User to modify, delete, or create the seasonal flight schedule information, using all related information and data available from the systems to be interfaced with as outlined above, and provide the ability to display, archive and print.

2. Daily Flight Schedules: Creating daily flight schedules from the seasonal flight schedule. The daily flight schedule is used for the storage of operational flight information for the day. The daily flight schedule is automatically created after midnight each day for the current day plus several days ahead. The previous daily flight schedule shall be transferred to a temporary storage location (database table) and later archived, before being purged from the database. The System Application shall be designed to allow an authorized User to create, modify, and delete, update for viewing, and printing of flights from the daily flight database.

3. Stored Data: The System Application shall allow accessing of stored data as requested by Aviation Authority staff or other designated personnel (herein after referred to as “User”) authorized to access the System and its data, for up to one year.

4. Public Message/Flight Status: If an estimated time is entered into the System and it differs from the scheduled time, a public message shall reflect the change in the Flight Status section accordingly.

5. Baggage Claim: The capability to display inbound flight information with claim device assignment shall also be provided. Flights shall be either automatically or manually removed from any baggage belt signage. Automatic removal shall occur after an adjustable designated time period.

6. Flight/Gate Status: Flight/Gate status shall indicate, but not be limited to: Gate Open, Boarding, Final Call, Flight Departing, Flight Closed, etc.

7. International Flight Information: Provide a Post-Cleared International Flight page within the MUFIDS system for users to access and a password protected Post-Cleared International Flight web page to be accessed by the appropriate U.S. governmental agencies.

8. Content: Provide the ability to drive custom content across designated location of the environment which may consist of an individually, segmented, grouped or combinations of areas for display.

a. Content schedules shall be available for the Aviation Authority to manage which content is displayed when and to which defined areas.

e. The System shall provide the following reports from the System’s data.

1. Cross Reference Tables: Shall produce several fixed data tables and provide printouts for every fixed data table. The report shall show the entire table content. The System Application shall allow the tables in the files to be viewed, created, deleted, updated, and printed. At a minimum, the following fixed data tables shall be included (listed in alphabetical order):

a. Aircraft Registration

b. Aircraft Type

c. Airline

d. Baggage Claim Device Assignment

e. Destination Airport City Name and City Code (for a minimum of three cities per flight)

f. Gate Assignment

g. Change History

h. International Status

i. Number of Seats per Flight

j. Originating Airport City Name and City Code (minimum of three cities per flight)

k. Public Message/Flight Status

l. System User Profiles

2. Graphical Presentations: Shall produce a complete graphical presentation of data in the System, to be viewed, created, deleted, updated, and printed, including but not limited to generating bar charts and other graphs as requested by the Aviation Authority. This shall be generated by user-friendly, point and click query of any attribute or combination thereof from the Cross Reference Tables.

3. Audit Trail: Shall have the standard functionality to identify the User who last updated each record and the date that each record was last updated. Track User’s actions and functions performed in the application(s). This feature must track the System User ID, logged-in station ID or IP Address, and a list of transactions made during the logged-in session. Reporting features shall allow for grouping of audit details on actions against a record, actions performed by an individual and configuration changes made to the application. A purge archive routine shall be available for the system administrator to remove audit trail history.

4. Report Development Application: The automated report writing component must contain a graphical user interface running on the Aviation Authority’s Windows platform (currently, 11) which allows quick and easy creation of reports by following a set of selected dialogues. The User must be allowed to cut, copy, and paste between different reports. The use of graphic objects like lines, rectangles, round rectangles, ellipses, and polygons can be drawn on reports as pictures, borders, surrounds, and underlines. They can be filled with different colors, drawn in different pen styles, using either solid or dotted lines. Static elements such as headings, titles and other information shall be placed in the report. Text fonts, colors, and alignments shall be definable. A date/time cell shall be placed on a report definition so that the date and time of printing appears on all reports. The automated report generator utility (RGU) shall be capable of placing columns (with or without borders) on reports. Columns displaying text from database tables shall be selected and/or sorted as required when the report is printed or viewed. Columns and fields shall also be capable of containing results of calculations or queries on the data. Pictures, spreadsheets, text and data from other programs shall also be included in reports generated by the RGU. The report development application must support data selection and data ordering rules, calculations on database fields, and allow the use of dynamic data to dynamic data linking. Functionality and capabilities of the report development application must be fully documented. Provide an automated RGU to provide various reports as needed by the Aviation Authority to meet requirements.

f. The System shall automatically generate statistical reports, at a time predetermined or specified by the User. The reports may also be requested manually. At a minimum, reports shall consist of the following information as determined by the User:

1. The System Application shall allow the User to query, sort, and edit the data for viewing, printing, or downloading to any other Windows application.

2. The flights (arrival/departure/total) are common based on the User’s defined criteria, either cumulative or specific by any selected combination of criteria. The criteria include, but not be limited to, arrival and departure times (both scheduled and actual), Gate(s), Wing(s), Airside(s), Airline(s), and date(s), both historical, current and/or future.

g. The System shall provide two types of event logging for a minimum archival period of three (3) days:

1. Log Messages that shall be stored in the System Application and shall be available to be printed or exported upon a User's request.

2. Data Communication Messages that shall be written on a log file.

h. Information Distribution System: Display Devices shall show information in the format as designed by the User. When a record is updated, any Display Device that is displaying that record or portions of that record shall reflect the updated information within a maximum of thirty seconds.

1. All display screens are to be always filled with the appropriate flight information. If the normal time period for displaying flights does not generate enough lines of flight information to fill the screen efficiently and clearly, then flight information that extends beyond the normal time period or other content as approved by the AAR, should be displayed until all Display Devices are filled.

2. When the flight information spans two days, the System shall clearly delineate the different days, in a format subject to the approval of the Aviation Authority. The User shall have the ability to modify the System’s delineation of two days flight information.

3. As part of the System Application, the following information may be displayed either as a text field or a logo screen, and at a minimum shall include (but is not limited to):

a. A full-screen color graphic carrier logo.

b. The Aviation Authority logo.

c. Static and/or Dynamic Video Advertising for Airport services.

d. Airport facility information to include but not limited to directional maps, wayfinding messages, etc.

i. The System shall incorporate security features to ensure the integrity of each airline’s flight information, and to ensure that airlines have access solely to their own flight information and are prevented from revising, modifying, or in any manner altering the flight information of any other airline.

j. The design of the System shall allow the Aviation Authority to replace existing hardware, including replacement with upgraded or approved alternate hardware, during the term of this Contract without affecting the integrity of the MUFID System or information displayed at the time of replacement. The System shall accommodate expansion without degradation to the System’s performance. The System shall not be interrupted for expansion without prior approval of the AAR. The communication network between the host computers and the Display Device Controllers shall be a TCP/IP network utilizing Ethernet for media access control. The Aviation Authority will provide the Contractor with a range of IP addresses to be used for the System. The Contractor shall provide the Aviation Authority with a spreadsheet showing the assignment of addresses for all devices on the System network, including IP address, MAC address, system/device name and system/device location, etc. The Contractor shall provide the AAR an updated spreadsheet within 24-hours after IP address changes, additions, or deletions, throughout the term of the Contract.

1. The System shall support several types of Display Devices which are commercially available from sources other than strictly from the Contractor or its agents.

k. The Contractor shall function as an Application Service Provider (ASP) for the Aviation Authority. All administration, repairs, maintenance and data protection and recovery are to be managed by the Contractor.

1. MUFID System Server Solutions: The Contractor must provide the Aviation Authority with MUFID System server solutions and its components that provide the following:

a. The solution should have an open system architecture able to run on VMware or Hewlett Packard Enterprise Servers using Red Hat Linux or Microsoft Windows operating system.

b. Utilize teaming Network Interface capability of Ethernet 100/1000.

c. Support hardware redundancy and server failover capability to ensure availability 99% uptime of the solution.

d. Backup and recovery capabilities for the solution.

e. Performance to handle up to 2,500 displays and 70 Users.

f. Able to support commercial Anti-Virus Software with frequent scheduled updates and scans.

g. Able to support solution failover to accommodate monthly OS patching of hardware maintenance with minimal disruption

h. Support the database residing on the Authority’s Dh2i SQL Server HA clustering data farm or Oracle database server with Data Guard

l. The proposed System shall include a powerful but simple User Interface for operation as well as managing data and individual applications. The user experience shall, to the extent feasible, be web-enabled to provide additional flexibility for the users of the System, including the ability to provide secured access from various workstations and devices (laptop, PC, iPad, mobile device, etc.).

m. The Contractor shall ensure that the User’s interface to the System shall be a GUI (Graphical User Interface) that is user-friendly. It shall be compliant with industry standards.

1. All modules (i.e., end-user interface, reports, content, etc.) shall have an easy-to-use Graphical User Interface (GUI).

2. Software GUI shall be accessible via standard web browser using secure protocols.

n. The System shall perform data validation in the appropriate fields during data entry and update to ensure the integrity of data content.

o. The proposed System shall be secure and follow the Aviation Authority Cybersecurity requirements for operation and access. The System shall utilize assignable levels of security and access level for each System User which shall define which functions are available to a User with a given security level (i.e., carrier employees cannot view or edit any flights other than their own).

p. The Contractor shall perform periodic testing to ensure the integrity of the System’s security infrastructure. The Aviation Authority may request from the Contractor results of penetration (PEN) testing, or the Aviation Authority may conduct their own Audit of the system as they deem necessary.

q. The proposed System shall provide administrative and user roles for access to system features. These roles shall be customizable by user function.

r. The System shall have on-line help available for the User, which shall be context sensitive and provide hypertext links to other related help topics within the help system.

s. Database licenses required to support existing Display Devices are to be provided by the Contractor. The licensing shall allow the Aviation Authority to increase to up to 2,500 Display Devices and 70 Users. The number of licenses shall expand as needed when displays are added.

t. The System shall contain a screen designer system which shall allow the User to create visual screen formats. Using the screen designer, the User shall be able to specify at least the following for a screen format:

1. Font type, style, and size.

2. Color attributes – foreground, background, per data or text field.

3. Blink and Blinds attributes – colors, rates of definition of when to blink or blind.

4. Header and footer – content, format, placement.

5. Color graphics – exact placement and scaling/sizing.

6. 3-D effects.

7. Background wallpaper.

8. Scrolling fields – left, right, up, down, rate.

u. Assumptions and Constraints:

1. The System has the capability to provide data at the highest level of granularity (i.e., details) to support different integration requirements.

2. The System has the capability to accept record level and field level information updates.

3. The System has the capability to accept Master Table changes while in full operation.

4. The System has the capability to buffer, queue, prepare and send/receive messages to a middleware integration platform.

5. The System has the capability to validate, to process and to apply business rules prior to data insertion.

6. The System has the capability to enforce referential integrity rules.

7. The System has the capability to send acknowledgments and statuses.

8. The System has the capability to generate and manage unique transmission identifiers in addition to unique record Ids.

9. The System has the ability for integration via API, message broker or middleware system using point-to-point and publish/subscribe messaging models.

10. The System has a mechanism to accept Push and Pull technologies.

11. The System has a mechanism to accept Time Synchronization with a standard Network Time Protocol (NTP).

12. The System has the capability to maintain dual interfaces with the System’s Integration Platform to provide redundancy of information.

13. The System has the capability to connect, to authenticate and to maintain valid connection with a middleware integration platform.

v. General Interfacing Rules:

1. Where it applies, all Flight Information shall be expressed and communicated in IATA standard format; including the IATA XML standard, all other standards (e.g. FAA or ICAO) shall be converted to its equivalent IATA standards.

2. All Flight times shall be expressed in Universal Time Coordinate (UTC) format; however, information could be displayed in either UTC or Eastern Standard Time (EST) format.

3. All Flight information shall be maintained inside the MUFID System for at least three days with the ability to retransmit the information to other systems if required.

4. In case of connection failure, all flights records should be held in a transmission queue. The system should have the capability to purge information from the transmission queue and refresh it with a new snapshot of all records based on a time-rule criteria.

5. Future systems upgrades, security patches and fixes shall not be conducted without coordination with other integrated systems. In addition, any interface modification should not require the MUFID System to go through a complete shutdown to reload or restart.

Hardware Requirements

a. General Requirements

1. The Contractor shall utilize the existing owner furnished equipment (OFE) used to support the existing system to the greatest extent possible. The Contractor shall be responsible for recommending any additional configured hardware necessary for a fully functional system to meet the functional and technical requirements specified herein.

2. All hardware provided by the Aviation Authority shall be tested and validated for use within the MUFIDS system.

b.…