90 likes | 102 Views
Simplified Subs Update. A&D Meeting April 18, 2001 Rick Oiesen, Volpe Center. Simplified Subs Testing Update. 6 April 2001: The last human-in-the-loop test was extremely successful for FSM and ETMS, though there was limited participation by the airlines. ETMS problems found: (already fixed)
E N D
Simplified Subs Update A&D Meeting April 18, 2001 Rick Oiesen, Volpe Center
Simplified Subs Testing Update • 6 April 2001: The last human-in-the-loop test was extremely successful for FSM and ETMS, though there was limited participation by the airlines. • ETMS problems found: (already fixed) • New SS messages (e.g., Sub Off, FA Delay, Purge) were not going out over ARINC (though successfully going out over CDMNET). • Slot Create for flight with IGTD of 0000 got stored as 0001, caused later sub to reject. • Not all ETMS internal database updates for Slot Create were done, although data appear correctly in the ADL and the slot list. • FSM problems found: (already fixed) • Handling of bad slot name in Java controller. • 25 April 2001 (next Wednesday): Next HITL test scheduled
Overview of the Current FAA Deployment Schedule • 23 April 2001: Limited deployment of FSM 1.8.1 to SFO position. • 1 May 2001: FSM deployment to FAA sites, • 4-5 May 2001: Full ETMS 7.2 deployment on the midnight shift.
Transition Overview • 23 April 2001 (Monday): FSM 1.8.1 will be deployed at the SFO position. • Operationally • Operational EDCTs will be issued to FAA personnel and to the airlines exactly as they are now. • Airlines will sub exactly as they do now with SI messages. • The only operational person who will see any difference is the ATCSCC specialist working the SFO position. • No operational ETMS hub site software will be changed (except for some comm software). • On ETMS test strings • New ETMS 7.2 hub site software, including SS software, will be running. • SFO GDPs will be received in the new slot list format. • Operational subs will be received in old SI format. • 23 April – 4 May 2001: The new software on the test strings will be tested with the old-style SI subs. (This is the point of this limited pre-deployment.) • Before 4 May 2001: FAA and airlines will all deploy FSM 1.8.1 everywhere. • 4-5 May 2001 (Friday/Saturday late night): The ETMS hub site will be upgraded to the new ETMS 7.2 software. FSM 1.8 will no longer work.
Transition Overview (continued) • 5 May 2001, early morning: FAA and airlines will delete historical files and restart FSM 1.8.1. • Starting on 5 May 2001: FSM 1.8.1 and ETMS 7.2 will be used to run all GDPs. Airlines are still getting old-style EDCTs and using old sub software. • 5 May 2001 or later: Airlines will upgrade their CDM data feeds to include slot hold flag settings. (Before 5 May, these messages will be rejected by ETMS.) • Each airline runs for some period of time using old subs to be sure this works correctly. • When an airline is ready to switch to simplified subs, it coordinates with the CSA, (703) 904-4451, at the ATCSCC one day ahead of time so that bridging status and configuration files can be changed. • If an airline needs to fall-back from simplified subs to old subs, notify the CSA.
Configuration Issues • New configuration files control what data is sent to what addresses. • Are EDCTs (old format) sent, and where? • Are slot lists (and other SS messages) sent, and where? • What SS clients can connect? • Planned deployment configuration: • Only EDCTs will be issued, using same addresses as current system. • No slot lists or other SS messages will be issued. • When airlines want to start getting slot lists and SS messages, the point of contact is the CSA at the ATCSCC.
What Do Airlines Need to Do? • Prior to 4 May 2001: Airlines must have FSM 1.8.1 installed and running operationally. • On 5 May 2001: Because of the incompatibility between the old and the new ADL formats, airlines must either: • remove FSM historical files after 0800Z on May 5 and restart controller or • bring down controller on night of May 4 and restart on morning of May 5 after 0800Z • Prior to 5 May 2001: Airlines must NOT send any SS messages. • In particular, do not send the slot hold flag on any CDM message. • ETMS will reject such messages prior to May 5.
What Do Airlines Need to Do? (cont) • An airline must notify the CSA at the ATCSCC when it wants to start using simplified subs. To configure, the following is needed. • If connecting through CDMNet, what IP addresses will your SS clients use? • Where do you want slot lists sent when a GDP/compression is issued (ARINC address and/or CDMNet)? • Where do you want other SS messages, e.g., Sub Off, Purge, FA Delay, to go (ARINC address and/or CDMNet)? • Do you still want to receive EDCT messages? • Where will you send SS messages from (ARINC address and/or CDMNet)? • NOTE: When you become a simplified subs user, ATCSCC will eliminate your bridge-only status. • An airline must notify ATCSCC if it falls back to its old sub software if it wants to regain bridge-only status.
A Change that Affects All Airlines: New Rule for Treating Former Pop-up Flights • On May 5, your existing subbing process should work as it always has with one exception: former pop-ups. • The new restriction is: • If you create a flight after a GDP is issued, it gets an FA delay and cannot be subbed. (No change.) • When the program is revised or extended, that flight gets an EDCT and is now considered a “former pop-up”. • You can use a former pop-up in subs except that you cannot use its slot to move up another flight. • If you cancel a former pop-up flight, its slot goes back to the general pool.