Exhibit_7_Demonstration_Script.pdf

Respondent Demonstration

As part of the procurement process the shortlisted Respondent(s) will be required to demonstrate their proposed solution. The demonstrations by the shortlisted respondent(s) will be part of the overall evaluation process and will be held onsite at the Authority. The Authority will provide the system environment for the Respondent(s) to load, configure and demonstrate their proposed solution. This environment will include similar hardware found in the field at MCO and will include two servers, multiple video extenders and a minimum of eight (8) displays to make up a display canvas. The shortlisted respondent(s) will be required to distribute and play content, demonstrate their system capabilities per the compliance matrix in the RFP and perform the final demonstration script with their proposed software/solution.

The following provides the anticipated demonstration script that will be required to be performed by shortlisted Respondent(s). Although not final, and changes could be made during the procurement process, the demonstration will require the Respondents to demonstrate their proposed solution in the following areas:

1. Acting as an Airport Operations Center (AOC) coordinator, demonstrate the full capabilities of the “manual override” or Command and Control features of the system to the scheduled content for all sizes of display canvases, canvas types and data as part of the environment.

2. Demonstrate an Airline Ticket Counter Backwall utilizing the full demonstration canvas.

Demonstrate how parts of the content can be changed as airline operations change on the fly, such as changes in ticket counter designations (bag drop, business class, full service, etc.) as well as airline information or airline advertisement changes. The Respondent must also demonstrate the ability to contract or expand the backwall to model when the airline reduces the number of ticket counters or adds counters and the backwall must adjust automatically and align with the types of ticket counter positions they represent/service.

Assume the ticket counter size does not match the display monitor portrait width for this demonstration.

3. Demonstrate the transitions from one type of content to another. For example, a fully functioning Airline Ticket Counter Backwall, full canvas to an Authority experience for all displays in the demonstration canvas environment.

4. Demonstrate a Flight Information Board utilizing GOAA flight information as well as messaging or information for the traveler on the same canvas. Show how the AOC user can override, and update FIDS information manually as required by a change in flight data/status. Demonstrate how changes in flight data (e.g., a flight gate change) dynamically changes the information shown on public displays.

5. Demonstrate wayfinding depicting at a minimum of 8 airlines and directional symbology and indicators with information that changes automatically to 12 airlines representing a change in daily activity from one day to the next. Use international symbols and arrows for directional indicators/wayfinding to model wayfinding signs inside the terminal.

6. With the wayfinding content demonstrate how the AOC staff will be able to make changes and modify the content/experience as required.

7. Demonstrate how the system handles emergency messaging where part of the display canvas is taken over and used for emergency messages that are selected from a canned library of messages by the AOC. Demonstrate how the AOC can also free hand type a message then immediately display to the messaging portion of the canvas. The other part of this canvas should be able adjust the sizing of the existing content to allow for the emergency messaging to display upon the takeover of part of the canvas.

8. As a gate canvas display, demonstrate the system capabilities to display various types of data related to a departing flight, showing all relevant departing flight and gate information, creative back drop and the next flight information on the display canvas.

9. Demonstrate the business rules and scheduling engine that automates displaying certain types of content at certain locations and certain times. As an example, demonstrate a gate change from a current departing flight from the gate to the next airline departing from that same gate based on the flight information integration.

10. Demonstrate how content is scheduled for a particular display and a set of displays.

11. Demonstrate reporting capabilities of the system including how reports are generated.