System Wide Information Management

1
System Wide Information Management

• Segment 2 JRC Progress

Presented to Demonstrations and Prototypes TIM
5 Presented by Deborah YoungDate May 26, 2010
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

3
Overview

• Four architecture alternatives
• Reference Case (Federation with Self Governance )
• Federated Architecture (Federation with
  Enterprise Governance)
• Enterprise Messaging Backbone Architecture
  (Shared Messaging Infrastructure and Security
  Management )
• SWIM Core Architecture (Enterprise Level SOA
  Infrastructure)

4
Reference Case

• Complete Segment 1 based on approved JRC
• No enterprise coordination, standards, or
  governance
• No enterprise oversight to test and monitor the
  critical performance of interconnections
• Segment 2 SIPs
• Future interfaces are ad hoc, negotiated between
  individual programs
• Each SOA-suitable program is solely responsible
  for implementing and provisioning their own SOA
  compliant services

5
Reference Case
NAS System D, E,
For N systems there are potentially N2 unique
interfaces
6
Alternative 1 Federated Architecture

• Develop additional NAS services and capabilities
  using the same technical approach as SWIM Segment
  1
• SWIM
• Continues to provide governance, registry,
  technical standards and guidance
• Segment 2 SIPs
• SOA-suitable programs will implement SWIM Core
  Services using SWIM-approved software, guidance,
  and standards, on separate NAS System platforms
• SIPs services must be registered in the Registry
• Service creation and provisioning is
  responsibility of individual SIPs
• Each SIP must provide and maintain its own SWIM
  infrastructure, including software/hardware for
  messaging, security and supporting services

7
Alternative 1 - Federated Architecture
NAS Information Layer (logical)
N2 standardized interfaces
8
Alternative 2 - Enterprise Messaging Backbone

• SWIM
• Continues to provide governance, registry,
  technical standards and guidance
• Deploys and operates a messaging backbone in the
  NAS
• Deploys and operates Identity and Key management
  security services
• Segment 2 SIPs
• Use the SWIM-provided messaging backbone to
  interconnect with other SIPs
• SOA-suitable programs will implement remaining
  SWIM Core Services using SWIM-approved software,
  guidance, and standards, on separate NAS System
  platforms

9
Alternative 2 Enterprise Messaging Backbone
SWIM Core backbone replaces interconnected
message brokers provided by individual programs
N interfaces to messaging backbone, N2
information interfaces
10
Alternative 3 SWIM Core

• SWIM
• Responsible for providing enterprise SOA
  infrastructure, including core and supporting
  services, such as
• Governance and Registry/Repository
• Interface and Enterprise Service Management
• Messaging and Security
• Service Composition and Orchestration
• Message Mediation
• Support Services
• Segment 2 SIPs
• Responsible only for exposing their services via
  SWIM compliant interfaces

11
Alternative 3 - SWIM Core
SWIM Core ESB provides a platform to host new NAS
common info services
Consolidated management of common NAS information
One Stop Shopping for information consumers
N information interfaces
12
Segment 2 Plans - Acquisition

• Conduct trade studies/ prototype SOA products
• Determine content of Approved Product List for
  use by other NAS programs
• Determine acquisition strategy that will enable
  other NAS programs to purchase SOA products
  needed for SWIM compliance and implementation in
  their systems
• Prepare for possibility of SWIM infrastructure
  contract
• Develop solicitation package to target 2012 award

13
JRC Status

• Dual JRC Final Investment Decisions 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