Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob

Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T 1

Agenda What is Battle Command Near Term Initiatives – – – – – TBES AD Server Consolidation Services COOP Future Vision 2

PEO C3T Battle Command Tactical Tactical Network Network Platform Satellite (JNN, SMART-T, GMF ) Radio (LOS, NTDR, EPLRS, ) Net OPS, Firewalls Tactical (FBCB2/BFT) Logistics (MTS) Dismounted Force Handhelds Messaging Lower TI TSG XX Services DIV/BCT CP LAN, Upper TI JTF AOC Net Centric BC Server Suite Battle Command Commander & Key Leader System Staff User Notebook Configurable Client Tools: CPoF, JTCW, Web Battle Command Common Services / Enterprise Services (Email, Security, Web Portal.) Interoperability Services ( PASS/DDS) Web Apps, C2 Data & Services, Etc. TOCS TOCS Integrated Command Post Platform Infrastructure (Servers, Power, Switches.) Environmental Control (AC) Tents, Shelters 3

Introduction Task from the Army CIO/G-6 500-Day Strategic Goal 6: “Deliver an integrated enterprise strategy that influences Joint and Army use of Information Management and Information technology in furthering the warfighting capabilities.” 4

Evolution of Battle Command Scope Intelligence Cross BOS KM From Information to Intelligence! BOS based KM LTG Vines, XVIII Corps CoS Net Centric Approach Common Map Display OIF1 OIF2 OIF3 Time Examples: MSR Evaluation: Three primary MSRs in Iraq. Provide a tool that would consider time of day, week and month and provide analysis of a planned trip by MSR showing percent chance of incident based on historical data. Incident Best Response: Typical responses are used to respond to critical incidents. These responses have various measures of success and the success differs based on location. When a critical incident occurs, provide a list of responses along with their success percentage for that location. 5

Adapting to Technology and Requirement Change Capabilities 1. Align with Industry best practices and standards Capability Convergence Graph 2. Adopt proven solutions & migrate from there (CPoF, JADOCS, JIOC-I) Web Services Network Mature 4 3 ABCS 6.4 BCCS IMF 3. Use “Best of Breed” Web technologies with an Open Controlled Source process to enable cross development between Units and PEO C3T 2 MS .NET 4. Continuous Engineering Using adaptive processes enabling agile technology insertion Requirements / Needs BCCS – Battle Command Common Services 1 ABCS 6.4 7 1 (ABCS GE) Technology Innovation TIME C4ISR Implementation IMF – Information Management Framework HIC / SASO 6

Tactical Business Enterprise Services (TBES) – extending ABCS Services Active Directory Exchange SQL Server DNS SMS/SUS Virus Protection Microsoft Server Infrastructure SharePoint Portal Server integration and web-parts Real-Time Collaborative tool suites Server/System Backup, Failover and Restoration Supporting Modularity by Providing Consistent, Engineered & Supported Infrastructure Architecture Engineering, Detailed Documentation, Accreditation\Validation, Administrator Training, HW Procurement & FSR Support 58% of ABCS 6.4 inte raction relies o n TBES 7

CIO G6 – Interim Guidance on Microsoft Directory Services Windows Server 2003 Active Directory Authentication and authorization service Synchronized Global Address List Centralized management of servers and client computers Centralized administration of users and computers Centralized management of network resources Directory services for applications Forest: When one or more domains share a directory structure thus enabling centralized management of accounts, resources and security. XX Every unit is self supporting Guidance Overview Generating Force SIPRNET AD Architecture: One Forest for Theater, one additional Enterprise Application forest (PEO EIS) Deployable Force NIPRNET and SIPRNET AD Architecture: Separate Forests for each UEy, UEx, BCT, and selected UAs (PEO C3T – develop system arch & create plan) Enterprise Directory Service (EDS) will provide the foundation for communication and integration across AD forests. (PEO EIS in coordination with PEO C3T) Provisioning solution to support moving users and services between forests 8

Server Consolidation Present Intermediate Objective hp ProLiant DL 580 UID Int Ex t S to rage Server 2 3 4 S yst Stat Dp lx Sp d 1 UI D Mode UI D UID UID UID UID UID UID 2 4 6 7 8 9 10 NI C 1 Do wn li nks 1 3 5 11 12 13 14 F P Upli nks XC NI C 1 NI C 2 NI C 2 NI C 3 NIC 1 NI C 4 NIC 2 15 16 17 18 19 20 21 22 23 24 NIC 3 NIC 1 NIC 1 NIC 1 NIC 1 NIC 1 NIC 2 NIC 2 NIC 2 NIC 2 NIC 2 NIC 3 NIC 3 NIC 3 NIC 3 NIC 3 NI C 3 NI C 4 23x Con sol e 24x CORE Pwr /Rst Ci sco N e twor k in g Cisco GES M HP Bl ad eS ystem OPTIONS OPTIONS TBES & ABCS Servers not Integrated Mix of Unit and PEO provided equipment No TBES FSR support Core Services for TBES & ABCS Servers Engineered & Configured Options (ex. VTC) PEO engineered arch Trained FSRs and soldier SAs h p BL25p HP BL45p hp BL 25p hp BL 25p hp BL25p h p B L25p h p B L2 5p HP BL45p rj45 Patch CORE TBES & ABCS Servers Integrated Engineered & Configured Options BCCS Architecture for all Phases of Deployment CPP Integrated Consistent HW Reduced support costs 9

STEP Site Server Locations Or MNC-I POP2 For DISN Services UEx TDMA – IP FDMA – IP CKT EHF via SMART-T Ku-Band Satellite FDMA X-Band via GMF L-Band Alternate Route LEASE CIRCUIT, DISN, MNC-I POP2 LOS MNC-I TDMA Unit Ku-Band Hub Common Services Server Stacks BC Svr Notebook SHF X-Band Satellite UEx Forest INMARSAT L-Band Satellite UA Forest UA Forest L-Band Hub in Sanctuary EHF-Band Satellite ISDN LINES JNN TSC-85 XX DMAIN JNN SMART-T Vendor L-Band Hub JNN XX DTAC JNN II X JNN X MAIN II Ku JNN II REAR UA TDMA Mesh #1 Ku II II Ku II Ku Ku X MAIN REAR TDMA - IP ABCS 6.4 BCT/UA (EPLRS) SMART-T X II Ku JNN TDMA Mesh #2 X USMC DTAC TSC-93 JNN SMART-T XX II Ku UA II II Ku Small Node Ku Ku ABCS 6.3 BCT/UA 8 TDMA Nets (7 UAs DIV) 10 FDMA Links (NOT ALL LINKS SHOWN) 10

Operational Example of the Framework Knowledge Forums Alerts SharePoint Portal J2EE ABCS Interop Web Server (IIS) Database High Availability VoIP Mail Security Search OPORD Bridge Calc Collateral Damage Est Web Applications Air Coord Req RFI TTP Log STAT Web COP Weather News Tailored by Unit from PEO C3T provided Web Applications WEB COP Reports Weather Route Planning TO & Battle Position TO/Battle Staff Tree SIG ACTS BUB Viewer C4ISR SIG ACTS Unit Sites Unit 2Name Logo Forums Unit1Name Logo Provided, Developed, Integrated by PEO C3T Infrastructure Services Provided, Supported, Integrated by PEO C3T 11

Services Integration Framework CPoF Process Based Collaboration Commanders Intent enables staff to share pertinent refined BFA specific information. CDR CDR CPOF VoIP Pasteboard G2 G2 FSO FSO G3 G3 G4 G4 Data Service Data Service Data Service Data Service Services Integration Framework Services Integration Framework Each BFA domain provides essential data services to the Services Integration Framework. These services are collected in the composition data grid for orchestration into the IM Framework services. G2 G2 Domain Domain Process Process && Services Services FSO FSO Domain Domain Process Process && Services Services G3 G3 Domain Domain Process Process && Services Services G4 G4 Domain Domain Process Process && Services Services 12

Services Considered for Consolidation Phase 3: Information Management Framework IM Framework Enterprise Services Domain Controller Directory Services – MS Active Directory / Server 2003 – IIFP (requires SQL Server) Email Asynchronous Collaboration Web Portal Technologies – File Sharing (SharePoint, SQL Server) – Web Applications – Unit Web Sites – MS Exchange 2003 Real Time Collaboration Common Database – MS SQL Server Domain Name Services – MS Server 2003 DNS Automatic Upgrades – SMS/MS SUS Anti-virus – Norton Anti-Virus Time Synchronization – SNTP JITC Certified Collaborative Tools – IWS (101 & MNC-I use) – CENTCOM requires DCTS VOIP Battle Command Server (BCS) Publish And Subscribe Service (PASS) Command & Control Registry (C2R) – C2R Planner (Management UI) – Netscape Directory Server (LDAP) – COE Alerts Battle Command Common Services (BCCS) C2PC Gateway Near Real Time Service (NRTS) MCS DB (requires SQL Server) 13

COOP Plan (AKO Fwd) Managing Services through all phases Provides Backup Recovery from Failover Unit Prior to Deploying pushes Virtual Servers and Data to AKO Fwd When unit server goes off-line, AKO Fwd virtual server maintains operations Hub JNN JNN Enterprise Services JNN BC Services TBES Sanctuary Single Point of Entry Unit Virtual Site & Data Unit Virtual Site & Data Unit Virtual Site & Data TOC/AKO Fwd – HW Platform AKO Single Point of Entry manages what server is currently active When Unit gets in place, and data is synchronized to its servers it becomes the primary. Data continues to be synchronized between the unit and AKO Fwd virtual server If the unit server goes off-line (planned or unplanned) the AKO Fwd virtual server maintains operations 14

Battle Command Technical Vision FY05-07 FY08-10 Battle Command CPoF MCS Intel Services Army & Marine Battle Common Command Viewers Services GCCS-A FBCB2 AFATDS Viewers are a Commodity Maneuver IMETS PASS BCS3 FY11-16 Fires Maneuver Engineer AMDWS DTSS Fires Air FCS/JC2 Logistics ASAS-L Note: Some system 1 to 1 interfaces still exist Server Centric Centralized service for Data exchange using standard schemas System of BFA independent servers and clients Gateway Lower TI Logistics DCGS-A Engineer Air TAIS others Logistics Intel Services Battle Command Services DDS TBES Enterprise Services Service Centric Common Viewers (Smart clients – CPoF, JTCW, Thin client – Web) Services start to replace servers & utilize common set of data Clients interface thru services DDS Battle Cmd TBES Enterprise Services Network Centric Viewers downloaded on demand (rich thin clients) Domain Specific Services that utilize common set of data Clients interface thru services 15

Available Reference Documents 101st AASLT Division Account Naming 1 JUN FM 6-02 32 TI NAMING APPENDIX B UEy UEx UA DOMAINS 543 10 MAR 05 0635 IM Framework Information Paper NOV 2005 Interim Guidance on MS Directory Services CIO G-6 DRAFT 2005 TBES Deployment Doc. May 10rp TBES Services White Paper Final Draft NOV 2005 PEO C3T AD Implementation 2005 These documents will be available for your use after the close of the conference. They will reside with the slides. 16

17