En Route Automation Modernization
Air Transportation
August 10, 2012
En Route Automation Modernization
En Route Automation Modernization (ERAM) is a system that is planned to replace the old en route air traffic control (ATC) automation system. The old system consists of the Host Computer System (HCS), The Display System Replacement (DSR), and the User Request Evaluation Tool (URET). Today those three systems are used at 20 ATC centers in the continental United States. ERAM is being made to provide a more safe and efficient ATC service. ERAM changes are intended to benefit controllers by increasing their efficiency, improving their situational awareness and decision making, reducing their workload, or reducing the frequency or impact of mistakes (Allendoefer, 2006, pp.1). However it may be possible that there will be some unintended negative affect on the controllers.
To try and make ERAM a more safe and proficient system there are a few main areas that will be changed from the old system. The main changes are listed as followed:
Backup and redundancy capabilities of ERAM
Areas of Interest (AOI)
User interface (UI)
Tracker
Safety Alerts
In the legacy system, a failure of the HCS forces controllers to use the backup system with reduced capabilities, which reduces operational efficiency (Allendoefer, 2006, pp.2). Depending on which facility you are taking about, the backup system is either the Enhanced Direct Access Radar Channel (EDARC) or the Enhanced Backup Surveillance (EBUS). EDARC has fewer functions than the HCS in the flight data processing and safety alert areas. EBUS is a more up to date backup system than the EDARC but still does not have the full capability as the HCS. By the time ERAM is deployed, EBUS will have replaced EDARC at all ATC centers (Allendoefer, 2006, pp.6). ERAM is equipped with a full function redundant backup system that is equivalent to the primary. Having this redundant backup system is intended to reduce the negative effects in
August 10, 2012
En Route Automation Modernization
En Route Automation Modernization (ERAM) is a system that is planned to replace the old en route air traffic control (ATC) automation system. The old system consists of the Host Computer System (HCS), The Display System Replacement (DSR), and the User Request Evaluation Tool (URET). Today those three systems are used at 20 ATC centers in the continental United States. ERAM is being made to provide a more safe and efficient ATC service. ERAM changes are intended to benefit controllers by increasing their efficiency, improving their situational awareness and decision making, reducing their workload, or reducing the frequency or impact of mistakes (Allendoefer, 2006, pp.1). However it may be possible that there will be some unintended negative affect on the controllers.
To try and make ERAM a more safe and proficient system there are a few main areas that will be changed from the old system. The main changes are listed as followed:
Backup and redundancy capabilities of ERAM
Areas of Interest (AOI)
User interface (UI)
Tracker
Safety Alerts
In the legacy system, a failure of the HCS forces controllers to use the backup system with reduced capabilities, which reduces operational efficiency (Allendoefer, 2006, pp.2). Depending on which facility you are taking about, the backup system is either the Enhanced Direct Access Radar Channel (EDARC) or the Enhanced Backup Surveillance (EBUS). EDARC has fewer functions than the HCS in the flight data processing and safety alert areas. EBUS is a more up to date backup system than the EDARC but still does not have the full capability as the HCS. By the time ERAM is deployed, EBUS will have replaced EDARC at all ATC centers (Allendoefer, 2006, pp.6). ERAM is equipped with a full function redundant backup system that is equivalent to the primary. Having this redundant backup system is intended to reduce the negative effects in
References: Allendoerfer, K. R., & Galushka, J. (1999). Air traffic control baseline methodology guide (DOT/FAA/CT-TN99/15) Allendoerfer, K. R., Galushka, J., & Mogford, R. H. (2000). Display system replacement baseline research report (DOT/FAA/CT-TN00/31) Allendoerfer, K. R., Pai, S., & Zingale, C. (2006). An analysis of en route air traffic control system usage during special situations (DOT/FAA/TC-TN06/11) Allendoerfer, K. R., Zingale, C., Pai, S., & Willems, B. (2006). En route air traffic controller commands: Frequency of use during routine operations Federal Aviation Administration. (2002). Blueprint for NAS modernization 2002 update. Retrieved May 23, 2006 from http://www.faa.gov/nasarchitecture/Blueprint2002.htm Federal Aviation Administration Federal Aviation Administration. (2004). Progress report of the Automation Metrics Test Working Group (AMTWG) Federal Aviation Administration. (2004, October). National Airspace System en route configuration management document: Computer program functional specifications - Federal Aviation Administration. (2005, June). En route automation modernization automation metrics and preliminary test implementation plan, version 2.7 Galushka, J., Frederick, J., Mogford, R., & Krois, P. (1995). Plan view display baseline report (DOT/FAA/CT-TN95/45)