Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim - - PowerPoint PPT Presentation

riding the it wave it acquisition technical challenges
SMART_READER_LITE
LIVE PREVIEW

Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim - - PowerPoint PPT Presentation

Headquarters U.S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim Rudolph CTO, Electronic Systems Center, Hanscom AFB, MA Agenda Agility to Get Capability


slide-1
SLIDE 1

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Headquarters U.S. Air Force

Riding the IT Wave: IT Acquisition Technical Challenges

Dr Tim Rudolph CTO, Electronic Systems Center, Hanscom AFB, MA

slide-2
SLIDE 2

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Agenda

 Agility to Get Capability  Critical Enablers  Common Infrastructure  Implementation Baseline  Integration Test Lifecycle Capability  Composable Capability Grand Challenge

2

slide-3
SLIDE 3

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

3

Consolidation of IT Infrastructure

Infrastructure

Mission Services & Threads Mission Services & Threads Mission Services & Threads

MISSION APPLICATIONS CORE SERVICES INFRASTRUCTURE

IT Infrastructure Acquisition Programs

Core Services

Classic Programs

From Stovepipes to Services

Number of Program efforts reduced Current Process with Stovepipe Programs Required activities separated for consolidation Application Acquisition Programs

3

slide-4
SLIDE 4

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Agility to Get Capability

Focus on Capability Delivery

 Cut down the time it takes to field capabilities  Use services to gain capability in modular, incremental approach

Separation between building Capability and building Infrastructure

 Capability built on known IT infrastructure reducing timelines  Move infrastructure to managed services and commodity IT

Use of Standards

 Develop a Standards-based approach for building the IT infrastructure

and then for building upon that IT infrastructure New Processes

 Services Development and Delivery Process (SDDP)  Governance structure to align programs  Testing of new capability in the environment it will run in

4

slide-5
SLIDE 5

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Acquisition Leadership Working to Provide Policy

 Ensure PMOs comply with web services standards and processes  Develop Acquisition Strategy to use the common IT Infrastructure

(network infrastructure, hosting environments, and middleware)

 Provide Capabilities built using lightweight services and

applications independent of infrastructure

 Monitor compliance with infrastructure “to be” standards as

specified in the Consolidated Enterprise IT Baseline (CEITB), aka “Target Baseline”

 Support Product Center definition of the Implementation Baseline  Provide necessary expertise (critical enablers) to PMOs in order

to use and manage the IT Infrastructure

5

slide-6
SLIDE 6

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Critical Enablers

Platform Services Management

 Key in defining architecture and infrastructure  Work agreements with AFSPC to partner with DISA and other

hosting providers and providing enterprise licenses Integration Test Lifecycle Capability (ITLC)

 Perform testing to ensure proper integration of new services  Maintain repository of capability web services documentation  Support Help Desk problem solving and service monitoring

Outreach

 Work closely with program offices and users to understand

compliance with standards & protocols and reduce development time for programs

Standards & Infrastructure are required

6

slide-7
SLIDE 7

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Common IT Environment

  • Focus on levels of commonality:

– Infrastructure as a Service, including network and physical infrastructure – Platform as a Service providing managed services platform – Info services, using PaaS – Redirector to the correct area – Consistent Web 2.0 presentation layer

  • Focus on classes of capability:

– Light Weight Exposure and other Info/Mission Services – ERP like COTS capability - combination of services and system(s) – More stand alone systems - preference on consistent network/IaaS)

  • Third dimension includes Terrestrial

(Ground & ground stations); Aerial; and Space

  • Challenge is defining baseline within
  • ne “cube” and growing out

PEOs build applications & services to fit

  • n

infrastructure provided

Light Weight Services ERP-like Hybrids “Stand Alone” Systems

IaaS

(Infrastructure)

Info Services

PaaS

(Platform)

7

Legacy Systems

slide-8
SLIDE 8

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Shifting to Development Process

8

Developing Capabilities Providing Infrastructure Time Baselines: Target Implementation Operational SDDP Steps: 1 2 3 4 5 6

Configuring Apps/ Writing Code Developing Mash-ups Testing & Integrating Fielding New Capability Determining COA Monitoring Performance Help Desk Support Provide Development And Test Environments Assess Infrastructure Requirements Put On Network

Acquisition Participation in New Collaborative Development Processes

Layers Presentation Apps Middleware OS Network

Running Capability Running Infrastructure

Requirements Development Services Development Fielding Testing Sustaining

slide-9
SLIDE 9

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Implementation Baseline

The Implementation Baseline explains how to apply the Web 2.0 Tenants:

 Client Neutral  Capabilities separate from

Infrastructure

 Bounded User Requirements  Web Enabled Services  Strong 2-way Authentication  Enterprise Sustainment of

infrastructure and core services

9

Applications Implementation Baseline Converged Middleware Servers (Hosting) AFNET ADS (Databases) Services Web 2.0 Infrastructure Capacity

slide-10
SLIDE 10

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Enterprise Baseline Relationships

10

IT Acquisition Policy (SAF/AQ)

ESC interprets CEIT baseline to develop program guidance SAF A6 CTO leads governance to change baselines based on enterprise needs Programs direct developers based on enterprise standards Architecture artifacts added to enterprise repository

Consolidated Enterprise IT (CEIT) Baseline (Target or “To Be” Baseline) Implementation Baseline Program RFPs (Standards and Requirements) Fielded Services, Applications, and Infrastructure Operation Baseline (“As Is” Baseline)

slide-11
SLIDE 11

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Integration Test Lifecycle Capability

The Integration Test Lifecycle Capability (ITLC) provides:

  • Test solutions in realistic “hot” environment
  • Aid in packaging and provisioning solutions for

fielding

  • Maintain repository of web services

documentation after fielding

  • Provide Help Desk Tier 2-3 support
  • Analysis/report on the performance of fielded

services for AFSPC (24th AF)

  • Advise on AF IT infrastructure and the Target

Baseline as a member of the CCB

Several organizations to provide the skills needed to support roles

11

slide-12
SLIDE 12

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

The Integration Test Lifecycle Capability (ITLC) in the SDDP

12

SDDP

Bounded User Requirement

Step 0 Step 2 Process Definition Step 3 COA Step 4 Development Step 1 Define Problem Step 5 Testing Step 6 Operationa l

Performs testing in the pre-production environment to ensure integration, security, and performance Involved in determining the provisioning needs for the new capability prior to development; changes to the infrastructure would be sent to AFSPC Provides level-2 and 3 helpdesk support to problem solve when services fail Participate in the “kickoff” meeting to determine schedule of tasks needed for fielding Monitors use and performance of services, then provides recommendations for changes to the infrastructure and deprecation of services

slide-13
SLIDE 13

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

End-to-End Test

 Applications only tested in

contractor development lab

 Disconnected from Air

Force IT environment

 Real testing starts after

system goes on operational network

 Lots of effort required after

fielding to meet acceptable user performance requirements

 Provide snap shot of test tools for

external use (e.g. TestForge.mil)

 Applications tested in a

government provided, representative environment

 Test environment aligned to the

  • perational environment to stage

capabilities

 Complete user experience tested;

end-to-end prior to release

13

A “Test Range” for IT systems to include collaborated responsibilities, facilities, personnel, and processes

slide-14
SLIDE 14

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Mission Capabilities

App AA App AB

AOC-WS JMS DCGS

App JB App DB

24AF Ops

An Example of the Future State:

Common IT Infrastructure + Multiple Capabilities

 Centralized design and provisioning of a common IT Infrastructure,  Increased C&A inheritance  Increased enterprise licensing & commodity procurement

14

Mission Service

WEB 2.0 – Presentation Layer

Mission Service

Implementation Baseline App JA

AFNET, including AFDS, etc.

Infrastructure

Enterprise Core Services

Platform

Common IT Environment

Other Common Platform Service, e.g., Monitoring, Enterprise Licensing Legacy Apps I/F I/F Mission Service

App DA

Common Mission Services

App AC

Mission Services

slide-15
SLIDE 15

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Summary

 Agility needed in providing Capability to the Warfighter  Separate building Capability from building Infrastructure  Use Baselines to define the IT Infrastructure and how to build

  • n this infrastructure

 Use new processes such as SDDP to develop services  End-to-End testing in realistic environments ensures

compliance and functionality before fielding

 Acquisition Community (AQ) needs to complete these tasks to

enable agility

 Change policy to match new processes  Resource critical enablers to support new processes  Use governance structure to oversee processes

15

slide-16
SLIDE 16

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Composable Capability Grand Challenge

(briefed by LtGen Bowlds, New Horizons, 26 Jan 2011)

USER COMPOSTION ENVIRONMENT COMPOSITION ENABLERS DYNAMIC RESOURCE PROVISIONING

Applications that Help Users Dynamically Plan, Manage and Allocate Resources, e.g. Applications, Computers, Networks Applications that Allow End Users to Configure, Create and Display Information Technologies that Enable Rapid Discovery, Creation, Assembly, Dissemination of Trustworthy Data and Services

 Grand Challenge

 Broadly engage Industry and Gov’t  Prototype and Demo with OSD Chief

Architect and Joint Staff J8

 Address future Business model

issues

 FFRDC-developed Reference

Implementation will be made available as optional starting point

Driven by Operational Need – Enabled by Technology Advances

■ A new paradigm for the design, acquisition and employment of IT-based Command and Control

  • Rapidly plan, configure and dynamically

adapt C2 functionality to meet evolving mission needs

  • Develop and field components as well as

a method to employ them

16