Airport Passenger Information Displays: An RFQ Checklist

Passenger information displays must remain readable in changing light while receiving accurate data and fitting strict architectural and operational constraints. A panel specification alone does not define data ownership, fallback behavior, mounting, monitoring, or how service work occurs in a live terminal.

This guide helps airport operators, consultants, IT, facilities, and procurement teams make a defensible decision about legibility, integration, and operational continuity. It connects the operating brief to a practical high-brightness stretch LCD display scope, supplier response, and acceptance record instead of relying on a short specification list.

Define the Operating Brief for an airport passenger information display

Identify passenger decision points, viewing distances, languages, data sources, update intervals, fallback content, terminal lighting, mounting zones, and permitted service windows. Record the normal operating hours, responsible team, content sources, audience position, maintenance window, and any construction or IT dependencies. Give every bidder the same brief so commercial differences are not confused with missing scope.

A useful brief also separates confirmed requirements from assumptions that still need a site survey or design review. The LED-versus-LCD cost framework provides a starting structure for documenting those inputs before the quotation is treated as final.

Passenger legibility

Test text size, contrast, language layouts, and viewing angles at decision points The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the passenger legibility conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for passenger legibility. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Data integration

Define source systems, refresh intervals, failure states, and interface ownership The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the data integration conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for data integration. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Ambient light

Measure daylight and terminal-light conditions across the operating schedule The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the ambient light conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for ambient light. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Airport Passenger Information Display RFQ Decision Matrix

Mounting and access

Coordinate structures, clearances, cable routes, and safe maintenance zones The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the mounting and access conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for mounting and access. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Continuity and monitoring

Define alerting, fallback content, recovery actions, and support escalation The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the continuity and monitoring conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for continuity and monitoring. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Acceptance records

Witness representative data, visual layouts, outages, and operator workflows The project team should translate this condition into a measurable design input and identify who owns any remaining site assumption For an airport passenger information display, this decision should be reviewed against the real content, viewing conditions, duty cycle, and access plan rather than a demonstration loop or a generic product sheet.

In the RFQ, ask the supplier to respond to the acceptance records conditions with the proposed configuration, limits, interface responsibilities, and any optional work. The response should include a project-specific drawing or schedule, stated assumptions, configuration details, and an acceptance method for acceptance records. Record exclusions, tolerances, and work supplied by others so the project team can compare complete systems instead of isolated component claims.

Connect Installation, Content, and Service

Display hardware is only one part of the operating result. Coordinate source devices, processing, signal routes, power distribution, structure, thermal conditions, content approval, monitoring, and service access. The window-facing LCD RFQ checklist and power-consumption guide help define the interfaces that can otherwise fall between the display vendor, integrator, contractor, IT team, and buyer.

Name an owner for every interface and agree when that owner must provide drawings, equipment, settings, access, or approval. If an assumption changes after manufacture, use a written change record that explains cost, schedule, performance, and acceptance impact before the team proceeds.

Plan Acceptance Evidence Before Shipment

Acceptance should test the purchased configuration with representative content and the intended control workflow. Define the samples, viewing positions, operating presets, fault scenarios, documents, and people required for the review. Where practical, close mapping, image, control, and documentation issues before the display leaves the supplier.

Repeat the relevant checks after delivery and installation because transport, field cabling, structure, and site power introduce new variables. Use the commissioning checklist to connect factory evidence with commissioning and final handover rather than treating each stage as a separate promise.

Buyer Checklist

• Confirm the passenger legibility requirement and responsible owner.
• Confirm the data integration requirement and responsible owner.
• Confirm the ambient light requirement and responsible owner.
• Confirm the mounting and access requirement and responsible owner.
• Confirm the continuity and monitoring requirement and responsible owner.
• Confirm the acceptance records requirement and responsible owner.
• Use representative content and the intended operating workflow during acceptance.
• Record exclusions, spares, training, documents, and post-handover support.

The strongest proposal will make assumptions visible, assign interface ownership, and show how the system will be tested and supported. For a project-specific review, contact SXLED with the site, screen dimensions, viewing positions, content examples, operating schedule, access constraints, and target installation date.