Bringing SOA to Life: The DCGS-A Interface Specification Drive Anthony Bradley Booz Allen Hamilton, McLean, VA 20 May 2006

Bringing SOA to Life:The DCGS-A Interface Specification Drive

Anthony Bradley Booz Allen Hamilton, McLean, VA 20 May 2006

Page 219 MAY 2006 UNCLASSIFIED

DCGS-A is the future provider of Army Intelligence, Surveillance, and

Reconnaissance (ISR) capabilities …


… Consolidating numerous existing Programs of Records (PORs) into a

Single Net-Centric ISR Platform

Moving from 13 programs and

over 100 applications to

1 program consisting of modular and interoperable

services

Moving from 13 programs and

over 100 applications to

1 program consisting of modular and interoperable

services


Objective DCGS-A SOA Architecture (Conceptual)

DCGS-A ESB

DCGS-A ESB

DCGS-A ESB

GIG

DCGS-A Enterprise Management Services

DCGS-A Security Services

DCGS-A Transaction Processing Services

DCGS-A Process Management Services

DCGS-A MASINT Services

DCGS-A HUMINT Services

DCGS-A Terrain Services

DCGS-A IMINT Services

DCGS-A Weather Services

DCGS-A All Source Services

DCGS-A Counter Intelligence Services

DCGS-A Multimedia Control Services

FCS/SOSCOE Core Services

DCGS-A Sensor Gateway Services

DCGS-A User Management Services

DCGS-A Dialog Management Services

DCGS-A Help and Training Services

NCES Core ServicesDIB Core Services

DCGS-A Military Intelligence Core Services

DCGS-A Common Access Services

DCGS-A Request Processing Services

DCGS-A Output Rendering Services

DCGS-A Intelligence Analytics Services

DCGS-A Fusion Services

JC2 Mission Services

DCGS-A Reliable Messaging Services


SOA Architecture Goals

• Deliver SOA systems designs that industry can use to develop/migrate to functional services that will easily integrate into the DCGS-A whole

• Ensure that the SOA system designs trace to and are relevant to the DCGS-A mission requirements and priorities

• Drive towards an objective DCGS-A system characterized by:

– Mission agility: Rapidly react to changing mission needs by assembling the required services

– Support the new TPPU process– Platform independence: update technology more easily– Modular approach: accelerates systems development and

evolution


……System DesignDocs

SOA Architecture and Design Primary Deliverables

SOA Strategic PlanningSOA Strategic Planning

Business/

Operational

Analysis

Business/

Operational

AnalysisSOA Systems Logical

Design

SOA Systems Logical Design

SOA Systems Reference Implementation

SOA Systems Reference Implementation

SOA Systems Physical Design

SOA Systems Physical Design

SOA CapabilityTimeline

OperationalModels

OperationalUse Cases

System UseCases

Logical Architecture

Interface Specifications

Software Specifications

Physical Deployment

Patterns

Physical Constraints

Physical Architecture

Performance Specifications

Provisioning Characteristics

Proof of Concept

Design Validation

Prototype

Test and Evaluate

Demonstration

ESpace*

ESB

Components:ü Metadata Publishing Serviceü Metadata Discovery Serviceü Alert Subscription Serviceü Event Assessment Serviceü KML Transformation Service

Components:ü Espace Gateway Serviceü BPEL Workflow Engineü XML Transformation Serviceü Service Management

Components:ü Native Espace Data

Service

Components:ü Google Earth Client Appü DCGS Analyst Dashboardü DCGS Service Explorerü Alert Listener Serviceü Test Harnesses

Network

Components:ü Salute Report Data Service

Components:ü MIP Data Service

MIP*CHAMS

ISR Domain Services

Components:ü Weather Effect Serviceü ...

UDDI

Components:ü Service Discoveryü Service Registrationü Service Taxonomy Mgmt

Metadata Catalog (MDC)“MI Core” Services

Analyst / TesterWorkstation

MetadataCatalog

ServiceRegistry

(* Non - DCGS-A Services)

DCGS-A Services Network

En

terp

rise S

erv

ice B

usMetadata

DiscoveryService

MetadataDiscovery

Service

MetadataDiscovery

Service

SIGINTGatewayService



MetadataPublishing

Service

MetadataPublishing

Service

MetadataPublishing

Service

MetadataCatalog

AlertSubscription

Service

AlertSubscription

Service

AlertSubscription

Service

EventAssessment

Service

EventAssessment

Service

EventAssessment

Service

WeatherEffect

Service

WeatherEffect

Service

WeatherEffect

Service

IMETS(IWEDA)

E-SpaceServices

WeatherEffects

EWData

AlertCriteria

Alerts /EventsMetadataMetadata

Searches

I nfrastructureI nfrastructureServicesServices

ISR DataListenerService



Async“Callbacks”

Filters

WorkflowEngine

ServiceManagement

HUMINT Data

Service(s)

HUMINT Data

Service(s)

HUMINT Data

Service(s)

HDWS (CHAMS)

Map /Coverage

Google EarthRich Client

Spec ComplianceTest Capability

Handheld

NCES Service

Discovery

TransformationEngine

BC GatewayService

BC GatewayService

BC GatewayService

ForceTracking

Blue Force Tracking


Technical Interface

& Taxonomy

Future …

Weather

…

…

MASINT

HUMINT

SIGINT

IMINT

ORD

Components

…

…

Future …

Weather Function 1.1

…

HUMINT Function 3

HUMINT Function 2

HUMINT Function 1

…

Coarse Grain Functionality

…

…

Future …

HUMINT Function 2.3

HUMINT Function 2.2

HUMINT Function 2.1

…

Fine Grain

Functionality

…

WSDL weather

…

…

…

WSDL…

WSDL …

…

…

Future…

WSDL …

WSDL ...

...

Interface

Specification

Detailed Functionality

High Level Functionality

FunctionalCategories

CGS

DTSS

GCS

IMETS

Prophet

CHIMS

Future…

ASAS-L

POR Data Models

Narrow functionality can directly be transitioned to an Interface Specification

PORs will implement one or more WSDLs; multiple PORs can implement a single WSDL.

Upon Interface Specification completion, the PORs implement the WSDL Interface Specifications

Multiple Sub-Functions may be aggregated into a single WSDL

This step-by-step iterative approach is essential to success

Interface Specification Development Process


Common Services (DIB / NCES / SosCOE)

SecurityServices

DiscoveryServices

WorkflowServices

System &Support

Services

StorageServices

MetadataCatalog

Logical Architecture – Near Term(Spiral 4.x)

AS-IS PORs(Service Providers)

LeveragedWeb Service Interface Specs

DC

GS

Po

rtal /V

isualizatio

n S

ervices

Joint

Other

C2

FCS

Native APIASAS-L

CGS

CHIMS

Other

Adapter – M4

Adapter – S1

Adapter – I2Adapter – H2

Adapter – I2Adapter – I1

Adapter – xxAdapter – xx

Adapter – H…

Adapter – H2Adapter – H1

SOAP/XML

Spec

S…

Spec

S2

Spec

S1

SIGINT

Spec

I…

Spec

I2

Spec

I1

IMINT

Spec

H…

Spec

H2

Spec

H1

HUMINT

Spec

M…

Spec

M2

Spec

M1

MASINT

DCGS-AAnalysts

PORAnalysts

“Above the line”

“Below the line”

Service Consumers

WSInterface

WSInterface

WSInterface

WSInterface

Native API

Native API

Native API

Web services façadeConforms to spec


Common Services (DIB / NCES / SosCOE)

SecurityServices

DiscoveryServices

WorkflowServices

System &Support

Services

StorageServices

MetadataCatalog

Logical Architecture – Objective(Spiral 5)

LeveragedWeb Service Interface Specs

DC

GS

Po

rtal /V

isualizatio

n S

ervices

Joint

Other

C2

FCS

Other

Spec

S…

Spec

S2

Spec

S1

SIGINT

Spec

I…

Spec

I2

Spec

I1

IMINT

Spec

H…

Spec

H2

Spec

H1

HUMINT

Spec

M…

Spec

M2

Spec

M1

MASINT

DCGS-AAnalysts

Trained PORAnalysts

“Above the line”

“Below the line”

Service Consumers

WSInterface

Native API

DCGS-A Services Capability

Sensor Systems

Service – I…

Service – H…

Service – H2Service – H1

Service – I2Service – I1

Service – S…Service – S2Service – S1

Service – x…Service – xxService – xxAdapter

Other

Information Source

WSInterface

WSInterface

WSInterface

WSInterface

SOAP/XML

Conforms to spec

POR Functionality Absorbed in

DCGS-A Spec

T…

Spec

T2

Spec

T1

Terrain

Spec

W…

Spec

W2

Spec

W1

Weather

Spec

F…

Spec

F2

Spec

F1

ISR Fusion


What do the interface specifications do?

Service Consumer

Service Provider

Application orService

FunctionalityMessage

MessageAPI

DCGS-A SOA Interface Specifications Enable this message exchange

Application or Service

Functionality

APIParse

TransformFormat

Input

Output

Data Data

ParseTransform

Format

Output

Input

DataData

WSDL*: Establishes what you can request and how to ask

XSD**: Establishes what data is provided in the answer

*Web Services Description Language** eXtensible Schema Definition


Web Services based SOA:Full Net-Centricity

Service Consumers

Service Providers

Service FunctionalityAPI



Services FunctionalityAPI

Service Functionality API

Message

Message





Infrastructure ServicesDCGS-A Core Services HUMINT Services

DCGS-A Services Portfolio (Partial ISR Domain View)

IMINT Services

Imagery data MTI Data

ISR Metadata Publishing

ISR Metadata Discovery

MASINT Services

Terrain Services

Geo-spatial Data

Movement Prediction

Tactical Routing Service

Visibility Analysis

ISR Data Listener

HUMINT Data

Biometrics Dossier

Biometrics Analysis

Event Interpreta-

tion

Biometrics Data

Language Translation

HUMINT Report Parsing

Dynamic Image

Analysis

Image Exploitation

MTI Tracker

Weather ServicesAS/OSINT Services

Enemy COA Analysis

Order of Battle

Analysis

Enemy Combat

Effectiveness Analysis

Enemy Behavior Analysis

Threat Analysis

Entity Correlation

SIGINT Services

SIGINT Data

Signal Parametric

Data

SIGINT Gateway

Signal Location Analysis

Comm. Network Data

Comm. Node Correlation

Emitter Track

Correlation

QoS MgmtData

Storage

Backup and Recovery

Service Reporting

Blue Force Tracking

Battle CommandGateway

Weather Overlay

Weather Forecast

ISR Alert Subscription

Weather AlertWeather

TDA

ISR Weather Effects

Event Assessment

ISR Data Transform-

ation

ISR Data Streaming

ISR Data Archival

ISR Data Snapshot

Reference Data

Management

FCS Training Gateway

ISR Data Pedigree

ISR Taxonomy

Admin

ISR Data Staging

Backup and Recovery

Security Policy Admin

Security Policy

Decision

User Profile Admin

Patch Distribution

Role AdminUser

Account Mgmnt.

Certification Validation

Security Policy

Notification

Entity Track Correlation

MASINT Data

Spectral Analysis

Target Signature

Data

Signature Id

Target Id

Coherent Change

Detection

Terrain Data Gateway

Ground Mobility

Signal Correlation

Management

RF Emissions Processing

Target Recognition

Weather Running Estimate

Workflow Execution

Service Inquiry

Service Publishing

ISR Metadata Publishing

ISR Metadata Discovery

ISR Data Listener

HUMINT Data

Blue Force Tracking

Battle CommandGateway

ISR Alert Subscription

Event Assessment

ISR Data Transform-

ation

Workflow Execution

Service Inquiry

Service Publishing

SIGINT DataSIGINT

GatewayISR Weather

Effects


DCGS-A Services Network

En

terp

rise S

erv

ice B

usMetadata

DiscoveryService

SIGINTGateway

Service

MetadataPublishing

Service

MetadataCatalog

AlertSubscription

Service

““MI Core” ServicesMI Core” Services

EventAssessment

Service

WeatherEffect

Service

IMETS(IWEDA)

E-SpaceServices

WeatherEffects

EWData

AlertCriteria

Alerts /EventsMetadataMetadata

Searches

ISR Domain ServicesISR Domain Services

InfrastructureInfrastructure ServicesServices


Async“Callbacks”

Filters

WorkflowEngine

ServiceManagement

HUMINT Data

Service(s)

HDWS (CHAMS)

Map /Coverage

Google EarthRich Client

Spec ComplianceTest Capability

Handheld

NCES Service

Discovery

TransformationEngine

Reference ImplementationLogical Architecture

BC GatewayService

ForceTracking

MIP Blue Force Tracking


Back-up


DCGS-A SOA Lessons (1) – SOA is the path, NOT the end goal

• SOA as the long-term, “to-be” solution is not good enough– Often used as excuse to maintain status quo!

• Rather, use SOA as the migration path to the future– Define incremental roadmap for “capability over time”– Service-enable legacy capabilities as a start– Target “low hanging fruits”– Develop stable interface specifications to mitigate risks

• Regular, frequent releases of deliverables (we delivered every month)

• Develop a Reference Implementation

• Show value early!


DCGS-A SOA Lessons (2) – SOA Is Not Just About Technology

• Don’t underestimate the organizational barriers to change– Choose a small but powerful group to build initial deliverables

– Identify a wide audience to review and provide feedback

– Help client understand how to utilize the SOA deliverables

• Communications and outreach (socialize the deliverables)

• Get senior level championship

• Solve client’s immediate problems to build trust and relationship

• Avoid semantic / terminology conflicts; use the client’s language

• “What is the business model?”


DCGS-A SOA Lessons (3) – Put the User Back in SOA

• SOA needs a user interface!– Needs to show how it results in improved user experience

– Demonstrate through real-world scenarios

• SOA is about enablement, not control– User-definable processes / workflows

– User-specified data scope (e.g., AOI and time range)

• Trace architecture decisions to user / operational priorities

• Have a clear story on how the SOA approach provides value to the user


DCGS-A SOA Lessons (4) – Grounded in Reality

• SOA transformation needs to be carried out under client’s existing programmatic, architectural, and technological contexts and constraints– DoD 5000 / JCIDS acquisition processes

– Joint / Army Doctrine (UJTL, AUTL, …)

– Industry best practices (CMM, CMMI, Six Sigma, …)

– Federal and DoD policies (DoDAF, DISR, NCOW-RM, C2IEDM, …)

– Architectural compliance (IEEE 1471, RUP)

– Communities of Interest (COI) and cross-organizational working groups

– Technology and solution mandates (DIB, …)

• Clearly promulgate the information sources that supported the SOA effort


Questions ?

Booz Allen & Hamilton Inc.8251 Greensboro Drive

Mclean, VA 22102(703) 917-2739

[email protected]

Greg WenzelPrincipal


Mclean, VA 22102(703) 377-5925

[email protected]

Anthony BradleySenior Associate


Mclean, VA 22102(703) 902-4617

[email protected]

Eric YuanAssociate

Documents

Bringing SOA to Life: The DCGS-A Interface Specification Drive Anthony Bradley Booz Allen Hamilton, McLean, VA 20 May 2006