Automated Flight Strip Management System Functional Description

5.4.2 Traffic Data Recording Requirements
Using the on and off line data base storage system described above, ASMS should
offer a menu driven software system accessible to the supervisor to generate traffic data
summary reports. The system should be capable of summarizing the data by: 1) arrivals
and departures; 2) aircraft category (heavy, large, small) or (air carrier, commuter, general
aviation); 3) runway used; 4) time period. Standardized report fonnats and parameters
should be stored so that the supervisor can select a standard report from a menu.
5.4.3 Operational Recording and Eligibility Requirements
The ASMS system should keep track ofthe acting controller by position by
requiring a log-in. The log-in should allow the recording oftraining time by trainer and
trainee. This data should be stored with the Flight Progress Strip data. A menu driven
software package should be provided that allows the supervisor to prepare standardized
summary time reports including training and overtime. The system should provide the
supervisor with real time eligibility checks which includes algorithms for position
certification, training, length oftime at position, or any other constraint that would
determine a persons eligibility to act as a controller at that position. In no case should the
ASMS software prevent a controller from logging in, even if it violates a preset constraint.
5.5 OPTIMUM QUEUE MODULE
ASMS will have access to data on departing aircraft by gate, aircraft type, and
routing including initial departure fix. It is possible that a knowledge based algorithm
could be developed to optimize the departure sequence by runway taking into account
arrivals (both known from ARTS or Host or predicted based on statistics), airport
configuration, separation standards, flow control limits to initial departure fixes, and
aircraft performance limits. The software design should at least make provisions for a
software module designed to optimize departure queues. This could serve as a test bedfor
future ASTA software and for integration with TATCA.
41