TMA System Specification by DTAvkE99

VIEWS: 115 PAGES: 221

									                                   FAA-E-2971 Final Rev N




      SYSTEM SPECIFICATION

TRAFFIC MANAGEMENT ADVISOR (TMA)




       FAA-E-2971 Final Rev N
         17 December 2008




 DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION




                                   FAA-E-2971 Final Rev N
                                SYSTEM SPECIFICATION

                        TRAFFIC MANAGEMENT ADVISOR (TMA)




                                  FAA-E-2971 Final Rev N

                                     17 December 2008




                         DEPARTMENT OF TRANSPORTATION

                        FEDERAL AVIATION ADMINISTRATION




Approved by: _________________________________             Date:_________________
               Bill Boyer
               Program Manager for CTAS, A0Z 500
                                                                                           FAA-E-2971
                                                                                      17 December 2008
                                                                                            Final Rev N


                                        Change Description



 Revision / Date                         Change contents                                Pages Affected

FAA-E-2971          Initial issuance of System Specification for CTAS/TMA.            All
02/26/2003          Supersedes CTAS System Specification, Rev 8A.
by AOZ-500 iCCB

FAA-E-2971          Second issuance of System Specification for CTAS/TMA.             All
08/01/2003          Supersedes CTAS System Specification, February 26, 2003.
by AOZ-500 iCCB

FAA-E-2971          Third issuance of System Specification for CTAS/TMA.              All
11/01/2003          Supersedes CTAS System Specification, August 1, 2003.
by AOZ-500 iCCB

FAA-E-2971 Rev A    Issuance of System Specification. Delivered to CSC as GFI for     All
1/23/04             maintenance requirements. Supersedes CTAS System
by AOZ-500 iCCB     Specification, November 1, 2003.

FAA-E-2971 Rev B    Second issuance of System Specification for CTAS/TMA.             All
2/26/04             Supersedes CTAS System Specification, January 23, 2004.
by AOZ-500 iCCB

FAA-E-2971 Rev C    Issuance of System Specification to correspond with TMA           All
05/14/2004 by CSC   Version 3.1.6 software. RPRs incorporated are: 1123 and 1152.
ICCB                Supersedes CTAS System Specification, February 26, 2004.

FAA-E-2971 Rev D    Issuance of System Specification to correspond with TMA           All
11/10/2004 by CSC   Version 3.2.0 software. RPRs incorporated are: 141, 537, 820,
ICCB                995, 1116, 1117, 1119, 1120, 1147, 1155, and 1172. Also
                    included is RPR-1186 which is spec update only. Supersedes
                    CTAS System Specification, May 14, 2004.

FAA-E-2971 Rev E    Issuance of System Specification to correspond with TMA           All
02/01/2005 by CSC   Version 3.2.2 software. RPR-1216 is incorporated. Supersedes
ICCB                CTAS System Specification, November 10, 2004.

FAA-E-2971 Rev F    Issuance of System Specification to correspond with TMA           All
04/27/2005 by CSC   Version 3.3.0 software. RPRs incorporated are: 884, 1205, 1206,
ICCB                1219, 1229, and 1235. Supersedes CTAS System Specification,
                    February 1, 2005.

FAA-E-2971 Rev G    Issuance of System Specification to correspond with TMA           All
09/15/05 by CSC     Version 3.4.0 software. RPRs incorporated are: 283, 1188,
ICCB                1250, 1254, 1260, and 1290. RPR 1277 is spec update only.
                    Supersedes TMA System Specification, April 27, 2005.
                                                                                               FAA-E-2971
                                                                                          17 December 2008
                                                                                                Final Rev N
 Revision / Date                            Change contents                                 Pages Affected

FAA-E-2971 Draft       Issuance of System Specification to correspond with TMA            All
Rev H 01/17/06 by      Version 3.4.1 software. RPRs incorporated are: 1218 and 1312.
CSC ICCB               Supersedes TMA System Specification, September 15, 2005.

FAA-E-2971 Final       Issuance of System Specification to correspond with TMA            All
Rev H 02/08/06 by      Version 3.4.1 software. RPRs incorporated are: 1218 and 1312.
CSC ICCB               Supersedes TMA System Specification, September 15, 2005.

FAA-E-2971 Draft       Issuance of System Specification to correspond with TMA            All
Rev I 06/06/06 by      Version 3.5.0 software. RPRs incorporated are: 1317, 1327,
CSC ICCB               1334, 1337, 1338, and 1341. Supersedes TMA System
                       Specification, Final Rev H, February 8, 2006.

FAA-E-2971 Final       Issuance of System Specification to correspond with TMA            All
Rev I 08/10/06 by      Version 3.5.0 software. RPRs incorporated are: 1317, 1327,
CSC ICCB               1334, 1337, 1338, 1341, 1350, and 1351. Also included are the
                       FAA’s comments, dated 8/3/06, of the Draft Rev I. Supersedes
                       TMA System Specification, Draft RevI, June 6, 2006.
                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Draft                                                                          All
                       Version 3.6.0 software. RPRs incorporated are: 1215, 1362,
Rev J 01/05/07 by
                       1381, 1382, 1385, and 1387. Supersedes TMA System
CSC ICCB
                       Specification, Final Rev I, August 10, 2006.
                       NOTE: The following RPRs are pending FAA approval and will
                       be included in the Final Version J if approved in time: 1357 and
                       1401.
                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Revised
                       Version 3.6.0 software. RPRs incorporated are: 1215, 1357,
Draft Rev J 01/16/07
                       1362, 1381, 1382, 1385, 1387, and 1401. Supersedes TMA
by CSC ICCB
                       System Specification, Draft Rev J, January 5, 2007.
                       NOTE: This Revised Draft includes RPRs 1357 and 1401, which
                       were approved on 1/9/07.
                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Final
                       Version 3.6.0 software. RPRs incorporated are: 1215, 1357,
Rev J 03/05/07 by
                       1362, 1381, 1382, 1385, 1387, 1401, and 1410. Supersedes
CSC ICCB
                       TMA System Specification, Draft Rev J, January 5, 2007.

                       NOTE: This Final includes RPR 1410 approved on 03/05/07 and
                       one FAA editorial comment dated 2/12/07.
                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Draft                                                                          All
                       Version 3.7.0 software, which includes 3.6.2 and 3.6.3. RPR-
Rev K 08/24/07 by
                       1430 incorporated in 3.6.2; RPRs 1487 and 1492 incorporated in
CSC ICCB
                       3.6.3, and RPRs incorporated for 3.7.0 are: 1308, 1389, 1423,
                       1426, 1432, 1435, 1438, 1443, 1448, 1449, 1450, 1453, 1454,
                       1467, 1468, 1473, 1491. Supersedes TMA System Specification,
                       Final Rev J, March 5, 2007.
                                                                                                FAA-E-2971
                                                                                           17 December 2008
                                                                                                 Final Rev N
 Revision / Date                             Change contents                                Pages Affected
                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Final
                       Version 3.7.0 software, which includes 3.6.2 and 3.6.3. RPR-
Rev K 10/12/07 by
                       1430 incorporated in 3.6.2; RPRs 1487 and 1492 incorporated in
CSC ICCB
                       3.6.3, and RPRs incorporated for 3.7.0 are: 1308, 1389, 1423,
                       1426, 1432, 1435, 1438, 1443, 1448, 1449, 1450, 1453, 1454,
                       1467, 1468, 1473, 1491, 1498. Supersedes TMA System
                       Specification, Draft Rev K, August 24, 2007.

                       NOTE: This Final also includes FAA editorial comments dated
                       10/05/07.

                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Draft
                       Version 3.8.0 software, which includes 3.7.1. RPR-1506
Rev L 04/23/08 by
                       incorporated in 3.7.1, and RPRs incorporated for 3.8.0 are: 1519,
CSC ICCB
                       1520, 1521, 1526, 1527, 1530, 1534, 1535, 1538, 1567.
                       Supersedes TMA System Specification, Final Rev K, October 12,
                       2007.

                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Final
                       Version 3.8.0 software, which includes 3.7.1 and 3.7.2. RPR-
Rev L 06/06/08 by
                       1506 incorporated in 3.7.1. There were no RPRs for 3.7.2. RPRs
CSC ICCB
                       incorporated for 3.8.0 are: 1519, 1520, 1521, 1526, 1527, 1530,
                       1534, 1535, 1538, 1567, 1568, and 1569. Supersedes TMA
                       System Specification, Draft Rev L, April 23, 2008.

                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Revised
                       Version 3.8.0 software, which includes 3.7.1, 3.7.2, and 3.7.3.
Final Rev L 07/25/08
                       There were no RPRs for 3.7.3. This Revised Final contains the
by CSC ICCB
                       RPRs included in the Final and two additional RPRs. The two
                       RPRs are: 1573 and 1579. Supersedes TMA System
                       Specification, Final Rev L, June 6, 2008.

                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Rev M
                       Version 3.8.1 software. The RPR incorporated is RPR-1519.
09/10/08 by CSC
                       Supersedes TMA System Specification, Revised Final Rev L,
ICCB
                       July 26, 2008.

                       Issuance of System Specification to correspond with TMA
FAA-E-2971 Draft
                       Version 3.9.0 software. The RPRs incorporated are: 1583, 1584,
Rev N 12/03/08 by
                       1585, 1586, 1587, 1588, 1612, and 1613. Supersedes TMA
CSC ICCB
                       System Specification, Rev M, September 10, 2008.

                       NOTE: Updates to Requirement 0877 were inadvertently missed
                       when incorporating RPR-1569. This is spec update only.

                       This Draft contains RPR-1612 (CSCwb08329) that has been
                       approved by the CSC ICCB but not the FAA.
                                                                                           FAA-E-2971
                                                                                      17 December 2008
                                                                                            Final Rev N
 Revision / Date                          Change contents                              Pages Affected
                     Issuance of System Specification to correspond with TMA
FAA-E-2971 Final N
                     Version 3.9.0 software. The RPRs incorporated are: 1583, 1584,
12/17/08 by CSC
                     1585, 1586, 1587, 1588, 1612, 1613, and 1614. Supersedes
ICCB
                     TMA System Specification, Draft Rev N, December 3, 2008.

                     NOTE: Updates to Requirement 0877 were inadvertently missed
                     when incorporating RPR-1569. This is spec update only.
                                                                                                                           FAA-E-2971
                                                                                                                      17 December 2008
                                                                                                                            Final Rev N
                                                    TABLE OF CONTENTS

Section                                                         Description                                                          Page No.

1. SCOPE..................................................................................................................................... 1
   1.1      Identification ...................................................................................................................... 1
   1.2      System Overview ............................................................................................................... 1
   1.3      Document Overview .......................................................................................................... 2
2. REFERENCED DOCUMENTS ........................................................................................... 3

3. REQUIREMENTS ............................................................................................................... 11
   3.1      Required States ................................................................................................................ 11
   3.2      System Capability Requirements ..................................................................................... 14
            3.2.1 TMA Processing .................................................................................................. 18
                    3.2.1.1 Inputs & Outputs .................................................................................... 20
                    3.2.1.2 Aircraft Processing................................................................................. 28
                    3.2.1.3 Route Analysis ....................................................................................... 30
                          3.2.1.3.1          Fix/Arc Assignment .............................................................. 31
              3.2.1.3.1.1 CTAS Meter Fix/Scheduling Meter Fix Assignment ............................ 31
              3.2.1.3.1.2 Meter Fix Arc Assignment..................................................................... 32
              3.2.1.3.1.3 Outer Fix Assignment ............................................................................ 33
              3.2.1.3.1.4 Outer Meter Arc Assignment ................................................................. 33
              3.2.1.3.1.5 Outer-outer Arc Assignment .................................................................. 34
              3.2.1.3.1.6 Outer-Three Arc Assignment ................................................................. 34
              3.2.1.3.1.7 Holding Arc Assignment ....................................................................... 35
                          3.2.1.3.2          Stream Class Assignment ...................................................... 35
                          3.2.1.3.3          Runway Assignment .............................................................. 36
              3.2.1.3.3.1 Identification of the Reallocation Procedure from Site Adaptation ....... 39
              3.2.1.3.3.2 Runway Search ...................................................................................... 40
                          3.2.1.3.4          TRACON Speed & Altitude Parameter Specification .......... 40
                          3.2.1.3.5          Situation Categorization ........................................................ 40
                          3.2.1.3.6          Route Estimation ................................................................... 41
                    3.2.1.4 ETA Generation ..................................................................................... 43
                          3.2.1.4.1          Determination of Vertices ..................................................... 45
                          3.2.1.4.2          Determination of Horizontal Ground Track .......................... 47
                          3.2.1.4.3          Determination of the Vertical Profile Along the Ground Track
                                             ............................................................................................... 48
              3.2.1.4.3.1 Vertical Profile in Center Airspace ........................................................ 48
              3.2.1.4.3.2 Vertical Profile in TRACON Airspace .................................................. 49
              3.2.1.4.3.3 Stepped Descent ..................................................................................... 50
                          3.2.1.4.4          Variable Speed Crossing Restriction (VSCR) ....................... 50
                          3.2.1.4.5          ETA Smoothing ..................................................................... 50
                    3.2.1.5 Scheduling.............................................................................................. 51
                          3.2.1.5.1          Scheduling Using Time Based Metering ............................... 53


                                                                       iii
                                                                                                               FAA-E-2971
                                                                                                      17 December 2008
                                                                                                                Final Rev N
  3.2.1.5.1.1 Separation at the Scheduling Meter Fix/Meter Fix Arc ......................... 58
  3.2.1.5.1.2 Separation at the Runway ...................................................................... 61
  3.2.1.5.1.3 Feedback from Runway Schedules to Scheduling Meter Fix/Meter Fix
  Arc Schedules ............................................................................................................... 62
  3.2.1.5.1.3.1                 Scheduling at the CTAS Meter Fix ....................................... 64
  3.2.1.5.1.3.2                 Scheduling at the Meter Fix Arc under Offset Scheduling. .. 65
  3.2.1.5.1.4 Scheduling at the Outer Meter Arc ........................................................ 65
  3.2.1.5.1.5 Scheduling at the Outer-outer Arc ......................................................... 66
  3.2.1.5.1.6 Scheduling at the Outer-Three Arc ........................................................ 67
  3.2.1.3.1.7 Outer-Four Arc Assignment................................................................... 68
  3.2.1.5.1.8 Scheduling from Locally Departed Airports .......................................... 69
  3.2.1.5.1.9 Computing Excess Delays ..................................................................... 70
              3.2.1.5.2         Scheduling Using Automated Miles-in-Trail (deleted) ......... 72
  3.2.1.5.2.1 Recommend Stop Time (deleted) .......................................................... 72
  3.2.1.5.2.2 Recommend Stream Class Combinations into Super Stream Classes ... 72
  3.2.1.5.2.3 Finalize the Miles-in-Trail Restrictions for Manually Set and "Lightly"
  Loaded Streams (deleted) ............................................................................................. 72
  3.2.1.5.2.4 Iterate the Non-finalized Miles-in-Trail Settings to Meet the Requested
  AAR (deleted) .............................................................................................................. 72
              3.2.1.5.3         Adjacent Facility Metering .................................................... 72
              3.2.1.5.4         Arrival Plan Preview Capability............................................ 77
              3.2.1.5.5         Automatic Deletion / Open Slot Processing .......................... 78
              3.2.1.5.6         Diversion List Processing ...................................................... 81
              3.2.1.5.7         Multi-TRACON Processing .................................................. 82
              3.2.1.5.8         En Route Departure Capability.............................................. 84
3.2.2 FAST Processing [deleted] .................................................................................. 91
  3.2.1.5.8.1 Multiple Meter Point Capability ............................................................ 91
3.2.3 TMC Graphical User Interface ............................................................................ 94
        3.2.3.1 Inputs & Outputs ................................................................................... 95
        3.2.3.2 Display Presentation .............................................................................. 96
              3.2.3.2.1         Timeline Display ................................................................... 96
              3.2.3.2.2         Load Graph Display............................................................... 96
              3.2.3.2.3         Plan View Display ................................................................. 97
              3.2.3.2.4         Statistical Calculations .......................................................... 97
  3.2.3.2.4.1 Traffic Count .......................................................................................... 97
  3.2.3.2.4.2 Statistical Delay Information ................................................................. 97
        3.2.3.3 Display Definition ................................................................................ 100
        3.2.3.4 Parameter Interaction ........................................................................... 100
        3.2.3.5 Data Retrieval (deleted) ....................................................................... 103
        3.2.3.6 Display Interaction (deleted) ................................................................ 103
3.2.4 Monitor & Control............................................................................................. 103
        3.2.4.1 Inputs & Outputs ................................................................................. 105
        3.2.4.2 Monitoring ........................................................................................... 105
        3.2.4.3 Control 107
        3.2.4.4 Diagnostics ........................................................................................... 108


                                                         iv
                                                                                                                    FAA-E-2971
                                                                                                           17 December 2008
                                                                                                                     Final Rev N
            3.2.4.5 Maintenance of System Log................................................................. 110
     3.2.5 Data Management (DM) (deleted) .................................................................... 111
     3.2.6 Adaptation, Validation, and Analysis ................................................................ 111
     3.2.7 Data Analysis and Testing ................................................................................. 112
     3.2.8 Playback ............................................................................................................ 113
     3.2.9 Simulation ......................................................................................................... 114
     3.2.10 Support Subsystem ............................................................................................ 114
     3.2.11 Weather Interface .............................................................................................. 115
3.3 System External Interface Requirements ....................................................................... 116
     3.3.1 Interface Identification and Diagram ................................................................. 116
     3.3.2 HCS Interface .................................................................................................... 118
     3.3.3 TRACON Automation Interfaces ..................................................................... 118
            3.3.3.1 ARTS Gateway .................................................................................... 119
            3.3.3.2 STARS Interface .................................................................................. 119
            3.3.3.3 ARTS III-A Interface ........................................................................... 119
     3.3.4 ETMS Interface ................................................................................................. 119
            3.3.4.1 ETMS Weather Interface ..................................................................... 119
            3.3.4.2 ETMS Center/TRACON Traffic Data ................................................. 120
            3.3.4.3 ETMS PGUI Display on TSD .............................................................. 120
     3.3.5 Adjacent Facility TMA Data I/O Interfaces ...................................................... 120
            3.3.5.1 Adjacent Center TMA Data I/O Interface ............................................ 120
            3.3.5.2 Adjacent TRACON TMA Data I/O Interface ...................................... 120
     3.3.6 Adjacent Facility User I/O Interfaces ................................................................ 121
            3.3.6.1 Adjacent Center Facility User I/O Interface......................................... 121
            3.3.6.2 Adjacent TRACON Facility User I/O Interface ................................... 121
            3.3.6.3 Tower TMA User I/O Interface ........................................................... 122
     3.3.7 AMCC Interface for a Center TMA Installation ............................................... 122
     3.3.8 [deleted] ............................................................................................................. 122
     3.3.9 [deleted] ............................................................................................................. 122
     3.3.10 WARP Interface ................................................................................................ 122
     3.3.11 Time Synchronization Interface ........................................................................ 123
     3.3.12 TRACON Passive Data Feed Interface ............................................................. 123
     3.3.13 Collaborative Arrival Planning (CAP) to Client Interface Requirements ......... 123
     3.3.14 National Airspace Infrastructure Management System (NIMS) Interface ........ 124
3.4 System Internal Interface Requirements ........................................................................ 125
3.5 System Internal Data Requirements .............................................................................. 125
3.6 Adaptation Requirements .............................................................................................. 125
3.7 Safety Requirements ...................................................................................................... 128
3.8 Security and Privacy Requirements ............................................................................... 128
3.9 System Environment Requirements .............................................................................. 129
3.10 Computer Resource Requirements ................................................................................ 129
     3.10.1 Computer Hardware Requirements ................................................................... 129
     3.10.2 Computer Hardware Resource Utilization Requirements ................................. 129
     3.10.3 Computer Software Requirements .................................................................... 130
     3.10.4 Computer Communication Requirements ......................................................... 130


                                                                v
                                                                                                                        FAA-E-2971
                                                                                                               17 December 2008
                                                                                                                         Final Rev N
   3.11     System Quality Factors .................................................................................................. 131
            3.11.1 System Functionality ......................................................................................... 131
            3.11.2 System Reliability.............................................................................................. 131
            3.11.3 System Maintainability ...................................................................................... 131
            3.11.4 System Availability ........................................................................................... 132
            3.11.5 System Flexibility.............................................................................................. 133
            3.11.6 System Portability.............................................................................................. 133
            3.11.7 System Reusability ............................................................................................ 133
            3.11.8 System Testability ............................................................................................. 133
            3.11.9 System Usability ................................................................................................ 133
   3.12     Design and Construction Constraints ............................................................................ 133
   3.13     Personnel-Related Requirements ................................................................................... 134
   3.14     Training-Related Requirements ..................................................................................... 134
   3.15     Logistics-Related Requirements .................................................................................... 134
   3.16     Other Requirements ....................................................................................................... 134
   3.17     Packaging Requirements ............................................................................................... 134
   3.18     Precedence and Criticality Requirements (deleted) ....................................................... 134
4. QUALIFICATION PROVISIONS ................................................................................... 135

5. REQUIREMENTS TRACEABILITY ............................................................................. 137

6. NOTES ................................................................................................................................ 139
   6.1      Acronyms ....................................................................................................................... 139
   6.2      Glossary ......................................................................................................................... 145
APPENDIX A. SOURCE OF REQUIREMENTS [deleted] ................................................. A-1

APPENDIX B. ANTECEDENT AND CONSEQUENCE FUNCTIONS FOR
ORDERING RULES IN FAST [deleted] ................................................................................ B-1

APPENDIX C. DEFERRED REQUIREMENTS .................................................................. C-1

APPENDIX D. RPRs Entered into System Specification as of TMA Software
Release 3.7.0 ............................................................................................................................... D-1




                                                                       vi
                                                                                                                     FAA-E-2971
                                                                                                                17 December 2008
                                                                                                                      Final Rev N
                                               LIST OF ILLUSTRATIONS

Figure                                                        Description                                                      Page No.
Figure 3.2-1. TMA Generic Installation ....................................................................................... 16
Figure 3.2.1-1. TMA Function ...................................................................................................... 19
Figure 3.2.1.5.3-1. TMA Near a Center Boundary ....................................................................... 73
Figure 3.2.1.5.3-2. Calculation of Coordination Fix STA ............................................................ 74
Figure 3.2.1.5.3-3. Assignment of Adjacent Facility Aircraft to an Adapted "In-range"
    Coordination Fix .................................................................................................................... 75
Figure 3.2.1.5.3-4. Stream Classes Entering the TMA Center ..................................................... 76
Figure 3.2.1.5.4-1. Preview Capability. ........................................................................................ 77
Figure 3.2.3-1 TMC-GUI Function ............................................................................................. 94
Figure 3.3.1-1. Diagram of Interfaces for Generic TMA Installations ...................................... 117




                                                                    vii
                                                                                                                    FAA-E-2971
                                                                                                               17 December 2008
                                                                                                                     Final Rev N
                                                          List of Tables

Table                                                        Description                                                     Page No.
Table 2-1.       FAA Development/Acquisition Documents.......................................................... 3
Table 2-2.       ATM-IPT Specific Documents.............................................................................. 4
Table 2-3.       External System Documents, En Route Automation, HCS General ..................... 5
Table 2-4.       External System Documents, En Route Automation, HCS/CTAS Patch ............. 6
Table 2-5.       External System Documents, En Route Automation, HCS/ATM ......................... 7
Table 2-6.       External System Documents, En Route Automation, HID/NAS LAN ................. 7
Table 2-7.       External System Documents, Terminal Automation ............................................. 8
Table 2-8. External System Documents, Enhanced Traffic Management System (ETMS) .......... 8
Table 2-9. External System Documents, Weather and Radar Processor (WARP) ........................ 8
Table 2-10. External System Documents, CTAS Time Synchronization ...................................... 9
Table 2-11. External System Documents, Standard Terminal Automation Replacement System
   (STARS) [deleted] ................................................................................................................... 9
Table 2-12. External System Documents, CAP System ................................................................ 9
Table 3.2-1.     Operational & Support Functions ........................................................................ 14
Table 3.2.1.3.6-1.       Route Estimate Generation .................................................................... 42
Table 3.2.4.1-1.         M&C Function Inputs .......................................................................... 105
Table 3.2.4.1-2.         M&C Function Outputs ....................................................................... 105
Table 3.3.1-1.           Required External Interfaces ................................................................ 116
Table 3.11.4-1 Outage Durations ................................................................................................ 132




                                                                  viii
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N
1.       SCOPE

1.1      Identification

The Traffic Management Advisory (TMA) system is being developed by the Federal Aviation
Administration (FAA) under its Air Traffic Management-Integrated Product Team (ATM-IPT).
According to the Plan for Development and Deployment of Air Traffic Management
Functionality, the activities of the ATM-IPT are intended to result in a decision support system
that will enhance the capacity and efficiency and maintain the safety of the National Airspace
System (NAS).

TMA is the result of prototyping efforts that were demonstrated at the Denver and Fort Worth
Air Route Traffic Control Centers (ARTCCs) and Terminal Radar Approach Controls
(TRACONs) through a cooperative effort conducted principally by the FAA, National
Aeronautics & Space Administration (NASA) Ames Research Center, and Massachusetts
Institute of Technology Lincoln Laboratory. TMA Build 1 was the first build of TMA. This
document specifies the requirements for TMA Build 2, herein referred to as TMA or the System.
The system has been installed at the Minneapolis, Atlanta, Denver, Los Angeles, Miami, and
Oakland ARTCCs.

1.2      System Overview

The System provides computer automation to enhance the arrival/departure throughput and
efficiency of air traffic operations in the extended terminal airspace surrounding major airports.
The end users of the System are Traffic Management Coordinators (TMCs) and Controllers in
both ARTCCs and TRACONs. The TMCs interact directly with the System via display and
input devices added into the Traffic Management Unit (TMU). Controllers interact indirectly
with the System via the existing en route or terminal Air Traffic Control (ATC) automation
systems (e.g., Host Computer System (HCS) and the Automated Radar Terminal System
(ARTS)).

The System's mission is to more efficiently utilize the available airport capacity without
decreasing safety or increasing controller workload. It accomplishes this by providing
automation aids to assist in optimizing:
    a. The flow of traffic to adapted airports (i.e., airports for which adaptation data are
       available) within the ARTCC/TRACON.
      b. The flow of aircraft departing from an in-Center or in-TRACON airport destined for
         adapted airports.
    c. The use of the available runways and surrounding airspace.
The implementation of the System will result in other benefits such as fuel savings from reduced
delays.

TMA is used in the ARTCC, TRACON and Tower. TMA calculates arrival schedules in real
time based on: a) flight plan and track information received from NAS components, including


                                                  1                              TMA System Spec
                                                                                   FAA-E-2971
                                                                             17 December 2008
                                                                                    Final Rev N
National ATM automation (ETMS), En-Route Automation (HCS) and Terminal Automation
(ARTS, STARS, etc.), and b) information entered by the TMCs and controllers about airport
configuration, required wake vortex separation and whether Instrument Flight Rules (IFR) or
Visual Flight Rules (VFR) rules apply to arrivals.

The TMA provides TMCs with tools to coordinate the arrival traffic flow by graphically
depicting the traffic demand and arrival schedules to the adapted airport(s). Graphic displays of
arrival and delay information can be customized on an individual facility and user basis. TMA-
assigned fix/arc crossing times of arrival aircraft and delays to be absorbed are displayed on color
workstations in the TMU. When enabled by the TMC, this information is displayed by the HCS
in meter lists on the ARTCC controller's Display System Replacement (DSR) consoles.

Details regarding the TMA operational concept may be found in the CTAS Build 2 Operational
Concept document.
1.3    Document Overview

This document establishes the characteristics, performance, development, and verification
requirements for the System.

This document follows the Data Item Description (DID) for the System/Subsystem Specification
(SSS) as detailed in MIL-STD-498, Software Development and Documentation, Department of
Defense, 5 December 1994.

The convention for stating system requirements or "SHALLs" in this document is to capitalize
and number each SHALL. An example is: "When requested, the System SHALL [20], etc." If a
requirement has siblings, they are listed as part of the top-level or parent requirement. In the
example, if requirement 20 has three siblings, those are listed as a, b, and c under requirement 20.
In a Verification Requirements Traceability Matrix (VRTM), the requirement in the example
would therefore have four requirements associated with it: 20, 20a, 20b, and 20c.

The System requirements, especially the algorithm requirements, are augmented with expository
detail which some might construe to be excessive for an SSS document. This detail is
intentionally included to reflect the algorithms embodied in the NASA Ames prototype, thus
providing the background and rationale for the requirements.




                                                 2                              TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
2.      REFERENCED DOCUMENTS


                  Table 2-1.    FAA Development/Acquisition Documents

Reference Number                Reference Title                        Applicability
RFC 1098              "Simple Network Management            A software protocol for monitoring
                      Protocol (SNMP) Version 2",           local area networks and their
                      SNMP V2 Group, University of          components such as processors,
                      Twente, 1994.                         servers and routers.
IEEE Std 1003.1       Portable Operating System             Defines the POSIX Compatible
                      Interface Part 1. Library Routines,   Operating System.
                      System Calls, and Header Files.

SVID3                 System V Interface Definition,        SVID3 Standard specifies the
                      Third Edition.                        operating system environment for
                                                            the source-code interface and run-
                                                            time behavior of each operating
                                                            system component.
ANSI/ISO 9899-        ANSI Standard for the C               The ANSI/ISO C standard which is
1990                  Programming Language.                 currently accepted.
C++ ARM Pre-          The Annotated C++ Reference           The basis of the ANSI/ISO C++
Standard              Manual by Margaret A. Ellis &         standard which is still under
                      Bjarne Stroustrup (Addison-           development.
                      Wesley Publishing Company).
FAA Order             Information Systems Security
1370.82A              Program
DoD 5200.28-STD       Trusted Computer System               Defines C2 security criteria.
                      Evaluation Criteria, Dec 1985.
CSC/E2-00/7391        Revised Final Spiral 2                Defines adjacent center feeds
                      System/Subsystem Design
                      Description (S/SDD) for Center-
                      TRACON Automation System
                      (CTAS) Software Development
                      and Support, Task XVI, Part 1 of
                      the En Route Software
                      Development and Support III
                      (ERSDS III) Contract, January,
                      2002.




                                               3                              TMA System Spec
                                                                             FAA-E-2971
                                                                       17 December 2008
                                                                              Final Rev N
Reference Number             Reference Title                     Applicability
CSC/CFF-03/0063    Spiral 3 System/Subsystem Design
                   Description (S/SDD) Update 9 for
                   Center-TRACON Automation
                   System (CTAS) Free Flight
                   Software and Adaptation
                   Development May 17, 2007



                    Table 2-2.    ATM-IPT Specific Documents

Reference Number             Reference Title                     Applicability
                   Plan for Development and            The mission statement for the
                   Deployment of Air Traffic           ATM IPT.
                   Management Functionality,
                   Version 1.0, September 1, 1996.
                   TFM Domain Environment
                   Definition (A Standard Profile),
                   April 29, 1996.
                   CTAS Build 2 Operational            Describes TMA Build 2
                   Concept Document.                   Operational Usage.
FAA-E-2972         Computer Human Interface            Details TMA Build 2 Human
                   Specification Traffic Management    Factor Requirements.
                   Advisor (TMA) , Rev N, Final,
                   December 17, 2008
CSC/CFF-08/0664    Center-TRACON Automation            Specifies interfaces between TMA
                   System Traffic Management           application software and site
                   Advisor (TMA) Adaptation            adaptation software.
                   Interface Control Document, Final
                   TMA Version 3.8.1, September 11,
                   2008
CSC/CFF-03/0053    Spiral 3 Data Recording Interface   Specifies interfaces between TMA
                   Control Document (ICD) Revision     application software and the Data
                   12 for CTAS TMA Software,           Recording tool.
                   Major Adaptation Maintenance,
                   and Integrated Support, September
                   10, 2008




                                          4                             TMA System Spec
                                                                            FAA-E-2971
                                                                       17 December 2008
                                                                             Final Rev N
    Table 2-3.     External System Documents, En Route Automation, HCS General

Reference Number            Reference Title                      Applicability
NAS-MD-312          Route Conversion and Posting.     Describes the route of flight field
                                                      included in the flight plan and other
                                                      messages.
NAS-SR-1000         National Airspace System          Details the reliability requirements
                    Requirements.                     for an "essential system" including
                                                      TMA.
FAA Order           National Airspace Performance     Describes the Official Format for
6040.15C            Reporting System (NAPRS).         NAPRS Reporting.
                    "NFDC Database Record Layouts",   Defines the data format of NFDC
                    National Flight Data Center.      data. This is used for the
                                                      generation and maintenance of site
                                                      adaptation.




                                           5                           TMA System Spec
                                                                                FAA-E-2971
                                                                           17 December 2008
                                                                                 Final Rev N
   Table 2-4.       External System Documents, En Route Automation, HCS/CTAS Patch

Reference Number                 Reference Title                       Applicability
FAA Order 7110.65      Air Traffic Controllers' Handbook.   This document lists all the
                                                            separation requirements that TMA
                                                            must obey as it produces arrival
                                                            schedules.
NAS-IR-82178219        “Interface Requirements Document
                       ARTCC Host Computer System
                       (HCS)/Center-TRACON
                       Automation System – User Request
                       Evaluation Tool”, July 13, 1999.
NAS Change             “Host Software Modifications for a
Proposal/Casefile      Two Way Interface for CTAS and
CT200-CPF-320          URET.”
                       "Host Computer System (HCS)
                       Functional Requirements to
                       Accommodate Center-TRACON
                       Automation System Traffic
                       Management Advisor (TMA)",
                       May 24, 1996.




                                               6                           TMA System Spec
                                                                               FAA-E-2971
                                                                          17 December 2008
                                                                                Final Rev N
        Table 2-5.    External System Documents, En Route Automation, HCS/ATM

Reference Number                 Reference Title                     Applicability
NAS-IR-82170001        "ARTCC Host Computer System        Describes the interface between the
                       (HCS) / Air Traffic Management     Host and the ATM-LAN.
                       (ATM) Applications Interface
                       Requirements Document", August
                       23, 1999.
N0070                  “HCS Common Message Set
                       (CMS) Functional Requirements
                       To Accommodate ATM
                       Applications.”, June 11, 1999.
NAS Change             “Modification of HCS Software to
Proposal/Casefile      Provide an HCS/ATM
UA500-CPF-002          Applications Common Interface”.


    Table 2-6.       External System Documents, En Route Automation, HID/NAS LAN

Reference Number                 Reference Title                    Applicability
NAS-IR-40100001        "ARTCC NAS LAN/User System
                       IRD", 12/21/95.
                       “HID/NAS LAN Integration
                       Requirements Document”, March
                       12, 1998.




                                              7                           TMA System Spec
                                                                             FAA-E-2971
                                                                        17 December 2008
                                                                              Final Rev N
            Table 2-7.   External System Documents, Terminal Automation

Reference Number             Reference Title                    Applicability
                    ARTS II-E Gateway (AGW) to         The communications between the
                    CTAS TMA ARTS Data Interface       ARTS II-E and TMA.
                    (ADIF) Interface Control
                    Document, February 2005.
                     ARTS III-E Gateway (AGW) to       The communications between the
                    CTAS TMA ARTS Data Interface       ARTS III-E and TMA.
                    (ADIF) Interface Control
                    Document, March 2002.
ATC-61015           “Common ARTS Interface Control
                    Document”.
                    "TRACON Map Definition",           Defines the electronic format for
                    Department of Commerce,            TRACON Video Maps used by
                    National Oceanic and Atmospheric   TMA.
                    Administration.


 Table 2-8. External System Documents, Enhanced Traffic Management System (ETMS)
Reference Number              Reference Title                  Applicability
                    Enhanced Traffic Management        The communications between the
                    System (ETMS) to CTAS TMA          ETMS and TMA.
                    ETMS Data Interface (EDIF)
                    Interface Control Document,
                    mm/dd/yy. (deferred)


     Table 2-9. External System Documents, Weather and Radar Processor (WARP)

Reference Number              Reference Title                     Applicability
NAS-IR-TBD          Weather and Radar Processor        Describes the interface between the
                    (WARP) to Center-TRACON            WARP (Weather and Radar
                    Automation System (CTAS)           Processor) distribution server and
                    Interface Requirements Document.   TMA.
NCEP Office Note    The WMO Format for the Storage     National Weather Service
388                 of Weather Product Information     Guideline on the WMO format for
                    and the Exchange of Weather        gridded weather products.
                    Product Messages in Gridded
                    Binary Form (GRIB), March 1998.




                                          8                             TMA System Spec
                                                                           FAA-E-2971
                                                                      17 December 2008
                                                                            Final Rev N
        Table 2-10. External System Documents, CTAS Time Synchronization

Reference Number          Reference Title                        Applicability
TBD                CTAS Time Synchronization          Describes the synchronization of
                                                      Host time and TMA time.

                    Table 2-11. External System Documents,
       Standard Terminal Automation Replacement System (STARS) [deleted]



               Table 2-12. External System Documents, CAP System

Reference Number             Reference Title                    Applicability
                   CAP CTAS to Volpe Interface
                   Control Document, Version 1.0,
                   May 11, 2000
                   CTAS Data for Air Carriers
                   Interface Control Document,
                   Version 1.0 March 20, 2000
                   CTAS Data Feed System
                   Requirements, Version 1.0, March
                   20, 2000




                                          9                           TMA System Spec
                                FAA-E-2971
                           17 December 2008
                                 Final Rev N




Page Intentionally Blank




          10               TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
3.      REQUIREMENTS

3.1     Required States

Note: RPR-159 replaced section 3.1 and 3.2.4 entirely. Several Monitor and Control (M&C)
requirements, which had been moved to section 3.2.4 by RPR-055, were moved back to section
3.1. Within section 3.1, RPR-159 supersedes RPRs 0001, 0002, 0003, 0013, 0014, 0017, 0018,
0019, 0025, 0026, 0040, 0044, 0055, 0057, 0064, and 0145.

The System’s capabilities fall into two categories, Operational and Support. The Operational
capabilities provide the ability to conduct the live ATC mission of Traffic Flow Management
(TFM) in an operational environment, and the Support capabilities provide a number of off-line
support functions. The stated requirements in this section apply only to the Operational
capabilities and not to the Support capabilities.

The M&C function, which is detailed in Section 3.2.4, provides the overall system management
and control of the Operational System (i.e., it manages the computational assets of the
Operational System). The general M&C function requirements are stated in this section, and the
detailed requirements are found in Sections 3.2.4 and 3.11.

During a live operation in the field, the M&C function SHALL [0010] monitor and control the
System’s hardware and software resources.

Whenever hardware or software faults or degradation in operation occur, the M&C function
SHALL [0012] indicate this condition to maintenance personnel.

Whenever displayed data are faulty, out of date, or degraded, the System SHALL [0014] indicate
this condition to air traffic users.

Requirement 0015 has been deleted.

The following condition SHALL [0017] be indicated to the air traffic user:
   a. A Timeline Graphical User Interface (TGUI) has not received schedule updates for a
       system parameter length of time (Site Adaptable Installation Data).
   b. A TGUI has not received radar track updates for a system parameter length of time (Site
       Adaptable Installation Data).
   c. The percentage of ETAs received and displayed by the TGUI during an update cycle is
       below a system parameter percentage of Estimated Time of Arrivals (ETA)s (Site
       Adaptable Installation Data).

When one of the following processes fails during system startup, the M&C SHALL [0018] allow
the remaining processes in the same TRACON/EDC group to become operational:
    a. TGUI
      b. PGUI



                                              11                             TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

The M&C function SHALL [0020] include the ability to automatically reconfigure the system
whenever hardware or software failures occur.

The M&C function SHALL [0022] include the ability to manually reconfigure the system in the
event that automatic reconfiguration fails.

The M&C function SHALL [0021] determine the system to be in one of the following states:
   a. Off State: When no M&C function software is executing.
   b. Standby State: When M&C function is active and is ready to monitor and control the
      system and its component functions.
   c. Run State: When the system is operating normally with all specified functionality.
   d. Reduced State: When the system is operating in a degraded manner (but the degradation
      is not sufficiently serious to be considered a loss of service).

Requirement 0023 has been deleted.

The maximum amount of time allowed between the occurrence of an error and the detection of
the same error SHALL [0024] be a system parameter. This time period will be referred to as the
System Error Detection Time.

The M&C function SHALL [0025] declare a function to be failed if any of the following occur:
   a. The function terminates due to an error condition.
   b. The function fails to respond within the function-specific, site adaptable time (Site
      Adaptable Installation Data).
   c. The function is forcibly terminated because it failed to terminate when instructed.

Function errors SHALL [0026] be classified into one of the following categories:
   a. Critical: An error has occurred from which a function can not recover.
   b. Warning: An error has occurred from which a function can recover.
   c. Informational: A notable event has occurred.

Requirement 0080 has been deleted.

The M&C function interface SHALL [0085] have the capability to put the system in any of the
following states:
    a. Run state.
   b. Standby state.
   c. Off state.




                                               12                              TMA System Spec
                                                                                FAA-E-2971
                                                                           17 December 2008
                                                                                 Final Rev N
The following requirements have been deleted: 0030, 0035, 0036, 0040, 0045, 0046, 0050,
   0060, 0061, 0062, 0063, 0070, 0090, 0100, 0110, 0120, 0130, 0140, 0141, 0142, and 0143.




                                            13                            TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.2    System Capability Requirements

The System's functions are listed in Table 3.2-1 subdivided into the Operational, and Support
categories. The table also identifies the section in which each function is discussed.

                        Table 3.2-1. Operational & Support Functions

          Category       Function                                              Section
          Operational    • TMA Processing                                      3.2.1
                          [function/section deleted]                           3.2.2
                         • TMC-Graphical User Interface (GUI)                  3.2.3
                         • Monitor and Control (M&C)                           3.2.4
                         • Data Management (DM) [deleted]                      3.2.5
                         • Adaptation Data Files                               3.2.6

          Support
                         • Data Analysis & Testing                             3.2.7
                         • Playback                                            3.2.8
                         • Simulation & Time Based Metering (TBM)              3.2.9
                           Training

The Operational functions, listed in Table 3.2-1, provide the required TMA functions at each of
the operational ATC facilities, i.e., ARTCC, TRACON, and Tower. The TMA Processing
function provides the principal processing to optimize the flow of traffic in the operational ATC
environment. The TMC-GUI function provides interactive capabilities for the TMC. The M&C
function provides the overall system management and control of the Operational TMA. NOTE:
The DM function has been eliminated.

The Operational functions are designed so that stand-alone instances of the Operational System
can be created with ability to interact with other instances. Each stand-alone TMA executes in
hardware that is separate from the primary ATC systems but is interfaced to the primary ATC
systems at that facility. The interface is two-way in some facilities, and in others, is one-way.

The Support functions, listed in Table 3.2-1, support the Operational System. These functions
execute in a manner such that they do not interfere with the execution of the Operational System.

The data analysis and testing support functions provide the ability to maintain an existing site
adaptation, provide site analysis for system performance based on data recorded by the
Operational System, and perform testing of new software or adaptation by communicating with a
TESTNAS running on the backup Host processor in two-way mode. These functions are used in
field facilities and in development laboratories.




                                                14                              TMA System Spec
                                                                                   FAA-E-2971
                                                                             17 December 2008
                                                                                    Final Rev N
Two of the remaining Support functions in Table 3.2-1, Playback and Simulation, are expected to
be used only in laboratory environments. The Playback function provides the ability to play
recorded data into the Operational System, and the Simulation function allows the Operational
System to be exercised with simulated aircraft.

The final Support function, TBM Training, allows TMA to provide users with the ability to
perform Time Based Metering Training onsite by communicating with a TESTNAS running on
the backup Host processor to access Host Dynamic Simulator (DYSIM) capabilities.

Each installation of TMA consists of a set of functional groups. Four different functional groups
are identified, as follows:
    • Monitoring and Control (M&C) group, which is one of the following:
            1) Center M&C group
            2) TRACON M&C group
            3) Tower M&C group
    • Data Input/Output (I/O) group, which is one of the following:
            1) Center Data I/O group
            2) TRACON Data I/O group
    • User Input/Output (I/O) group capable of supporting:
            1) TMA displays
    • Data Processing function:
            1) TMA Data Processing group

The M&C group is always present for any TMA installation. The other groups may or may not be
present for a particular installation.

Figure 3.2-1 is a diagram of the TMA system in its four generic installations:
   • Arrival Center TMA
   • Arrival TRACON TMA
   • Adjacent Facility without TMA
   • Control Tower TMA
The figure shows the functional groups necessary for each generic installation.

NOTE: A TMA display is referred to as a Generic Display Station (GDS).




                                               15                                 TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
                    Figure 3.2-1. TMA Generic Installation



            Arrival Center                                       Adjacent Facility
              Center M&C                                           Facility M&C
User I/O        Data I/O           Data Proc                 Data I/O        User I/O
 Group           Group              Group                    Group 1          Group

                Center                                        Facility
GDSs can         Data                                         HDAR
                                                               Data
                                                                             GDSs can
view TMA       Interface             TMA                                     view TMA
                                                             Interface



               TRACON
GDSs can         Data                                                        GDSs can
view TMA       Interface                                                     view TMA


User I/O     Data I/O                                                       User I/O
 Group        Group                                                          Group
      TRACON M&C                                                           Tower M&C

           Arrival TRACON                                           Control Tower


                                     16                                      TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N
The TMA installation in the Arrival Center consists of:
   1) A Center M&C functional group.
   2) A Data I/O group which consists of a one-way or two-way interface with the ARTS and
      interfaces to other TMA installations.
   3) A User I/O group, capable of displaying local TMA output.
   4) Data Processing groups consisting of TMA. TMA receives external inputs from the
      associated TRACONs and other TMA installations.

The TMA installation in an Arrival TRACON consists of:
   1) A TRACON M&C functional group.
   2) A Data I/O group which consists of a one-way or two-way interface with the local ARTS.
   3) A User I/O group capable of displaying TMA output from the associated Center.

The Adjacent Facility Installation can be full-blown Arrival Center installations described above
or a skeletal adjacent installation providing surveillance data to a TMA-equipped adjacent Center
or TRACON. In the latter case, an installation consists of up to three groups:
    1) An M&C group.
   2) An optional User I/O group.
   3) A Data I/O group.

A TMA installation in a Tower consists of:
   1) A Tower M&C group.
   2) A User I/O group capable of displaying TMA output from the associated Center.

Support functions such as Data Recording and Adaptation are not shown on the diagram and are
assumed to be present where there is a Data Processing group.

For the purposes of system design and performance, each TMA system SHALL [0065] have the
capability of populating a maximum of 50 Timeline Graphical User Interface (TGUI) displays
and 50 Planview Graphical User Interface (PGUI) displays. For the system design and
performance calculations, each GDS SHALL [0067] support the outputs of one TGUI or
Planview Graphical User Interface (PGUI).

The TMA software processes input data at process initialization. These files can be classified as
one of the following 5 file types:

      a. Site Independent Data: Site independent data is defined as data that is required to be
      read in at initialization for TMA, but is not dependent on any site-specific characteristics
      or need. Examples of this type of data include:
             adaptation/"site_data"/comm_mgr/cm_defaults and
             realtime_procs/Common_data/trajectory_synthesizer/aircraft_specific_


                                                17                             TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
            model data

      b. Static Site Adaptable Scheduler Data: Static site adaptable scheduler data include
      any input data containing site specific parameters or logic that can impact the TMA
      scheduler (i.e., general airspace, routing, runways, or Dynamic Planner (DP) scheduler
      data), but cannot be modified via command line option or user input during operation.
      Examples of this type of data are all in the site data system directory and include
       General:         runways
       Routing:         analysis_categories
       Runway:          dp_runway_category_definitions
       Scheduler:       stream_classes

      c. Dynamic Site Adaptable Scheduler Data: Dynamic site adaptable scheduler data
      include any input data containing site specific parameters or logic that can impact the
      TMA scheduler (i.e., general airspace, routing, runways, or DP scheduler data) and can be
      modified via command line option or user input during operation. All of these values
      must have defaults in the adaptation data set.

      If a direct one-to-one mapping does not exist between the command line option or user
      input and the input data, then the software will not allow for the user to place the system
      into a situation that is not achievable directly from the input data. The preference is for a
      one-to-one mapping with no logic imposed on the input data from the software; however,
      algorithm and/or Computer Human Interface (CHI) issues may result in a reduced
      capability for the user.

      d. Site Adaptable Installation Data: Site adaptable installation data include any input
      data containing parameters associated with the particular hardware and system
      configuration at a particular site. These values can in no way impact the TMA schedule or
      advisories. The values in this data are not modifiable by the user during runtime.
      Examples of this type of data include:
             realtime_procs/Common_data/system/remote and
             adaptation/"site_data"/wthr_data/wdpd_site_info

      e. Site Adaptable GUI Setup Parameters: Site adaptable GUI setup parameters are
      divided into two subsets:
              GUI Configuration Files -- which contain site specific data such as layouts of the
              gates on a panel and
              Site Adaptable User Preference Data -- which contains PGUI and TGUI display
              defaults that can be controlled by a user (e.g., number of timelines, fixes on a
              timeline, PGUI map choices, etc.)

3.2.1 TMA Processing

The TMA Processing function, hereafter in the section referred to as TMA, operates in the En
Route environment. It produces an arrival plan that meets the flow requirements for the adapted


                                                18                              TMA System Spec
                                                                                        FAA-E-2971
                                                                                  17 December 2008
                                                                                         Final Rev N
airport. It does this by generating a schedule that is conflict-free at the runway and the meter fix
arc if adapted, or scheduling meter fix.

TMA is depicted in Figure 3.2.1-1. The input sources, appearing in italics, are shown at the top
of the figure. The processing steps or sub-functions are shown in the central portion of the
figure. The outputs of the function and their destinations, appearing in italics, are shown at the
bottom.

            WX                              Adjacent                HID                      TMC-GUI
                                           CDI or TDI              CDI

                      Adaptation             Flight Plans        Flight Plans   Controller
         Weather                                                                                TMC
                         data                  & Tracks            & Tracks      entries
          data                                                                                 entries



                                            Aircraft Processing
                                                Initial meter fix & runway

                                                Route Analysis
                                                            Routes


                                                ETA Generation
                                                             ETAs


                                                    Scheduling
                                       Meter List                        STAs,
                                                                        Runways,
                                         CDI                              MiT


 All processes interact with M&C.
                                        HID                           TMC-GUI



                                    Figure 3.2.1-1. TMA Function

As depicted in Figure 3.2.1-1, the functions within TMA are:
   • Aircraft Processing.
   • Route Analysis.
   • ETA Generation.
   • Scheduling.

TMA makes continuous predictions, based on the current track or converted route (received with
the HCS flight plan or generated by TMA) and winds aloft data, of arrival aircraft routes and
ETAs for several locations, i.e., Runway Threshold, Final Approach Fix (FAF), Scheduling
Meter Fix, CTAS Meter Fix, Meter Fix Arc if adapted, and Outer Arc. The ETAs are used by the
Scheduling function to determine the aircraft Scheduled Times of Arrival (STAs).



                                                            19                                           TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N

The Scheduling function utilizes the available airspace at, or as close as possible to, its
designated capacity, operating in light of several constraints on the arrival traffic.

Scheduling is based on a time-based metering approach. In-Center and In-TRACON departures
can also be scheduled.

After the Scheduling is complete the scheduled load to the TRACON and airport is displayed to
the TMCs. ETAs and STAs are output to the TMCs. Additionally, if time-based scheduling is in
effect, the results in the form of a meter list can be sent to the HCS by the TMC via the Host
Interface Device (HID) for display to feeder Sector Controllers at the en-route facility.

All references in “SHALL” statements to “TRACON” should be interpreted as “the TRACON
which contains the arrival airport for a particular aircraft” unless specifically identified as a
different case (e.g., the departure TRACON).

Requirement 0135 has been moved to Section 3.2.1.5.7.

3.2.1.1 Inputs & Outputs

TMA SHALL [0145] use the following inputs:
  a. Adaptation data files.
   b. In-Center aircraft data from the local HID/NAS Local Area Network (LAN).
   c. Adjacent Facility aircraft data from the Adjacent Facility TDI or CDI.
   d. Rapid Update Cycle (RUC) weather data.
   e. TMC entries from the TMC-GUI.
   f. Sector controller entries from the HCS via the HID/NAS LAN.
   g. Control data from the M&C function.
   h. Flight plan and track data from ETMS

TMA SHALL [0146] obtain all available track surveillance data/or flight plan data for all aircraft
from any ARTCC that is,

   a) defined in the SSDD as an Adjacent Center Data Feed facility,
   b) in whole or part, is within 200 nm of a TMA adapted airport,

and is neither an:

   c) Oceanic System,
   d) Air traffic control system under the control of a foreign country.




                                                 20                               TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
TMA SHALL [0144] accept and process ARTS flight plan and track data.

TMA SHALL [0151], when specified using system configuration parameters, process Host
DYSIM generated flights in the same manner as non-DYSIM.

TMA SHALL [0152] not process data for any aircraft identified by site adapted beacon codes.

TMA SHALL [0147] perform ETA generation, track update processing, and scheduling for
aircraft destined for a TMA-adapted airport using information from all configured data sources
which can include: the primary arrival Center’s Host, one or more adjacent Center’s Host(s),
ETMS, and the primary arrival TRACON.

Requirements 0148 and 0149 have been deleted.

For the purposes of scheduling, TMA SHALL [0150] meet performance requirements for up to
750 aircraft, maximum. Out of those 750 aircraft, for the purposes of performing track update
processing, TMA SHALL [0160] meet performance requirements for up to 360 tracked aircraft,
maximum. (Examples are message response times and ETA update times.)

TMA SHALL [0161] support up to 32 CTAS meter fixes per TRACON.
TMA SHALL [0162] support up to 12 outer meter fixes/arcs per meter fix/arc.
TMA SHALL [0163] support up to 10 CTAS meter fixes per feeder gate.
TMA SHALL [0164] support up to 15 feeder gates per TRACON.
TMA SHALL [0165] support up to 16 runway thresholds per airport.
TMA SHALL [0166] support up to 48 stream class configurations per TRACON.
TMA SHALL [0167] support up to 75000 NAS Waypoints.
TMA SHALL [0168] support up to 200 TMA Waypoints.
TMA SHALL [0169] support up to 8 Adjacent Centers.
TMA SHALL [0171] support up to 1800 Satellite Airports.

Requirements 0170 and 0750 have been combined into one requirement. See Requirement 1552
in Section 3.2.1.5.7.

TMA SHALL [0180] read and use the following adaptation databases:
  a. Meter fixes (Host adapted meter fixes, CTAS meter fixes, scheduling meter fixes).
   b. (sub-requirement deleted)
   c. Nominal TRACON routes.
   d. Nominal TRACON speeds.
   e. Stream class definitions.
   f. Permissible super stream classes.
   g. TMA adaptable airports (Static Site Adaptable Scheduler Data).
   h. Available runways.



                                              21                             TMA System Spec
                                                                                    FAA-E-2971
                                                                              17 December 2008
                                                                                     Final Rev N
   i. Permissible MiT settings including blends (i.e., use of different MiT values for different
      aircraft types in the same super stream). {Subrequirement i is deferred}
   j. Runway allocation adaptation.
   k. Aircraft characteristics including engine and drag models.
   l. nas_pdrs

When the TMA function receives aircraft data, it SHALL [0190] update its ETAs within six (6)
seconds.

Whenever the TMA function receives new weather data, it SHALL [0200] update its weather
information within 30 seconds.

When TMA receives the Sector Controller command to swap between two and five aircraft,
TMA SHALL [0210] re-sequence the affected aircraft by exchanging the STAs and runway
assignments, unless a rejection condition is met, as described in requirement [0237].

For cases in which only the standard TMC swap processing has been enabled in adaptation and
TMA has received TMC input to swap two aircraft destined for the same airport where either
aircraft type has no adapted restriction on runway use, TMA SHALL [0202] re-sequence the
affected aircraft by exchanging the STAs and runway assignments, unless a rejection condition is
met, as described in requirement [0204].

For cases in which standard TMC swap processing and recalculation of upstream MRP(s) have
been enabled in adaptation and TMA has received TMC input to swap two aircraft destined for
the same airport where either aircraft type has no adapted restriction on runway use, TMA
SHALL [0192] re-sequence the affected aircraft by exchanging the STAs at the TMC swapped
meter reference point level and any downstream meter reference point(s) STAs and runway
assignments, recalculate the non-traversed upstream meter reference point STAs using the
computed delay at the TMA swapped meter reference point, current ETAs, and current AMDT
values of the affected aircraft, unless a rejection condition is met, as described in requirement
[0204].

NOTE: AMDT is the maximum delay that can be absorbed within the performance
characteristics of a large set of aircraft types on the trajectory between two assigned MRPs.

For cases in which only the standard TMC swap processing has been enabled in adaptation and
TMA has received TMC input to swap two aircraft destined for different airports or where either
aircraft type has an adapted restriction on runway use, TMA SHALL [0203] re-sequence the
affected aircraft by recalculating the runway STAs and exchanging other STAs, unless a rejection
condition is met, as described in requirement [0204].

For cases in which standard TMC swap processing and recalculation of upstream MRP(s) have
been enabled in adaptation and TMA has received TMC input to swap two aircraft destined for
the different airports or where either aircraft type has an adapted restriction on runway use, TMA


                                                22                              TMA System Spec
                                                                                        FAA-E-2971
                                                                                   17 December 2008
                                                                                         Final Rev N
SHALL [0194] re-sequence the affected aircraft by recalculating the runway STAs and
exchanging the STAs at TMC swapped meter reference point level and any downstream meter
reference point(s) STAs, recalculate the non-traversed upstream meter reference point STAs
using the computed delay at the TMA swapped MRP, current ETAs, and current AMDT values
of the affected aircraft, unless a rejection condition is met, as described in requirement [0204].

In the event that a TMC selects aircraft from two different meter reference point levels, the level
closest to the meter fix SHALL [0196] be used for the swap level.

For cases in which standard TMC swap processing has been enabled in adaptation and TMA has
received TMC input to swap two scheduled, but not departed, internal departure aircraft
departing from the same airport and departure configuration, if assigned, TMA SHALL [0206]
exchange the scheduled departure times (STDs) in addition to performing other standard TMC
swap processing, unless a rejection condition is met, as described in requirement [0204].

TMA SHALL [0204] reject the TMC input of a swap request if standard swapping has been
enabled in adaptation and the aircraft have different stream classes that are not in the same
superstream.

When alternate TMC swap processing has been enabled in adaptation in arrival TMA mode and
TMA has received TMC input to swap non-runway STAs for two aircraft (i.e. both aircraft were
selected from non-runway timelines) that are assigned to different meter fixes, TMA SHALL
[0257] reject the swap request.

When alternate TMC swap processing has been enabled in adaptation and TMA has received a
TMC swap request that includes a non-runway STA for two aircraft assigned to the same meter
fix that are destined for the same airport, where both aircraft types have no adapted runway
restrictions, TMA SHALL [0258] swap the runway assignments and the aircraft STAs at the
meter reference point level closest to the runway, based upon the timelines used by the TMC
when selecting the aircraft to be swapped. TMA SHALL [0263] recalculate the total delay at that
meter point, apportioning it to the scheduling segments going backwards along the flight route
until all delay has been distributed, and SHALL [0264] assign maximum delay to all of the
flight’s downstream route segments.

When alternate TMC swap processing has been enabled in adaptation and TMA has received a
TMC swap request that includes a non-runway STA for two aircraft assigned to the same meter
fix that are destined for different airports, or where either aircraft type has a runway restriction on
the intended runway, TMA SHALL [0259]swap the aircraft STAs at the meter reference point
level closest to the runway, based upon the timelines used by the TMC when selecting the
aircraft to be swapped. TMA SHALL [0265] recalculate the total delay at that meter reference
point, apportioning it to the scheduling segments going backwards along the flight route until all
delay has been distributed, and SHALL [0266] assign maximum delay to all of the flight’s
downstream route segments, while making no change to the runway assignments.




                                                  23                               TMA System Spec
                                                                                    FAA-E-2971
                                                                             17 December 2008
                                                                                     Final Rev N
Excess delay normally assigned downstream of the meter reference point level for the swapped
aircraft SHALL [0267] be assigned at the outermost meter reference point, per the standard
method for allocating delay.

When alternate TMC swap processing has been enabled in adaptation and TMA has received
TMC input to swap runway STAs for two aircraft that are destined for the same airport, where
both aircraft types have no adapted runway restrictions, TMA SHALL [0261] exchange runway
STAs and runway assignments. TMA SHALL [0268] then recalculate the total runway delay,
apportioning it to the scheduling segments going backwards along the flight route until all delay
has been distributed.

When alternate TMC swap processing has been enabled in adaptation and TMA has received
TMC input to swap runway STAs for two aircraft that are destined for different airports, or
where either aircraft type has a runway restriction on the intended runway, TMA SHALL [0262]
exchange runway STAs. TMA SHALL [0269] then recalculate the total runway delay,
apportioning it to the scheduling segments going backward along the flight route until all delay
has been distributed, while making no change to the runway assignments.

Requirements 0204a and 0204b have been deleted.

Whenever TMA receives TMC input to AutoSwap aircraft (i.e., swap aircraft in a stream class),
TMA SHALL [0212] re-sequence only frozen aircraft by exchanging the STAs and runway
assignments. To ensure a flight is not given an STA that is too far ahead of its ETA, a flight that
is being AutoSwapped SHALL [0211] retain its original STA if the new STA is more than an
adaptable parameter ahead of its ETA. TMA SHALL [0213] be able to swap flights based on:
    a. altitude
   b. holding arc crossing time
   c. outer arc crossing time

The type of arc to use at a site SHALL [0215] be defined in site adaptation data. When
swapping, TMA SHALL [0216] exempt from swapping aircraft in the stream that do not have a
crossing time at the arc in use at that site. These aircraft are considered to not yet be in holding
and SHALL [0214] be given STAs that are after the aircraft that have been autoswapped. Those
aircraft not yet in holding will be ordered sequentially by the current set of available STAs.
TMA SHALL [0217] optionally include in swapping any of the following:
    a. manually scheduled aircraft
   b. internal departures

The meter list broadcast status SHALL [0219] remain in the same state as it was before the
swapping.

Requirement 0220 has been deleted.




                                                 24                              TMA System Spec
                                                                             FAA-E-2971
                                                                       17 December 2008
                                                                              Final Rev N
TMA SHALL [0221] be capable of handling a maximum of two future configuration changes at
any given time. {Requirement 0221 is deferred}

TMA SHALL [0222] process changes that can be made in the future:
  a. Airport configuration change (which includes the runway acceptance rate).
     {Subrequirement a is deferred}
   b. Airport acceptance rate change.
   c. TRACON acceptance rate change.
   d. (subrequirement deleted).
   e. Separation matrix change (this is the separation at the runway)
   f. Gate and scheduling meter fix acceptance rate change.
   g. Stream class setting change (which is the miles-in-trail)
    h. Runway occupancy time (per runway).
All these changes can be made independently, and the TMA will allow the user to enter up to two
future changes per category (a,...h).

TMA SHALL [0224] be capable of handling a site adaptable time interval (with a maximum of
90 minutes) (Site Adaptable Installation Data) during which a future change can be specified.
Any change that is attempted for further in the future than this interval will be rejected. This
maximum scheduled time will be site specific, however not changeable during system operation.
A maximum of two future changes can be scheduled.

TMA SHALL [0225] produce the following outputs:
  a. TMC display data to the TMC-GUI.
   b. Meter List to Sector Controllers, via the HID/NAS LAN and HCS, located at any of the
      following:
       1. The Primary Arrival Center
       2. Up to eight Adjacent Centers
   c. Status monitoring data to the M&C function.
   d. Aircraft flight information to the CAP system. {Subrequirement d is deferred.}

TMA SHALL [0230] send the following meter list data to the HCS via the HID/NAS LAN:
  a. Aircraft computer ID (CID).
  b. Airport identifier.
  c. Runway configuration.
  d. Airport acceptance rate.
  e. Assigned CTAS meter fix or meter fix arc and, if adapted, the assigned outer fix.
  f. Scheduled time of arrival (STA) to the CTAS meter fix or meter fix arc and, if adapted,
     the outer meter arc. The STA will be sent to the HCS in the form “hhmmss”. The HCS
     controls the format of the STA display on the DSR.



                                               25                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                 17 December 2008
                                                                                        Final Rev N
   g. Delay to absorb prior to reaching the CTAS meter fix or meter fix arc and, if adapted,
       the outer meter arc. The delay time will be sent to the HCS in the form “(-)mms”, where
       s is tens of seconds. If adapted for delay time rounding, delay times sent to the HOST
       will be rounded to the nearest tens of seconds. If adapted for delay time truncating,
       delay time minutes sent to the HOST will be rounded down and have the tens of seconds
       set to zero. The HCS controls the format of the delay time display on the DSR.
   h. Special display indicators. If a meter fix arc is adapted, the meter fix sector display
      indicator will be set to arc mode. If no meter fix arc is adapted, the meter fix sector
      display indicator will be set to list mode. The outer fix sector display will be set to arc
      mode. (See NAS-IR-82170001, Interface Requirements Document (IRD) ARTCC
      HCS/ATM Applications; N0070, HCS Common Message Set (CMS) Functional
      Requirements to Accommodate ATM Applications; and NAS Change Proposal/Casefile
      UA500-CPF-002, Modification of HCS Software to Provide an HCS/ATM Applications
      Common Interface).

TMA SHALL [0231] block the output of the meter list data after the following TMC inputs:
  a. Changes to airport/runway configuration or scheduling constraints
  b. Changes to TRACON acceptance rate
  c. Changes to TRACON buffer
  d. Changes to Gate and Meter Fix acceptance rates
  e. Changes to stream class miles-in-trail constraints
  f. Creation of or changes to Blocked intervals for meter fixes or runways
  g. Creation of or changes to Single Gate Free Flow periods
  h. Reschedule of multiple aircraft
  i. Allocate runway for multiple aircraft
  j. Assign runway for multiple aircraft
  k. Changes to the freeze horizon settings

The output of meter list data SHALL [0232] be blocked until re-enabled by the TMC.

TMA SHALL [0239] be capable of blocking and re-enabling the output of the meter list data
separately for each airport.

Requirement 0233 has been moved to Section 3.2.1.5.7.

The meter list data SHALL [0234] be able to be filtered by the joint criteria of arrival airport and
the Center to which meter list data is to be sent (Dynamic site adaptable data).

The purpose of the following SHALL is to prevent changes in Host TMAD status or in One
Way/Two Way status from changing the airport/Center meter list filter settings.

TMA SHALL [0238] modify airport/Center meter list filter settings only in response to TMC
input.

Requirement 0235 has been deleted.


                                                 26                              TMA System Spec
                                                                                        FAA-E-2971
                                                                                   17 December 2008
                                                                                         Final Rev N

TMA SHALL [0237] send a reject message to the HCS whenever it receives a swap or
resequence message from a sector controller for between two and five aircraft and any of the
aircraft have:
    a. A different arrival airport
    b. A different gate
    c. A different engine type
    d. (subrequirement [d] deleted)
    e. Not been frozen

TMA SHALL [0236] prevent meter list information from being sent to the Host for NOFIX
aircraft when operating in the 320 patch environment.

Eligibility for non-frozen aircraft to be selected for inclusion in the meter list information sent to
the Host SHALL [0241] be defined as Static Site Adaptable Data.

Aircraft SHALL [0242] be eligible for display on the Host Meter Lists if all of the following are
true:
    a. The flight is frozen, or the receiving metering facility is adapted to display metering data
       for non-frozen flights
    b. The flight’s ETA or distance, depending on adaptation, is calculated to be inside the
       meter list display interval value
    c. The flight has not yet reached the meter reference point, or the flight’s ETA or distance,
       depending on adaptation, has not yet reached the meter list drop point.

Once an aircraft (frozen or non- frozen) is eligible for display, its eligibility for display SHALL
[0244] not change if its ETA or distance, depending on adaptation, is calculated to be outside the
meter list display interval value.

A field exists in the meter list information message to specify the state of the aircraft as either
frozen or unfrozen. The effect of setting this field to frozen produces a frozen status indicator
symbol one space to the left of the aircraft id in the Meter Fix/Outer Fix Sector List. TMA
SHALL [0243] have the capability to set the frozen status indicator symbol display parameter to
apply to either frozen or non-frozen aircraft through Static Site Adaptable Data.

Meter list display eligibility SHALL [0247] be computed using the aircraft’s ETA or distance,
depending on adaptation, to the associated meter reference point.

TMA SHALL [0248] be capable of setting unique static site adaptable values for each meter
reference point for the following meter list display parameters:
    a. Meter list display interval value
    b. Meter list display drop parameter value
    c. Meter list display interval value set by distance or time
    d. Meter list display drop parameter value by distance or time



                                                  27                               TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N
TMA SHALL [0249] be capable of setting unique static site adaptable values for each metered
facility (local and adjacent) for the following meter list display parameters:
    a. Display/non-display of frozen/non-frozen aircraft
    b. Display/non-display of pennant symbol for frozen/non-frozen/ aircraft
    c. Rounding/truncation of delay value

TMA SHALL [0245] send a copy of the Host meter list entry to multiple sectors as defined in
adaptation. TMA SHALL [0246] suppress only the HOST meter list entry at the sector
sending the list entry suppression message.

If adapted, TMA SHALL [0252] provide the following as alternate values for display on the
meter list of any upstream meter reference point:
    a. MRP name
    b. Downstream MRP STA
    c. Delay value based on downstream MRP delay and AMDT

When an alternate downstream MRP is used TMA SHALL [0253] use the upstream meter
reference point’s meter list control parameters (eg. display/drop interval) and aircraft filtering
during meter determination processing.

TMA SHALL [0251] provide the capability to dynamically use Special Use Airspace (SUA) in
determining an aircraft’s route of flight. ETAs of tracked aircraft in the SUA area or those
projected to traverse the SUA area would not change until the next track hit, when RA would
reevaluate the analysis category and update the RA route. Updated ETAs for proposed and
estimated aircraft would occur when CM sends a FLIGHT_PLAN_ETA_REQUEST to RA for
each aircraft upon receipt of the new message.


Requirements 0240 and 0250 have been deleted.


3.2.1.2 Aircraft Processing

In most cases, the first notification of a new aircraft to the TMA Processing function is the
receipt of the Flight Plan from the HCS or ETMS. In other cases, the initial receipt of a flight
plan may be from the TRACON Data Interface (TDI) especially if the TRACON is very large
such as in the case of the Southern California TRACON. The initial flight plan may be received
from the adjacent center in some cases, or could be received from a nearby TRACON. In
response to an initial flight plan, the function calculates a nominal ETA that is sent to the TMC
GUI function.

Since HADDS requests flight plans for all aircraft that it receives a track message for prior to a
flight plan, TMA SHALL [0254] configure the HADDS API to block the forwarding of track
messages if the associated flight plan message was not previously sent to TMA by HADDS.



                                                 28                               TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N
Requirement 0255 has been deleted.

If TMA does not have a flight plan corresponding to a track message, TMA SHALL [0256]
ignore the associated track message.

Upon receipt of a new flight plan, TMA SHALL [0260] parse:
   a. Aircraft type.
   b. Assigned altitude.
   c. Filed True Air Speed (TAS).
   d. Route(s) of flight (filed route 10a and, if present, applied route 10b).
   e. Aircraft ID including:
       1. Callsign
       2. Optional CID, when provided
       3. Flight Unique Identifier (FLUID) (ERAM Only)
       4. Site Specific Plan Identifier (SSPI) (ERAM Only)
   f. Aircraft beacon code.
   g. Company ID.

Upon receipt of a HOST converted route, TMA SHALL [0270] determine the following
information based on the current flight plan information and the Host converted route:
a. Coordination Time.
b. Coordination Fix.
c. CTAS Meter Fix.
d. Route of flight from the Coordination Fix to the CTAS Meter Fix.
e. NOFIX Indication (TMA Pseudo Fix determination).

TMA SHALL [0272] generate a converted route from the longest Field 10 in a compatible flight
plan associated with the current aircraft; and merge into that converted route any Host converted
route segments on hand for associated flight plans that also have a compatible Field 10.
Compatible here means that one flight plan Field 10 is either the same as the other or is a tailored
copy (i.e., portions of the Field 10 have been removed from the beginning).

Where the usage of Field 10b is configured and available, TMA SHALL [0273] generate a
converted route from the applied route (Field 10b).

Where the usage of Field 10b is not available, TMA SHALL [0274] generate a converted route
from the filed route (Field 10a).

Requirement 0275 has been deleted.




                                                29                               TMA System Spec
                                                                                  FAA-E-2971
                                                                           17 December 2008
                                                                                   Final Rev N
TMA SHALL [0276] delete a flight plan from processing and display as a result of the following:
  a. TMA receives a deletion message from the HCS, ETMS, or ARTS
   b. The flight plan has not been updated for 6 hours.

Requirement 0280 has been replaced by requirement 0410.
Requirement 0290 has been deleted.

Upon receipt of and based on a flight plan, TMA SHALL [0300] calculate an initial ETA for the
aircraft at the:
    a. Outer Meter Arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS Meter Fix or Meter Fix Arc, if adapted.
   b1. Scheduling Meter Fix or Meter Fix Arc, if adapted.
   c. FAF.
   d. Runway Threshold.

3.2.1.3 Route Analysis

For TMA, the Route Analysis (RA) function determines the aircraft situation (analysis category),
generates a route to the CTAS meter fix, and generates a nominal route from the CTAS meter fix
to the runway.

TMA SHALL [0310] process the following information, at a minimum, to construct a nominal
route from the aircraft’s current position to an adapted runway threshold:
    a. Track data.
   b. Flight plan converted route data.
   c. Aircraft type data.
   d. Adapted information about the assigned runway.
   e. Configuration anticipated to be in effect at landing.
   f. Arrival feeder gate information.
   g. Arrival CTAS meter fix information.
   h. Aircraft analysis category.
   i. Stream class definitions.
   j. Airline preferred speed and altitude profiles, if applicable.


Requirements 0315 and 0316 have been deleted.




                                                30                           TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.2.1.3.1     Fix/Arc Assignment

This function chooses the arrival CTAS meter fix utilizing the information contained in the flight
plan and the converted route. Typically, the CTAS meter fix is contained in the converted route.

TMA will recompute CTAS meter fix assignments following a change in a flight’s anticipated
arrival airport configuration or when the flight’s Host converted route is updated.


3.2.1.3.1.1     CTAS Meter Fix/Scheduling Meter Fix Assignment

TMA SHALL [0325] determine the CTAS meter fix based on logic defined in static site
adaptable scheduler data and based on one of the following:
   a. Upon receipt of an en route Flight Plan
   b. Upon receipt of an ARTS/STARS flight plan when no en route flight plan and converted
       route have been received
   c. Upon a change in the airport configuration anticipated to be in effect at the aircraft’s
       projected arrival time.
   d. Upon receipt of an ETMS flight plan when no en route flight plan has been received.

Requirement 0320 has been deleted.

TMA SHALL [0330] first attempt to assign an aircraft a CTAS meter fix using site adaptable
logic (meter fix decision tree) based on the following inputs:
    a. The presence or absence of site specific waypoints in the converted route.
   b. The aircraft's engine class (i.e., Heavy, Jet, Turboprop or Piston).
   c. (subrequirement deleted).

If there is more than one eligible CTAS meter fix in the converted route, TMA SHALL [0331]
assign the CTAS meter fix that is farthest along the route from the current position.

If the evaluation of the converted route does not result in a CTAS meter fix assignment, then the
aircraft is considered a NOFIX aircraft. NOFIX aircraft are internally allocated to the closest
CTAS meter fix to the intersection of the converted route and the TRACON boundary and
evaluated for inclusion in an adapted meter fix arc based on the projected route of flight. Those
NOFIX aircraft that are assigned a meter fix arc are scheduled as if they were going over a CTAS
meter fix. Those NOFIX aircraft that are not within a meter fix arc are only scheduled to the
runway, using the closest CTAS meter fix for stream class and runway assignment and route
generation.

In the event that the site adaptable logic (Static Site Adaptable Scheduler Data) does not assign a
CTAS meter fix from the route, TMA SHALL [0340]:
    a. Determine the intersection point between the converted route and the TRACON
        boundary.


                                                31                              TMA System Spec
                                                                                FAA-E-2971
                                                                         17 December 2008
                                                                                 Final Rev N
   b. Determine the CTAS meter fix closest to the TRACON intersection that is compatible
      with the aircraft’s engine type.
   c.   Provide the TMC with an indicator on the timeline display, if enabled in Site Adaptable
        GUI Setup Parameters.


TMA SHALL [0341] assign a scheduling meter fix using site adaptable logic based on the
following:
   a. The assigned CTAS meter fix.
   b. The aircraft’s engine type.
   c. The destination airport.
   d. Configuration.

TMA SHALL [0361] assign a gate for an aircraft from static site adaptable scheduler data based
on the assigned meter fix. TMA SHALL [0362] assign a gate for an aircraft whenever it:
     a. Receives a new flight plan
     b. Determines the meter fix has changed.

Requirements 0350, 0360, 0370, and 0380 have been deleted.

3.2.1.3.1.2    Meter Fix Arc Assignment

Under certain airport conditions, a meter fix arc is more applicable for scheduling than a CTAS
meter fix. A meter fix arc is an arc at an adapted distance and direction from a runway or airport
for which TMA calculates ETAs and STAs. A meter fix arc is adaptable by airport configuration
and by engine type. If adapted, a meter fix arc uses the attributes of its associated CTAS meter
fix for route generation, route recovery, and the application of constraints in addition to the
generation of ETAs and STAs. In addition, the meter fix arc times are sent to the HCS for
display on the relevant meter fix sector list. If no meter fix arc is adapted, then the assigned
CTAS meter fix will be used for route generation and time calculations at the meter fix.

TMA SHALL [0332] assign a meter fix arc to an aircraft using site adaptable logic (Static Site
Adaptable Scheduler Data) based on the following:
a. The intersection of the projected converted route with an adapted meter fix arc.
b. The aircraft’s engine class.
c. The airport configuration anticipated to be in effect at the aircraft’s projected arrival time.
d. CTAS meter fix.

TMA SHALL [0334] assign a meter fix arc for an aircraft whenever it:
a. Receives a new flight plan.
b. Receives a flight plan amendment for an aircraft modifying the converted route of flight.
c. Determines that the aircraft will land under a different configuration than currently assigned.



                                                 32                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.2.1.3.1.3    Outer Fix Assignment

TMA SHALL [0342] assign an outer fix to an aircraft using site adaptable logic (Static Site
Adaptable Scheduler Data) based on the following:
   a. The assigned CTAS meter fix.
   b. The presence of the site adaptable outer fix in the converted route of flight.
   c. Adaptable engine class.

If there is more than one eligible outer fix in the converted route, TMA SHALL [0344] assign the
outer fix that is farthest along the route from the current position.

TMA SHALL [0346] assign an outer fix for an aircraft whenever it:
  a. Receives a new flight plan, i.e., unknown to TMA.
   b. Receives a flight plan amendment for an aircraft modifying the converted route.

3.2.1.3.1.4    Outer Meter Arc Assignment

An outer meter arc is an arc with an adapted distance and angle from a CTAS meter fix for which
TMA calculates ETAs and STAs. In addition, the outer meter arc times are displayed on the
HCS sector lists. Also, outer meter arcs are used in AutoSwap processing to designate holding
areas. TMA assigns an outer meter arc through adaptation based on the aircraft’s assigned
CTAS meter fix, engine type and the intersection of the route of flight with the adapted outer
meter arc. Aircraft without an assigned CTAS meter fix use the closest associated CTAS meter
fix to assign the outer meter arc.

TMA SHALL [0352] assign an outer meter arc to an aircraft using site-adaptable logic (Static
Site Adaptable Scheduler Data) based on the following:
    a. The intersection of the converted route with an adapted outer meter arc.
   b. Assigned CTAS meter fix, or associated CTAS meter fix, as applicable.
   c. Engine type.
   d. Aircraft filed altitude.

If an aircraft cannot be assigned an outer meter arc via the above criteria, then TMA SHALL
[0353] assign the first eligible outer meter arc adapted. If an aircraft cannot be assigned an outer
meter arc, and TMA is using outer meter arcs to designate holding areas, then the aircraft will not
be eligible for AutoSwap processing.

If an aircraft is eligible for more than one outer meter arc, then TMA SHALL [0354] assign the
first adapted outer meter arc.

TMA SHALL [0356] assign an outer meter arc to an aircraft whenever it:
  a. Receives a new flight plan.


                                                33                              TMA System Spec
                                                                                   FAA-E-2971
                                                                            17 December 2008
                                                                                    Final Rev N
   b. Receives a flight plan amendment that modifies the converted route of flight or engine
      type.
   c. Receives a flight plan amendment that modifies the filed altitude.


3.2.1.3.1.5    Outer-outer Arc Assignment

An Outer-outer arc is an arc with an adapted distance and angle from an adapted TMA waypoint
for which TMA calculates ETAs and STAs. In addition, the Outer-outer arc times are displayed
on the HCS sector lists. TMA assigns an Outer-outer arc through adaptation based on the
aircraft’s assigned Outer meter arc, engine type, assigned altitude and the intersection of the route
of flight with the adapted Outer meter arc.

TMA SHALL [0371] assign an Outer-outer arc to an aircraft using site-adaptable logic (Static
Site Adaptable Scheduler Data) based on the following:
    a. The intersection of the converted route with an adapted Outer-outer arc.
    b. Assigned Outer meter arc.
    c. Engine type.
    d. Aircraft assigned altitude.

If an aircraft cannot be assigned an Outer-outer arc via the above criteria, then TMA SHALL
[0372] assign the first eligible Outer-outer arc adapted.

If an aircraft is eligible for more than one Outer-outer arc, then TMA SHALL [0373] assign the
first adapted Outer-outer arc.

TMA SHALL [0375] assign an Outer-outer arc to an aircraft whenever it:
  a. Receives a new flight plan.
  b. Receives a flight plan amendment that modifies the converted route of flight or engine
     type.
  c. Receives a flight plan amendment that modifies the assigned altitude.

3.2.1.3.1.6    Outer-Three Arc Assignment

An Outer-Three Arc (O3A) is an arc with an adapted distance and angle from an adapted CTAS
waypoint for which TMA calculates ETAs and STAs. This arc is typically located beyond the
Outer-Outer Arc. In addition, the Outer-Three Arc times are displayed on the HCS sector lists.

TMA SHALL [0381] assign an Outer-Three Arc to an aircraft using site-adaptable logic (Static
Site Adaptable Scheduler Data) based on the following:
    a. The intersection of the HCS converted route with an adapted Outer-Three Arc.
    b. Assigned Outer-Outer Arc.
    c. Engine type.
    d. Aircraft assigned altitude.


                                                 34                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

If an aircraft is eligible for more than one Outer-Three Arc, then TMA SHALL [0383] assign the
first adapted Outer-Three Arc.

TMA SHALL [0384] assign an Outer-Three Arc to an aircraft whenever it:
  a. Receives a new flight plan.
  b. Receives a flight plan amendment that modifies the converted route of flight or engine
     type.
  c. Receives a flight plan amendment that modifies the assigned altitude.


3.2.1.3.1.7    Holding Arc Assignment

A holding arc is an arc with an adapted distance and angle from a center waypoint allowing hold
areas, which may not be coincident with an outer meter arc, to be defined in TMA. Holding arcs
are used in AutoSwap processing. TMA SHALL [0385] assign a holding arc to an aircraft using
site-adaptable logic (Static Site Adaptable Scheduler Data) based on the intersection of the
converted route with an adapted holding arc. If any aircraft cannot be assigned a holding arc, and
TMA is using holding arcs to designate holding areas, then the aircraft will not be eligible for
AutoSwap processing.

If an aircraft is eligible for more than one holding arc, then TMA SHALL [0387] assign the first
eligible adapted holding arc.

TMA SHALL [0389] assign a holding arc to an aircraft whenever it:
  a. Receives a new flight plan.
   b. Receives a flight plan amendment that modifies the converted route of flight.
   c. Receives a new airport configuration change.

3.2.1.3.2      Stream Class Assignment

TMA SHALL [0400] assign a stream class for each aircraft based on site adapted rules that take
into account:
    a. Aircraft engine class.
   b. Presently assigned CTAS meter fix.
   c. Airport configuration anticipated for the time of landing at the arrival airport.
   d. Destination airport.
   e. (subrequirement deleted)
   f. Departure fix.
   g. Filed altitude.
   h. Filed airspeed {subrequirement h is deferred}



                                                35                              TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N
   i. Route string
   j. TMA Converted Route


The route string (i) is a direct subset of the flight plan route field. The flight’s TMA converted
route (j) crosses an adapted line, the size and location of which is determined by traffic patterns.

TMA SHALL [0390] reassign a stream class for each aircraft whenever any of that aircraft's
following data changes:
    a. CTAS meter fix
    b. Route
    c. Anticipated arrival configuration (subrequirement is deferred)



3.2.1.3.3      Runway Assignment

Whenever TMA receives a new flight plan for an aircraft, it SHALL [0410] assign the aircraft to
the default runway based on site adapted rules that take into account:
    a. Aircraft engine class.
   b. Assigned stream class.
   c. Anticipated arrival configuration at the time of landing.

When TMA modifies the ETA for an unscheduled internal departure due to a change in EDCT
processing, and the change in ETA causes the aircraft to land in a different airport configuration,
it SHALL [0412] assign the aircraft to the default runway based on site adapted rules that take
into account:
    a. Aircraft engine class.
   b. Assigned stream class.
   c. Anticipated arrival configuration at the time of landing.

When TMA modifies the ETA for an unscheduled internal departure that has not departed at its
estimated time of departure, and the change in ETA causes the aircraft to land in a different
airport configuration, it SHALL [0414] assign the aircraft to the default runway based on site
adapted rules that take into account:
    a. Aircraft engine class.
    b. Assigned stream class
    c. Anticipated arrival configuration at the time of landing.

From the time of initial runway assignment until the time that scheduling of the aircraft is
terminated (or "frozen"), an aircraft is periodically considered for alternate runway assignments.
Different events cause different subsets of aircraft to be reviewed for runway reassignment, as
described below.


                                                 36                              TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N

TMA SHALL [0420] perform runway allocation based on certain conditions or events as
follows:

          Event                                     TMA SHALL [0420] allocate
                                                    runways for:
   a.     TMC enters:                               All aircraft assigned to the runway
          New blocked runway interval.              being blocked which are currently
                                                    scheduled to land during the blocked
                                                    interval.
   b.     TMC enters:                               All aircraft on any other runway
          Remove blocked runway interval.           scheduled during the blocked interval.
   c.     TMC enters:                               All aircraft assigned to any other
          Increase of a runway acceptance rate.     runway.
   d.     TMC enters:                               All aircraft assigned to this runway.
          Decrease of a runway acceptance rate.
   e.     TMC enters:                               The aircraft whose arrival configuration
          Changes concerning pending airport        is anticipated to change.
          configuration change(s).
   f.     TMC enters:                               The manually scheduled aircraft.
          Manual Scheduling of a TMA Internal
          Departure.
   g.     Receipt of a flight plan amendment with   Only the aircraft that just departed.
          a d-time from the HCS for a TMA
          Internal Departure, unless the aircraft
          departure has been manually scheduled
          and frozen by the TMC.
   h.     Determination that an aircraft's STA is   Only the aircraft which is about to be
          about to be frozen (by TMA).              frozen.
   i.     TMC enters:                               Only the aircraft which has been reset.
          A command "resetting" an aircraft's
          ETA. This procedure will remove an
          aircraft from scheduling for one
          scheduling cycle, following which it
          will be added to the schedule.
   j.     TMC enters:                               Only the aircraft which had a change in
          Changes concerning an aircraft's          priority status.
          "priority" status.
   k.     TMC enters:                               Only the aircraft that has had scheduling
          A command causing an aircraft that has    resumed.
          been suspended from scheduling to have
          its scheduling resumed.




                                            37                                TMA System Spec
                                                                                 FAA-E-2971
                                                                           17 December 2008
                                                                                  Final Rev N
     Event                                      TMA SHALL [0420] allocate
                                                runways for:
l.   TMC enters a command to reassign a         Only the aircraft that has had its CTAS
     single aircraft to another CTAS meter      meter fix reassigned.
     fix.
m.   TMC enters a command to reassign all       All aircraft that had a CTAS meter fix
     aircraft on a certain CTAS meter fix       re-assignment as a result of this
     after a certain aircraft to another CTAS   command.
     meter fix.
n.   (subrequirement deleted)
o.   TMA receives a flight plan amendment.      Only the aircraft whose flight plan is
                                                amended.
p.   TMA calculates an aircraft's ETA for       Only the aircraft that has had its first
     the first time                             ETA calculated.
q.   TMA is initialized.                        All aircraft.
r.   TMC enters:                                Only the specified aircraft.
     The "reallocate runway" command
     ALLOCATE_SINGLE (aircraft).
s.   TMC enters:                          All aircraft with a threshold STA or
     The "reallocate runway" command      ETA later or equal to the threshold ETA
     ALLOCATE_FROM (all aircraft after). of the specified aircraft.

t.   TMC enters:                                All aircraft going to the specified
     The "reallocate runway" command            aircraft’s airport.
     ALLOCATE_ALL (all aircraft).
u.   TMA receives an initial track for a        Only the aircraft that just received the
     proposed aircraft, unless the proposed     initial track.
     aircraft departure has been manually
     scheduled and frozen by the TMC.
v.   TMC enters:                                All aircraft assigned to this runway.
     Increase of a runway occupancy time.
w.   TMC enters:                                All aircraft assigned to any other
     Decrease of a runway occupancy time.       runway.
x.   Determination that an aircraft has         Only the aircraft that has reached the
     reached a site adaptable number of         site adaptable value from freeze
     miles from the freeze horizon when in      horizon.
     spatial based freeze mode
     OR
     a site adaptable number of minutes from
     the freeze horizon when in time based
     freeze mode or when in spatial based
     freeze mode and the aircraft isn't
     tracked.



                                         38                                TMA System Spec
                                                                                       FAA-E-2971
                                                                                17 December 2008
                                                                                        Final Rev N
              Event                                  TMA SHALL [0420] allocate
                                                     runways for:
   y.         TMC requests that runway allocation be Only aircraft that have either their
              performed in conjunction with the      Scheduling Meter Fix ETA time or their
              creation of a Single Gate Free Flow    Scheduling Meter Fix STA time
              constraint                             occurring at a time that is later than the
                                                     start of the SGFF constraint start time.
   z.         Periodic reallocation every site       All nonfrozen aircraft.
              adaptable number of minutes.

All of the above events except r, s & t are events that trigger automatic runway reallocation,
while r, s & t are commands that cause manual runway reallocation.

If the TMC entered a command to “reallocate runway” and selected airports to be rescheduled,
only flights for those airports SHALL [0422] be affected.

TMA SHALL [0424] examine all adapted runway selections for an aircraft and identify the one
which results in the lowest “total time to fly” for all of the aircraft within the system. TMA
SHALL [0425] further determine whether or not the savings in total time to fly exceeds the
specified adaptation threshold (Static Site Adaptable Scheduler Data). If this threshold is
exceeded, TMA SHALL [0426] then perform alternate runway allocation for that aircraft.

The practical effect, however, is to produce trial schedules with the aircraft reassigned to several
candidate runways which might be appropriate to the airport arrival configuration (and several
other factors).

Runway allocation is accomplished in two steps. The first is the identification of the reallocation
procedures for each aircraft from the site adaptation. The second is a search over all alternate
runways for each aircraft to find the one that provides the largest total delay savings.


3.2.1.3.3.1      Identification of the Reallocation Procedure from Site Adaptation

A reallocation procedure consists of a set of candidate runways to be tried for a given aircraft.
Each aircraft has its own reallocation procedure.

TMA SHALL [0430] identify a list of reallocation procedures from the site adaptation for each
aircraft to be reallocated based on:
    a. Anticipated airport arrival configuration.
   b. The aircraft's assigned CTAS meter fix.
   c. The aircraft's currently assigned runway.
   d. The type of reallocation (i.e., automatic or manual).




                                                 39                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N
3.2.1.3.3.2     Runway Search

Once the reallocation procedures have been identified, they are carried out. The runway search
consists of calculating the total time to fly for each of the candidate runway reallocations.

Based on the current runway assignment (and schedule) a total time to fly is calculated. Then a
new total time to fly is calculated based on a tentative schedule in which the aircraft is assigned
to the new runway (and removed from the current runway).

If the resulting savings in Total Time to Fly is larger than a site adaptable value (adaptable for
each proposed transition), the transition is accepted (Static Site Adaptable Scheduler Data).

The reallocation procedure (which is a list of runway transitions) is examined to completion.
The final runway resulting from this procedure becomes the newly -assigned runway.

TMA SHALL [0440] implement a site adaptable runway reallocation procedure for each aircraft
to be reallocated (Static Site Adaptable Scheduler Data), based on:
    a. An aircraft's currently assigned runway.
   b. The reduction in Total Time to Fly for all aircraft affected by the proposed runway
      change.
   c. Any future runway acceptance rate changes for the aircraft's currently assigned runway.

3.2.1.3.4     TRACON Speed & Altitude Parameter Specification

Based on an aircraft's assigned stream class, TMA SHALL [0450] retrieve from adaptation an
aircraft's TRACON entering parameters (Static Site Adaptable Scheduler Data), including:
    a. CTAS Meter fix crossing speed (Calibrated Airspeed (CAS)).
   b. CTAS Meter fix crossing altitude.
   c. TRACON altitude profile.
   d. (subrequirement deleted).

3.2.1.3.5     Situation Categorization

On every track data update cycle, TMA SHALL [0460] determine the "analysis category" of each
aircraft, based on the following conditions:
    a. Whether the aircraft is in track.
   b. Whether the aircraft is on the ground.
   c. Whether the aircraft is following its converted route.
   d. Whether the runway assignment is frozen.
   e. Whether the aircraft is a priority aircraft.
   f. The CTAS meter fix assigned.


                                                 40                               TMA System Spec
                                                                                FAA-E-2971
                                                                           17 December 2008
                                                                                 Final Rev N
   g. The anticipated airport configuration.
   h. The runway assignment.

3.2.1.3.6   Route Estimation

On every track data update cycle, TMA SHALL [0464] determine whether or not each aircraft is
off its converted route.

For the purposes of route generation, TMA SHALL [0469] consider a reference point to be one
of the following:
1. CTAS meter fix
2. Meter fix arc
3. Pseudo fix—represents the intersection of the converted route with the TRACON boundary
    for NOFIX aircraft.

TMA SHALL [0470] generate route estimates depending on aircraft status (In Track, On Ground,
and On Converted Route as shown Table 3.2.1.3.6-1.




                                               41                          TMA System Spec
                                                                                FAA-E-2971
                                                                           17 December 2008
                                                                                 Final Rev N

                   Table 3.2.1.3.6-1.   Route Estimate Generation
   Aircraft Status
   In     On     On
   Trk Gnd Conv               Route Estimate
   ?      ?      Route
                 ?
a. No     No     Don't        Places the aircraft at the coordination fix at the coordination
                 Care         time with an initial heading toward the first Converted
                              waypoint, follows the Converted route to the reference point,
                              and then follows the nominal TRACON route to the runway.
b   No   Yes    Yes           Places the aircraft at the departure airport fix at the
.                             coordination time with an initial heading along the adapted
                              departure heading (Static Site Adaptable Scheduler Data).
                              This initial heading is followed for an adapted distance
                              (Static Site Adaptable Scheduler Data) and is followed by an
                              immediate turn toward the first Converted waypoint. The
                              route follows the Converted route to the reference point, and
                              then follows the nominal TRACON route to the runway.
c. Yes   No     Yes           Places the aircraft at the track location at the track time, and
                              using the heading reported by the tracker as the initial
                              heading:

                              1. If the aircraft is within a site-adaptable distance from its
                                 reference point, follows an immediate turn heading
                                 toward the reference point, and then follows the nominal
                                 TRACON route to the runway (Static Site Adaptable
                                 Scheduler Data).
                              2. If the aircraft is beyond the site-adaptable distance from
                                 its reference point, follows an immediate turn heading
                                 toward the next converted waypoint, follows the
                                 converted route to the reference point, and then follows
                                 the nominal TRACON route to the runway (Static Site
                                 Adaptable Scheduler Data).




                                           42                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N
    Aircraft Status
d   Yes No        No                Places the aircraft at the track location at the track time, and
.                                   using the heading reported by the tracker as the initial
                                    heading:
                                    1. If the aircraft is within a site adaptable distance (Static
                                        Site Adaptable Scheduler Data) of its assigned reference
                                        point, follows an immediate turn heading toward the
                                        reference point, and then follows the nominal TRACON
                                        route to the runway.
                                    2. If the aircraft is beyond the site adaptable distance (Static
                                        Site Adaptable Scheduler Data) from its reference point,
                                        follows a recovery route (see Requirement 0475) from
                                        the current position (and heading) to one of the remaining
                                        waypoints in the Converted route, follows the remainder
                                        of the Converted route to the reference point, and then
                                        follows the nominal TRACON route to the runway.

For every track update, it is determined whether each aircraft is off its converted route (i.e., its
closest distance to the converted route exceeds a site-adaptable distance, e.g., 5 nmi). For each
aircraft off its converted route, the "route recovery procedure" is carried out as follows.

TMA SHALL [0475] apply the following route recovery procedure for each aircraft which is off
its converted route:
     a. Check a waypoint in the converted route that is closest to and ahead of the aircraft’s
        current position, and select the waypoint as the recovery waypoint if the angle of intercept
        is less than or equal to a site-adaptable number of degrees (Static Site Adaptable
        Scheduler Data).
    b. If the test in (a) fails, continue checking waypoints in the converted route until one is
       found which passes the test.
    c. If the waypoint being tested is the reference point, it is selected as the recovery waypoint.
    d. If the waypoint to be tested is the Meter Fix Arc, it is selected as the recovery waypoint.
       If no meter fix arc is adapted, and the waypoint to be tested is the CTAS Meter Fix, it is
       selected as the recovery waypoint.
    e. The first segment of the recovered route is the direct segment from the current position to
       the recovery waypoint, after which the remainder of the converted route is used.


Requirements 0480 and 0490 have been deleted.

3.2.1.4 ETA Generation


TMA calculates the Time To Fly (TTF) from the aircraft's current position or coordination fix to
Outer-Four Arc, Outer-Three Arc, Outer-Outer Arc, Outer Meter Arc, CTAS Meter Fix/Meter


                                                  43                              TMA System Spec
                                                                                    FAA-E-2971
                                                                              17 December 2008
                                                                                     Final Rev N
Fix Arc, Scheduling Meter Fix, Final Approach Fix and Runway Threshold. These TTFs are
added to the current time or coordination time to produce the ETAs at these locations.

The first step in calculating the TTF is to convert a list of waypoints into a ground track that
includes turns which are capable of being flown according to the aircraft model. The second step
is to calculate the vertical speed profile along this ground track in accordance with standard
aircraft arrival procedures.

ETAs are recalculated for each aircraft whenever any information about aircraft status is received
from the HCS or ETMS systems or whenever new weather information is received.

TMA SHALL [0500] calculate ETAs based upon:
  a. Aircraft position (HCS, ETMS, ARTS/STARS reported position and altitude).
   b. Aircraft speed reported by HCS, ETMS, ARTS/STARS.
   c. Aircraft heading reported by HCS and ARTS/STARS.
   d. Aircraft models (Engine Thrust and Airframe Drag models).
   e. Horizontal route.
   f. Weather data (wind speed, wind direction, temperature, and pressure).
   g. Ascent and Descent profiles.
   h. Prescribed altitude regime s (current altitude, flight plan altitude, CTAS meter fix
      crossing altitude, and TRACON altitude profile).
   i. Delay adapted for fixes in a coded route in the flight plan.
   j. Delay specified for fixes in the flight plan (takes precedence over adapted coded route
      delay for the same fix).

TMA SHALL [0510] calculate a new ETA for each aircraft for the following:
  a. Every new radar update.
   b. Flight plan route amendment.
   c. Change of the anticipated airport configuration.
   d. CTAS meter fix reassignment.
   e   Runway reassignment.
   f. Change in coordination time.
   g. For tracked aircraft only, updated weather data.
   h. Proposed aircraft is manually scheduled or rescheduled. (New ETA calculated only for
      the untracked aircraft which was manually scheduled or rescheduled, not all aircraft.)
   i. Flight plan message with a departure time (“d-time”) received from Host. (New ETA
      calculated only for the untracked aircraft which departed, not all aircraft.)
   j. Change of the departure airport configuration. (New ETA calculated only for proposed
      aircraft departing from the airport whose configuration changed, not all aircraft.)


                                               44                              TMA System Spec
                                                                                   FAA-E-2971
                                                                            17 December 2008
                                                                                    Final Rev N
   k. Change in departure time due to change in use of EDCT at the arrival airport
      (unscheduled Internal Departures only)
   l. Change in departure time for an unscheduled internal departure that has not departed at its
      estimated time of departure.

If enabled, TMA SHALL [0512] set an aircraft’s departure time to the current time for an
unscheduled internal departure that has not departed an adapted time after its estimated time of
departure. The default state of the departure time reset function is specified in adaptation and can
be enabled/disabled thru user input. TMA SHALL [0514] continue to set the departure time to
the current time until any of the following:
    a. The flight has departed
   b. The flight is scheduled
   c. The controller disables the departure time resets for the flight
   d. The controller disables the departure time reset function
   e. A specified time has passed

If the departure time reset is reenabled for the function or for a flight, adjustments SHALL
[0516] be resumed.

Requirements 0520 and 0530 have been deleted.

3.2.1.4.1   Determination of Vertices

This section describes the determination of vertices, which are selected waypoints used for Time
To Fly calculations. Vertices most commonly used in this context are the Outer Meter Arc,
CTAS Meter Fix/Meter Fix Arc, Scheduling Meter Fix, Final Approach Fix and Runway
Threshold.

TMA SHALL [0540] obtain the TTF by modeling the three-dimensional flight of the aircraft as a
function of time (a so-called 4D trajectory) based on the following inputs:
   a. Aircraft track position.
   b. Routing information.
   c. Altitude profile.
   d. Aircraft type.
   e. Aircraft ground speed.
   f. Aircraft characteristics.
   g. Weather data.

TMA SHALL [0550] be capable of calculating an aircraft’s TTF from the following vertices:
  a. The aircraft's most recently reported position.


                                                45                              TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
   b. The aircraft's coordination fix at the en-route center boundary.
   c. An adapted airport within the en-route center (including the TRACON).

TMA SHALL [0560] be capable of calculating an aircraft’s ETA to the following adapted
vertices (Static Site Adaptable Scheduler Data):
    a. Outer Meter arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS meter fix or meter fix arc.
   b1. Scheduling meter fix.
   c. Final approach fix.
   d. Runway threshold.

For aircraft that are airborne and tracked in the Center airspace, TMA SHALL [0571] calculate
an aircraft’s ETA by summing the aircraft’s track time and the TTF from the aircraft’s current
position to the:
    a. Outer Meter arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS meter fix or meter fix arc.
   b1. Scheduling meter fix.
   c. Final approach fix.
   d. Runway threshold.

For aircraft that are airborne in an adjacent center, TMA SHALL [0572] calculate an aircraft’s
ETA by summing the aircraft’s projected coordination time and the TTF from the aircraft’s
coordination fix to the:
   a. Outer Meter arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS meter fix or meter fix arc.
   b1. Scheduling meter fix.
   c. Final approach fix.
   d. Runway threshold.

When TMA receives a proposed flight plan from the HCS, TMA SHALL [0573] calculate an
aircraft’s ETA by summing the aircraft’s projected departure time, and the TTF from the
aircraft's departure fix to the:
    a. Outer Meter arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS meter fix or meter fix arc.
   b1. Scheduling meter fix.
   c. Final approach fix.
   d. Runway threshold.
Host sends proposed flight plan some adaptable time (for example 30 minutes) prior to departure.



                                               46                             TMA System Spec
                                                                                    FAA-E-2971
                                                                              17 December 2008
                                                                                     Final Rev N
Accuracy of the calculated ETAs is required to establish the proper sequence at an early time and
to properly predict the demand on the airport.

TMA SHALL [0580] compute the track-based ETA for all aircraft type trajectories to within
Root Mean Square (RMS) accuracy of +/- 60 seconds when the aircraft time to the CTAS meter
fix or meter fix arc is 19 minutes. The error rate SHALL [0581] decrease linearly as:

                error = (60sec/19min) X (time to CTAS meter fix or meter fix arc)

where the upper bound for time to CTAS meter fix or meter fix arc is 19 minutes.


TMA SHALL [0585] calculate and display the Original ETA (OETA) calculated as follows:
  a. If no track updates have been received, the OETA is the most recently calculated ETA.
   b. If between one and five track updates have been received, the OETA is the average ETA
      resulting from all track updates.
   c. If more than five track updates have been received, the OETA is the average of the ETAs
      resulting from the first five track updates.

TMA's prediction of the TTF is required to satisfy the following performance requirement:

The percentage of error, in absolute value, associated with the final track OETA for a statistical
sample of 500 aircraft with "unimpeded" flight to the CTAS meter fix/meter fix arc SHALL
[0590] have a sample mean of not more than 6% and a 99th percentile of not more than 10%,
respectively, where percentage error is defined as:

             | OETA minus Actual CTAS meter fix/meter fix arc crossing time | * 100
       ------------------------------------------------------------------------------------------------
                          | Actual CTAS meter fix/meter fix arc crossing time
                         minus Average time when the OETA was calculated |

In this context, the final track OETA refers to the average of the first five ETAs based on track
updates. The "Average time of OETA calculation" is the average "track time" of the first five
track updates. Unimpeded flight is one which was not affected by the presence of other aircraft
while traversing the planned path to the CTAS meter fix or meter fix arc.

Requirement 0570 has been deleted.

3.2.1.4.2       Determination of Horizontal Ground Track

The horizontal ground track is determined so that the horizontal motion can be decoupled from
the vertical solution. The first step in the determination of the horizontal ground track is to
complete the converted route by inserting turns at each waypoint. This, in turn, requires the
computation of the approximate ground speed at each waypoint. These velocities are then used


                                                       47                                    TMA System Spec
                                                                                        FAA-E-2971
                                                                                  17 December 2008
                                                                                          Final Rev N
to calculate the turn radii. Finally, the straight segments of flight are connected with the constant
radius turns to produce the refined ground track.

TMA SHALL [0600] use constant radius horizontal turns, taking into account aircraft type,
speed, permissible bank angle, and winds aloft.

3.2.1.4.3     Determination of the Vertical Profile Along the Ground Track

Once the ground track has been refined, the four-dimensional trajectory is produced by solving
the coupled differential equations for position, speed, and altitude.

The differential equations are solved in trajectory segments that define the operating constraints
of the aircraft in each stage of flight. Each trajectory segment transitions to the next when its
predefined capture condition is reached. A capture condition may be a Calibrated Air Speed, a
Mach number, an altitude, or a certain path distance. The prediction of flight in each segment is
made by the solution of the appropriate differential equations using a numerical integration
method.

3.2.1.4.3.1     Vertical Profile in Center Airspace

TMA SHALL [0610] model the flight of aircraft using realistic aircraft models and the following
control variables, which mimic piloting procedures:
   a. Thrust (either idle or maximum).
   b. Speed in the form of CAS or Mach.
   c. Vertical rate (climb rate or descent rate expressed either in feet per minute or as a
      prescribed inertial flight path angle.

TMA SHALL [0620] model flight over trajectory segments by solving equations of motions
where constant values are chosen for any two of the following control variables:
   a. Thrust (either idle or maximum).
   b. Speed in the form of CAS or Mach.
   c. Vertical rate (climb rate or descent rate expressed either in feet per minute or as a
      prescribed inertial flight path angle).

During the computation of a descent, the TS computes a constant Mach segment, using the
aircraft’s descent Mach, in order to capture the aircraft’s descent CAS. The Mach/CAS
transition altitude is the altitude at which these two speeds cross on a true airspeed vs. altitude
graph.

TMA SHALL [0630] model the flight of jets at a constant speed at or above the Mach/CAS
transition altitude, whether flying level or descending, using a constant Mach number.

Below the Mach/CAS transition altitude, TMA SHALL [0640] use a constant CAS value.


                                                  48                              TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

TMA SHALL [0650] model en route descents for jets using idle-thrust descents in the following
four phases:
    a. Mach acceleration.
   b. Constant Mach.
   c. Constant CAS.
   d. Level deceleration.

The permissible values for CAS or Mach SHALL [0660] be defined by the aircraft performance
model and ATC procedures.

TMA SHALL [0670] be capable of modeling descents using maximum (fast) and minimum
(slow) speed descent profiles when called upon to do so for the purposes of scheduling arrivals
earlier than the nominal ETA.

Requirement 0680 has been deleted.

TMA SHALL [0690] be capable of modeling aircraft descents using company preferred descent
speeds, where known.

TMA SHALL [0692] define adapted angle of descent data (optional) in site adaptation data
using:
    a. Flight path angle (descent angle) in degrees
    b. Calibrated airspeed (CAS) for the descent portion of the adapted angle of descent
       (optional)

TMA SHALL [0694] identify aircraft to be modeled with adapted angle descents by categories in
site adaptation data.

For aircraft categories identified in adaptation to use adapted angle of descent, TMA SHALL
[0696] replace the use of a model based flight path angle in descent calculations with an adapted
angle of descent.

TMA SHALL [0699] suppress changes to vertical trajectory resulting from a hard altitude
amendment within an adapted distance from a meter fix and within an adapted altitude range,
when specified in site adaptable data.



3.2.1.4.3.2    Vertical Profile in TRACON Airspace

TMA SHALL [0695] model flight within the TRACON following air traffic procedures from the
adaptation (Static Site Adaptable Scheduler Data).



                                               49                              TMA System Spec
                                                                            FAA-E-2971
                                                                     17 December 2008
                                                                             Final Rev N
TMA SHALL [0697] model flight within the TRACON by using segments of the following
types.
    a. Constant CAS at constant altitude.
   b. Constant CAS descents with constant glide slopes.
   c. Idle thrust deceleration at constant altitude.

3.2.1.4.3.3     Stepped Descent

TMA SHALL [0702] define stepped descent data in site adaptation data using:
  a. distance from meter fix to beginning of the level portion of the stepped descent.
   b. altitude of the level portion of the stepped descent
   c. calibrated airspeed (CAS) for the level portion of the stepped descent (optional)

TMA SHALL [0704] identify aircraft to be modeled with stepped descents by categories in site
adaptation data.

Under conditions specified in adaptation, TMA SHALL [0706] replace the computation of a
standard descent with the stepped descent to accurately model the aircraft’s altitude profile. The
TS computes the constant Mach and constant descent CAS segments in the same manner as the
standard descent profile. TS models the stepped descent using the adapted altitude, distance, and
optional CAS. If no CAS is adapted, the TS continues to use the default descent CAS for the
level portion of the stepped descent and the subsequent descent to the meter fix.


3.2.1.4.4     Variable Speed Crossing Restriction (VSCR)

Requirements 0700 and 0710 have been deleted.

3.2.1.4.5     ETA Smoothing

ETA estimation must be temporally stable so that arrival sequences are not switched
unnecessarily. This requires the result of the ETA process to be temporally smoothed by
appropriate algorithms.

TMA SHALL [0720] limit the fluctuation of an aircraft’s ETA due to estimation errors by:
     a) Using the most recent flight plan ETA if no track updates have occurred.
       b) Averaging the last five ETAs based on track updated provided they are available and
          no change has occurred in the route in the last five track updates.
          NOTE: This is known as a moving window average.
       c) Averaging all ETAs following a route change if a change has occurred in the last five
          track updates.



                                                50                             TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N
Requirement 0730 has been deleted.

3.2.1.5 Scheduling

The Scheduling function determines the time in which aircraft will arrive over a scheduling
meter fix and over a runway threshold (or FAF) based on aircraft ETAs, operator selected
constraints, or operator entered sequencing constraints. Scheduling uses the super stream class
sequence and the ETAs generated by the ETA generation function to generate an STA for each
aircraft by applying site adapted or operator selected scheduling constraints and required
minimum separation constraints (Static Site Adaptable Scheduler Data/Dynamic Site Adaptable
Scheduler Data -- the operator selected component defines the dynamic items).

The scheduler is capable of providing scheduling preference to aircraft in user designated stream
classes that have ETAs that fall inside user specified intervals. This functionality is called Single
Gate Free Flow or SGFF.

When adapted, a Meter Fix Arc is used instead of the Scheduling Meter Fix for ETA generation,
constraint application, and scheduling. Times are referenced to the arc, and sequences and
schedules are established based on arc times.

When adapted, offset scheduling is used to provide deconflicted arrival scheduling at points that
are inside the TRACON. Under offset scheduling, scheduling constraints are applied, and ETAs
are used for scheduling, at scheduling meter fix locations that are not coincident with the CTAS
meter fix locations used for Host metering display and TRACON nominal interior route
development.

Sequencing and scheduling occurs at the scheduling meter fix or meter fix arc only for those
aircraft in a super stream that have the scheduling meter fix in their nominal interior TRACON
route or are assigned a meter fix arc. All other aircraft are scheduled to the runway only, and are
not considered for scheduling at the scheduling meter fix or meter fix arc.

For every super stream of aircraft entering the TRACON, the initial order or sequence is First
Come First Served (FCFS) based on the ETA at the Scheduling Meter Fix or meter fix arc. This
initial sequence can be modified to take into account any user-specified constraints.

Sequencing and scheduling occurs periodically, e.g., every 6 seconds, or when triggered by
specific events, such as an aircraft being added or subtracted from the list of aircraft for a
particular super stream for which the scheduling operation is being considered.

Requirement 0832 has been moved to Section 3.2.1.5.7

TMA SHALL [0830] generate a sequence of aircraft to the Scheduling Meter Fix or Meter Fix
Arc for each super stream.




                                                 51                              TMA System Spec
                                                                                  FAA-E-2971
                                                                            17 December 2008
                                                                                   Final Rev N
TMA SHALL [0840] sequence aircraft at the Scheduling Meter Fix or Meter Fix Arc in each
super stream on a First-Come-First-Served (FCFS) order, in accordance with each aircraft's:
   a. ETA at the Scheduling Meter Fix or Meter Fix Arc
   b. (subrequirement deleted)

TMA SHALL [0850] modify its sequences at the Scheduling Meter Fix or Meter Fix Arc to
accommodate any sequence constraints entered manually by the TMC.

TMA SHALL [0855] only sequence and schedule aircraft at the scheduling meter fix or meter fix
arc if the aircraft has the scheduling meter fix in its nominal interior TRACON route or is
assigned to a meter fix arc.

Requirement 0860 has been deleted.

After the sequence is established, STAs will be generated by the time based metering algorithms.

Requirement 0865 has been deleted.

The TMA system SHALL [0867] determine the closest available STA for an aircraft based on
the TMC input of
    1. Desired STA to the scheduling meter fix or meter fix arc, or Desired STA to the runway,
       or aircraft ready time
   2. Departure runway (optional)
   3. Arrival runway (optional)

The closest STA SHALL [0868] be computed such that the aircraft will not have to depart earlier
than its ready time, and without rescheduling any manually-assigned aircraft or aircraft whose
STAs have been frozen.

TMA SHALL [0780] display a stabilized STA which is calculated according to the following
rules:
    a. The initial value of the stabilized STA equals the first calculated STA.
   b. Subsequently, the stabilized STA is updated to be equal to the newly calculated STA only
      if the difference exceeds 12 seconds.

For Host requested SWAP and RESEQUENCE commands, TMA SHALL [0782] disregard the
12 seconds DP restriction for displaying a stabilized STA.

For a TMC input of a swap request, TMA SHALL [0783] disregard the 12 seconds DP restriction
for displaying a stabilized STA.

The following computations are used in acceptance rate processing:


                                               52                            TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
The acceptance rate interval divisor is computed to be:
         acceptance rate interval divisor =
                 60 min / acceptance rate interval

The acceptance rate per acceptance rate interval is computed to be:
         rate per acceptance rate interval =
            acceptance rate per hour / acceptance rate interval divisor

The rate per acceptance rate interval is the number of aircraft that the Dynamic Planner (DP)
should allow every acceptance rate interval number of minutes. When the acceptance rate per
hour is not evenly divisible by the acceptance rate interval divisor, TMA SHALL [0785]
distribute the remainder of aircraft across the hour. {Requirement 0785 is deferred}.

When adapted to do so, TMA SHALL [0787] provide a configuration change status indicator to
the user and determine reallocation according to the following rules:
    a. A site adapted value sets the maximum number of seconds that DP will wait for ETAs
        received for schedulable objects associated with the configuration change before starting
        reallocation.
   b. A site adapted value sets the maximum number of seconds that DP will wait between
      each individual ETA received for schedulable objects associated with the configuration
      change before starting reallocation.
   c. The TMC may force an earlier reallocation via the TGUI interface.

For Non-Internal departures, when an aircraft is manually scheduled to a meter reference point,
TMA SHALL [0789] apply delay absorption values when computing the STAs at the other
reference points.


3.2.1.5.1   Scheduling Using Time Based Metering

The Scheduler begins by scheduling each super stream at the scheduling meter fix/meter fix arc,
and then checks for conflicts defined as violations of separation constraints between consecutive
aircraft. The scheduler then attempts to build runway schedules. Several iterations may occur in
an attempt to reconcile constraints applicable at runways and scheduling meter fixes/meter fix
arcs, leading to a final schedule at the scheduling meter fix/meter fix arc and at the runway. This
schedule should be conflict free to within specified separation requirements at the runway and at
the scheduling meter fix/meter fix arc. Finally, the schedules at the CTAS meter fix (if adapted
at a different location from the scheduling meter fix) and the outer meter arc are calculated based
on the schedule at the scheduling meter fix or meter fix arc.

TMA SHALL [0740] schedule:
  a. Tracked flights (flight plans and radar tracks).
   b. Untracked flights (flight plans only).



                                                53                              TMA System Spec
                                                                                 FAA-E-2971
                                                                            17 December 2008
                                                                                  Final Rev N

TMA SHALL [0745] only schedule proposed aircraft by manual scheduling.
Requirement 0747 has been deleted.

TMA SHALL [0746] optionally exempt manually scheduled aircraft from automatic reschedules
and broadcasts.

TMA SHALL [0744] not exempt manually scheduled aircraft from automatic reschedules and
broadcasts on a configuration change if
    a. the manually scheduled aircraft's currently assigned runway is not valid in the new
       configuration, or
    b. the manually scheduled aircraft's currently assigned CTAS meter fix or scheduling meter
       fix or meter fix arc is not the adapted CTAS meter fix or scheduling meter fix or meter
       fix arc in the new configuration.

TMA SHALL [0748] have the capability of unscheduling a manually scheduled internal
departure due to a manual action by the TMC. No frozen schedules SHALL [0749] be affected
by such unscheduling.

Requirements 0750 and 0170 have been combined into one requirement. See Requirement 1552
in Section 3.2.1.5.7.

Requirements 0751 and 0752 have been deleted.

TMA SHALL [0760] generate an STA for each aircraft to its assigned:
  a. Outer Meter Arc, Outer-Outer Arc, Outer-Three Arc, Outer-Four Arc, if adapted.
   b. CTAS Meter Fix, if adapted, or Meter Fix Arc.
   b1. Scheduling meter fix.
   c. Final Approach Fix.
   d. Runway Threshold.

TMA SHALL [0770] generate an STA based on the following constraints:
  a. Feeder gate acceptance rate.
   b. (subrequirement deleted)
   c. Stream class Miles-in-Trail separation.
   d. Scheduling Meter Fix or Meter Fix Arc Acceptance Rate.
   e. Airport Acceptance Rate.
   f. Runway threshold (or FAF) Acceptance Rate.
   g. Aircraft ETAs.
   h. (subrequirement deleted)
   i. Generated sequence.


                                                54                          TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
   j. Delay information fed back from the TRACON and delay allocation rules between
      TRACON and Center including a separate delay apportionment between the CTAS meter
      fix and scheduling meter fix when they are non-coincident; if adapted.
   k. Separation criteria from FAA Order 7110.65, Air Traffic Controllers’ Handbook (wake
      vortex constraints).
   l. (subrequirement deleted).
   m. TMC-entered STA, blocked slots, blocked intervals.
   n. Runway occupancy time.
   o. (subrequirement deleted).
   p. Runway separation buffer.
   q. Single Gate Free Flow intervals.

TMA SHALL [0790] generate an STA for a priority aircraft to be equal to its ETA, or the first
available STA if the aircraft is in conflict with another priority aircraft or blocked time.

Freeze processing in TMA provides the TMC with stable STAs when aircraft reach an adaptable
distance or time from the CTAS meter fix, designated as the freeze horizon (Dynamic Site
Adaptable Scheduler Data). If a meter fix arc has been assigned, then the freeze horizon is
referenced to the arc, otherwise it is referenced to the CTAS meter fix. NOFIX flights that are
not being scheduled to a meter fix arc use a separate NOFIX freeze horizon value. If both miles
and minutes are adapted, site adaptable logic will be used to determine which is applicable for an
aircraft. The values of the freeze horizons may be changed by the TMC from the TMC GUI. In
addition, certain TMC commands will freeze the STA of an aircraft.

TMA SHALL [0775] be capable of enabling/disabling freeze processing via the site adapted
freeze horizon toggle value or in response to a TMC entered command. TMA SHALL [0777]
default freeze processing to enabled. If multiple arrival airports exist, TMA SHALL [0779] be
capable of enabling/disabling freeze processing for each airport via site adaptable scheduler data
or in response to a TMC entered command.

TMA SHALL [0791] be capable of changing the site adapted freeze horizon values (0-60
minutes or 0-200 nautical miles) in response to a TMC entered command (Dynamic Site
Adaptable Scheduler Data).

TMA SHALL [0792] determine the applicability of miles or minutes to the freeze horizon based
on site adaptable logic (Dynamic Site Adaptable Scheduler Data).

TMA SHALL [0793] apply freeze horizon determination to the assigned meter fix arc, if adapted
(Static Site Adaptable Scheduler Data).

TMA SHALL [0800] freeze the STA of aircraft on any of the following events (unless STA
freeze suppression SHALL [0804] applies):



                                                55                              TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
   a. The aircraft’s undelayed TTF to the CTAS meter fix or meter fix arc is within the freeze
      horizon number of minutes.
   b. The distance from the aircraft’s present position to the CTAS meter fix or meter fix arc is
      within the freeze horizon number of miles.
   c. If the aircraft is a NOFIX aircraft not assigned to a meter fix arc and its nominal interior
      TRACON route does not contain its scheduling meter fix, the aircraft’s TTF or distance
      to the runway is within a site adaptable NOFIX freeze horizon minutes or miles (Dynamic
      Site Adaptable Scheduler Data).
   c1. If the aircraft is a NOFIX aircraft not assigned to a meter fix arc and its nominal interior
       TRACON route does contain its scheduling meter fix, and the aircraft’s TTF or distance
       to the intersection point between the converted route and the TRACON boundary is
       within the fix freeze horizon minutes or miles of the assigned nearest CTAS meter fix.
   d. In response to a TMC-entered command to freeze the STA.
   e. In response to a TMC-entered command to manually assign an STA.
   f. In response to a TMC-entered command to change the freeze horizon value such that the
      aircraft is now within the freeze horizon.
   g. The aircraft crosses the TRACON boundary.
   h. Manual action by the TMC to “Accept and Freeze” a manually scheduled internal
      departure.
   i. In response to a TMC-entered command to swap the STAs of aircraft.
   j. The aircraft’s STA is earlier than a frozen aircraft in the same stream class, provided that
      the aircraft was not manually frozen.

TMA SHALL [0801] freeze a manually scheduled proposed departure when the ETA enters the
time freeze horizon even if it was scheduled using the Accept button of the Schedule a Departure
dialog box (unless STA freeze suppression SHALL [0804] applies).

If adapted, when a proposed departure is manually scheduled using the Accept button of the
Schedule a Departure dialog box and the ETA falls inside the time freeze horizon, TMA SHALL
[0802] freeze the entry as if the Accept and Freeze button had been used (unless STA freeze
suppression SHALL [0804] applies). When a proposed departure is manually scheduled, the user
SHALL [0806] be able to specify if that scheduling of the flight should impact other flight’s
schedules or be scheduled into the first empty slot. If specified by adaptation, a proposed
nonfrozen internal departure that was scheduled using the Accept button SHALL [0803] compete
for STA times with other nonfrozen aircraft each scheduling update.

If specified by adaptation, TMA SHALL [0808] reschedule a manually-scheduled frozen internal
departure aircraft upon receiving the first track-based ETA:
    a. If the rescheduling results in an earlier runway or meter fix/meter fix arc STA, the earlier
        runway and meter fix/meter fix arc STAs will be used and the current AMDT values
        reapplied to any assigned outer arc STAs



                                                56                               TMA System Spec
                                                                                     FAA-E-2971
                                                                               17 December 2008
                                                                                       Final Rev N
   b. If the rescheduling does not result in an earlier runway or meter fix/meter fix arc STA and
      the meter fix/meter fix arc delay is
           1. positive or zero, retain the original runway and meter fix/meter fix arc STAs and
               reapply the current AMDT values to any assigned outer arc STAs
           2. negative, retain all the original STAs
   c. Retain or remove the flight’s manually scheduled status as specified in adaptation
   d. Only send metering information to controllers after the rescheduling is performed

An asymmetric freeze horizon enables stream classes within a super stream class to freeze
independently, allowing their individual freeze horizons to apply. TMA SHALL [0807] provide
the capability to optionally freeze aircraft whose STAs are earlier than a frozen aircraft in the
same super stream, provided that the aircraft was not manually frozen.

TMA SHALL [0804] be capable of suppressing the STA freeze functionality specified in
SHALL [0800] sub-items a, b, c, c1, f, j, SHALL[0801], and SHALL[0802], and SHALL [0807]
for flights departing from airports that have been adapted as STA freeze suppression airports for
the flight’s arrival airport (Static Site Adaptable Scheduler Data).

TMA SHALL [0805] apply STA freeze suppression on qualifying flights until they have either
departed or become tracked, based on a site adaptable parameter that is specified for each STA
freeze suppression airport (Static Site Adaptable Scheduler Data).

As a result of the following TMC commands, TMA SHALL [0810] recalculate STAs for frozen
aircraft that have not been manually scheduled:
    a. Configuration change
   b. Acceptance rate change
   c. Miles-in-trail or super-stream change
   d. Sequence constraints change
   e. THD separation, THD separation buffer, or THD occupancy time change
   f. Reschedule this aircraft, all aircraft, all aircraft except manually scheduled, this aircraft
      and after, or this aircraft and after except manually scheduled
   g. Reassign runway for this aircraft, all aircraft, or this aircraft and after
   h. Add/delete aircraft as priority
   i. Freeze horizon change
   j. Single gate free flow change
   k. Add/delete MFX or runway blocked interval.


If the TMC input for THD separation or THD separation buffer would violate the FAA
separation requirements as defined in FAA Order 7110.65, Air Traffic Controllers’ Handbook,
then the entry SHALL [0811] not be applied to TMA and an indicator SHALL [0813] be
provided to the TMC.


                                                 57                                 TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N

TMA SHALL [0812] recalculate STAs for frozen aircraft as a result of a sector controller route
amendment that changes the CTAS meter fix.

As a result of the following TMC commands, TMA SHALL [0814] recalculate STAs for frozen
aircraft that have been manually scheduled:
         a. Configuration change subject to SHALLs [0746] and [0744]
         b. THD separation, THD separation buffer, THD occupancy time change, or THD
             acceptance rate change
         c. Reschedule this aircraft, all aircraft, or this aircraft and after
         d. Reassign runway for this aircraft, all aircraft, or this aircraft and after
         e. Add/delete MFX or runway blocked interval

TMA SHALL [0820] be capable of accepting dynamic user input that specifies the stream
class(es) and time interval(s) that will be used in selecting aircraft to receive scheduling
preference in runway order of consideration. This form of schedule preferencing is called Single
Gate Free Flow.

TMA SHALL [0822] be capable of rescheduling aircraft arriving at specified airports without
changing the STAs for frozen aircraft at other airports.

When scheduling a departure, TMA SHALL [0824] calculate a suggested departure time based
on an airborne delay increment if TMA has determined that the flight requires some amount of
delay. This airborne delay increment specifies the maximum amount of delay that can be taken
in the air on route to the scheduling point.

If TMA has determined that no delay is required when scheduling a departure, TMA SHALL
[0826] calculate the suggested departure time without regard to the airborne delay increment.

TMA SHALL [0828] assign this airborne delay increment to an aircraft based on Departure
Airport using site-adaptable parameter(s) (Dynamic Site Adaptable Scheduler Data).

Requirement 0825 has been deleted.

3.2.1.5.1.1    Separation at the Scheduling Meter Fix/Meter Fix Arc

Schedules for every super stream class are made at all Scheduling Meter Fixes/Meter Fix Arcs.
Derived schedules are also made for outer arcs, if adapted and CTAS meter fixes. Schedules are
also made for runway FAF's or thresholds. The latter are made simultaneously with Scheduling
Meter Fix/Meter Fix Arc schedules since they have mutual dependencies.

Once the sequence at the Scheduling Meter Fix/Meter Fix Arc has been determined, the
scheduler generates a schedule at the Scheduling Meter Fix/Meter Fix Arc consisting of an STA
for each aircraft in the sequence, using the following rules:


                                               58                             TMA System Spec
                                                                                      FAA-E-2971
                                                                                17 December 2008
                                                                                       Final Rev N
   •   No aircraft is scheduled to arrive earlier than its ETA. Many aircraft are scheduled at a
       time later than their ETA to satisfy separation requirements between aircraft in the
       sequence.
   •   The separation imposed between specific aircraft depends on a variety of constraints at
       the Scheduling Meter Fix/Meter Fix Arc.
   •   Separation constraints at the runways are fed back to the appropriate Scheduling Meter
       Fixes/Meter Fix Arcs and may further increase separations.

TMA SHALL [0870] generate a schedule for each super stream class (at the Outer Meter Arc, if
adapted, the CTAS Meter Fix, the Scheduling Meter Fix or Meter Fix Arc, if adapted, the Final
Approach Fix, and the Runway threshold) and a set of derived schedules periodically, nominally
every 6 seconds, or when triggered by any of a specific set of events, as follows:
   a. Anything that causes immediate runway allocation.
   b. Addition or deletion of a gate blocked interval.
   c. Addition or deletion of a scheduling meter fix blocked interval.
   d. Change in the Airport Acceptance Rate.
   e. Change in runway occupancy time.
   f. Change in any value in the runway wake vortex separation matrix.
   g. Change in the gate acceptance rate.
   h. Change in the scheduling meter fix or meter fix arc acceptance rate.
   i. Change in super stream class definition.
   j. Change in MiT restriction.
   k. Change in TRACON acceptance rate.
   l. Addition of a scheduling meter fix sequence constraint.
   m. Define slot operation initiated by the TMC.
   n. Manual STA setting of any aircraft.
   o. User requests a reschedule.
   p. Rescheduling caused by pending scheduling events of the following types:
          1. (subrequirement deleted). Flight plan amendment changes a runway.
          2. Flight plan amendment changes coordination fix.
          3. Aircraft ETA is hovered (i.e., an aircraft fails to meet its coordination time
              and Host continues to increment at three minute intervals).
       where rescheduling is triggered whenever either:
          1. The type of a new pending event is different from any in the pending list.
          2. The new pending event if added to the pending list causes the number of pending
             events to exceed the maximum number of pending events.
   q. Flight plan amendment changes a runway.


                                                 59                            TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
   r. Creation of or changes to Single Gate Free Flow periods.
          1. Aircraft to be rescheduled can be specified by the user to be those with meter fix
             ETA after the start of the SGFF so as to not affect flights earlier than the SGFF, or
             all aircraft in order to include aircraft whose delays might cause them to affect the
             scheduling of the SGFF aircraft.
   s. (subrequirement deleted)

Requirements 0880, 0885, and 0890 have been deleted.

A Mirror Meter Fix is an alternate CTAS Meter Fix through which a flight route change from the
original CTAS Meter Fix will not cause a reschedule of the flight’s STA to the Mirror Meter Fix
or to the runway.

TMA SHALL [0873] allow adapted CTAS Meter Fixes to be defined as Miror Meter Fixes for
an adapted CTAS Meter Fix.

TMA SHALL [0875] allow the TMC to dynamically enable or disable rescheduling when flights
are reassigned to a Mirror Meter Fix.

When Mirror Meter Fixes are enabled, and a frozen aircraft assigned to a CTAS Meter Fix that
is within an adapted distance from that CTAS Meter Fix is reassigned to an adapted Mirror
Meter Fix of that original CTAS Meter Fix TMA SHALL [0877]
    a. maintain the current STA times to the Mirror Meter Fix and to the runway.
   b. be notified of any conflict as defined in Static Site Adaptable Scheduler Data.

Requirement 0879 has been deleted.

TMA SHALL [0900] delay the STA of an aircraft to fall outside of any Scheduling Meter Fix
blocked time interval if the tentative STA falls within such interval.

TMA SHALL [0910] not schedule an aircraft within a blocked time interval.

TMA SHALL [0920] associate a specific aircraft type (e.g., Heavy, Large, Small or 757), which
may optionally be derived from a specific call sign, with a blocked time slot.

TMA SHALL [0930] schedule other aircraft around a blocked time slot, taking into account the
wake vortex requirement for the type of aircraft for which the slot is reserved.
   a. (subrequirement deleted)
   b. (subrequirement deleted)

Requirement 0935 has been deleted.




                                               60                             TMA System Spec
                                                                                     FAA-E-2971
                                                                               17 December 2008
                                                                                      Final Rev N
The delay to be absorbed in Center airspace may cause other aircraft in the sequence to be
delayed in order to retain adequate separation but should never change the established sequence.

3.2.1.5.1.2    Separation at the Runway

For the purposes of runway scheduling, "runway" means the runway threshold if the airport is
operating under IFR, and means the FAF if the airport is under VFR.
Although in the En Route airspace, scheduling applies principally to scheduled times to the
Scheduling Meter Fix/Meter Fix Arc, it also needs to consider the implications of these schedules
on the operations at the runways. Therefore, a tentative runway schedule to all runways is
calculated where runway separation constraints are applied.

The runway schedule is not necessarily FCFS ordering based on ETAs to the assigned runway.
Instead, the runway sequence and schedule depends on the so-called "order of consideration".
This order establishes the precedence with which each aircraft that is assigned to the runway is
allowed to establish its "landing slot", taking into account only the STA of aircraft already
scheduled and the set of separation constraints at the runway.

TMA SHALL [0939] apply runway scheduling to the runway threshold if the operator- selected
airport configuration is IFR and to the FAF if the operator-selected airport configuration is VFR.

TMA SHALL [0940] establish a schedule for each runway based on the following order of
consideration:
   a. (subrequirement deleted)
   b. Only aircraft assigned to the runway under consideration are considered in establishing
      the precedence.
   c. Aircraft from the same super stream have a precedence based on their sequence in the
      super stream.
   d. When considering aircraft from different super streams only the "next-to-be-scheduled"
      aircraft from each super stream can compete, and precedence goes to the aircraft with the
      earliest runway ETA, unless aircraft designated as Single Gate Free Flow are present.
   e. When aircraft designated as Single Gate Free Flow are present, perform the following
      check to determine if any SGFF aircraft should take preference over the aircraft that
      would have been selected for runway scheduling under item d (earliest runway ETA)
      above.
      1. Determine the assigned runway of the aircraft selected using the rules of item d
          above. Find the first SGFF in each super stream class that is assigned to the same
          runway.
      2. For each of the selected SGFF aircraft, determine a preliminary runway STA based on
          the aircraft’s preliminary Scheduling Meter Fix/Meter Fix Arc STA, the time to fly
          from the Scheduling Meter Fix/Meter Fix Arc to the runway threshold and the runway
          and airport scheduling constraints.
      3. For each of the selected SGFF aircraft, compute the preliminary runway delay using
          the following equation:


                                                61                             TMA System Spec
                                                                                     FAA-E-2971
                                                                               17 December 2008
                                                                                      Final Rev N
              Preliminary Runway Delay = Preliminary Runway STA – (Preliminary
              Scheduling Meter Fix or Meter Fix Arc STA+ Time to Fly from the Scheduling
              Meter Fix or Meter Fix Arc to the Runway Threshold).
       4. For each of the selected SGFF aircraft, identify those that meet the following two
          conditions:
           have preliminary runway delays that equal or exceed the product of the
              dynamically assignable SGFF Preferencing Delay Parameter (PDP in fractional
              form) and the flight’s Flight TRACON Maximum Delay (FTMD), and
           the first aircraft to be scheduled in the selected SGFF aircraft’s super stream is an
              SGFF aircraft.
       5. From the group of SGFF aircraft that met the above conditions (qualifying
          preliminary runway delays and first AC in super stream is SGFF), determine the
          SGFF aircraft with the earliest runway ETA and call it the SGFF AC To Be
          Preferenced. If an SGFF AC To Be Preferenced has been identified, then select for
          runway scheduling, the first AC in the super stream that also contains the SGFF AC
          To Be Preferenced. Otherwise, select for runway scheduling the aircraft found using
          the rules in item d above.

TMA SHALL [0950] schedule the STA (at the runway) of an aircraft as the later of:
  a. The STA at the Scheduling Meter Fix/Meter Fix Arc plus the nominal TTF from the
     Scheduling Meter Fix/Meter Fix Arc to the runway.
   b. The earliest time which does not conflict with the aircraft that have already been
      scheduled at the runway in this cycle.
   c. The ETA at the runway if the aircraft does not have an assigned scheduling meter fix or
      meter fix arc.

In case of conflict at the runway, TMA SHALL [0960] delay the STA at the runway of the
selected aircraft until no further conflict exists. TMA SHALL [0970] derive the minimum
required separation as the largest separation (converted to time based on the ground speed)
compatible with the following constraints:
    a. Runway threshold (or FAF) acceptance rate.
   b. Runway occupancy time.
   c. Separation criteria from FAA Order 7110.65, Air Traffic Controllers’ Handbook (wake
      vortex constraints).
   d. Runway separation buffer.
   e. TMC-entered runway blocked slots and intervals.

TMA SHALL [0980] delay any STA which falls within a runway blocked time interval to be
outside and later than that interval, at which time the STA must be checked again for possible
conflict with other scheduled aircraft.

3.2.1.5.1.3    Feedback from Runway Schedules to Scheduling Meter Fix/Meter Fix Arc
               Schedules


                                               62                             TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

The requirements in this section apply to meter fix arcs when the meter fix arcs are used as the
points of deconfliction scheduling, i.e. when offset scheduling is not active.

Allocation of excess TRACON, or scheduling meter fix to runway/threshold, delays into the
ARTCC arrival scheduling process is based on parameters called Route Maximum Delay (RMD)
(Static Site Adaptable Scheduler Data) and TRACON Buffer (TB) (Dynamic Site Adaptable
Scheduler Data). The RMD, specified by the RMD in the site adaptation for each route,
quantifies the maximum delay which could be absorbed in the TRACON on a specific route by
delaying the aircraft on its path between the CTAS meter fix and the runway. The TB, initialized
through site adaptation or updated by the TMC, quantifies the maximum delay that will be
allowed in the TRACON or between the CTAS meter fix and runway/threshold.

The maximum delay that can be absorbed in the TRACON (between CTAS meter fix and
runway) by a flight (Flight TRACON Maximum Delay {FTMD}) SHALL [0982] be the lesser of
the RMD for the route the aircraft will follow or the TB.

Because the scheduler uses the Scheduling Meter Fix or Meter Fix Arc as the point where
constraints are applied (including the application of delay absorption maximums), the scheduler
must have a value to use for the maximum delay that can be absorbed between the runway and
the Scheduling Meter Fix/Meter Fix Arc. The Scheduling Meter Fix/Meter Fix Arc maximum
delay (SFMD) must be computed from the FTMD and the delay that may be absorbed between
the CTAS Meter Fix and the Scheduling Meter Fix/Meter Fix Arc (CSMD).

The CSMD, a site adaptable parameter, SHALL [0985] be the maximum delay that can be
absorbed within the performance characteristics of a large set of aircraft types on the trajectory
between the CTAS Meter Fix and the Scheduling Meter Fix/Meter Fix Arc. {Requirement 0985
is deferred.} The CSMD SHALL [0986] be assigned a positive value if the Scheduling Meter
Fix/Meter Fix Arc is further along the flight’s trajectory (closer to runway) than the CTAS Meter
Fix, otherwise the CSMD is assigned a negative value.

The SFMD SHALL [0987] be computed by subtracting the CSMD from the FTMD and
represents the maximum delay that can be absorbed between the runway and the Scheduling
Meter Fix/Meter Fix Arc.

If the scheduled time at the runway is later than the scheduled time at the Scheduling Meter
Fix/Meter Fix Arc plus the nominal TTF from the Scheduling Meter Fix/Meter Fix Arc to the
runway, the flight’s runway arrival must be delayed. Since the delay absorbing ability between
the scheduling meter fix/meter fix arc and runway/threshold is limited to a maximum value
(SFMD), it may be necessary to absorb the excess delay in ARTCC airspace or between the
Scheduling Meter Fix and the CTAS Meter Fix when they are adapted at different locations. The
Scheduling Meter Fix/Meter Fix Arc STA will be set later by the amount of that excess delay.

TMA SHALL [0990] delay the Scheduling Meter Fix/Meter Fix Arc STA for each aircraft for
which the STA at the runway is later than the sum of the Scheduling Meter Fix/Meter Fix Arc


                                                63                             TMA System Spec
                                                                                 FAA-E-2971
                                                                           17 December 2008
                                                                                  Final Rev N
STA, the TTF from the Scheduling Meter Fix/Meter Fix Arc to the runway, and the SFMD (the
maximum delay that can be absorbed between the scheduling meter fix/meter fix arc and
runway/threshold).

TMA SHALL [1000] delay the Scheduling Meter Fix/Meter Fix Arc STA by the amount of time
the runway STA is later than the sum specified in requirement 0990. This amount of time is the
excess delay to be absorbed in the Center airspace and/or between the Scheduling Meter Fix and
the CTAS Meter Fix when they are adapted at different locations.

TMA SHALL [1010] not change the sequence of aircraft in the Scheduling Meter Fix/Meter Fix
Arc schedules due to any feedback from the TRACON runway schedules.

Requirement 1020 has been deleted.

TMA SHALL [1030] re-examine the Scheduling Meter Fix/Meter Fix Arc schedule for possible
conflicts if any aircraft in the sequence was delayed due to feedback from the runway schedule.

TMA SHALL [1040] iterate the process of setting up runway schedules and Scheduling Meter
Fix/Meter Fix Arc schedules until all constraints are met both at the runways and Scheduling
Meter Fixes/Meter Fix Arcs, allocating to the route segment between the scheduling meter
fix/meter fix arc and runway/threshold, no delays greater than the maximum delay that can be
absorbed between the scheduling meter fix/meter fix arc and runway/threshold.

Requirements 1042, 1044, and 1046 have been deleted.

3.2.1.5.1.3.1 Scheduling at the CTAS Meter Fix

When offset scheduling is active and meter fix arc processing is not active, scheduling times are
generated for CTAS Meter Fixes to be used for Host Sector Meter List display.

When offset scheduling is active and Meter Fix Arc processing is not active, TMA SHALL
[1041] calculate CTAS meter fix STAs based on the Scheduling Meter Fix schedules, the TTF
between the CTAS Meter Fix and the Scheduling Meter Fix, the delay to be absorbed in Center
airspace and/or between the CTAS Meter Fix and the Scheduling Meter Fix, and the CSMD (the
maximum delay that can be absorbed between the CTAS Meter Fix and the Scheduling Meter
Fix.

When offset scheduling is active and Meter Fix Arc processing is not active, TMA SHALL
[1043] compute CTAS Meter Fix STAs as follows:
   a. When the flight’s Scheduling Meter Fix STA less its Scheduling Meter Fix ETA is
       greater than the CSMD, the CTAS Meter Fix STA is set equal to the Scheduling Meter
       Fix STA less the sum of the TTF from the CTAS Meter Fix to the Scheduling Meter Fix
       and CSMD.




                                                64                             TMA System Spec
                                                                                FAA-E-2971
                                                                          17 December 2008
                                                                                 Final Rev N
   b. When the flight’s Scheduling Meter Fix STA less its Scheduling Meter Fix ETA is less
      than or equal to the CSMD, the CTAS Meter Fix STA is set equal to the CTAS Meter Fix
      ETA.


3.2.1.5.1.3.2 Scheduling at the Meter Fix Arc under Offset Scheduling.

Meter Fix Arc schedules are generated differently depending on whether the Meter Fix Arc is
used as the non-runway point of schedule deconfliction. This section addresses the generation of
Meter Fix Arc scheduling times when offset scheduling is active and the Meter Fix Arc is not
used as the non-runway point of deconfliction. When offset scheduling and Meter Fix Arc
processing are both active, TMA computes deconflicted STAs at the Scheduling Meter Fix then
“backs off” Meter Fix Arc STAs to be used for Host Sector Meter List display.

When offset scheduling and Meter Fix Arc processing are both active, TMA calculates schedules
at the Meter Fix Arc based on the Scheduling Meter Fix schedules, the TTF between the Meter
Fix Arc and the scheduling meter fix, the delay to be absorbed in Center airspace and/or between
the Meter Fix Arc and the Scheduling Meter fix and the Meter Fix Arc Maximum Delay
(MFAMD). The MFAMD is the maximum delay that can be absorbed within the performance
characteristics of a large set of aircraft types on the trajectory between the Scheduling Meter Fix
and the Meter Fix Arc. (Requirement 1047 has been deleted.)

When offset scheduling and Meter Fix Arc processing are both active, TMA SHALL [1048]
compute Meter Fix Arc STAs as follows:
   a. When the flight’s Scheduling Meter Fix STA less its Scheduling Meter Fix ETA is
      greater than the MFAMD, the Meter Fix Arc STA is set equal to the Scheduling Meter
      Fix STA less the sum of the TTF from the Meter Fix Arc to the Scheduling Meter Fix and
      MFAMD.
   b. When the flight’s Scheduling Meter Fix STA less its Scheduling Meter Fix ETA is less
      than or equal to the MFAMD, the Meter Fix Arc STA is set equal to the meter Fix Arc
      ETA.


3.2.1.5.1.4    Scheduling at the Outer Meter Arc

TMA SHALL [1050] calculate schedules at the Outer Meter Arc based on the CTAS Meter Fix
or Meter Fix Arc schedules, the TTF from the Outer Meter Arc to the CTAS Meter Fix or Meter
Fix Arc, the delay to be absorbed in the Center airspace, any computed Excess Outer Fix Delay
EOFD and a dynamically assignable parameter called Outer Fix Delay (OFD) (Dynamic Site
Adaptable Scheduler Data). The OFD is the maximum delay that can be absorbed within the
performance characteristics of a large set of aircraft types on the trajectory between the Outer
Meter Arc and the CTAS Meter Fix/Meter Fix Arc.

Upon a change to the Outer Fix Delay (OFD), TMA SHALL [1051] reallocate the delay at the
Outer Meter Arc, the Outer-Outer Arc, Outer-Three Arc, and Outer-Four Arc. For this re-


                                                65                              TMA System Spec
                                                                                         FAA-E-2971
                                                                                   17 December 2008
                                                                                          Final Rev N
allocation, delay refers to the delay at the time of the freeze, or the delay when the frozen aircraft
was re-scheduled, if it was re-scheduled.


TMA SHALL [1060] assign an Outer Meter Arc STA to an aircraft:
  a. No later than the CTAS Meter Fix/Meter Fix Arc STA minus the nominal TTF between
     Outer Meter Arc and CTAS Meter Fix/Meter Fix Arc.
   b. No earlier than the CTAS Meter Fix/Meter Fix Arc STA minus the sum of the nominal
      TTF between Outer Meter Arc and CTAS Meter Fix/Meter Fix Arc, any computed
      EOFD, and the value of the relevant OFD.

TMA SHALL [1070] calculate the difference of ETA and STA for each aircraft at the CTAS
Meter Fix/Meter Fix Arc, i.e., the "Delay to be absorbed in the Center Airspace" (DCA) by that
aircraft.

TMA SHALL [1080] assign an Outer Meter Arc STA for an aircraft equal to the ETA at the
Outer Meter Arc if DCA is less than or equal to the sum of any computer EOFD and OFD for the
assigned Outer Meter Arc and CTAS Meter Fix/Meter Fix Arc (since the total Center delay can
then be comfortably absorbed between Outer Meter Arc and CTAS Meter Fix/Meter Fix Arc).

TMA SHALL [1090] assign an STA for an aircraft equal to the ETA plus the difference DCA
minus the sum of any computed EOFD and OFD, when DCA is larger than the sum of any
computed EOFD and OFD.


3.2.1.5.1.5    Scheduling at the Outer-outer Arc


TMA SHALL [1092] calculate schedules at the Outer-outer Arc based on the Outer Meter Arc
schedules, the TTF from the Outer-outer Arc to the Outer Meter Arc, the delay to be absorbed in
the Outer-Center airspace, any computed Excess Outer-outer Arc Delay (EOOAD) and a
dynamically assignable parameter called Outer-outer Arc Delay (OOAD) (Dynamic Site
Adaptable Scheduler Data). The OOAD is the maximum delay that can be absorbed within the
performance characteristics of a large set of aircraft types on the trajectory between the Outer-
outer Arc and the Outer Meter Arc.

Upon a change to the Outer-outer Arc Delay (OOAD), TMA SHALL [1093] reallocate the delay
at the Outer Meter Arc, the Outer-Outer Arc, and the Outer-Three Arc, and Outer-Four Arc. For
this re-allocation, delay refers to the delay at the time of the freeze, or the delay when the frozen
aircraft was re-scheduled, if it was re-scheduled.


TMA SHALL [1094] assign an Outer-outer Arc STA to an aircraft:



                                                 66                               TMA System Spec
                                                                              FAA-E-2971
                                                                         17 December 2008
                                                                               Final Rev N
   a. No later than the Outer Meter Arc STA minus the nominal TTF between Outer-outer Arc
      and Outer Meter Arc.
   b. No earlier than the Outer Meter Arc STA minus the sum of the nominal TTF between
      Outer-outer Arc and Outer Meter Arc, any computed EOOAD and the value of the
      relevant OOAD.

TMA SHALL [1095] calculate the difference of ETA and STA for each aircraft at the Outer
Meter Arc, i.e., the "Delay to be absorbed in the Outer-Center Airspace" (ODCA) by that aircraft.

TMA SHALL [1097] assign an Outer-outer Arc STA for an aircraft equal to the ETA at the
Outer-outer Arc if ODCA is less than or equal to the sum of any computed EOOAD and OOAD
for the assigned Outer-outer Arc and Outer Meter Arc (since the total Outer-Center delay can
then be comfortably absorbed between Outer-outer Arc and Outer Meter Arc).

TMA SHALL [1099] assign an STA for an aircraft equal to the ETA plus the difference ODCA
minus the sum of any computed EOOAD and OOAD, when ODCA is larger than the sum of any
computed EOOAD and OOAD.

Requirement 1100 has been deleted.


3.2.1.5.1.6    Scheduling at the Outer-Three Arc

TMA SHALL [1101] calculate schedules at the Outer-Three Arc based on the Outer-Outer Arc
schedules, the TTF from the Outer-Three Arc to the Outer-Outer Arc, the ODCA, any computed
EO3AD, and a dynamically assignable parameter, O3AD (Dynamic Site Adaptable Scheduler
Data). The O3AD is the maximum delay that can be absorbed within the performance
characteristics of a large set of aircraft types on the trajectory between the Outer-Three Arc and
the Outer-Outer Arc.

TMA SHALL [1103] assign an Outer-Three Arc STA to an aircraft:
  a. No later than the Outer-Outer Arc STA minus the nominal TTG between the Outer-Three
     Arc and the Outer-Outer Arc.
  b. No earlier than the Outer-Outer Arc STA minus the sum of the nominal TTF between
     Outer-Three Arc and Outer-Outer Arc, any computed EO3AD and the value of the
     relevant O3AD

TMA SHALL [1108] calculate the difference of ETA and STA for each aircraft at the Outer-
Outer Arc, i.e., the "Delay to be absorbed in the Outer-Outer Center Airspace" (OODCA) by that
aircraft.

TMA SHALL [1112] assign an Outer-Three Arc STA for an aircraft equal to the ETA at the
Outer-Three Arc if OODCA is less than or equal to the sum of any computed EO3AD and O3AD
for the assigned Outer-Three Arc and Outer-Outer Arc (since the total Outer-Outer Center delay
can then be comfortably absorbed between the Outer-Three Arc and the Outer-Outer Arc).


                                                67                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

TMA SHALL [1114] assign an STA for an aircraft equal to the ETA plus the difference OODCA
minus the sum of any computed EO3AD and O3AD, when OODCA is larger than the sum of any
computed EO3AD and O3AD.

Upon a change to the O3AD, TMA SHALL [1096] reallocate the delay at the Outer Meter Arc,
Outer-Outer Arc, Outer-Three Arc, and Outer-Four Arc. For this re-allocation, delay refers to the
delay at the time of the freeze, or the delay when the frozen aircraft was re-scheduled, if it was
re-scheduled.


3.2.1.3.1.7    Outer-Four Arc Assignment

An Outer-Four Arc (O4A) is an arc with an adapted distance and angle from an adapted CTAS
waypoint for which TMA calculates ETAs and STAs. This arc is typically located beyond the
Outer-Three Arc. In addition, the Outer-Four Arc times are displayed on the HCS sector lists.

TMA SHALL [1301] assign an Outer-Four Arc to an aircraft using site-adaptable logic (Static
Site Adaptable Scheduler Data) based on the following:
    a.   The intersection of the HCS converted route with an adapted Outer-Four Arc.
    b.   Assigned Outer-Three Arc.
    c.   Engine type.
    d.   Aircraft assigned altitude.

If an aircraft is eligible for more than one Outer-Four Arc, then TMA SHALL [1303] assign the
first adapted Outer-Four Arc.

TMA SHALL [1305] assign an Outer-Four Arc to an aircraft whenever it:
  a.  Receives a new flight plan.
  b. Receives a flight plan amendment that modifies the converted route of flight or engine
      type.
  c.  Receives a flight plan amendment that modifies the assigned altitude.

TMA SHALL [1306] calculate schedules at the Outer-Four Arc based on the Outer-Three Arc
schedules, the TTF from the Outer-Four Arc to the Outer-Three Arc, the ODCA, any computed
EO4AD, and a dynamically assignable parameter, O4AD (Dynamic Site Adaptable Scheduler
Data). The O4AD is the maximum delay that can be absorbed within the performance
characteristics of a large set of aircraft types on the trajectory between the Outer-Four Arc and
the Outer-Three Arc.

TMA SHALL [1307] assign an Outer-Four Arc STA to an aircraft:
  a.  No later than the Outer-Three Arc STA minus the nominal TTF between the Outer-Four
      Arc and the Outer-Three Arc.




                                                68                              TMA System Spec
                                                                                FAA-E-2971
                                                                          17 December 2008
                                                                                 Final Rev N
   b.    No earlier than the Outer-Three Arc STA minus the sum of the nominal TTF between
         Outer-Four Arc and Outer-Three Arc, any computed EO4AD and the value of the
         relevant O4AD.

TMA SHALL [1308] calculate the difference of ETA and STA for each aircraft at the Outer-
Three Arc, i.e., the "Delay to be absorbed in the Outer-Three Center Airspace" (O3DCA) by that
aircraft.

TMA SHALL [1309] assign an Outer-Four Arc STA for an aircraft equal to the ETA at the
Outer-Four Arc if O3DCA is less than or equal to the sum of any computed EO4AD and O4AD
for the assigned Outer-Four Arc and Outer-Three Arc (since the total Outer-Three Center delay
can then be comfortably absorbed between the Outer-Four Arc and the Outer-Three Arc).

TMA SHALL [1315] assign an STA for an aircraft equal to the ETA plus the difference O3DCA
minus the sum of any computed EO4AD and O4AD, when O3DCA is larger than the sum of any
computed EO4AD and O4AD.

Upon a change to the O4AD, TMA SHALL [1317] reallocate the delay at the Outer Meter Arc,
Outer-Outer Arc, Outer-Three Arc, and Outer-Four Arc. For this re-allocation, delay refers to the
delay at the time of the freeze, or the delay when the frozen aircraft was re-scheduled, if it was
re-scheduled.

3.2.1.5.1.8    Scheduling from Locally Departed Airports

TMA SHALL (1102) provide the capability to suppress normal scheduling functionality for
aircraft departing from selected airports to all or a specified arrival airport and provide
alternative handling instead. (Candidate internal departure airports, known as locally departed
airports, will be identified for this functionality via adaptation (Static Site Adaptable Scheduler
Data)). The following conditions will apply for this functionality:

   a) The Scheduler will not apply its normal scheduling algorithms to any flight originating
      from an airport listed in the adaptation file and flying to all or a specified arrival airport.
      Instead, the Scheduler will set the STA of such a flight to be equal to its ETA. If the user
      sets a departure time using the TGUI interface, the ETA will change, and the STA will
      follow exactly.

   b) A local departure’s STA will not affect the STAs of any other flights. Note this implies
      that the Scheduler will not schedule such flights to achieve legal separation or to meet any
      other constraints such as airport acceptance rate.

   c) Once such a flight becomes active, the Scheduler will continually set its STA to be equal
      to its ETA as computed.

   d) The locally departed aircraft will be distinguishable on the TGUI from other aircraft.
      TGUI load graphs will reflect these local departure flights just like any other flights.


                                                 69                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
       Since the Scheduler does not provide true scheduling for these aircraft, acceptance rates
       may be exceeded. This will be reflected on the load graphs.

   e) Meter list data for all aircraft departing the identified locally departed airports and
      arriving at any of the associated arrival airports will not be sent to the HOST controller
      sector lists.


3.2.1.5.1.9    Computing Excess Delays

The standard method for allocating delay is to begin assigning delay from the runway outward.
In the standard method, all delay above some maximum amount will be scheduled at outermost
adapted arc assigned to the flight. TMA can assign this excess delay to other portions of a
flight’s route, for example between the OOA and O3A. This section specifies the requirements
for computing, and assigning, excess delays by this alternative method of delay allocation.

TMA may compute and assign excess delay based on the values adapted on the aircraft’s
outermost assigned arc. An OOA, O3A, or O4A may be adapted which may specify the
maximum amount of delay that can be taken prior to reaching the respective arc. If this is the
case, the location where any excess delay is to be taken may also be specified in the definition of
the arc. This may be specified as EOFD, in which case excess delay is to be taken between the
OMA and the display point. It may be specified as EOOAD, in which case excess delay is to be
taken between the OOA and the OMA. It may be specified as Excess Outer-Three Arc Delay
(EO3AD), in which case excess delay is to be taken between the O3A and the OOA. It may be
specified as Excess Outer-Four Arc Delay (EO4AD), in which case excess delay is to be taken
between the O4A and the O3A.

If the outermost assigned arc is the O4A, TMA SHALL [1131] compute excess delay when a
dynamically assignable parameter, OO4AD (Dynamic Site Adaptable Scheduler Data), is adapted
for the assigned O4A. The OO4AD is the maximum delay that can be absorbed by an aircraft
prior to reaching the O4A.

If SHALL [1131] applies, TMA SHALL [1133] compute excess delay as the difference between
the DCA and the sum of; OFD, OOAD, O3A Delay (O3AD), OO3AD, O4A Delay (O4AD) and
OO4AD.

If SHALL [1131] applies, TMA SHALL [1135] assign all excess delay to one of the following,
based on Static Site Adaptable Scheduler Data:
    a. Excess Outer Fix Delay
    b. Excess Outer-Outer Arc Delay
    c. Excess Outer-Three Arc Delay
    d. Excess Outer-Four Arc Delay

If the outermost assigned arc is the O3A, TMA SHALL [1132] compute excess delay when a
dynamically assignable parameter, OO3AD (Dynamic Site Adaptable Scheduler Data), is adapted


                                                70                              TMA System Spec
                                                                              FAA-E-2971
                                                                        17 December 2008
                                                                               Final Rev N
for the assigned O3A. The OO3AD is the maximum delay that can be absorbed by an aircraft
prior to reaching the O3A.

If SHALL [1132] applies, TMA SHALL [1134] compute excess delay as the difference between
the DCA and the sum of; OFD, OOAD, O3A Delay (O3AD) and OO3AD.

If SHALL [1132] applies, TMA SHALL [1136] assign all excess delay to one of the following,
based on Static Site Adaptable Scheduler Data:
    a. Excess Outer Fix Delay
    b. Excess Outer-Outer Arc Delay
    c. Excess Outer-Three Arc Delay

If the outermost assigned arc is the OOA, TMA SHALL [1142] compute excess delay when a
dynamically assignable parameter, OOOAD (Dynamic Site Adaptable Scheduler Data), is
adapted for the assigned OOA. The OOOAD is the maximum delay that can be absorbed by an
aircraft prior to reaching the OOA.

If SHALL [1142] applies, TMA SHALL [1144] compute excess delay as the difference between
the DCA and the sum of; OFD, OOAD, and the OOOAD.

If SHALL [1142] applies, TMA SHALL [1146] assign all excess delay to one of the following,
based on Static Site Adaptable Scheduler Data:
    a. Excess Outer Fix Delay
    b. Excess Outer-Outer Arc Delay

Upon a change to the Outside O4A Delay (OO4AD), TMA SHALL [1139] reallocate the delay at
the Outer Meter Arc, Outer-Outer Arc, Outer-Three Arc, and Outer-Four Arc. For this re-
allocation, delay refers to the delay at the time of the freeze, or the delay when the frozen aircraft
was re-scheduled, if it was re-scheduled.

Upon a change to the Outside O3A Delay (OO3AD), TMA SHALL [1053] reallocate the delay at
the Outer Meter Arc, Outer-Outer Arc and the Outer-Three Arc. For this re-allocation, delay
refers to the delay at the time of the freeze, or the delay when the frozen aircraft was re-
scheduled, if it was re-scheduled.

Upon a change to the Outside Outer-outer Arc Delay (OOOAD), TMA SHALL [1055] reallocate
the delay at the Outer Meter Arc and the Outer-Outer Arc. For this re-allocation, delay refers to
the delay at the time of the freeze, or the delay when the frozen aircraft was re-scheduled, if it
was re-scheduled.

Requirements 1052, 1054, and 1056 have been deleted.




                                                 71                               TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
3.2.1.5.2     Scheduling Using Automated Miles-in-Trail (deleted)
Requirements 1105, 1106, 1107, 1110, 1150, 1155, 1160, 1165, 1166, 1170, 1180, 1190, 1200,
   1210, 1215, 1217, 1220, 1230, 1240, 1250, 1260, 1270, 1280, and 1290 have been deleted.

3.2.1.5.2.1     Recommend Stop Time (deleted)

Requirements 1120, 1130, 1140, 1320, 1330, 1340, 1350, 1360, and 1370 have been deleted.

3.2.1.5.2.2     Recommend Stream Class Combinations into Super Stream Classes

Requirements 1300 and 1310 have been deleted.

3.2.1.5.2.3  Finalize the Miles-in-Trail Restrictions for Manually Set and "Lightly" Loaded
             Streams (deleted)
 Requirements 1311 and 1312 have been deleted.

3.2.1.5.2.4  Iterate the Non-finalized Miles-in-Trail Settings to Meet the Requested AAR
             (deleted)
 Requirements 1313 and 1314 have been deleted.

3.2.1.5.3     Adjacent Facility Metering

In order to get a view of future demand, TMA must receive track surveillance data from any
ARTCC that, in whole or in part, is within 200 nmi of the arrival TMA-adapted airport except for
oceanic airspace and the airspace of a foreign country. Figure 3.2.1.5.3-1 depicts a situation in
which the 200-nmi radius extends beyond the Center boundary and includes Adjacent Center
airspace.




                                                72                            TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N


                                T MA Ad jacent F acility




                                                             Adapted
                                                           ‘‘In-Range’’
                                                          Coordination
                                                            Fixes and
                    200 Miles                            Stream Classes



                                       TRACON


                                        TMA Arrival C enter




           O c e a ni c
           A ir S p a c e                       A irs pa c e o f a
                                            Fo re i gn C o u n t ry

                       Figure 3.2.1.5.3-1. TMA Near a Center Boundary

Requirements 1380 and 1390 have been deleted.

TMA SHALL [1400] schedule all arrival aircraft for which tracks have been received from other
facilities and are destined to a TMA adapted airport in the same way as TMA schedules aircraft
reported to be in its Center.

Having determined the total demand at the TMA airport, it is necessary to meter aircraft arriving
from the adjacent Center through coordination fixes that are closer than 200 nmi. This is because
there is not enough delay capability within the arrival Center to produce an orderly arrival flow.
The schedule at the coordination fix is calculated by passing excess delay back to the adjacent
Center.

Requirement 1410 has been deleted.

Requirement 1420 has been deleted.


                                                73                             TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

Figure 3.2.1.5.3-2 depicts the calculation of STAs at the coordination fix.




                                           CMD

                          Calculated
                                                Delay to
                          Delay
                                             be absorbed
                          at CTAS MF        in the adjacent
                                                 facility




       ETA       STA                                            ETA        STA
       MF        MF                                              CF         CF
                   Figure 3.2.1.5.3-2. Calculation of Coordination Fix STA



Requirement 1430 has been deleted.

Figure 3.2.1.5.3-3 depicts the assignment of adjacent facility aircraft to an adapted "In-range"
coordination fix (i.e., a coordination fix within 200 nmi of the arrival airport).




                                                74                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N


      Alpha Turbo

                                                          Alpha (Jet & Turbo)
             Alpha Jet
        Alpha Jet

                Alpha Jet

                  Alpha Jet
                                                        Beta (Turbo only)

         Beta Turbo



             Adjacent Facility                            TMA Center

  Figure 3.2.1.5.3-3. Assignment of Adjacent Facility Aircraft to an Adapted "In-range"
                                     Coordination Fix



Requirement 1431 has been deleted.

Figure 3.2.1.5.3-4 depicts the assignment of adjacent Center aircraft to stream classes at an "In-
range" coordination fix.




                                                75                              TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N


                       33000                        Jets


                       17000                        Turbo-props

                        9000                        Piston



                           Coordination
                               Fix
                Figure 3.2.1.5.3-4. Stream Classes Entering the TMA Center



Requirement 1432 has been deleted.

Requirements 1433, 1434, 1435, 1440, and 1450 have been deleted.

Requirements 1451 and 1452 have been deleted.

TMA SHALL [1453] be capable of sending metering data for display on sector controllers’
displays to any one, or combination of the following;
a. The Primary Center
b. Up to eight Adjacent Centers.

When sending flight specific messages to an Adjacent Center’s Host, TMA SHALL [1454] send
CID values used by the Adjacent Center’s Host in its processing of the flights.

TMA SHALL [1455] be capable of accepting the specification for, via Static Site Adaptable
Scheduler Data, the Center, or Centers, where metering data for a Meter Reference Point (MRP),
or portion of an MRP, is to be displayed.

TMA SHALL [1456] be capable of sending metering data to an Adjacent Center’s Host when the
Adjacent Center's TMA is; running, not running, or none is configured.

TMA SHALL [1457] be capable of restricting, via Site Adaptable Installation Data, the ability to
turn on or off the display of metering data, by TGUI instance and by Center where the metering
data is to be displayed.


                                               76                            TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.2.1.5.4   Arrival Plan Preview Capability

In general usage, all TMA displays at the En Route Center and the TRACON will see a unified
arrival plan which has been agreed upon by controllers at both facilities. At times, however, it
will be beneficial for controllers to investigate alternate arrival plans, that is, to preview an
alternate plan. Figure 3.2.1.5.4-1 depicts the preview capability.




                            Figure 3.2.1.5.4-1. Preview Capability.

TMA SHALL [1460] provide one preview arrival plan at the En Route Center, and one preview
arrival plan at the TRACON without causing any degradation in the computation of the main
arrival plan. {Requirement 1460 is deferred.}

TMA SHALL [1470] allow a TMC to study the effect of modifying the following parameters:
  a. Airport Configuration Changes.
   b. Flow Rate or Acceptance Rate Changes.
   c. Miles-in-Trail changes.
   d. Gate / CTAS Meter Fix/Scheduling Meter Fix Changes (multiple or single aircraft).
   e. Runway Change (multiple or single aircraft).
   f. Blocked Intervals.
   g. Blocked Slots.
   h. Sequence Constraints.


                                                77                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N
   i. Grouping and Merging of Stream Classes.
   j. Single Gate Free Flow intervals {Requirement 1470 is deferred.}

TMA SHALL [1480] provide the capability for TMCs in either facility to view:
  a. The current arrival plan.
   b. The Center's preview arrival plan.
   c. The TRACON's preview arrival plan. {Requirement 1480 is deferred.}

TMA SHALL [1490] mark all preview information in a way that makes it readily distinguishable
from information from the main arrival plan. {Requirement 1490 is deferred.}

TMA SHALL [1500] provide the capability for TMCs to duplicate the preview arrival plan
parameters from the main arrival plan. {Requirement 1500 is deferred.}

TMA SHALL [1510] provide the capability for TMC's to accept a preview plan as the main
arrival plan. {Requirement 1510 is deferred.}


3.2.1.5.5   Automatic Deletion / Open Slot Processing

After a flight has been processed by TMA, several controller actions may cause the flight to no
longer be considered eligible for an arrival plan. In order to maximize the use of available
landing times and minimize the effects of automatic rescheduling, TMA either automatically
deletes the ineligible flight or converts it into an “open slot”. A “non-frozen” flight is deleted; a
“frozen” flight is converted into an “open slot.”

The concept of “frozen” versus “non-frozen” flights involves time-based scheduling, where
schedules for frozen flights are considered “frozen” once the flight is within the STA freeze
horizon. “Non-frozen” flights are outside the freeze horizon.
Schedules for non-frozen flights are dynamic. If the flight is no longer eligible for the schedule,
it will be automatically deleted from TMA processing and both TMA and HCS display.

Schedules for frozen flights need to remain stable until the TMC takes manual action. If a frozen
flight is no longer eligible for the schedule, it will be converted into an “open slot.” The STA will
be retained and an indication will be provided to the TMC that a frozen flight has become an
“open slot” in order to allow the TMC to evaluate and resolve the schedule change manually. A
flight that has been converted to an “open slot” will be deleted from Host sector meter lists but
remain in TMA. (Since it only applies to frozen flights, “open slot processing” only applies to
scheduling under time-based scheduling mode.)

Whenever any of the following is received for a flight whose STA is not frozen, TMA SHALL
[0794] delete the flight from TMA processing and display:
   a. Manually generated Remove Strip message.



                                                  78                              TMA System Spec
                                                                                FAA-E-2971
                                                                          17 December 2008
                                                                                  Final Rev N
   b. Amendment that changes the flight’s destination airport to a non-TMA airport.
   c. subrequirement is deleted
   d. subrequirement is deleted
   e. subrequirement is deleted

Whenever any of the following is received for a flight whose STA is frozen, TMA SHALL
[0795] convert the flight into an “open slot”:
   a. Manually generated Remove Strip message. (Subrequirement a is deferred)
   b. Amendment that changes the flight’s destination airport.
   c. subrequirement is deleted.
   d. subrequirement is deleted.
   e. Amendment that changes the flight’s altitude status to VFR.

If a frozen flight becomes an “open slot” or a non-frozen flight is automatically deleted, TMA
SHALL [0796] delete the flight from the TMA metering.
An indication is provided to the TMC on both the TGUI and the PGUI displays that a frozen
flight has become an “open slot.” (Details are provided in the TMA Build 2 CHI Requirements
Specification) This enables the TMC to easily identify a frozen landing time that may be
available for other aircraft.

TMA SHALL [0797] delete an “open slot” from TMA processing and display whenever any of
the following occurs:
    a. The “open slot” is rescheduled.
   b. The STA expires (i.e., times out) from the schedule.
   c. The “open slot” is suspended by operator input on the TGUI.
   d. A TMC rescheduling event occurs affecting all frozen aircraft.

If the condition that caused a flight to be ineligible for TMA processing is reversed (e.g., a flight
is amended back to IFR), the flight will be considered a newly eligible flight. The new or
amended flight plan will be processed and displayed separately from any “open slot” with the
same AID. This may result in duplicate AIDs on a timeline, one with an “open slot” indicator
and one without. Retaining the “open slot” provides the TMC with the option of manually
rescheduling the “empty” slot.

If a new flight plan or an amendment is received that reverses the condition that created the
“open slot,” TMA SHALL [0798] retain the “open slot” and process the newly entered or
amended flight plan as a unique new flight plan.

When a TMC performs a manual schedule operation, TMA SHALL [1511] provide visual
indication when the cursor is positioned over an open slot. If the TMC manually schedules an




                                                 79                               TMA System Spec
                                                                                          FAA-E-2971
                                                                                     17 December 2008
                                                                                           Final Rev N
aircraft over an open slot (i.e. the visual indicator is active), TMA SHALL [1512] assign the
open slot's scheduling times to the aircraft and delete the open slot.
If a new flight plan is received with an altitude status indicating that the flight is VFR, TMA
SHALL [1513] ignore that flight for scheduling.

TMA SHALL [1493] reject the TMC input of open slot scheduling request if superstream
validation has been enabled in adaptation and the aircraft have different stream classes that are
not in the same superstream.

Requirement 1514 has been deleted.

When standard open slot processing has been enabled in adaptation and TMA has received TMC
input to schedule into an open slot and the selected aircraft and the open slot are destined for the
same airport where the selected aircraft’s type has no adapted restriction on runway use, TMA
SHALL [1491] assign the selected aircraft the runway STA, the STAs for all the meter reference
points and the runway assignment from the open slot.

When standard open slot processing has been enabled in adaptation and TMA has received TMC
input to schedule into an open slot and the selected aircraft and the open slot are destined for
different airports or the selected aircraft’s type has an adapted restriction on the intended runway,
TMA SHALL [1492] recalculate the selected aircraft’s runway STA, while making no change to
the runway assignment, and assign the STAs for all other meter reference points from the open
slot.



When alternate open slot processing has been enabled in adaptation and TMA has received TMC
input to schedule into an open slot on a non-runway timeline and the selected aircraft and open
slot are assigned to different meter fixes, TMA SHALL [1494] reject the request.

When alternate TMC open slot processing has been enabled in adaptation and TMA has received
TMC input to schedule into an open slot and both the selected aircraft and the open slot are from
runway timelines, TMA SHALL [1495] use the runway as the meter reference point level.

When alternate TMC open slot processing has been enabled in adaptation and TMA has received
TMC input to schedule into an open slot and either the selected aircraft or the open slot are from
non-runway timelines, TMA SHALL [1496] use the meter reference point (meter fix, meter fix
arc, etc.) closest to the runway of the selected aircraft or of the open slot as the meter reference
point level.

When alternate TMC open slot processing has been enabled in adaptation and TMA has received
TMC input to schedule into an open slot and both the selected aircraft and the open slot are
assigned to the same meter fix and are destined for the same airport and the selected aircraft’s
type has no adapted runway restrictions, TMA SHALL [1497] assign the selected aircraft the



                                                 80                               TMA System Spec
                                                                                     FAA-E-2971
                                                                              17 December 2008
                                                                                      Final Rev N
STA from the open slot at the meter reference point level and calculate STAs for all other meter
reference points, and assign the runway from the open slot.

When alternate TMC open slot processing has been enabled in adaptation and TMA has received
TMC input to schedule into an open slot and both the selected aircraft and the open slot are
assigned to the same meter fix and are destined for different airports, or the selected aircraft’s
type has a runway restriction on the intended runway, TMA SHALL [1498] assign the selected
aircraft the STA of the open slot at the meter reference point level and calculate STAs for all
other meter reference points, while making no change to the runway assignment.

3.2.1.5.6   Diversion List Processing

TMCs need to keep track of flights that have been diverted to nearby airports that may represent
future landing demand. The TMA capability to keep track of diverted flights is referred to as
diversion list processing (DLP). Flights that are amended to change the flight's destination will
be eligible for diversion list processing. Frozen flights are always included in DLP; while non-
frozen flights can be, based on site dependent adaptation. The time a flight remains in the
diversion list is also site adaptable. The diversion list will detail diversion information for each
diverted flight for each TMA adapted airport. TMA will provide the TMC the ability to view
(onscreen) and print the diversion list. Diversion list data will be archived for a user defined
period of up to 15 days.

Whenever an amendment is received that changes the destination of a flight from a TMA adapted
airport, TMA SHALL [1516] add the flight to diversion list processing if any of the following
conditions are met:
        a. The flight's STA is frozen.
        b. The flight's STA is not frozen, but the flight's runway ETA is within a site static
           adaptable number of minutes of the time the diversion occurred. {Requirement 1516
           is deferred.}

TMA SHALL [1518] delete a flight from diversion list processing whenever one of the following
occurs:
        a. The flight's time on the diversion list exceeds a site adaptable value.
        b. TMC manually deletes the flight.
        c. When an active flight plan is received for an aircraft that matches the AID and
           destination airport of an entry on the diversion list. {Requirement 1518 is deferred.}

TMA SHALL [1519] maintain the following information for each flight in diversion list
processing:
       a. AID.
       b. Airport diverted from.
       c. Airport diverted to.
       d. Time the diversion occurred.
       e. Delay absorbed prior to diversion
       f. Assigned remaining delay at the time of the diversion


                                                 81                              TMA System Spec
                                                                                     FAA-E-2971
                                                                               17 December 2008
                                                                                      Final Rev N
       g. Diversion location, from field 6 (coordination fix) or beginning of field 10 of the
          amended flight plan. {Requirement 1519 is deferred.}

TMA SHALL [1522] compute the delay absorbed prior to diversion as the difference between
the aircraft's ETA at the CTAS meter fix/meter fix arc at the time of diversion and the aircraft's
CTAS meter fix/meter fix arc ETA computed as the aircraft entered the ARTCC boundary.
{Requirement 1522 is deferred.}

TMA SHALL [1523] compute the assigned remaining delay at the time of the diversion as the
difference between the aircraft's STA at the CTAS meter fix/meter fix arc at the time of diversion
and the aircraft's ETA at the CTAS meter fix/meter fix arc at the time of the diversion.
{Requirement 1523 is deferred.}

TMA SHALL [1524] provide the operator with the ability to view diversion list information
either on a TGUI display or printed hardcopy. {Requirement 1524 is deferred.}


3.2.1.5.7   Multi-TRACON Processing

Multi-TRACON functionality, will allow TMA to be capable of scheduling arriving aircraft at
adapted airports in to up to 5 independent TRACONS.

Prior to Multi-TRACON, TMA treated all airports as if they were in one single “TRACON”
whether they actually were or not. For the purpose of system software limits, Multi-TRACON is
the capability for a single TMA system to be able to schedule arriving aircraft to up to five (5)
independent TRACONs. Each TRACON can be configured with up to five (5) arrival airports.
Airports must be adapted within TMA in order for TMA to schedule to them.

Each TRACON being served is a “TRACON Group”. Each group is operationally independent
from each other. Activities within one TRACON Group (when there is more than one TRACON
Group actively metering) must not interfere with the other TRACON Groups. This includes:
    Start up and initialization of any TRACON when there is more than one TRACON
       actively metering.
    All metering and scheduling actions taken in any TRACON when there is more than one
       TRACON actively metering.
    Failover and recovery for any TRACON lost when there is more than one TRACON
       actively metering.
    Shutdown of a TRACON when there is more than one TRACON actively metering.

The Failover and Recovery of a single TRACON Group in a Multi-TRACON environment must
not compromise the operation of any other TRACON Group in the TMA system. The loss of a
single TRACON Group or up to N-1 TRACON Group(s) in a N-TRACON Group configuration
must not compromise the operation of the remaining TRACON Group(s). TMA System failover
and recovery response should be independent of the number of TRACON Group(s) configured.



                                                 82                              TMA System Spec
                                                                                   FAA-E-2971
                                                                            17 December 2008
                                                                                    Final Rev N
To support TRACON independence, TMA requires that each TRACON have a unique set of
meter fixes, which apply to it and it only. Each TRACON will have to access distinct set of
adaptation data.

Graphical User Interfaces, (GUIs) will only display data for a single arrival TRACON.

All current scheduling requirements for the existing primary adapted airport remain in effect for
Multi-TRACON. All current requirements for timing, performance, and functionality apply.

TMA SHALL [1551] be capable of scheduling arriving aircraft to multiple TRACONs (called
TRACON Groups) independent of each other, applying all scheduling requirements to each.

For the purpose of system software limits, TMA will be capable of independently scheduling,
and metering arriving aircraft to up to five (5) eligible airports per TRACON, in up to five (5)
TRACONs within an ARTCC.

Requirement 1552 has been deleted.

Eligible Multi-TRACON airports SHALL [1553] be independent from each other and not effect
metering or scheduling to any other TRACON(s).

The schedule for each TRACON SHALL [0832] not be affected by events that trigger
rescheduling in other TRACONs.

The output of meter list data for a TRACON SHALL [0233] not be blocked or re-enabled due to
TMC inputs for other TRACONs.

Changes to the state of TMA processing for a TRACON (e.g., restart, termination) SHALL
[0135] not impact the outputs for other TRACONs.

M&C SHALL [1554] provide the capability for any TRACON Group(s) to independently:
     a. start
     b. stop, or
     c. restart

M&C SHALL [1555] provide the capability to monitor the operational status of each
TRACON’s:
     a. Data Feed(s)
     b. Core Group
     c. TRACON Groups.

All alerts that M&C is required to send for display on a TGUI and/or PGUI SHALL [1556] be
sent to all TGUIs and/or PGUIs in each TRACON Group.




                                                83                              TMA System Spec
                                                                                FAA-E-2971
                                                                         17 December 2008
                                                                                 Final Rev N
A single GUI process (TGUI or PGUI) SHALL [1557] only display data for a single TRACON at
any time.

A dual GUI workstation SHALL [1558] be capable of being configured to display two GUI
processes (one PGUI, one TGUI) each fed by a different TRACON simultaneously.

Each TRACON SHALL [1559] have a unique set of meter fixes.


3.2.1.5.8   En Route Departure Capability

TMA has been designated to provide the comparable metering functionality of the NAS En
Route Spacing Program (ESP) off board of En Route Automation Modernization (ERAM).
Where Arrival TMA provides metering of aircraft to TRACON/airports, ESP provides for the
metering of aircraft to ARTCC boundaries. Its metering function generates sequenced lists of
aircraft destined to external airports in other ARTCCs. It allows an ARTCC to meter and freeze
scheduled times for outbound aircraft to the Center boundary. Thus, TMA will now perform
both arrival and En Route metering to adapted airports. The En Route Departure Capability
(EDC) is TMA’s capability equivalent of ESP.

TMA EDC metering architecture adopts the software architecture used by TMA for the Multi-
TRACON capability. Similar to the TRACON Group concept, TMA adds a new group called the
Meter Point Group that performs En Route metering using a process developed by NASA’s
Multi-Center research system and modified for use in TMA, called the Meter Point DP (MPDP).

With the addition of EDC, the TMA software architecture is composed of three main collections
or groups of components; an input processing and database management component (Core
Group), one or more ETA and STA generation and information display TRACON-specific
components (TRACON Group) and an En Route metering component that generates ETAs and
STAs at the Center boundary for outbound traffic (Meter Point Group). The Core Group is
composed of the following processes: one HDIF, one or more ADIFs, one WDPD, one ISM and
one CM. A TRACON Group is composed of one TRACON DP process and one or more of the
following processes: RA/TS, GUIR, PGUI and TGUI. The Meter Point Group is composed of
one MPDP process and one or more of the following processes: RA/TS, GUIR, PGUI and TGUI.

EDC deconflicts/schedules departure and overflight aircraft exiting an ARTCC’s airspace,
destined to adapted external destination airport, at an arc, called a meter point (MP), located near
the Center boundary. In contrast to arrival scheduling, where the runway represents the common
coupling point for scheduling of all super stream classes, EDC meter point scheduling considers
super stream classes as independent entities and any changes applied to one super stream class,
such as Miles-in-Trail restrictions, will not affect any other super stream class. Deconfliction in
EDC TMA is decoupled from Arrival TMA and does not consider scheduling constraints at
downstream arrival meter fixes and runways.




                                                 84                              TMA System Spec
                                                                                      FAA-E-2971
                                                                                17 December 2008
                                                                                       Final Rev N
Functionally, EDC generates sector meter list data for local MPs that allow users to select which
MP/external destination airport combinations are displayed on DSR sector lists. Likewise, EDC
TGUIs display MP timelines, while EDC PGUIs display tracks and sequence lists for both
overflight and departure aircraft destined to EDC airports. As stated above, EDC
deconflicts/schedules exiting departure and overflight aircraft at a MP as opposed to an “airport”.
Thus metering is done, not to an airport, but to an arc near the Center boundary. Therefore, a
number of TMA’s Multi-TRACON arrival capabilities specifically related to metering to an
airport are not required for the EDC. Capabilities not applicable in EDC are:

           a.   airport configuration change
           b.   airport and TRACON acceptance rate changes
           c.   TRACON buffer changes
           d.   runway separation matrix change
           e.   subrequirement deleted
           f.   runway occupancy time
           g.   blocked intervals for runways
           h.   single gate free flow (TRACON)
           i.   runway assignments
           j.   nominal routes to runways
           k.   delay reporting
           l.   autoswap
           m.   display of arrival routes
           n.   display of TRACON related airspace
           o.   display of outer fixes/names and holding arcs/names
           p.   offset scheduling
           q.   Enabling/disabling freeze horizons by airport
           r.   Independent scheduling by airport
           s.   Alternate TMC Swap processing


The following naming convention changes SHALL [4200], for the purposes of display, apply to
the system in EDC mode:
           a. Meter Fix to Meter Point
           b. Meter Fix Arc to Meter Point
           c. Outer Meter Arc/Outer Arc to Outer Point
           d. Outer-Outer Arc to Outer-Outer Point
           e. (subrequirement deleted)
           f. Arrival Airport to Destination Airport
           g. Meter Reference Point to Meter Point.
           h. Outer-Three Arc to Outer-Three Point
           i. Outer-Four Arc to Outer-Four Point


The following acronym changes SHALL [4205], for the purposes of display, apply to the system
in EDC mode:


                                                85                             TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
           a.   MFA to MP
           b.   OMA to OP
           c.   OOA to OOP
           d.   O3A to O3P
           e.   O4A to O4P

TMA SHALL [4207] be capable of configuring one (1) Meter Point Group within an ARTCC.

EDC SHALL [4210] define a Meter Point (MP) over which it will deconflict (sequence and
schedule) aircraft outbound from a Center.

The MP SHALL [4215] be defined in site adaptation data using:
         a. distance and radial ends from a Meter Point Arc center
         b. lower and upper altitude limits
         c. destination airport(s)
         d. engine type(s)
         e. altitude and speed crossing restrictions, optional.

EDC SHALL [4223] disable TMC MP reassignment for aircraft until all upstream meter points
have been crossed.

Requirement 4220 is deleted.

Only aircraft destined to an adapted EDC airport SHALL [4225] be eligible for Meter Point
assignment. EDC SHALL [4230] perform Meter Point assignment in order to determine that a
flight is eligible for EDC processing. When an eligibility is determined, the flight will be
assigned to a Meter Point for deconfliction. EDC SHALL [4235] consider the following flight
plan data during MP assignment:
             a. intersection of converted route with MP Arc
             b. destination airport
             c. engine type
             d. assigned altitude

EDC SHALL [4240] perform MP reassignment if any of the following are changed:
       a. assigned altitude
       b. engine type
       c. destination airport
       d. converted route

After performing MP reassignment, if the aircraft did not have an MP assigned previously, a
message adding the flight plan SHALL [4245] be generated.

After performing MP reassignment, if a new MP is assigned, an amendment message SHALL
[4250] be generated.



                                              86                             TMA System Spec
                                                                                 FAA-E-2971
                                                                           17 December 2008
                                                                                  Final Rev N
After performing MP reassignment, if a new MP cannot be assigned from the converted route for
a flight that previously had an assigned MP a delete message SHALL [4255] be generated.

Flights that are not assigned an MP SHALL [4260] cause a warning message to be generated.

In EDC mode, the Meter Point, the Scheduling Meter Point and the Display Point SHALL [4265]
be coincident.

EDC SHALL [4270] assign the most downstream eligible MPs to a flight, as specified in
adaptation.

In addition to Meter Points, EDC SHALL [4275] optionally adapt Outer Points (OP), Outer-
Outer Points (OOP), Outer-Three Points (O3P), and Outer-Four Points (O4P) as additional
processing locations associated with the Meter Points. Times at these Outer Points are not
deconflicted but are based on times-to-fly and delay absorption restrictions.

Each Aircraft SHALL [4280] have a maximum of one OP, one OOP, one O3P, and one O4P
assigned for each assigned MP. The OP SHALL [4285] be determined from the assigned MP’s
associated OPs. The OOP SHALL [4290] be determined from the assigned OP’s associated
OOPs. The O3P SHALL [4292] be determined from the assigned OOP’s associated O3Ps. The
O4P SHALL [4293] be determined from the assigned O3P’s associated O4Ps.

M&C SHALL [4295] support the capability to:
       a. start TRACON groups and the EDC group independently
       b. stop TRACON groups and the EDC group independently
       c. configure TRACON groups and the EDC group independently.

Requirement 4300 is deleted.

EDC SHALL [4305] provide the Center the capability for outbound EDC processing for up to
128 airports.

EDC SHALL [4310] provide the capability to manage the display of meter lists by Center and
Meter Point and airport.

EDC SHALL [4315] be capable of setting freeze horizons on a stream class basis.

EDC SHALL [4317] provide asymmetric freeze horizon capability.

TMA uses “predetermined sets” of Super Stream Class mappings which will be adapted and will
be available to choose from on the TGUI. This is dynamic in that the user may change which set
of Super Stream Classes are in effect at runtime on the TGUI. This provides the capability to
combine and decombine streams of traffic so that they are deconflicted together when combined
and separately when decombined.



                                              87                            TMA System Spec
                                                                                     FAA-E-2971
                                                                               17 December 2008
                                                                                      Final Rev N
EDC SHALL [4320] be capable of combining aircraft assigned to a stream class destined to
different EDC airports over the same Meter Point into a single super stream class using
“predetermined sets”.

EDC SHALL [4325] be capable of combining aircraft assigned to a stream class destined for the
same or different airports going over multiple Meter Points into a single super stream class using
“predetermined Sets”.

EDC SHALL [4330] provide the capability to specify up to two future super stream class
mappings for EDC processing.

EDC SHALL [4335] provide the capability to specify a super stream class miles-in-trail
constraint. This constraint applies to any aircraft that is deemed to be in that SSC at the time the
restriction is to be put into effect.

EDC SHALL [4340] provide the capability to specify up to two future miles-in-trail restrictions
for EDC processing.

EDC SHALL [4345] support independent scheduling of each EDC super stream class such that
constraint changes intended to affect one do not affect scheduling information for any other.

EDC SHALL [4350] provide the capability to reschedule all flights in a super stream class.

EDC SHALL [4355] provide the capability to reschedule only flights in a super stream class after
and including a selected aircraft.

EDC SHALL [4360] optionally include manually scheduled aircraft in EDC processing when
rescheduling.

To provide deconfliction of more than one super stream class over EDC Meter Points without
also imposing the first come first served (FCFS) sequencing constraint associated with the
grouping of aircraft into super streams, the Multiple Super Stream Class Deconfliction (MSSD)
capability is provided.

EDC SHALL [4356] provide the capability to dynamically create groups of super streams.

EDC SHALL [4357] allow a super stream to be part of one, and only one, MSSD constraint at
any one time.

EDC SHALL [4358] provide the capability to dynamically change the Multiple Super Stream
Deconfliction (MSSD) miles-in-trail (MIT) constraint for a super stream class group.

EDC SHALL [4359] apply MSSD constraints only to scheduling of aircraft to EDC Meter Points
(MPs).



                                                 88                               TMA System Spec
                                                                          FAA-E-2971
                                                                    17 December 2008
                                                                           Final Rev N
When applying MSSD constraints, EDC SHALL [4361] enforce FCFS sequence constraints on
aircraft within the same super stream class.

When applying MSSD constraints, EDC SHALL [4362] enforce the super stream MIT constraint
on aircraft within the same super stream class.

When applying MSSD constraints, EDC SHALL [4363] enforce the MSSD MIT separation
restriction on aircraft within all super stream classes included in a super stream class group.

When a constituent super stream class in a super stream class group is rescheduled, EDC SHALL
[4364] reschedule all super stream classes in that super stream class group.

EDC SHALL [4366] support a number of EDC MSSD constraints up to one-half the maximum
number of supported EDC super stream classes.

EDC SHALL [4367] allow up to two sets of future scheduling MSSD scheduling constraints to
be specified and used in scheduling at the Meter Point.

EDC SHALL [4365] calculate ETAs at assigned:
       a. Meter Points
       b. Outer Points
       c. Outer-Outer Points
       d. Outer-Three Points
       e. Outer-Four Points

EDC SHALL [4370] calculate STAs at assigned:
       a. Meter Points
       b. Outer Points
       c. Outer-Outer Points
       d. Outer-Three Points
       e. Outer-Four Points

EDC SHALL [4375] allow a TMC to manually assign an MP STA to a flight over an MP.

EDC SHALL [4380] allow a TMC to manually reassign an aircraft from one MP to another MP.

EDC SHALL [4385] support EDC processing using existing CMS Metering message formats for
the ability to manage and display meter lists on the HOST DSR.

EDC SHALL [4390] provide the following information for display to sector controllers:
  a) Header containing:
     1. Airport identifier ("MP " or an adapted 3 character alphanumeric ID)
     2. Runway configuration ("METRG")
     3. Airport acceptance rate



                                                 89                              TMA System Spec
                                                                                      FAA-E-2971
                                                                                17 December 2008
                                                                                       Final Rev N
   b) For each aircraft entry, the airport field is “MP “ or an adapted 3 character alphanumeric
      ID

When the adapted 3 character alphanumeric ID for a MP matches an adapted arrival airport
within the arrival TRACON, TMA SHALL [4393] pass the currently assigned airport acceptance
rate of the arrival airport to the Host, otherwise, pass an airport acceptance rate of zero.

EDC SHALL [4395] provide the capability to manually schedule a proposed flight departing
from a local airport referenced to its first assigned MP or, if adapted and assigned, the first MP’s
corresponding Outer Point, Outer-Outer Point, Outer-Three Point, or Outer-Four Point.

When a proposed internal departure flight is manually scheduled to a Meter Point, and is destined
for an arrival TRACON in the same center, TMA SHALL [4397] schedule and display the STD
on the arrival TRACON TGUI(s).

When a proposed internal departure flight is manually scheduled to a Meter Fix, and is assigned
to a meter point in the same center, TMA SHALL [4398] schedule and display the STD on the
meter point TGUI(s).

When running in EDC mode, the periodic reschedule duration SHALL [4400] be set to 12
seconds.

EDC SHALL [4410] provide the capability to apply a maximum Meter Point (MP) acceptance
rate to aircraft assigned to a MP and destined for a single adapted EDC airport. A MP
acceptance rate must always be associated with a single adapted EDC airport.
EDC SHALL [4415] provide the capability to apply a maximum MP Gate acceptance rate to
aircraft assigned to an adapted group of MPs (Gate) and destined for a single adapted EDC
airport. A MP Gate acceptance rate must always be associated with a single adapted EDC
airport.

EDC SHALL [4420] provide the capability to apply up to two MP and MP gate future
acceptance rates for each adapted EDC airport. A single future acceptance rate may change any
or all of the MP and MP gate rates for the adapted EDC airport.

EDC SHALL [4425] provide the capability to delete a previously applied future MP and MP
Gate acceptance rate.

When a MP acceptance rate changes, EDC SHALL [4430] reschedule the superstreams and
associated MSSD superstreams that contain flights assigned to the MP and destination airport.

When a MP Gate acceptance rate changes, EDC SHALL [4435] reschedule the superstreams and
associated MSSD superstreams that contain flights assigned to the MP Gate and destination
airport.




                                                 90                              TMA System Spec
                                                                              FAA-E-2971
                                                                         17 December 2008
                                                                               Final Rev N
EDC SHALL [4440] optionally include manually scheduled aircraft in MP and MP Gate
acceptance rate processing.


3.2.2 FAST Processing [deleted]

Section 3.2.2 and all its subsections, including Figures 3.2.2-1, 3.2.2.3.2-1, 3.2.2.4.1.1-1,
3.2.2.4.1.2-1, and 3.2.2.7.4-1, Table 3.2.2.3.1-1, and Requirements 1515, 1520, 1525, 1526,
1530, 1531, 1532, 1533, 1534, 1535, 1536, 1537, 1540, 1544, 1545, 1546, 1550, 1560, 1565,
1570, 1571, 1572, 1574, 1580, 1585, 1590, 1600, 1601, 1602, 1605, 1610, 1620, 1625, 1626,
1630, 1640, 1650, 1660, 1670, 1680, 1690, 1700, 1710, 1715, 1720, 1730, 1740, 1750, 1760,
1765, 1770, 1780, 1790, 1800, 1810, 1820, 1830, 1835, 1840, 1845, 1850, 1855, 1860, 1865,
1870, 1880, 1890, 1900, 1910, 1920, 1930, 1940, 1950, 1955, 1960, 1964, 1965, 1966, 1970,
1980, 1990, 2000, 2010, 2011, 2012, 2020, 2030, 2040, 2050, 2060, 2070, 2080, 2090, 2091,
2100, 2110, 2120, 2130, 2140, 2150, 2160, 2170, 2180, 2190, 2200, 2210, 2220, 2230, 2240,
2250, and 2260 have been deleted.


3.2.1.5.8.1    Multiple Meter Point Capability

The Multiple Meter Point (MMP) capability is an enhancement to the existing TMA system
aimed at extending the metering horizon for arrival and En Route aircraft. This new feature will
enhance intra-center metering. It also provides support for future regional metering. It extends
the functionality of both the Multi-TRACON Arrival TMA and the En Route Departure
Capability (EDC) as described below.

Multiple meter points can be applied to En Route aircraft by providing up to three (3) metering
locations for overflight and departure traffic traversing an ARTCC. Whereas EDC provides
deconfliction for outbound aircraft at a single meter point typically near the center boundary,
MMP extends this to up to 3 meter points located anywhere in the center, or within reason,
upstream of the center as in adjacent center arcs. As with EDC, center departures may be
scheduled to available slots in the overhead En Route traffic stream, and then continue through
additional meter points before existing in ARTCC’s airspace.

 MMP provides three (3) additional upstream deconflicted metering locations where arrival
aircraft can be scheduled independently from the Arrival TRACON. These upstream points
provide additional metering opportunities for controllers working arrival traffic flows in an
ARTCC or adjacent ARTCC. Traffic can be metered at any of the arrival meter points in
addition to the meter fixes and runways. Aircraft can be frozen relative to the next meter point it
approaches while still remaining unfrozen to meter points further downstream. This reduces
sequencing and scheduling errors induced by a long freeze horizon. This is termed
“independent-freeze”. It may be applied to either arrival or En Route aircraft.




                                                 91                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                 17 December 2008
                                                                                        Final Rev N
Sector meter list data for each of the meter points can be selected for display on the DSR sector
lists. EDC TGUI timelines can be configured to display aircraft scheduled to each of the adapted
meter points.

No coupled scheduling is provided with this new MMP capability. Super stream classes may
group one or more MPs and super stream classes may be grouped via MSSD. Aircraft belonging
to a super stream class or MSSD group are deconflicted independently from aircraft belonging to
a different super stream class or MSSD group. Scheduling is also independent between the
Arrival TMA and any upstream arrival MPs. Scheduling parameters put into effect for the
Arrival TMA (e.g., airport acceptance rates, runway rates) affect only the Arrival TMA
scheduler. These rates are not “passed-back” to any additional meter points. As in EDC, traffic
can be controlled by specifying restrictions over each of the Meter Points.

Due to the complexities introduced when a flight is assigned to more than one MP, a TMC will
only be allowed to change an aircraft’s MP assignment for the last assigned MP after all
upstream MPs have been crossed.

NOTE: Except where specifically overridden in this section, MMP inherits the requirements
specified in Section 3.2.1.5.8 for the En Route Departure Capability.

TMA’s MMP capability SHALL [4600] allow the assignment of up to three (3) MPs to an En
Route aircraft (e.g. overflight, MP departure) or an arrival aircraft upstream of the arrival
TRACON boundary (i.e. arrival airport in the local ARTCC).

TMA’s MMP capability SHALL [4602] deconflict up to a total of 25 MPs for either En Route or
arrival aircraft.

TMA’s MMP capability SHALL [4604] disallow the grouping of upstream and downstream MP
stream classes into
    a. super stream classes
    b. super stream class groups

TMA’s MMP capability SHALL [4606] deconflict a MP superstream independently from
deconfliction at any upstream or downstream MP superstreams.

TMA’s MMP capability SHALL [4608] deconflict a MSSD group independently from
deconfliction at any upstream or downstream MSSD groups.

TMA’s MMP capability SHALL [4610] deconflict EDC MP superstreams independently from
deconfliction of arrival TRACON meter fixes/arcs and runway.

TMA’s MMP capability SHALL [4612] deconflict EDC MSSD groups independently from
deconfliction of arrival TRACON meter fixes/arcs and runway.




                                                92                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                17 December 2008
                                                                                        Final Rev N
TMA’s MMP capability SHALL [4614] be capable of setting freeze horizons on a stream class
basis. Since a stream class definition includes the MP, a flight can be frozen relative to one MP
and unfrozen relative to another (downstream) MP.

NOTE: It is recommended that the user restrict the setting of MP freeze horizons so as not to
overlap or interfere with freeze horizons of other meter reference points.

TMA’s MMP capability SHALL [4616] allow for optionally adapted crossing restrictions to be
applied for En Route aircraft at the last MP in the set of MPs a flight traverses.

For MMP processing, the arrival TRACON SHALL [4618] use available downstream
coordination information from the very last assigned MP for computation of an ETA until the
aircraft crosses that MP. Downstream coordination information is MP crossing time, crossing X
and Y coordinates, crossing altitude, and speed information.

When TMA receives the Sector Controller command to swap between two and five aircraft at a
MP, TMA SHALL [4620] re-sequence the affected aircraft by exchanging the STA unless a
rejection condition is met, as described in requirement [4624].

When a flight is assigned to more than one MP, Sector Controller swap validation and STA
exchange SHALL [4622] be performed at the first non-traversed MP for each flight included in
the swap.

TMA SHALL [4624] send a reject message to the HCS whenever it receives a swap or
resequence message from a sector controller for between two and five aircraft at a MP and any of
the aircraft have:
    a. A different assigned MP gate
    b. A different engine type (Subrequirement b. is deferred)
    c. Not been frozen

If the TMC entered a command to “reset aircraft ID” after a TMC meter fix or meter point
reassignment, TMA SHALL [4626] reapply the current flight plan routing and assigned MRPs to
that aircraft and recalculate ETAs and STAs.




                                                93                             TMA System Spec
                                                                                             FAA-E-2971
                                                                                        17 December 2008
                                                                                              Final Rev N

3.2.3 TMC Graphical User Interface

The TMC-GUI function provides the CHI for the TMC. The function is capable of generating a
number of generic display presentations that can be provided at any of the facilities, i.e., En
Route, Terminal, or Tower, in which TMA is installed.

A single TMA remote GUI SHALL [2263] be capable of switching between TMA TGUI and
TMA PGUI.

The TMC-GUI function is depicted in Figure 3.2.3-1.


        M&C                                                      TMC entry     TMA
                                                                             Processing
   Event Timer           Adaptation data


             allowable entries,
              display configs.       Display Definition                      Data Messages


                                     Display Interaction
                                    Display Presentation
                                      - Timeline
                                      - Load Graph
                                      - Plan View
                                      - Auxiliary Info

                                           Data Retrieval

                                    Parameter Interaction
                                               Data Messages


All processes interact with M&C                  TMA             TMC display ETMS
                                               Processing


                                       Figure 3.2.3-1 TMC-GUI Function

As depicted in Figure 3.2.1-1, the TMA Processing sub-functions are:
   • Display Presentation.
    •    Display Definition.
    •    Parameter Interaction.




                                                            94                          TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
   •      Data Retrieval.
   •      Display Interaction.

These sub-functions are site-adapted through the use of the Adaptation Data Files.

3.2.3.1          Inputs & Outputs

The TMC GUI SHALL [2265] be capable of processing the following inputs:
   a. Adaptation data.
   b. TMC entries.
   c. TMA data.

Whenever it recalculates ETAs or STAs, TMA SHALL [2270] also update the TMC display
presentations.

Requirement 2280 has been deleted.

TMA SHALL [2290] place a print request in the queue (response) as a result of the TMC request
to print a report (stimuli) with a mean response time of 3 seconds or less, a 99th percentile
response time of 5 seconds or less, and a maximum response time of 10 seconds or less.

TMA SHALL [2291] be capable of printing out the following:
  a. Traffic count.
   b. Statistical Delay Information (SDI).
   c. Diversion list information. {Subrequirement c is deferred}

The TMC GUI SHALL [2295] be capable of producing the following outputs:
   a. TMC display .
   b. TMC entries.


TMA SHALL [2296] be capable of producing color hardcopy output.

Upon receipt of any of the scheduling entries listed in Section 3.2.3.4, the TMC-GUI function
SHALL [2300] forward data to the TMA Processing function.

TMA SHALL [2310] display lexical feedback (response) for TMC input (stimuli) with a mean
response time of 0.15 second or less, a 99th percentile response time of 0.2 second or less, and a
maximum response time of 0.25 second or less.

NOTE: Lexical feedback is the feedback for operator input actions such as display keyboard
inputs on the display device. The time measurement is taken from the moment that the operator
entry occurs to the completion of the feedback response.


                                                95                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N

TMA SHALL [2320] display syntactic feedback (response) for TMC sent messages (stimuli)
with a mean response time of 0.6 second or less, a 99th percentile response time of 1.2 seconds
or less, and a maximum response time of 1.8 seconds or less.

NOTE: Syntactic feedback is the confirmation received for message format validity. The time
measurement for a syntactic feedback starts from the moment that the message is sent for
processing (e.g., an operator enters a command) to the moment that the syntactic feedback is
either returned to the operator or when the message is cleared to be processed.

3.2.3.2 Display Presentation

The Display Presentation function provides the following logical displays for the TMC:
   • Timeline display.
   •   Load graph display.
   •   Plan View display.
   •   Auxiliary Info display.

These displays are specified in terms of logical display formats, i.e., identification of objects on
the screen, organization of objects on the screen, sizing, orientation, etc.

Upon receipt of data from the TMA function, TMA SHALL [2330] update the TMC displays.

Upon receipt of TMC entries affecting display presentations, TMA SHALL [2340] update the
TMC displays.

Requirements 2345 and 2346 have been deleted from this document and moved to the TMA
Build 2 CHI Requirements Specification.

3.2.3.2.1   Timeline Display

Requirement 2410 has been deleted from this document and moved to the TMA Build 2 CHI
Requirements Specification.

3.2.3.2.2   Load Graph Display

Requirements 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432,
2433, 2434, 2435, 2436, 2437, 2438, 2439, 2440, 2441, 2442, 2443, 2444, 2445, 2446, 2447,
2448, 2449, 2450, 2451, 2452, 2453, 2454, 2455, 2456, 2457, 2458, 2459, and 2460 have been
deleted from this document and moved to the TMA Build 2 CHI Requirements Specification.




                                                 96                               TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

3.2.3.2.3     Plan View Display

Requirements 2470, 2471, 2472, 2473, 2474, 2475, 2476, 2477, 2478, 2479, 2480, 2481, 2482,
2483, 2484, 2485, 2486, 2487, 2488, 2489, 2490, 2491, 2492, 2493, 2494, 2495, 2496, 2497,
2498, 2499, 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, and 2510 have been
deleted from this document and moved to the TMA Build 2 CHI Requirements Specification.

Requirements 2350 and 2520 have been deleted.

TMA SHALL [2521] provide a capability for the PGUI process to execute standalone and
independent of the operational system.

A standalone PGUI is defined as a PGUI capability that does not require any active flight
information (i.e., live data or prerecorded data) and can execute on a single machine without any
network connectivity or network dependencies.

3.2.3.2.4     Statistical Calculations

TMA SHALL [2530] provide the capability to calculate the following quantities for display
purposes:
   a. Traffic Count.
   b. Statistical Delay Information.

as described in the following sections.

3.2.3.2.4.1     Traffic Count

TMA SHALL [2540] compute a daily traffic count according to the following:
  a. Over a time interval of 60 minutes in the past to 120 minutes in the future (-75 to 134
     minutes).
   b. By selected time intervals: 10, 15 minutes.
   c. (subrequirement deleted).
   d. By runway threshold and/or CTAS meter fix according to STA.
   e. By runway threshold and/or CTAS meter fix according to ETA.
   f. (subrequirement deleted).
   g. By runway threshold and/or CTAS meter fix according to actual aircraft crossing time.

3.2.3.2.4.2     Statistical Delay Information

Note: This section was completely replaced by RPR-109. Within this section, RPRs 055, 119,
and 170 were superceded by RPR-109.


                                                97                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N

This section describes the delay calculations required using the terms defined below.

Delay SHALL [2556] be computed for the Center as the difference between the ETA computed
as the aircraft entered the ARTCC boundary (referred to as the CTAS Meter Fix (MF) ETA
below), and the last actual crossing time at the CTAS meter fix/meter fix arc. The CTAS MF
ETA SHALL [2558] not be recomputed if the assigned CTAS meter fix/meter fix arc is changed
after the aircraft has entered the Center boundary. A reportable delay period SHALL [2559]
begin when the minimum possible delay for an aircraft is equal to or greater than the user
specified delay threshold. For the delay information stored in delay reporting files, the actual
delay after crossing the meter fix for the last time SHALL [2561] be used. The delay threshold
can range between 0 and 15 minutes. (Note that when the delay threshold is set to 0 minutes,
every flight is considered to be a reportable delay.) A user-defined delay close-out time (which
can range between 0 and 60 minutes) is used to determine when a delay file is closed.

The longest delay in the system is categorized into 15 minute bins, called delay levels. For
example, if the longest delay in the system is 38 minutes, the current delay level is “+30”. The
delay level SHALL [2565] be increased whenever the minimum possible delay for any aircraft in
the system exceeds the next multiple of 15 minutes. For example, when the longest delay in the
system goes from 38 minutes to 45 minutes, the new delay level is “+45”. (Note that the delay
level is a multiple of 15 minutes, regardless of the delay threshold set by the user.)

A separate record of delays SHALL [2562] be kept for each adapted airport supported by TMA.

A separate delay threshold and delay close-out time SHALL [2563] be maintained for each
adapted airport supported by TMA.

The name of each delay report file SHALL [2564] contain the following:
   a. Date of the delay reporting period.
   b. CTAS MF ETA for the first aircraft that exceeded the delay threshold.
   c. Last actual CTAS meter fix/meter fix arc crossing time for the last aircraft with a
      reportable delay.
   d. Name of the airport for which delays are recorded.

A delay report file SHALL [2568] be opened for a given airport when (a) no delay file is
currently open for that airport and (b) the delay for any aircraft in the system going to that airport
exceeds the user-defined delay threshold for that airport.

A delay report file SHALL [2572] be closed for a given airport when either (a) midnight local
time occurs, or (b) no aircraft in the system going to that airport has exceeded the delay threshold
within the user-defined delay close-out time for that airport.




                                                  98                              TMA System Spec
                                                                                     FAA-E-2971
                                                                              17 December 2008
                                                                                      Final Rev N
The user SHALL [2573] be able to print out any one of the stored delay report files, including
data from a delay period currently in progress.

Delay report files for the current day and 15 past days SHALL [2574] be stored for archival
purposes.

A delay report file SHALL [2576] consist of the following sections in the given order:
   a. Header information.
   b. Individual reportable delays and summary statistics for pre-defined subsets of operations.
   c. Summary statistics across all operations.
   d. Delay summary table for all operations.
   e. Cumulative statistics.

The delay report file header information SHALL [2578] include:
   a. Time and date of printing.
   b. Name of file.
   c. Identification of data contents.
   d. Date on which data were recorded.
   e. A field labeled “Start Time” which contains the CTAS MF ETA for the first aircraft with
      a reportable delay.
   f. A field labeled “Stop Time” which contains the last actual CTAS meter fix/meter fix arc
      crossing time for the last aircraft with a reportable delay.
   g. Space designated for employee initials.
   h. Column headers for the delay data.
   i. User-specified cause of the delay.
   j. User-entered comments for the delay period.

Each individual reportable delay SHALL [2582] be given in one row of information containing
five items: the flight identifier, arrival CTAS meter fix/meter fix arc, CTAS MF ETA, last actual
CTAS meter fix/meter fix arc crossing time, and actual arrival delay. The times of arrival
SHALL [2584] be rounded to the nearest minute, but delays (displays in minutes) are calculated
from non-rounded times. Within each set of individual reportable delays (i.e., for pre-defined
subsets of operation), entries SHALL [2586] be sorted by actual CTAS meter fix/meter fix arc
crossing time.

The summary statistics for each subset of operations SHALL [2588] include four items: total
minutes of delay, number of aircraft, average minutes of delay, and maximum delay time for a
single aircraft.




                                                99                            TMA System Spec
                                                                                      FAA-E-2971
                                                                                17 December 2008
                                                                                       Final Rev N
The delay summary table SHALL [2592] include three columns, one for the delay level, (e.g.,
+15), another for the operational start time, and another for the stop time. Each row of the delay
summary table SHALL [2594] contain data for each change in the delay level during the delay
reporting period.

The following cumulative statistics SHALL [2596] be printed for all the delays, regardless of
type of operation: cumulative minutes of delay, number of aircraft with reportable delays, and
detailed information for the aircraft with the maximum delay in that period. For the aircraft with
the maximum delay in that period, the following information SHALL [2598] be given: its call
sign, airport of origin, destination airport, and minutes of delay.

The following requirements have been deleted: 2550, 2551, 2552, 2553, 2554, 2555, 2560,
2570, 2580, 2590, 2600, 2610, 2620, 2630, 2631, 2632, 2633, 2634, 2635, 2636, 2637, 2638,
2639, 2640, 2650, 2660, 2661, 2662, 2663, 2664, 2665, 2666, 2667, 2668, 2669, 2670, 2671,
2672, 2673, 2674, 2675, 2676, 2677, 2678, 2679, and 2680.

Requirements 2690, 2691, 2692, 2693, 2694, 2695, 2696, 2697, 2698, 2699, 2700, 2701, 2702,
2703, 2704, 2705, 2706, 2707, 2708, 2709, 2710, 2711, 2712, 2713, 2714, 2715, 2716, 2717,
2718, 2719, and 2720 were deleted from this document and moved to the TMA Build 2 CHI
Requirements Specification.

3.2.3.3 Display Definition

Requirements 2730, 2731, 2732, 2733, 2734, 2735, 2736, 2737, 2738, 2739, and 2740 have been
deleted from this document and moved to the TMA Build 2 CHI Requirements Specification.

3.2.3.4 Parameter Interaction

TMA SHALL [2750] if authorized by the site adaptation on a GUI by GUI basis provide TMCs
the capability to issue the following commands to TMA (Site Adaptable Installation Data):
    a. Designate/remove an aircraft as priority.
   b. Suspend/resume aircraft scheduling.
   c. Resequence aircraft routed over the same feeder gate in the sector metering list.
   d Change airport acceptance rate effective at an entered time.
   e. Cancel pending airport acceptance rate change.
   f. Cancel pending airport/runway configuration change.
   g. Create/remove a blocked interval.
   h. Insert/remove a blocked time slot.
   i. Assign departure release time to an internal departure aircraft.
   j. Cancel pending feeder gate acceptance rate change.
   k. Group traffic flow based on engine class into a stream class. {subrequirement 2750k is
      deferred}


                                               100                             TMA System Spec
                                                                                   FAA-E-2971
                                                                             17 December 2008
                                                                                    Final Rev N
l. Group traffic flow based on aircraft feeder gate crossing altitude into a stream class.
m. Combine two or more stream classes into a super stream class.
n. Change stream class Miles-in-Trail separation effective at an entered time.
o. Cancel pending stream class Miles-in-Trail separation change.
p. Change the airport/runway configuration effective at an entered time and continuing.
q. Reschedule an aircraft (i.e., assign STA to an aircraft).
r. Reset an aircraft scheduling (i.e., erases all scheduling information except the last track
   data and flight plan information and the aircraft is scheduled as though for the first time).
s. Change runway threshold acceptance rate effective at an entered time.
t. Cancel pending runway flow constraints change.
u. Change an aircraft’s feeder gate for a particular aircraft.
v. (subrequirement deleted)
w. Change aircraft feeder gate assignment for all aircraft to fly over a particular fix,
   waypoint, or feeder gate starting immediately.
x. Change aircraft feeder gate assignment for all aircraft to fly over a particular fix,
   waypoint, or feeder gate starting at an entered time in the future and continuing.
   {subrequirement 2750x is deferred}
y. Change Scheduling Meter Fix acceptance rate effective at an entered time.
z. Cancel pending Scheduling Meter Fix acceptance rate change.
aa. Change the CTAS Meter Fix for a particular aircraft.
bb. Change the CTAS Meter Fix for all aircraft to fly over a particular fix, waypoint, or
    feeder gate starting immediately.
cc. Change the CTAS Meter Fix for all aircraft to fly over a particular fix, waypoint, or
    feeder gate starting at an entered time in the future and continuing.
dd. Set Scheduling Meter Fix to meter using Miles-in-Trail separation, meter using time-
    based separation, or free flow arrival aircraft.
ee. (subrequirement deleted)
ff. Change the runway assignment for a particular aircraft.
gg. Change the runway assignment for all aircraft flying over a particular fix or waypoint.
hh. Change runway threshold separation effective at an entered time.
ii. Change runway threshold separation buffer effective at an entered time.
jj. Change runway occupancy time effective at an entered time.
kk. Freeze the STA of an aircraft.
ll. Change the eligibility criteria for ETA generation, track update processing, and
    scheduling (i.e., number of minutes from TMA adapted airport). {subrequirement 2750ll
    is deferred}
mm.Turn on or off meter data display by Center in which data is to be displayed.


                                             101                              TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N
   nn. Change the status of the use of EDCTs to an arrival airport
   oo. Change the departure runway for a particular internal departure.



TGUI SHALL [2752], if enabled in adaptation, display a confirmation dialog when the TMC
enters a command to have multiple aircraft:
    a. rescheduled,
   b. assigned to a runway,
   c. allocated new runways,
   d changed to a different meter fix, or
   e. changed to a different CTAS meter fix.

Requirement 2760 has been deleted.

TGUI SHALL [2765] provide a visual indication when a manually scheduled internal departure
does not depart within a site adaptable user preference time interval.

Semantic feedback is the feedback response from the system to a TMC-issued message. The
time measurement for semantic feedback starts from the completion of the syntactic feedback to
the moment that the results from the message processing are either (1) completed, and a
completion indication is sent back to the originator, or (2) to the moment that the message or
control signal is passed on to non-TMA equipment (for situations that do not require a
completion indication).

Requirements 2770 and 2780 have been deleted.

TMA SHALL [2790] provide semantic feedback, e.g., new STAs on the screen, in response to
TMC-entered:
  a. Schedule constraints with a mean response time of 3 seconds or less, a 99th percentile
     response time of 5 seconds or less, and a maximum response time of 10 seconds or less,
     and
   b. Configuration changes with a mean response time of 15 seconds or less, a 99th percentile
      response time of 25 seconds or less, and a maximum response time of 30 seconds or less.

These response times SHALL [2794] be met at loads and flight characteristics up to the limits
specified in 3.2.1.1 “Inputs and Outputs for TMA”.

Requirement 2795 has been deleted.

The response time for multiple schedule constraints or configuration changes SHALL [2796] be
measured from the time at which the preceding request is completed.



                                               102                           TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.2.3.5 Data Retrieval (deleted)

Requirements 2800, 2801, 2802, 2803, 2804, 2805, 2806, 2807, 2808, 2809, 2810, 2811, 2812,
2813, 2814, 2815, 2816, 2817, 2818, 2819, and 2820 have been deleted.

3.2.3.6 Display Interaction (deleted)

Requirement 2830 has been deleted.

3.2.4 Monitor & Control

Note: RPR-159 replaced all of section 3.2.4. Several requirements that had been moved to this
section by RPR-055 were moved by RPR-159 to section 3.1. Within section 3.2.4, RPR-159
superceded RPRs 001, 018, 055, 086, 087, 110, and 155.

The M&C function provides centralized system management of the Operational System. It
manages the computational assets of the Operational System. This includes the allocation of
software functions to hardware, initiation and termination of functions, and the collection of
status information pertaining to computer resources and software functions. The above listed
functionality is considered control of these local hardware and software assets.

The M&C function monitors and displays computer resource utilization information
(e.g., Central Processing Unit (CPU), memory, etc.). In addition, the M&C SHALL [2835]
generate visual and audible alarms when thresholds are exceeded. The auditory alarm SHALL
[2833] repeat until it is acknowledged by the M&C operator. It provides fault detection and
recovery when resource problems arise. It monitors the status of TMA processes and manages
initialization, failure recovery and shutdown of these functions. The M&C function also includes
event logging. The above listed functionality is considered a local monitoring capability.

The M&C SHALL [2834] use the colors green, yellow, red and off-white exclusively to indicate
the status of hardware and software through icons on the M&C display. Green SHALL [2836]
represent software and hardware running normally as expected including running in standby.
Yellow SHALL [2837] indicate a degraded condition in the software or hardware represented.
Red SHALL [2838] indicate a failure. An off white color SHALL [2839] indicate an item that
has been administratively turned off (software) or not monitored (hardware).

Each M&C functional group has the ability to monitor hardware and software at other connected
sites beyond the particular facility. This functionality is considered a remote monitoring
capability.

The M&C functional group will monitor and control all the local hardware and software. Note
that there will be a single M&C functional group at each facility. Facility is defined to include:
ARTCC, TRACON, and Towers.




                                                103                             TMA System Spec
                                                                                 FAA-E-2971
                                                                            17 December 2008
                                                                                  Final Rev N
Note that the Operational System can be comprised of the following groups: Data Processing,
User I/O (Displays), and Data I/O (Host interfaces, TRACON automation interfaces, etc.).

All Hardware and Software control SHALL [2841] be accomplished locally at each facility by a
single M&C function group.

Upon request or status change, the M&C function SHALL [2842] have the capability of
transmitting information to the MPS. {Requirement 2842 is deferred}

The M&C function SHALL [2843] have the ability to control all functional groups of Data
Processing, User I/O, and Data I/O independently.

The M&C function SHALL [2844] have the ability to control all User I/O and Data I/O in:
   a. An associated control tower.
   b. An adjacent facility.

All hardware (workstation and networks) anywhere in the overall system (excluding the HCS,
ETMS and TRACON Automation) SHALL [2846] be capable of being monitored by user tools
taking advantage of the SNMP protocol.

All software anywhere in the overall system (excluding the HCS, ETMS and TRACON
Automation) SHALL [2847] be capable of being monitored by using the SNMP protocol with
the construction of the necessary Management Information Bases (MIBs), agents and proxies.
(See RFC 1098, SNMP version 2).

TMA SHALL[2852] be capable of communicating, in one way or two way mode, to Host
Computer Systems via either; HADDS directly, or through a Multi-Metering Gateway (MMG).

TMA SHALL [2853] have Monitor and Control functionality to independently configure,
monitor and control connections to multiple Centers’ Hosts.

When MMG is running under M&C control, TMA SMC SHALL [2854] control the MMG under
the software category of HADDS and start the MMG independently of the rest of TMA.

TMA SHALL [2855] be capable of connecting to an MMG running in stand alone mode (not
under M&C control).




                                             104                           TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
3.2.4.1 Inputs & Outputs

The inputs to the M&C function are identified in Table 3.2.4.1-1.
                         Table 3.2.4.1-1.       M&C Function Inputs
     Input                                  Description
     Configuration data                     Hardware & software configuration data
     SMC entries                            SMC entries
     Status data                            Status from application functions
     Operating environment signals          Hardware and software failure
     (operating system, SNMP, etc.)

The outputs of the M&C function are identified in Table 3.2.4.1-2.

                         Table 3.2.4.1-2.      M&C Function Outputs
      Output                    Description
      SMC display data          SMC displays
      Control data              Control data messages to, e.g., start, stop, recover, etc.,
                                sent to application functions
      Status data for the MPS   High level system information and major events and alerts
      SNMP messages             System information for remote SNMP management station


The local interface SHALL [2850] provide for the M&C function a graphical display and input
capability via mouse/trackball and/or keyboard for monitor and control.

3.2.4.2 Monitoring

The M&C function SHALL [2880] monitor and report at a minimum (but is not limited to) the
following:
    a. Overall system status and status changes.
   b. Hardware component availability.
   c. Software component status.

The M&C SHALL [2882] present the status of TMA nodes (node level view) of the operations
network within the ARTCC (computers, printers, modems) in a single presentation to facilitate
the ability to 'monitor at a glance.' The M&C SHALL [2884] present switches, routers, and
networks on a top-level map that can coexist with this node-level view on a M&C monitor
display. Thus, more than one open window may be presented simultaneously to satisfy this
requirement.




                                               105                            TMA System Spec
                                                                                    FAA-E-2971
                                                                              17 December 2008
                                                                                     Final Rev N
M&C icons for software and hardware maps and submaps SHALL [2886] flash to indicate that a
failed or degraded condition has occurred that the M&C operator needs to know about or take
action in response to. The icon(s) so affected SHALL [2888] continue to flash until
acknowledged by the M&C operators. This flash coding includes icons that have turned green
due to software failover or reintroduction of a previously failed component which has been
repaired.

The M&C function SHALL [2890] recognize and present alarm and alert conditions. Alarm
conditions are defined as any condition when a subsystem parameter is outside of an acceptable
operating range. Alert conditions are defined as any condition when a subsystem parameter is
outside of normal operating range but within an acceptable operating range.

The M&C workstation SHALL [2891] issue a repeating audible alarm under the following
conditions enumerated under both the "Hardware-related" and "Software-related" sections.

   Software-related:
   a. Application has exited ungracefully from OpenView (ovw). This indicates an M&C
      failure
   b. TMA has gone to a reduced state or has transitioned off due to a fatal error
   c. ADIF, EDIF or MMG has failed
   d. TMA interface to ARTS/STARS, ETMS, Host, or Weather has failed

   Hardware-related:
   e. Status of a node has become down (unable to elicit response from node)
   f. Status of a network has become critical or major
   g. Status of a network segment has become critical or major
   h. Status of a node has become unknown (typically due a connector failure)

This alarm SHALL [2893] require a manual acknowledgement at the M&C to terminate it.

Failure to receive a weather update SHALL [2892] cause a notification to be displayed to the
TMC. Restoration of the weather service SHALL [2894] also cause a notification to be sent to
the TMC. In both cases, a popup window is sufficient notification. Once acknowledged, the
popup window is removed.

TMA SHALL [2895] display weather status by the use of an independent icon. This icon SHALL
[2897] display weather status on the M&C console, using the following color code:
   a. Green - Current weather file is in use.
   b. Yellow - 75 minutes (one cycle) has passed without a weather update.
   c. Red - 150 minutes (two cycles) have passed without a weather update.




                                              106                             TMA System Spec
                                                                                 FAA-E-2971
                                                                           17 December 2008
                                                                                  Final Rev N
TMA SHALL [2899] display the time, date, and format of the current weather file.

Loss of a remote data feed SHALL [2896] cause a notification to be displayed to the TMC.
Appearance and clearance of a big X on the TGUI display SHALL[2919] cause notification to be
displayed to the TMC.

Requirement 2898 has been deleted.

The M&C function SHALL [2900] provide for operator input to effect dynamic change to the
subsystem parameter settings.

M&C SHALL [2905] display the status of CAP.

M&C SHALL [2906] provide the capability to start up and/or shutdown CAP.

M&C SHALL [2903] display the identity of all connected CAP clients.

TMA SHALL [2902] rollback to the previous weather file, if distribution of the current weather
file to any weather-aware processes except PGUI is not successful.

Weather file distribution failure SHALL [2904] cause a notification to be displayed to the TMC
to indicate which PGUI(s) are not displaying the latest weather.


3.2.4.3 Control

The M&C function SHALL [2910] provide for the local start/stop and function or task allocation
and the capability to do this remotely for:
   a. Control towers.
   b. Adjacent facilities.

The M&C SHALL [2911] have the functional ability to startup and/or shutdown individual
members of the GUI group and the Remote GUI group.

The M&C function SHALL [2915] provide for operator input to modify the System
Configuration Data.

This allows an operator to modify the available processing components and the functionality
allocated to each processing component. These configuration changes become effective upon
system restart. Additionally, modifications to the System Configuration Data can only be made
by an authorized user as outlined by the Security Requirements in Section 3.8.

The controlling M&C SHALL [2912] provide a control capability to enable or disable developer
debug code by an authorized M&C user. It SHALL [2913] not be necessary to shut down or


                                              107                            TMA System Spec
                                                                                   FAA-E-2971
                                                                             17 December 2008
                                                                                    Final Rev N
reboot TMA or the affected GUIs to make or use these selections while the operational system
continues to run normally. The M&C SHALL [2914] issue enable/disable directives to either the
PGUI or TGUI. The M&C SHALL [2916] have the ability to issue enable/disable directives to a
single TGUI or PGUI or multiple TGUIs/PGUIs. To prevent inadvertent activation in the enabled
mode, debug and research code SHALL [2918] be accessed through M&C menu items. The
specific PGUI and/or TGUI will reflect the selected enabled/disabled mode.

The M&C SHALL [2908] be able to configure a controlling or non-controlling GUI. The M&C
SHALL [2907] be able to specify the facilities (e.g., specific Host, TRACON) that a TGUI is
assigned to.

The M&C SHALL [2909] be able to specify the alert dialogs that will be shown on a TGUI.

M&C SHALL [2917] restart CAP upon failure. Upon restart, CAP clients will be able to
reconnect to CAP.

M&C SHALL [2942] provide the capability to disconnect and block CAP clients from
connecting, and to remove blocks for CAP clients.


3.2.4.4 Diagnostics

The M&C function SHALL [2920] provide internal diagnostic capability for fault isolation.

The TMA SHALL [2921] provide a capability for enhanced diagnostic capabilities within the
Operations String and within the Support String through the M&C subsystem for authorized
M&C Operator and System Administrators. Within the M&C subsystem, simple icon or menu
selections SHALL [2922] be used in areas of diagnostics, start and set up, and obtaining detailed
status information as follows:

Diagnostics

       a. Execute scripts. The M&C SHALL [2923] provide the capability to execute a script
           on a menu list of scripts from an appropriately designated directory that includes
         1. A script that provides system uptimes, and
         2. Scripts to search for and provide core files from all boxes. M&C SHALL [2829]
         provide the capability to copy selected core files to the M&C box for manual archive by
         the M&C Operator.


       b. Remote screen information. The M&C SHALL [2924] provide the capability to
          access and display the current screen display from another box through a selection of
          the box name and, as necessary, the specific display device (in the case of dual GUIs).
          The M&C keyboard SHALL [2929] have a print screen capability.


                                               108                            TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

Start and Set Up

         c. Easy reboot. The M&C SHALL [2925] provide the capability to optionally reboot all
            boxes on a string or just the GUI boxes ( the M&C boxes are excluded). By way of
            example, just the GUI boxes could be rebooted.

         d. Simplified Start of OpenView GUI. The M&C SHALL [2926] provide an icon on
            the M&C that invokes the OpenView GUI.

         e. Help for Command Line Arguments. The M&C SHALL [2927] provide, as a Help
            option associated with the manual configuration process, a list of supportable
            command line arguments.

         f. Quick recovery for timed-out boxes. The M&C SHALL [2928] provide a capability to
            quickly recover any box that has been timed out (deleted from) of Open View.

Status

         g. Host interface status. The M&C SHALL [2931] provide on the M&C Software Sub-
            system map an indication of the status of the HADDS-HID NAS LAN connection and
            of the HDIF - HADDS connection status in terms of Two Way, or One Way modes,
            or a Down status. The capability of putting the TMA in a Two Way mode is now in
            the TGUI and affects the CM to HDIF two way connection. This functionality control
            SHALL [2932] be moved to the controlling M&C GUI.

         h. System CIDS load status. The M&C SHALL [2933] provide a capability to display a
            status panel that indicates the numbers of radar CIDS and how many have
            corresponding Flight Plans.

         i. Capability to determine the ARTS data feed status. The M&C SHALL [2934] provide
            a capability to easily confirm the ARTS feed to the TMA by adding an ARTS feed
            count to the existing traffic count capability.

         j.    The M&C SHALL [2936] display the currently configured software version and
              adaptation version. The M&C SHALL [2937] also display a list of each process ID's
              command line arguments.

         k.   For each active Center interface, the M&C SHALL [2946] display the system type
              (Host or ERAM) in use at that Center. For each active interface to a Center at which
              ERAM is in use, the M&C SHALL [2947] also display the ERAM version ID.

         l.   Capability to determine the ETMS data feed status. The M&C SHALL [2948]
              provide a capability to confirm the ETMS feed to the TMA.



                                                 109                            TMA System Spec
                                                                                 FAA-E-2971
                                                                            17 December 2008
                                                                                  Final Rev N
M&C function local and/or remote execution and reporting of diagnostic procedures SHALL
[2930] be provided. The M&C SHALL [2935] provide the capability to health check computers,
routers, and switches before they are brought up into the system.


Diagnostics SHALL [2940] identify the Line Replaceable Unit (LRU) of a failed or degraded
component whenever possible and provide visual and hard copy diagnostic data for fault
isolation analysis.

M&C Sub-system panel icons SHALL [2943] be location coded and not movable.


3.2.4.5 Maintenance of System Log

The M&C function SHALL [2950] maintain an event log recording that contains alarms, alerts,
function errors, software component status, system status changes, and manually entered system
configuration changes.

Major alarms that require attention SHALL [2952] now be red in color, normal events SHALL
[2953] be either green or off white, and others SHALL [2954] be yellow.

The M&C function SHALL [2960] time-stamp all system log entries with the system
Coordinated Universal Time.

Operator actions at the M&C GUI SHALL [2963] be logged to the Alarm Browser in such a way
as to clearly distinguish them from other "system-generated" messages, providing a clear
indication of the actions taken by the M&C operator.

M&C SHALL [2865] create a Log entry in the Alarm Browser whenever the OpenView "ovw"
GUI is shutdown.

According to the current version of M&C, M&C SHALL [2867] create log entries for the
following operator's action:
    a. Start up a software (TMA, MMG, EDIF and ADIF)
   b. Shut down a software (TMA, MMG, EDIF and ADIF)
   c. Switch other M&C to Primary
   d. Turn audio on
   e. Turn audio off
   f. Initialize Manual Configuration GUI
   g. Initialize Data Recording GUI
   h. Data Recording control changes
   i. Exit OpenView


                                             110                             TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N

The M&C function SHALL [2970] provide the ability to display the system log.

The M&C function SHALL [2980] provide the ability to print the system log.

The M&C function SHALL [2990] preserve the system log files for a minimum of 48 hours.

The following requirements have been deleted from section 3.2.4 by RPR-159: 2840, 2845,
2848, 2860, 2870, and 2995.

3.2.5 Data Management (DM) (deleted)

Requirements 3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012,
3013, 3014, 3015, 3016, 3017, 3018, 3019, 3020, 3021, 3022, 3023, 3024, 3025, 3026, 3027,
3028, 3029, 3030, 3031, 3032, 3033, 3034, 3035, 3036, 3037, 3038, 3039, 3040, 3070, 3071,
3072, 3073, 3074, 3075, 3076, 3077, 3078, 3079, 3080, 3081, 3082, 3083, 3084, 3085, 3086,
3087, 3088, 3089, 3090, 3091, 3092, 3093, 3094, 3095, 3096, 3097, 3098, 3099, 3100, 3101,
3102, 3103, 3104, 3105, 3106, 3107, 3108, 3109, 3110, 3111, 3112, 3113, 3114, 3115, 3116,
3117, 3118, 3119, 3120, 3121, 3122, 3123, 3124, 3125, 3126, 3127, 3128, 3129, 3130, 3131,
3132, 3133, 3134, 3135, 3136, 3137, 3138, 3139, 3140, 3141, 3142, 3143, 3144, 3145, 3146,
3147, 3148, 3149, 3150, 3151, 3152, 3153, 3154, 3155, 3156, 3157, 3158, 3159, 3160, 3161,
3162, 3163, 3164, 3165, 3166, 3167, 3168, 3169, 3170, 3171, 3172, 3173, 3174, 3175, 3176,
3177, 3178, 3179, 3180, 3181, 3182, 3183, 3184, 3185, 3186, 3187, 3188, 3189, 3190, 3191,
3192, 3193, 3194, 3195, 3196, 3197, 3198, 3199, 3200, 3201, 3202, 3203, 3204, 3205, 3206,
3207, 3208, 3209, and 3210 have been deleted. All references to DM in this specification have
been expunged.

3.2.6 Adaptation, Validation, and Analysis

TMA provides an adaptation maintenance toolset which executes independently from the
operational TMA capabilities and supports the maintenance associated with an existing site
adaptation (i.e., chart change updates).

TMA SHALL [3225] provide site independent software processes and site dependent adaptation
data files that conform to the TMA Adaptation/Software Interface Control Document.

Requirements 3220, 3230, 3231, 3240, 3245, 3250, 3251, 3252, 3253, 3254, 3255, 3260, and
3270 have been deleted.

The subsections under Section 3.2.6, including Table 3.2.6.1.1-1 and Requirements 3280, 3290,
3300, 3310, 3320, 3321, 3322, 3330, 3340, 3350, 3360, 3362, 3365, 3366, 3370, 3380, 3390,
3400, 3410, 3420, 3425, and 3430 have been deleted.




                                              111                            TMA System Spec
                                                                                  FAA-E-2971
                                                                             17 December 2008
                                                                                   Final Rev N

3.2.7 Data Analysis and Testing

The Adaptation Maintenance Toolset SHALL [3440] conform to the CTAS Data Recording
Interface Control Document.

The TMA software SHALL [3442] conform to the CTAS Data Recording Interface Control
Document.

TMA SHALL [3449] provide the capability to record analysis data for use in offline data analysis
and playback.

TMA SHALL [3451] provide a user initiated capability to display the following information for
an aircraft:
        a. Aircraft Enhanced ID
        b. Data sources in use
        c. Flight Plan
        d. Track data information
        e. STA information
        f. RA generated ETAs, process, and times to each runway
        g. Analysis category
        h. Route segment category
        i. Scheduler freeze information
        j. Route area (TRACON, CENTER, CENTER_TRACON)

Requirements 3450, 3460, 3470 have been deleted.

TMA SHALL [3474] provide analysis data in an adaptation independent format.

TMA SHALL [3475] provide analysis data in a coordinate reference frame independent format.

TMA SHALL [3476] provide the capability to produce human readable reports of all recorded
data.

TMA SHALL [3478] provide the capability to record the aircraft airspeed associated with each
aircraft state update.

TMA SHALL [3479] provide the capability to record the aircraft Mach number associated with
each aircraft state update.

Requirement 3480 has been deleted.

TMA SHALL [3481] record the system start time including the TMA computer time, day, and
date.


                                              112                            TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

TMA SHALL [3482] include version number identifiers in all output files to support output file
and tool compatibility.

TMA SHALL [3483] update the version number for an output file whenever the format of the
output file changes or new output capabilities are added to the output file.

TMA SHALL [3484] provide the capability to output the command line options used for each
process.

TMA SHALL [3486] provide a data analysis capability to report diversions over a user defined
period not to exceed 15 days. {Requirement 3486 is deferred}

TMA SHALL [3488] be capable of testing new software or adaptation by communicating with a
TESTNAS running on the backup Host processor in two-way mode. {Requirement 3488 is
deferred}

3.2.8 Playback

TMA SHALL [3490] provide a Playback capability which executes independently from the
operational TMA, reading HCS, ETMS, and TRACON Automation data previously recorded by
the operational TMA, and provides the ability to exercise all of the functions of the operational
TMA.

TMA SHALL [3492] provide a Basic playback capability to replay all previously recorded
external flight plan and track data. TMA SHALL [3493] allow the playback operator to perform
TMA operator inputs (e.g., TGUI, PGUI, Wx file in use, …) in Basic playback mode.
{Requirements 3492 and 3493 are deferred}

TMA SHALL [3494] provide a Complete playback capability to replay all previously recorded
external input data (e.g., Host, ARTS sources) and all of the TMA operator inputs (e.g., TGUI,
PGUI) that impact the scheduler. TMA SHALL [3495] allow the playback operator to perform
TMA operator inputs (e.g., TGUI, PGUI, Wx file in use, …) in Complete playback mode.
{Requirements 3494 and 3495 are deferred}

TMA SHALL [3496] provide a Movie playback capability to replay all previous recorded
external input data (e.g., Host, ARTS sources), all TMA operator inputs ( e.g., TGUI, PGUI) that
impact the scheduler, and all schedule/advisory information (ETAs, STAs, and runway
assignments). TMA SHALL [3497] not allow any TMA operator inputs that would impact the
schedule in Movie playback mode. {Requirements 3496 and 3497 are deferred}

The Playback SHALL [3500] provide the capability for setting system time to “recorded” instead
of actual time of day for the duration of the playback.




                                               113                             TMA System Spec
                                                                                           FAA-E-2971
                                                                                     17 December 2008
                                                                                            Final Rev N
TMA Playback SHALL [3505] allow for the introduction of simulated aircraft with full user
control over aircraft properties (i.e., type, flight plan, meter fix,…) and state (i.e., position,
velocity, heading,…)

TMA SHALL[3501] provide a playback capability that allows for the start time associated with
the playback to be different from the start of the associated playback file while maintaining all
pertinent information to result in a valid playback at the designated start time. {Requirement
3501 is deferred}

TMA SHALL[3502] provide a playback capability that allows for the playback clock to be a
dynamic user selection that is faster than realtime. {Requirement 3502 is deferred}

TMA SHALL[3503] provide a playback capability that allows for the playback clock to be a
dynamic user selection that is slower than realtime. {Requirement 3503 is deferred}

TMA Playback SHALL [3507] treat simulated aircraft identical to aircraft received from the
HCS or TRACON data interfaces.

3.2.9 Simulation

TMA SHALL [3510] provide a Simulation capability, such as the Pseudo Aircraft Simulator
(PAS) which can exercise the Operational TMA in a laboratory environment.

The TMA Simulation capability SHALL [3509] be capable of running Host Dysim on the TMA
support string simultaneously with the operational TMA running on the Operational string.

3.2.10 Support Subsystem

TMA SHALL [3511] support an on-site support subsystem capability that can operate on a live
data feed in a one-way only mode. There SHALL [3512] be at most one such subsystem per full
TMA operational TMA installation.

This on-site support subsystem SHALL [3513] support the capabilities of the operational TMA
which are necessary to validate new site specific software and adaptation releases (excludes
M&C functionality for example). The support subsystem SHALL [3514] support all TMA
external system interfaces.

The support subsystem SHALL [3515] be subject to maximum site load requirements of the
operational TMA but SHALL NOT [3516] be subject to operational system availability
requirements. The support subsystem SHALL [3517] be subject to the same security and privacy
requirements as the operational TMA.

The support subsystem SHALL [3518] be capable of operating concurrently with the operational
TMA, using the same live data, without adversely impacting the operational TMA.



                                                 114                              TMA System Spec
                                                                                     FAA-E-2971
                                                                              17 December 2008
                                                                                      Final Rev N
The support subsystem SHALL [3519] have sufficient connectivity to the operational system to
allow electronic transfer of software and adaptation from the support subsystem to the
operational system.

The TMA Build 2 system SHALL [3521] be designed such that a support subsystem can be
installed and run at a site whether or not an operational system is also installed. The TMA Build
2 system SHALL [3522] be designed such that an operational system can be installed and run at a
site whether or not a support subsystem is also installed.

Requirement 3523 has been deleted. The support subsystem will be designed such that it can
support an on-line data analysis capability.

The TMA Build 2 system SHALL [3524] be designed such that connection of data feeds will
NOT interfere with the operational system or support subsystem.

The support subsystem SHALL [3525] have the ability to host a remote GUI.

Requirement 3526 has been deleted.

TMA support string SHALL [3527] be designed to allow the support string to be configured to
automatically acquire the current raw weather file from the operational string.

3.2.11 Weather Interface

TMA SHALL [3535] use the following weather data elements from the primary data - RUC
weather data:
   a. u-winds
   b. v-winds
   c. temperature
   d. geopotential height
   e. barometric pressure at sea level


TMA SHALL [3536] use the following weather data elements from the secondary data - Eta
weather data:
   a. u-winds {subrequirement 3536a is deferred}
   b. v-winds {subrequirement 3536b is deferred}
   c. temperature {subrequirement 3536c is deferred}
   d. geopotential height {subrequirement 3536d is deferred}
   e. barometric pressure at sea level {subrequirement 3536e is deferred}

TMA SHALL [3537] be capable of:
  a. determining when the designated primary source of weather data is unavailable.
  b. receiving weather from multiple sources.



                                              115                             TMA System Spec
                                                                                     FAA-E-2971
                                                                              17 December 2008
                                                                                       Final Rev N
      c. switching among available weather data sources to obtain weather data until it determines
         the primary is available.
      d. obtaining and converting Eta data to RUC GRIB format if RUC data is unavailable.
         {subrequirement 3537d is deferred}

3.3      System External Interface Requirements

3.3.1 Interface Identification and Diagram

The external interfaces for a generic TMA installation are shown in Table 3.3.1-1. Included is the
applicable reference for each interface.

                           Table 3.3.1-1. Required External Interfaces

      Category                                Description/Reference         ID        Section
      HOST                                    Reference in Table 2-6
       HID/LAN Interface                       HOST messages                HID   3.3.2
      TRACON Interfaces                       Reference in Table 2-7              3.3.3
       ARTS Gateway                            ARTS II-E messages           AGW   3.3.3.1
       ARTS Gateway                            ARTS III-E messages          AGW   3.3.3.1
       STARS Interface                         STARS messages               STARS 3.3.3.2
       ARTS III-A Interface                    ARTS III-A messages          ADG   3.3.3.3
      ETMS Interface                          Reference in Table 2-8        ETMS 3.3.4
      Adjacent Facility Data I/O Interfaces   Reference in Table 2-1              3.3.5
       Adjacent Center Data I/O                TMA internal format          ACD   3.3.5.1
       Adjacent TRACON Data I/O                TMA internal format          ATRD 3.3.5.2
      Adjacent Facility User I/O Group        Reference in Table 2-1              3.3.6
       Adjacent Center User I/O                TMA internal format          ACG   3.3.6.1
       Adjacent TRACON User I/O                TMA internal format          ATRG 3.3.6.2
        Tower User I/O                         TMA internal format          ATWG 3.3.6.3
      ARTCC Maintenance Control Center        Reference in Table 2-3
         CTAS/AMCC Interface                    CTAS/AMCC IRD               AMCC 3.3.7
      WARP Interface                          Reference in Table 2-9
         RUC Weather Date                       WMO GRIB format             WMX       3.3.10
      Time Synchronization                    Reference in Table 2-10
                                                Time Sync format            TBD       3.3.11
      TRACON Passive Feed Interface           Reference in Table 2-1
                                                TMA internal format         TPFI      3.3.12
      CAP Tool                                Reference in Table 2-12       CAP       3.3.13

Figure 3.3.1-1 depicts how these external interfaces are connected for generic Center and
TRACON TMA Installations.


                                                116                              TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N

The principal interface in every TMA installation is the Data I/O Group, which connects to the
Host in the Center installation or to ARTS in the TRACON installation. The same Data I/O
group interfaces to ETMS in both types of installations. Other interfaces in the Center
installation are the interface of M&C to the ARTCC Maintenance Control Center (AMCC) and
interfaces of TMA to Adjacent Facility Data I/O Groups, the interface of WARP to the Data I/O
Group, and the interface of Time Synchronization to the Data I/O Group. Other interfaces in the
TRACON installation are one-way interfaces between the Data I/O Group and up to twelve (12)
other TMA installations.

      INTERFACES FOR GENERIC TMA INSTALLATION
                            AMCC

                                             Adjacent Facility
                                                                                     ARTS/
                     Center TMA                                     TRACON TMA       STARS
   TIME SYNC                                            TMA
      CREWS
        ETMS
           HOST      M&C                      M&C




                     DATA                    DATA                    DATA
                      I/O                     I/O                     I/O

    CAP TOOL

                     DATA                    DATA
                     PROC                    PROC




                     USER                    USER                    USER
                      I/O                     I/O                     I/O




                                             USER
                                              I/O

                                      TOWER INSTALLATION




Figure 3.3.1-1. Diagram of Interfaces for Generic TMA Installations

The Data I/O Group in a Center installation consists of all the hardware and software necessary
to perform two way communication with a single Host HID; it includes all the hardware and
software necessary to send data to a single Host HID, and to receive and distribute data from the
same Host. Software to select data to be sent to other functional groups within TMA is included


                                                117                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
in this functional group. The Data I/O group also interfaces to ETMS in some cases, to provide
flight plan (FP) and track data from adjacent facilities which do not have any TMA equipment
(with Data I/O groups) installed. The Data I/O Group in a Center installation also interfaces to
WARP to provide Weather Data.

ARTS data may be required by TMA to schedule Tower EnRoute Control (TEC) flights (for
example in LAX).

The Data I/O Group in a TRACON Installation consists of all the hardware and software
necessary to perform one-way communication with a single TRACON system (via either an
ARTS Gateway to an ARTS II-E or an ARTS III-E, an interface to ARTS III-A, or a connection
to STARS ); it includes all the hardware and software necessary to receive and distribute data
from the single TRACON system. Software to select data to be sent to other functional groups
within TMA is included in this functional group.

The Data I/O group in an Adjacent Facility Installation with a Data processing Group is a Center
Data Interface. An Adjacent Facility without a Data Processing Group does not have a Data I/O
group.

Observe that data exchange with the TMA Graphical User Interface (GUI), whether PGUI or
TGUI, is considered internal to TMA. The manual inputs from the Traffic Management
Coordinator (TMC) and the display capability is discussed as part of the CHI.

3.3.2 HCS Interface

This section states the requirements for the interface, referred to as HID in Table 3.3.1-1,
between the HCS and any Center TMA installation.

All information related to the Host Interface is collected in Table 2-6, especially as related to the
HID/NAS LAN. (See NAS-IR-40100001, ARTCC NAS LAN/User System IRD; and HID/NAS
LAN Integration Requirements Document).

TMA SHALL [3538] comply with the HCS IRD.

Requirements 3520, 3530, 3050, 3060 have been deleted.

3.3.3   TRACON Automation Interfaces

This section states the requirements for the interface between the TRACON automation system
and a TRACON TMA installation. This interface is referred to as either the ADG or ARTS Gate
Way (AGW) or STARS in Table 3.3.1-1.




                                                 118                              TMA System Spec
                                                                                 FAA-E-2971
                                                                            17 December 2008
                                                                                  Final Rev N
3.3.3.1 ARTS Gateway

If the TRACON system is either an ARTS II-E or an ARTS III-E, the interface is called the
AGW.

Requirement 3540 has been deleted.

TMA SHALL [3541] be capable of interfacing to the AGW for receiving flight plan and aircraft
track data.

Requirements 3542 and 3543 have been deleted.

3.3.3.2 STARS Interface

If the TRACON Automation is a STARS (currently being developed), the interface is called the
STARS interface.

Requirement 3550 has been deleted.

TMA SHALL [3551] be capable of interfacing to STARS for receiving flight plan and aircraft
track data.

Requirements 3552 and 3553 have been deleted.

3.3.3.3 ARTS III-A Interface

Requirement 3560 has been deleted.

TMA SHALL [3561] be capable of interfacing with ARTS III-A to receive flight plan and
aircraft track data.

3.3.4 ETMS Interface

This section states the interface requirements between a TMA installation and ETMS.
The overall reference for the ETMS interface is the CTAS/ETMS Interface Requirements
Document (document number to be assigned).

The interfaces are referred to as Estimated Time of Departure (ETD) for an ETMS interface
handling Center/TRACON flight plan and track data, and as EXD for the ETMS interface
handling PGUI display data being sent to ETMS in the X/Motif format.

3.3.4.1 ETMS Weather Interface

Subsection 3.3.4.1, including requirement 3570, has been deleted.



                                              119                           TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
3.3.4.2 ETMS Center/TRACON Traffic Data

The ETMS will provide Center and TRACON flight plan and track data to TMA in an ETMS
internal format as specified in the references in Table 2-8.

TMA SHALL [3571] be capable of receiving FP and track data from ETMS.

3.3.4.3 ETMS PGUI Display on TSD

The ETMS will eventually have a network connection with TMA capable of displaying a PGUI
on the Traffic Situation Display (TSD) in X/Motif format. The reference for the X/Motif protocol
is in Table 2-1.

TMA SHALL [3572] be capable of displaying a PGUI on the ETMS TSD when the TSD is
available. {Requirement 3572 is deferred.} NOTE: The Aircraft Situation Display (ASD) will
not be capable of supporting X/Motif displays until the open system conversion is complete.

Requirement 3580 has been deleted.

3.3.5 Adjacent Facility TMA Data I/O Interfaces

This section states the interface requirements between a TMA installation and an Adjacent
Facility TMA Data I/O Group that can be in either a Center or TRACON installation. The
interfaces are referred to as ACD or ATRD in Table 3.3.1-1.

3.3.5.1 Adjacent Center TMA Data I/O Interface

This section states the requirements for the interface between a Center TMA installation and any
other TMA installation. This interface is referred to as ACD in Table 3.3.1-1

Requirement 3590 has been deleted.

The Data I/O Group of an Adjacent Center Facility SHALL [3591] be capable of sending FP and
track data to the TMA in the Center.

Requirement 3592 has been deleted.

TMA SHALL [3593] be capable of receiving and processing FP and track data from the Data I/O
group of an Adjacent Center facility.

3.3.5.2 Adjacent TRACON TMA Data I/O Interface


This section states the requirements for the interface between a TRACON TMA installation and
any TMA installation. This interface is referred to as ATRD in Table 3.3.1-1.


                                              120                             TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

Requirement 3600 has been deleted.

The Data I/O Group of an Adjacent TRACON Facility SHALL [3601] be capable of sending FP
and track data to the TMA in the Center which contains that TRACON. {Requirement 3601 is
deferred.}

The Data Processing Group of TMA SHALL [3602] be capable of receiving and processing FP
and track data from the Data I/O group of an Adjacent TRACON facility. {Requirement 3602 is
deferred.}

3.3.6 Adjacent Facility User I/O Interfaces

This section states the interface requirements between a TMA installation and an Adjacent
Facility TMA User I/O Group that can be in either a Center or TRACON or Tower installation.
The interfaces are referred to as ACG or ATRG or ATWG in Table 3.3.1-1.

In general, displayed data from any connected facility can be requested and displayed locally.
Also, any keyboard entries made locally can be made to affect operations at any connected
facility. However, site adaptation will limit and circumscribe this capability (Site Adaptable
Installation Data). For example, a Tower facility could ask for the display data from the
connected TRACON TMA User I/O Group and the Center TMA User I/O group, but would
almost never be allowed to command an airport configuration change.

3.3.6.1 Adjacent Center Facility User I/O Interface

This section states the requirements for the interface between a Center TMA User I/O Group and
any TMA installation. This interface is referred to as ACG in Table 3.3.1-1.

The User I/O Group at a Center Facility SHALL [3611] be capable of issuing keyboard
commands to connected TMA facilities and displaying GDS data received from these facilities in
response.

The User I/O Group at a Center Facility SHALL [3612] be capable of receiving keyboard
commands from connected TMA facilities and providing GDS data to these facilities in response.


3.3.6.2 Adjacent TRACON Facility User I/O Interface

This section states the requirements for the interface between a TRACON TMA User I/O Group
and any TMA installation. This interface is referred to as ATRG in Table 3.3.1-1.

The User I/O Group at a TRACON Facility SHALL [3613] be capable of issuing keyboard
commands to connected TMA facilities and displaying GDS data received from these facilities in
response. {Requirement 3613 is deferred.}


                                               121                             TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N

The User I/O Group at a TRACON Facility SHALL [3614] be capable of receiving keyboard
commands from connected TMA facilities and providing GDS data to these facilities in response.
{Requirement 3614 is deferred.}


3.3.6.3 Tower TMA User I/O Interface

This section states the requirements for the interface between a Tower installation User I/O
Group and any TMA installation. This interface is referred to as ATWG in Table 3.3.1-1.

Interfaces between any TMA installation and the TOWER TMA installation is limited to GUI
display data being sent from any connected facility to the Tower.

The User I/O Group at a Tower Facility SHALL [3615] be capable of issuing keyboard
commands to connected TMA facilities and displaying GDS data received from these facilities in
response. {Requirement 3615 is deferred}

Requirements 3610, 3620, 3630, and 3640 have been deleted.

3.3.7 AMCC Interface for a Center TMA Installation

This section states the requirements for the interface between a Center TMA installation and the
Center AMCC. This interface is referred to as AMCC in Table 3.3.1-1.

Requirement 3650 has been deleted.

The TMA M&C Group in the Center SHALL [3660] interface with the AMCC as specified in
the NAS-IR-82198101, CTAS/AMCC Interface Requirements Document. {Requirement 3660 is
deferred.}

Sections 3.3.8 and 3.3.9, including requirement 3670, have been deleted.

3.3.8 [deleted]

3.3.9 [deleted]

3.3.10 WARP Interface

This section states the requirements for the interface between a Center TMA installation and a
Center Weather and Radar Processor (WARP) system. This interface is referred to as WARP in
Table 3.3.1-1. WARP will provide gridded RUC weather data to TMA in World Meteorological
Organization (WMO) Gridded Binary (GRIB) format.




                                               122                             TMA System Spec
                                                                              FAA-E-2971
                                                                        17 December 2008
                                                                               Final Rev N
A Center TMA installation SHALL [3665] be capable of receiving RUC weather data from
WARP as specified in the WARP to TMA Interface Requirements Document (document number
to be assigned). {Requirement 3665 is deferred.}

3.3.11 Time Synchronization Interface

TMA SHALL [3672] use UTC (or equivalent) as its time reference when calculating, comparing,
or displaying quantities that indicate time-of-day.

TMA SHALL [3674] accept the time-of-day supplied by a Coded Time Source (CTS) as the
UTC clock reference.

TMA SHALL [3676] issue an alarm when the Host time supplied in the XE message and the
time supplied by the CTS disagree by a parameter amount of time (nominally 30 seconds) (Site
Adaptable Installation Data).

3.3.12 TRACON Passive Data Feed Interface

This section states the interface requirements for a passive data feed from a TMA TRACON Data
I/O Group to one or more TMA installations. This interface is referred to as TPFI in Table 3.3.1-
1.

The TRACON Data I/O Group SHALL [3682] be capable of interfacing with up to twelve (12)
TMA installations in a one-way mode.

The TRACON Data I/O Group SHALL [3684] be capable of sending FP and track data to all
connected passive feed TMA installations.

Requirements 3686 and 3688 have been deleted.

3.3.13 Collaborative Arrival Planning (CAP) to Client Interface Requirements

This section states the interface requirements between a Center TMA and the Volpe CAP
distributor. This interface is referred to as CAP in Table 3.3.1-1.

   a. CAP SHALL [3622] listen for incoming TCP connection requests on an adapted TCP
      port number as defined in the TMA CAP to CAP Client Interface Control Document
      (CAP ICD).

   b. CAP SHALL [3624] accept a TCP connection request from a client if it is connecting
      from a client name and IP address that are adapted. A client that receives persistent
      updates is classified as a permanent connection.




                                              123                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                 17 December 2008
                                                                                         Final Rev N
   c. CAP SHALL [3626] allow each client to make up to two TCP connections per IP
      address, one for persistent transfer of data and one for queries, if the client’s IP address is
      adapted.

   d. CAP SHALL [3628] log all data transmitted to and received from a client.

   e. CAP SHALL [3632] transmit data to and receive data from a client encoded in XML as
      specified in the CAP ICD, and as constrained by site specific adaptation.

   f. CAP SHALL [3634] be able to compress all data sent over the TCP connection as
      specified in the CAP ICD. CAP SHALL [3635] accept a request from a client to use
      compression.

   g. CAP SHALL [3636] transmit time information in a standardized format using a subset of
      the ISO 8601 protocol as specified in the CAP ICD.

   h. CAP SHALL [3638] accept a request from a client indicating the category or categories
      of information as specified in the CAP ICD. Examples of categories are: flight data,
      routing data, meter reference point (MRP) data, ETAs, STAs, scheduling status, and
      airport configuration.

   i. CAP SHALL [3642] filter out all military flights. Normally, military flights are not
      processed by the core TMA software unless they are actually involved in scheduling to an
      adapted airport. {Deferred}

   j. Requirement 3697l has been deleted

          1. subrequirement has been deleted

          2. subrequirement has been deleted

          3. subrequirement has been deleted

   k. Requirement 3698 has been deleted.

   l. Requirement 3699 has been deleted.

Requirements 3622 (3685), 3624 (3687), 3626 (3689), 3628 (3691a-d), 3632 (3692), 3634
(3693), 3636 (3694), 3638 (3695), 3642 (3696) have replaced the numbers following them in
parentheses.

3.3.14 National Airspace Infrastructure Management System (NIMS) Interface

TMA SHALL [3735] be capable of interfacing with NIMS for remote maintenance, monitoring
and control. {Requirement 3735 is deferred}




                                                124                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
3.4      System Internal Interface Requirements

TMA SHALL [3680] employ a common Inter-Process Communication (IPC) capability allowing
processes to communicate with each other via messages.

The TMA IPC capability SHALL [3690] transmit messages from a sender to one or more
receivers reliably, i.e., preserving the data content of each message and the order in which they
were sent.

Sections 3.4.1 - 3.4.5, including requirements 3700, 3701, 3702, 3703, 3704, 3705, 3706, 3707,
3708, 3709, 3710, 3711, 3712, 3713, 3714, 3715, 3716, 3717, 3718, 3719, 3720, 3721, 3722,
3723, 3724, 3725, 3726, 3727, 3728, 3729, and 3730, have been deleted.

3.5      System Internal Data Requirements

All decisions about system internal data will be left to design.

3.6      Adaptation Requirements

The operational TMA SHALL [3740] be adaptable to airspace parameters (Static Site Adaptable
Scheduler Data) including at a minimum:
   a. Arrival gates.
      b. CTAS Meter Fixes.
      b1. Scheduling meter fixes.
      c. Outer Meter, Outer-Outer, Outer-Three, and Outer-Four Arcs.
      d. Primary airports.
      e. Runways at primary airports.
      f. FAFs.
      g. Satellite airports.
      h. Airspace fixes (Waypoints).
      i. Preferential Arrival Routes (PARs).
      j. Center Airway Routes for display.
      k. TRACON maps for display.
      l. ARTCC sector boundaries.
      m. TRACON boundaries.
      n. Special Use Airspace (SUA).
      o. Meter Fix Arcs.




                                                125                             TMA System Spec
                                                                              FAA-E-2971
                                                                         17 December 2008
                                                                                Final Rev N
The operational TMA SHALL [3750] be adaptable to (Static Site Adaptable Scheduler Data):
   a. Dependencies between gates and airports.
   b. Dependencies between CTAS Meter Fixes/Scheduling Meter Fixes and airports.
   c. Dependencies between Meter Fix Arcs and configurations.
   d. Dependencies between FAFs and configurations.
   e. Mapping between aircraft types and engine class.
   f. For TMA, a total of up to 20 adjacent TRACONs that are either:
         1) within the ARTCC or
         2) not located in the ARTCC, but within 200 nmi of the TMA arrival airport.
        {Subrequirement f is deferred.}
   g. (subrequirement deleted)
   h. (subrequirement deleted)
   i. Up to twelve (12) outer meter arcs for any CTAS meter fix. {Subrequirement i is
      deferred.}
   j. Up to two (2) meter fix arcs per CTAS meter fix. {Subrequirement j is deferred.}
   k. Up to 9 Outer-outer arcs per Outer meter arc.
   l. Up to 9 Outer-Three Arcs adapted per Outer-Outer Arc.
   m. Up to 9 Outer-Four Arcs adapted per Outer-Three Arc.

Requirements 3800, 3810, and 3860 have been deleted.

The operational TMA in an ARTCC and the associated TRACON SHALL [3870] be adaptable
to procedural parameters including at a minimum (Static Site Adaptable Scheduler Data):
    a. Nominal TRACON routes.
   b. Airport Configurations.
   c. Arrival gate crossing altitude and speed restrictions.
   d. Runway assignment preferences.

The operational TMA SHALL [3880] be adaptable via static site adaptable scheduler data to the
minimum separation requirements for final approach including at a minimum:
   a. Single runway approach in IFR conditions.
   b. Single runway approach in VFR conditions.
   c. Independent simultaneous approaches in IFR conditions.
   d. Independent simultaneous approaches in VFR conditions.
   e. [subrequirement deleted]
   f.   [subrequirement deleted]
   g.   [subrequirement deleted]


                                               126                          TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
   h. [subrequirement deleted]

The operational TMA SHALL [3890] be adaptable to:
   a. [subrequirement deleted]
   b. Routes used when assigning aircraft to a different feeder gate (Static Site Adaptable
      Scheduler Data).
   c. TRACON analysis categories when establishing routes (Static Site Adaptable Scheduler
      Data).
   d. Degrees of freedom associated for each TRACON analysis category (Static Site
      Adaptable Scheduler Data).
   e. TRACON altitude profiles when establishing routes (Static Site Adaptable Scheduler
      Data).
   f. Irregular TRACON shapes (Static Site Adaptable Scheduler Data).
   g. Landing approach segments (Static Site Adaptable Scheduler Data).
   h. Approach segment determination information (Static Site Adaptable Scheduler Data).
   i. Prohibited runway assignments for particular aircraft types (Static Site Adaptable
      Scheduler Data).
   j.   [subrequirement deleted]
   k. [subrequirement deleted]
   l.   [subrequirement deleted]
   m. [subrequirement deleted]
   n. Stream Class definitions (Static Site Adaptable Scheduler Data).
   o. Allowable combinations of Stream Classes into Super Stream Classes (Static Site
      Adaptable Scheduler Data).
   p. CTAS Meter Fix and Scheduling Meter Fix assignment information (Static Site
      Adaptable Scheduler Data).
   q. [subrequirement deleted]
   r. The amount the ETA or STA needs to change before automatic rescheduling (Static Site
      Adaptable Scheduler Data).{Subrequirement r is deferred.}
   s. The maximum amount of delay an aircraft can be expected to absorb on a particular
      nominal TRACON route or between a particular scheduling meter fix/meter fix arc and
      runway (Static Site Adaptable Scheduler Data).
   s1. The maximum amount of delay an aircraft can be expected to absorb between a particular
       scheduling meter fix and CTAS meter fix when they are adapted at different locations
       (Static Site Adaptable Scheduler Data).
   t. The maximum amount of delay an aircraft can be expected to absorb from the outer meter
      arc to the CTAS Meter Fix/meter fix arc (Static Site Adaptable Scheduler Data).
   u. Weather Grid conversion information (Site Adaptable Installation Data).



                                              127                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N
      v. Default Weather Model (Model Data).
      w. Wake vortex separation information (Model Data).
      x. Aircraft models used for Trajectory synthesis (Model Data).
      y. Aircraft model performance information (Model Data).
      z. Airline descent preferences (Static Site Adaptable Scheduler Data). {Subrequirement z is
         deferred.}
      aa. Eligibility criteria for ETA generation, track update processing, and scheduling (Static
          Site Adaptable Scheduler Data).
      bb. Specified aircraft callsigns (Static Site Adaptable Scheduler Data).
      cc. General aviation aircraft (Static Site Adaptable Scheduler Data).
3.7      Safety Requirements

There are no special safety requirements for TMA beyond than the normal safety requirements
for FAA equipment.
3.8      Security and Privacy Requirements

The Commercial Off the Shelf (COTS) software products utilized by TMA SHALL [3891] meet
the C2 criteria of DoD 5200.28-STD, Trusted Computer System Evaluation Criteria .

In order to obtain a waiver from FAA Office responsible for Information Systems Security
Program or an agreement that TMA complies with FAA Order 1370.82A, Information Systems
Security Program, TMA must satisfy the following three requirements on Identification,
Authentication, and Access Control, and another three requirements on System Accountability:

For the purpose of Identification and Authentication TMA SHALL [3892]:
   a. Provide the requirement to log on all users to the system with a user-identification and
        password, and
      b. Provide the capability to create and maintain user-identifications and passwords.


For the purpose of Discretionary Access Control TMA SHALL [3893] provide the capability to:
   a. Control access between each named subject and object.
      b. Provide the mechanisms to add, change, or delete user permissions by an authorized user.
      c. Provide the capability to create and maintain user-IDs and passwords providing four
         categories of access privilege.

The four categories of access or roles, along with an example of their rights and responsibilities,
are:
     1) TMA User - is allowed to use only the end-user functions of the TMA system. This will
        require no password or group creation on TMA itself. The TMA User will sign the
        Station Log upon turnover, which will be used to track TMA User access.


                                                  128                             TMA System Spec
                                                                               FAA-E-2971
                                                                         17 December 2008
                                                                                Final Rev N
      2) M & C User - will perform M&C start-up and shut-down, TMA Operational system
         startup and shutdown, and the ability to reboot workstations.
      3) Maintenance User – will perform upkeep and troubleshooting of TMA, reboot of remote
         systems, remote system startup and shutdown of TMA LAN computers, and associated
         types of functions.
      4) System Administrator - will perform the adding/deleting of users, setting up new/user
         directories, configuring, add in new releases, etc., type of functions.

The access and restriction for each user category SHALL [3894] be determined by the TMA
System Developer, subject to FAA approval.

For the purposes of System Accountability (Auditing) TMA SHALL [3895]:
   a. Provide the capability to create and maintain an audit trail of all relevant events and
        accesses to security and mission critical objects.
      b. Protect the audit trail from unauthorized access, modifications and destruction.
      c. Provide the capability to audit the following types of security-relevant events:
         1) All identification and authentication procedures to include all logon attempts.
         2) Access and access attempts (modification and/or deletions to any security or mission
            critical object).
      d. Provide the capability to tailor events to be audited and reported.
      e. Provide the capability to produce audit reports that are formatted for both on-line viewing
         and printing.

TMA SHALL [3896] provide the capability to have the audit reports viewed on the TMA
workstations and at the facility providing the remote maintenance capability.

TMA SHALL [3897] provide the capability to perform checks to detect changes to the system
and operational software.
3.9      System Environment Requirements

There are no special environmental requirements for TMA beyond than the normal
environmental conditions for FAA equipment.
3.10     Computer Resource Requirements

3.10.1 Computer Hardware Requirements

The System SHALL [3900] use standard, non-developmental computer resources, including
CPUs, servers, interfaces, storage devices, switches, and peripherals.

3.10.2 Computer Hardware Resource Utilization Requirements




                                                  129                             TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
Reserves of at least fifty percent SHALL [3910] exist for memory utilization when averaged over
any 12-second interval in each hardware unit containing TMA software.

Reserves of at least fifty percent SHALL [3920] exist for network utilization when averaged
over any 12-second interval in each hardware unit containing TMA software.

Reserves of at least fifty percent SHALL [3930] exist for processor utilization when averaged
over a 12-second interval in each hardware unit containing TMA software.

3.10.3 Computer Software Requirements

TMA SHALL [3940] use a standard, non-developmental computer operating system that
conforms to the POSIX (Institute of Electrical & Electronic Engineers (IEEE) 1003.1, Portable
Operating System Interface Part 1 Library Routines, System Calls, and Header files) standard and
is compliant with the SVID3, System V Interface Definition, Third Edition.

Computer program software firmware and data bases SHALL [3950] be designated as Computer
Software Configuration Items (CSCIs).

All delivered software except COTS and NDI modules SHALL [3960] be implemented either in
the ANSI C programming language (as specified in ANSI/International Standards Organization
(ISO) Standard 9899-1990, ANSI Standard for the C Programming Language) or the C++
programming language (with prior approval according to the exception procedure specified in the
Traffic Flow Management (TFM) Domain Environment Definition Document (A Standard
Profile), 29 April 1996) See C++ ARM Pre-Standard, The Annotated C++ Reference Manual.

NOTE: The exception procedure referenced will be a waiver procedure. The FAA- approved
waiver will specify the agreed upon C++ compiler. It is the FAA’s responsibility to ensure
appropriate organizations are included in the waiver approval process.

NDI software used in TMA SHALL [3970]:
  a. Meet the reliability and maintainability requirements stated herein.
   b. Not be modified without the approval of the FAA.
   c. Be such that its licensing, use, and limits of use do not degrade specified performance and
      protect the FAA's ability to use the software for the purpose procured and to maintain the
      software.
   d. Be documented in published technical descriptions that show suitability of use.

3.10.4 Computer Communication Requirements

All decisions regarding computer communications requirements (e.g., geographic locations,
network topology, data transfer rates, type and volume of data, etc.) are left to design, except for




                                                130                              TMA System Spec
                                                                             FAA-E-2971
                                                                        17 December 2008
                                                                              Final Rev N
those communication requirements imposed on TMA by external systems with which TMA is
required to interface.
3.11   System Quality Factors

3.11.1 System Functionality

The ability to perform all required functions will be demonstrated as part of the qualification
procedure defined in Section 4.

3.11.2 System Reliability

TMA SHALL [3980] meet a hardware mean-time-between-failure (MTBF) of 2190 hours.

3.11.3 System Maintainability

TMA provides the capability for fault detection or reduced service recognition, fault verification,
fault isolation, and ease of rapid fault correction to support the mission.

TMA SHALL [3990] provide hardware diagnostic capabilities capable of determining, at a
minimum, whether the following are available for use:
   a. Individual processors.
   b Inter-process communication paths.
   c. Data recording equipment.
   d. The coded time reference.
   e. Communication network interfacing equipment.

The operational TMA SHALL [4000] require periodic maintenance no more than two times per
year.

The periodic maintenance of the operational TMA SHALL [4010] be completed within 12 hours.

TMA SHALL [4020] satisfy a mean-time-to-repair (MTTR) for hardware failures of 30 minutes
from the commencement of repair activity.

NOTE: MTTR is calculated based upon the total time of all interruption of service except for
technician notification time, regardless of their duration. MTTR does not include the delay times
associated with technician notification, provisioning of required equipment or parts, and
response, but does include the total time for isolation and retest.




                                                131                             TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N
3.11.4 System Availability

Failures of system components are expected to occur. Automatic fault detection, isolation, and
recovery mechanisms will be employed to ensure rapid restoration of critical functions and to
sustain system availability. TMA must meet the system availability requirements for "Essential"
services as specified in NAS-SR-1000, National Airspace System Requirements. NOTE: Time
allocated to maintenance as defined in Section 3.11.3 is not considered for the purposes of
computing system availability.

The operational TMA SHALL [4029] demonstrate a system availability of 0.999 for an
endurance test of 168 hours with representative flight plan and traffic data loads for a selected
TMA deployment site. The operational TMA SHALL [4030] have an analytically determined
hardware system inherent availability of not less than 0.999.

No single equipment failure in the operational TMA SHALL [4031] cause loss of service to the
user of a duration longer than those specified in the following table (see Table 3.11.4-1). If a
TMA system recovers within the time limits defined, then, by definition, no loss of service has
occurred. Loss of service is defined as the inability to use TMA for its intended purpose by
either sector controller(s) or the facility TMU.

The M&C SHALL [4035] detect the failure of remote equipment in the TRACON and/or Tower
within 1 minute. This SHALL [4036] include detection of a communications link failure between
the ARTCC and TRACON or Tower.

                                Table 3.11.4-1 Outage Durations
             Operational Function                                                Outage Duration
TMA          a. Display of CTAS meter fix/meter fix arc times to sector          1 minute
                controllers
             b. Display of Timelines, Load Graphs, Plan View Situation           1 minute
                Displays to TMU

             c. (Subrequirement deleted)
             d. (Subrequirement deleted)

M&C          No requirement

External     e. All except weather                                               1 minute
Interfaces   f. Weather                                                          75 minutes
                                                                                 (restore last
                                                                                 weather received)


When a software failure or equipment failure causes more than a momentary interruption (i.e.,
functionality is immediately restored through redundant equipment) an indication or alarm of the


                                                132                              TMA System Spec
                                                                                  FAA-E-2971
                                                                           17 December 2008
                                                                                   Final Rev N
failed condition SHALL [4032] be presented to the controller and/or TMC until recovery is
completed to the configuration state prior to the time of failure.

The operational TMA SHALL [4033] establish service within 15 minutes from the application of
power to the system (i.e., cold start). The operational TMA SHALL [4034] establish service
within 5 minutes of starting or restarting the TMA application software (i.e., warm start).

3.11.5 System Flexibility

The System will be functionally and operationally modular to facilitate System modification,
support, and expansion.

The System SHALL [4040] be composed of hardware configuration items, software
configuration items and database configuration items, selected based upon intended use, support,
maintenance and configuration control.

The System will incorporate design features that support modification with minimal impact to
unaffected components.

Requirement 4050 has been deleted.

3.11.6 System Portability

Requirement 4060 has been deleted and will be addressed in the Full Scale Development
Statement of Work.

3.11.7 System Reusability

To minimize development and assure compatibility with existing and planned improvements, the
use of existing software and hardware components, including COTS components, Government
Furnished Data (GFD), Government Furnished Item (GFI) software, and Government Furnished
Equipment (GFE) is encouraged.

Requirement 4070 has been moved to the CTAS Build 2 Non-Technical Requirements Matrix.

3.11.8 System Testability

All decisions regarding system testability will be left to design.

3.11.9 System Usability

All decisions regarding system usability will be left to design.
3.12   Design and Construction Constraints




                                                 133                         TMA System Spec
                                                                                      FAA-E-2971
                                                                                17 December 2008
                                                                                       Final Rev N
All decisions regarding design and construction constraints (e.g., weight limits, dimensional
limits, etc.) will be left to design.
3.13   Personnel-Related Requirements

There are no special personnel-related requirements for TMA beyond the normal FAA personnel
procedures.
3.14   Training-Related Requirements

Requirement 4080 has been moved to the CTAS Build 2 Non-Technical Requirements Matrix.
3.15   Logistics-Related Requirements

There are no special logistics-related requirements for TMA beyond the normal FAA logistics
procedures.
3.16   Other Requirements

The TMA system must produce correct results when processing dates leading up to and
continuing into the year 2000. All hardware and software components whether in operational or
support mode SHALL [4085] correctly process the following dates:
   a. The 9th of September 1999.
   b. The century crossover from 12/31/1999 to 1/1/2000.
   c. The leap year date 2/29/2000.
3.17   Packaging Requirements

There are no special packaging requirements for TMA.
3.18   Precedence and Criticality Requirements (deleted)

Section 3.18, including requirement 4090, has been deleted.




                                               134                            TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
4.      QUALIFICATION PROVISIONS

Requirement 5000 has been deleted.

A set of qualification methods will be developed for TMA and provided separately. The set will
specify for each requirement in Section 3 the method(s) to be used to ensure that the requirement
has been met.

Qualification methods may include:
   a. Demonstration: The operation of the system, or part of the system, which relies on
       observable functional operation not requiring the use of instrumentation, special test
       equipment, or subsequent analysis.
     b. Test: The operation of the system, or a part of the system, using instrumentation or other
        special test equipment to collect data for later analysis.
     c. Analysis: The processing of accumulated data obtained from other qualification methods.
        Examples are reduction, interpolation or extrapolation of test results.
     d. Inspection: The visual examination of system components, documentation, etc.
     e. Special qualification methods: Any special qualification methods for the system, such as
        special techniques, procedures, use of standard samples or any other method not covered
        by a-d above.




                                                135                             TMA System Spec
                                FAA-E-2971
                           17 December 2008
                                 Final Rev N




Page Intentionally Blank




           136             TMA System Spec
                                                           FAA-E-2971
                                                      17 December 2008
                                                            Final Rev N
5.     REQUIREMENTS TRACEABILITY

Not required for this system-level specification.




                                                137   TMA System Spec
                                FAA-E-2971
                           17 December 2008
                                 Final Rev N




Page Intentionally Blank




           138             TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
6.      NOTES

This section contains information intended to aid the understanding of this document.
6.1     Acronyms

      AAR                     Airport Acceptance Rate
      A/C                     Aircraft
      ACES                    Adaptation Controlled Environment System
      ACG                     Adjacent Center Group
      ACID                    Aircraft ID or Aircraft Identification
      ACO                     Office of Security
      ADG                     ARTS Data Gatherer
      AERA                    Automated En Route ATC
      AF                      Airways Facilities
      AGW                     ARTS Gateway
      AMCC                    ARTCC Maintenance Control Center
      ANSI                    American National Standards Institute
      AMDT                    Maximum Delay Time
      AOC                     Airline Operations Center
      ARTCC                   Air Route Traffic Control Center
      ARTS                    Automated Radar Terminal System
      ASD                     Aircraft Situation Display
      ASP                     Arrival Sequencing Program
      AT                      Air Traffic
      ATC                     Air Traffic Control
      ATM                     Air Traffic Management
      ATRD                    Adjacent TRACON Data
      ATRG                    Adjacent TRACON Group
      ATWG                    Adjacent Tower Group
      AWIPS                   Advanced Weather Interactive Processing System

      CAP                     Collaborative Arrival Planning
      CAS                     Calibrated Air Speed
      CCB                     Configuration Control Board
      CDR                     Continuous Data Recording
      CDI                     Center Data Interface
      CHI                     Computer Human Interface
      CID                     Aircraft Computer Identification
      CMD                     Center Maximum Delay
      COTS                    Commercial Off-The-Shelf
      CPDP                    Company Preferred Descent Procedures
      CPU                     Central Processing Unit
      CSCI                    Computer Software Configuration Item



                                              139                             TMA System Spec
                                                                         FAA-E-2971
                                                                   17 December 2008
                                                                          Final Rev N
CSMD                    CTAS Meter Fix to Scheduling Meter Fix/Meter Fix
                        Arc Maximum Delay
CTAS                    Center/TRACON Automation System
CTS                     Coded Time Source

DCA                     Delay to be absorbed in Center Airspace
DFW                     Dallas/Fort Worth
DID                     Data Item Description
DLP                     Diversion List Processing
DM                      Data Management
DOT                     Department of Transportation
DP                      Dynamic Planner
DSR                     Display System Replacement
DT&E                    Development Test & Evaluation
DYSIM                   Dynamic Simulator

EDC                     En Route Departure Capability
EDCT                    Estimated Departure Clearance Time
EO3AD                   Excess Outer-Three Arc Delay
EO4AD                   Excess Outer-Four Arc Delay
EOFD                    Excess Outer Fix Delay
EOOAD                   Excess Outer-outer Arc Delay
ERAM                    En Route Automation Modernization
ETA (all capitals)      Estimated Time of Arrival
Eta data (initial cap   designation of the Eta Weather Model data
          only)
ETD                     Estimated Time of Departure
ETMS                    Enhanced Traffic Management System

FAA                     Federal Aviation Administration
FAF                     Final Approach Fix
FAST                    Final Approach Spacing Tool
FCFS                    First Come First Served (scheduling method)
FCTS                    First Common Time Step
FDAD                    Full Digital ARTS Display
FDB                     Full Data Block
FIPS                    Federal Information Processing Standard
FLUID                   Flight Unique Identifier
FP                      Flight Plan
FTMD                    Flight TRACON Maximum Delay

GDS                     Generic Display Station
GFD                     Government Furnished Data
GFE                     Government Furnished Equipment
GFI                     Government Furnished Information


                                       140                            TMA System Spec
                                                              FAA-E-2971
                                                         17 December 2008
                                                               Final Rev N
GMT     Greenwich Mean Time (ZULU)
GRIB    Gridded Binary
GUI     Graphical User Interface

HCS     Host Computer System
HID     Host Interface Device

IAW     In Accordance With
ICD     Interface Control Document
IEEE    Institute of Electrical & Electronic Engineers
IFR     Instrument Flight Rules
ILS     Instrument Landing System
I/O     Input/Output
IOP     Input Output Processor
IPC     Inter Process Communication
IPT     Integrated Product Team
IRD     Interface Requirements Document
ISO     International Standards Organization

LAN     Local Area Network
LAX     Los Angeles Tower
LRU     Lowest Replaceable Unit

M&C     Monitor and Control
MACH    MACH number (speed ratio to speed of sound)
MDT     Mean Downtime
MF      Meter Fix
MFAMD   Meter Fix Arc Maximum Delay
MIB     Management Information Base
MIL     Military
MIT     Miles-in-trail
MMG     Multi-Metering Gateway
MOTIF   Modular Toolkit Interface
MMP     Multiple Meter Point
MP      Meter Point
MPDP    Meter Point Dynamic Planner
MPE     Multiprocessor Executive
MTBF    Mean-Time-Between-Failure
MSSD    Multiple Super Stream Deconfliction
MTTR    Mean-Time-to-Restore; Mean-Time-to-Repair

NAILS   National Airspace Integrated Logistics Support
NAPRS   National Airspace Performance Reporting System
NAS     National Airspace System
NASA    National Aeronautics & Space Administration


                        141                              TMA System Spec
                                                            FAA-E-2971
                                                       17 December 2008
                                                             Final Rev N
NAVAID   Navigational Aid
NCEP     National Center for Environmental Protection
NDI      Non-developmental Items
NFDC     National Flight Data Center
NIMS     National Airspace Infrastructure Management System
NMI      Nautical Miles
NWS      National Weather System

O3A      Outer-Three Arc
O4A      Outer-Four Arc
O3AD     Outer-Three Arc Delay
O4AD     Outer-Four Arc Delay
O3P      Outer-Three Point
O4P      Outer-Four Point
OBE      Overcome By Events
ODCA     Delay to be absorbed in the Outer-Center Airspace
OETA     Original Estimated Time of Arrival
OFD      Outer Fix Delay
OO3AD    Outside Outer-Three Arc Delay
OO4AD    Outside Outer-Four Arc Delay
OOAD     Outer-outer Arc Delay
OOOAD    Outside Outer-outer Arc Delay
OOP      Outer-Outer Point
OP       Outer Point
ORD      Operational Requirements Document
OSF      Open Software Foundation
OSP      Open Slot Processing

PAMRI    Peripheral Adapter Module Replacement Item
PAR      Preferred Arrival Route
PAS      Pseudo Aircraft Simulation
PDP      Preferencing Delay Parameter
PGUI     Planview Graphical User Interface
POSIX    Portable Operating System Interface for OSE
P3I      Pre-Planned Product Improvement

RA       Route Analysis
RFC      Request for Comments
RMD      Route Maximum Delay
RMS      Root Mean Square
RPR      Requirement Problem Report
RS       Remove Strip
RUC      Rapid Update Cycle

SAR      System Analysis Recording


                        142                            TMA System Spec
                                                               FAA-E-2971
                                                          17 December 2008
                                                                Final Rev N
SBSD      Spatially Based Sequencing Distance
SDI       Statistical Delay Information
SFMD      Scheduling Meter Fix/Meter Fix Arc Maximum Delay
SGFF      Single Gate Free Flow
SMA       Surface Movement Advisor
SMC       System Maintenance Coordinator
          System Manager Console
SMP       Scheduling Meter Point
SNMP      Simple Network Management Protocol
SSC       Super Stream Class
SSDD      System Subsystem Design Description
SSPI      Site Specific Plan Identifier
SSS       System/Subsystem Specification
STA       Scheduled Time of Arrival
STARS     Standard Terminal Automation Replacement System
SUA       Special Use Airspace

TAR       TRACON Acceptance Rate
TAS       True Air Speed
TATCA     Terminal Air Traffic Control Automation
TB        TRACON Buffer
TBD       To Be Defined
TBM       Time Based Metering
TBS       To Be Supplied
TCP/IP    Transmission Control Protocol/Internet Protocol
TEC       Tower En route Control
TESTNAS   NAS Under Test Mode
TDI       TRACON Data Interface
TFM       Traffic Flow Management
TGUI      Timeline [ed.] Graphical User Interface
TMA       Traffic Management Advisor
TMC       Traffic Management Coordinator
TMC-GUI   Traffic Management Coordinator
          Graphical User Interface
TMU       Traffic Management Unit
TRACON    Terminal Radar Approach Control
TS        Trajectory Synthesis
TSD       Traffic Situation Display
TTF       Time to Fly

UTC       Coordinated Universal Time (Zulu)

VFR       Visual Flight Rules
VRTM      Verification Requirements Traceability Matrix
VSCR      Variable Speed Crossing Restriction


                         143                              TMA System Spec
                                                FAA-E-2971
                                           17 December 2008
                                                 Final Rev N

WARP   Weather and Radar Processor
WMO    World Meteorological Organization
WX     Weather

ZDV    Denver ARTCC
ZFW    Fort Worth ARTCC




                     144                   TMA System Spec
                                                                                        FAA-E-2971
                                                                                   17 December 2008
                                                                                         Final Rev N
6.2     Glossary

Active Aircraft:        Aircraft that are actively flying within the NAS environment.

Adaptation: A collection of data files that customizes the functions of TMA to a specific air
traffic control facility.

Adaptation Function: The process of tailoring a system to the relevant ARTCC and associated
primary airports within TRACONs.

Adapted Airport:     An airport for which adaptation data files exist and schedules/advisories
may be generated by TMA.

Adjacent Center:       A Center other than the Center which contains the adapted arrival
airport(s) for which schedules/advisories may be generated by TMA.

Adjacent TRACON: A TRACON which shares a border with the arrival TRACON which is the
subject of TMA metering.

Aircraft's Total Flight Distance:       The great circle distance from departure airport to arrival
airport. This is the shortest distance the aircraft could travel and accomplish its flight.

Airport Acceptance Rate (AAR):        A dynamic input parameter specifying the number of
arriving aircraft (measured at the runway threshold) which an airport or airspace can accept from
the ARTCC per hour. AAR is used to calculate the desired interval between successive arrival
aircraft.

Airport Runway Configuration:          The list of arrival runways at an airport that are active (i.e.,
operational) for any specific time interval.

Air Route Traffic Control Center (ARTCC) (also called "Center"): Has the responsibility for the
enroute portion of Instrument Flight Rules (IFR) flights.

Alarm: An alarm is defined as a condition that occurs when a subsystem determines that a key
monitored parameter, condition, or status is outside required operating limits, or changed to an
invalid state. When this happens, the subsystem shall be considered to be in an alarm condition.
An alarm message shall be generated when the subsystem is in an alarm condition.

Alert: An alert is defined as a condition that occurs when a subsystem determines that a key
monitored parameter, condition or status is within required operating limits but outside desired
operating limits. When this happens, the subsystem shall be considered to be in an alert state. An
alert message shall be generated when the subsystem is in an alert condition.




                                                  145                               TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
AMDT:           The maximum delay that can be absorbed within the performance characteristics
of a large set of aircraft types on the trajectory between two assigned MRPs.

Analysis Category: The same as the Route Analysis Category. A categorization of an aircraft's
current situation. This basic categorization determines the estimate of an aircraft's future
intention. Based on this categorization, TMA determines an aircraft's probable future route and
all permissible routing variations.

Analysis Category Decision Tree:       A list of rules found in the site adaptation which assign an
aircraft to an analysis category. The analysis category decision tree examines an aircraft's
position and heading, and compares it to the local airspace route structure.

Arrival Plan: The aggregate of all assignments, schedules, and advisories.

ARTCC Maintenance Control Center (AMCC):            A central facility within each ARTCC (En-
Route Center) which monitors the functioning of all the facility's hardware and software. The
AMCC will also have some control capability over the hardware and software in the ARTCC.
TMA will have an interface to the AMCC.

Availability: The probability that an item will be operationally ready to perform its function
where called upon at any point in time. Steady state availability of installed equipment is a
function of equipment mean-time-between-failures (MTBF) and equipment downtime (MDT), as
follows:
                                                MTBF
                                       A
                                           MTBF  MDT

Blocked Runway Interval:      A length of time during which no aircraft can automatically be
assigned to a specified runway. This is usually used for a large departure rush or for runway
maintenance such as snow plowing.

Blocked Scheduling Meter Fix Interval:      A length of time during which no aircraft can be
automatically assigned to a scheduling meter fix. This is usually used for periods of hazardous
weather over a scheduling meter fix.

Blocked Slot: A runway landing interval reserved for a specific type of aircraft. The specific
type of aircraft may be derived from a specific aircraft for which the Blocked Slot is reserved.

Calibrated Air Speed (CAS): The airspeed measured on an aircraft using a forward mounted
pivot tube. This measured speed is relative to the local wind, and is lower than the true air speed
by the square root of the ratio of the density of the local atmosphere to the density of the
atmosphere at sea level.

Center:        Air Route Traffic Control Center (also called ARTCC).




                                                146                              TMA System Spec
                                                                                       FAA-E-2971
                                                                               17 December 2008
                                                                                        Final Rev N
Center Maximum Delay (CMD):            The maximum delay which can be absorbed by an aircraft
traveling along its converted route of flight between the boundary of the Center's airspace and the
aircraft's assigned CTAS meter fix.

Center-TRACON Automation System (CTAS):              The collection of integrated software and
hardware ATC automation tools researched and tested for the purpose of providing automated
schedules on arrival and departure air traffic at TRACON and En Route Centers. As of 2004,
TMA is the only CTAS tool deployed operationally at multiple sites.

Company Preferred Descent Procedures (CPDP): The airline specific portion of the descent
procedures used by the Trajectory Synthesis algorithms to predict the aircraft arrival trajectory.
The company specific portion of each descent is the idle thrust descent speed (Mach or CAS) to
be used in each descent segment.

Commercial Off the Shelf (COTS): Hardware or software which is available for sale in a
commercial catalog (and which is likely to be mass produced). Hardware and Software that is
commercial off the shelf is likely to be less expensive than specially ordered hardware and
software.

Critical System:        Any air traffic control system that would make the job of maintaining
adequate separation impossible if it failed. Critical systems are required to be powered by the
critical electrical power supply and are also required to maintain a 0.9999 availability rating.


CTAS Meter Fix:       A waypoint, generally at or near the TRACON boundary, used for nominal
interior TRACON route determination, determination of the scheduling meter fix, and after the
implementation of the Host Common Message Set, for Host meter list display.

CTAS Meter Fix Crossing Tolerance:             When determining the CTAS meter fix assignment
for an aircraft, TMA determines the intersection of the Converted Route with the TRACON
boundary. If this intersection point is within the CTAS Meter Fix Crossing Tolerance distance of
the closest CTAS meter fix, than the aircraft is assigned to that CTAS Meter Fix. This value is
found in the site adaptation.

Data Item Description (DID):     Describes the format and required contents of a document
developed under MIL-STD-498, Software Development and Documentation, Department of
Defense, 5 December 1994.

Decision Tree:        A list of rules found in the site adaptation that will categorize an aircraft in
a specific way. Examples are the Stream Class Decision Tree, the Meter Fix Decision Tree and
the Analysis Category Decision Tree. These assign an aircraft's CTAS Meter Fix, Stream Class,
or Analysis Category based on an aircraft's situation and a site-specific set of rules.

Delay Close Out Time:        A SDI session ends if there is no reportable delay within the Delay
Close Out Time. This time is read from adaptation but is usually 45 minutes.


                                                 147                              TMA System Spec
                                                                                      FAA-E-2971
                                                                                 17 December 2008
                                                                                       Final Rev N

Delay to be absorbed in Center Airspace (DCA):        The difference between the STA and ETA at
the CTAS Meter Fix.

Departed Flight Plan: A flight plan issued for an aircraft that has just become airborne and has
been detected on any NAS system. The coordination time is the actual time of takeoff.

Development Test and Evaluation (DT&E): DT&E is that T&E conducted primarily to assist the
engineering design and development process by determining incrementally the degree to which
functional engineering specifications are attained. DT&E includes T&E of systems, subsystems,
units, hardware, software, full-scale engineering models and prototypes. DT&E includes
functional T&E of unit, subsystem, and system integration; testing functional integration of
hardware with software and the operational program; and testing functional capability and
integration with operational systems on sites and with the NAS.

Display Point: An optional arc where ETA and STA may be displayed. ETA and STA at the
Display Point are based on a calculated schedule referenced to the Meter Point.

Diversion List Processing: The processing capability to keep track of diverted flights. Flights
that have been diverted to nearby airports may represent future landing demand and must be
monitored.

Dynamic Planner (DP):        A TMA process responsible for scheduling arrival aircraft at the
Scheduling Meter Fix and the Runway. DP is usually defined to be Essential and Non-
restartable.

Dynamic Site Adaptable Scheduler Data:         Any input data containing site specific parameters
or logic that can impact the TMA scheduler (i.e., general airspace, routing, runways, or DP
scheduler data) and can be modified via command line option or user input during operation. All
of these values must have defaults in the adaptation data set. If a direct one-to-one mapping does
not exist between the command line option or user input and the input data, then the software
will not allow for the user to place the system into a situation that is not achievable directly from
the input data. The preference is for a one-to-one mapping with no logic imposed on the input
data from the software; however, algorithm and/or CHI issues may result in a reduced capability
for the user than the input data. Examples of this type of data are in the site data system directory
and include freeze horizon settings.

DYSIM (Dynamic Simulator): A Host function that generates non-radar data/messages that NAS
En Route system uses as a source of simulated real time data inputs. DYSIM generated flights
are identified by the presence of a “+” as the first character of the flight’s ACID.

Enhanced Traffic Management System (ETMS):             A system used by FAA Traffic Management
Personnel to predict, on national and local scales, traffic surges, gaps, and volume based on
current and anticipated airborne aircraft. TMA receives flight and track data from ETMS that it
can not obtain from other sources.


                                                148                              TMA System Spec
                                                                                         FAA-E-2971
                                                                                    17 December 2008
                                                                                          Final Rev N

ERAM:           The replacement system for the Host computer system.

Essential Process:        A process/function/service that if lost will cause the entire TMA system to
fail if the non-critical item itself fails or is shut down and can not be restarted.

Essential System:    Any air traffic control system that would make the job of maintaining
adequate separation more difficult if it failed. Essential systems are required to maintain a 0.999
availability rating.

Estimated Flight Plan:     A flight plan issued for an aircraft that is currently airborne in the
NAS system. The coordination time listed is the estimated time of entry into this ARTCC.

Estimated Time of Arrival (ETA): This is the time at which the aircraft is estimated to cross
the runway threshold (or meter fix, FAF). The ETA is determined without any restrictions
imposed by other aircraft. A non-radar based ETA is derived from an aircraft's flight plan. It is
used until the aircraft is tracked by radar. A radar-based ETA is computed based on the aircraft's
current position and velocity estimates given by the surveillance processor, the expected route,
speed, altitude profile of the aircraft to the threshold, and the projected wind. The ETA is the
earliest time an aircraft would cross a fix or runway threshold if allowed to follow its assigned
flight path without being impeded by separation constraints to other aircraft and with no weather
or air traffic control restrictions are placed on the aircraft flight.

Estimated Time of Departure (ETD): This is the time at which the aircraft is estimated to take
off.

Fail-over:     A method of automatic recovery from a hardware failure in which all the
processes on the failed platform are restarted on a spare hardware platform by the system
Monitor and Control Function. In TMA Build 2, only restartable processes may failover to
another platform.

Feeder Gate: An arrival corridor, normally associated with the TRACON boundary, which may
include one or more arrival routes or CTAS meter fixes, primarily used for arrival traffic.

Final Approach:           The last portion of a standard landing pattern in which the aircraft is
moving on the runway heading and is approaching the runway in an attempt to land. There is
very little variability in potential landing time after an aircraft has established itself on the Final
Approach segment.

Final Approach Fix (FAF):       This is a fix that marks the beginning of the ILS approach for a
runway.

Fix: A geographical position determined by visual reference to the surface, by reference to one
or more radio navigational aids (NAVAIDs), by celestial plotting, or by another navigational
device. A geographical point expressed in latitude and longitude (which Is converted to system


                                                  149                               TMA System Spec
                                                                                        FAA-E-2971
                                                                                  17 December 2008
                                                                                         Final Rev N
coordinates). The fix is stored and uniquely identified in adaptation. A fix is both an aid for
navigation and a reference point for control purposes. The geographical position of an aircraft for
a specified time which is established by reference to navigational aids or celestial plot.

Flight Plan: A detailed plan for each flight occurring under Instrument Flight Rules. The flight
plan contains a route of flight, anticipated departure and arrival times, aircraft identification,
aircraft call sign, aircraft type, on board equipment, anticipated speed and altitude, and other
information pertinent to the flight. TMA makes substantial use of this information in order to
anticipate aircraft routing and procedures.

Flow: A generic orthogonal categorization of aircraft with similar scheduling characteristics
(e.g., all aircraft in a Super Stream Class are said to be in one flow).

FLUID:         A unique identifier assigned to each flight in the ERAM system.

Free Flow:     The condition at a particular scheduling meter fix where the only flow constraint
imposed is that of minimum legal separation or ATC coordinated separation at that meter fix.

Frozen Schedule:      In TMA, the portion of the schedule which is beyond the Freeze Horizon
and which is not subject to further change.

Full Data Block (FDB):         Refers to the display tag that conveys information such as aircraft
id, altitude, and speed on a TMA situation display.

Full Digital ARTS Display (FDAD): The air traffic controller's display used in the TRACON in
sites that use the ARTS-IIIE system.

Gate: See Feeder Gate.

Gate Dependencies: A relationship between available gates and some other condition, e.g.,
arrival configuration, and destination airport. For instance, in Oakland some gates are not used
by aircraft going to San Jose. In Los Angeles, some gates are used only in West configuration
and others are used only during East configuration.

Generic Display Station:     A single display station (hardware element) which is capable of
displaying information from TMA.

Ground Speed:          The rate of travel of an aircraft relative to earth fixed coordinates. This is
the velocity reported by ground based radar tracking. It is also the velocity reported by the
Global Positioning System.

HCS Update Cycle: The period between track reports provided by the HCS to TMA. This
value is hard coded in the TMA patch to twelve seconds.




                                                 150                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N
Host Adapted Meter Fix:       A navigational fix, along an established route, depicted on
published instrument approach procedures and charts, used to meter air traffic flows into a
TRACON. It is used in NOFIX determination and, until the implementation of the Host
Common Message Set, for Host meter list display. A typical configuration has four meter fixes
distributed evenly around the congested TRACON airspace.

Host Computer System (HCS):             The existing mainframe computer system which is at the
heart of every ARTCC. The HCS conveys Flight Plans, assembles radar data within the ARTCC,
plots the position of all tracked aircraft and prints flight progress strips for controllers. It is a
primary source of information for the TMA system.

Host Converted Route:           The final computerized version of the route of flight taken
originally from the field ten route of flight in the flight plan. The process of converting this route
of flight involves translating all fixes into standard ones for that area, expanding all short hand
expressions to their full form, converting the end of the flight using the active Preferred Arrival
Route (PAR), and calculating a predicted time of passage for every fix in the route.

Hovering ETA or STA:            A situation in which the predicted time of flight is not changing
and the ETA or STA of one aircraft appears to be "hovering" on the timeline while all the others
move down inexorably toward landing. This is usually due to the predicted entry of an aircraft
into the arrival center not occurring. If the aircraft does not enter the center airspace within three
minutes of its prediction, the HCS adds another three minutes to this predicted time. This can go
on for a considerable time until the aircraft actually enters the center, or the HCS determines that
the expected arrival is not actually going to occur.

In-Center Departure: A flight destined for a TMA airport that originates in the same center as
the TMA airport.

Inertial Flight Path Angle:   The angle between the path of motion of an aircraft and the local
horizontal plane defined as normal to the earth's local gravitational field.

Instrument Flight Rules (IFR):        Rules governing the procedures for conducting instrument
flight. Also a term used by pilots and controllers to indicate type of flight plan.

Instrument Landing System (ILS): A microwave landing system that allows an aircraft to fly
most of the final approach segment under instrument conditions. It provides an indication of the
runway center line and the recommended glide slope for the landing approach.

Internal Departure: A flight that originates from an airport within or near the ARTCC
boundary and is destined to the adapted arrival airport.

In-TRACON Departure:     A flight destined for a TMA airport that originates within the same
TRACON as the TMA airport (a very short flight).




                                                 151                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                  17 December 2008
                                                                                        Final Rev N
Kinematic Trajectory Modeling:          Trajectory modeling based on air traffic procedures. In this
type of trajectory modeling, it is assumed that the pilot will supply what ever commands are
necessary to achieve certain air traffic procedures. It is assumed that the procedures call for
flight modes that are well within the capability of all airframes in the TMA system. This type of
trajectory modeling is used in the TRACON by TMA.

Kinetic Trajectory Modeling: Trajectory modeling using the complete force model equation. In
this type of trajectory modeling, the flight capabilities of the aircraft model are used. The
trajectory of each aircraft is calculated from its engine thrust and airframe drag models. This
type of trajectory modeling is used in the En-Route Center in TMA.

Main Arrival Plan: In TMA, the arrival plan viewed in both the ARTCC and the TRACON.
The main arrival plan is in contrast to a Preview Arrival Plan that has not been agreed upon by
both facilities.

Metering:        (1) Controlling the flow rate (aircraft per hour) into the terminal area; (2)
Controlling the traffic flow rate past a particular gate, usually without concern for spacing the
traffic or the particular sequence that results; or (3) The En Route Metering (ERM) or the Arrival
Sequencing Program (ASP) functions.

Meter Fix (MF):        A generic term referring to any waypoint used for one or more of the
following TMA functions: nominal interior TRACON route determination, application of non-
runway scheduling constraints and Host meter list display development. Specific types of meter
fixes are: Host adapted meter fixes, CTAS meter fixes and scheduling meter fixes.

Meter Fix Arc:         An arc defined in adaptation with both range and angular extent,
referenced to a runway or airport. When adapted, the meter fix arc is used instead of the
scheduling meter fix to generate routes, apply constraints and calculate ETAs and STAs.

Meter Fix Decision Tree:        A list of rules found in the site adaptation which assign an aircraft
to a CTAS meter fix. The meter fix decision tree looks for the presence of certain site specific
indicators in the converted route. It also examines the anticipated arrival configuration and the
destination airport as part of the decision process.

Meter Point: A term referring to a waypoint used when running TMA in EDC mode. A Meter
Point is a point at which EDC will deconflict aircraft outbound from the Center. When adapted,
the Meter Point is used to provide an ETA and STA referenced to the intersection of the
aircraft route with the Meter Point.

Meter Point Dynamic Planner (MPDP): A TMA process when running in EDC mode
responsible for scheduling aircraft at the Meter Point. MPDP, like the Dynamic Planner process
in TMA Arrival mode, is usually defined to be Essential and Non-Restartable.

Miles-In-Trail (MiT): A method of restricting aircraft flow in a stream based on defining a
minimum separation distance between aircraft.


                                                 152                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

Minimum Legal Separation: An adaptable pair of values, distance and time, to be applied by the
TMA scheduling algorithm that define the minimum longitudinal separation (in distance and
time) between aircraft in the same superstream class.

Mirror Meter Fix: An alternate CTAS Meter Fix through which a flight route change from the
original CTAS Meter Fix will not cause a reschedule of the flight’s STA to the Mirror Meter Fix
or to the runway, when Mirror Meter Fix is enabled.

Monitor and Control (M&C): The portion of a distributed computing system which controls the
function of all the system's parts. This system component is also responsible for monitoring the
health of all the system hardware and software and is responsible for attempting to correct any
system failures it detects.

National Airspace Performance Reporting System (NAPRS):              Records delay data by fix and
total, for any aircraft that enter the ARTCC airspace and experience delays greater than a
user-specified time. FAA Order 6040.15, National Airspace Performance Reporting System
(NAPRS). covers the reporting of air traffic delays of more than 15 minutes, and the procedures
to report these delays occurring under the control of each respective Air Traffic Facility.

National Airspace System (NAS): The common network of U.S. air traffic airspace; air
navigation facilities, equipment and services, airports or landing areas; aeronautical charts,
information and services; rules, regulations, and procedures, technical information, manpower,
and materials. Included are system components shared jointly with the military.

Nearby TRACON: A TRACON which does not share a border with the arrival TRACON, and
whose traffic forms a significant portion of the arrival flow to the arrival TRACON, and which is
within 100 miles of the arrival TRACON.

NOFIX:          Until the implementation of the Host Common Message Set, an aircraft that does
not have an assigned Host adapted meter fix in its route of flight. After the implementation of
the Host Common Message Set, an aircraft that does not have an assigned CTAS meter fix in its
route of flight. There are two types of NOFIX aircraft: (a) If the aircraft’s route is projected to
cross a meter fix arc, it is assigned to that arc, is considered an intra-gate NOFIX, and is
schedulable to the meter fix arc; or (b) If the NOFIX aircraft is not within a meter fix arc, it is
considered an inter-gate NOFIX and is schedulable only to the runway.

Nominal TRACON Routes: A set of routes of flight for aircraft within the arrival TRACON.
These routes are defined in the site adaptation.

Nominal TRACON Speeds: A set of air speeds used in conjunction with Nominal TRACON
Routes. These are stored in the site adaptation in association with the routes and the different
aircraft engine classes for aircraft that use each route.




                                                153                             TMA System Spec
                                                                                       FAA-E-2971
                                                                                 17 December 2008
                                                                                        Final Rev N
Non-Essential Process:       A process/function/service that, if lost, will not cause the entire
TMA system to fail if the non-critical item itself fails or is shut down and cannot be restarted.

Non-Restartable Process:      A process/function/service that if lost cannot be restarted
automatically by the TMA Monitor and Control function. This usually applies to processes that
would require the restoration a great deal of state memory.

Offset Scheduling: A TMA scheduling option in which the locations of the CTAS meter fix
and scheduling meter fix are not coincident.

Open Slot Processing: The process of retaining an open slot in the arrival schedule when a frozen
flight is no longer eligible for the schedule.

Original Estimated Time of Arrival (OETA):           The ETA calculated when the aircraft first
enters the TMA area. It is determined from the first five ETA calculations based on track data.

Outer Fix:     An adapted fix along the route of flight, prior to the CTAS meter fix, that is
associated with an outer meter arc.

Outer Fix Delay (OFD):       The maximum delay that can be absorbed as an aircraft travels
from a specific Outer Meter Arc to a specific CTAS Meter Fix/Meter Fix Arc.

Outer Meter Arc:     An arc defined in adaptation with both range and angular extent,
referenced to a CTAS meter fix. When adapted, the outer meter arc is used to provide an ETA
and STA referenced to the intersection of the aircraft route with the outer meter arc.


Outer-outer Arc: An arc defined in adaptation that is specified by an arc center point, a range and
an angular extent. An Outer-outer arc is associated with one or more Outer meter arcs. When
adapted, the Outer-outer arc is used to provide an ETA and STA referenced to the intersection of
the aircraft route with the Outer-outer arc.

Outer-Outer Point: An arc defined in adaptation with both range and angular extent, referenced
to an Outer Point. When adapted, the Outer-Outer Point is used to provide an ETA and STA
referenced to the intersection of the aircraft route with the Outer-Outer Point.

Outer Point: An arc defined in adaptation with both range and angular extent, referenced to a
Meter Point. When adapted, the Outer Point is used to provide an ETA and STA referenced to
the intersection of the aircraft route with the Outer Point.

Outside Outer-Outer Arc Delay:         An optional value that specifies the maximum delay that
can be absorbed by an aircraft prior to reaching a specific Outer-outer Arc.




                                                154                             TMA System Spec
                                                                                    FAA-E-2971
                                                                              17 December 2008
                                                                                     Final Rev N
Outer-Three Arc (O3A):      An arc defined in adaptation with both range and angular extent,
referenced to an Outer-Outer Arc. When adapted, the Outer-Three Arc is used to provide an
ETA and STA referenced to the intersection of the aircraft route with the Outer-Outer Arc.

Outer-Four Arc (O4A):       An arc defined in adaptation with both range and angular extent,
referenced to an Outer-Three Arc. When adapted, the Outer-Four Arc is used to provide an ETA
and STA referenced to the intersection of the aircraft route with the Outer-Three Arc.

Outer-Three Point (O3P): An arc defined in adaptation with both range and angular extent,
referenced to an Outer-Outer Point. When adapted, the Outer-Three Point is used to provide an
ETA and STA referenced to the intersection of the aircraft route with the Outer-Outer Point.

Outer-Four Point (O4P):     An arc defined in adaptation with both range and angular extent,
referenced to an Outer-Three Point. When adapted, the Outer-Four Point is used to provide an
ETA and STA referenced to the intersection of the aircraft route with the Outer-Three Point.

Preferencing Delay Parameter:        A parameter used by the preferencing algorithms of the
Single Gate Free Flow functionality to determine if a SGFF aircraft is eligible for preferencing
during the runway order of consideration portion of the scheduling process.

Preferred Arrival Route (PAR):         The last portion of a Host Converted Route that concerns
the portion of flight immediately before the Host adapted meter fix. The Host Computer System
adds this detailed portion of the route to the Host Converted Route about an hour before landing.
The exact PAR assigned may be a function of the Airport Runway Configuration or the details of
which Host adapted meter fixes are available at the time of landing.

Preview Arrival Plan: In TMA, the arrival plan viewed by a single TMC as a tool for visualizing
the effect of proposed flow rate changes. The Preview Arrival Plan is local to a small number of
displays, and has an appearance that is distinguishable from the Main Arrival Plan. If the Center
and TRACON facilities agree on a particular Preview Arrival Plan, it may replace the Main
Arrival Plan.

Primary Center:       The Center which contains the adapted arrival airport(s) for which
schedules/advisories may be generated by TMA.

Priority Aircraft: An aircraft status designated by the TMC to a particular aircraft that causes that
aircraft to have priority in sequencing at the scheduling meter fix and at the runway. All other air
traffic in TMA will be scheduled to accommodate an aircraft with the Priority Aircraft
designation.

Proposed Flight Plan: A flight plan issued for an aircraft that has not yet become airborne. The
coordination time is the proposed time of takeoff.




                                                155                              TMA System Spec
                                                                                       FAA-E-2971
                                                                                 17 December 2008
                                                                                        Final Rev N
Region:         A closed set of all arrival stream classes that could ever be combined into super
streams at a facility. In Denver, the set of stream classes TOMSN Jets, TOMSN Props, RAMMS
Jets, and RAMMS Props, form the North West Region of stream classes.

Restartable Process: A process/function/service that, if lost, may be restarted automatically by
the TMA Monitor and Control function. This usually applies to processes that would require the
restoration little or no state memory. Restartable processes can be restarted on alternate
machines in the event of hardware failure giving TMA some "failover" capability.

Route Analysis (RA): A TMA process responsible for predicting the ground track of all arrival
aircraft from their current position through landing. RA is usually defined to be Essential and
Restartable.

Route Analysis Category:      A categorization of an aircraft's current situation. This basic
categorization determines the estimate of an aircraft's future intention. Based on this
categorization, TMA determines an aircraft's probable future route and all permissible routing
variations.

Route Maximum Delay (RMD):        The maximum delay which can be absorbed between the
Scheduling Meter Fix and the Runway along a specific TRACON route.

Runway Threshold: The beginning of the arrival runway, and the location of aircraft touchdown
used by TMA in its scheduling calculations.

Runway Threshold Separation:         A setting that allows additional separation to be applied to
all values of the runway wake vortex separation matrix.

Runway Threshold Separation Buffer:          An extra “cushioning distance” that can be added
onto the specified runway threshold separation values.

Satellite Airports:  Airports that lie under or within the airspace of the ARTCC. Usually used
by TMA in the sense of airports from which aircraft are departing, to go to a TMA-adapted
airport.

Schedule:     A specific sequenced list of Scheduled Times of Arrival (STAs) and the
corresponding times in which each aircraft will cross the runway threshold or other point of
reference.

Scheduled Time of Arrival (STA): An STA is the desired time that an aircraft should cross the
runway threshold. It takes other traffic and airspace configuration into account. An STA shows
the results of the TMA scheduler that has calculated an arrival time according to parameters such
as spacing, aircraft performance, and weather.




                                               156                             TMA System Spec
                                                                                    FAA-E-2971
                                                                               17 December 2008
                                                                                     Final Rev N
Schedule Freeze:      In TMA, aircraft at a certain distance or time from the CTAS meter fix
have their schedule "Frozen". This means that its STA is no longer recalculated, and that the
aircraft's CTAS meter fix (and scheduling meter fix) and runway assignment will not be changed.

Scheduling Meter Fix:         A waypoint, which is at a distance from the destination airport, at
which full scheduling (constraint application and deconfliction) is performed within TMA
software. Scheduling in TMA is performed by the Dynamic Planner (DP). DP provides
schedule deconfliction at two locations, at the runway or final approach fix and the scheduling
fix.

Scheduling Meter Point: A waypoint at which TMA software in EDC mode will perform full
scheduling (constraint application and deconfliction).

Sector Controller:       The generic name for an air traffic controller who is actually responsible
for air traffic in one or more sectors either in an ARTCC or in a TRACON.

Simultaneous Approach:         A condition in which two aircraft can land simultaneously on
parallel runways that are separated by a sufficient distance.

Single Gate Free Flow (SGFF):          A scheduling preference that the TMC can turn on by
stream class and time interval. SGFF aircraft will be checked for possible scheduling preference
during the runway order of consideration portion of the scheduling algorithm. Generally, SGFF
aircraft will be scheduled to receive lower delays than non-SGFF aircraft when arrival demand is
sufficiently large. A dynamic assignable input, the preferencing delay parameter, allows the user
to effect the conditions under which SGFF aircraft are given preference.

Site Adaptable GUI Setup Parameters:           GUI setup parameters which are divided into two
subsets: (a) GUI Configuration Files -- which contain site specific data such as layouts of the
gates on a panel and (b) Site Adaptable User Preference Data -- which contains PGUI and TGUI
display defaults that can be controlled by a user (e.g., number of timelines, fixes on a timeline,
PGUI map choices, etc.)

Site Adaptable Installation Data:    Any input data containing parameters associated with the
particular hardware and system configuration at a particular site. These values can in no way
impact the TMA schedule or advisories. The values in this data are not modifiable by the user
during runtime. Examples of this type of data include:
        realtime_procs/Common_data/system/remote and
        adaptation/"site_data"/wthr_data/wdpd_site_info

Site Independent Data:         Data that is required to be read in at initialization for TMA but is
not dependent on any site-specific characteristics or need. Examples of this type of date include:
       adaptation/"site_data"/comm_mgr/cm_defaults and
       realtime_procs/Common_data/trajectory_synthesizer/aircraft_specific_model_data




                                                157                               TMA System Spec
                                                                                      FAA-E-2971
                                                                               17 December 2008
                                                                                       Final Rev N
Site Specific Plan Identifier (SSPI): A unique identifier for a flight. The SSPI is provided by
the ERAM system.

Spatially Based Sequencing Distance (SBSD):            The distance from the arrival airport at
which TMA switches from time based sequencing to spatially based sequencing. TMA is
programmed to predict that aircraft will not be allowed to pass one another within a certain
distance of the arrival airport. This specific distance is part of the site adaptation.

STA Freeze Suppression Airport: Airports for which the freezing of departing aircraft’s STAs
will be suppressed until the aircraft have either departed or for which tracking has begun. STA
freeze suppression can be overridden by the entry of a “direct” command to freeze an aircraft’s
STA, from the TGUI for example. The designation of an airport as an STA freeze suppression
airport, the associated arrival airport, and the level of STA freeze suppression are specified in
adaptation.

Standard Terminal Automation Replacement System (STARS):    The replacement to the
present ARTS system in the TRACON. The first STARS system is scheduled for Boston
TRACON in late 1997.

Staggered Approach: A condition in which two aircraft are simultaneously approaching parallel
runways that are not separated by a sufficient distance to allow a simultaneous approach. In this
case, the required separation is achieved by causing one aircraft to be substantially ahead of the
other during the approach and landing.

Statistical Delay Information (SDI): Information compiled by TMA summarizing flights
experiencing major air traffic delays. This information is similar to their type of information
gathered in the National Airspace Performance Reporting System (NAPRS).

Static Site Adaptable Scheduler Data:           Any input data containing site specific parameters
or logic that can impact the TMA scheduler (i.e., general airspace, routing, runways, or DP
scheduler data), but cannot be modified via command line option or user input during operation.
Examples of this type of data are all in the site data system directory and include
                General:      runways
                Routing:      analysis_categories
                Runway:       dp_runway_category_definitions
                Scheduler:    stream_classes

Stream Class: The set of aircraft of specific type(s) that will cross a particular scheduling meter
fix (e.g., all jets crossing LANDR). Within a stream class, all aircraft must maintain a specified
minimum miles-in-trail separation at the scheduling meter fix. For aircraft in different stream
classes, there may be no in-trail separation requirements at the scheduling meter fix.

Stream Class Decision Tree: A list of rules found in the site adaptation that assign an aircraft to
a stream class. The stream class decision tree examines an aircraft's assigned CTAS meter fix, its
engine type, the anticipated airport arrival configuration, its departure fix, and its filed altitude.


                                                 158                              TMA System Spec
                                                                                     FAA-E-2971
                                                                                17 December 2008
                                                                                      Final Rev N

Special Use Airspace (SUA): Is an airspace wherein limitations may be imposed upon aircraft
operations. Types of Special Use Airspace areas are Prohibited Areas, Restricted Areas, Military
Operations Areas, Warning Areas, Alert Areas, Controlled Firing Areas, and National Security
Areas.

Super Stream Class: The set of one or more stream classes that have a combined miles-in-trail
separation constraint.

System Flight Time: The total time of flight remaining to all aircraft in the TMA system if all
the aircraft behave as predicted by the arrival plan. This time is used as a metric to determine the
relative benefit of one arrival plan versus another.

System Management: A primary functional component of TMA that monitors the health of the
hardware and software. It also provides control functions to start and stop TMA operations.

System Management Console (SMC):             A TMA workstation with a Graphical User Interface
that allows an operator to access the TMA Monitor and Control Functions. The System
Management Console displays the status of all TMA hardware and software, and allows the user
to start, stop, and reconfigure the TMA system.

System Management Coordinator (SMC): The title for an individual who is responsible for
initialization, termination and monitoring the health of TMA.

Terminal Radar Approach Control Facility (TRACON):            Concerned with the approach and
departure portions of IFR flights in relation to a major airport.

TGUI: The acronym that refers to the aggregate of the TMA timeline display, loadgraph display,
and their associated auxiliary displays and controls.

Threshold: The beginning of the arrival runway, and the location of aircraft touchdown used by
TMA in its scheduling calculations.

Time-Based Metering:          A method of restricting aircraft flow by scheduling the time at
which each aircraft should cross a predetermined fix.

Time to Fly (TTF): The time (either predicted or actual) for an aircraft to fly along a
prescribed route from one specified location (on the route) to another.

TMA Internal Departure:     An aircraft that originates “close enough” to the adapted airport
that the TMA scheduler must account for the presence of the aircraft prior to (or soon after) the
aircraft departs.

Tower En Route Control (TEC):           Tower En Route Control aircraft are generally those that fly
at lower altitudes and that are controlled by a series of abutting TRACONs as they proceed along


                                                159                             TMA System Spec
                                                                                   FAA-E-2971
                                                                             17 December 2008
                                                                                     Final Rev N
their route of flight. They are not in contact with the overlying ARTCC. Very often, they are
turboprop aircraft.

Track Time:    The time associated with a radar track report.

TRACON Acceptance Rate (TAR): A dynamic input parameter specifying the number of
arriving aircraft (measured at the TRACON boundary) that the TRACON airspace can accept
from the ARTCC per hour. TRACON Acceptance Rate is used to calculate the desired interval
between successive arrival aircraft.

TRACON Altitude Profile: A complete prescription for the altitude profile of an aircraft's
flight in the TRACON. This is a list of altitudes and distances from the runway at which they are
to become effective. The TRACON Altitude Profile is part of the site adaptation and is
associated with each TRACON route.

Traffic Management Advisor (TMA):              A primary functional component of TMA that
generates runway assignments, landing sequences, and schedules arriving aircraft to runway
threshold and meter fix. It also assists in runway configuration control and flow management.

Traffic Management Coordinator (TMC): The title for an individual air traffic controller
located in the Traffic Management Unit who is responsible for metering traffic as it flows into
and out of the Center or TRACON. Under TMA, the person performing the system-wide
management of air traffic. This person communicates directly with area supervisors (as opposed
to communicating directly with pilots). A typical function is that of metering operations, for
example, closing gates or controlling the volume to meet acceptable rates. Also known simply as
Traffic Manager.

Trajectory Synthesis (TS): A TMA process responsible for converting a predicted ground
track into a complete four-dimensional predicted trajectory. This is done using knowledge of
each aircraft's flight capabilities and arrival procedures. TS is usually defined to be Essential
and Restartable.

True Air Speed (TAS):        The rate of travel of an aircraft relative to the air mass in which it
is flying. The True Air Speed vector is the Ground Speed vector minus the Wind vector.

Unimpeded Flight: An aircraft that is allowed to follow its assigned flight path without being
impeded by separation constraints to other aircraft and with no weather or air traffic control
restrictions are placed on the aircraft flight.

Universal Time Coordinated (UTC): Also called Zulu time or Greenwich Mean Time (GMT).

Vertex:        A fix that is also the endpoint of a route segment and to which aircraft are
frequently scheduled. These points are usually Coordination Fixes, Outer Meter Arcs, CTAS
Meter Fixes, Scheduling Meter Fixes/Meter Fix Arcs, and Final Approach Fixes.



                                                160                              TMA System Spec
                                                                                        FAA-E-2971
                                                                                  17 December 2008
                                                                                          Final Rev N
Visual Flight Rules (VFR): Rules governing the procedures for conducting non-instrument
flight. Aircraft operating under Visual Flight Rules are not required to file a flight plan and are
not monitored by TMA.

Wake Vortex Separation Matrix: A separation rule found in FAA Order 7110.65 for safe
operation with respect to wake vortex turbulence. The nXn matrix contains separation
requirements for leading and trailing aircraft and is a data parameter that can only be changed at
the national level. The size of the wake vortex separation matrix is a data parameter and can only
be changed at the national level.




                                                161                              TMA System Spec
                                                                                FAA-E-2971
                                                                           17 December 2008
                                                                                 Final Rev N
            APPENDIX A. SOURCE OF REQUIREMENTS [deleted]

[Appendix A, including Table A-1, has been deleted. The appendix was used at the beginning of
development of TMA Build 2 to identify whether the requirement was met by the Build 1 code,
the NASA Prototype, or was a new requirement for Build 2. The appendix was not updated to
address requirements added as the result of Requirement Problem Reports (RPRs) generated
throughout the development of Build 2. Which RPRs may have introduced which requirements
can be ascertained from the RPR status table at the front of this System Specification.




                                            A-1                            TMA System Spec
                                FAA-E-2971
                           17 December 2008
                                 Final Rev N




Page Intentionally Blank




           A-2             TMA System Spec
                                                            FAA-E-2971
                                                       17 December 2008
                                                             Final Rev N
      APPENDIX B. ANTECEDENT AND CONSEQUENCE FUNCTIONS
                  FOR ORDERING RULES IN FAST [deleted]

Appendix B, including Figures B-1, B-2, B-3, B-4, B-5, B-6, B-7, B-8, B-9, B-10, B-11, B-12, B-
13, B-14, and B-15, has been deleted.




                                             B-1                            TMA System Spec
                                FAA-E-2971
                           17 December 2008
                                 Final Rev N




Page Intentionally Blank




           B-2             TMA System Spec
                                                                                   FAA-E-2971
                                                                              17 December 2008
                                                                                    Final Rev N
                  APPENDIX C. DEFERRED REQUIREMENTS

The implementation of the following requirements has been deferred, and is not reflected in
TMA software release 3.9.0

                            Requirement                        Section
               Shall [0180][i]                           3.2.1.1
               Shall [0221]                              3.2.1.1
               Shall [0225][d]                           3.2.1.1
               Shall [0390] [c]                          3.2.1.3.2
               Shall [0400][h]                           3.2.1.3.2
               Shall [0785]                              3.2.1.5
               Shall [0795][a]                           3.2.1.5.5
               Shall [0985]                              3.2.1.5.1.3
               Shall [1460]                              3.2.1.5.4
               Shall [1470][a-j]                         3.2.1.5.4
               Shall [1480][a-c]                         3.2.1.5.4
               Shall [1490]                              3.2.1.5.4
               Shall [1500]                              3.2.1.5.4
               Shall [1510]                              3.2.1.5.4
               Shall [1516][a, b]                        3.2.1.5.6
               Shall [1518][a-c]                         3.2.1.5.6
               Shall [1519][a-g]                         3.2.1.5.6
               Shall [1522]                              3.2.1.5.6
               Shall [1523]                              3.2.1.5.6
               Shall [1524]                              3.2.1.5.6
               Shall [2291][c]                           3.2.3.1
               Shall [2750][k, x, ll]                    3.2.3.4
               Shall [2842]                              3.2.4
               Shall [3486]                              3.2.7
               Shall [3488]                              3.2.7
               Shall [3501]                              3.2.8
               Shall [3502]                              3.2.8
               Shall [3503]                              3.2.8
               Shall [3536][a - e]                       3.2.11
               Shall [3537][d]                           3.2.11
               Shall [3572]                              3.3.4.3
               Shall [3601]                              3.3.5.2
               Shall [3602]                              3.3.5.2
               Shall [3613]                              3.3.6.2
               Shall [3614]                              3.3.6.2
               Shall [3615]                              3.3.6.3
               Shall [3660]                              3.3.7


                                              C-1                             TMA System Spec
                                                     FAA-E-2971
                                                17 December 2008
                                                      Final Rev N
Shall [3665]                      3.3.10
Shall [3642]                      3.3.13
Shall [3735]                      3.3.14
Shall [3750][f1, f2, h-j]         3.6
Shall [3890][r, z]                3.6
Shall {4624} [b]                  3.2.1.5.8.1




                            C-2                 TMA System Spec
                                                                           FAA-E-2971
                                                                      17 December 2008
                                                                            Final Rev N
APPENDIX D. RPRs Entered into System Specification as of TMA Software Release 3.9.0.

   DDTS # and RPR # assigned to each RPR in the DDTS database.
   CSC Letter: Date of letter transmitting the final version of RPR approved by FAA iCCB
   Dispositioned RPRs: X= Final wording entered; NC= No change to System Specification;
   R=Rejected; D= Duplicate; S= Superseded; P=Postponed; L= Closed & transferred, FAST
   related, N/A for TMA


   RPR #       DDTS #         CSC Letter    Entrd                     Comments
    001       CSCnj00007       07/03/97      X                     New SHALL 2915
    002       CSCnj00013       07/03/97      X
    003       CSCnj00014       07/03/97      X
    004       CSCnj00015       07/03/97      R                 (no change to Specification)
    005       CSCnj00020       08/15/97      X
    006       CSCnj00021       01/20/98      X                     New SHALL 0235
    007       CSCnj00022       08/15/97      X
    008       CSCnj00023       01/20/98      X
    009       CSCnj00028       01/20/98      X              New SHALL 0825, 1215, 1217
    010       CSCnj00030       01/20/98      X                 New SHALL 1165, 1166
    011       CSCnj00031       06/07/99      X       New SHALL 3672, 3674, 3676. Still need CSCI ID
                                                              name & reference number.
     012      CSCnj00621        07/03/97      R              (no change to Specification)
     013      CSCnj00622        08/15/97      X
     014      CSCnj00623        07/03/97      X
     015      CSCnj00625        07/03/97      X
     016      CSCnj00626        07/03/97      R                (no change to Specification)
     017      CSCnj00627        07/03/97      X                     New SHALL 0023
     018      CSCnj00628        07/03/97      X
     019      CSCnj00629        07/03/97      X
     020      CSCnj00632        01/20/98      X                  New SHALL 1451, 1452
     021      CSCnj00633        07/03/97      X
     022      CSCnj00636        08/26/97      R                 (no change to Specification)
     023      CSCnj00639        07/03/97      X                      New SHALL 2296
     024      CSCnj00640           N/A        R      (no change to Specification—covered by RPR-053)
     025      CSCnj00648        07/03/97      X                      New SHALL 0143
     026      CSCnj00649        07/03/97      X
     027      CSCnj00660         7/27/98      X                  New SHALL 0065, 0067
     028      CSCnj00661        08/15/97      R                (no change to Specification)
     029      CSCnj00662        08/15/97      X
     030      CSCnj00663        07/22/97      X
     031      CSCnj00689         7/27/98      X
     032      CSCnj00688        01/20/98      X


                                              D-1                               TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                     Comments
 033    CSCnj00705     3/17/98     R                 (no change to Specification)
 034    CSCnj00653    08/15/97     X
 035    CSCnj00655    07/07/99     X
 036    CSCnj00656    08/26/97     X
 037    CSCnj00659    01/20/98     R                 (no change to Specification)
 038    CSCnj00702    12/08/97     X
 039    CSCnj00704    07/22/97     X
 040    CSCnj00624    07/22/97     X
 041    CSCnj00706       N/A       R                  (no change to Specification)
 042    CSCnj00707       N/A       R      (no change to Specification—determined not to be a
                                                               problem)
 043    CSCnj00710    08/15/97     R                  (no change to Specification)
 044    CSCnj00696    06/07/99     X                     Clarified in RPR-285
 045    CSCnj00697    07/22/97     X
 046    CSCnj00695    08/15/97     X
 047    CSCnj00691    12/08/97     X
 048    CSCnj00693    01/20/98     R                 (no change to Specification)
 049    CSCnj00687    08/15/97     X
 050    CSCnj00703    01/20/98     X               New SHALL 0791, 0792, 0793
 051    CSCnj00698    01/20/98     X
 052    CSCnj00701    08/15/97     X
 053    CSCnj00692      N/A        D        Duplicate to the following Data Recording &
                                           Playback RPRs: 257, 258, 260, 276, 353 & 387
 054    CSCnj00658      N/A        R      (no change to Specification—superseded by RPR-
                                                                 061)
 055    CSCnj00685    08/26/97     X
 056    CSCnj00684    12/08/97     X
 057    CSCnj00647    01/20/98     X            New SHALL 0017 (seems incongruous)
 058    CSCsn00002      N/A        R      (no change to Specification—determined not to be a
                                                               problem)
 059    CSCnj00734    01/20/98      R                 (no change to Specification)
 060    CSCnj00743    08/15/97     X                       New SHALL 0256
 061    CSCnj00719    12/08/97     X
 062    CSCnj00736       N/A        R       (no change to Specification--OBE by RPR-159)
 063    CSCnj00737     7/27/98     X
 064    CSCsn00001       N/A        R       (no change to Specification--OBE per RPR-159)
 065    CSCnj00694       N/A        R      (no change to Specification—OBE per RPR-159)
 066    CSCnj00747    08/15/97     NC
 067    CSCnj00739    08/15/97     NC
 068    CSCnj00748     7/27/98     X
 069    CSCnj00637    08/15/97     X                     New SHALL 1435
 070    CSCnj00746    01/20/98     X
 071    CTSrv00002    08/15/97     X


                                   D-2                                TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                    Comments
 072    CSCnj00770    08/15/97     X
 073    CSCnj00771    08/15/97     X
 074    CSCnj00773    08/15/97     X
 075    CSCnj00766    08/15/97     X
 076    CSCnj00768    08/15/97     X
 077    CSCnj00769    08/15/97     X
 078    CSCnj00772    08/15/97     X
 079    CSCnj00498    01/20/98     X
 080    CSCnj00745    08/26/97     X
 081    CSCnj00738    08/26/97     NC
 082    CSCnj00776    08/26/97     X
 083    CSCnj00777    12/08/97     X           P3I requirements will be noted in RTM
 084    CSCnj00779    08/26/97     X
 085    CSCnj00778    08/26/97     X
 086    CSCnj00780    01/20/98     X                    New SHALL 2995
 087    CSCnj00781    08/26/97     X
 088    CSCnj00735    12/30/98     X                     New SHALL 4034
 089    CSCnj00791    08/26/97     X                  New SHALL 0221, 0222
 090    CSCnj00792    08/26/97     X                  New SHALL 1571, 1572
 091    CSCnj00617       N/A        R         (no change to Specification—not needed)
 092    CSCnj00814    01/20/98     X                     New SHALL 0855
 093    CSCnj00810       N/A        R     (no change to Specification—OBE per RPR-170)
 094    CSCnj00812    08/15/97     X
 095    CSCnj00690    12/08/97     X              New SHALL 0794, 0797, 0798
 096    CTSrv00003    08/26/97     X                   New SHALL 4085
 097    CSCnj00784    07/07/99     X                   New SHALL 0812
 098    CSCnj00825    08/26/97     X
 099    CSCnj00858    08/26/97     X
 100    CSCnj00859    08/26/97     X
 101    CTSrv00004    08/26/97     X            New SHALL 1565, 2794, 2795, 2796
 102    ARCpr02711    08/15/97     X
 103    CSCnj00926    01/20/98     X
 104    CSCnj00935    12/08/97     X                       New SHALL 0224
 105    CSCnj00937    12/08/97     X           Used 1574 vice 1572 for new SHALL
 106    CSCnj00938     7/27/98     X            New SHALL 0146, 0147, 0148, 0149
 107    CSCnj00940     7/27/98     X       New SHALL 1531, 1532, 1533, 1534, 1535,
                                                               1536, 1537
 108    CSCnj00934    12/08/97     X             Still to do: reword intro paragraphs
 109    ARCpr02712     3/17/98     X      New SHALL 2556, 2558, 2562, 2563, 2564, 2568,
                                          2572, 2573, 2574, 2576, 2578, 2582, 2584, 2586,
                                                    2588, 2592, 2594, 2596, 2598
 110    CSCnj00965    12/08/97     X



                                   D-3                               TMA System Spec
                                                                   FAA-E-2971
                                                              17 December 2008
                                                                    Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                 Comments
 111    CSCnj00966    01/20/98      R            (no change to Specification)
 112    CSCnj00967    12/08/97      R            (no change to Specification)
 113    CSCnj00968    12/08/97      R            (no change to Specification)
 114    CSCnj00969    12/08/97      R            (no change to Specification)
 115    CSCnj00970     2/23/98     NC              Superseded by RPR-106.
 116    CSCnj00971     2/23/98     NC              Superseded by RPR-106.
 117    CSCnj00972    12/08/97      R            (no change to Specification)
 118    CSCnj00973    12/08/97     X
 119    CSCnj00974    12/08/97     X             CHI specification referenced
 120    CSCnj00975    12/08/97      R            (no change to Specification)
 121    CSCnj00976    12/08/97     X
 122    CSCnj00977    12/08/97     X
 123    CSCnj00978    01/20/98      R            (no change to Specification)
 124    CSCnj00979    01/20/98      R            (no change to Specification)
 125    CSCnj00980     7/27/98      R            (no change to Specification)
 126    CSCnj00981    01/20/98     X                  New SHALL 0581
 127    CTSrv00001    11/13/98     X                  New SHALL 0982
 128    CSCnj00988    01/20/98     X
 129    CSCnj00994                  P                   POSTPONED
 130    ARCpr02871       N/A       D       Duplicate of RPR-642 (10/04/00-DDTS)
 131    CSCnj00995       N/A       D       Duplicate of RPR-636 (02/28/01-DDTS)
 132    CSCnj00997    12/08/97     X           New SHALL 0342, 0344, 0346
 133    CSCnj01006     7/27/98     X           New SHALL 0352, 0354, 0356
 134    CSCnj01011    12/08/97     X
 135    CSCnj00982       N/A        R     (no change to Specification—OBE because
                                                      automated M-i-T)
 136    CSCnj00987    12/08/97     X                  New SHALL 1155
 137    CSCnj01015    01/20/98      R            (no change to Specification)
 138    CTSrv00010    12/08/97     X
 139    CTSrv00011    01/20/98     X
 140    CSCnj01032     3/17/98     X
 141    CTSrv00013     7/27/98     X
 142    CTSrv00014    12/08/97     X        New SHALL 0867, 0868, 1964, 1966
 143    CSCnj01037    07/27/99     X             New SHALL 0276, 1626
 144    CSCnj01038       N/A       D              Duplicate of RPR 634.
 145    ARCpr02924    12/08/97     X
 146    ARCpr02927    12/08/97      R            (no change to Specification)
 147    ARCpr02928    12/30/98      R            (no change to Specification)
 148    ARCpr02929    12/30/98      R            (no change to Specification)
 149    ARCpr02930    12/08/97     X
 150    ARCpr02931    12/08/97      R            (no change to Specification)
 151    CSCnj01041    12/08/97     NC     CHI specification (superceded by RPR-467)



                                   D-4                            TMA System Spec
                                                                        FAA-E-2971
                                                                   17 December 2008
                                                                         Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                      Comments
 152    CSCnj01042       N/A       R        (no change to Specification) (08/02/00-DDTS)
 153    CSCnj01043       N/A       R                 (no change to Specification)
 154    CSCnj01044       N/A       R        (no change to Specification) (08/02/00-DDTS)
 155    CSCnj01045    12/08/97     X        New SHALL 2848. Superseded by RPR-159.
 156    CSCnj01070    12/08/97     X               New SHALL 0424, 0425, 0426
 157    CSCnj01072    12/08/97     X                      New SHALL 0464
 158    CSCnj01073    12/30/98     X                      New SHALL 0469
 159    CSCnj01103     2/23/98     X         New SHALL 0015, 0021, 0024, 0026, 0085
                                          Supersedes RPRs 1, 2, 3, 13, 14, 17, 18, 19, 25, 26,
                                                      40, 44, 55, 57, 62, 64, 145
 160    CSCnj00999    01/20/98      R                (no change to Specification)
 161    CSCnj01010       N/A        R                (no change to Specification)
 162    CSCnj01059    01/20/98     X                   New SHALL 0275, 1625
 163    ARCpr02998    01/20/98      R                (no change to Specification)
 164    ARCpr02993    01/20/98     X
 165    ARCpr02994     3/17/98      R                (no change to Specification)
 166    ARCpr02995    12/30/98      R                (no change to Specification)
 167    CSCnj01095     3/17/98     X
 168    CSCnj01094    01/20/98     X
 169    ARCpr03107    01/20/98      R                (no change to Specification)
 170    CSCnj01115    01/20/98     X
 171    CSCnj01116    01/20/98     X                   New SHALL 0332, 0334
 172    ARCpr02999    01/20/98      R                (no change to Specification)
 173    ARCpr03098    01/20/98     X
 174    ARCpr03099    01/20/98     X
 175    ARCpr03100    06/07/99     X
 176    ARCpr03105    01/20/98     X
 177    ARCpr03106    01/20/98      R                (no change to Specification)
 178    ARCpr03109    01/20/98     X
 179    CSCnj01152    06/05/01     NC                     CHI specification
 180    CSCnj01153    01/20/98      R                     CHI specification
 181    CSCnj01155    04/03/00     NC                     CHI specification
 182    CSCnj01156       N/A        R               (no change to Specification)
 183    CSCnj01157    03/05/02      R                (no change to specification)
 184    CSCnj01158    09/13/02      R               (no change to Specification)
 185    CSCnj01159    11/26/02     NC        Closed – OBE, implemented in release 2.1.4
 186    CSCnj01160    07/07/99     NC                     CHI specification
 187    CSCnj01161    01/10/01     NC                     CHI specification
 188    ARCpr03176       N/A        R               (no change to Specification)
 189    ARCpr03181    06/26/00      R                     CHI specification
 190    ARCpr03182    03/05/02     D                    Duplicate of RPR-666
 191    ARCpr03183    01/08/02      R                (no change to specification)



                                   D-5                                  TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                     Comments
 192    ARCpr03185    04/03/00     NC                     CHI specification
 193    ARCpr03186   04/03/00 &    NC                     CHI specification
                      05/04/00
 194    CSCnj01164    09/13/02     S        Initially approved. Subsequently superceded by
                                                               RPR-1041
 195    CSCnj01183
 196    CSCnj01182    11/26/02     R       (no change to Specification – superseded by the
                                                 implementation of Meter Fix Arcs)
 197    CSCnj01181      N/A        R                (no change to Specification)
 198    CSCnj01175      N/A        R                (no change to Specification)
 199    CSCnj01165    01/03/01     X
 200    ARCpr03330      N/A        D                   Duplicate of RPR 888
 201    CSCnj01208                 R
 202    CSCnj01209    07/27/98     X
 203    CSCnj01210    06/07/99     X
 204    CSCnj01211    07/27/98     X
 205    CSCnj01215    07/27/98     X
 206    CSCnj01221    07/27/98     X                     New SHALL 1835
 207    CSCnj01222    07/27/98     X                     New SHALL 1855
 208    CSCnj01228    12/30/98     X
 209    CSCnj01229    07/27/98     X
 210    CSCnj01240    12/30/98     X
 211    CSCnj01231    07/27/98     X
 212    CSCnj01247    07/27/98     X
 213    CSCnj01248    07/27/98     X
 214    CSCnj01230    07/27/98     X
 215    CSCnj01261    07/27/98     X
 216    CSCnj01709    12/30/98     X                      New SHALL 0331
 217    CSCnj01708     N/A*        R        (no change to Specification – superseded by the
                                                  implementation of Meter Fix Arcs)
 218    CSCnj01746      N/A         R                (no change to Specification)
 219    CSCnj01951    12/30/98      R                (no change to Specification)
 220    CSCnj01973    06/07/99     X             New SHALL 2892, 2894, 2896, 2898
 221    CSCnj01974    10/22/99     NC      CHI specification; New shalls 5700, 5705, 5710,
                                          5715, 5720, 5725, 5730, 5735, 5740, & 5745. Still
                                                      need to input new Figure.
 222    CSCnj01975    07/07/99     NC                      CHI specification
 223    CSCnj02093                  R                (no change to Specification)
 224    CSCnj02296    12/30/98     X      New SHALL 3511, 3512, 3513, 3514, 3515, 3516,
                                           3517, 3518, 3519, 3521, 3522, 3523, 3524, 3525
 225    CSCnj02297    12/30/98     X                      New SHALL 3665
 226    CSCnj02319    06/07/99     X             New SHALL 3682, 3684, 3686, 3688
 227    CSCnj02440    06/07/99     NC                  Superseded by RPR-235
 228    CSCnj02557    06/07/99     NC                         ARTS IRD



                                   D-6                                TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
 229    CSCnj02558    06/07/99     NC                     ARTS ICD
 230    CSCrv00074    06/07/99     NC                   CHI specification
 231    CSCrv00113    06/07/99     X
 232    CSCrv00093    06/07/99     NC                   CHI specification
 233    CSCnj02568      N/A         R              (no change to Specification)
 234    CSCnj03284    06/07/99     NC                   CHI specification
 235    CSCnj03675    06/07/99     X
 236    ARCpr04027      N/A        D      Duplicate to following Internal Departure RPRs:
                                            CSCnj01165, CSCnj04665, CSCnj04680;
                                            CSCnj04681; CSCnj04682; CSCnj04684;
                                            CSCnj04686; CSCnj04712; CSCnj04713;
                                            CSCnj04714; CSCnj04715; CSCnj04727;
                                            CSCnj04728; CSCnj04729; CSCnj04730;
                                            CSCnj04732; CSCnj04733; CSCnj04734;
                                            CSCnj04635; CSCnj04737; CSCnj04739;
                                           CSCnj04741; CSCnj04742; CSCnj04743; &
                                                            CSCnj04745
 237    ARCpr04028    05/04/00      R                No change to specification
 238    ARCpr04029    05/04/00      R                No change to specification
 239    ARCpr04030    06/05/00      R               (no change to Specification)
 240    CSCnj03966    06/07/99     X
 241    CSCnj04006    06/07/99     X
 242    CSCnj04007    12/10/99     X                     New shall 0254
 243    CSCnj04008      N/A         R              (no change to Specification)
 244    CSCnj04009    06/07/99     X
 245    CSCnj03961      N/A        D                  Duplicate to RPR-427
 246    CSCnj04301    07/07/99     X
 247    CSCnj04302    07/07/99     X
 248    CSCnj04304    07/07/99     X
 249    CSCnj04281    10/22/99      S            Superceded by RPRs 409 & 410
 250    ARCpr04356    09/20/99     X
 251    ARCpr04382    07/07/99     X
 252    ARCpr04385    07/07/99     X                    New SHALL 3225
 253    ARCpr04389    07/27/99     X
 254    ARCpr04391    07/07/99     X
 255    ARCpr04396    07/07/99     NC         Duplicates 3225 inserted by RPR-252.
 256    ARCpr04398    07/07/99     X                   Voids section 3.2.6
 257    ARCpr04399    07/07/99     X                   New SHALL 3442
 258    ARCpr04400    07/07/99     X
 259    ARCpr04401    07/07/99     X                  Voids section 3.2.6.1.2
 260    ARCpr04403    07/07/99     X
 261    ARCpr04404    07/07/99     X
 262    ARCpr04381
 263    ARCpr04383    03/02/01     NC                   CHI specification


                                   D-7                               TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
 264    ARCpr04384    01/10/01     NC                     CHI specification
 265    ARCpr04386    03/02/01     NC                     CHI specification
 266    ARCpr04387    10/04/02      R                (no change to Specification)
 267    ARCpr04388    01/03/01     NC                     CHI specification
 268    ARCpr04390    01/17/01     NC                     CHI specification
 269    ARCpr04392    01/17/01     NC                     CHI specification
 270    ARCpr04394      N/A        D                    Duplicate of RPR 514
 271    ARCpr04395    01/02/03      R                (no change to Specification)
 272    ARCpr04397    03/02/01     NC                     CHI specification
 273    ARCpr04410    10/22/99      S                  Superceded by RPR-410
 274    ARCpr04406    01/03/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 275    ARCpr04405    10/22/99     S            Superceded by RPR-445 & RPR-446
 276    ARCpr04402    07/07/99     X                      Assume wording.
 277    CSCnj04442
 278    ARCpr04393    07/07/99     X
 279    CSCnj04476    07/27/99     X
 280    CSCnj04477    07/27/99     X
 281    ARCpr04493    10/22/99     X
 282    CSCnj04575    10/22/99     X
 283    ARCpr04492    08/23/05     X                New SHALLs 0787 a-c
 284    CSCnj04482    10/22/99     X           New shalls: 0161-0166; 1544-1546
 285    CTSrv00134    09/27/00     NC                  CHI Specification
 286    ARCpr04423      N/A         R             (no change to Specification)
 287    ARCpr04420      N/A         R             (no change to Specification)
 288    ARCpr04516    05/04/00     NC                  CHI Specification
 289    CSCnj04303    10/22/99     X
 290    ARCpr04484    09/20/99      S                  Superceded by RPR-410
 291    ARCpr04301      N/A         R                (no change to Specification)
 292    ARCpr04300    09/20/99      S                  Superceded by RPR-410
 293    ARCpr04298    03/05/02      S     Initially approved. Subsequently superceded by
                                                             RPR-1045
 294    CSCnj04602      N/A         R                (no change to Specification)
 295    CSCnj04604      N/A         R                (no change to Specification)
 296    CSCnj04606    09/20/99      R                (No change to Specification)
 297    CSCnj04639    10/22/99     NC                     CHI specification
 298    ARCpr04566    09/20/99     X
 299    ARCpr04572    12/10/99      R              (no change to Specification)
 300    ARCpr04604    09/20/99     X                 New shalls 1525 & 1526
 301    ARCpr04605    09/20/99     X                     New shall 1601
 302    ARCpr04606    09/20/99     X                     New shall 1602
 303    ARCpr04613    06/05/00     NC               Adaptation/Software ICD




                                   D-8                              TMA System Spec
                                                            FAA-E-2971
                                                       17 December 2008
                                                             Final Rev N
RPR #    DDTS #      CSC Letter   Entrd          Comments
 304    CSCnj04686    09/15/99     X
 305    CSCnj04665    10/22/99     X            New shall 1965
 306    CSCnj04680    09/15/99     X
 307    CSCnj04681    10/22/99     X        New shalls 0748, 0749
 308    CSCnj04682    09/15/99     X
 309    CSCnj04684    09/15/99     X
 310    CSCnj04712    09/15/99     X
 311    CSCnj04713    09/15/99     X
 312    CSCnj04714    09/15/99     X
 313    CSCnj04715    09/15/99     X
 314    CSCnj04727    09/15/99     X
 315    CSCnj04728    09/15/99     X
 316    CSCnj04729    09/15/99     X
 317    CSCnj04730    09/15/99     X
 318    CSCnj04732    09/15/99     X            New shall 2765
 319    CSCnj04733    05/04/00     NC          CHI Specification
 320    CSCnj04734    10/25/99     X        New shalls 0801-0802
 321    CSCnj04735    09/15/99     X            New shall 0747
 322    CSCnj04737    10/25/99     NC          CHI specification
 323    CSCnj04739      N/A        D      Duplicate of RPR-534 (CHI)
 324    CSCnj04742    05/04/00     NC          CHI specification
 325    CSCnj04743    09/15/99     NC          CHI specification
 326    CSCnj04741    05/04/00     NC          CHI specification
 327    CSCnj04745    09/15/99     NC          CHI specification
 328    ARCpr04619    10/22/99     NC      Adaptation/Software ICD
 329    ARCpr04630    09/07/01     X          Shall 0320 deleted
 330    ARCpr04631    09/20/99     NC      Adaptation/Software ICD
 331    ARCpr04632    10/22/99     NC      Adaptation/Software ICD
 332    ARCpr04633    09/20/99     NC      Adaptation/Software ICD
 333    ARCpr04634    09/20/99     NC      Adaptation/Software ICD
 334    ARCpr04635    01/22/01     NC      Adaptation/Software ICD
 335    ARCpr04636    09/20/99     NC      Adaptation/Software ICD
 336    ARCpr04637    09/20/99     NC      Adaptation/Software ICD
 337    ARCpr04638    10/22/99     NC      Adaptation/Software ICD
 338    ARCpr04639    10/22/99     NC      Adaptation/Software ICD
 339    ARCpr04640    10/25/99     NC      Adaptation/Software ICD
 340    ARCpr04641    09/20/99     NC      Adaptation/Software ICD
 341    ARCpr04663    09/20/99     X             Item n not m
 342    CSCnj04747    09/20/99      S      Superceded by RPR-410
 343    ARCpr04668    01/03/01     X
 344    CSCnj04768      N/A         R     (no change to Specification)




                                   D-9                     TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
 345    ARCpr04661    09/15/99      R              (no change to Specification)
 346    ARCpr04660    09/15/99     X
 347    ARCpr04670    10/25/99     X                     New shall 2091
 348    ARCpr04671    12/10/99      S               Superceded by RPR-444
 349    CSCnj04767      N/A        D               Duplicate of RPR-322 (CHI)
 350    CSCnj04761    02/24/00     X
 351    CSCnj04798    10/25/99     NC                   CHI specification
 352    CSCnj04799    10/22/99     NC              Adaptation/Software ICD
 353    ARCpr04664    10/22/99     X         New shalls 3449, 3474-3476, 3481-3484
 354    CSCnj04842    10/25/99     NC              Adaptation/Software ICD
 355    CSCnj04843      N/A         R             (no change to Specification)
 356    ARCpr04685
 357    ARCpr04667    10/22/99     NC               Adaptation/Software ICD
 358    ARCpr04652    12/10/99     X                    New shall 3451
 359    ARCpr04651    10/22/99     X
 360    ARCpr04535    10/25/99     X
 361    CSCnj04871     2/22/05      R
 362    ARCpr04696    10/25/99     X                     New shall 1955
 363    ARCpr04590
 364    CSCnj04874    10/22/99     X                     New shall 3526
 365    ARCpr04662    10/25/99     X
 366    ARCpr04581     8/23/05     NC                   CHI specification
 367    ARCpr04582    10/25/99     X
 368    ARCpr04578    03/12/01     X                New shalls 1513, 1514
 369    CSCnj04688    01/03/01     X             New shalls 0237, 0361, & 0362
 370    ARCpr04421    10/25/99     X
 371    ARCpr04618
 372    ARCpr04677    10/25/99     R               (No change to specification)
 373    ARCpr04422    10/25/99     X
 374    ARCpr04534    01/02/03     R      (no change to Specification – superseded by the
                                                implementation of Meter Fix Arcs)
 375    CSCnj04942    10/25/99     NC               Adaptation/Software ICD
 376    ARCpr04730    10/25/99     NC               Adaptation/Software ICD
 377    ARCpr04732    10/25/99     NC               Adaptation/Software ICD
 378    CSCnj04934      N/A         R
 379    CSCnj04948    10/25/99     X
 380    CSCnj04900                  P                     Postponed*
 381    ARCpr04733    12/10/99     NC               Adaptation/Software ICD
 382    ARCpr04731    12/10/99     NC               Adaptation/Software ICD
 383    ARCpr04729    12/10/99     NC               Adaptation/Software ICD
 384    ARCpr04739    12/10/99     NC               Adaptation/Software ICD
 385    ARCpr04740    12/10/99     NC               Adaptation/Software ICD



                                   D-10                              TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
 386    ARCpr04741    12/10/99                            Not implemented
 387    CSCnj04975    12/10/99     X                   New shalls 3492 - 3497
 388    CSCnj04973    02/24/00     NC                     CHI specification
 389    CSCnj04974    12/10/99     NC                     CHI specification
 390    CTSrv00430    12/10/99      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 391    ARCpr04747    01/02/03      R                (no change to Specification)
 392    CSCnj04972    12/10/99     NC                 Adaptation/Software ICD
 393    ARCpr04772    12/10/99     NC                 Adaptation/Software ICD
 394    ARCpr04773    12/10/99     NC                 Adaptation/Software ICD
 395    CSCnj05048    12/10/99     X
 396    ARCpr04746     1/31/00     X                     New shall 2263
 397    ARCpr04763    06/05/00     X                     New shall 0144
 398    ARCpr04776     2/22/05      R
 399    CSCnj05079    01/03/01     NC                   CHI specification
 400    CSCnj05087
 401    CSCnj05088     N/A*        R              (no change to Specification)
 402    CSCnj05089    03/05/01     R              (no change to Specification)
 403    CSCnj05090      N/A        R      (no change to Specification – already done by
                                                        controlling GUIs)
 404    CSCnj05175      N/A         R             (no change to Specification)
 405    CSCnj05188    01/07/00     NC                   CHI specification
 406    CSCnj05189    01/07/00     NC                   CHI specification
 407    CSCnj05190    01/07/00     NC                   CHI specification
 408    CSCnj05191    01/07/00     NC                   CHI specification
 409    CSCwb00016    01/07/00     X                     New shall 2521
 410    CSCwb00020    01/07/00     NC                   CHI specification
 411    CSCnj05151    01/07/00     X
 412    CSCwb00022    01/31/00     X
 413    CSCwb00023    01/31/00     X
 414    CSCwb00024    03/05/01     X
 415    CSCnj05220    02/24/00     NC                  CHI specification
 416    CSCnj05221    05/04/00     NC                  CHI specification
 417    CSCnj05152    01/03/01     NC               Adaptation/Software ICD
 418    CSCwb00025    01/31/00     X
 419    ARCpr04813    01/31/00     X          New shalls 2011, 2012, 0811, & 0813
 420    ARCpr04814    01/31/00     NC              Adaptation/Software ICD
 421    CSCnj05239    06/26/00     X
 422    CSCnj05263    01/07/00     X                     New shall 0236
 423    CSCnj05265    01/31/00     NC                   CHI specification
 424    CSCnj05274    01/31/00     NC                   CHI specification
 425    CSCnj05153


                                   D-11                             TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 426    CSCnj05154
 427    CSCwb00026    01/31/00     X
 428    CSCwb00027    01/31/00     NC                     CHI specification
 429    CTSrv00553      N/A         R                (no change to Specification)
 430    CSCnj05270    01/31/00     X
 431    CTSrv00555    01/31/00     NC                      CHI specification
 432    CSCwb00030    01/31/00     X      New shalls 3231,3245,3321,3322,3362,3365, 3366
 433    ARCpr04824     N/A*         R      (no change to Specification – superseded by the
                                                   implementation of Meter Fix Arcs)
 434    CSCnj05313    01/31/00     NC                      CHI specification
 435    CSCnj05314    01/31/00     NC                      CHI specification
 436    CSCnj05321    01/31/00     NC                      CHI specification
 437    CSCnj05340      N/A        D             Duplicate of CSCwb00024 (RPR-414)
 438    CSCnj05342      N/A        D             Duplicate of CSCwb00024 (RPR-414)
 439    CSCnj05343      N/A        D             Duplicate of CSCwb00024 (RPR-414)
 440    CSCnj05379    02/24/00     NC                   Adaptation/Software ICD
 441    CSCnj05383    02/24/00     NC                   Adaptation/Software ICD
 442    CSCnj05384    02/24/00     NC                   Adaptation/Software ICD
 443    CSCnj05387    02/24/00     NC                   Adaptation/Software ICD
 444    CSCwb00036    02/24/00      S       Initially approved. Subsequently superceded by
                                                               RPR-1015
 445    CSCwb00037    02/24/00     X
 446    CSCwb00038    02/24/00     S        Initially approved. Subsequently superceded by
                                                               RPR-1041
 447    CSCwb00039       N/A       D         Duplicate of CSCwb00075 (RPR-467) (CHI)
 448    CSCwb00034     2/22/05      R
 449    ARCpr04844    04/03/00     X
 450    CTSrv00592    02/24/00     NC                    CHI specification
 451    CTSrv00593    02/24/00     NC                    CHI specification
 452    CTSrv00595    02/24/00     NC                    CHI specification
 453    CTSrv00596    05/04/00     NC                    CHI specification
 454    CTSrv00599    02/24/00     NC                    CHI specification
 455    CTSrv00602    04/03/00     NC                    CHI specification
 456    CTSrv00603    02/24/00     NC                    CHI specification
 457    CSCwb00045       N/A       D                Duplicate of RPR-534 (CHI)
 458    CSCnj05437    02/24/00     NC                Adaptation/Software ICD
 459    CSCnj05456    02/24/00     NC                    CHI specification
 460    CSCwb00044    03/05/02      R               (no change to specification)
 461    CTSrv00618    05/04/00     NC                    CHI specification
 462    CSCnj05480    06/26/00     NC                Adaptation/Software ICD
 463    CTSrv00617   04/03/00 &    NC                    CHI specification
                      05/04/00
 464    CTSrv00621    05/04/00     NC                     CHI specification



                                   D-12                               TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 465    CTSrv00622    04/03/00     NC                   CHI specification
 466    CSCnj05559    04/03/00     NC                Adaptation/Software ICD
 467    CSCwb00075    05/04/00     NC                   CHI specification
 468    CSCwb00088    04/03/00     NC                Adaptation/Software ICD
 469    CSCwb00054    04/03/00     X
 470    CSCwb00064    01/14/03      R
 471    CTSrv00623    04/03/00     NC                   CHI Specification
 472    ARCpr04840    09/07/01     X                  Partially implemented
 473    CTSrv00652    05/04/00     NC                   CHI specification
 474    CSCnj05049    06/05/00     X              New shalls 0241, 0242, & 0243
 475    CSCwb00047      N/A         R              (no change to Specification)
 476    CSCwb00110    06/05/00     NC                   CHI specification
 477    CSCnj05194
 478    CSCnj05669      N/A        R      (no change to Specification) Rejected (01/25/01-
                                                              DDTS)
 479    CSCnj05668    04/03/00     NC                    CHI specification
 480    CSCnj05667      N/A        D        Duplicate of CSCnj05079 (RPR-399) (CHI)
 481    CTSrv00655    04/03/00     NC                    CHI specification
 482    CTSrv00656    04/03/00     NC                    CHI specification
 483    CTSrv00658    01/03/01     NC                    CHI specification
 484    CTSrv00659      N/A        D        Duplicate of CSCnj04733 (RPR-319) (CHI)
 485    CTSrv00657      N/A         R               (no change to Specification)
 486    CTSrv00660    04/03/00     NC                    CHI specification
 487    CTSrv00661      N/A        D        Duplicate of ARCpr03186 (RPR-193) (CHI)
 488    CTSrv00663      N/A        D        Duplicate of CSCnj04741 (RPR-326) (CHI)
 489    CTSrv00664    04/03/00     NC                    CHI specification
 490    CTSrv00665    04/03/00     NC                    CHI specification
 491    CTSrv00666    04/03/00     NC                    CHI specification
 492    CTSrv00667    04/03/00     NC                    CHI specification
 493    ARCpr04940                  R                Superceded by RPR-1012
 494    CSCwb00084    09/07/01      P              Not implemented/Postponed
 495    CTSrv00689      N/A         R               (no change to Specification)
 496    CTSrv00688    05/04/00     NC                    CHI specification
 497    CTSrv00687    01/10/01     NC                    CHI specification
 498    CTSrv00684      N/A         R               (no change to Specification)
 499    CTSrv00683    05/04/00     NC                    CHI specification
 500    CTSrv00682    05/04/00     NC                    CHI specification
 501    CTSrv00681    05/04/00     NC                    CHI specification
 502    CTSrv00680    05/04/00     NC                    CHI specification
 503    CTSrv00679    10/04/02      R               (no change to Specification)
 504    CSCwb00135    06/05/00     NC                    CHI specification
 505    CSCwb00136    06/05/00     NC                    CHI specification



                                   D-13                              TMA System Spec
                                                                    FAA-E-2971
                                                               17 December 2008
                                                                     Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                  Comments
 506    CSCwb00138    09/08/00     NC                  CHI specification
 507    CSCwb00139    01/03/01     NC                  CHI specification
 508    CSCwb00140    06/26/00      R             (no change to Specification)
 509    CSCwb00141    09/27/00     NC                  CHI specification
 510    CSCwb00146    01/03/01     NC                  CHI specification
 511    CSCnj05695       N/A       D        Duplicate of RPR-542 (06/27/01-DDTS)
 512    CTSrv00690    05/04/00     NC                  CHI specification
 513    CTSrv00691    05/04/00     NC                  CHI specification
 514    CTSrv00692    05/15/00     NC                  CHI specification
 515    CTSrv00693    05/04/00     NC                  CHI specification
 516    CTSrv00694    05/04/00     NC                  CHI specification
 517    CSCnj05957    05/15/00     NC                  CHI specification
 518    CTSrv00703    05/04/00     NC                  CHI specification
 519    CSCwb00171    03/05/01     NC                  CHI specification
 520    CSCwb00172    06/26/00     NC              Adaptation/Software ICD
 521    CSCwb00173    01/03/01     NC                  CHI specification
 522    CSCwb00174    06/05/00     X
 523    CSCwb00180    05/04/00     X
 524    CSCwb00181    09/27/00     NC                   CHI specification
 525    CSCwb00183    09/07/01     NC                   CHI Specification
 526    CTSrv00704    05/04/00     NC                   CHI specification
 527    CTSrv00705    05/04/00     NC                   CHI specification
 528    CTSrv00709    01/03/01     NC                   CHI specification
 529    CTSrv00712    05/04/00     NC                   CHI specification
 530    CSCnj05940    10/16/00     NC                   CHI specification
 531    CTSrv00714    08/23/05     NC                   CHI specification
 532    CTSrv00715    05/04/00     NC                   CHI specification
 533    CTSrv00718    06/05/00     NC                   CHI specification
 534    CTSrv00719    06/05/00     NC                   CHI specification
 535    CSCnj05762    06/05/01     NC               Adaptation/Software ICD
 536    CSCwb00190    11/09/00     NC               Adaptation/Software ICD
 537    CSCnj05768    07/21/04     X                     New shall: 2752
 538    CSCwb00192    01/10/01     NC                   CHI specification
 539    CTSrv00724    06/05/00     NC                   CHI specification
 540    CTSrv00725       N/A        R              (no change to Specification)
 541    CTSrv00732       N/A        R     (no change to Specification) (12/28/00-DDTS)
 542    ARCpr05005     6/20/05      R        no change to specification – Adapt. ICD
 543    CSCwb00208    01/03/01      R              (no change to Specification)
 544    CTSrv00743    06/05/00     NC                   CHI specification
 545    CTSrv00744    06/05/00     NC                   CHI specification
 546    CTSrv00745    06/05/00     NC                   CHI specification




                                   D-14                            TMA System Spec
                                                                    FAA-E-2971
                                                               17 December 2008
                                                                     Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                  Comments
 547    CTSrv00746      N/A         R
 548    CTSrv00753    06/05/00     NC                  CHI specification
 549    CTSrv00754      N/A         R             (no change to Specification)
 550    CSCwb00207    05/15/00     X                    New shall 0814
 551    CSCwb00215      N/A         R             (no change to Specification)
 552    CSCwb00216    06/26/00     NC                  CHI specification
 553    CSCwb00217    06/26/00     NC                  CHI specification
 554    CSCwb00218    06/26/00     NC                  CHI specification
 555    CSCwb00221    06/26/00     X                    New shall 3527
 556    CSCwb00230    06/26/00     X
 557    CTSrv00775    06/26/00     NC                   CHI specification
 558    CTSrv00776    11/09/00     NC               Adaptation/Software ICD
 559    CTSrv00777    11/09/00     NC               Adaptation/Software ICD
 560    CTSrv00785    05/15/00     NC                   CHI specification
 561    CSCwb00222    01/03/01     X                 New shalls 3535 & 3536
 562    CSCwb00223    08/15/01     X                     New shall 3537
 563    CSCwb00224      N/A        D          Incorporated into RPR-562; Duplicate
 564    CSCwb00225      N/A        D          Incorporated into RPR-562; Duplicate
 565    CSCwb00226      N/A         R              (no change to Specification)
 566    CSCnj05909    01/03/01     NC                   CHI specification
 567    CSCwb00228    11/09/00     NC               Adaptation/Software ICD
 568    CSCwb00229    11/09/00     NC               Adaptation/Software ICD
 569    CSCwb00231    11/09/00     NC               Adaptation/Software ICD
 570    CSCwb00233    11/09/00     NC               Adaptation/Software ICD
 571    CTSrv00758    11/09/00     NC               Adaptation/Software ICD
 572    CTSrv00759    11/09/00     NC               Adaptation/Software ICD
 573    CTSrv00760    11/09/00     NC               Adaptation/Software ICD
 574    CTSrv00761    11/09/00     NC               Adaptation/Software ICD
 575    CTSrv00762    11/09/00     NC               Adaptation/Software ICD
 576    CTSrv00763    11/09/00     NC               Adaptation/Software ICD
 577    CTSrv00788    06/26/00     NC                   CHI specification
 578    CTSrv00791    06/26/00     X             New shalls 2559, 2561, & 2565
 579    CSCwb00267    09/08/00     NC               Adaptation/Software ICD
 580    CSCnj05918    01/03/01     NC                   CHI specification
 581    CSCnj05922    09/08/00     NC               Adaptation/Software ICD
 582    CSCwb00269    09/08/00     X                 New shalls 0341 & 1041
 583    CSCnj05920      N/A         R     (no change to Specification) (05/25/01-DDTS)
 584    CSCwb00272      N/A        D        Duplicate of RPR-673) (08/30/01-DDTS)
 585    CTSrv00797    01/03/01     NC                   CHI specification
 586    CSCwb00298    01/10/01     NC                   CHI Specification
 587    CSCwb00317    01/03/01     X



                                   D-15                            TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 588    CTSrv00806    09/08/00     NC                      CHI specification
 589    CTSrv00813    09/27/00     NC                      CHI specification
 590    CSCnj06023    05/23/05     NC                      CHI Specification
 591    CTSrv00815    09/27/00     NC                      CHI specification
 592    CTSrv00825      N/A         R      (no change to Specification) (12/28/00-DDTS)
 593    CTSrv00826    09/27/00     NC                      CHI specification
 594    CTSrv00831    04/27/01      R                 (no change to Specification)
 595    CTSrv00832    10/01/01      R                 (no change to Specification)
 596    CSCnj06097    09/13/02     NC                  Adaptation/Software ICD
 597    CSCwb00365    01/03/01     NC                      CHI specification
 598    CSCwb00366    04/26/01      R                 (no change to Specification)
 599    CTSrv00829    09/08/00     X                    New shalls 0231 & 0232
 600    CTSrv00830    09/07/01      R                 (no change to Specification)
 601    CSCnj06017    01/08/02      R                 (no change to specification)
 602    CTSrv00870    01/03/01     NC                      CHI specification
 603    CTSrv00871    08/15/01     NC                      CHI specification
 604    CSCnj06103    03/02/01      S      Initially approved. Subsequently superceded by
                                                              RPR-1041
 605    CSCnj06105    03/02/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 606    CSCwb00399    01/03/01     NC                      CHI specification
 607    CSCwb00400    01/03/01     NC                      CHI specification
 608    CTSrv00874    01/03/01     NC                      CHI specification
 609    CSCnj06209    03/02/01      S      Initially approved. Subsequently superceded by
                                                              RPR-1041
 610    CSCnj06214     6/20/05     R                   no change to specification
 611    CSCwb00434    10/04/02     R      (no change to Specification - superseded by RPR
                                                                 986)
 612    CTSrv00918    09/07/01     NC                      CHI specification
 613    CTSrv00919    08/15/01     NC                      CHI specification
 614    CTSrv00920    01/02/03      R                 (no change to Specification)
 615    CTSrv00922    01/03/01     NC                      CHI specification
 616    CSCnj06245    08/15/01     NC                     HNL 320 patch IRD
 617    CSCwb00442    01/10/01     NC                      CHI Specification
 618    CSCwb00466    03/02/01     NC                      CHI specification
 619    CTSrv00931    01/02/03      R                 (no change to Specification)
 620    CTSrv00932    01/17/01     NC                      CHI specification
 621    CTSrv00933    03/02/01     NC                      CHI specification
 622    CSCnj06391    10/11/01     NC                  Adaptation/Software ICD
 623    CSCnj06393    09/13/02      R                 (no change to Specification)
 624    CSCnj06414    03/05/01     NC                      CHI specification
 625    CSCnj06422    03/05/01      R                 (no change to Specification)
 626    CSCnj06426    01/03/01      S      Initially approved. Subsequently superceded by



                                   D-16                              TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
                                                              RPR-1041
 627    CTSrv00983    03/05/01     NC                     CHI specification
 628    CSCwb00679    01/10/01      S      Initially approved. Subsequently superceded by
                                                              RPR-1041
 629    CTSrv00988      N/A         P                         Postponed
 630    CTSrv01000    01/03/01     NC                     CHI specification
 631    CTSrv01003    03/05/01     NC                     CHI specification
 632    CTSrv01005    03/05/01     NC                     CHI specification
 633    CSCwb00738    03/02/01      X                   New shalls 1511, 1512
 634    CSCwb00739    03/02/01     NC                     CHI specification
 635    CSCwb00741    03/02/01     NC                     CHI specification
 636    CSCwb00742    03/02/01      X     New shalls 1516, 1518, 1519, 1522, 1523, 1524,
                                                                3486
 637    CSCwb00743    03/12/01     X
 638    CSCwb00744    03/02/01     X
 639    CSCwb00745    03/02/01     X
 640    CSCwb00746
 641    CSCwb00747    03/02/01     X                     New shall 3509
 642    CSCwb00748    03/12/01     X      New shalls 3685, 3687, 3689, 3691, 3692, 3693,
                                               3694, 3695, 3696, 3697, 3698, 3699
 643    CSCwb00749    05/13/02     X      New shalls 0371, 0373, 0375, 1092, 1094, 1095,
                                                            1097, 1099
 644    CSCnj06529    04/26/01     NC                Adaptation/Software ICD
 645    CSCnj06531    04/26/01     NC                Adaptation/Software ICD
 646    CSCnj06532    01/10/01     NC                 Adaptation/Software ICD
 647    CTSrv01030    01/17/01     NC                     CHI specification
 648    CTSrv01031    03/02/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 649    CTSrv00873    01/17/01     NC                    CHI specification
 650    CSCnj06564    01/03/01     NC                 Adaptation/Software ICD
 651    CSCwb00790    01/03/01     NC                     CHI specification
 652    CSCwb00791    01/17/01     NC                    CHI specification
 653    CSCwb00792    01/10/01     NC                    CHI Specification
 654    CSCwb00793    10/16/00     NC                    CHI specification
 655    CSCwb00794    01/17/01     NC                    CHI specification
 656    CSCwb00795    01/22/01     NC                    CHI specification
 657    CSCwb00796    01/17/01     NC                    CHI specification
 658    CSCwb00797    11/09/01     D                   Duplicate of RPR-695
 659    CSCwb00799    10/16/00     NC                    CHI specification
 660    CSCwb00839    03/02/01     X                   New shalls 2886, 2888
 661    CSCnj06741    04/27/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 662    CSCnj06740    03/05/02     S      Initially approved. Subsequently superceded by
                                                             RPR-1041



                                   D-17                              TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 663    CSCwb00884    01/10/01     X      New shalls 0985, 0986, 0987, 1043, 1047, & 1048
 664    CSCnj06743    01/08/02     NC                      CHI specification
 665    CSCnj06742    04/27/01      S      Initially approved. Subsequently superceded by
                                                              RPR-1041
 666    CSCnj06738    03/05/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 667    CSCnj06737    03/02/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 668    CSCnj06736      N/A        R       (no change to Specification) (06/12/01-DDTS)
 669    CSCnj06735    03/02/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 670    CSCnj06733    03/02/01     S       Initially approved. Subsequently superceded by
                                                               RPR-800
 671    CSCnj06654    04/27/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 672    CSCnj06747
 673    CSCnj06748    04/27/01     X                   New shalls 0744, 0746
 674    CSCwb00871    03/02/01     NC                     CHI specification
 675    CSCwb00872    03/02/01     X                       New shall 2833
 676    CSCwb00880    03/02/01     NC                     CHI specification
 677    CSCnj06802    10/04/02      R                (no change to Specification)
 678    CSCwb00889    03/02/01     X                   New shalls 2882, 2884
 679    CSCwb00895    03/02/01     X         New shalls 2834, 2836, 2837, 2838, 2839
 680    CSCnj06822    01/10/01     NC                     CHI Specification
 681    CSCwb00905    01/10/01     NC                     CHI Specification
 682    CSCwb00906    01/02/03      R     (no change to Specification – superseded by the
                                                 implementation of Meter Fix Arcs)
 683    CSCwb00907    01/17/01     NC                     CHI specification
 684    CSCwb00908    01/17/01     NC                     CHI specification
 685    CSCwb00909    03/02/01     NC                     CHI specification
 686    CSCwb00910    04/27/01     NC                     CHI specification
 687    CSCwb00911    01/17/01     NC              New shalls 2963, 2965, & 2967
 688    CSCwb00918    01/08/01     NC                     CHI specification
 689    CSCwb00919    10/11/01     NC                     CHI specification
 690    CSCwb00930    03/02/01     NC                     CHI specification
 691    CSCnj06918    10/11/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 692    CSCwb00946    03/02/01     X      New shalls 2921, 2922, 2923, 2924, 2925, 2926,
                                                    2927, 2928, 2931, 2932, 2933
 693    CSCwb00947    03/02/01     NC                     CHI specification
 694    CSCwb00948    03/02/01     NC                     CHI specification
 695    CSCwb00949    03/02/01     NC                     CHI specification
 696    CSCwb00953    03/02/01     NC                     CHI specification
 697    CSCwb00954    03/02/01     NC                     CHI specification
 698    CSCwb00955    03/02/01     NC                     CHI specification



                                   D-18                              TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 699    CSCwb00957    01/10/01     NC                    CHI Specification
 700    CSCwb00958    04/26/01     NC                Adaptation/Software ICD
 701    CSCwb00975    01/17/01     X                 New shalls 2895 & 2897
 702    CSCwb01000    09/07/01     X          New shalls 2912, 2913, 2914, 2916, 2918
 703    CSCwb01009
 704    CSCwb00976    01/22/01     X                      New shall 2835
 705    SSWca01003    01/17/01     NC                 Adaptation/Software ICD
 706    CSCnj06993     2/22/05      R
 707    CSCwb01015    04/02/01     NC                     CHI specification
 708    CSCwb01016    03/02/01     NC                     CHI specification
 709    CSCwb01017    03/05/01     NC                     CHI specification
 710    CSCwb01018    10/01/01      R                (no change to Specification)
 711    CSCwb01019    03/02/01     NC                     CHI specification
 712    CSCwb01029    03/02/01     NC                     CHI specification
 713    CSCwb01034    01/22/01     X                       New shall 2911
 714    CSCwb01036    03/12/01     X                    New shalls 4035, 4036
 715    CSCwb01040    01/22/01     X                   New shalls 2891 & 2893
 716    CSCnj07020    03/05/02     X
 717    CSCwb01037    04/26/01     NC                 Adaptation/Software ICD
 718    CSCwb01038    04/26/01     NC                 Adaptation/Software ICD
 719    CSCwb01053    03/02/01     X
 720    CSCwb01087    03/02/01     X                         New shall 2899
 721    CSCnj07118    03/12/01      S       Initially approved. Subsequently superceded by
                                                               RPR-1041
 722    CSCwb01094    08/15/01     NC                       CHI specification
 723    CSCwb01100    08/15/01     NC                   Adaptation/Software ICD
 724    CSCwb01113    02/24/03      R                  (no change to Specification)
 725    CSCwb01114    03/05/01     NC                       CHI specification
 726    CSCwb01116    07/17/01      R                  (no change to Specification)
 727    CSCwb01117    07/17/01     NC                       CHI Specification
 728    CSCwb01123    07/17/01     NC                       CHI specification
 729    CSCwb01124    03/05/01     NC                       CHI specification
 730    CSCwb01125    08/15/01      R                  (no change to Specification)
 731    CSCwb01126    03/05/01      R                  (no change to Specification)
 732    CSCwb01127    04/27/01      S      Initially approved. Subsequently superceded by
                                                               RPR-1043
 733    CSCwb01128    10/10/01     NC                       CHI specification
 734    CSCwb01129    10/01/01      R                  (no change to Specification)
 735    CSCwb01131    04/29/02      R     Adaptation/Software ICD. Subsequently superceded
                                                              by RPR-1038
 736    CSCwb01132    09/07/01     NC                   Adaptation/Software ICD
 737    CSCwb01133    08/15/01     NC                   Adaptation/Software ICD
 738    CSCwb01153    07/17/01     NC                       CHI specification



                                   D-19                               TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 739    CSCwb01154                  S     Initially approved. Subsequently superceded by
                                                             RPR-1044
 740    CSCwb01155     N/A*         R                (no change to Specification)
 741    CSCwb01156    03/05/01     NC                     CHI specification
 742    CSCwb01157    10/01/01      R                (no change to Specification)
 743    CSCwb01158    07/17/01     NC                     CHI specification
 744    CSCwb01159    01/08/02     NC                     CHI specification
 745    CSCwb01160
 746    CSCwb01161    07/17/01     R               (no change to Specification)
 747    CSCwb01163    11/01/02     X
 748    CSCwb01170    10/01/01     R               (no change to Specification)
 749    CSCwb01109    03/12/01     X                      New shall 3538
 750    CSCwb01166     N/A*        R      (no change to Specification – superseded by the
                                                implementation of Meter Fix Arcs)
 751    CSCwb01167    11/01/02     NC                    CHI specification
 752    CSCwb01168    03/05/01     NC                    CHI specification
 753    CSCnj07223    06/18/01     NC               Adaptation/Software ICD
 754    CSCnj07224    06/18/01     NC               Adaptation/Software ICD
 755    CSCwb01177    04/26/01     X
 756    CSCwb01180    07/17/01     NC           CHI specification not implemented??
 757    SSWca01344    06/18/01     NC                 Adaptation/Software ICD
 758    CSCnj07228    06/18/01     NC                 Adaptation/Software ICD
 759    CSCnj07229    06/18/01     NC                 Adaptation/Software ICD
 760    CSCwb01225    09/07/01     NC                    CHI specification
 761    CSCwb01226    09/07/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 762    CSCwb01227    04/26/01     X
 763    CSCwb01228    09/07/01     NC           CHI specification not implemented
 764    CSCwb01229    03/05/02     NC                  CHI specification
 765    CSCwb01230    09/07/01     NC                  CHI specification
 766    CSCwb01232    09/26/01     NC                  CHI specification
 767    CSCnj07278    03/05/01     X                    New shall 0244
 768    CSCnj07307    04/27/01     X
 769    CSCwb00981    07/17/01     NC         CHI specification not implemented ??
 770    CSCwb01241    10/01/01      R             (no change to Specification)
 771    CSCwb01242    10/01/01      R             (no change to Specification)
 772    CSCwb01245
 773    CSCwb01246                 S      Initially approved. Subsequently superceded by
                                                             RPR-1048
 774    CSCwb01247    06/05/01     NC                     CHI specification
 775    CTSrv01184    06/27/01     NC                     CHI specification
 776    SSWca01438    06/10/02     NC                 Adaptation/Software ICD
 777    CSCwb01260    12/09/04     NC                     CHI specification



                                   D-20                              TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 778    CSCwb01043    09/07/01      R                (no change to Specification)
 779    CSCwb01267    07/17/01     NC                     CHI specification
 780    CSCnj07414    06/05/01     NC                    Data Recording ICD
 781    CSCnj07428    04/29/02      S     Initially approved. Subsequently superceded by
                                                              RPR-1041
 782    CSCwb01277      N/A        P                          Postponed
 783    CSCwb01278
 784    CSCwb01279    05/07/02     NC                     CHI specification
 785    CSCwb01280    08/15/01     NC                     CHI specification..
 786    CSCwb01282      N/A         R                (no change to Specification)
 787    CSCwb01284    08/15/01                       Not implemented/Postponed
 788    CTSrv01214    11/09/01     NC                 Adaptation/Software ICD
 789    CSCnj07450    11/09/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 790    CSCnj07451    01/08/02     S      Initially approved. Subsequently superceded by
                                                             RPR-1041
 791    CSCnj07452
 792    CSCwb01302    07/17/01     NC          CHI Specification not implemented
 793    CSCwb01328    09/07/01     NC                 CHI Specification
 794    CSCwb01326    04/10/02     NC                 CHI Specification
 795    CSCnj07471    04/27/01     NC              Adaptation/Software ICD
 796    CSCnj07485    08/15/01     X
 797    CSCnj07484      N/A         R               (no changed to Specification)
 798    CSCwb01334    09/07/01     NC                     CHI specification
 799    CSCwb01333    07/17/01     NC                     CHI specification
 800    CSCnj07495    08/15/01      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 801    CSCnj07500    04/27/01     NC                 Adaptation/Software ICD
 802    CSCwb01354      N/A        D                   Duplicated of RPR-600
 803    CTSrv01250    09/26/01     NC                     CHI specification
 804    CTSrv01251    10/01/01      R                (no change to Specification)
 805    CTSrv01252      N/A         R        Editorial corrections covered in RPR-519
 806    CSCnj06746    10/04/02      R                (no change to Specification)
 807    CSCwb01358    08/15/01     NC                     CHI specification
 808    CSCwb01398    07/17/01     NC                     CHI specification
 809    CSCwb01414     N/A*         R                (no change to Specification)
 810    CSCwb01421    10/11/01     NC                 Adaptation/Software ICD
 811    CSCwb01422    10/11/01      R                (no change to Specification)
 812    CSCwb01425    03/05/02      R                (no change to specification)
 813    CSCwb01426    11/09/01     NC                 Adaptation/Software ICD
 814    CSCwb01427    08/15/01     NC                     CHI specification
 815    CTSrv01275    10/11/01     NC                 Adaptation/Software ICD
 816    CSCnj07564    08/15/01     NC                 Adaptation/Software ICD



                                   D-21                             TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 817    CSCnj07525
 818    CSCwb01440    08/15/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 819    CSCwb01435    01/02/03      R                 (no change to Specification)
 820    CSCnj07589    07/15/04     NC     (no change to Specification) – The updates are in
                                                               RPR-995
 821    CSCnj07593    08/15/01     X
 822    CSCnj07591      N/A         R               (no change to Specification)
 823    CSCnj07609    09/07/01     X
 824    CSCnj07619    09/07/01     NC            CHI specification. Not implemented.
 825    CSCwb01483    10/11/01     NC                      CHI Specification
 826    CSCwb01484    01/08/02     NC                  Adaptation/Software ICD
 827    CSCwb01487    01/02/03      R                 (no change to Specification)
 828    CSCwb01488      N/A         R                 (no change to Specification)
 829    CSCwb01489    10/04/02      R                 (no change to Specification)
 830    CSCwb01492    01/08/02      R                 (no change to Specification)
 831    CSCwb01493    09/07/01      R                 (no change to Specification)
 832    CSCnj07629    09/13/02     NC                  Adaptation/Software ICD
 833    CSCwb01523      N/A         R                 (no change to Specification)
 834    CSCwb01548    09/07/01     NC                  Adaptation/Software ICD
 835    CSCwb01405    10/04/02      R                 (no change to Specification)
 836    CSCnj07645    01/08/02     NC            CHI specification. Not implemented.
 837    CSCnj07643    09/26/01      S      Initially approved. Subsequently superceded by
                                                              RPR-1041
 838    CSCnj07642    09/26/01     S       Initially approved. Subsequently superceded by
                                                              RPR-1040
 839    CSCnj07640
 840    CSCwb01545    06/08/04     NC                Adaptation/Software ICD
 841    CSCnj07639     6/20/05      R               No change to specification
 842    CSCwb01540    09/25/02     NC                Adaptation/Software ICD
 843    CSCnj07659    03/05/02     NC                   CHI specification
 844    CSCwb01555    10/11/02     NC                   CHI specification
 845    CSCnj07658    05/13/02     X                      New shall 2943
 846    CSCwb01563    01/08/02     NC                Adaptation/Software ICD
 847    CSCwb01560    10/11/01     NC                   CHI specification.
 848    CSCwb01556    10/11/01     NC                   CHI specification
 849    CSCwb01579    11/09/01     NC           CHI specification. Not implemented.
 850    CSCnj07679    10/04/02      R              (no change to Specification)
 851    CSCnj07682
 852    CSCnj07687    01/08/02     S       Initially approved. Subsequently superceded by
                                                              RPR-1041
 853    CSCnj07686    11/09/01     NC                     CHI specification
 854    CSCnj07685



                                   D-22                               TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 855    CSCnj07684    02/23/05     NC                     CHI specification
 856    CSCnj07683      N/A        D         Duplicate of RPR-790 (07/23/01-DDTS)
 857    CSCnj07681     N/A*         R                (no change to Specification)
 858    CSCnj07688    09/13/02      R                (no change to Specification)
 859    CSCwb01577    11/09/01     NC           CHI specification. Not implemented.
 860    CSCwb01576    10/11/01     NC                     CHI specification
 861    CSCnj07666    01/08/02                       Not implemented/Postponed
 862    CSCwb01565    10/11/01     NC                     CHI specification
 863    CSCwb01575    11/02/02     NC                 Adaptation/Software ICD
 864    CSCwb01596    11/09/01     NC           CHI specification. Not implemented.
 865    CSCwb01586    10/11/01     X                   New shalls 0151, 3488
 866    CSCnj07715    01/08/02      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 867    CSCwb01627    11/09/01     NC                     CHI specification
 868    CSCwb01640    11/09/01     NC                     CHI specification
 869    CSCwb01638    01/31/05     NC                     CHI specification
 870    CSCwb01650    01/08/02     X
 871    CSCwb01651    03/05/02     NC                  CHI specification
 872    CSCwb01687    11/09/01     NC               Adaptation/Software ICD
 873    CTSrv01361    04/29/02     NC               Adaptation/Software ICD
 874    CSCwb01694    03/05/02     NC                  CHI specification.
 875    CSCnj07843
 876    CSCnj07843    05/13/02     X                     New shall 2829
 877    CSCnj07859    05/13/02     X                     New shall 2934
 878    CSCnj07858    02/26/02     X
 879    CTSrv01377
 880    CSCwb01805    09/06/02     X                     New shall 2929
 881    CSCwb01816
 882    CSCnj07881    02/26/02     NC               Adaptation/Software ICD
 883    CSCwb01818    01/11/02     NC               Adaptation/Software ICD
 884    CSCwb01821    12/09/04     X             New shalls 0412, 0510k, 2750nn
 885    CSCwb01824    09/06/02     X                     New shall 2935
 886    CSCwb01829    12/01/06      R              (no change to Specification)
 887    CSCwb01830    02/22/02     NC               Adaptation/Software ICD
 888    CSCnj07896    09/13/02     NC               Adaptation/Software ICD
 889    CSCnj07905
 890    CSCnj07909    12/01/06      R                (no change to Specification)
 891    CSCwb01837    03/05/02     NC                     CHI specification
 892    CSCwb01838                  P                        Postponed*
 893    CSCwb01839    03/05/02      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 894    CSCwb01852    02/26/02     X


                                   D-23                             TMA System Spec
                                                                   FAA-E-2971
                                                              17 December 2008
                                                                    Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                 Comments
 895    CSCwb01853
 896    CSCnj07939    06/10/02     X
 897    CSCwb01859    06/10/02     NC                 CHI specification
 898    SSWfw06215
 899    SSWfw06216
 900    CTSrv01434    06/10/02     NC                 CHI specification
 901    CSCwb01870    06/10/02     NC              Adaptation/Software ICD
 902    CSCwb01879    06/10/02            Adaptation/Software ICD. Not implemented
 903    CSCwb01886
 904    CSCwb01887    06/10/02     NC                 CHI specification
 905    CSCwb01889    06/10/02     NC                 CHI specification
 906    CSCwb01895    06/10/02     NC                 CHI specification
 907    CSCnj07985
 908    CSCwb01908    01/11/02     NC             Adaptation/Software ICD
 909    CSCwb01909    01/11/02     NC             Adaptation/Software ICD
 910    CSCwb01910    10/04/02      R            (no change to Specification)
 911    CSCnj07995    07/15/04     NC                 CHI specification
 912    CSCwb01918    10/04/02     NC                 CHI specification
 913    CSCwb01921    11/06/02     NC             Adaptation/Software ICD
 914    CSCwb01923    10/04/02     NC                 CHI specification
 915    CSCwb01926    01/11/02     NC             Adaptation/Software ICD
 916    CTSrv01455    10/04/02     NC                 CHI specification
 917    CSCwb01937    04/29/02     NC                 CHI specification
 918    CSCwb01938    12/01/06      R            (no change to Specification)
 919    CSCwb01939    04/29/02     NC                 CHI specification
 920    CSCwb01940    07/29/03     NC                 CHI specification
 921    CSCwb01942    06/08/04     NC                 CHI specification
 922    CSCwb01945      TBD         R
 923    CSCwb01962    01/11/02     NC             Adaptation/Software ICD
 924    CSCwb01949    04/29/02     NC                 CHI specification
 925    CSCwb01964    12/01/06      R            (no change to Specification)
 926    CSCwb01965    10/04/02     NC                 CHI specification
 927    CSCwb01966    09/25/02     NC                 CHI specification
 928    CSCwb01973    02/22/02     NC                 CHI Specification
 929    CSCwb01974    02/26/02     NC             Adaptation/Software ICD
 930    CSCwb01976    04/29/02     NC                 CHI specification
 931    CSCwb01997
 932    CSCwb02006    02/26/02     NC                 CHI Specification
 933    CTSrv01505    04/29/02     NC                 CHI specification
 934    CSCwb02013    05/17/06     NC                 CHI specification
 935    CSCwb02041    09/06/02     NC                 CHI specification




                                   D-24                           TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 936    CSCwb02038
 937    CSCwb02014    11/26/02      R                (no change to Specification)
 938    CSCwb02062    12/01/06      R                (no change to Specification)
 939    CSCwb02063    02/26/02     NC                 Adaptation/Software ICD
 940    CSCwb02064    02/26/02     NC                     CHI Specification
 941    CSCwb02065
 942    CSCwb02066    02/26/02     X                     New shalls 0775 & 0777
 943    CSCwb02067    02/26/02     NC                   Adaptation/Software ICD
 944    CSCwb02096    05/13/02     NC                   Adaptation/Software ICD
 945    CSCnj08187    09/25/02      R                  (no change to Specification)
 946    CSCnj08173    04/10/02      S       Initially approved. Subsequently superceded by
                                                                RPR-1041
 947    CSCnj08171    05/13/02     S        Initially approved. Subsequently superceded by
                                                                RPR-1041
 948    CSCwb02094                 D      Duplicate of the following Adaptation/Software ICD
                                                           RPR CSCwb02694
 949    CSCnj08200    05/13/02     X                         New shall 0152
 950    CSCnj08213    05/13/02     X
 951    CSCnj08219    04/10/02     NC                 Adaptation/Software ICD
 952    CSCwb02180
 953    CSCwb02177    05/13/02     NC                 Adaptation/Software ICD
 954    CSCwb02176    05/13/02     NC                 Adaptation/Software ICD
 955    CSCnj08260    05/13/02     NC                 Adaptation/Software ICD
 956    CSCwb02190    09/13/02     NC                 Adaptation/Software ICD
 957    CSCwb02193
 958    CSCnj08282    05/13/02     NC                   Adaptation/Software ICD
 959    CSCnj08283    05/13/02     NC                   Adaptation/Software ICD
 960    CSCwb02211    05/13/02     X                     New shalls 0245, 0246
 961    CSCwb02212    05/13/02     NC                   Adaptation/Software ICD
 962    CSCnj08297                 D      Duplicate of the following Adaptation/Software ICD
                                                            RPR CSCnj08307
 963    CSCnj08307    05/13/02     NC                   Adaptation/Software ICD
 964    CSCwb02230    12/13/02     NC                       CHI specification
 965    CSCnj08433    06/28/02     NC                   Adaptation/Software ICD
 966    CSCnj08432    08/06/02     NC                   Adaptation/Software ICD
 967    CSCnj08441    08/06/02     NC                   Adaptation/Software ICD
 968    CSCnj08442    08/06/02     X                         New shall 0803
 969    CSCnj08443    08/06/02     X
 970    CSCwb02282    02/13/03      R                (no change to Specification)
 971    CSCwb02283    02/13/03      R                (no change to Specification)
 972    CSCwb02400    10/30/02     NC                     CHI specification
 973    CSCwb02402
 974    CTSrv01564    10/30/02     NC                     CHI specification



                                   D-25                               TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 975    CTSrv01565    10/30/02     NC                   CHI specification
 976    CTSrv01566    10/30/02     NC                   CHI specification
 977    CTSrv01567    10/30/02     NC                   CHI specification
 978    CTSrv01571    10/30/02     NC                   CHI specification
 979    CTSrv01568    10/30/02     NC                   CHI specification
 980    CTSrv01569    06/23/04      R              (no change to Specification
 981    CSCnj08440    08/06/02     NC               Adaptation/Software ICD
 982    CSCwb02434    09/06/02     NC                   CHI specification
 983    CSCnj08460    08/06/02     X
 984    CSCwb02441    08/06/02     NC                  CHI specification
 985    CSCwb02451    08/14/02     NC                  CHI specification
 986    CSCwb02500    09/13/02     NC                  CHI specification
 987    CSCwb02501    09/13/02     NC               Adaptation/Software ICD
 988    CSCwb02502    09/13/02     NC               Adaptation/Software ICD
 989    CSCwb02456    10/30/02     NC                  CHI specification
 990    CSCwb02563    09/13/02     X
 991    CSCwb02562    09/13/02     NC                    CHI specification
 992    CSCnj08506    09/13/02      S     Initially approved. Subsequently superceded by
                                                             RPR-1041
 993    CSCwb02556    09/06/02     X                      New shall 2919
 994    CSCwb02529    09/06/02     NC                 Adaptation/Software ICD
 995    CSCwb02516    07/15/04     X              New shalls 0247, 0248, and 0249
 996    CSCnj08466
 997    CSCnj08458
 998    CSCwb02522
 999    CSCnj08192    09/06/02     X          Clarification RPR. No changes to SSS
1000    CSCnj08263    09/06/02     X              New shalls 2952, 2953, 2954
1001    CSCwb02612    09/13/02     X          Clarification RPR. No changes to SSS
1002    CSCwb02646    09/25/02     X
1003    CSCwb02621    10/03/02     NC               Adaptation/Software ICD
1004    CSCwb02645    10/30/02     NC                  CHI specification
1005    CSCwb02662    10/30/02     NC                  CHI specification
1006    CSCwb02681    10/03/02     X
1007    CSCwb02682    10/03/02     X
1008    CSCwb02683    10/03/02     X
1009    CSCwb02600    10/30/02     X
1010    CSCwb02601    10/30/02     NC                    CHI specification
1011    CSCwb02603    01/14/03     NC                    CHI specification
1012    CSCwb02654    01/14/03     NC                    CHI specification
1013    CSCwb02687    10/03/02     NC                 Adaptation/Software ICD
1014    CSCwb02694    10/03/02     NC                 Adaptation/Software ICD
1015    CSCnj08704    11/01/02      S     Initially approved. Subsequently superceded by



                                   D-26                             TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #    DDTS #      CSC Letter   Entrd                   Comments
                                                             RPR-1041
1016    CSCwb02753    11/13/02     X                  New shalls 0353 and 0372
1017    CSCnj08190    02/03/03     S      Initially approved. Subsequently superceded by
                                                             RPR-1041
1018    CSCnj08183    02/03/03     S      Initially approved. Subsequently superceded by
                                                             RPR-1041
1019    CSCwb02799    12/13/02     NC                 Adaptation/Software ICD
1020    CSCwb02784    03/25/03     X
1021    CSCwb02785    03/25/03     NC                     CHI specification
1022    CSCwb02786    03/25/03     NC                 Adaptation/Software ICD
1023    CSCwb02800    12/01/06      R                (no change to Specification)
1024    CSCwb02801    04/30/03     NC                     CHI specification
1025    CSCwb02802    03/10/03     NC                     CHI specification
1026    CSCwb02803    03/25/03     NC                     CHI specification
1027    CSCwb02804    03/25/03     NC                 Adaptation/Software ICD
1028    CSCwb02794    12/13/02     NC                 Adaptation/Software ICD
1029    CSCwb02815    02/03/03     NC                     CHI specification
1030    CTSrv01618    02/13/03     NC                     CHI specification
1031    CSCwb02891    02/03/03     NC                 Adaptation/Software ICD
1032    CSCwb02863    02/03/03     NC                 Adaptation/Software ICD
1033    CSCwb02795    02/03/03     NC                     CHI specification
1034    CSCwb02904    02/03/03     NC                 Adaptation/Software ICD
1035    CSCnj08823    02/03/03     NC                 Adaptation/Software ICD
1036    CSCwb02910    02/03/03     X                       New shall 1102
1037    CSCwb02921    02/24/03     NC                     CHI specification
1038    CSCwb02922    02/24/03     NC       Adaptation/Software ICD-Undoes RPR-735
1039    CSCwb02791    03/25/03     X                  New shalls 0804 and 0805
1040    CSCwb02973    02/21/03      S     Initially approved. Subsequently superceded by
                                                              RPR-1041
1041    CSCwb02926    02/21/03     NC                     CHI specification
1042    CSCwb02983    02/21/03     NC                     CHI specification
1043    CSCwb02963    03/11/03     NC           CHI specification. Undoes RPR-732
1044    CSCwb02964    03/11/03     NC           CHI specification. Undoes RPR-739
1045    CSCwb03027    03/11/03     NC           CHI specification. Undoes RPR-293
1046    CSCwb03038    02/21/03     X             New shalls 0167, 0168, 0169, 0171
1047    CSCwb03031    02/21/03     NC                 Adaptation/Software ICD
1048    CSCwb02965    03/11/03     NC           CHI specification. Undoes RPR-773
1049    CSCwb03046    03/11/03     NC                    Data Recording ICD
1050    CSCnj08910    03/04/03     NC                 Adaptation/Software ICD
1051    CSCwb03061    02/25/03     NC                     CHI specification
1052    CSCwb03091    03/06/03     NC                 Adaptation/Software ICD
1053    CSCwb03093    03/06/03     NC                 Adaptation/Software ICD
1054    CSCwb03094    03/06/03     NC                 Adaptation/Software ICD



                                   D-27                             TMA System Spec
                                                                     FAA-E-2971
                                                                17 December 2008
                                                                      Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                   Comments
 1055   CSCwb03095    03/06/03     NC               Adaptation/Software ICD
 1056   CSCwb03096    03/06/03     NC               Adaptation/Software ICD
 1057   CSCwb03097    03/06/03     NC               Adaptation/Software ICD
 1058   CSCwb03180    04/30/03     X
 1059   CSCnj08520    04/30/03     NC                    CHI specification
 1060   CSCwb03218    04/30/03     NC                    CHI specification
 1061   CSCwb01961    05/28/03     X                New shalls 2936 and 2937
 1062   CSCwb03219    06/05/03     NC                    CHI specification
 1063   CSCwb03230    05/28/03     NC                  Data Recording ICD
 1064   CSCwb03231    06/05/03     X      New shalls 1453, 1454, 1455, 1456, 1457, 2852,
                                                       2853, 2854, and 2855
1065    CSCwb03253    05/28/03     NC                Adaptation/Software ICD
1066    CSCnj08974    05/28/03     NC                  Data Recording ICD
1067    CSCnj08975    06/05/03     NC                Adaptation/Software ICD
1068    CSCwb03287    06/05/03     NC                Adaptation/Software ICD
1069    CSCwb03283    06/05/03     X                      New shall 0272
1070    CSCwb03295    06/05/03     NC                  Data Recording ICD
1071    CSCnj09003    06/05/03     NC                  Data Recording ICD
1072    CSCwb03297    06/05/03     NC                Adaptation/Software ICD
1073    CSCwb03302    06/05/03     NC                Adaptation/Software ICD
1074    CSCwb03395    07/16/03     NC                    CHI specification
1075    CSCwb03396    07/16/03     NC                Adaptation/Software ICD
1076    CSCwb03416    07/16/03     X
1081    CSCwb03465    07/29/03     NC               Adaptation/Software ICD
1082    CSCwb03466    07/29/03     NC               Adaptation/Software ICD
1083    CSCwb03467    09/15/03     NC               Adaptation/Software ICD
1084    CSCwb03469    09/15/03     NC               Adaptation/Software ICD
1085    CSCwb03471    07/29/03     NC                 Data Recording ICD
1086    CSCwb03427    07/29/03     NC               Adaptation/Software ICD
1087    CSCnj08770    08/22/03     NC                  CHI specification
1089    CSCnj08771    08/22/03     NC                  CHI specification
1090    CSCwb03412    08/22/03     X
1091    CSCwb03413    08/22/03     NC               Adaptation/Software ICD
1093    CSCwb03464    08/22/03     NC               Adaptation/Software ICD
1094    CSCwb03516    08/22/03     NC               Adaptation/Software ICD
1095    CSCwb03522    08/22/03     NC                  CHI specification
1096    CSCwb03526    09/15/03     NC               Adaptation/Software ICD
1097    CSCwb03559    09/05/03     NC                 Data Recording ICD
1098    CSCwb03596    09/05/03     X
1099    CSCwb03688    11/10/03     X                    New shall 0234
1100    CSCwb03689    11/10/03     NC                  CHI specification
1101    CSCwb03690    11/10/03     NC               Adaptation/Software ICD



                                   D-28                             TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 1102   CSCwb03691    04/16/04     NC                    Data Recording ICD
 1103   CSCnj08186    07/11/05     NC                     CHI specification
 1104   CSCwb03681    10/22/03     NC                  Adaptation/Software ICD
 1105   CSCwb03683    11/10/03     NC                  Adaptation/Software ICD
 1106   CSCwb03684    10/22/03     NC                  Adaptation/Software ICD
 1107   CSCwb03685    10/22/03     NC                  Adaptation/Software ICD
 1108   CSCwb03686    11/10/03     NC                  Adaptation/Software ICD
 1109   CSCwb03687    11/10/03     NC                  Adaptation/Software ICD
 1110   CSCwb03883    12/22/03     NC                  Adaptation/Software ICD
 1111   CSCwb03885    12/22/03     NC                  Adaptation/Software ICD
 1112   CSCnj08521    06/08/04     NC                     CHI specification
 1113   CSCnj08769                  R
 1114   CSCnj08917
 1115   CSCwb03705    05/03/04     NC                     CHI specification
 1116   CSCwb04116    02/27/04     X               New shalls: 0135, 0233, and 0832
 1117   CSCwb04176    02/27/04                            Not implemented
                      05/07/04
1118    CSCwb04178    02/27/04     NC                     CHI specification
                      05/07/04
1119    CSCwb04199    02/27/04     X      New Section 3.2.1.5.1.7 (new shalls 1052, 1054, and
                                                                 1056
1120    CSCnj09312    06/08/04     X
1121    CSCwb04253    03/19/04     NC                    Data Recording ICD
1122    CSCwb04296    03/19/04     NC                    Data Recording ICD
1123    CSCwb04324    05/03/04     X                       New shall 0238
1124    CTSrv01613    05/03/04     NC                     CHI specification
1125    CSCwb04377    05/03/04     NC                     CHI specification
1126    CSCwb04139    05/03/04     NC                    Data Recording ICD
1127    CSCnj02968
1128    CSCwb03037
1129    CSCwb03052    03/10/05     NC                     CHI Specification
1130    CSCwb03423     4/19/05     NC                 Adaptation/Software ICD
1131    CSCwb03503    12/01/06      R                (no change to Specification)
1132    CSCwb04407    04/16/04     NC                    Data Recording ICD
1133    CSCnj08649
1134    CSCwb03417
1135    CSCwb03463                 R                  (no change to Specification
1136    CSCwb03500
1137    CSCnj08184    06/08/04     NC                     CHI specification
1138    CSCnj08532
1139    CSCnj08533
1140    CSCnj08918    06/24/04     NC                     CHI specification



                                   D-29                                TMA System Spec
                                                          FAA-E-2971
                                                     17 December 2008
                                                           Final Rev N
RPR #     DDTS #     CSC Letter   Entrd        Comments
 1141   CSCnj08919    06/24/04     NC        CHI specification
 1142   CSCwb04467    06/08/04     NC     Adaptation/Software ICD
 1143   CSCwb04474    06/08/04     NC     Adaptation/Software ICD
 1144   CSCwb04482    06/23/04     NC     Adaptation/Software ICD
 1145   CSCwb04483    06/23/04     NC     Adaptation/Software ICD
 1146   CSCnj09429    07/15/04     NC        CHI specification
 1147   CSCwb04496    06/23/04
 1148   CSCwb04500    07/15/04     NC     Adaptation/Software ICD
 1149   CSCwb04515    07/15/05     NC     Adaptation/Software ICD
 1150   CSCwb04488    07/21/04     NC        CHI specification
 1151   CSCwb04540    07/01/04     NC     Adaptation/Software ICD
 1152   CSCwb04542    07/01/04     X
 1153   CSCnj09537    07/21/04     NC     Adaptation/Software ICD
 1154   CSCwb04555    08/02/04     NC     Adaptation/Software ICD
 1155   CSCwb04556    08/02/04     X
 1156   CSCwb04550      N/C         R
 1157   CSCwb04551    01/31/05     NC     Adaptation/Software ICD
 1158   CSCwb03099    01/27/05     NC        CHI Specification
 1159   CSCwb03087    01/27/05     NC        CHI Specification
 1160   CSCwb03098    01/27/05     NC        CHI Specification
 1161   CSCwb03088    01/27/05     NC        CHI Specification
 1162   CSCwb03085    02/23/05     NC        CHI Specification
 1163   CSCwb03769    02/23/05     NC        CHI Specification
 1164   CSCnj08755    02/22/05      R
 1165   CSCnj08923    02/23/05     NC        CHI Specification
 1166   CSCnj08921    02/23/05     NC        CHI Specification
 1167   CSCwb03915    02/23/05     NC        CHI Specification
 1168   CSCwb03102    02/23/05     NC        CHI Specification
 1169   CSCnj09494    07/15/04     NC     Adaptation/Software ICD
 1170   CSCnj09489    07/15/04     NC     Adaptation/Software ICD
 1171   CSCnj09536    07/15/04     NC       Data Recording ICD
 1172   CSCwb04559    08/02/04     X
 1173   CSCnj09560    07/21/04     NC       Data Recording ICD
 1174   CSCwb04091
 1175   CSCwb04115
 1176   CSCnj09584    07/21/04     NC       Data Recording ICD
 1177   CSCnj09585    07/21/04     NC       Data Recording ICD
 1178   CSCnj09588    08/02/04     NC     Adaptation/Software ICD
 1179   CSCnj09606    08/23/04     NC     Adaptation/Software ICD
 1180   CSCnj09613    08/23/04     NC     Adaptation/Software ICD
 1181   CSCnj09616    08/23/04     NC     Adaptation/Software ICD




                                   D-30                  TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 1182   CSCwb04607    08/23/04     NC                    CHI specification
 1183   CSCwb04615    02/23/05     NC                    CHI Specification
 1184   CSCwb04613    09/29/04     NC                   Data Recording ICD
 1185   CSCnj09632    09/29/04     NC                Adaptation/Software ICD
 1186   CSCwb04668     10/6/04     X      New Section 3.2.1.5.7; New SHALLS 1551, 1552,
                                           1553, 1554, 1555, 1556, 1557, 1558, and 1559
1187    CSCwb04740    03/10/05     NC                Adaptation/Software ICD
1188    CSCwb04627    08/23/05     X      New SHALLs 0212, 0213, 0216, 0217, 0219. Also
                                            adding new Section 3.2.1.3.1.6 SHALLs 0385,
                                                             0387, 0389
1189    CSCwb04631    08/04/05     NC                    CHI specification
1190    CSCwb04632    08/04/05     NC                Adaptation/Software ICD
1191    CSCwb04696
1192    CSCwb04731
1193    CSCwb04732
1194    CSCwb04734
1195    CSCwb04735
1196    CSCwb04738
1197    CSCwb04739
1198    CSCwb04741
1199    CSCwb04748    12/22/05     NC                 Adaptation/Software ICD
1200    CSCwb04724
1201    CSCwb04744
1202    CSCwb04769
1203    CSCwb04772    01/31/05     NC                 Adaptation/Software ICD
1204    CSCwb04725
1205    CSCwb04745    01/31/05     X                     New shall 0870r1.
1206    CSCnj09646     2/23/05     X
1207    CSCwb04722    12/01/06     R                (no change to Specification)
1208    CSCwb04775
1209    CSCwb04776
1210    CSCwb04782    01/31/05     NC                   Data Recording ICD
1211    CSCwb04789    01/31/05     NC                    CHI Specification
1212    CSCwb04790    12/22/05     NC                    CHI Specification
1213    CSCwb04791    01/31/05     NC                Adaptation/Software ICD
1214    CSCwb04788    01/31/05     NC      Data Recording ICD scheduled for future release
1215    CSCwb04825    12/12/06     X
1216    CSCwb04826    01/31/05     X                    New SHALL 2908
1217    CSCwb04614     2/23/05     NC                   CHI Specification
1218    CSCwb04836    01/03/06     X                    New SHALL 0251
1219    CSCwb04835     3/10/05     X                 New Shalls 2902 and 2904
1220    CSCwb04838    06/01/06     X                 Adaptation/Software ICD




                                   D-31                               TMA System Spec
                                                                        FAA-E-2971
                                                                   17 December 2008
                                                                         Final Rev N
RPR #     DDTS #      CSC Letter     Entrd                   Comments
 1221   CSCwb04873      4/4/05        X                    CHI Specification
 1222   CSCwb04882     01/03/06        R                  Data Recording ICD
 1223   CSCwb04883     03/10/05       NC                  Data Recording ICD
 1224   CSCwb04876
 1225   CSCwb04877    07/07/05 and    NC                   CHI Specification
                        07/11/05
1226     CSCwb04878
1227     CSCwb04879
1228     CSCwb04889    03/10/05       NC                Adaptation/Software ICD
1229     CSCwb04890     3/10/05       X
1230     CSCwb04894    03/10/05       NC                   CHI Specification
1231     CSCwb04900     4/19/05       NC                  Data Recording ICD
1232     CSCwb04907    03/10/05       NC                   CHI Specification
1233     CSCwb04908    04/19/05       NC                Adaptation/Software ICD
1234     CSCwb04913    09/19/05       NC                  Data Recording ICD
1235     CSCwb04915     3/10/05       X
1236     CSCwb04919    08/23/05       NC                Adaptation/Software ICD
1237     CSCwb04942    04/26/05       NC                    CHI Specification
1238     CSCwb04944     4/14/05       NC                Adaptation/Software ICD
1239     CSCwb04949     4/14/05       NC                    CHI Specification
1240     CSCwb04952     4/14/05       NC                    CHI Specification
1241     CSCwb04953     4/14/05       NC                    CHI Specification
1242     CSCwb04957     4/14/05       NC                   Data Recording ICD
1243     CSCwb04945    04/26/05       NC                    CHI Specification
1244     CSCwb04964     4/19/05       NC                Adaptation/Software ICD
1245     CSCwb04969     08/4/05       NC                Adaptation/Software ICD
1246     CSCwb04986    06/20/05        R     no change to specification – Data Recording ICD
1247    CSCwb04995      07/7/05       NC                    CHI Specification
1248     CSCwb05000     07/7/05       NC                Adaptation/Software ICD
1249     CSCwb04997    06/20/05       NC                Adaptation/Software ICD
1250     CSCwb04999    06/20/05       X
1251     CSCwb04990    07/15/08       X                   Data Recording ICD
1252     CSCwb04991
1253     CSCwb04994    06/20/05       NC                  CHI Specification
1254     CSCwb05006     07/7/05       X                  New SHALL 2750-oo
1255     CSCwb05008    07/11/05       NC                  CHI Specification
1256     CSCwb05034     07/7/05       NC                  CHI Specification
1257     CSCwb05039    07/11/05        R
1258     CSCwb05044
1259     CSCwb05045    08/4/05        NC                   CHI Specification
1260     CSCwb05046    07/7/05        X                    New SHALL 0806
1261     CSCwb05047    07/7/05        NC                   CHI Specification



                                      D-32                              TMA System Spec
                                                                         FAA-E-2971
                                                                    17 December 2008
                                                                          Final Rev N
RPR #      DDTS #     CSC Letter   Entrd                      Comments
 1262    CSCwb05048     07/7/05     NC                  Adaptation/Software ICD
 1263   CSCwb05050     07/24/07     NC                     CHI Specification
 1264    CSCwb05051    06/14/05     NC                  Adaptation/Software ICD
 1265    CSCwb05053     07/7/05     NC                     CHI Specification
 1266    CSCwb05052    10/23/07     NC                  Adaptation/Software ICD
 1267    CSCwb05054    08/23/05     NC                  Adaptation/Software ICD
 1268    CSCwb05060    05/17/06     NC                     CHI Specification
 1269    CSCwb05066    09/19/05     NC                    Data Recording ICD
 1270    CSCwb05073
 1271    CSCwb05075
 1272    CSCwb05076
 1273    CSCwb05080    07/11/05     NC                 Adaptation/Software ICD
 1274    CSCwb05082    08/23/05     NC                 Adaptation/Software ICD
 1275    CSCwb05084    07/11/05     NC                 Adaptation/Software ICD
 1276    CSCwb05088     08/4/05     NC                     CHI Specification
 1277    CSCwb05093     08/4/05     X      Spec update changed outer fix arc to outer meter arc
 1278    CSCwb05095     08/4/05     NC                 Adaptation/Software ICD
 1279    CSCwb05102    08/23/05     NC                     CHI Specification
 1280    CSCwb05098     08/4/05     NC                     CHI Specification
 1281    CSCwb05111    08/23/05     NC                 Adaptation/Software ICD
 1282    CSCwb05104     08/4/05     NC                     CHI Specification
 1283    CSCwb05117    09/19/05     NC                    Data Recording ICD
 1284    CSCwb05120    08/23/05     NC                     CHI Specification
 1285    CSCwb05126    08/23/05     NC                 Adaptation/Software ICD
 1286    CSCwb05124    08/23/05     NC                 Adaptation/Software ICD
 1287    CSCwb05137    09/19/05     NC                    Data Recording ICD
 1288    CSCwb05123
 1289    CSCwb05014
 1290    CSCwb05160    09/19/05     X                 New SHALL 0211 and 0214
 1291    CSCwb05016
 1292    CSCwb05162
 1293    CSCwb05163    09/19/05     NC                  Adaptation/Software ICD
 1294    CSCwb05165    01/03/06     NC                    Data Recording ICD
 1295    CSCwb05167    01/03/06     NC                  Adaptation/Software ICD
 1296    CSCwb05168
 1297    CSCwb05169
 1298    CSCwb05170
 1299    CSCwb05171
 1300    CSCwb05174
 1301    CSCwb05175
 1302    CSCwb05241    11/03/05     NC                      CHI Specification




                                    D-33                                TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 1303   CSCwb05300    12/22/05     NC                  Adaptation/Software ICD
 1304   CSCwb05302    12/22/05     NC                    Data Recording ICD
 1305   CSCwb05306    12/22/05     NC                    Data Recording ICD
 1306   CSCwb05308    12/22/05     NC                    Data Recording ICD
 1307   CSCwb05309    12/22/05     NC                    Data Recording ICD
 1308   CSCwb05310     1/30/06     X
 1309   CSCwb05312    01/03/06     NC                 Adaptation/Software ICD
 1310   CSCwb05319                  S     Adaptation/Software ICD – This RPR is superseded
                                                           by RPR-1463.
1311    CSCwb05323    01/03/06     NC                 Adaptation/Software ICD
1312    CSCwb05326    01/03/06     X                     New SHALL 0870s
1313    CSCnj10878    01/12/06     NC                 Adaptation/Software ICD
1314    CSCnj10881    01/12/06     NC                 Adaptation/Software ICD
1315    CSCwb05365    01/16/06     NC                     CHI Specification
1316    CSCwb05366    01/16/06     NC                 Adaptation/Software ICD
1317    CSCnj10836    05/17/06     X                       New shall 0782
1318    CSCwb05426
1319    CSCwb05439    04/27/06     NC                     CHI Specification
1320    CSCwb05440    04/27/06     NC                     CHI Specification
1321    CSCwb05441    04/27/06      R               No change to CHI Specification
1322    CSCwb05442    04/27/06     NC                     CHI Specification
1323    CSCwb05452    04/27/06     NC                     CHI Specification
1324    CSCwb05453    04/27/06     NC                     CHI Specification
1325    CSCwb05454    04/27/06     NC                     CHI Specification
1326    CSCwb05455
1327    CSCwb05327    04/27/06     X      New Section 3.2.1.5.8, new shalls 4200, 4205, 4210,
                                           4215, 4220, 4225, 4230, 4235, 4240, 4245, 4250,
                                           4255, 4260, 4265, 4270, 4275, 4280, 4285, 4290,
                                           4295, 4300, 4305, 4310, 4315, 4320, 4325, 4330,
                                           4335, 4340, 4345, 4350, 4355, 4360, 4365, 4370,
                                                 4375, 4380, 4385, 8390, 4395, 4400.
1328    CSCwb05456
1329    CSCwb05484    07/30/06     NC                  Adaptation/Software ICD
1330    CSCwb05421    07/27/06     NC                  Adaptation/Software ICD
1331    CSCwb05477    07/27/06     NC                    Data Recording ICD
1332    CSCwb05522    04/27/06     NC                     CHI Specification
1333    CSCwb05585
1334    CSCwb05595    05/17/06     X
1335    CSCnj11141    07/27/06     NC                  Adaptation/Software ICD
1336    CSCwb05605    05/17/06     NC                     CHI Specification
1337    CSCwb05630    05/17/06     X
1338    CSCwb05633    05/17/06     X
1339    CSCwb05660    05/17/06     NC                     CHI Specification



                                   D-34                                TMA System Spec
                                                                       FAA-E-2971
                                                                  17 December 2008
                                                                        Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                     Comments
 1340   CSCwb05659    05/17/06     NC                   CHI Specification
 1341   CSCwb05676    05/17/06     X                 New shalls 2907 and 2909
 1342   CSCwb05677    05/17/06     NC                   CHI Specification
 1343   CSCnj11114    06/01/06     NC                Adaptation/Software ICD
 1344   CSCwb05690    06/01/06     NC                   CHI Specification
 1345   CSCwb05625    07/30/06     NC                Adaptation/Software ICD
 1346   CSCwb05717    07/30/06     NC                Adaptation/Software ICD
 1347   CSCwb05736    06/20/06     NC                Adaptation/Software ICD
 1348   CSCwb05741
 1349   CSCwb05744    06/20/06     NC                     CHI Specification
 1350   CSCwb05742    06/20/06     X
 1351   CSCwb05748    06/20/06     X
 1352   CSCwb05753    07/27/06     NC                 Adaptation/Software ICD
 1353   CSCwb05778    07/19/06     NC                    CHI Specification
 1354   CSCwb05779    07/19/06     NC                    CHI Specification
 1355   CSCwb05831    12/12/06     NC                    CHI Specification
 1356   CSCwb05832    12/12/06     NC                    CHI Specification
 1357   CSCwb05350     1/10/07     X
 1358   CSCwb05351
 1359   CSCwb05352
 1360   CSCwb05353
 1361   CSCwb05835    07/16/07     NC                    CHI Specification
 1362   CSCwb05833    12/12/06     X      New shalls 0239, 0822, 0422, Section 3.2.1.5.8, in
                                                   paragraph 5 added item r to list
1363    CSCwb05834    12/12/06     NC                    CHI Specification
1364    CSCwb05836
1365    CSCwb05837
1366    CSCwb05838
1367    CSCwb05840
1368    CSCwb05711
1369    CSCwb05841      N/A        D                   Duplicate of RPR-1436
1370    CSCwb05842
1371    CSCwb05843
1372    CSCwb05844
1373    CSCwb05845
1374    CSCwb05849
1375    CSCwb05950    12/08/06     NC                 Adaptation/Software ICD
1376    CSCwb05859     1/10/07     NC                    CHI Specification
1377    CSCwb05860    07/24/07     NC                    CHI Specification
1378    CSCwb05861
1379    CSCwb05953    12/12/06     NC                     CHI Specification
1380    CSCwb05204    07/24/07     NC                     CHI Specification



                                   D-35                               TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 1381   CSCwb05914    12/08/06     X
 1382   CSCwb05916    12/12/06     X           New shalls 0202, 0204, 0783, 0800i
 1383   CSCwb05917     1/10/07     NC                   CHI Specification
 1384   CSCwb05733     1/10/07     NC                   CHI Specification
 1385   CSCwb05962    12/12/06     X      New Section 3.2.1.4.3.3, new shalls 0702, 0704,
                                                               0706
1386    CSCwb05967    12/08/06     NC                   CHI specification
1387    CSCwb05969    12/12/06     X      New shalls 0779, Section 3.2.1.5.8 paragraph 5
                                                        added q to the list
1388    CSCwb05970    02/09/07     NC               Adaptation/Software ICD
1389    CSCwb05983    05/17/07     X                 New shalls 0500i, 0500j
1390    CSCwb05984
1391    CSCwb05985       N/A        R               (no change to specification)
1392    CSCwb06039    02/27/07     NC                Adaptation/Software ICD
1393    CSCwb06040    02/09/07     NC                Adaptation/Software ICD
1394    CSCwb06052    02/09/07     NC                  Data Recording ICD
1395    CSCwb06053    02/09/07     NC                  Data Recording ICD
1396    CSCwb06054    02/09/07     NC                  Data Recording ICD
1397    CSCwb06055    02/09/07     NC                  Data Recording ICD
1398    CSCnj11694    02/09/07     NC                Adaptation/Software ICD
1399    CSCnj11665    02/09/07     NC                Adaptation/Software ICD
1400    CSCwb06148     1/10/07     NC                    CHI Specification
1401    CSCwb06170     1/10/07     X
1402    CSCwb06169     1/10/07     NC                   CHI Specification
1403    CSCwb06171     1/10/07     NC                   CHI Specification
1404    CSCwb06155    02/09/07     NC                Adaptation/Software ICD
1405    CSCwb06239     1/11/07     NC                   CHI Specification
1406    CSCwb06293    02/09/07     NC                Adaptation/Software ICD
1407    CSCwb06299    02/09/07     NC                Adaptation/Software ICD
1408    CSCwb06336    03/05/07     NC                  Data Recording ICD
1409    CSCwb06344    03/05/07     NC                  Data Recording ICD
1410    CSCwb06380    03/05/07     X                     New shall 0203
1411    CSCwb06384    03/05/07     NC                   CHI Specification
1412    CSCwb06395    04/04/07     NC                  Data Recording ICD
1413    CSCwb06394    04/04/07     NC                  Data Recording ICD
1414    CSCwb06405    04/09/07     NC                Adaptation/Software ICD
1415    CSCwb06413    04/09/07     NC                Adaptation/Software ICD
1416    CSCwb06415    05/18/07     NC                Adaptation/Software ICD
1417    CSCwb06421    04/09/07     NC                Adaptation/Software ICD
1418    CSCwb06422    05/17/07     NC                Adaptation/Software ICD
1419    CSCwb06423    05/17/07     NC                Adaptation/Software ICD
1420    CSCwb06427    05/18/07     NC                Adaptation/Software ICD




                                   D-36                              TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 1421   CSCwb06441    04/09/07     NC                Adaptation/Software ICD
 1422   CSCwb06446    04/09/07     NC                Adaptation/Software ICD
 1423   CSCwb06455    04/04/07     X           New shalls 0870s, 1051, 1093, 1055
 1424   CSCwb06498    07/16/07     NC                   CHI Specification
 1425   CSCwb06234    07/24/07     NC                   CHI Specification
 1426   CSCwb05981    07/24/07     X      New shalls 0414a-c, 0510l, 0512, 0514a-e, 0516
 1427   CSCwb05982    08/15/07     NC                   CHI Specification
 1428   CSCwb06511    05/18/07     NC                Adaptation/Software ICD
 1429   CSCwb06525    07/24/07     NC                   CHI Specification
 1430   CSCwb06527    04/27/07     X
 1431   CSCwb06528    04/27/07     NC                    CHI Specification
 1432   CSCwb06529    05/17/07     X
 1433   CSCwb06530    05/17/07     NC                    CHI Specification
 1434   CSCwb06531    07/16/07     X                     CHI Specification
 1435   CSCwb06532     5/17/07     X
 1436   CSCwb06534    07/16/07     X                     CHI Specification
 1437   CSCwb06535
 1438   CSCwb06548    07/24/07     X      New shalls 0381, 0383, 0384, 3750-l, 1132, 1134,
                                          1136, 1142, 1144, 1146, 1101, 1103, 1108, 1112,
                                            1114, 1096, 4200-h, 4205-d, 4365-d, 4370-d
1439    CSCwb06550    10/19/07     NC                   Data Recording ICD
1440    CSCwb06584    05/17/07     NC                 Adaptation/Software ICD
1441    CSCwb06585    05/17/07     NC                 Adaptation/Software ICD
1442    CSCwb06587    05/17/07     NC                   Data Recording ICD
1443    CSCwb06227    08/15/07     X
1444    CSCwb06608    04/27/07     NC                   CHI Specification
1445    CSCwb06626    05/18/07     NC                Adaptation/Software ICD
1446    CSCnj12371    08/08/07     NC                Adaptation/Software ICD
1447    CSCwb06627    05/18/07     NC                Adaptation/Software ICD
1448    CSCwb06667    07/16/07     X      New shalls 3622, 3624, 3626, 3628, 3632, 3634,
                                                        3636, 3638, 3642
1449    CSCwb06668    07/24/07     X               New shalls 0824, 0826, 0828
1450    CSCwb06669    07/16/07     X
1451    CSCwb06675    10/19/07     NC                Adaptation/Software ICD
1452    CSCwb06674    07/24/07     NC                   CHI Specification
1453    CSCwb06686    0724/07      X                New shall 0692, 0694, 0696
1454    CSCwb06688    07/24/07     X                     New shall 0789
1455    CSCwb06699    07/24/07     X                    CHI Specification
1456    CSCwb06726    10/19/07     NC                Adaptation/Software ICD
1457    CSCwb06727    08/08/07     NC                Adaptation/Software ICD
1458    CSCwb06728    10/19/07     NC                Adaptation/Software ICD
1459    CSCwb06729    10/19/07     NC                Adaptation/Software ICD




                                   D-37                              TMA System Spec
                                                                  FAA-E-2971
                                                             17 December 2008
                                                                   Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                Comments
 1460   CSCwb06730    08/15/07     NC            Adaptation/Software ICD
 1461   CSCwb06732    10/23/07     NC              Data Recording ICD
 1462   CSCwb06735    10/19/07     NC              Data Recording ICD
 1463   CSCwb06744    08/08/07     NC            Adaptation/Software ICD
 1464   CSCwb06757    08/08/07     NC            Adaptation/Software ICD
 1465   CSCwb06760    08/15/07     NC            Adaptation/Software ICD
 1466   CSCwb06763    08/15/07     NC            Adaptation/Software ICD
 1467   CSCwb06764    07/24/07     X                 New shall 0699
 1468   CSCnj12500    07/16/07     X              New shalls 2946, 2947
 1469   CSCwb06765    10/19/07     NC              Data Recording ICD
 1470   CSCwb06766    10/19/07     NC              Data Recording ICD
 1471   CSCwb06756    10/23/07     NC            Adaptation/Software ICD
 1472   CSCwb06768    10/19/07     NC            Adaptation/Software ICD
 1473   CSCnj12461    07/16/07     X                New shall 0260-e4
 1474   CSCwb06762    10/19/07     NC            Adaptation/Software ICD
 1475   CSCwb06776    10/23/07     NC              Data Recording ICD
 1476   CSCwb06777    10/19/07     NC              Data Recording ICD
 1477   CSCwb06778    08/15/07     NC            Adaptation/Software ICD
 1478   CSCwb06779    10/19/07     NC            Adaptation/Software ICD
 1479   CSCwb06780
 1480   CSCwb06746    08/15/07     NC                CHI Specification
 1481   CSCwb06865    08/15/07     NC                CHI Specification
 1482   CSCwb06868    08/15/07     NC                CHI Specification
 1483   CSCwb06871    08/10/07     NC                CHI Specification
 1484   CSCwb06879    08/15/07     NC                CHI Specification
 1485   CSCwb06880    08/15/07     NC                CHI Specification
 1486   CSCwb06875    08/10/07     NC            Adaptation/Software ICD
 1487   CSCwb06882    08/10/07     X      New shalls 0257, 0258, 0259, 0261, 0262
 1488   CSCwb06889    08/10/07     NC               Data Recording ICD
 1489   CSCwb06890
 1490   CSCwb06895    08/15/07     NC                CHI Specification
 1491   CSCwb06903    08/15/07     X                  New shall 2942
 1492   CSCwb06926    08/24/07     X
 1493   CSCwb06925    10/19/07     NC            Adaptation/Software ICD
 1494   CSCwb06932    08/28/07     NC               CHI Specification
 1495   CSCwb06944    10/19/07     NC            Adaptation/Software ICD
 1496   CSCwb06961    10/19/07     NC            Adaptation/Software ICD
 1497   CSCwb06960    09/18/07     NC               CHI Specification
 1498   CSCwb06982    09/26/07     X
 1499   CSCwb06992    09/26/07     NC               CHI Specification
 1500   CSCwb07000    10/19/07     NC              Data Recording ICD




                                   D-38                          TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #     CSC Letter   Entrd                    Comments
 1501   CSCwb07008    10/19/07     NC                   Data Recording ICD
 1502   CSCwb07046    10/23/07     NC                   Data Recording ICD
 1503   CSCwb07090    10/23/07     NC                Adaptation/Software ICD
 1504   CSCwb07131    12/31/07     NC                Adaptation/Software ICD
 1505   CSCwb07193    12/31/07     NC                Adaptation/Software ICD
 1506   CSCwb07246    02/05/08     X      New shalls 0263, 0264, 0265, 0266, 0267, 0268,
                                                               0269
1507    CSCwb07248    02/05/08     NC                   Data Recording ICD
1508    CSCwb07249    06/13/08     NC                Adaptation/Software ICD
1509    CSCwb07252    12/31/07     NC                Adaptation/Software ICD
1510    CSCwb07253    01/09/08     NC                Adaptation/Software ICD
1511    CSCwb07282    03/20/08     NC                    CHI Specification
1512    CSCwb07283    03/20/08     NC                    CHI Specification
1513    CSCwb07287    03/20/08     NC                    CHI Specification
1514    CSCwb07289    04/07/08     NC                    CHI Specification
1515    CSCwb07290    03/24/08     NC                    CHI Specification
1516    CSCwb07292    03/24/08     NC                    CHI Specification
1517    CSCwb07293    04/07/08     NC                    CHI Specification
1518    CSCwb07294    03/20/08     NC                    CHI Specification
1519    CSCwb07270    04/07/08     X              New shalls 0145h, 0325d, 2948.
1520    CSCwb07300    04/07/08     X      New shalls 4410, 4415, 4420, 4425, 4430, 4435,
                                                               4440
1521    CSCwb07334    03/20/08     X      New shalls 1301, 1303, 1305, 1306, 1307, 1308,
                                            1309, 1315, 1317, 1131, 11333, 1135, 1139,
                                                3750m, 4200i, 4205e, 4365e, 4370e,
1522    CSCwb07330    04/07/08     NC                    CHI Specification
1523    CSCwb07331    04/07/08     NC                    CHI Specification
1524    CSCwb07332    04/07/08     NC                    CHI Specification
1525    CSCwb07333    04/07/08     NC                    CHI Specification
1526    CSCwb07326    03/20/08     X                    New shalls 0018a-b
1527    CSCwb07337    04/17/08     X             New shalls 0873, 0875, 0877, 0879
1528    CSCwb07338                 NC                Adaptation/Software ICD
1529    CSCwb07339    07/15/08     NC                   Data Recording ICD
1530    CSCwb07346    04/07/08     X      New shalls 1491, 1492, 1493, 1494, 1495, 1496,
                                          1497, 1498. Shalls 0795b, 0795c, 0796, 0797a-c,
                                                       0798, 1511, and 1512.
1531    CSCwb07348    06/13/08     NC                Adaptation/Software ICD
1532    CSCwb07356    06/13/08     NC                Adaptation/Software ICD
1533    CSCwb07393    06/13/08     NC                Adaptation/Software ICD
1534    CSCwb07416    03/20/08     X      New shalls 4356, 4357, 4358, 4359, 4361, 4362,
                                                      4363, 4364, 4366, 4367
1535    CSCwb07419    03/20/08     X            New shalls 0400j, 0800j, 0807, 4317
1536    CSCwb07418    07/15/08     NC                Adaptation/Software ICD
1537    CSCwb07431    07/17/08     NC                   Data Recording ICD



                                   D-39                              TMA System Spec
                                                          FAA-E-2971
                                                     17 December 2008
                                                           Final Rev N
RPR #     DDTS #     CSC Letter   Entrd        Comments
 1538   CSCwb07438    03/30/08     X
 1539   CSCwb07430    03/24/08     NC        CHI Specification
 1540   CSCwb07439    03/20/08     NC        CHI Specification
 1541   CSCwb07442    06/13/08     NC     Adaptation/Software ICD
 1542   CSCwb07443    06/13/08     NC     Adaptation/Software ICD
 1543   CSCwb07467                 NC     Adaptation/Software ICD
 1544   CSCwb07471    07/15/08     NC       Data Recording ICD
 1545   CSCwb07495    03/20/08     NC        CHI Specification
 1546   CSCwb07491    07/07/08     NC        CHI Specification
 1547   CSCwb07492    07/07/08     NC       Data Recording ICD
 1548   CSCwb07509                 NC       Data Recording ICD
 1549   CSCwb07510    07/15/08     NC       Data Recording ICD
 1550   CSCwb07511    07/15/08     NC       Data Recording ICD
 1551   CSCwb07546    04/17/08     NC        CHI Specification
 1552   CSCwb07630    04/07/08     NC        CHI Specification
 1553   CSCwb07631    04/07/08     NC        CHI Specification
 1554   CSCwb07647    07/17/08     NC        CHI Specification
 1555   CSCwb07648                 NC        CHI Specification
 1556   CSCwb07612    07/07/08     NC       Data Recording ICD
 1557   CSCwb07641    07/07/08     NC       Data Recording ICD
 1558   CSCwb07660    07/07/08     NC       Data Recording ICD
 1559   CSCwb07675    04/17/09     NC        CHI Specification
 1560   CSCwb07677    07/15/08     NC       Data Recording ICD
 1561   CSCwb07682    04/21/08     NC        CHI Specification
 1562   CSCwb07685    06/13/08     NC     Adaptation /Software ICD
 1563   CSCwb07687    07/15/08     NC     Adaptation/Software ICD
 1564   CSCwb07689    06/13/08     NC     Adaptation/Software ICD
 1565   CSCwb07688    06/13/08     NC     Adaptation/Software ICD
 1566   CSCwb07702    06/13/08     NC     Adaptation/Software ICD
 1567   CSCwb07733    04/21/08     X
 1568   CSCwb07755    05/12/08     X         New shall 0797d
 1569   CSCwb07779    05/12/08     X        New shalls 0877a-b
 1570   CSCwb07833                 NC        CHI Specification
 1571   CSCwb07855                 NC     Adaptation/Software ICD
 1572   CSCwb07903    07/07/08     NC        CHI Specification
 1573   CSCwb07924    07/07/08     X
 1574   CSCwb07947    07/15/08     NC     Adaptation/Software ICD
 1575   CSCwb07961    07/15/08     NC     Adaptation/Software ICD
 1576   CSCwb07982    07/15/08     NC      Data Recording ICD
 1577   CSCwb07993    07/15/08     NC     Adaptation/Software ICD
 1578   CSCwb08003    07/17/08     NC        CHI Specification




                                   D-40                  TMA System Spec
                                                                      FAA-E-2971
                                                                 17 December 2008
                                                                       Final Rev N
RPR #     DDTS #      CSC Letter   Entrd                   Comments
 1579   CSCwb0817      07/22/08     X
 1580   CSCwb08026
 1581   CSCwb08046     08/12/08     NC                   CHI Specification
 1582   CSCwb08055                  NC                Adaptation/Software ICD
 1583   CSCwb08100     11/19/08     X      New Section 3.2.1.5.8.1, new shalls 4600, 4602,
                                           4604 a-b, 4606, 4608, 4610, 4612, 4614, 4616,
                                              4618, 4620, 4622, 4624a-c, 4626., 4223,
1584    CSCwb08137     11/19/08     X              New shalls 0192, 0194, 0196
1585    CSCwb08138     11/19/08     X                New shalls 0252a-c, 0253
1586    CSCwb08139     11/19/08     X                   New shall 0808a-d
1587    CSCwb08140     11/19/08     X                     New shall 4393
1588    CSCwb08141     11/19/08     X                     New shall 0206
1589    CSCwb08142
1590    CSCwb08143
1591    CSCwb08130
1592    CSCwb08132
1593    CSCwb08133
1594    CSCwb08148     10/30/08     NC                   CHI Specification
1595    CSCwb08149     10/30/08     NC                   CHI Specification
1596    CSCwb08150     10/30/08     NC                   CHI Specification
1597    CSCwb08174
1598    CSCwb08175
1599    CSCwb08176
1600    CSCwb08170
1601    CSCwb08171
1602    CSCwb08172
1603    CSCwb08173
1604    CSCwb08181
1605    CSCwb08182
1606    CSCwb08183
1607    CSCwb08188     11/18/08     NC                   CHI Specification
1608    CSCwb08195
1609    CSCwb08199     10/30/08     NC                   CHI Specification
1610    CSCwb08266
1611    CSCwb08312                  NC                   CHI Specification
1612    CSCwb08329     12/12/08     X                     New shall 4207
1613    CSCwb08330                  X
1614    CSCwb008359    12/12/08     X                  New shalls 4397, 4398
1615    CSCwb08365
1616    CSCwb08370
1617    CSCwb08371
1618    CSCwb08372


                                    D-41                              TMA System Spec
                                                    FAA-E-2971
                                               17 December 2008
                                                     Final Rev N
RPR #    DDTS #     CSC Letter   Entrd   Comments
 1619   CSCwb0832




                                  D-42          TMA System Spec

								
To top