DoD ESI COTS Systems Integration Services (CSIS)

Overview Briefing

June 22, 2009

2

Agenda

Acquisition Overview

DoD System Integration (SI) Needs

SI Capabilities Sought

3

Acquisition Overview

4

ESI Timeline

4

5

Mission

5

6

Since 2002, ESI extended to agreements for IT hardware and IT services:

Agreements were in place from 2004 -2009 for systems integration services for COTS (expired in May).

Currently we are in the process of securing our next generation of agreements for COTS systems integration services and expect them to be awarded by the end of the calendar year.

The scope of the new agreements will be broadened to include: COTS involving or using SOA Cost based pricing Any COTS product (not just ERP) Entire life-cycle of services (see BSF) Firms with expertise in selected niche areas of expertise

Anticipated spending over the five year period is $7.5 B to $10B

Our approach is aligned with the DoD BTA, next-generation of the EI Toolkit, and efforts of the JITT (cost estimating).

Background on Systems Integration Agreements

7

TO ADVANCE THE FOLLOWING DoD GOALS

Enable information sharing; Make data visible, accessible

understandable, and trusted. Reuse DoD technology assets before

investing in new programs. Build technology on accepted standards

for architectural consistency Conform to SOA Foundation being

developed at DISA Reduce cost of technology Improve agility Reduce DoD’s reliance on third parties

PURPOSE IS TO:

Streamline the acquisition and implementation process

Provide access to the best qualified vendors

Add value to programs by providing education and tools

Develop a vehicle that forces discipline, rigor and best practices behavior.

Focus on greatest expected demand for technology-related services in the DoD for the next five to ten years

Provide a contract vehicle for a scope of services that is not covered adequately by any existing contract vehicles available to DoD programs

ESI Systems Integration Agreements Overview

8

1. GOVERNANCE / ENTERPRISE ARCHITECTURE

2. DEFINITION 3. INVESTMENT 4. EXECUTION 5. OPERATIONS & SUSTAINMENT

2.1 Strategic Problem / Opportunity

3.1 Analysis of Alternatives

4.1 Preparation 5.1 Post-Deployment Testing

2.2 Capability Definition (process, metrics and views)

3.2 Business Case 4.2 Blueprint 5.2 Sustainment

3.3 Acquisition Strategy 4.3 Detailed Design 5.3 Upgrades

3.4 Risk Assessment 4.4 Build 5.4 Enhancements

2.3 Project Charter 3.5 Information Assurance Strategy

4.5 Test / QA 5.5 Support

3.6 Net-Centric Data Strategy

4.6 Transition / Deploy  

6. PROJECT MANAGEMENT  

7. CHANGE MANAGEMENT 

Scope of Services and Segmented Vendor Pool

Full Life-Cycle

xxxx

x

x

x

9

Acquisition Approach/ESI COTS Systems Integration Competition Roadmap

• Vendor rankings

• Implementation methods and usage

• Commercial best practices (users)

• Software firm views

RFIIndustry Views

Competition Plan

• Best practices – general

• Analysts views and research

• SOA vs. traditional

• One competition

• Flexible pricing

• ESG / BTA

• Purpose & objectives

• Sponsorship

• Lessons learned from 1st term

• Scope

• Type of service

• Demand (FY09 +5)

• Existing vehicles

• Buyer scope

• Resources

• JITT

• BTA

• ESG

Market Research

• Statement of Work

• Acquisition Plan

• Baseline Service Framework

• JITT cost element structure / WBS

• S, M, L scope table

• RICE Dictionary

Gain Approval

Develop / Integrate

• ESI Working Group

• DoD CIO

• NAV-ICP

• NAV-SUP

Pre-Solicitation

Solicitation

Plan

Aug / Sep 2007

Sep 07 Aug 08

Draft Approve & Issue

Evaluate Submissions

Award

July 09 Dec. 09

Nov 08 Jun 09

Phase

Scope / Deliverable

Timeline

• Discussions

• Peer Review

Program Management & Education

Evaluation

• RFP

•Source Selection Plan

•Selection Panel Identified

•Peer Review

• Briefing Package

• Vendor Pre-Qual Tool

• Price Estimating Tool

• Templates

• Tutorial

• Web site

Ongoing

Completed

Vendor Conference

10

Acquisition Approach

Price Evaluation• Price Request Table for RFP – Baseline Service Framework or

Vendor’s Methodology (whichever is more robust)

• Phase or Track: ________________

WBS Service Deliverable (s) Acceptance Criteria

Duration Government Duties

Price Basis

S M L

# Cost $ $ $

FFP $ $ $

11

Acquisition Approach

Selection Criteria– Price

• RICE Complexity Level Definitions (one table each for R, I, C and E)– Low– Medium– High

• RICE Services Included in Price– Develop and Document RICE Requirements– Develop and Document the Business Case for RICE Object(s)– Establish Design Standards– Develop Functional Specification; – Develop Technical Specifications

12

DoD System Integration Needs

13

Optimize Use of Core Mission Systems

14

Transform DoD Business Systems

15

SOA: DoD Data Strategy Vision

Pre-determined “point to point” connections within systems and applications on disparate networks

Producer “pushes” information to pre-defined consumers

TodayToday FutureFutureSystems and applications are web-

enabled to expose their information

Authorized known & unanticipated consumers “pull” or “subscribe to” what they need regardless of who produced the information

3

Information Not Easily SharedInformation Not Easily Shared Information Ubiquitous on DoD “Web”Information Ubiquitous on DoD “Web”

Source: Mr. Mike Krieger, OASD(NII)I/DoD CIO

16

Communities of Interest (COIs) Address an Information Sharing Increment

Determine capability needed

Develop information exchange vocabulary– Vocabulary = Agreements on terms and definitions common to the COI, including data

dictionaries (DoD 8320.02G)

– Syntax = data structure

– Semantics = data meaning

Implement the software services– Service = a mechanism to enable access to one or more capabilities, where the access is

provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. (DoD Net-Centric Services Strategy, May 2007)

CapabilityNeeded

CapabilityNeeded

ServiceNeededServiceNeeded

DataNeeded

DataNeeded

Vocabulary & Implementations

Vocabulary & ImplementationsDrives DrivesDrives

Info Sharing

Need

Info Sharing

NeedDrives

17

Find and Use Available Services

• Are services available that can be used?

• Are services available that can be modified to fit need?

• Can others use the service that will be created?

Joint, DoD, and Intelligence Community Services Strategy is to leverage available services across the

enterprise

18

COIs Enable DoD Transformation

Global InformationGrid (GIG)

Global InformationGrid (GIG)

TIME

ProgramProgram

ProgramProgram

ProgramProgram

ProgramProgram

COICOI

COICOICOICOI

Data & Services tightly coupledto applicationsSystem specific vocabulariesServices start to emergeN2 integration problem

Decouple data from applicationsService enable dataCreate standards-based vocabularies (community & core) to enable interoperability

Data and Services available on the GIGComposable servicesPrograms provide services or value-added services

ProgramProgram

ProgramProgram

Organization & processes tied to IT COIs cut across organizations usingexisting processes

Organization & processesindependent of IT

Deliver ServicesDeliver Systems

19

Agile Information Sharing

Old New

Point-to-Point Information Sharing

Username / password

Multiple and DoD specific data format standards

System specific data definitions

Data semantics embedded in code and databases

Data and services difficult to find

Each program responsible for implementing all its capabilities

Tightly coupled, platform dependent architectures

Producers GIG Consumers

Common user identity via DoD PKI

XML (International standard for data exchange)

Community agreed upon vocabularies

Data semantics well-defined, published, and shared

Data and services discoverable

Core Enterprise Services available to programs

Service Oriented Architectures

20

SI Capabilities Sought

21

System Integration Needs Plan and architect solutions

– Determine line of business, program requirements and enterprise requirements

– Evaluate solution alternatives (legacy systems, existing services, new services, new COTS solutions)

– Develop application architectures

Implement, expand and maintain legacy COTS Solutions (e.g., ERPs)– Configure COTS application modules

– Integrate proprietary COTS application modules

– Develop and customize RICE objects

Implement, expand and maintain COTS SOA infrastructure– Configure SOA infrastructure COTS products

– Configure COTS business applications implemented using SOA

Implement, expand and maintain SOA-based COTS business solutions– SOA enable legacy COTS applications and modules to expose legacy data and services via web services

– Orchestrate services for enterprise solutions

– Integrate COTS applications with NCES

Complete conversions and migrations– Migrate conventional COTS applications and/or modules to SOA releases

– Consolidate multiple platforms to rationalize applications

– Adapt proprietary interfaces to use open standards

– Migrate legacy applications to or interface with Software as a Service (SaaS) solutions

– Virtualize COTS application infrastructure

– etc.

22

SI Capabilities Sought: Methodologies

Conventional COTS solution systems integration (e.g., mainframe, client-server, ERP)

SOA COTS solutions and/or hybrid solutions

Attributes

– Provides enterprise perspective, when required

– Enables rapid, incremental deployments

– Supports flexible / agile solutions

Multiple methodologies may be necessary.

23

SI Capabilities Sought: Sample Skills & Experience Requirements analysis – full spectrum (line of business through enterprise)

Architecture planning

System design

DoD legacy ERP platforms

RICE

COTS SOA infrastructure products

Application rationalization / consolidation

Service enabling legacy systems

Service orchestration

NCES

Data modeling, standardization

Use of industry standards

Operations & sustainment

Program & project management

Change management

Governance: program to enterprise level