A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/823383
Airborne Reroute and Pre - Departure Reroute (ABRR / PDRR) Conformant Route ind icators were enabled May 7th. The se chevrons in the flight plan indicate a segment of the route protected by a Traffic Management Initiative that should not be altered. This step, along with the deployment of EAD600, allows for the full use of ABRR and PD RR. This tool, which allows for Tr affic Management reroutes to be pushed to the sector and accepted by the controller, has been in development for several years and should greatly simplify rer outes for TMCs and controllers. The ERAM team finalized a deployment plan with the Data C omm team for the software release bringing the Data C omm functionality. EAE100 should be available for the Test and Training Lab by October 2017 and the Operational versi on will be ready by March 2018. This will allow the Data Comm keysites ( ZKC, ZID, and ZME ) to begin testing the new functionality. Below is a summary of some of the issues being worked by the National User Team: ER 175725 Block Altitude Probing and Posting The team discussed the ER; it deals with the ACL posting behavior of a formation flight in a block altitude where some of the aircraft were Non - RVSM. The team determined that no functional changes were needed. ER 175723 Relevant Leg Indicator The AIMS ticket was discussed, it describes undesirable behavior with the Relevant Leg Indicator; speci fically, the continued display of the indicator when a second leg no longer exists. The site will change the ticket to an ER and promote it to national so that the issue can be addressed. ER 174189 UM154 Radar Service Termination The draft use case was di scussed, the desired behavior is when Data Comm enabled flights enter a non - radar environment allow the controller the ability to uplink an independent Radar Service Terminated Message, UM154, to inform the flight of termination of radar services. The use case has both a keyboard command and menu input m ethod for entering the message. The team needs to determine if both methods ar e needed in the final use case. The draft was sent out for review and will be discussed again next week. ER 174400 Disable Data Com Route Messages A draft problem statement was discussed, its desired behavior is to create a dynamic switch that will allow ARTCCs to turn off the Route functionality of Data Com m . Additionally, the type of switch, what functions it would control and th e training component were discussed. The document was sent for review and will be discussed again next week. AIMS 173242 Emergency Alerts single line too short for some Emergency PIDs Ray Berndt briefed the team on issues with the Emergency Message PID be havior with respect to the Alert, PID Menu , and History Views. There are still some unanswered questions regarding what information will be displayed in the views; once this is resolved the final proposed change would be brought back to the user team. The briefing material was sent to the team as a reference.