System Wide Information
Presented to:   Japanese Civil Aviation Bureau Presented by: Jay Merkle SWIM
Today Enterprise Management FAA Systems - Cumbersome data access outside of NAS System Wide Information Management (SWIM) October 22, 2008 2 SWIM
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 NAS •  Lower information costs •  Increase speed to establish new interfaces •  Increase common situational awareness •  Increase NAS agility System Wide Information Management (SWIM) October 22, 2008 w SWIM The Plan Enterprise Service Bus (ESB) Security Messaging Interface Management Enterprise Service Management
LEGEND
System Wide Information Management (SWIM) October 22, 2008 4 Segment 1 Overview . Nine Segment 1 capabilities were derived from three Communities of Interest: ▷ Aeronautical Information Management (AIM) ▷ Flight & Flow Management (F&FM) > Weather ● SWIM will not implement a separate infrastructure for Segment 1 ▷ SWIM will leverage existing infrastructures, processes, resources, and logistics chains that are part of the program offices implementing the nine SWIM capabilities ▷ SWIM Governance will ensure use of common protocols and interfaces, assisted by use of commercial software for some Core Services
5
SWIM Segment 1 Capabilities AIM SUA Automated Data Exchange Weather CIWS Publication ITWS Publication PIREP Data Publication Capabilities will be implemented as services by SWIM Implementing Programs (SIPs) over the next five years Flight & Flow Management Flight Data Publication Terminal Data Distribution Flow Information Publication RVR Publication Reroute Data Exchange System Wide Information Management (SWIM) October 22, 2008 6 SWIM
System Wide Information Management (SWIM) October 22, 2008 7 SWIM
Establishing SWIM governance via standards & coordination with EAB Established relationship with ATA, AOPA, NBAA and RAA for airspace Return to JRC Investment analysis
System Wide Information Management (SWIM) October 22, 2008 8
System Wide Information Management (SWIM) October 22, 2008 SWIM Technical Architecture Policy WS-Policy Assertions WS-Policy Attachment WS-Policy Framework Messaging SOAP WS- WS- WS- MTOM Attachments Addressing Notification Transport HTTP JMS MQ SWIM Segment 1 Standards System Wide Information Management (SWIM) October 22, 2008 10 SWIM
System Wide Information Management (SWIM) October 22, 2008 11 Service Container Contract . . Contract award to Iona Technologies on August 18, 2008 Contract options: - Software - Documentation - Support Licenses | Training l Consulting Services ● . . – - - Indefinite Delivery Indefinite Quantity Base year + 12 option years Iona was purchased by Progress Software on September 12, 2008 Fuse will remain and continue to evolve Artix will be combined with Progress SOA portfolio Artix already interoperates with the Progress Sonic ESB Product integration between Artix and Actional for run-time visibility and - governance is already underway as part of an existing partnership between IONA and Progress SWIM Available Products on Contract . Products Available: - FUSE Suite . FUSE ESB . FUSE Services Framework . FUSE HQ FUSE Mediation Router . . FUSE Message Broker Artix Data Services l - l - l Artix Registry/Repository Artix ESB C++ Artix Connect for WCF Artix Security l • . Artix Enterprise Management Service Plug-in Artix Orchestration (meets desirable requirement for BPEL) available at extra cost Fuse is not currently supported on AIX but will be by mid November 2008. SWIM
Interface Management
Interface Specification Interface Discovery Schema Management
Enterprise Service Management Service Monitoring Service Configuration System Monitoring
licy Manageme Authentication Authorization Audit Security lona Fuse Servic Framework Artix Security E Messaging Reliable Messaging Publish-Subscribe Message Routing
a
System Wide Information Management (SWIM) October 22, 2008 14 Artix Enteprise Management Service SWIM Prototype: Goals . Prior to Service Container Contract award to IONA Technologies, Two prototypes were developed to evaluate service containers – ITWS-SWIM Prototype  using a service container product provided by IONA Fuse –  CIWS-SWIM Prototype using a service container product provided by Mule CIWS-SWIM Prototype was completed and was not made available to users once the IONA Service Container Product was selected. . . ITWS-SWIM prototype was extended to be able to provide service to interested non-FAA consumers to evaluate web services and XML formats, and overall products’ usability –  Publishing four ITWS weather products •   Microbursts; Gust Fronts; Configured Alerts; Terminal Text . ITWS-SWIM Prototype became operational on October 6, 2008 and will operate until ITWS-SWIM Segment One capability is deployed in December 2010 SWIM
. . Initial end-to-end testing and stress testing successful, August 2008 Conducted successful tests with the FTI National Test Bed (FNTB) and the ED-8 Gateway . Three airlines selected as initial participants – JetBlue, UPS, NWA – UPS operational today . SCAP update effort successful to date – with late September Certification and Authorization target . FTI connectivity between Volpe and the WJHTC in place –  Backbone will support ITWS SWIM Prototype subscriber traffic . UPS connectivity to FTI ED-8 Gateway occurred the week of September 23 . Successfully explored “don’t code, configure” principles. Results to date with Iona Fuse have been very promising –  Produced a proof-of-concept configuration enabling WS-Security functions in ITWS SWIM Prototype System through configuration only (no coding required) SWIM Prototype: FY09 Plans . Agreement reached and documented with ITWS to maintain the Prototype through FY10 –  No enhancements after initial deployment are currently funded or planned Volpe will provide client software and a user guide to additional service consumers • . More service consumers may be added until the current allocated bandwidth limit for the prototype is reached
FY09 Work
.
Service Registry/Repository
l | • Initial RegistryRepository stood up at WJHTC Evaluation based on Requirements to be conducted this year XML Gateway l . Qualified Vendor List in process Policy Server l l . Requirements in Development Evaluation to be conducted early next year
SWIM Resource Kit
Assist the SIP developers in learning and utilizing the SWIM Core Services l Assist the SIP developers in debugging COTS and related third party l products Assist the SIP developers in obtaining and managing the resources l required for development. Assist the SIP developers in identifying the SWIM Service Container l components required to implement their Service. Assist the SIP developers in sharing knowledge. l Provide tools to assist the SIP developers with testing. l
.
Guidance Documentation
l Maven Guidance Developers Guide for Fuse ESB l Procedures for installing Eclipse, Fuse tools for Eclipse and Maven plug-in . Build procedures . Debugging procedures . • Examples
COTS Repository
|
●
Fuse ESB, Fuse Mediation Router, Fuse Message Broker, Fuse HQ, Fuse Service Framework, Spring, Eclipse, Maven, Ant
SWIM Reference Model
l l l Description of Service Container components and interfaces Maps Service Container components to Core Services Decision Tree for identifying which Service Container components and architecture are required to achieve particular operational needs •   i.e.,  guaranteed messaging Governance and Policy Guidance . Standards ●

• Tools
–  WS-I Testing Tools –  iTKO LISA – SOA Test Tool and Virtual Service Emulation (VSE) • XML Gateway Qualified Vendor List . SWIM Wiki . Third Party References and Training Information . Available on the SWIM Wiki as Resource Kit items are completed (NLT 1/1/09) •  Resource Kit is dynamic –  New items will be added as required SWIM Future Plans for Segment 2 . Determine operational requirements for information that must be met in FY12-16 (Segment 2) –  Input from JPDO, Roadmaps, Operational Improvements . Determine technical requirements needed to meet Segment 2 operational requirements Determine how the Segment 1 architecture must evolve to meet Segment 2 requirements –  Ex. Segment 1 federated approach vs. possible future centralized approach JRC for Segment 2 currently planned for June 2010 . • SWIM Web Site www.swim.gov System Wide Information Management (SWIM) October 22, 2008