A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/663490
them. We will push the sites to up level both of them – the STR gives them the option of 1 or both. - IFCET can travel home after 2 nd processor and router conf iguration has been completed. E mail already sent advis ing them of this. - We need to set up a telcon with ZLA, So Cal, and associated towers to discuss TEC routes. - Core Team m embers to attend Exit Briefs . - Need TO involvement in Exit Briefs . - Feedback that some Harris Site Leads (not all) are not knowledgeable about what needs to b e done for an IOC declaration. - Would be helpful to add a slide to the Pre - Launch deck about IOC declaration . - Core Team would really like us to push sites to do processor turn ups during the day shift – or later during the midshift so t hat a Core Team member is there for several hours during the morning "push" in case anything is incorrect in the adaptation. - Caucus time of 1 hour before the activity is excessive . W e will cut down the time to 30 minutes on future ORRs. - Many sites seem to want a trackball over a regular mouse for the TDLS system. This is due mainly to space limitations in the tower cab – there just isn't enough room to operate a regular mouse. AIMS 159754 has been opened as an ER on this. - Core Team requests that the Play Bo ok be sent as a separate file to the Core Team member that is on the site – instead of being buried in the slide deck. Went over Travel Policy and Time & Attendance to make sure that we are in compliance . Most important - We all left with the same message going forward and we all missed you! Everything discussed in the meeting will be implemented as noted or over the next few weeks pending further discussions with the responsible parties. o Published Route Issue in ATL: Harris has identified issues with 44 new CDRs in ATL that will go active in May. They are claiming that these 44 routes will not be loadable in CP DLC and will also error in PDC. Background: DataComm (V12) has implemented a route check in CPDLC, that was also carried over into PDC, to ensure t he route being sent is a loadable route in the aircraft FMS. Essentially DataComm (V12) searches for published routes and rejects anything that is different than the published route. When a facility attempts to alter the published route for local procedure s, these are rejected by V12. Unfortunately the routes that have been built for ATL are not loadable in the FMS for one of two reasons: leaving the SID midstream or the ADR ends at or after the AAR begins (overlapping segme nts).