A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/597273
adaptations. The S6 transition could leave the OSF maintaining up to 5 adaptations. The different adaptions are required because the TCW allocations are different from the old building to the new, thus requiring separate platforms. With an S6 transition it would require adaptions for G1, G4, R27 (bridge to S6), R2A (S6 baseline), finally R4. This gets very complicated for the stak eholders and without a current Training Delta to brief the differences between the systems to controllers. The tentative plan is to stay with the legacy system to the new building, then follow the nature progression to upgrade to S6R4. Although this is t he most organic way to transition, the risk is with the availability of the Dell 710 RAIDS. This is end of life hardware, and an increasingly hard piece of equipment to secure. The plan is for the program to continue to use the Dell 710s from ELITE facil ities upgrading to X2000. The stockpile will support facilities with failing RAIDS throughout the NAS, until X2000 is available to G4 systems. L30/LAS were briefed on the difficulty ahead and have requested to attend the next R4 risk mitigation testing e vent, which NATCA agrees to. o S46 (Seattle) suffers a dual RDP failure, resulting in transitioning to full EFSL. Complaints ranged from not having data blocks in EFSL, to taking up to 10 minutes for the system to recover. The RDP failure was due to a keyboard command that was accepted, but should have been rejected. This flaw has been identified and is in process of correction. The facilities slow recovery was due to not following proper transition procedures from Air Traffic and Tech Ops. These pro blems were also recognized locally and will be dealt with, with refresher training for all. This should be a call to action for ALL facilities to test their new G4 capabilities, so they will be ready in case of system failure. The 10 minute delay in reco very is within the 15 minute allowable time frame. o PHL (Philadelphia) TRACON starts key site for V2.04 (more debugging software) for the MDM3. It also allows more data collection capability, to help TSLE track down issues with the MDM that have been r eported NAS wide. TERMINAL FLIGHT DATA MANAGER (TFDM): Matt Baugh (IAH) is the Article 48 for TFDM. His report for this week is below: · Monday - Traveled to DC, Ops staff meeting, AEFS 5.3.0.2 build meeting o We are in the process of selecting another key site for phase two of the EFSTS replacement keyboard project. o There will be a site survey to PHL and BNA for phase one sometime within the next 6 weeks. They are coordinating with the facilities to determine a good time. o The DALR time sync has been installed into the current build and is updating to the AEFS screens as requested. · Tuesday – Participated in the weekly AEFS update, and a SVT meeting o CLE and PHX both had screen freezes this last week, an issue the team is hoping will become less frequent with the new build coming to both facilities by mid Nov. o For SVT they are looking at asking two facilities to run a 45 day test on