A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/913906
The next TSAS meeting is scheduled for the week of Nov . 27th at D01. The agenda includes one day with Leidos going over the t raining capability delivery as well as two days of continuing adaptation work. The week of 11/27 the TBFM Ops team will be visiting SCT al ong with representatives from ZLA to review and discuss the plan to implement IDAC at the TRACON. This purpose of this meeting will mainly be to plan out what will be the first IDAC installation/training activity at a TRACON. Up until this point , IDAC tool s have been utilized to replace phone calls to the ARTCC from t owers where IDSTs have been installed. Moving forward, starting at SCT, IDST will be able to be utilized by the TRACON to schedule departures directly into TBFM from select Towers. Additionally , Ops team representatives will participate at the next TSAS meeting at D01 the same week. TRAFFI C FLOW MANAGEMENT SYSTEM (TFMS) Brian Campos (DCC) represents the NATCA membership as their Article 114 Representative to the TFMS project. His report is belo w. Field 11 Prototype for the RAD reached wrap - up position to provide an at - a - glance status that will not be confusing. Assumptions are still expected to detect the FRC whether the user types it or it pre - existed when they brought the flight in, no manual intervention by the user to indicate the presence of an FRC and finally a key feature of adding a mouse - over and right - click capability to the Remarks button. This is tentatively expected around an 18 - month development cycle. Further tweaks are always exp ected. RAD war ning boxes after selecting SEND needed some tweaking. When a user sends amendments, all are held if any of them get warning boxes. The goal is to send what doesn't need a second look, and then address any remaining warning boxes. Some of the warning boxes could be from multiple flight plan issues or within 45 minutes of departure time. In addition to this issue, better indication will be necessary to suggest multiple flights plans exist rather then the current blue P - time, which could be over looked. A hover - over the blue P - time to show the multiple flight plans may be one of many options to help this scenario. Multiple flight plan amendment on a flight with multiple flight plans, TFMS will send amendments for all of the flight plans. The ame ndment status displayed to the TMC applies only to the TFMS current flight plan. TFMS does not display the amendment status of the other flight plans; therefore, if ERAM rejects any of the other amendments, the TMC may not have visibility of this error. Da ta showed this being a low risk occurrence. However, improvements can be expected to identify better multiple flight plans and their statuses in all situations. R13 P9A TFMS software release was critical in passing to get Chevrons and ABRR/PDRR turned ba ck on. The week of TFMS DT meeting involved pretesting assistance to the WJHTC center's test team. This corrected and created an understanding of some flaws still needing tweaking for official testing the following week with ERAM/TFMS joint testing of the P9A release.