3 User Forum Logistics Date: July 9, 2015 - 2:30 pm – 4:00pm Location: Noblis Lakes Conference Rm – A&BGo-to-Meeting: Please register for “SWIM Users Forum” at SWIM website:User Forum briefing distributed via invitation & on SWIM website
4 SWIM Users Forum - Overview Purpose: Monthly forum for SWIM Users to obtain program updates, provide feedback, obtain answers to SWIM related questions or data concernsScope: SWIM Portfolio of ServicesAeronautical DataFlight and Flow DataWeather Data
5 SWIM Users Forum – Overview (cont.) Forum Participation:NAS and non-NAS consumersAirlines, Industry service providers, research & development, FAA Programs, AirportsAverage attendees 1st four sessionsSWIM Resources:SWIM website:NSRR:SWIM Help Desk:1-855-FAA-NEMC ( ) Option #3, “Enterprise Services” for phone supportfor support
6 SWIM Flight Data Publication Service (SFDPS) Status, Capabilities, Benefits, Cost Savings, and Future CapabilitiesJuly 9, 2015Chris Pressler Lead Engineer SWIM Program
7 Summary What is HADDS and SAFA? What is SFDPS? SFDPS Phase 1 Schedule SFDPS Phase 1 Benefits
8 What is SWIM Flight Data Publication Services (SFDPS)? SFDPS makes Air Traffic Control Center (ARTCC) data available to authorized consumers as SWIM services including the following received from a legacy system called HADDS:En Route Flight DataEn Route Airspace DataEn Route Operational DataEn Route General Message Data
9 What is a Host ATC Data Distribution System (HADDS)? HADDS is an Air Traffic Control legacy system providing 49 different message types referred to as the Common Message Set (CMS). HADDS has a complementary system called Store and Forward Application (SAFA) providing much of the same data.These messages can be roughly categorized as follows:Flight DataAirspace DataOperational DataGeneral Message DataTraffic Management Data
10 SFDPS System Diagram SFDPS Services En Route Flight Data Service LEGENDCMS – Common Message SetEDDS – ERAM Data Distribution SystemERAM – En Route Automation ModernizationFIXM – Flight Information Exchange ModelFTI – FAA Telecommunications InfrastructureHADDS – Host ATM Data Distribution SystemNEMS – NAS Enterprise Messaging ServicesSFDPS – SWIM Flight Data Publication ServiceSWIM – System Wide Information ManagementXML – Extensible Markup LanguageSFDPS ServicesEn Route Flight Data ServiceEn Route Airspace Data ServiceEn Route Operational Data ServiceEn Route General Information Message ServiceERAMEDDS(HADDS)SFDPSFTI /NEMSSWIMConsumersCMSFIXM / XML
11 SFDPS Phase 1 Schedule Baseline MilestoneAPB PlannedDateDurationFlight Data Publication OT&E complete (SIP=FDPS)Mar-1481 monthsFlight Data Publication operational (SIP=FDPS)Jul-1597 monthsRef: SWIM Segment 1 Acquisition Program Baseline (APB) CIP G05C.01-01Deployment to Key Sites (SLC & ATL)PlannedNEMCCompleted04/2015SLC04/23/201505/2015ATL05/13/2015APB Duration as of July 2009FDP OT&E has code S30, as shown backup slide
13 SFDPS Prospective Consumers FAA ProgramsTFMSTBFMTFDMPDARSNOPData CommSTDDSR&D OrganizationsMITRENASAMIT Lincoln LabUniversity of North Dakota UASAviation CommunityPASSURJetBlueDelta AirlinesFedExAerospace EngineeringBoeing ATMCSC DUATSGeneral Dynamics Information TechnologyMosaic ATMNetJetsNoblisNorthrop GrummanThales
14 What are SFDPS Phase 1 Benefits? Service Oriented Architecture (SOA)Compliance with International Standards FIXM and AIXM in XML formatUse of SWIM Infrastructure and Core ServicesBetter Services for More UsersSFDPS vs HADDS/SAFA PlatformsDelivering NEXTGEN ImprovementsSaving the big bucks
15 Advantages of Service Oriented Architecture HADDS and SAFA do not use SOA and any of the capabilities listed belowDeveloping an SFDPS client can be accomplished in a day using simple SWIM program examples to connect and receive dataSFDPS uses Publish/Subscribe and Request/ResponseConsumers receive custom services meeting specific needs rather than one size fits allDramatically reduces bandwidth requirements because of filteringEliminates stovepipe connections to existing ARTCC centric interfaces with up to 20 separate interfaces needed to receive flight information from departure to arrivalSFDPS provides loosely coupled XML services for easy user integrationRedundant connections to SFDPS services are optionalData exchange, Routing, Filtering, Transformation, Security are available with SFDPS
16 Use of SWIM Infrastructure and Core Services HADDS/SAFA does not use SWIM Infrastructure or NEMS shared core servicesSFDPS uses NEMS hardware and software infrastructureSFDPS uses numerous core services for performing filtering, routing, failover, Pub/Sub, data exchange and Request/Response, security, etc.Use of all of these core services including new core services available in SWIM S2B provide capabilities that far exceed the legacy HADDS/SAFA services
17 Compliance with International Standards HADDS and SAFA do not provide any of the features listed belowSFDPS data is SWIM compliantSFDPS data uses FIXM and AIXM standardsSFDPS provides clean data eliminating the ARTCC centric data with redundant and conflicting updatesHADDS data is complicated to work with because of duplicate messages and conflicting messages when more than one center is processing the same flight. This requires users to perform special processing.Replaces HADDS once size fits all distribution with customizable Pub/Sub and Request/ResponseSFDPS uses the ERAM supplied GUFI and makes it into a FIXM compliant GUFI.This feature will eliminate software problems resulting from ambiguities.
18 SFDPS vs. HADDS/SAFA Platform HADDS and SAFA use older technology systems with custom software with both systems located at all 20 ARTCCsSFDPS uses state of the art consolidated scalable hardware and softwareSFDSP is consolidated at SLC and ATLSFDPS will be supportable far longer than HADDS/SAFA with the existing technology
19 Better Services for More Users The HADDS and SAFA systems exist in 2 separate platforms to satisfy the needs of different users and require special access.Sensitive Data Filtering rules will be available for all NAS and Non NAS consumers via NEMS/NESGSensitive Data Filtering from SFDPS means a single service will serve a much larger group of consumersSFDPS services will provide several service options:All current data with information tagged to assist the user with handling duplicates and conflicting dataAll data cleaned to eliminate duplicate and conflicting dataAn SFDPS user can have data reconstituted
20 Better Services for More Users (cont.) The HADDS and SAFA users would be required to consume, process and filter all of the flight data from the selected ARTCC for the systems listed below to receive the data needed.SFDPS data can be filtered to meet very specific requirementsUsers like TBFM will be able to avoid processing a significant volume of flight data irrelevant to their objectivesUsers like TFDM will be able to create a subscription for departure and arrival flights specific to their airportTAMR/STARS will be able to create a subscription for departures, arrivals and overflights specific to TRACONAn SFDPS client can be developed in a day with simple SWIM program provided examplesAn SFDPS user can request 15 days of historical data
21 Saving the Big BucksSFDPS Phase 1 reduces the cost of delivering CMS data to consumers over the legacy HADDS and SAFA systems in the following ways:SFDPS saves money for NAS and Non NAS usersSFDPS Phase 1 can provide all of the data needed by SAFA systems eliminating the need for 2 servers located at all 20 ARTCCsSFDPS Phase 1 will be less expensive to maintain with a smaller footprint at 2 locationsSFDPS Phase 1 will be less expensive to maintain because it operates on state of the art, shared, commercially available hardware and software with a longer shelf life.CMS data users transitioning to SFDPS will require far fewer connections to receive SFDPS data.Systems currently connecting to all or several HADDS or SAFA systems to receive data will substantially reduce bandwidth costsSystems using filtering to limit the volume of data to specific subscriptions will reduce bandwidth costs
22 Delivering NextGen Major Investments Legacy SystemNextGenRadarVoice CommunicationsDisparate InformationSatelliteVoice & Digital CommunicationsAutomated Decision Support ToolsEn-routeTower controllerTerminalTerminalTowerNextGenAutomatic Dependent Surveillance-Broadcast (ADS-B),DataComm, National Airspace System (NAS) Voice System (NVS),Terminal Flight Data Manager (TFDM), System-Wide Information Management (SWIM)NextGen airspace efficiency, operational predictability and airspace access benefits depend on several major infrastructure investments including:Development of more precise sensor technologies (ADS-B fused with Radar)Development of integrated automation addressing separation assurance and traffic flow control (ERAM, TAMR, TFM)Development of flexible networked voice and data (DataComm, NVS)Development of more robust information sharing to support collaborative decision making (SWIM, TFDM)FoundationalEn Route Automation Modernization (ERAM)Terminal Automation Modernization/Replacement (TAMR)2222
23 STDDS 3.1 Patch Release July 9, 2015 Jeri Groce STDDS Program Manager
24 STDDS 3.1 Patch Release ASSC data Issue identified with the ASSC packet captured data.PTR assignedPTR verification and testing planned – late JulySoftware build/adaption – late JulyKey site NCT (SFO data) planned – mid AugustKey site CLE ( BUF data) planned – early SeptemberFollow –on ASSC sites planned – STDDS R 3.2
25 NSRR 2.0 Federal Aviation Administration July 9, 2015 Mark Kaplun Governance Lead, SWIM Program
26 NSRR 2.0 Major Objectives The NSRR 2.0 will support: Discovery of NAS Services through enriched service meta-data.SWIM Governance Processes prescribed by SWIM Governance policies and regulations.Registries integration between FAA and EUROCONTROL SWIMs.
28 Support of SWIM Governance Policies NSRR 2.0 will support service lifecycle management processes to ensure metadata completeness and integrity in compliance with SWIM Governance Policies and other Governance regulations.
30 Technical ApproachCurrent proprietary system with its limited capability for customization, Systinet HP, is replaced with an open-source web publishing framework, Drupal, with almost no limitations on possible modifications.Both NSRR 2.0 and European SESAR Registry are built on the Drupal v.7 platform.Drupal /ˈdruːpəl/ is a free and open- source web publishing framework written in PHP and distributed under the GNU General Public License. It is used as a back-end framework for at least 2.1% of all Web sites worldwide ranging from personal blogs to corporate, political, and government sites including whitehouse.gov and data.gov.uk.
31 VPN Connection Process July 9, 2015Michelle Head Enterprise Security Infrastructure Manager FTI Security Harris Corporation
32 FTI VPN Briefing Agenda NAS Enterprise Security Gateway VPN Overview FTI VPN RequirementsConnection OptionsTips for a Successful On-boarding Call
33 NAS Enterprise Security Gateway (NESG) Provides secure data transfer between the NAS and external entities via the use of specific application architectures and data flowsPrevents unsecured traffic from entering the NASAggregation Points for AccessInternet connectivity or Dedicated Telecom Services, depending on whether availability is criticalFewer connections needed by external userConsistent security policies
34 VPN Overview What is a VPN? A Virtual Private Network (VPN) implements a restricted access network that makes use of public network infrastructure. The VPN encrypts communications between hosts so that only the machines within the network can access and understand them.A VPN establishes a virtual tunnel ensuring that any communications and information traveling through it remains secure, even when running on public networks.
35 VPN Overview Site-to-Site vs Remote Access: Site-to-Site VPNs connect entire networks to each other. Traffic is sent and received through a VPN gateway, which encapsulates and encrypts outbound traffic, then sends it through a VPN tunnel to a peer VPN gateway at the target site. Only Site-to-Site VPNs are supported for FTI NESG connections.Remote Access (Client-based) VPNs connect individual hosts to private networks. Every host must have VPN client software, which encapsulates and encrypts traffic before sending it to the VPN gateway at the edge of the target network. Remote Access VPNs are not supported for FTI NESG connections.Upon receipt, the target VPN gateway strips the headers, decrypts the content, and relays the packet towards the target host inside its private network.
36 FTI VPN RequirementsRequirements are the same for R&D, FNTB, and operational environmentsSite-to-Site VPNAt least one fixed public IP addressUnique IP address per NAS ProgramPermit only required application traffic (Source/Destination IP, TCP port); prohibit all other access.IPSec with pre-shared key, AES-256
38 Connection OptionsConnections between the external user and the gateway are secured using Virtual Private Networking based on IPSec for all connections.User-provided Dedicated Transmission Service (DTS) – Ethernet:LAN based Ethernet connection attached to the gatewayRequires established point of presence physically collocated with the gatewayUser-provided Dedicated Transmission Service (DTS) – Serial:External user provides a dedicated circuit attached to the gatewayFAA-provided T1/E1 interfaces integrated with the gatewayNo external user equipment at the FAA gateway location beyond the digital demarcation
39 Connection Options (cont.) Internet Based Virtual Private Network (VPN):Public Internet transport mechanismNo external user equipment physically installed at the gatewayPrivate Network Based Virtual Private Network (VPN):External user-provided private network service as the wide-area / long-haul transport mechanismA private network access device is typically required at the gateway
42 On-boarding TipsPre-configure your VPN connection settings before the callPre-shared key will be received on the callHave your network engineer available during the callFor R&D and FNTB environments, only one VPN connection is needed
43 SWIM Calendar July August September DEVELOPMENT/UPDATE 2015 SFDPS ISD Briefing 7/16/15SWIM Users Forum -2nd Thursday/Month8/13/15SWIM Users Forum -2nd Thursday/Month9/1015SFDPS ISD Briefing 7/1615SWIM Interactive Developer Workshop9/22-24/15ATIEC Conference8/25-27/15@ NOAAFYI: 60th Annual ATCA Conference & Exposition11/1-4/15
45 Post-User Forum Survey: We want your feedback Note: Your comments and your contact information (if applicable), will not be shared outside of the SWIM User Forum planning team. If the survey results are presented publicly in a future Forum or in an internal FAA capacity, the User Forum planning team will not disclose names associated with the comments.
49 Delivering NextGen Improvements Legacy SystemNextGenRadarInefficient RoutesVoice CommunicationsDisparate InformationFragmented Weather ForecastingWeather Restricted VisibilityForensic Safety SystemsNationwide FocusSatellitePerformance Based Navigation (fuel savings)Voice & Digital CommunicationsAutomated Decision Support ToolsIntegrated Weather InformationImproved Access in Low VisibilityPrognostic Safety SystemsFocus on Congested MetroplexesNextGen implementation is organized into foundational and transformational programs, and other activities that enable operational capabilities and improvements.We will have much of our foundational infrastructure in place in the near future.By 2015, the agency expects to have largely completed the infrastructure that will enable additional layers of operational improvements, with TAMR being completed at large TRACONs by May of 2016.Think of this foundation as an iPad, on which NextGen “apps” can be loaded to provide benefit in the NAS.The iPad, itself, is not NextGen, but the capabilities it enables are.It is on this foundation that the FAA will continue to implement the transformational technologies that provide operational benefits to users throughout the NAS.Performance Based Navigation (PBN) will improve operational efficiencies much like upgrades to the U.S. interstate system improved our highways. Because we have updated our automation systems, we can increase use of PBN to deliver benefits to users like savings in time, fuel, and reduced emissions.