system wide information management swim n.
Skip this Video
Loading SlideShow in 5 Seconds..
System Wide Information Management (SWIM) PowerPoint Presentation
Download Presentation
System Wide Information Management (SWIM)

System Wide Information Management (SWIM)

133 Views Download Presentation
Download Presentation

System Wide Information Management (SWIM)

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. System Wide Information Management (SWIM) “SWIM and Making Service Orientation Pay Off” 9th SOA for eGovernment Conference Ahmad Usmani, SWIM Program Manager May 6, 2010

  2. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

  3. SWIM and the Evolution of Air Transportation SWIM supports FAA’s long-term goals for the Next Generation Air Transportation System to: • Allow more aircraft to fly more closely together on more direct routes • Reduce delays and congestion • Provide benefits for the environment and the economy through reductions in carbon emissions, fuel consumption, and noise Specifically, SWIM will support these goals by: • Providing more efficient operations • Streamlining communications • Connecting more FAA systems and airspace users

  4. Program Concept SWIM is an IT infrastructure program that will operate in the background to provide data to authorized users SWIM will: • Implement a Service-Oriented Architecture (SOA) in the National Airspace System (NAS) • Allow the FAA to create new system interfaces more quickly and more cheaply than is possible today • Facilitate the increased data-sharing that is required for NextGen SWIM is not: • A set of avionics equipment • A substitute for NAS modernization programs • A Telecom program

  5. Host ETMS WARP IDS/ERIDS ASDE ATOP ERAM STARS/ ARTS/ TAMR CIWS Inter-Agency TMA TFM STARS CARTS/ State of the System Business as Usual - More point-to-point unique interfaces - Costly development, test, maintenance, CM - New decisions linked to old data constructs - Cumbersome data access outside the NAS Today Enterprise Management FAA Systems ERAM AIM TFMS CIWS TDDS - Existing point-to-point hardwired NAS - Unique interfaces, custom designs SWIM Compliant Government Systems SWIM Compliant Non-Government Systems FTI ITWS LEGEND TBFM WMSCR DOTS SWIM Segment 1 SWIM Future Segment SWIM Adapter

  6. Terminal Controllers En Route Controllers Non-FAA Users (e.g., Airlines, DoDDHS, ANSPs) FAA Command Center NextGen Applications SWIM Infrastructure for Messaging FTI IP Backbone Conceptual Overview

  7. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

  8. Service SOA standardizes the necessary interfaces and behavior to support interaction SOA establishes services as the mechanism by which needs and capabilities are brought together SOA provides an organizing and delivery paradigm that derives greater value by reusing existing software solutions rather than duplicating capabilities S Capabilities performed by one for another to achieve a desired outcome Oriented O When capabilities are self-contained and independent to enable a collection of services to be linked together to solve a business problem Architecture A The fundamental organization of a system embodied in its capabilities, their interactions, and the environment What is SOA?SOA organizes technical capabilities in a standard way to allow flexible accomplishment of constantly changing demands

  9. SWIM – Selecting Services and the Information You Want

  10. SWIM is a SOA Implementation • SWIM provides: • SOA technology infrastructure • Governance to ensure that information management standards and processes are followed • Leads to consistent service development, operation and management enterprise-wide • By following SOA standards and principles: • SWIM makes services available on a network • Enables systems on the network seeking those services to invoke them without having to change or adapt to the underlying implementation of the service (i.e. loose coupling)

  11. What are the main SOA business drivers?Business dynamics are rendering current systems approaches obsolete Agility Process Interoperability Costs • Organizations are slow to respond to emergent business needs because the current systems are inflexible and difficult to change • Decision cycles are unnecessarily lengthened by data stovepipes • Customers are complaining that systems are not easy-to-use • Data is locked in many disparate sources and is not available to support cross-functional operations • Systems cause business process “lock-in” inhibiting evolutionary business improvements • The demand for systems and data interoperability within and external to the organization is continually growing • Inability of applications to interoperate due to platform incompatibility and proprietary interfaces • Organizational stovepipes limit the ability to exchange information and leverage capability • Business objectives and technology capabilities are not well aligned causing • poor returns on information technology investments, • inefficient operations, and, • lost business opportunities. • Duplicate systems result in higher costs Inability of technology to align with and respond to an organization’s mission Lack of agility, process redundancy, inefficient system interactions, and increasing costs

  12. What are the main SOA technology drivers? Agility Process Interoperability Costs • Technology assets cannot be quickly repositioned in response to strategic decisions • IT leaders can’t replace old technologies without significant cost and disruption • Technology and vendor lock-in inhibits the IT organization ability to change • Systems and organizations duplicate work • It is difficult to determine ‘what exists’ or “situational truth” because duplicate data and application functionality create contradictory information • Traditional systems development tightly couples systems to predefined and static business processes • Existing IT systems are very heterogeneous often with proprietary interfaces creating growing interoperability challenges • More time spent patching systems together than adding mission critical capabilities • Data used across an organization is often inconsistent and potentially inaccurate • Integrating data stovepipes is expensive and wasteful • IT maintenance and integration costs are becoming a larger percentage of the budget resulting in less money for new initiatives • Duplicate data entry and manual data reconciliation create higher labor costs Technology is not growing toward an organization’s mission

  13. Key Aspects of SOA for SWIM • Business and IT Alignment • Systems design is driven by a market forces model (supply and demand) • Systems are grown to evolve with the environment rather than designed and built as a fixed structure (a city vs. a building) • Adaptability • Agility: allow for rapid enhancement of services capability • Flexibility: enable on-demand composition and restructuring of services to meet business needs • Interoperability: • Priority on exposing capability for rapid consumption • Create ability for unanticipated utilization (emergent behaviors) • Leveragability: • Maximize utility of the services provided • Maximize utilization of existing services (eliminate/reduce development) • Scalability • Distribution of effort: widely distribute the development of capability • Distribution of value: enable wide access to capability

  14. What types of information are shared through SWIM? SWIM facilitates more efficient sharing of air traffic management (ATM) system information such as: • Airport surface movement information • Flight planning information • Airspace restrictions • Weather information • Traffic flow management information

  15. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

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

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

  18. Users Users NAS Application System Functions Application Application NAS System NAS System Service Interface Service Interface Service Interface Service Interface Messaging Messaging Interface Management Value-Added Services SWIM Service Functions Enterprise Service Management Service Security Boundary Protection Secure IP Network Connectivity Naming & Addressing Identity & Certificate Management Intrusion Detection and Response Information Technology Infrastructure Functions SWIM Functional Architecture

  19. FY09 Accomplishments Integrated Terminal Weather System (ITWS) Publication prototype service subscribed to by UPS, Harris, DoD, and FedEx; Memorandum of Agreement signed with NWA Trained developers from SWIM Implementing Programs (SIPs) on Progress FUSE Middleware SIPs have started systems engineering and design Conducting Service Oriented Architecture (SOA) suitability assessments of other FAA programs Finishing design for the Airspace Information Management (AIM) portion of the Special Use Airspace (SUA) Automated Data Exchange Developing Corridor Integrated Weather System (CIWS) Publication prototype service Received Final Investment Decision for Segment 1B (FY11-15) Phase 1 SWIM Registry operational SWIM COTS Repository operational

  20. FY10 Accomplishments Released the SWIM Segment 2 Technical Overview and draft Final Program Requirements Selected participants from industry to receive the Corridor Integrated Weather System (CIWS) Weather data. The CIWS SWIM prototype became operational in March 2010 Selected an additional industry partner (FedEx) to receive the SWIM-compliant data via the Integrated Terminal Weather System (ITWS) Prototype Service Met with Single European Sky ATM Research Joint Undertaking (SESAR JU) to discuss commonality and interoperability between future SWIM environments

  21. 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 Joint Resources Council (JRC) Final Investment Decision Respond to Integrated Baseline Review (IBR) findings

  22. 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, DoD, and FedEx; MOA signed with NWA Initial participants selected for CIWS SWIM prototype, including Delta Airlines, Raytheon Company, ARINC, Harris Corporation, Kent State University, and WSI Corporation

  23. ITWS-SWIM Prototype Productivity

  24. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

  25. Segment 2 Overview Goals Support data exchange needs of NextGen Build on Segment 1 Governance, for all NAS programs that score high on the SOA Suitability Checklist Expand SWIM infrastructure to include additional Enterprise Service Management, Security, other SOA infrastructure services, and Core services that were delegated to the SIPs in Segment 1 Segment 2 JRC planned for summer FY10, to request baseline funding for FY12 – FY15

  26. EA SV4 NAS Enterprise Services (SWIM Segment 2)

  27. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

  28. To learn more about SWIM, please visit our website… The website describes the SWIM program and provides news announcements for current issues 1

  29. Agenda • Introduction • SWIM and SOA – Business Drivers and Benefits • Segment 1 Overview • Segment 2 Overview • How to Learn More • Q&A

  30. Questions and Comments? Risk Management