1 / 38

System-Wide Information Management (SWIM) Program and Delivery

System-Wide Information Management (SWIM) Program and Delivery. Agenda. Program Overview and Status Core Services ATM Services and Data Flows Prototyping Future Segments. SWIM Program Structure. SWIM Program Team Key Roles. Program Management.

Download Presentation

System-Wide Information Management (SWIM) Program and Delivery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. System-Wide Information Management (SWIM) Program and Delivery

  2. Agenda • Program Overview and Status • Core Services • ATM Services and Data Flows • Prototyping • Future Segments

  3. SWIM Program Structure

  4. SWIM Program Team Key Roles Program Management • Responsible for leading and directing the activities of the SWIM Team in the development, test, and deployment of SWIM; Resource Planning and External Acquisition • Responsible for Acquisition Services Program Management, Acquisition Strategy Planning, Acquisition Contract Management Program Control • Responsible for Business Management, Risk Management, Metrics Management, Earned Value / Schedule Management / Investment Baseline Reviews, Investment Analysis, Budgeting and Capital Planning Requirements (e.g. OMB Exhibit 300) • Responsible for Planning & Prototyping Management, Stakeholder Coordination, Concept Exploration, Program Evolution, Future Segment / Service Planning, Prototyping Evolution & Coordination • Responsible for definition and management of SWIM functional and non-functional requirements, (i.e. Security, Safety, Configuration/Interface Management, Quality, and other specialty engineering) and the definition and management of the architecture to meet SWIM requirements and SWIM Governance (program and technical) throughout the system and services lifecycle Requirements & Governance Implementation • Responsible for Implementation Management, SIP Coordination, SIP Engineering Support, SWIM Lab Management, Software Component Selection

  5. Segment 1 Overview NWS ATCSCC ARTCC 1 AOCs AOCs ERAM AIM SUA NESG NNCC WJHTC FTI WMSCR TFMS CIWS ERAM TDDS TRACON 1 TFMS DRC ATCT 1 TDDS VNTSC TDDS ITWS

  6. Program Status • Joint Resources Council (JRC) Final Investment Decision was made on 20 June 2007 • Two-year baseline (FY09 and FY10) approved • SWIM returned to the JRC in FY09 for approval to complete the development and deployment of SWIM Segment 1on 15 July 2009 • Five-year baseline (FY11 – FY15) approved • Segment 2 JRC planned for summer FY10, to request baseline funding for FY12 – FY15

  7. Current SWIM Capabilities Capabilities will be implemented as multiple services over the next five years

  8. Segment 1 Program Overview • Nine Segment 1 capabilities were derived from Communities of Interest: • Aeronautical Information Management (AIM) • Flight & Flow Management (F&FM) • Weather • SWIM is not implementing a separate infrastructure for Segment 1 • SWIM is leveraging existing infrastructures, processes, resources, and logistics chains that are part of the program offices implementing the 9 SWIM capabilities • SWIM Governance is ensuring use of common protocols and interfaces, assisted by use of commercial software for some Core Services

  9. NAS Domains ERAM CIWS ITWS TFM SWIM Federation AIM TDDS NAS WMSCR SWIM Is Federated

  10. Segment 1 Schedule

  11. Priorities for FY10 • Provide SWIM-compliant information to more external users/agencies/aircraft • Procure and start operating SWIM service registry v2.0 • Deploy AIM SUA Automated Data Exchange • Conduct Segment 2 JRC Final Investment Decision • Respond to Integrated Baseline Review (IBR) findings

  12. Agenda • Program Overview and Status • Core Services • ATM Services and Data Flows • Prototyping • Future Segments

  13. Core Services Components • Core Services SWIM supports include: • Interface Management • Messaging • Security • Enterprise Service Management

  14. Publisher Requirements for SWIM-Compliance • Use of FUSE Software • SOAP Message Processing • Java Message Service (JMS) Provider Standardization (Apache Active MQ) • Supported Message Formats and Transports • SOAP-over-HyperText Transfer Protocol (HTTP)/HyperText Transfer Protocol Secure (HTTPS) • eXtensible Mark-up Language (XML)-over-HTTP/HTTPS • SOAP-over-JMS • XML-over-JMS • SOAP Attachments • Message Transmission Optimization Mechanism • JMS Message Type - Text message • Registry / Repository • Discoverability – Web Services Description Language (WSDL) • Categorization – SWIM Taxonomy • Service Management – Java Management Extensions (JMX)

  15. Systems Engineering Deliverables • “GFE from SWIM” package for SIPs • Package will contain: • Service Container Software • SIPs will implement and administer servers to run SWIM-provided service container software • Core Services • At a minimum, standards will be specified for all core services • Governance, policy, and guidance • SWIM Approved Products List

  16. FUSE Software Contract • Contract award to Iona Technologies on August 18, 2008 • Indefinite Delivery Indefinite Quantity • Base year + 12 option years • Contract options: • Software • Documentation • Support Licenses • Training • Consulting Services

  17. Progress FUSE Software • FUSE Suite • Apache Servicemix 3.x • Apache CXF 2.x • HQ 3.x • Apache Camel 1.x • Apache Active MQ 5.x • Artix Suite • Artix Registry/Repository • Artix ESB C++ • Artix Connect for WCF • Artix Security • Artix Enterprise Management Service Plug-in • DataXtend Semantic Integrator (DXSI) • Progress Actional Team Server (MindReef SOAPScope)

  18. XML Gateway • Currently, three vendors have met the FAA's XML Gateway requirements and have successfully passed a technical evaluation of their product's installation and initial configuration, as well as system performance, including: • Layer 7 Technologies - Secure Span product • Cisco Systems, Inc. - ACE XML Gateway product • Vordel, Inc. - VXG2 XML Gateway product • Their products were deemed capable of providing support to the SWIM Implementing Programs (SIPs) • This QVL is valid through March 31, 2015 • The QVL will be reviewed annually

  19. Agenda • Program Overview and Status • Core Services • ATM Services and Data Flows • Prototyping • Future Segments

  20. ARTCC ERAM ERAM ERAM NASR AIM COI FAA HQ Current SUA Status and SUA updates SUA updates ATCSCC FTI SAMS SUA updates

  21. FTI Gateway Weather COI VOLPE WJHTC ITWS ARTCC CIWS ITWS products ERAM CIWS Products NWS PIREPs ITWS, CIWS, WMSCR products FTI ITWS, CIWS, WMSCR products PIREPs & Altimeter data NNCC AOCs WMSCR

  22. F&FM: ERAM and Terminal SWIM ZDC WJHTC ATCSCC TFMS SAMS NORAD SUA Data Flight Data ICE Gateway (FTI) FTI Flight Data Flight Data ERAM TDDS TDLS EFSTS ARTCC ASDE-X RVR Terminal Cluster (TRACON & TOWER)

  23. WJHTC TFMS TPC F&FM: TFMS and Terminal SWIM ARTCC ERAM ZDC TFMS DRC Flow Data, Reroute Data Flow Information, Surface, & Reroute Data (Backup Data) FTI Surface Data TDDS Flow Information, RVR, and Reroute Data TDLS EFSTS AOCs AOCs ASDE-X RVR Terminal Cluster (TRACON & TOWER)

  24. Agenda • Program Overview and Status • Core Services • ATM Services and Data Flows • Prototyping • Future Segments

  25. ITWS/CIWS Prototyping • Two programs are actively participating in SWIM prototyping • SWIM-Compliant ITWS and CIWS data products are now available • ITWS Publication prototype service subscribed to by UPS, Harris, and DoD; MOA signed with NWA and FedEx

  26. ITWS-CIWS Summer 2009 Product List

  27. ITWS-CIWS 2010 Product List

  28. ITWS Prototype Service Demonstration

  29. Segment 2 Prototyping • Conducted at SWIM Lab at FAA Technical Center • Prototype implementation of an Enterprise Service Bus (ESB) • Purpose is to help refine requirements for SWIM Segment 2

  30. Agenda • Concept • Architectural Context • Program Overview and Status • Core Services • ATM Services and Data Flows • Prototyping • Future Segments

  31. SWIM Roles • Leadership in Developing Enterprise Service Orientation in the NAS • Understanding NextGen and NAS Objectives which Require SWIM Capabilities • Identification and Evaluation of Information Management Technologies and Processes for the NAS Enterprise • Governance via Industry Standards

  32. SWIM SOA Suitability Checklist

  33. Suitability Scorecard 28 total items Step #1 Summary of scoring Step #2 Value range Step #3

  34. NASEAF SV4 NAS Enterprise Services (SWIM Segment 2)

  35. Near Term • SWIM Segment 2 • Operation Services Environment Definition (OSED) • Requirements • Architecture • SWIM Air • SWIM Interagency • SWIM International • Federated vs Consolidated

  36. Segment 2: Desired Capabilities • Desired capabilities include: • Current Special Use Airspace (SUA) status • Current Temporary Flight Restrictions (TFRs) • Improved information on Notices to Airmen (NOTAMs) • Automatic Terminal Information Service (ATIS) information • Automated Weather Observing Systems (AWOS) information • More timely flight plans filed • Improved real-time delay reporting • Current route closures and corresponding reroutes status • Improved Airport surface lineups status reporting • Establishment of single centralized route database

  37. Mid Term • SWIM Segment 3 • Operation Services Environment Definition (OSED) • Requirements • Architecture • SWIM Air • SWIM Interagency • SWIM International • SOA to Cloud Computing?

  38. SWIM Web Site www.swim.gov

More Related