A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/597273
activities. · An issue occur red last week with TBFM at ZTL. o After the STARS install at A80, it was identified that there was code that STARS introduced to the system that is not within requirements, which created issues with TBFM. o The ZTL TBFM feed temporarily from A80 wa s temporarily cut. Lockheed Martin is currently working to correct this issue. TRAFFIC FLOW MANAGEMENT SYSTEM (TFMS): Cliff Keirce (DCC) is the TFMS Article 48 Representative. His report on the activities of TFMS for the past couple of weeks is below. · The Traffic Flow Management Deployment Team (TFM DT) met October 14 - 15 at the FAA Tech Center. Activities during this meeting included: o TFMS Release 13 early look. This is an opportunity for members of the group to have hands on time with the new release capabilities. Release 13 consists of: o SWIM (systemwide information management) TFM Data interfaces. o Departure Viewer. This is a new tool that is focused on showing departure data. It can be sorted by airports or departure fixes. There currently is not a member on the team representing towers/tracons. This is a tool that will most likely be used frequently by tower/tracon TMCs. I have asked that a tower/tracon TMC attend one of our upcoming meetings so that we can get their inpu t on this tool. o Additional reports that can be generated from the list reports tool or command line. o NTML advisories. Gives NTML users more flexibility in choosing which types of advisories they can subscribe to. o TFMS messaging. This is a new email system to be used for sending messages through the TFMS system. o TSD enhancements. New features available on the TSD. Most of these changes are enhancements to the Collaborative Trajectories Options Program (CTOP) tool. There are also enhancem ents to the FEA/FCA filtering tool. o OIS Summary Page enhancements. · There will be two Release 13 Operational Testing sessions, March 8 - 10 and March 29 - 31. Keysite testing will be at Atlanta Center April 18 - 28, with deployment planned for April 29. · Reviewed changes to the List Tool (part of TFMS Release 12 described in previous updates) that were recommended by the TFM DT and participants from the first R12 Operational Testing Session. Also reviewed changes to the Departure Viewer tool t hat were recommended by the TFM DT. · The TFM DT had a telcon with members of the ERAM team to review some concerns about the interaction between the TFMS and ERAM systems with routes sent from TFMS to ERAM through the Airborne Reroute (ABRR) Route A vailability Dialog (RAD) tool. · Met with the engineering team for CSC to discuss the changes that need to be made to the ABRR RAD optimize feature in order for it to behave as expected. It is hoped that these changes can be made in time for us to e xercise the tool at our next meeting in November.