Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Working Draft DCGS-A Mar 2007 Working Draft
  2. 2. Purpose/Agenda PURPOSE • Discuss Challenges with Multiple SOA Approaches • Intro & Background AGENDA • SOA Approach • Lessons Learned
  3. 3. UNCLASSIFIED Enterprise Support to the BCT U2 Rivet Joint Overhead NSA NSA Global Hawk CIA CIA DIA DIA Predator NGA NGA EAC INSCOM JSTARS IDC ACS X XX COCOM XXX Divisions ll ll ll FCS ll ll FCS (BCT) MLS Corps BTB SPT Guards Fires Stability Ops EP MI Convoy Ops FCS LR FCS FCS BSB FCS S FCS FCS MLS JNN Guards Air Ops LandWarrior AN LRSS LRSS GRCS SINCGARS JTRS TRO T WIN-J Tactical GIG FireScout HUMINT Direct Teams Action AF DCGS SHADOW Long Long Range Range UGS DCGS-N Prophet Embedded DCGS-A Surveillance Surveillance ERMP COMPLEX DCGS-MC TERRAIN Biometrics CENTRIX Coalition PSDS2 SBU Partners SIPRNET JWICS NSANet Support to the BCT is the central focus of DCGS-A
  4. 4. DCGS-A Variants DCGS-A Comes in DCGS-A SW Three Variants: Foundation will be Fixed, Mobile and Fixed: DIB, SOSCOE and Embedded NCES complaint • Regional Focus DIB • 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 SOSCOE • Integrated into Complimentary Systems – ACS, FCS, NECC, etc. • Integrated into DCGS-A at All Echelons NCES DCGS-A DCGS-A Infrastructure ISR Services
  5. 5. DCGS-A Development Evolution V4 Initiates Interoperability and Interdependencies with Transformational Systems DCGS JTRS/ FoS Joint ISR WIN-T 2005-06 2006-07 2007-08 2009+ FCS V2 V3 V4 V5 • Access to over 120 • Two-way Battle Command • Provides on the move Completes Capabilities: databases in OIF/OEF Interoperability • Full spectrum BCT solution • Automated Fusion • Improved SA • Joint Interoperability • Enhance common tools • Fully Integrates PORs • Enhanced analyst Tools • Displace ASAS Light • Semi-automated Fusion • Ground Stations and ACS • SCI to Bde/Bn • Builds upon, improves on V2 • Start POR Migration in OIF/OEF • Enterprise Network • Successfully fielded to • Builds on V3 SW Iraq in Dec 05; • Adds other capability as • Integrated ISR Component • Designed to meet threshold to FCS • Primary Intel System prioritized by the TCM CDD requirements • Failover & COOP Site • Embedded Battle • Transitioned to DCGS-A – Net-ready & Automated Command • V2 TPE and training sets • Upgrade to Fixed Sites fusion KPPs – FCS • Interoperability with future supported by sensors supplementals interface/interoperability – NCES/NECC interoperable • Battle Command • Completes steps skipped integration (FCS & NECC) during QRC process • Integrates IPV6,JTRS, • Upgrade to Fixed Sites WIN-T V3 made available to NCES NECC other Services DOD Enterprise Battle Command
  6. 6. How to Get To The End State . . . 1 Leave Legacy Systems In Place, but Put them In the SOA Framework Via Adaptors 2 Pull Key Functions From Legacy and Convert to Services CLIENT PLATFORM SERVER PLATFORM GE IE Comms Request Service Name IEA IEC Hardware User GC •Task 1 Visualizer GC EE GC EEA EEC Other . GC Systems SE . GC SEA SEC UE Response DE . UE DBI DBI DBI DBI DATABASE •Task N Event Server Phase In SOA While Legacy Systems Are Phased Out 3 Viewer CLIENT PLATFORM SERVER PLATFORM Layer GE IE Comms e IEA IEC ur Hardware User GC ct Visualizer it e GC EE ch SoS COE GC EEA EEC Application Other Ar Services GC SE Systems r SEA SEC ie -T GC UE Data N DE Repository UE DBI DBI DBI DBI DATABASE Layer Other Services NCES P2P Data Movement Event Server Infrastructure DIB Services Layer Etc. Service SOA / J2EE Framework
  7. 7. Software Capability Progression V3 FY07 ASAS-L/ACT-E V4 FY08 FCS EI1 SDM/L1F HUMINT (HDWS,CHIMS) V5 FY10 Metadata Cat Fusion & Analysis IWEDA Client BCT BC (FCS EI3+) (BLK II ACE) DTSS Services Prophet Control Joint BC (NECC) V2 MFWS Terrain Svcs (DTSS) GR IPF JIOC-I V2 JIOC-I Prophet Triton V3 Prophet Ctl V4 CHIMS Wx (IMETS) DTSS-L MTI & Video (CGS) Wx (JET) IMETS-L Urban Fusion (RAID) IMINT & SIGINT (DTES) CGS Theater/Natl DDL (TES) FLT (Sequoyah) Integrated Capability BC FCS EI2 SDM/L1F/Terr Enhance Trackwolf Data Service Interface PSDS2 NCES NCES/SoSCOE COIC Capability Planned Leveraging of Developments
  8. 8. V2 Capabilities Limited access to …to access to all data…at all echelons stovepipe data… “Flattened” ISR Network MNF-I Does in minutes XXX what used to MNC-I Relational DB take weeks w/multiple views XX PORs JIOC-I “Brain” X SIPRNET & JWICS • Knowledge Centers • Ground Stations II • Pre-Processors • Databases “Stovepipe” ISR Systems DCGS-A builds on the V2 success… Fielded Equipment (V2) Warfighter View – DCGS-A v2 DCGS-A v2 is not … WSS VIZ BAL MB Provides • Replacement for any POR • Provides access to over 120 • Full-spectrum capable OIF 42 3 448 0 databases throughout OIF/OEF • Single source processor • Improved SA OEF 5 1 110 2 • Automated fusion • Enhanced Analyst Tools • Ground station Trning • SCI to Bde/Bn Sets 66 31 507 11 • Successfully fielded to Iraq in Dec 05; • Primary Intel System Totals 113 35 1065 13
  9. 9. 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 V2 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 Warfighter View: • Battle Command Interoperability • Joint Interoperability – DCGS Integrated Backbone (DIB) enabled • Displace ASAS Light V3 is a Software Only Build to OIF/OEF V3 is a Software Only Build to OIF/OEF Joint Interoperability V3.1 begins migration of ASAS FoS (ASAS-L and V3.1 begins migration of ASAS FoS (ASAS-L and ACT-E) into DCGS-A ACT-E) into DCGS-A
  10. 10. V4 Capabilities for SWB 10-12 MICAD ABCS / NBCRS BC Server PEWD Apache MELIOS Tactical JSTARS Predator Hunter Shadow Longbow PSDS2 Weather IBS ARH Land Warrior HUMINT LCMR Teams I-REMBASS NTM GRCS LRAS3 Firefinder EP-3 JIC / JAC / JTF U-2 NSANET DCGS-A Global Hawk V4 Mobile INSCOM F/A-18 JWICS Prophet IDC SIPRNET V4.1 (MIB) CENTRIX Coalition DCGS-A INTERNET Partners Open Software Ready Source DCGS-AF Sep ’08 NSA System Ready FY09 DCGS-N - ISR Component to Battle Command DCGS-MC - Provides actionable intelligence CIA DIA NGA - Multiple source exploitation (SIGINT, - Running estimate - Planning and collaboration GEOINT, HUMINT, MASINT, All-Sources, - Modular and scalable Open Source) - Mobile and Transportable - Intel Fusion - Enables distributed operation - Access to Data (including BCT Sensors) - V4 supports EBCT - Net-centric compliant (NECC interoperable) Completes POR Capability Completes POR Capability
  11. 11. 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
  12. 12. SOA Governance Governance Activity Design Run Time 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 Standards Catalog Services • Store Service Interface Artifacts (WSDL, Schema, Usage Documentation) in Service Spec Catalog • Maintain version control / version identification for services during lifecycle Publish Service Interfaces To Registry • Service metadata for discovery –Descriptive data for query, Version Identification • Service execution/binding information • Service availability/Quality of Service information Monitor 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
  13. 13. DIB/MDC Variants == Tools, Architecture, Standards, Documentation Name Sponsor Tools* Architecture Standards Documentation Delivery Enhancements to DIB 1.0 Availability/Licensing DIB Air Force •WebLogic 8.1 sp3 Documented Listed in DIB Delivery, install, Boxed N/A •80 CPU licenses of WebLogic owned by 1.0 •Oracle 9i in AF 10.2 delivery and CD Set Army and available to DCGS-A (second •MDC (WebLogic / design document programmer purchase of 200 licenses ongoing) Oracle) reviews guides/docs •Oracle Army enterprise licensing •Supports Solaris 8 available •Installable MDC delivered on DIB CDs RDE Raytheon •MDC (JBoss 4.0.3 / Documented No changes “Reconfiguration Installed •MDC Query Enhancement •JBoss open source licensing available 1.5 DCGS-A Oracle10g) in DCGS-A documented of the MDC after on V3 •MDC Events V3 •Win 2003/RHEL V3 CDR a Clone” hard •MDC Results Folder slides drives DIB DIB Mgmt •WebLogic 8.1 sp5 No changes No changes Documentation Install- •MDC Enterprise Bridge •Army purchased WebLogic licensing 1.2 Office •Oracle 10g expected expected updates able •MDC Events (listed above) is upgradeable at no cost Beta1 (DMO) •MDC (WebLogic / expected CDs •MDC Results Folder •March 2007 beta availability Oracle) expected •MDC OpenMap •Fielding at DCGS-A Fixed Ft. Gordon •MDC Runtime XSDs •Supports Solaris 8, Win 2003, RHEL 4.2 DIB DMO •WebLogic 8.1 sp6 No changes No changes Documentation Install- •1.2 Beta1 Updates •Army purchased WebLogic licensing 1.2 •Oracle 10g expected expected updates able •MDC Radial Search Fixes (listed above) is upgradeable at no cost •MDC (WebLogic / expected CDs •MDC Search Limit Fixes •December 2007 availability Oracle) expected •NSA guided install fixes •Supports Solaris 10, Win 2003, RHEL 4.2 DIB DMO “Emphasize DIB TBD “Validation “Software, TBD TBD TBD 2.x released standards and methodology / documentation, RFI for architecture, not framework configuration / evolution product allows DIB install of DIB late implementation” implementatio procedures 2006 n developers available to to verify DIB DCGS COI as interoperability open source” & standards compliance” Use of DIB 1.2 Beta1 lines DCGS-A up with DMO plans and makes use of existing Army WebLogic purchases * Only primary tools are shown
  14. 14. DCGS-A Specification Refinement Process Use of Service Interface Spec help maintain open system DCGS-A Service Interface Government DCGS-A Service Interface Specification v1.7 Specification vX.X DCGS-A Consolidated Baseline CM Draft XSDs retrieved Government and Industry jointly Draft WSDLs retrieved from 1.7 Spec from 1.7 Spec own Governance Process for WSDLs XSDs Service Interface Standards XSDs WSDLs Refined WSDLs/XSDs used in DCGS-A system WSDLs mapped Subject Matter Experts to services XSDs Service WSDLs Implementers UDDI XSDs WSDLs Registry XSDs mapped to data model DCGS-A V4 Services DCGS-A V4 Data Model Deployed System Industry
  15. 15. 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
  16. 16. 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
  17. 17. Working Draft Questions Working Draft
  18. 18. Contact Information Jeffrey Malapit 703-349-7071 System of Systems Analytics, Inc Support to PM DCGS-A Jeffrey.malapit@us.army.mil