A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/982835
and we hope, given our experiences with Build 1, that this meeting ' s outcome will lead to better and more efficient processes in Build 2. A swap in the TFDM waterfall received final approval from Teri Bristol, LAX and SMF have traded Initial Ope rating Capability (IOC) dates. LAX's new IOC is December of 2020 and SMF's is now October of 2021. This means LAX is now the first Level 12 facility to get TFDM without any prior experience on the prototype electr onic flight strip system, AEFS. Having an electro nic flight strip system in play will help LAX reduce some physical and verbal coordination procedures currently in play in their complex system, which will increase their operating efficiency and allow them to focus even more energy on the movement of surf ace traffic. There is a new watch item/risk with TFDM dealing with the Adaptation of the local builds that w ill be available to all sites. Leidos initially proposed the adaptation tool be in XML format, not good for the typical controller without a comput er engineering degree. They have been working on building a more user - friendly version, which we got a quick look at last week. The newer version is not much better, if at all, and has been deemed unacceptable by the FAA, both NATCA and Terminal Se cond Lev el Engineering (TSLE). We are working to change direction and fix this issue before it does any damage to the training timelines we are currently working towards. Advanced Electronic Flight Strips (AEFS) The next build, 5.5.0.0, and its requirements have been finalized and the working date of late August for its suitability testing with installation and site testing/approval to occur sometime i n September is still the goal. This build will be dependent on what CLT will need with its interface with ATD - 2. There will be other minor improvements/enhancements made, but CLT and ATD - 2 are the priority driver of the build. Prior to installing and running build 5.4.0.0 in CLT, the engineering team at the tech center found numerous bug fixes that would increas e t he stability of the system. With the old build, a hard reset of the system was required every 7 days in order to ensur e that it would not freeze up. With the new fixes, we were hopeful that the reset schedu le would be closer to 14 days. Unfortunately, on the 13th day of testing in CLT, tech ops had to reset the system. CLT will remain on the new build with the old weekly reset schedule. We will test the reset duration again in CLE when we update their system, which we are currently still in the process of planning with the facility. CLT Nothing new PHX Nothing new CLE Nothing new LAS Nothing new SFO Nothing new EWR Nothing new