Air Traffic Management Concept Baseline Definition - The Boeing ...

Air Traffic Management Concept Baseline Definition - The Boeing ... Air Traffic Management Concept Baseline Definition - The Boeing ...

catsr.ite.gmu.edu
from catsr.ite.gmu.edu More from this publisher
02.01.2015 Views

To cope with this uncertainty, the modernization must continue to be driven by a clear statement of system mission and goals, and guided by an operational concept that strives to achieve those goals. 1.2 Context This work was performed with knowledge of a variety of related completed or ongoing efforts. The primary related activities were the following: • FAA Air Traffic Operational Concept Definition team, formed in January 1997, and chartered with defining a concept for a target completion date of 2005. • RTCA Task Force 3, whose Free Flight Report, published in 1995, along with ongoing RTCA Free Flight follow-on work, includes the recent definition of an operational concept for users of the NAS. • FAA NAS Architecture Working Group had published Version 1.5 and 2.0 of the architecture through 2012 when the team started work, and industry comments on it had been published as V2.5. Some preliminary data on V3.0 was made available to the team, but considerable uncertainty still remains. • The Flight 2000 initiative was launched in early 1997, and the team kept up-to-date on the program as much as possible. Again, uncertainty remains regarding program funding and details of the final program plan. • Eurocontrol had published its European Air Traffic Management System (EATMS) Operational Concept V1.0, and the team had a number of other sources of information available to keep abreast of developments in Europe. The pending changes in the Eurocontrol charter seem likely to lead to an increased emphasis within the organization on capacity issues in Europe’s terminal areas, and thus the U.S. and European ATM concepts may see more convergence in the near future. During this period the FAA budget constraints have continued to hamper the architecture definition efforts. This, along with substantial difficulties in FAA’s recent system development and procurement efforts produce considerable volatility in the NAS modernization plan. Some of these difficulties can be traced to a lack of a clear business case for most of the current modernization initiatives, and a lack of consensus among users on many of the implementation details. 1.3 Scope The operational concept presented here is aimed at driving research to support preliminary design decisions for the NAS, which will produce top level technical and human factors requirements to achieve the system mission. Detailed concept validation research must then be performed, where technology and human factors are combined with economic evaluation of concept components to fully define the operational concept and architecture. Thus, the concept presented here, although well supported by rationale as to what might be feasible in the next two decades, must be subjected to critical analysis and validation. This process will inevitably lead to concept refinement, perhaps enabled by currently 2

unknown technology, and thus the concept will evolve to continue to reflect the current state and the system mission. This operational concept is for the Continental U.S. (CONUS) and the adjacent oceanic areas, with primary focus on the domestic radar environment where NASA’s research efforts are concentrated. The focus is on services and functions directly involved with planning and operating flights in the CONUS. System components such as the airport ground side, airway facilities operation and airline operations are not treated in any detail. These are equally important to the operation of the total system, and must be considered in their own right along with the ATM operational concept. 1.4 Report Overview A capacity-driven operational concept developed by the team is summarized in Section 6.2, with supporting detail on improvements needed in the various ATM functions presented in Sections 3.3 and 3.4. An operational concept must be clearly driven by stated mission goals, and Section 2 presents the predicted traffic growth scenario that the team chose as the primary driver for change in this operational concept. Section 2 also discusses the current lack of consensus in the industry on the details of the NAS modernization path. Section 2.3 addresses the need for a disciplined systems engineering approach to the NAS modernization, and in particular the current lack of preliminary design activity that is required to focus the effort on achieving the critical mission needs. Section 3 presents a view of the functional structure of the ATM system as it exists today, and the fundamental system objectives of capacity, safety and efficiency. The primary system functions are presented in the context of these objectives, using a representation that illustrates the levels of flow planning in the system and of plan execution through separation assurance and navigation. Section 3.3 and 3.4 discuss the improvements that the team believes are needed in the system to achieve the capacity and safety objectives stated in Section 2, with primary focus on the separation assurance function. Sections 4 and 5 present the human factors issues and the technology performance parameters that must be taken into account throughout the system development process. The concept presented here is aimed at safely increasing traffic density in the system, and this will have a substantial impact on the separation assurance function, where safety is maintained and where human operator performance is a key issue. Section 4 discusses the human factors issues in some detail, and Section 5 follows with an overview of the current and emerging technologies available to support the concept. Section 6 discusses the methodology that the team employed in synthesizing the operational concept, which is then presented in the form of transition paths for the various operating phases in Section 6.2. Each step in the transition path is described briefly to relate technology to a proposed operational improvement. Section 6.3 details the concept validation process that is needed to ensure that a concept fulfills the mission requirements and to drive successful system design, build and installation. 3

unknown technology, and thus the concept will evolve to continue to reflect the current<br />

state and the system mission.<br />

This operational concept is for the Continental U.S. (CONUS) and the adjacent oceanic<br />

areas, with primary focus on the domestic radar environment where NASA’s research<br />

efforts are concentrated. <strong>The</strong> focus is on services and functions directly involved with<br />

planning and operating flights in the CONUS. System components such as the airport<br />

ground side, airway facilities operation and airline operations are not treated in any detail.<br />

<strong>The</strong>se are equally important to the operation of the total system, and must be considered<br />

in their own right along with the ATM operational concept.<br />

1.4 Report Overview<br />

A capacity-driven operational concept developed by the team is summarized in Section<br />

6.2, with supporting detail on improvements needed in the various ATM functions<br />

presented in Sections 3.3 and 3.4. An operational concept must be clearly driven by stated<br />

mission goals, and Section 2 presents the predicted traffic growth scenario that the team<br />

chose as the primary driver for change in this operational concept.<br />

Section 2 also discusses the current lack of consensus in the industry on the details of the<br />

NAS modernization path. Section 2.3 addresses the need for a disciplined systems<br />

engineering approach to the NAS modernization, and in particular the current lack of<br />

preliminary design activity that is required to focus the effort on achieving the critical<br />

mission needs.<br />

Section 3 presents a view of the functional structure of the ATM system as it exists today,<br />

and the fundamental system objectives of capacity, safety and efficiency. <strong>The</strong> primary<br />

system functions are presented in the context of these objectives, using a representation<br />

that illustrates the levels of flow planning in the system and of plan execution through<br />

separation assurance and navigation. Section 3.3 and 3.4 discuss the improvements that<br />

the team believes are needed in the system to achieve the capacity and safety objectives<br />

stated in Section 2, with primary focus on the separation assurance function.<br />

Sections 4 and 5 present the human factors issues and the technology performance<br />

parameters that must be taken into account throughout the system development process.<br />

<strong>The</strong> concept presented here is aimed at safely increasing traffic density in the system, and<br />

this will have a substantial impact on the separation assurance function, where safety is<br />

maintained and where human operator performance is a key issue. Section 4 discusses the<br />

human factors issues in some detail, and Section 5 follows with an overview of the current<br />

and emerging technologies available to support the concept.<br />

Section 6 discusses the methodology that the team employed in synthesizing the<br />

operational concept, which is then presented in the form of transition paths for the various<br />

operating phases in Section 6.2. Each step in the transition path is described briefly to<br />

relate technology to a proposed operational improvement. Section 6.3 details the concept<br />

validation process that is needed to ensure that a concept fulfills the mission requirements<br />

and to drive successful system design, build and installation.<br />

3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!