We Guide You Home

Traffic Flow Management System (TFMS)

Ryan Jacobs is the NATCA TFMS Representative. 

Background:  TFMS is a data exchange system for supporting the management and monitoring of national air traffic flow. TFMS processes all available data sources such as flight plan messages, flight plan amendment messages, and departure and arrival messages. The National Airspace System (NAS) Data Warehouse assembles TFMS flight messages into one record per flight. TFMS is restricted to the subset of flights that fly under Instrument Flight Rules (IFR) and are captured by the EnRoute computers. TFMS is the main tool used at the Air Traffic Control System Command Center. 

TFMS continues to struggle with contract uncertainty. Despite that uncertainty, R14 is still projected to be released later this year. As a deployment team we met remotely several times. Twice we met discuss AIMS tickets from a previous Ops Evaluation and review the solutions that CSRA had produced. We invited ABRR/PDRR representatives from ERAM to join us as well. This was the first time we had done this AIMS ticket verification remotely, but we were able to resolve most of the tickets that we reviewed successfully.  

One issue that did arise during the AIMS ticket review was the wording of error messages. We determined that one of the error messages associated with PDRR was too vaguely worded. We later me to work on rewording the error message so the TMC would know exactly what the issue was and be able to correct it if the amendment failed via PDRR.  

While R15 and R16 have been tabled for now our team continues to discuss certain items we had already been working on that would have been part of those releases. One of those items is the runway monitor that would have been part of R16. We discussed where that window should be accessible from both the surface viewer and a TSD. Another item we discussed from a future build is the fix monitor. We discussed how to arrange and manipulate the different columns and the concept for how they would operate as a prefset. 

Another one of these issues for a potential future release had to do with reroute modeling requirements. The previous requirements for reroute preview, model and display had never been met so we discussed what to do moving forward. Everyone agreed that the most important aspect was the preview and that it needed to perform as quickly as possible. We discussed with CSRA how many flight segments were associated with commonly used routes and the need for performance while using those routes.  

Another task we had was to assist in the development of FMDS by discussing and compiling the most used quick keys with TFMS. We provided feedback and our human factors specialists compiled the data to show which we some of the most used quick keys that should be considered for FMDS. Another consideration that was discussed is that the Command Center has different needs than the field facilities since TFMS is their primary tool. 

Tech refresh for TFMS is almost complete with ZOB being completed in February and ZAU in March. 

Jump to top of page