Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.
OCR for page 195
Technology 195 The opposite is also true--the potential amount of information needed is increased the further from the airport passengers are located. Obviously, it is not practical to install massive numbers of displays at these remote locations. To address this issue, there are a number of options available as shown in the paragraphs below. 7.2.27 Flight Information Kiosks To resolve the ever-increasing need to provide passengers with information on demand, some airports have elected to implement "passenger information kiosks" to help provide timely, needed information. These kiosks typically have a touch-screen interface providing a convenient opportunity for passengers to obtain pertinent information from the MUFIDS. In addition to flight information, the kiosks can provide additional information about hotels, rental cars, tourist attractions, restaurants, airport services, wayfinding, etc. The flight informa- tion presented at these kiosks can be obtained from on-line services or the Airport's website (via internet) or through a network connection with the Airport's MUFIDS (requires local network connection). There are a number of sources for such kiosks. These units can leverage upon existing commu- nications infrastructure or operate in a wireless environment, if available. 7.3 Design Elements 7.3.1 Regulatory Requirements--ADA and Display Systems The flexible software of a modern MUFIDS and/or wayfinding signage controller system enables the user to display data to disadvantaged passengers and to comply with any ADA requirements which may in the future be mandated by local or Federal laws. An example is displaying visual pag- ing messages on designated monitors. Because MUFIDS displays are dynamic in nature, they normally are considered temporary signs and, therefore, are not specifically addressed under ADA. It is in the public interest, however, that any new wayfinding and signing system accommodate and anticipate ADA-type display features during the design phase. Each display bank should consider the inclusion of provisions for the future addition of TDD phones. 7.3.2 Sign Lighting Controllers (Dimming, Groups of Signs) Controls for sign lighting typically is provided as part of the wayfinding and signing system soft- ware. The control of the lighting can be set by individual sign or by groups of signs either manu- ally and/or via an automatic time program. Sign lighting may also be automatically controlled locally at each sign with photoelectric cells. 7.4 Open System Architecture System architecture constitutes the framework that describes how system components interact and work together to achieve total system goals. It describes the system operation, what each com- ponent of the system does, and what information is exchanged among the components. System architecture may be either "open" or "closed." System equipment should be installed that support "open" system architecture standards and protocols to allow the use of several different manufacturers' systems and devices that support an
OCR for page 195
196 Wayfinding and Signing Guidelines for Airport Terminals and Landside "open" system architecture to provide interoperability, compatibility and interchangeability within the wayfinding and signing system. This allows a facility to establish multi-source, "common-off- the-shelf" (COTS), and industry standards for all components and network devices. 7.4.1 System Testing Establish test beds to support full testing of any new software, firmware and hardware. Test beds shall support the full testing of components in actual and simulated environments to identify and eliminate problems that may cause system instability prior to its actual implementation.