A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/587238
NTML requires a connection to the TFMS system. It will be helpful for smaller facilities that don't have access to TFMS and for special events. · In addition to the R12 items, the group also tested the Airborne Reroute (ABRR) functionality that was part of Release 11, but will not be activated until testing with ERAM is complete. o The second R12 OT session was scheduled for September 22 - 24 but was moved to October 14 - 15 due to power maintenance a t the Tech Center. R12 is scheduled for keysite testing at ZHU Oct 26 - Nov 6, with deployment on November 7. · September 2: Participated in a telcon with TFMS Sustainment. Reviewed the dates when the various TFMS Change Requests that were reviewed at our las t meeting would be implemented. There are several " patch " releases between the major TFMS Releases to address issues that are not working correctly or need improvement. · The TFM - DT (Traffic Flow Management Deployment Team) met September 15 - 17 at the FA A Tech Center in Atlantic City. Activities included: o Reviewed changes to the Route Amendment Dialog (RAD) box that is used with the Airborne Reroute (ABRR) and Pr edeparture Reroute (PDRR) tool. Most of the focus is on Field 11 to ensur e that the TMC is aware of any existing remarks in a flight plan before sending an amendment. o Reviewed many of the tool tips and error responses to ensure the meaning is clear. o Reviewed changes requested for the Collaborative Trajectory Options Pro gram (CTOP) tool scheduled for TFMs Release 13. o Reviewed the List Report tool tip messages and made numerous suggested changes to make them more plain language and less confusing. o Reviewed the Thin Client CBI. o Given an early look presentation o n TFMS Release 13. o Reviewed TFMS Change Request prioritization with the Program Office Sustainment team. o Conducted a dry run of the TFMS Release 12 OT&E session. o Reviewed some of the items being considered for Work Package 4. This is the next group of TFMS enhancements planned for the time period of 2016 - 2020. This session focused primarily on tools to improve prediction demand modeling for sectors. o Reviewed several CTOP scenarios being developed for end to end testing with airlines/custom ers. o Condu cted testing of the ABRR tool. As mentioned in previous updates, there were several problems with the logic used to merge flights onto new routes using the " merge " and " optimize " features. This was the first time testing the tool with corre ctions made to the programming. Unfortunately, there are still many issues that need to be resolved. · Then next TFM DT meeting is scheduled for October 14 - 15 at the Tech Center. · Attended the 2015 FAA Industry Technical Forum in Atlanta on S eptember 29 - 30. This meeting focused on briefing the industry of planned changes/improvements over the next 6 months. · Specific topics included: Decision Support Systems, TFMS Release 10 and