SWIM Concept presented December 2009 for EUROCONTROL Conference


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Core of Program Concept How SWIM lowers information costs: Uses standard interfaces and new protocols such as XML. This greatly reduces the amount of software that must be created share data between FAA systems. How SWIM increases speed for new interfaces: Use of standard interfaces reduces customization time. Plus, XML protocols eliminates the need for “information consumers” to write special parsing program to figure out which data they need. The ability to manage data at a lower cost (and faster setup speed) means more data sharing… which increases common situational awareness and improved agility.
  • SLIDE #2 Also mention: Safety is paramount. Global harmonization is essential. Environmental stewardship must be a focus. We understand what must change in order to realize NextGen. We are working to implement the foundational programs today, and define the future building blocks that enable mid- and far-term operational capabilities. We have identified timelines and budgets to support them.
  • Alternate slide for: Connectivity to Other NextGen Programs Rationale for this structure: Matches the NextGen decision-making paradigm with the three fundamental enabling air/ground capabilities: ADS-B for precision input from the aircraft systems DataComm for real-time complex trajectory management exchanges SWIM for situational awareness and system level feedback to the planning processes Leverages time-honored safety practices of FAA lower safety levels for advisory and situational awareness services allow faster, more dynamic evolution IAW industry standards and commercial practices higher safety levels for separation and trajectory management ensures only data that’s a “must have” is subjected to the rigor and high cost Allows the individual supporting systems to evolve in a federated fashion minimum dependencies to achieve some level of benefit allows systems to operate cooperatively without needless or arbitrary dependencies Allows properly separated and efficient use of spectrum
  • Sub: expected with “as obligated by the Service Contract”
  • SWIM Concept presented December 2009 for EUROCONTROL Conference

    1. 1. System-Wide Information Management (SWIM) SWIM in General (Concept)
    2. 2. SWIM is: <ul><li>A Concept </li></ul><ul><li>A Next Generation Air Transportation System (NextGen) Transformational Program </li></ul><ul><li>An FAA Technical Solution </li></ul>
    3. 3. Program Concept <ul><li>SWIM will : </li></ul><ul><li>Implement a Service-Oriented Architecture (SOA) in the NAS </li></ul><ul><li>Lower information costs </li></ul><ul><li>Increase speed to establish new interfaces </li></ul><ul><li>Increase common situational awareness </li></ul><ul><li>Increase NAS agility </li></ul>SWIM is an IT infrastructure program that will operate in the background to provide data to authorized users
    4. 4. Business as Usual Today State of the System - Existing point-to-point hardwired NAS - Unique interfaces, custom designs - More point-to-point unique interfaces - Costly development, test, maintenance, CM - New decisions linked to old data constructs - Cumbersome data access outside the NAS Enterprise Management LEGEND SWIM Segment 1 SWIM Future Segment SWIM Adapter FAA Systems SWIM Compliant Non-Government Systems SWIM Compliant Government Systems FTI TFMS CIWS TDDS ITWS WMSCR AIM TBFM DOTS ERAM Host WARP IDS/ ERIDS ATOP CIWS TFM TMA STARS/ ARTS/ TAMR ERAM ASDE ETMS Inter- Agency CARTS/ STARS
    5. 5. SWIM Concept <ul><li>Migrate the National Airspace System (NAS) to a service oriented architecture </li></ul><ul><ul><li>Facilitate ease of establishing interfaces between computing and information systems </li></ul></ul><ul><li>Get the “right information to the right place at the right time”: Net Centricity </li></ul><ul><ul><li>Facilitate Shared Situational Awareness </li></ul></ul><ul><ul><li>Facilitate Collaborative Decision Making </li></ul></ul><ul><li>Establish governance over information management </li></ul>
    6. 6. NextGen: Improving Service Delivery Ground-based Navigation and Surveillance Air Traffic Control Communications By Voice Disconnected Information Systems Air Traffic “Control” Fragmented Weather Forecasting Airport Operations Limited By Visibility Conditions Forensic Safety Systems Satellite-based Navigation and Surveillance Clearance Trajectories and Routine Information Sent Digitally Information More Readily Accessible Air Traffic “Management” Forecasts Embedded into Decisions Operations Continue Into Lower Visibility Conditions Prognostic Safety Systems Today’s NAS NextGen
    7. 7. Air Traffic Operations <ul><ul><li>Aircraft & Operator Requirements </li></ul></ul>Airport Development NextGen Transformational Program Integration ADS-B SWIM DATA COMM NNEW NVS Trajectory Based Operations X X X X X High Density Arr/Dep Terminals and Airports X X X X X Flexible Terminals and Airports X X X X X Collaborative ATM X X X X Reduce Weather Impacts X X X X X Safety, Security and Environment X X X Transform Facilities X X X X X X X X X X
    8. 8. Integration of Key NextGen Programs NAS Voice Switch Data Comm ERAM NNEW Weather Information Publication Flight Flow Management ADS-B Stations Government System Non Government System SWIM Flight Flow Information ADS-B
    9. 9. ATM Decision Timeframes, Required Information Exchanges, and Required Services and Infrastructure <ul><li>Trajectory Based Operations </li></ul><ul><li>Airborne Separation Assistance </li></ul><ul><li>Trajectory negotiations/resolutions </li></ul><ul><li>Aircraft Intent & Status Downlink </li></ul><ul><li>Taxi instructions </li></ul>TFM Reroutes PDC Revisions Air Traffic Management Decisions Collision Avoidance Separation Management Trajectory Management Flow Management Capacity Management Required Information Exchanges Sensor Registration Command and Control Conformance Monitoring Real-time Planning Collaborative Planning Safety Target Level/Design Assurance Lower (D/E, 4/5) Higher (C, 3) Strategic Planning Seconds Days Minutes <ul><li>Airborne SWIM Characteristics </li></ul><ul><li>Advisory data </li></ul><ul><li>Commercial spectrum, market driven </li></ul><ul><li>User defined requirements: </li></ul><ul><ul><li>Authentication </li></ul></ul><ul><ul><li>Reliability </li></ul></ul><ul><ul><li>Delivery (e.g. best effort) </li></ul></ul><ul><ul><li>Latency </li></ul></ul><ul><ul><li>Controls and displays </li></ul></ul><ul><ul><li>FMS integration </li></ul></ul><ul><li>International usage based on reach of service provider </li></ul><ul><li>DataComm Characteristics </li></ul><ul><li>2 way Command and Control exchanges </li></ul><ul><li>VHF Band Protected spectrum </li></ul><ul><li>Safety Assessment Drives : </li></ul><ul><ul><li>High reliability </li></ul></ul><ul><ul><li>High safety assurance levels </li></ul></ul><ul><ul><li>Guaranteed delivery </li></ul></ul><ul><ul><li>Low latency </li></ul></ul><ul><li>International usage based on agreements </li></ul><ul><li>Standardized controls and displays </li></ul><ul><li>FMS integration </li></ul><ul><li>ADS-B Characteristics </li></ul><ul><li>Position and intent Broadcasts </li></ul><ul><li>L-Band Protected spectrum </li></ul><ul><li>Safety Assessment Drives : </li></ul><ul><ul><li>High reliability </li></ul></ul><ul><ul><li>High safety assurance levels </li></ul></ul><ul><ul><li>Contention broadcast/receive filtering </li></ul></ul><ul><ul><li>Low latency </li></ul></ul><ul><li>International usage based on agreements </li></ul><ul><li>Standardized controls and displays </li></ul><ul><li>FMS integration </li></ul>TDLS ERAM SAMS NNEW TFM Collaborative ATM Trajectory Negotiations Weather Airspace status NOTAMS Airline SOC DoD/DHS GBT STARS
    10. 10. Governance Basics <ul><li>Definition </li></ul><ul><ul><li>Ensuring and validating that assets and artifacts within the architecture are acting as expected and maintaining a certain level of quality. (Gartner, 2007) </li></ul></ul><ul><li>Components </li></ul><ul><ul><li>WHO is responsible </li></ul></ul><ul><ul><ul><li>Governance Authority </li></ul></ul></ul><ul><ul><ul><li>Service Providers </li></ul></ul></ul><ul><ul><ul><li>Service Consumers </li></ul></ul></ul><ul><ul><li>WHAT must they do </li></ul></ul><ul><ul><ul><li>Governance Policies </li></ul></ul></ul><ul><ul><ul><li>Service Contracts </li></ul></ul></ul><ul><ul><li>HOW must they do it </li></ul></ul><ul><ul><ul><li>Standards </li></ul></ul></ul><ul><ul><ul><li>Governance Processes </li></ul></ul></ul>
    11. 11. Simplified NextGen NAS SV-4 Framework Interaction Services Mission Services Support Services (Content Management /Data Acquisition) SOA Core Services Technical Infrastructure Services Enterprise Governance Administrative Services
    12. 12. SWIM Governance Policies Outline <ul><li>STRATEGIC SOA </li></ul><ul><ul><li>SOA Technology Acquisition </li></ul></ul><ul><ul><li>Enterprise Architecture </li></ul></ul><ul><ul><li>Opportunity Management for SOA Services </li></ul></ul><ul><ul><li>Interoperability, Reuse and Standards </li></ul></ul><ul><ul><li>SWIM Enterprise Services Registry/Repository </li></ul></ul><ul><li>SOA/SERVICE DESIGN POLICIES </li></ul><ul><ul><li>Namespace and Schema </li></ul></ul><ul><ul><li>Service Interface Design </li></ul></ul><ul><ul><li>Services Technical and Design </li></ul></ul><ul><ul><li>Information Security </li></ul></ul><ul><ul><li>Service Development Process </li></ul></ul><ul><ul><li>Service Lifecycle Management </li></ul></ul><ul><ul><li>Services Operations Readiness </li></ul></ul><ul><ul><li>Service Provisioning </li></ul></ul><ul><ul><li>Service Consumer </li></ul></ul><ul><li>RUNTIME AND OPERATIONAL </li></ul><ul><ul><li>Messaging and Routing </li></ul></ul><ul><ul><li>Runtime Security </li></ul></ul><ul><ul><li>Service Management </li></ul></ul><ul><ul><li>Maintenance and Support </li></ul></ul>