Working Draft

Working Draft

DCGS-A DCGS-A

Mar 2007Mar 2007

Purpose/Agenda

• Intro & Background• SOA Approach• Lessons Learned

PURPOSE

AGENDA

• Discuss Challenges with Multiple SOA Approaches

EPLRS

SINCGARS

JNN

TROJAN

CENTRIXSBUSIPRNETJWICS

SHADOW

Prophet

Direct Action

TacticalHUMINT

Teams

MLS Guards

Air Ops

Convoy OpsBTB

ll ll ll ll

SPTll

X

FiresStability Ops

XXX

Corps

EAC

XX

Divisions

COCOM

MLS Guards

FireScout

U G S

Global Hawk

U2Rivet Joint

PSDS2

Biometrics

Overhead

COMPLEXTERRAIN

CoalitionPartners

JSTARS

NSANSACIACIANGANGA

DIADIAINSCOM

I D C

ERMP

GRCSGIG WIN-TJTRS

LongRange

Surveillance

LongRange

Surveillance

LRSSLRSS

Predator

UNCLASSIFIEDUNCLASSIFIED

NSANet

ACSACS

LandWarrior

FCS (BCT)FCS

FCSFCSMI

FCS FCS BSB FCSFCS

Embedded DCGS-A

Enterprise Support to the BCT

AF DCGS

DCGS-NDCGS-MC

Support to the BCT is the central focus of DCGS-A

DCGS-A Variants

Fixed:• Regional Focus• Continuous Collection & Analysis• Dedicated Support (Overwatch) to

Operationally Engaged Units• Ensures Information Superiority• TIBs Only

Mobile:• Deployable and Modular • Scalable to Meet Mission Needs• Operations on the Move• All Echelons

Embedded:• Software Capability• Spiral-out Common ISR Mission Tools• Integrated into Complimentary Systems

– ACS, FCS, NECC, etc.• Integrated into DCGS-A at All Echelons

DCGS-AInfrastructure

DCGS-A Comes in Three Variants:

Fixed, Mobile and Embedded

SOSCOE

DIB

NCES

DCGS-AISR Services

DCGS-A SW Foundation will be DIB, SOSCOE and NCES complaint

V5

2009+

Completes Capabilities:• Automated Fusion • Fully Integrates PORs• Ground Stations and ACS• Enterprise Network• Integrated ISR Component

to FCS• Embedded Battle

Command• Interoperability with future

sensors• Battle Command

integration (FCS & NECC)• Integrates IPV6,JTRS,

WIN-T

DCGS-A Development Evolution

DCGSFoS

Joint ISRJTRS/WIN-T

FCS

NECCNCESDOD Enterprise

• Access to over 120 databases in OIF/OEF

• Improved SA• Enhanced analyst Tools• SCI to Bde/Bn• Successfully fielded to

Iraq in Dec 05; • Primary Intel System • Transitioned to DCGS-A• V2 TPE and training sets

supported by supplementals

• Two-way Battle Command Interoperability

• Joint Interoperability• Displace ASAS Light• Builds upon, improves on V2

in OIF/OEF• Adds other capability as

prioritized by the TCM• Failover & COOP Site• Upgrade to Fixed Sites

• Provides on the move• Full spectrum BCT solution • Enhance common tools• Semi-automated Fusion • Start POR Migration• Builds on V3 SW• Designed to meet threshold

CDD requirements– Net-ready & Automated

fusion KPPs– FCS

interface/interoperability– NCES/NECC interoperable

• Completes steps skipped during QRC process

• Upgrade to Fixed Sites

V2 V3 V4

2005-06 2006-07 2007-08

Battle Command

V4 Initiates Interoperability and Interdependencies

with Transformational Systems

V3 made available to other Services

Leave Legacy Systems In Place, but Put them In the SOA Framework Via Adaptors

Pull Key Functions From Legacy and Convert to Services

Phase In SOA While Legacy Systems Are Phased Out

1

2

3

SERVER PLATFORMCLIENT PLATFORM

GC

GC

GC

GC

Visu

aliz

er

GE

GCOther

Systems

User

CommsHardware

UE

UE

UE

UE

IECIE

IEA IECIE

IEA

EECEE

EEA EECEE

EEA

SECSE

SEA SECSE

SEA

Event ServerEvent Server

DATABASEDEDBIDBI DBIDBI DATABASEDATABASEDEDBIDBIDBIDBI DBIDBIDBIDBI

Service Name•Task 1

.

.

.•Task N

Request

Response

SERVER PLATFORMCLIENT PLATFORM

GC

GC

GC

GC

Visu

aliz

er

GE

GCOther

Systems

User

CommsHardware

UE

UE

UE

UE

IECIE

IEA IECIE

IEA

EECEE

EEA EECEE

EEA

SECSE

SEA SECSE

SEA

Event ServerEvent Server

DATABASEDEDBIDBI DBIDBI DATABASEDATABASEDEDBIDBIDBIDBI DBIDBIDBIDBI

SOA / J2EE Framework

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

DIB Services

Other ServicesNCESEtc.

P2P Data MovementService

SoS

CO

E

N-Tier A

rchite

cture

SOA / J2EE Framework

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

DIB Services

Other ServicesNCESEtc.

P2P Data MovementService

SoS

CO

E

N-Tier A

rchite

cture

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

ViewerLayer

ApplicationServices

DataRepositoryLayer

InfrastructureLayer

DIB Services

Other ServicesNCESEtc.

P2P Data MovementService

SoS

CO

E

N-Tier A

rchite

cture

How to Get To The End State . . .

Software Capability Progression

V4

V3

HUMINT (HDWS,CHIMS)

Fusion & Analysis (BLK II ACE)

Prophet Control

IMINT & SIGINT (DTES)

FCS EI2 SDM/L1F/Terr

ASAS-L/ACT-E

CHIMS

DTSS-L

IMETS-L

CGS

V2

V3

V4V5

NCES

JIOC-IJIOC-I

FY07

FY10

FY08

BC

Prophet Ctl

FCS EI1 SDM/L1F

MFWS

Integrated Capability

Data Service Interface

Metadata Cat

DTSS Services

IWEDA Client

Terrain Svcs (DTSS)

Wx (IMETS)

MTI & Video (CGS)

PSDS2

COIC

Urban Fusion (RAID)

Theater/Natl DDL (TES)

GR IPF

Prophet Triton

FLT (Sequoyah)

NCES/SoSCOE

Capability Planned Leveraging of Developments

Wx (JET)

V2

BCT BC (FCS EI3+)

Joint BC (NECC)

Enhance Trackwolf

V2 Capabilities

“Stovepipe”ISR Systems

PORs

Limited access tostovepipe data…

DCGS-A builds on the V2 success…WSS VIZ BAL MB

OIF 42 3 448 0OEF 5 1 110 2TrningSets 66 31 507 11

Totals 113 35 1065 13

Fielded Equipment (V2)

…to access to all data…at all echelons

JIOC-I“Brain”

SIPRNET & JWICS

“Flattened” ISR Network

Relational DBw/multiple views

XXX

XX

X

II

MNC-I

MNF-IDoes in minutes

what used to take weeks

• Knowledge Centers• Ground Stations• Pre-Processors• Databases

Warfighter View – DCGS-A v2 Provides

• Provides access to over 120 databases throughout OIF/OEF

• Improved SA• Enhanced Analyst Tools• SCI to Bde/Bn• Successfully fielded to Iraq in Dec 05; • Primary Intel System

DCGS-A v2 is not …• Replacement for any POR• Full-spectrum capable• Single source processor• Automated fusion• Ground station

V3 Capabilities

• V3 Provides:– Ease of use via MFWS Functionality to

Include: Visualization; Mapping Services; Tools to Support Data Mining, Correlation, Alerting, Analysis and Presentation

– A Common Framework Leveraging the Advanced Analytical Capabilities of JIOC-I and Incorporates them into a DCGS-A Enterprise

– ABCS Interoperability– Includes Portal Access to DCGS-A Data

/ Products via Existing Networks• Providing a Means to Support

Rehosting on/Displacement of ASAS-Light

V2

V3 is a Software Only Build to OIF/OEFV3 is a Software Only Build to OIF/OEF

V3.1 begins migration of ASAS FoS (ASAS-L and ACT-E) into DCGS-A

V3.1 begins migration of ASAS FoS (ASAS-L and ACT-E) into DCGS-A

JointInteroperability

Warfighter View:• Battle Command Interoperability • Joint Interoperability – DCGS Integrated Backbone (DIB) enabled• Displace ASAS Light

V4 Capabilities for SWB 10-12

- ISR Component to Battle Command- Provides actionable intelligence - Running estimate - Planning and collaboration- Modular and scalable- Mobile and Transportable- Enables distributed operation- V4 supports EBCT

- Multiple source exploitation (SIGINT, GEOINT, HUMINT, MASINT, All-Sources,

Open Source)- Intel Fusion

- Access to Data (including BCT Sensors)- Net-centric compliant (NECC interoperable)

NSANET

JWICS

SIPRNET

CENTRIX

INTERNET

CIA NGADIADCGS-MC

DCGS-N

DCGS-AF

JSTARSPSDS2

Prophet

IBSTacticalHUMINT Teams

Predator

NSA

Hunter Shadow

CoalitionPartners

WeatherApache

Longbow ARH

JIC / JAC / JTF

MICADNBCRSPEWD

MELIOSLand Warrior

LCMR

LRAS3

Firefinder

ABCS /BC Server

OpenSource

I-REMBASS

Completes POR CapabilityCompletes POR Capability

Global Hawk

GRCS

U-2

V4.1(MIB)

EP-3

NTM

F/A-18DCGS-A V4 Mobile

Software ReadySep ’08

System ReadyFY09

INSCOMI D C

DCGS-A

V4 Increment 1 SOA Goals…

• Integrated Portal– Create an integrated Portal available to both internal and external users– Portal presents both domain-specific and multi-domain JSR 168 compliant portlets

• JSR 168 promotes capability of using portlets in different Portal frameworks• Integrated Data Access

– Develop single multi-domain search interface compliant with NCES Content Discovery and DDMS• Establishes architecture for integration of NCES compliant data sources and integration of DCGS-A nodes into

larger enterprise searches• Introduction of SOA Infrastructure Toolset

– Commercial Enterprise Service Bus (ESB) used to realize Multi-INT objectives though content-based routing and orchestration of domain services using BPEL 1.1 compliant workflow

• BPEL compliance promotes capability of porting workflow to different workflow engines– Use of UDDI compliant service repository

• UDDI Repository wrapped in NCES defined services to abstract complexities of UDDI and promote portability to different repository implementations

• Establishment of SOA Governance Procedures– Government and industry jointly own process for specification and validation of service interface

standards• Implementation of a Layered DIB Compliant Architecture

– User Facing Layer – Portal and Desktop Visualization Framework (MFWS/VIPER)– Processing Layer – Service Orchestration– Data Layer – Publication of Metadata to DIB MDC for inter-service DCGS interoperability– Core Layer – SOA security model based on NCES Security Services

SOA Governance

Governance Activity Design Time

Run Time

Specify Service Interface Standards • Industry standard for interoperability / syntax (WS-I Profile, WSDL, XML Schema)• Domain Specific Services / Data Types

–WSDL (ports, operations, parameters), Schema (data types)Validate Service Interfaces Adhere to StandardsCatalog Services• Store Service Interface Artifacts (WSDL, Schema, Usage Documentation) in Service

Spec Catalog• Maintain version control / version identification for services during lifecyclePublish Service Interfaces To Registry• Service metadata for discovery

–Descriptive data for query, Version Identification• Service execution/binding information• Service availability/Quality of Service informationMonitor Service Interfaces• Collect service statistics

–Usage, Availability, Performance / Quality of Service• Update service statistics in registry• Monitor SLA contracts SOA governance manages and controls complexity by specifying,

validating, cataloging, publishing, and monitoring service interfaces

== Tools, Architecture, Standards, Documentation

DIB/MDC Variants

Name Sponsor Tools* Architecture Standards Documentation Delivery Enhancements to DIB 1.0 Availability/LicensingDIB 1.0

Air Force •WebLogic 8.1 sp3•Oracle 9i•MDC (WebLogic / Oracle)•Supports Solaris 8

Documented in AF 10.2 design reviews

Listed in DIB delivery document

Delivery, install, and programmer guides/docs

Boxed CD Set

N/A •80 CPU licenses of WebLogic owned by Army and available to DCGS-A (second purchase of 200 licenses ongoing) •Oracle Army enterprise licensing available•Installable MDC delivered on DIB CDs

RDE 1.5

RaytheonDCGS-A V3

•MDC (JBoss 4.0.3 / Oracle10g)•Win 2003/RHEL

Documented in DCGS-A V3 CDR slides

No changes documented

“Reconfiguration of the MDC after a Clone”

Installed on V3 hard drives

•MDC Query Enhancement•MDC Events•MDC Results Folder

•JBoss open source licensing available

DIB 1.2 Beta1

DIB Mgmt Office (DMO)

•WebLogic 8.1 sp5•Oracle 10g•MDC (WebLogic / Oracle)•Supports Solaris 8, Win 2003, RHEL 4.2

No changes expected

No changes expected

Documentation updates expected

Install-able CDs expected

•MDC Enterprise Bridge•MDC Events•MDC Results Folder•MDC OpenMap•MDC Runtime XSDs

•Army purchased WebLogic licensing (listed above) is upgradeable at no cost•March 2007 beta availability •Fielding at DCGS-A Fixed Ft. Gordon

DIB 1.2

DMO •WebLogic 8.1 sp6•Oracle 10g•MDC (WebLogic / Oracle)•Supports Solaris 10, Win 2003, RHEL 4.2

No changes expected

No changes expected

Documentation updates expected

Install-able CDs expected

•1.2 Beta1 Updates•MDC Radial Search Fixes•MDC Search Limit Fixes•NSA guided install fixes

•Army purchased WebLogic licensing (listed above) is upgradeable at no cost•December 2007 availability

DIB 2.x

DMO released RFI for evolution of DIB late 2006

“Emphasize DIB standards and architecture, not product implementation”

TBD “Validation methodology / framework allows DIB implementation developers to verify DIB interoperability & standards compliance”

“Software, documentation, configuration / install procedures available to DCGS COI as open source”

TBD TBD TBD

* Only primary tools are shown

Use of DIB 1.2 Beta1 lines DCGS-A up with DMO plans and makes use of existing Army WebLogic purchases

Industry

Government

DCGS-A Specification Refinement Process

DCGS-A Service Interface Specification v1.7

DCGS-A V4 Services

Draft WSDLs retrieved from 1.7 Spec

Draft XSDs retrieved from 1.7 Spec

DCGS-A ConsolidatedBaseline CM

DCGS-A Service Interface Specification vX.X

Subject MatterExperts

WSDLs

XSDs

WSDLs mapped to services

XSDs mapped to data model

Refined WSDLs/XSDs used in DCGS-A system

WSDLs XSDs

WSDLs

XSDs

Service Implementers

WSDLs

XSDs

Deployed System

UDDIRegistry

Government and Industry jointly own Governance Process for Service Interface Standards

DCGS-A V4 Data Model

Use of Service Interface Spec help maintain open system

Future Challenges

• FCS SoSCOE– IDL Based SOA– Optimized for the tactical radio net environment

• Leveraging each others developments

• Interoperability – Both have legacy messaging interfaces

• USMTF, JVMF– Web-services to OMG IDL

• Use of Proxies– Discovery

• UDDI, JXTA

Lessons Learned

• Leverage systems that you have

• Start with most pressing mission critical functions

• Use proof of concepts and demos

• Use right technology for right tasks

• Collaborate

Working Draft

Working Draft

Questions

Contact Information

Jeffrey Malapit703-349-7071

System of Systems Analytics, Inc

Support to PM DCGS-AJeffrey.malapit@us.army.mil