Data Communications Implementation Team (DCIT)

1. Data Communications Implementation Team (DCIT) DCIT #11 Meeting 12/01/2011 To: DCIT By: Gregg Anderson

2. Agenda • Welcome – Gregg Anderson • Introductions & Roll Call – Jerry Smith • DCIT #10 Minutes & Action Item Review – Jonathan Rappaport • Go Button – Kevin Grimm • CONOPS: Initial DCL – Jerry Smith • P-45 / Cleared as Filed – Gregg Anderson • Trials Site Selection and MOUs – Gregg Anderson • Trials Test System End-to-End Architecture • DCL End-to-End Scenario Review – Rob Mead • En Route Trials look ahead – Rob Meade • DCIT Working Group Results – Fry, Onken, Boyd, Maki, Smith • Open Discussion – Gregg Anderson/Rob Mead

3. Data Communications Implementation Team (DCIT) Welcome – Gregg Anderson

4. Data Communications Implementation Team (DCIT) Introduction & Roll Call – Jerry Smith

5. Data Communications Implementation Team (DCIT) DCIT #10 Minutes and Action Item Review – Jonathan Rappaport

6. Data Communications Implementation Team (DCIT) Go Button – Kevin Grimm

7. Data Communications Implementation Team (DCIT) CONOPS: Initial DCL – Jerry Smith

8. Data Communications Implementation Team (DCIT) P-45 / Cleared as Filed Gregg Anderson

9. Potential Impact of Providing DCL’s at 45 minutes prior to P-time • Operational • Flight Plan would need to identify DCL aircraft • Impact on strip printing at 45 minutes • Impact of flight data available without flight strip • Impact of beacon code not available at 45 minutes • Impact of “autosend” of beacon code at 30 minutes • Controller may process DCL’s twice • Impact of EDCT time not available until 30 minutes • Impact on processing of revisions • ERAM • Additional requirements increases risk for inclusion in Release 4.2 • New Logic changes for FDP • Beacon Code Assignment • Adding Flight object data to identify DCL • Possible Logic Changes relating to flight strip printing and flight plan state change

10. Potential Impact of Providing DCL’s at 45 minutes prior to P-time • TDLS • CHI • New indicators to accommodate differentiating PDC/DCL • New Revision Indicators • Redisplay of flight data • Revisions may require multiple windows of information • System • ERAM/TDLS Interface Changes • TDLS Data Management Logic • TDLS Schedule will move to the right • Other Programs that may be impacted • Potential impact on 20+ other systems • e.g. ARMT, EFSTS, ARTS, STARS, • Programmatic • Analysis costs • Schedule negatively impacted • Services/Benefits Delayed

11. Data Communications Implementation Team (DCIT) Trials Site Selection and MOUs – Gregg Anderson

12. Data Communications Implementation Team (DCIT) Trials Test System End-to-End Architecture Pete Muraca

13. Data Communications Implementation Team (DCIT) En Route Trials Look-Ahead – Rob Mead

14. Data Communications Implementation Team (DCIT) DCL End-to-End Scenario Review – Rob Mead

15. DCIT Working Group Results – Andy Fry, Andrew Onken, Ron Boyd, Matt Maki, Jerry Smith Data Communications Implementation Team (DCIT)

16. Data Communications Implementation Team (DCIT) Open Discussion – Gregg Anderson / Rob Mead

17. Letter of Commitment Submissions