scope:

There are generally three purposes for segment specifications: 1) The specification enables the government to specify the requirements for the segment to potential developers of the system. 2) The specification provides a general overview of the segment which can be used by trainers, support personnel, or other users of the system. 3) Upon government approval and authentication, the specification becomes the functional baseline for the segment. Since the TMS was an operational segment when this specification was produced, the second and third purposes shall apply to the TMS. That is, this document serves to allocate functions for Phase II and shall not be used for procurement purposes. More detailed specification documents shall be generated to document the as-built configuration for the hardware and software system elements.

This document specifies automation functions to be performed in support of Phase II of the Automation Enhancement Project to the Federal Aviation Administration (FAA) Traffic Management System (TMS). (Unless stated otherwise, 'TMS' in this document shall refer to Phase II capabilities.) The system elements required to carry out the automation functions are identified herein as either Hardware Configuration Items (HWCIs) or Computer Software Configuration Items (CSCIs). Requirements of the TMS automation are allocated to specific HWCIs and CSCIs so that separate contracting (task orders and statements of work) can be initiated for the development and implementation of any Configuration Item.

Purpose. The purposes of TMS automation are:

a. To collect all air traffic demand and capacity data pertinent to flow management.

b. To supply computing resources to analyze air traffic demand and capacity data for flow management purposes.

c. To deliver flow management information and analyses to all NAS specialists involved in flow management.

d. To provide more effective alternatives to manual and teletype procedures for coordinating and communicating flow management information.