IOOS Conceptual Design Summary

1
IOOS Conceptual DesignSummary Status

Kurt Schnebele IOOS Regional Coordination
Workshop Chicago November 2006
2
Conceptual Design Background

• Two delivery orders awarded under GSA Schedule
• Raytheon Intelligence Information Systems
• Lockheed-Martin Transportation Security
  Solutions
• Identical 6-month periods (March-August 2006)
• Companies worked independently
• Deliverables
• Received September 1, 2006
• Conceptual Design, Cost Estimate, Viability
  Narrative

3
Current Status

• Do NOT endorse either Conceptual Design
• This was not a down-select from two to one
• Full text of both deliverables are available at
  http//www.ocean.us/IOOS_Arch_Proposals
• Next steps are being considered by Ocean.US
  and IWGOO agencies
• Many assumptions were made in both designs with
  impacts on architecture and cost estimates
• Analysis of assumptions and validation of
  requirements essential to proceeding

4
Similarities - Highlights

• IOOS is technically viable concept
• Use service-oriented-architecture
• Allows incremental build-out
• Readily extensible for new requirements
• Takes advantage of web-services technologies
• Things to do first
• Establish program management governance
• Implement enterprise system management common
  services infrastructure
• Initial Operating Condition
• 3 to 5 years (Lockheed Raytheon, respectively)

5
Design Comparison
6
Conceptual Design Cost Estimates

• Two independent estimates
• Based on 20-year system life
• 7-12 Billion total
• 350-580 Million annual avg.
• Integration piece (DMAC)
• 3-5 Billion of total
• Includes Fed and Non-Fed
• Analysis continuing
• Validate Design Cost Assumptions

Range of Annual Estimates
7
Next Steps
8
Overview
9
Motivation for SOA Approach

• Large-scale, Internet-scale provisioning,
  crossing ownership boundaries
• Encapsulation and adaptability for the
  integration and reuse of existing assets
• Loosely-coupled features that allow for
  independent development and operations across
  stakeholder communities
• Resource sharing across IOOS
• Extensibility, scalability, upgradeability and
  sustainability for expansion and technology
  evolution.

10
Services Operations
11
Framework
12
Services Architecture
13
Concluding Recommendations

• Appoint a Federal Agency to lead IOOS and to take
  on full responsibility and accountability for
  IOOS
• Establish a IOOS Program office that must
• Assume responsibility for operational and
  technical Governance
• Assume responsibility for operations of IOOS
  Infrastructure
• Coordinate Research on-ramp
• Coordinate Education/Outreach
• Coordinate IOOS Funding through OMB
• Must foster active academic and research
  participation
• Must foster active private sector participation
• Initiate IOOS System Design Phase at the earliest

14
Overview
15
Physical Communications Interfaces
16
Horizontal Integration
17
SOA Layers
18
Asset Integration Summary
LCCE very sensitive to this distribution
19
Concluding Recommendations

• Establish a Viable Business Case for IOOS
• Establish a Viable Governance Structure
• Issue a GEOSS Government-Wide Acquisition
  Contract (GWAC)
• Develop the IOOS System Segment Specification
  and Preliminary Design
• Develop Essential Common Services, RINs and HI
  Components Required to Achieve IOC
• Develop Simple Horizontal Integration Services
• Develop Operational Modeling Framework