NATCA Bookshelf

repeatedly happened with these tests - the variables are not constrained enough to determine what is producing beneficial changes. CDM Steering Group (CSG) has received a proposal for a new SCT tasking that will recommend SCT engagement with TFDM as it continues to be introduced to industry. The NextGen Integration Work Group (NIWG) will be presented this proposal in December, and, if approved, the SCT will move on it in early 2017. ENROUTE AUTOMATION MODERNIZATION (ERAM) Julio Henriques (ZNY) leads the ERAM efforts for NATCA. This update is provided by Dan Mullen (ZID). ZDC had to operate on EBUS for a short period during the midshift on Oct 20 when their system's internal clock got out of sync and the ERAM channel failed. This wouldn't normally have had an impact to the operation, but one of the two channels had been taken offline for testing. A new release of ERAM to prevent the problem from recurring was built and sent to all ARTCCs. The Test and Training Lab (TTL) phase of site testing the latest version of ERAM (EAD600) was completed at ZLC and ZSE the first week of November. That testing went very well, but when ZLC loaded the release on the Operational channel, a new problem was uncovered. We determined that there was not an acceptable mitigation to work around the problem, so the Operational phase of testing was postponed until a new release can be built and distributed. The Airborne Reroute (ABRR) and ERAM teams have been working for the last several months to get that program ready for deployment. ABRR and PDRR (Pre-Departure Reroute) will allow controllers and TMCs to use automation to distribute and accept Traffic Management Initiatives so they won't have to be hand written and retyped. There have been several software changes needed in both ERAM and TFMS software, and those changes will be complete by January. We've been working on a deployment schedule with the intention of making this program available prior to Swap Season this spring. The National User Team has weekly telcons to work automation issues and procedures. Some of their work the last few weeks includes: ER 166602 ERAM Processing Enhancement for non ICAO ER 162528 Multiple SD-Keys The task team will create a problem statement based on an adaptation solution. The desired behavior is to create more/different keys available through adaptation; this may include have two functions enabled by a single key. Data Com Use Cases Minor edits to two use cases are pending; these have been sent back to the Data Com team. Once these changes are completed all team members will have concurred with the updated use cases. ER 159834 GIMS Display of Transition Speed SIG 1674 CRR Auto Add Handoff to Non-US ER 167950 Changed Portion of Route not Cyan Coded The desired behavior is to correct the coordination of the "???" coding from ERAM to TFMS; currently this is not handled correctly. In addition to the problem statement the team discussed data analysis of incidences of XXX and ??? in routings today, how TMC's envision using the new tool and long term solutions for processing routes that contain ???.

• Cover