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 29
Check-in/Ticketing Model 29 Figure 31. Example of Check-in/Ticketing model dashboard. of passengers at most airports. Because there are different ways a passenger can check-in, or check a bag after checking in remotely (by Internet, remote kiosk, or other means), the ticket lobby may accommodate the different types of facilities described above and possibly others which may be developed in the future. Model Overview The Check-in/Ticketing model is formatted like all of the other models and uses a color-coded cell system to differentiate types of cells. The top of the model is a dashboard of current settings and status for the inputs and condi- tions that the user is entering. In Figure 31 the dashboard shows the status summary, as well as some ratios such as check-in positions per EQA that can be compared to other similar airports. The Check-In/Ticketing model incorporates models for the Staffed Counter, Kiosk, and Curb- side check-in areas. However, the three basic models can be used for any type of future check-in procedure, such as self-tagging, with the appropriate inputs. Use the toggle buttons as seen in Figure 32 to auto scroll the screen to work on one area at a time. In most of the input cells, a small red triangle will be in the upper right corner, signifying that a comment has been attached to give more explanation to the input requirements and/or more information on the general ranges. Some inputs and their title lines are conditionally formatted to alert the user to the possibility of an input error. The user can either keep the entered value if it is truly correct, or make a change to fall within the expected range, and the highlighted areas will return to the normal appearance. See Figure 33. The terminal planner should be aware of the various systems and procedures in use, or expected to be used, as the check-in lobby and related spaces are planned. Flexibility in configuration and design is especially important for this evolving passenger-processing function. The Design Hour Forecast Worksheet should have been completed before doing this step or an estimated design hour value will need to be used. If an estimate is used, enter the value into cell C11 in the Staffed Counter section; this will break the link to the Design Hour Forecast Worksheet and the other dependant cells will use this value as well. Figure 32. Toggle buttons for check-in areas.