Aircraft Access to SWIM (AAtS)

1. Aircraft Access to SWIM (AAtS) Demonstration and Prototyping Information Exchange Briefing Matthew de Ris, Title> November 3, 2010

2. Description What is it? • At present: A Concept • Aircraft Access to SWIM (AAtS) – The aircraft is Accessing the SWIM network. • What is available on SWIM is potentially available to the aircraft Why do we want it? • So in-flight users have the same information the FAA uses to make its ATM decisions. • Scalability is key. • New data elements can be added with much greater ease. • New data is made available to the cockpit by granting it access to the additional data elements in SWIM.

3. Aircraft Access to SWIM (AAtS) How does it work? • Details are still to be determined • Industry input needed • Givens • The FAA has no current plans to build a specific supporting infrastructure. • AAtS is not intended to replace existing or planned systems

4. SWIM / AAtS Global Harmonization / Interoperability issues • Minimal impact on aircraft avionics / EFB equipage for initial early implementation • Intend to leverage existing or planned equipage • Eventual requirements should be defined by intended use • Intend to leverage existing or planned standards and requirements as much as possible • Global data sourcing issue still needs to be established • With IP connection, location alone does not determine access to SWIM data (local or global). • Connection to SWIM data (local or global) is only determined by the authenticated IP session. • Example: A flight en route to Hong Kong is transiting Beijing Airspace. Due to IP connectivity, a connection to FAA SWIM data is enabled. Where does the FAA receive its data source for Beijing airspace if the flight only has access to FAA SWIM?

5. Key Players • Many moving parts • Global Interoperability a challenge unless everyone coordinates

6. Future Plans • Working Group meeting • November 17th • Discussion of Initial ConOps Draft • FY11 • Interface process description • Industry Day • Initial Validation efforts • Initial Use Case development • Mature Concept of Operations • Continued engagement with global standards groups • Pivotal role in RTCA SC206 standards development

7. Backup

8. AAtS Architecture • What we believe as of today: • SWIM data is provided at the NAS Enterprise Security Gateway (NESG) for qualified subscribers. • Operators can choose how they wish to get the data to/from the aircraft within FAA guidelines. • Operators will choose their level of vetting and reconciliation of the SWIM data to/from the aircraft within FAA guidelines. • Operating with the assumption that an EFB or an EFB-like device will be an acceptable means to display AAtS data. Industry input needed.

9. How things may work - Notionally