A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/565556
changes to facilitate ARTS IIE replacement in the most expeditious and responsible way possible. o Aug 27, 2017, the SEG2 monitored the TSLE Shakedown out brief for the installation of the G4 STARS ELITE at the Denver OSF. o Aug 27, 2015, Joe Yannone and Frank Stahler (Region X) dialed into the weekly CTD test preparation meeting. The CTD has yet to be certified for deployment in the NAS and the work that Joe and Frank are doing is vital to a successful deployment of this digitizer. ยท STARS/TAMR Phase 1 update submitted by Jimmie White - PHL o Monday 8/24: Weekly TAMR Staff Meeting. Risk Identified with bringing F11 (Orlando) and A9 0 (Boston) up on the new RAIDS (X2000). X2000 RAIDS can only be deployed with R4 (merge build) software. R4 has slid to the right by two months putting the R4 run for record at the end of January or early February. Then Key site and national release bef ore X2000 can be key - sited. The tentative plan is to use the two DELL RAIDS in the testing lab at WJHTC until the X2000 can be deployed. o Tuesday 8/25: MDM meeting. Testing V2.03 is still planned during the Sept. R4 risk mitigation event. The test will operate FSL in digital and EFSL in analog. The goal is prove stability in this configuration. But first the test team has to buy off on the plan. The question mark is how the team can determine any flaws found were due to R4 flaws and not V2.03. Pending this is a go and proved during the risk mitigate event, the program will request a key site at S46 (Seattle). The goal is to mitigate the issues that have stifled the MDM engineers while proving the long held belief that the S46 MDM issues are ana log driven. Between TSLE and Esterline, they are almost out of options with finding the root cause of the MDM3 issues. The hope is that the digital input will eliminate all MDM problems at the site. o Wednesday 8/26: R3 Drop 11 OT&E Regression passed without issue. This software fixes a beacon code mismatch. Aircraft on the runway were acquiring with airborne aircraft tracking near the departure airport while climbing through Ten Thousand feet. Also, we observed the stitching issue at I90 was resolv ed via software. The tracking was smooth and steady where as before, the track update in a certain area of the display jumped quite a bit. o Thursday 8/27: Risk and Opportunities meeting. Big topic with what to do for A90 with respect to the RAIDS sit uation. This is complicated due to the fact R4/X2000 won't be ready and no other build supports the direct radar feed to BOS tower. Two options for discussion are, can BOS deal without DRF until X2000 is ready to be released to the field. If no, can A90 work FSL on G4 and EFSL in G1. Theoretically it could work, but this has to be proved. Further discussions to come. o Friday 8/28: Tag up meeting. Phase 1 rep reports X2000 complications and best case scenario, with all testing and key site efforts going successful on a first run, allow R4/X2000 to be nationally deployed in the middle of May 2016. Further slipping could put other I.O.C.'s at risk. o Saturday 8/29: S56 (Salt Lake City) declares I.O.C.