TY - JOUR
T1 - Considerations in the design of an air traffic management system
AU - Buede, Dennis
AU - Farr, John
AU - Powell, Robert
AU - Verma, Dinesh
PY - 2002
Y1 - 2002
N2 - An air traffic management system (ATMS) is a network-centric system being used to manage another network-centric system, namely an air transportation system. At Stevens Institute of Technology we are developing a design language for network-centric systems and design guidelines for the development system of engineers and domain specialists involved in designing and integrating systems. Note, this development system with today's technology is also a network-centric system. This paper provides an outline of the design language under construction and the design guidelines being studied. Specifically, we will discuss the ATMS mission objectives (e.g., average yearly throughput of people and freight for a high demand scenario), ATMS sample usage scenarios (e.g., ATMS reroutes air traffic in time and space in reaction to major weather deviation along northeast coast), and system objectives for an ATMS (e.g., timeliness of a specific high volume of messages out of ATMS given a high volume of incoming messages from aircraft, weather sensors, and airports). In addition, we will lay out some of key design decisions associated with both the development system of engineers and domain specialists and the operational ATMS. Examples of key design decisions for the engineering system are (1) appropriate partitioning of functional/physical architectures of the engineering system, (2) appropriate degree to telecollaboration and collaboration among design/integration groups, (3) appropriate incremental delivery packages for an incremental delivery schedule of ATMS elements, and (4) appropriate levels and thrusts of the risk management program. Examples of key design decisions for the operational ATMS are (1) throughput and security trades of the ATMS and (2) throughput and resiliency to weather changes. Finally we will relate network-centric architecture issues to both of the above sets of design decisions.
AB - An air traffic management system (ATMS) is a network-centric system being used to manage another network-centric system, namely an air transportation system. At Stevens Institute of Technology we are developing a design language for network-centric systems and design guidelines for the development system of engineers and domain specialists involved in designing and integrating systems. Note, this development system with today's technology is also a network-centric system. This paper provides an outline of the design language under construction and the design guidelines being studied. Specifically, we will discuss the ATMS mission objectives (e.g., average yearly throughput of people and freight for a high demand scenario), ATMS sample usage scenarios (e.g., ATMS reroutes air traffic in time and space in reaction to major weather deviation along northeast coast), and system objectives for an ATMS (e.g., timeliness of a specific high volume of messages out of ATMS given a high volume of incoming messages from aircraft, weather sensors, and airports). In addition, we will lay out some of key design decisions associated with both the development system of engineers and domain specialists and the operational ATMS. Examples of key design decisions for the engineering system are (1) appropriate partitioning of functional/physical architectures of the engineering system, (2) appropriate degree to telecollaboration and collaboration among design/integration groups, (3) appropriate incremental delivery packages for an incremental delivery schedule of ATMS elements, and (4) appropriate levels and thrusts of the risk management program. Examples of key design decisions for the operational ATMS are (1) throughput and security trades of the ATMS and (2) throughput and resiliency to weather changes. Finally we will relate network-centric architecture issues to both of the above sets of design decisions.
UR - http://www.scopus.com/inward/record.url?scp=85013581632&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85013581632&partnerID=8YFLogxK
U2 - 10.1109/DASC.2002.1067962
DO - 10.1109/DASC.2002.1067962
M3 - Article
AN - SCOPUS:85013581632
VL - 1
SP - 4B11-4B19
JO - AIAA/IEEE Digital Avionics Systems Conference-Proceedings
JF - AIAA/IEEE Digital Avionics Systems Conference-Proceedings
M1 - 78
ER -