1 / 6

Presented by: Mike Hritz To: ICNS Date: May 11, 2010

NextGen Integration: SWIM Lessons Learned. Presented by: Mike Hritz To: ICNS Date: May 11, 2010. SWIM/SOA Evolution. Where We Were GCNSS Segment 1 JRC: “Build it They Will Come” FAA/EUROCONTROL R&D Committee Where We Are SWIM Segment 1: SIPs/PLAs SWIM Prototypes

elgin
Download Presentation

Presented by: Mike Hritz To: ICNS Date: May 11, 2010

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. NextGen Integration: SWIM Lessons Learned Presented by: Mike Hritz To: ICNS Date: May 11, 2010

  2. SWIM/SOA Evolution • Where We Were • GCNSS • Segment 1 JRC: “Build it They Will Come” • FAA/EUROCONTROL R&D Committee • Where We Are • SWIM Segment 1: SIPs/PLAs • SWIM Prototypes • FAA SESAR Joint Undertaking Collaboration • Where We Need to Go • Technology Drivers • SOA Challenges

  3. 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

  4. Where We Need to Go • SOA Challenges • Security • Governance • Change Management • Process Management • Project Management

  5. Where We Need to Go • Communication/Coordination: Program Level Agreements/Service Level Agreements • Governance Maturity • Enterprise Security Solution • Infrastructure Focus to Information Management Focus • Balancing SOA Ideals and Objectives with practical needs based implementation • SOA Guidance focused on Classic Business Operations vice Command and Control Operations

  6. Questions?

More Related