1. A Rationale for Collaboration Leverage technical, resource and political strengths of participants Create core energy and shared purpose to advance airborne internet architecture concept and business opportunities Provoke consideration of new paradigms for communications, navigation and surveillance information and data exchange to support transportation stakeholders (specially non traditional) Propel public and industry investment otherwise not likely or possible (high risk initiatives) Create mechanism for industry consensus based standards

2. Next (Today’s?) Considerations Begin to define desired activities/studies beyond SATS Identify the core group of participants Clearly articulate a mutually acceptable group purpose/vision/ objective(s) Share and discuss personal/organizational interests Define an acceptable work concept/process Identify Champion, Sponsors and Advocates Identify and confirm core memberships (CNS, PMEI, Microsoft, ITT, Dataline, FAA, NASA, etc)

3. Considerations Continued Begin to develop (integrate input) Work Plan Begin to develop Resource Plan - Avoid competition for government funding Begin to define/assess issues (organizational and technical) Define product concepts sufficiently to encourage membership and collaboration Assemble alliance/alliances for specific/defined tasks (Begin to consider SATS Lab relationship?) Seek the “killer app!”

4. FAA Participation Options Technical Participation Technical demonstrations - Target generation facility - Air Traffic Labs - Aircraft/Flight experiments Leadership - Private Sector…Ralph/Pete must be able to tell FAA Executives that Collaboration is industry led Funding?* - Task specific - Sustaining - Limited to CRDA, matching or task contracts * Commitment dependent of level of energy and purpose of emerging collaboration … early indications/expressions of interest