180 likes | 273 Views
System Wide Information Management. Program Overview. Presented to: 2010 Integrated Communications Navigation and Surveillance (ICNS) Conference Presented by: Ahmad Usmani, SWIM Program Manager Date: May 12, 2010. Agenda. SWIM Program Overview and Status Segment 2. Program Concept.
E N D
System Wide Information Management Program Overview Presented to: 2010 Integrated Communications Navigation and Surveillance (ICNS) Conference Presented by: Ahmad Usmani, SWIM Program ManagerDate: May 12, 2010
Agenda • SWIM Program Overview and Status • Segment 2
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
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
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
Current SWIM Capabilities Capabilities will be implemented as multiple services over the next five years
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 1 on 15 July 2009 Five-year baseline (FY11 – FY15) approved Dual approach plan for JRC Final Investment Decision for Segment 2 Segment 2A JRC planned for 4th quarter FY10, to request baseline funding for FY12 and a placeholder for FY13– FY16 Segment 2B JRC planned for FY12
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
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
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
Agenda • SWIM Program Overview and Status • Segment 2
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
SWIM Alternatives Alt. 2 Messaging Backbone and Security Management Ref. Case Complete Segment 1 based on approved JRC Alt. 1 Expand Federated Approach to Segment 2 Programs Alt. 3 SOA Core Adhoc coordination among individual programs. No enterprise governance, only self-governance SWIM compliant interfaces, messaging services, support services, interaction services, security mgmt, enterprise service mgmt (same as Seg. 1 but beyond 7 SIPs) SWIM compliant interfaces, interaction services, orchestration, mediation and enterprise service mgmt SWIM compliant interfaces Governance, registry/repository, interaction services, interface mgmt, messaging, security mgmt, enterprise services mgmt, orchestration, support services, mediation SIP Governance, registry/repository, interface mgmt, messaging, security mgmt SWIM Governance, registry/repository
SWIM Web Site www.swim.gov