Aerospace Systems Exchange for Advanced Development Programs

1. Complex Aerospace Systems Exchange (CASE) • New event created to share problems, insights and lessons learned on large complex system developments. • First offering of CASE was in September 2012. • CASE 2013 will be part of the Aviation Forum. • Hyatt Regency Los Angeles. • August 12-14, 2013.

2. Complex Aerospace Systems Exchange (CASE) • In 2012, CASE was collocated with SPACE. • Programs were not integrated, although SPACE and CASE worked to avoid schedule conflicts. • For 2013, CASE will be part of the AVIATION FORUM. • First attempt at an integrated forum event under the AIAA New Event Model. • CASE will have it’s own program, but we will be more closely coupled with the rest of the AVIATION Forum program as well.

3. Organizational/Operational Structure for the 2013 Aviation Forum Aviation 2013 Executive Committee Plenary The Big Picture General Chair – Jim Vasatka CASE systems level stuff General Chair – Allen Arrington Technical ATIO, etc General Chair – David Maroney Main themes from Plenary level work through systems/integration and on into Technology Planning Committee Program/Track Chairs Session/Panel Chairs and Organizers Planning Committee Program/Track Chairs (3 -4 Tracks) Session/Panel Chairs and Organizers Planning Committee Program/Track Chairs Session/Panel Chairs and Organizers

4. Starting actions for CASE 2013 • Determine Track Themes. • 2012 Tracks were: • 1: Complex Systems Development • 2: Integration, Test and Validation of Complex Systems • 3: Project Management of Robust and Resilient Systems • Continue with these? Alter? Add? • Track Chairs and Co-Chairs. • Three Track Chairs have signed-up: Laura McGill, David Dress and Sophia Bright. • Need Co-chairs for each Track. • Track Chairs will need to start building their programs (identifying session topics, session chairs). • Session Chairs will have the job of building each session. • Relying on invited presentations, panels. • Do we even want to try a “call for papers” or use the “call or proposals” approach that we used last year? • Planning Committee will work each of these topics….and more. • Use lessons learned and other feedback from 2012 to help shape CASE 2013. • Determine the general layout and flow of the event • I’ve taken at first shot at this; see the next chart.

5. Possible program layout for CASE • Just a starting point; not cast in concrete. Will need to marry this with the Plenary and Technical pillars. • Somewhat mimics 2012 program layout with lead-in workshop and 2-days worth of sessions. • Retaining the opening and closing plenary sessions. • Shorted session blocks to 2-hours each, so up to 6 session times for each track. • Nothing says that each track has to use all 6 blocks; could leave some gaps to that folks can attend the other tracks.

6. Operations • What we did last year seemed to work pretty well, so we’ll stick to that formula, at least to start. • Weekly telecons with the planning committee to get the program in order, identify topics, speakers, session chairs, etc. • Additional telecons with focused groups (perhaps track specific) as needed to work issues. • Use the AIAA SharePoint site for storing/sharing documents. • I will get that set up and have you all added to the access list. • We had a couple of planning spreadsheets in play for the 2012 event (one for the general planning and a second for the program (track and session) details. • Abdi and I will make sure that there are notes from each telecon so that folks can keep up on that plans, status and actions (particularly actions!). • A face-to-face meeting at the Aerospace Sciences Meeting (January in Grapevine TX), is probably a good idea, at least for the folks who will be attending ASM (so not a mandatory gathering).