Flight Information Display and Content Management System

The Vendor is required to provide flight information display system (FIDS), gate information display system (GIDS), baggage information display system (BIDS), ticketing information display system (TIDS), advertising display services (ADS), and integrated content management system (CMS).
- Functional requirements
1. Flight information display system (FIDS)
•    FIDS shall provide passenger-facing displays for departures, arrivals, and operational messaging using authoritative upstream data sources and coordinated multi-screen presentation.
2. Core FIDS capabilities
•    Real-time display of flight information for departures and arrivals sourced from airport and resource management system (RMS) and approved flight data feeds
•    Automatic refresh and synchronization with upstream data sources 
•    Paging, scrolling, or looping logic for high flight volumes 
•    Coordinated multi-screen display layouts with overflow or spill logic across adjacent displays 
•    Multi-language display capability 
•    Time-based scheduling of layouts and content 
•    Manual override and emergency messaging by authorized airport personnel limited to display presentation only and not operational data control 
•    Coordination of visual emergency and operational messaging with the airport’s public address system, including support for synchronized announcements during security, safety, weather, operational, or emergency events, where applicable 
•    Support for airport-controlled commercial display panels with embedded web player or native browser functionality to render externally hosted public flight information URLs directly at the display device level, and integration with airport-designated third-party flight data services, whether existing at time of award or implemented thereafter, without requiring proprietary rendering servers, playback appliances, or bundled vendor-managed flight data subscriptions unless expressly authorized by the airport 
•    Support for display of externally hosted public flight information feeds provided by county designated third-party data providers (current or future), including rendering of secure public URLs and ingestion of third-party API-based flight data for presentation within CMS-managed templates, where such data sources are approved by county and do not conflict with the airport and RMS as the authoritative systems of record. 
•    Clear separation between authoritative operational airport and RMS data and externally sourced public visualization feeds
3. Gate information display system (GIDS)
•    Display of flight-specific departure information, including flight number, destination, scheduled and estimated departure times 
•    Display of boarding status, boarding groups, and related gate messaging 
•    Display of gate assignments and gate changes as provided by authoritative upstream systems 
•    Support for gate-specific layouts and templates distinct from common-use FIDS layouts 
•    Automatic refresh and synchronization with upstream data sources 
•    Manual override and emergency messaging by authorized airport personnel limited to display presentation only and not operational data control
4. Ticketing information display system (TIDS)
•    Display of airline branding and counter-specific messaging 
•    Display of ticketing and check-in counter assignments 
•    Association of counters with flights or airlines as provided by authoritative upstream systems, including support for time-based, permanent, and temporary counter assignments defined at the airport’s discretion 
•    Support for counter-specific layouts and templates 
•    Automatic refresh and synchronization with upstream data sources 
•    Manual override capability for airport operations staff limited to display presentation only and not authoritative operational data control or persistence
5. BSO counter-level display support
•    The TIDS component shall also support baggage service office (BSO) counter-level passenger-facing displays. 
•    BSO displays function as operational service counters providing baggage claim assistance, flight status reference, carousel messaging, and airline-specific service messaging.
6. BSO displays shall:
•    Operate using the same presentation-layer architecture as TIDS displays 
•    Support airline branding and counter-specific layouts 
•    Display flight status and possible baggage carousel information sourced from authoritative upstream systems 
•    Support time-based scheduling and content zoning 
•    Inherit all resilience, data handling, security, logging, and presentation-layer requirements defined for TIDS 
•    Remain display-layer only and shall not create, modify, or persist authoritative baggage or flight data
7. Resilience and data handling
•    Graceful degradation during upstream data delays or outages
•    Clear differentiation between confirmed, estimated, and pending information
•    Configurable fallback messaging when data is unavailable
•    Automatic BIDS updates for late or corrected belt assignments.