“25 Days to Field Functionality” Case study of GCSS-AF

© 2010 The MITRE Corporation. All rights reserved.

Harvey Reed (MITRE), Michael Clark (CIV)Thu 16 Sep 2010

“25 Days to Field Functionality” Case study of GCSS-AF

Agile & Affordable


■ Agility– BLUF– Definition– Relevance

■ Agility related to SOA and Key Processes– Coordinate multiple parties with multiple tasks integrated into a single

SOA environment■ Agility Case Study: GCSS-AF (Combat Support)

– Ave 25 days to field new mission capability– IOC 2004, mature, constant additions/refresh to stay up to date– Serves all Air Force Airmen (~900K) via AF Portal– Serves bulk of combat support systems and services via security,

messaging, storage, etc. (>250 systems secured, >150 apps/services, >150 ESB topics)

– Ave ~400 releases per year– Approx ~$400M per year savings – Studied extensively by OSD/CAPE, DON, IRS, NGA, CMS, and others.

Outline


GCSS-AF Evolution

1996 Created from BLSM, 10 year ID/IQ contract to Lockheed2001 Designated as a RIT program2002 Launched first COTS Portal2004 Launched AF Portal with Akamai2005 Reorganized program, contractor and processes around services

Incorporated AF EDW (Enterprise Data Warehouse) as Data ServicesReleased first ESB in the Air ForceDeemed a RIT success, moved back to classic acquisition

2006 Re-launched AF Portal with updated architecture and AJAX for UIData Services rolls out self-service request for data accessReceived 2 year J & A extension to contractWorked with DISA to in-source Akamai to NIPR & SIPR as GCDS

2007 Data Services rolls out RIA based analyticsRolled out Web Service proxy securityBegan work on attribute-based access control (ABAC)Data Services rolls out web service data access

2008 Re-deployed AF Portal using open source for scalabilityJoined the DoD/IC AATT team (ABAC and Identity Management)Began virtualizing core infrastructure servicesCOOP site approved and fundedBegan federation with DISA DKO DoD Portal, due April 2009

2009 CAC Restricted AF portalInitial COOP rolloutDEAMS Spiral 1 into productionAchieved FDDRFielded Next Generation Portal 2.0

2010 Deployed Enterprise 2.0Supported DEAMS go liveImplemented Positive Inventory Control (PIC)Declared FOC

Services Offered:• Security

• PKI-based authentication• RBAC• ABAC (in progress w/AATT)

• Akamai • transitioned to GCDS

• Hosting• J2EE• .NET

• Storage• NAS, SAN, Edge

• Portal• User Interface to GCSS-AF and Enterprise

Services• Enterprise Web Content Management

System• Enterprise Discovery Service (Search)• Enterprise Collaboration Service

• Messaging• ESB• WS Proxy

• Discovery• People, Services, Content, Metadata

• Analytics• Collaboration

• IM

Services Used:• Collaboration

• DCO• OCSP Responder, GCDS, DMDC, AFDS


BIGGER FASTER CHEAPER

Increased capabilities

Shorter delivery cycles

Less O&M

TEAM TASKS INTEGRATION

Total team of Gov’t, FFRDC, Ctr

Small IDIQ tasks, rapid replanning

Gov’t owns integration, assisted

by FFRDC

■ What is success in GCSS-AF?

■ How did it happen in GCSS-AF?

■ How to increase adoption beyond GCSS-AF?

Agility Bottom Line

POWERTECTURE BUDGET FEEDBACK

Relationships, dependencies, money rewired

Budget for annual plan, individually fund tasks during

execution year

Rapid transparent response and escalation to a

constantly changing environment


The Point

Stovepipe

Thread/Data

MissionInformation

MissionThreadMission

Functionality

Core Middleware

Computing

Network

Acq

uisi

tion

Bou

ndar

y

Presentation

Workflow

MM

Acq

uisi

tion

Bou

ndar

yA

cqui

sitio

nB

ound

ary

CC

CCA

cqui

sitio

nB

ound

ary

Security

StandaloneProgram Modular

StandaloneProgram

DELIVER

DELIVER

ISP/ASP

Core Infrastructure

Service Program

Acq

uisi

tion

Bou

ndar

y

CC

CCA

cqui

sitio

nB

ound

ary

DELIVER

Workflow

MM

Acq

uisi

tion

Bou

ndar

y

Workflow

MM

Acq

uisi

tion

Bou

ndar

y

Mission Service Program


HOST


ADAPTIVEAGILITY(SOA)

EXECUTION AGILITY

(INFO SHARING)

Coal

ition

Join

tCo

mpo

nent

Loca

l

StandaloneClassic

Service HostingISP/ASP

StandaloneWeb Augmented

StandaloneModular

DeliveryTimeLong Long Medium Short

■ Execution Agility – How wide is info

shared (joint, coalition, etc.)?

– How fast is network, software and hardware performance?

■ Adaptive Agility – How fast can we

adapt using SOA?

– How fast can we further connect, federate, share information?

Agility Quad Chart

BeforeGCSS-AF

GCSS-AF


7

GCSS-AFStakeholders Air Force

AFMC

ESC

554 ELSW

GCSS-AFFunctional SPO

Functional SPO

AFSPC

AFNIC

Functionals Deployed Ops/Support

Base

Base

GCSS-AF is both an acquisition program and a data center management program

Whole AF is the GCSS-AF customer. Deployed troops are most dependent on GCSS-AF via AF Portal and associated capabilities

4-star

3-star

1-star

4-star2-star Up to 4-star

GCSS-AF partners with Functional SPOs who provide functional code

GCSS-AF gets high level requirements and funding from corporate

Collaborate

Reqt

s an

dFu

ndin

g

Reqts andFunding

Use and

Feedback

ManageDoD Datacenter, Network Services

Network

&

Compu

ters Netw

ork &

Compu

tersDISA

GCSS-AFSecurity + Infrastructure

MissionFunctionalityMission

FunctionalityMissionFunctionalityMission

Functionality155

1

3


GCSS-AFProgram


■ “SOA is not a Thing”:– You can’t purchase it– You must practice it

■ Adaptive Agility / SOA is:– Multi-party– Many concurrent small tasks– A lot of coordination and

alignment– Gov’t needs to be the integrator

■ SOA requires trust– Build trust first– SLAs can describe the trust

relation– Enforcement by SLA does not

work■ Questions to Ask:

– Who is the SOA community?– How is trust built and maintained?– What about feedback?– What about escalation?

Agility related to SOA and Key Processes


Outreach (cont)

OutreachWork Plan / Road Map

Requirements

GCSS-AF Ops and Support

GCSS-AF Outreach

IMS

Testing Production

Sustainment

PPRR

Installation

PRR IOC

Artifact Package

to CM QTE2

ArtifactPackageReview

ReleaseDevelopment of New Capabilities RSO, Applications, Links, Gadgets

Application SPO & Domain

Testing

For Applications Test

ApplicationOwner

O&S Initial Coordination Meeting

RTO

Verification

Major - 90 day

Advertise

Engage Early!

PFM and RMB Approval Air Staff and AFNIC

Engage Here

Outreach (cont)

Process Steps 1 - 3

Process Step 4

Process Steps 6 - 7

Process Step 7

Process Step 8

Process Step 9

Process Step 10

Process Step 11

GCSS-AF Application Lifecycle


GCSS-AF Application Lifecycle

PPRR - Engineering Review 1 0PPRR - Security Review 2 1PPRR - Test Manager Review 2 1Preproduction Readiness Review 0 0Pre-Prod Installation 5 2PRR - Security Review 5 2PRR - RTO Testing 5 2

Production Readiness Review 0 0Production Installation 5 2Post Production Security Review 4 4Total 25 10

The standard process has levels of prioritization for releases that need to be expedited quicker than 25 days.

25 Days to field new mission functionality


FY10 O&S Accomplishments

Jan-2010 Feb-2010 Mar-2010 Apr-2010 May-2010 Jun-2010Service Users 25 34 38 106 52 50

Infrastructure 11 14 15 16 12 12

Portal 0 1 4 1 1 1

RSO 0 0 1 0 0 0

O&S 34 14 13 17 35 41

ESB 1 1 1 2 35 7

– Pace of Production Releases accelerating

– Driven by Service User and O&S work plans


453 Capability releases in FY

2008 – this is a reflection of response to

change■ 453 Capability Releases deployed to Production in 2008

■ Where GCSS-AF has been - 4 year history

Service User IF AFP RSO O&S ESB

228 85 15 21 66 38

GCSS-AF OperationsProduction Service Release Rate


FY10 O&S Accomplishments

0

20

40

60

80

100

120

140

160

180

Tick

ets

GCSS Level 2 Help Desk: Tickets Opened/Closed Per Week

GSOC_Level2_Opened GSOC_Level2_Closed Linear (GSOC_Level2_Opened)

Account Mgt14%

Content/www7 11%

Form4126%

ISQL2%

Mission App 37%

OID Sync5%

RSO5%

Ticket Types

DEAMS50%

ETIMS8%

REMIS8%

AFFMS8%

TOV-ENCLAVE6%

PRPS5%

PAMS3%

EESOH3%

CAS3%

TBA3%

EODIMS1%

AFRIMS2%

Mission Apps

Aggressively managing help desk tickets—120-160 weekly Mission apps support growing esp for DEAMS Extensive metrics management process


Flexibility and responsiveness to tradeoffs leads to rapid and

wide adoptionGCSS-AF

Shared Infrastructure Business Case

14

$1.00

$0.80

$0.60

$0.40

$0 .20

9M

8M

7M

6M

5M

4M

3M

2M

1M

$1.02

$0.024

$0.58148

100

198

247

RSO Applications

202

$0.03

$0.08

Cost per page view

910K registered customers

470K

625K

800K

100K$0.14

42

77

244

143

$0.10$0.16

FY02 FY03 FY04 FY05 FY06 FY07 FY08 FY098.9M pages of data per day

822K

250K

Fully Hosted Applications

Reduced Sign-on Applications

$ Cost per Page View

Registered Customers

67

Pages of Data per Day

1,200K

2,000K

2,500K

4,100K

7,800K

1PageViews

Since IOC in 2004: Applications Up 210% Customer base Up 190% Daily use Up 750% Cost per page view Down 88%

250K

100K23

825K

155

244

RSO Applications

Fully HostedApplications

Cost per page view


GCSS-AFSOA Infrastructure Sustainment Costs (2008)


Dec-04 Dec-04 Aug-08 Aug-08

Parameter Avg Cost Savings per Unit (BY07, $) Number Migrated Total Annual Savings

(BY07, $) Number Migrated Total Annual Savings (BY07, $)

Applications $1,407,000 26 $36,582,000 143 $201,201,000

RSOs $789,000 225 $177,525,000 247 $194,883,000

Security $185,000 251 $46,435,000 390 $72,150,000

Web Content $9,812,000 $9,812,000

$270,354,000 $478,046,000

The ‘AFCAIG Business Case Validation and Assessment’ concluded that GCSS-AF provides the Air Force with SIGNIFICANT savings.

AFCAIG Finding: GCSS-AF Business Case is Valid and SIGNIFICANT!

Shared infrastructure leads to huge

ROI

GCSS-AF ExploitationAFCAIG –Business Case Validation

“25 Days to Field Functionality” Case study of GCSS-AF

Documents

Transcript of “25 Days to Field Functionality” Case study of GCSS-AF