11

Service Oriented Architecture (SOA) - Where is the

Federal Government Now?

John J. SheaDir, Information Policy & IntegrationOffice of the DoD CIOjohn.shea@osd.mil28 April 2009

22

Maritime Domain Awareness (MDA)−Real example of the challenges we face

Scaling SOA to the Enterprise

33

SMS/JPSC2

Google Earth

MASTER

CAS

Seaport

AISData

Tripwire

E-MIO

FASTC2AP

CMA

LINXTAANDEM

Current SECNAV MDA Spiral 1 Architecture

Systems to systems approach with point to point data transferacross multiple security domains

44

Federated Core Enterprise Services providing authorized consumers the ability to discover, access and understand

shared data, products and services

Publish

Subscribe

SMS/JPSC2

Google Earth

MASTERCAS

Seaport AISData

Tripwire

E-MIO

FASTC2AP

CMA

LINXTAANDEM

SMS/JPSC2

Google Earth

MASTERCAS

Seaport AISData

Tripwire

E-MIO

FASTC2AP

CMA

LINXTAANDEM

Transition to net-centric, services-based information sharing architecture…..

Future MDA Architecture….

55

…and it needs to scale to support national MDA requirements

Federated Core Enterprise Services providing authorized consumers the ability to discover, access and understand

shared data, products and services

Publish

Subscribe

VesselData

PeopleData

InfrastructureData

Cargo Data

DHS Systems& Services

DOT System& Services

DOD Systems& Services

DNI System& Services

DOJ System& Services

International Systems

& Services

Lots of Sources, Lots of Consumers….

66

MASS SD

MSSIS

GMMS

USCG NAIS

SCC-JSMS

DRDCHalifax GHMD

MASS C5F MASS C2F MASS C3F MASS CPF

SAGE @ NORTHCOMMIDAS

DOJ’s SeaHawk Charleston, SC

GCCS-I3

NAVAIR

Panda C4I Suite

DISA’sNet-CentricEnterprise Services

Security Service Discovery Messaging (Pub/Sub) Content Discovery

Enterprise Service ManagementMediationIdentity Management

USCG NAIS ONI AMRS SILO ANOA

DHS iCAV

Publishing data in acommunity defined schema

via NCES

Subscribing to data via NCES

MASTERRMACCMA

Current “MDA DS COI” Architecture

Begins to address DOD’s needs, but not a national MDA solution

In Progress

AIS Data

Vessel of Interest Data

People Data

Value-Added ServicesHosted at a DECC

GMMS

DAS HAS

ADS

DECC

(Exploited AIS data--Only part of the Vessel Data picture)

77

NCES

PeopleData

Infrst.Data

CargoData

VesselData

PeopleSystems

Infrst.Systems

CargoSystems

VesselSystems

InternationalES

PeopleData

Infrst.Data

CargoData

VesselData

PeopleSystems

Infrst.Systems

CargoSystems

VesselSystems

ICES

PeopleData

Infrst.Data

CargoData

VesselData

PeopleSystems

Infrst.Systems

CargoSystems

VesselSystems

DHSES

PeopleData

Infrst.Data

CargoData

VesselData

PeopleSystems

Infrst.Systems

CargoSystems

VesselSystems

FederalES

PeopleData

Infrst.Data

CargoData

VesselData

PeopleSystems

Infrst.Systems

CargoSystems

VesselSystems

National MDA Architecture needs to support all types of data across the U.S Government as well as our partners (foreign and commercial industry)

NCES by itself will not scale to meet the national MDA requirements.Other enterprises (ES) must be involved as well. What will “bind” them?

88

NCES

PeopleData

Infrst.Data

CargoData

VesselData

International CES

PeopleData

Infrst.Data

CargoData

VesselData

ICES

PeopleData

Infrst.Data

CargoData

VesselData

DHSES

PeopleData

Infrst.Data

CargoData

VesselData

FederalES

PeopleData

Infrst.Data

CargoData

VesselData

National MDA Architecture needs to be based upon common standards, specifications, services to

ensure interoperability across multiple enterprises.

Common standards, specifications, services are neededbut they have to be adopted, implemented to federate the enterprise

Global MDA Data Consumers

DOTES

DOJES

State &Local ES

IndustryES

Common, Industry-Based Standards, Specifications, Services

99

NCES

PeopleData

Infrst.Data

CargoData

VesselData

International CES

PeopleData

Infrst.Data

CargoData

VesselData

ICES

PeopleData

Infrst.Data

CargoData

VesselData

DHSCES

PeopleData

Infrst.Data

CargoData

VesselData

FederalCES

PeopleData

Infrst.Data

CargoData

VesselData

National MDA Architecture needs to be based upon common standards, specifications, services to

ensure interoperability across multiple enterprises

Global MDA Data Consumers

DOTCES

DOJCES

State &Local CES

IndustryCES

Common, Industry-Based Standards and Specifications

Multiply this example of one domain with a few agencies to the broader challenge of creating a federal enterprise!

Things we learned we need:•Identity management•Access control privileges•Standard syntax and semantics for some content (e.g., UCore)•Strong governance

1010

How do we federate?

• What is the minimum set of controlling standards, specifications, services needed to “federate” across all the entities in the enterprise(s)?

• How do we choose common standards, specifications, and services?

• Who governs the federation? How?

• Who enforces compliance within the federation?

• Who provides the “top level” infrastructure?

But wait……..

1111

But wait……..

• Can we really expect the federal government to agree to and adopt a massively scale federation plan?

• IF we define/execute a COA to support federal federation how long will it take to implement?

• Will we still be having this conversation in five years? Ten years?

Is this even achievable???

1212

The Cloud Buzz……..

• Tipping point….

– Cloud Computing is real

• 2-10 Technology

– Rob Carter, EVP CIO FedEx

– Two years of Hyper-Buzz

– Ten years of adoption

The next big thing….

1313

The Cloud Buzz……..

• Obvious benefits… not so obvious implementation

• Fact: Cloud Computing has the attention of the new Administration

– Public – Secure– Federal, State, Local, Tribal - Law

Enforcement

Federal CIO moving fast….

1414

Our Strategy…

• Continue to evolve the Services Construct to achieve an “Information Advantage for our people and mission partners….” through the establishment of the Service-Oriented Enterprise

– Enterprise Guidance Board (EGB)

– Establishment of Key Services • Identity Management• Access Control • Access Management

Our Strategy…

1515

• Services Construct

– Update our Department of Defense Net-Centric Services Strategy memorandum to align with EGB activities

• Strategy for a Net-Centric, Service Oriented DoD Enterprise, March 2007

– Prepare a new Enterprise Services Implementation Guidance document

• Like we did with DODD 8320.2g for Data Strategy

1616

Our Strategy…

• Looking towards the future of Cloud Computing – near term:

– Keep pace with Federal plans

– DISA RACE project

– DISA Forge.MIL

– Establish DoD CIO outreach

• Industry, FFRDCs, etc

1717

Our Strategy…

• Establish DoD CIO Cloud Computing Pilots

– DoD CIO “Storefront”• Lightweight User Composeable Framework

• Enterprise / Community Portlets – App Store

– Enterprise: SSO, Search, Publish, etc– Community: User submitted / Forge.MIL

– Publishing into the Cloud will reshape our understanding of Content Management

1818

Our Strategy…

• IaaS / PaaS / SaaS - Commodities

• Focus on transition – How to move Apps into the Cloud?

– What are the pre-cursors / requirements?

– Invest in highly reusable tools to migrate current legacy Apps into the DoD Cloud

• Minimize the risk of transition

• Easy for PoR to transition

1919

We need your help…

• We need to rethink HOW we are going to achieve the Information Advantage

• We don’t have the answers…

We need your help!!!

2020

Thank you for your time and attention